Gitiles
Code Review Sign In
gerrit.opencord.org / cord / e92458d1d28bf8714bdee5fa2826de89c7be3664
commite92458d1d28bf8714bdee5fa2826de89c7be3664[log] [tgz]
authorLuca Prete <luca@opennetworking.org>Wed Oct 18 11:52:30 2017 -0700
committerLuca Prete <luca@opennetworking.org>Wed Oct 18 11:53:26 2017 -0700
tree4adbc295c5a348da3833416f42430835c3fcf390
parentf9cad993dc09fe153c17b0f6717a9140efc9f5b7 [diff]
Revert "Adding multicore functionalities"

This reverts commit a7cd43f15e1e3f3ff5feccdfbfaa1e16ead480de.

Change-Id: I5b6664f7f01963d9f25f1073cf9df3787936bfd9
1 file changed
tree: 4adbc295c5a348da3833416f42430835c3fcf390
  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: