Gitiles
Code Review Sign In
gerrit.opencord.org / cord / be198b8ef3abcfc128930ae9f5b766864924a65b
commitbe198b8ef3abcfc128930ae9f5b766864924a65b[log] [tgz]
authorLuca Prete <luca@onlab.us>Tue Oct 24 17:22:09 2017 -0700
committerLuca Prete <luca@opennetworking.org>Tue Oct 24 17:26:16 2017 -0700
tree4ec429f8f8257811184cb40e5058fda48d0d6675
parent4f7a4ce8892678687b1eef573b4bc60013831639 [diff]
increasing timeout for compute nodes provisioning

Change-Id: I21746a535b8c1cfc999e572ae02000c7828e7daf
(cherry picked from commit 49c818ccbce7b74d372a9a7a0ee16ad9b1cb66d5)
1 file changed
tree: 4ec429f8f8257811184cb40e5058fda48d0d6675
  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: