Gitiles
Code Review Sign In
gerrit.opencord.org / cord / c1bc2e22462f543eb2e48ea62d4557cbdd70090e
commitc1bc2e22462f543eb2e48ea62d4557cbdd70090e[log] [tgz]
authorAndy Bavier <andy@onlab.us>Fri Sep 15 07:40:31 2017 -0700
committerAndy Bavier <andy@opennetworking.org>Fri Sep 15 09:16:19 2017 -0700
tree2194f9e7f51339b94f13a36d48a74397f004790e
parent7821e64a4ed2c55fd9974a6f695319c67dcaf1ad [diff]
CORD-1905 Wait for head node to become available

Change-Id: If9a531d67f4dcb1071c523aafc325875ba8bfbc8
(cherry picked from commit f8e46cdc110c34d418ea6a6867037d37f0822e63)
1 file changed
tree: 2194f9e7f51339b94f13a36d48a74397f004790e
  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: