Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 9c6fef5bb100770e28a15d525be5d1b723f01de5
commit9c6fef5bb100770e28a15d525be5d1b723f01de5[log] [tgz]
authorLuca Prete <luca@onlab.us>Mon Sep 11 14:57:32 2017 -0700
committerLuca Prete <luca@onlab.us>Mon Sep 11 14:57:32 2017 -0700
tree0dc82d35a37bc1739910bc540d3b920e5d593152
parent4e0c2ede8552a7fcbf0ceecd98f0cc9998d7919f [diff]
Fixing master book.json

Change-Id: If61f691cc9656b39bcaa42affac35721eeff6f2b
1 file changed
tree: 0dc82d35a37bc1739910bc540d3b920e5d593152
  1. .gitignore
  2. .gitmodules
  3. Jenkinsfile
  4. Jenkinsfile.ciab
  5. Jenkinsfile.imagebuilder
  6. Jenkinsfile.newBuildSystem
  7. LICENSE.txt
  8. Makefile
  9. README.md
  10. Vagrantfile
  11. ansible.cfg
  12. ansible/
  13. build.gradle
  14. buildSrc/
  15. config/
  16. docker_images.yml
  17. docs/
  18. elk-logger/
  19. genconfig/
  20. gradle.properties
  21. gradle/
  22. gradlew
  23. gradlew.bat
  24. image_logs/
  25. logs/
  26. milestones/
  27. podconfig/
  28. scenarios/
  29. scripts/
  30. settings.gradle
  31. 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: