Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 4350d5fcf39b9b0f3b0075ff6c5a31c7fc175275
commit4350d5fcf39b9b0f3b0075ff6c5a31c7fc175275[log] [tgz]
authorMarc De Leenheer <marc@opennetworking.org>Fri Dec 01 17:35:57 2017 -0800
committerMarc De Leenheer <marc@opennetworking.org>Fri Dec 01 17:35:57 2017 -0800
treed0a15d77411ab7425363b8492ef43a5e5580db61
parentfd97e020e9a05aab5e18a15455ff75228fa374ee [diff]
Split multiple commands in separate sessions to avoid permission problems

Change-Id: Ib9ac49493108e3460049fdae9cbf44322807f02a
1 file changed
tree: d0a15d77411ab7425363b8492ef43a5e5580db61
  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: