Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 7ec0e39ec05cf6096af0ff0c96c72d4ea3b6efa4
commit7ec0e39ec05cf6096af0ff0c96c72d4ea3b6efa4[log] [tgz]
authorZack Williams <zdw@opennetworking.org>Wed Jan 24 17:38:56 2018 -0700
committerZack Williams <zdw@opennetworking.org>Wed Jan 24 17:38:56 2018 -0700
treee36df5004a8dc59658e2ed8767d75dde1b5da725
parentf2572b551937a65a3878360741c67519ab9dec80 [diff]
[CORD-2603]
Define headnode so that interface-config can differentiate nodes

Change-Id: Iaacefc459f7c51da55326951ffb56ce68667251c
3 files changed
tree: e36df5004a8dc59658e2ed8767d75dde1b5da725
  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: