Gitiles
Code Review Sign In
gerrit.opencord.org / cord / c597d42fb53974a8e808c70f1f765ba72e4f6305
commitc597d42fb53974a8e808c70f1f765ba72e4f6305[log] [tgz]
authorZack Williams <zdw@opennetworking.org>Mon Jan 22 14:25:06 2018 -0700
committerZack Williams <zdw@opennetworking.org>Tue Jan 23 18:35:45 2018 +0000
tree97529e4f8ec48c981eb2fc318bea1bc1b0140ffc
parentc56517f4661bef47a8729745dd494fdb3ed24567 [diff]
[CORD-2566]
Avoid creating nested genconfig directories

Change-Id: I00c69da4344a8c5bdf9197b5edc76aab55339f34
1 file changed
tree: 97529e4f8ec48c981eb2fc318bea1bc1b0140ffc
  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: