Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 49c818ccbce7b74d372a9a7a0ee16ad9b1cb66d5
commit49c818ccbce7b74d372a9a7a0ee16ad9b1cb66d5[log] [tgz]
authorLuca Prete <luca@onlab.us>Tue Oct 24 17:22:09 2017 -0700
committerLuca Prete <luca@onlab.us>Tue Oct 24 17:22:09 2017 -0700
tree90e9fdae551c0ca6e9f33e3da7a3e4adcdd1c114
parent1bd23c84d3f707612244f50ab40a142748d0d408 [diff]
increasing timeout for compute nodes provisioning

Change-Id: I21746a535b8c1cfc999e572ae02000c7828e7daf
1 file changed
tree: 90e9fdae551c0ca6e9f33e3da7a3e4adcdd1c114
  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: