Gitiles
Code Review Sign In
gerrit.opencord.org / cord / a61248f7861ce3f95b0624d8b92c836297f13a20
commita61248f7861ce3f95b0624d8b92c836297f13a20[log] [tgz]
authorMatteo Scandolo <teo@opennetworking.org>Wed Jan 24 08:47:16 2018 -0800
committerMatteo Scandolo <teo@opennetworking.org>Wed Jan 24 09:45:52 2018 -0800
tree06253ba7d48be32fee56b4186db065a7f29ccbb2
parentc597d42fb53974a8e808c70f1f765ba72e4f6305 [diff]
[CORD-2600] Moving loadconfig into an ansible role

Change-Id: Ifb6bfb6f8cf89212ec518c443e9c9b1af662a236
2 files changed
tree: 06253ba7d48be32fee56b4186db065a7f29ccbb2
  1. .gitignore
  2. .gitmodules
  3. Jenkinsfile.ciab
  4. Jenkinsfile.imagebuilder
  5. Jenkinsfile.newBuildSystem
  6. LICENSE.txt
  7. Makefile
  8. README.md
  9. ansible.cfg
  10. ansible/
  11. docker_images.yml
  12. docs/
  13. elk-logger/
  14. genconfig/
  15. image_logs/
  16. logs/
  17. milestones/
  18. podconfig/
  19. scenarios/
  20. scripts/
  21. utils/
README.md

Building and Installing CORD

This is the main entry point for building and installing CORD.

If this is your first encounter with CORD, we suggest you start by bringing up an emulated version called CORD-in-a-Box. It installs CORD on a set of virtual machines running on a single physical server. Just follow our CORD-in-a-Box Guide.

You can also install CORD on a physical POD. This involves first assembling a set of servers and switches, and then pointing the build system at that target hardware. Just follow our Physical POD Guide.

For additional information about the CORD Project, see: