Gitiles
Code Review Sign In
gerrit.opencord.org / cord / f8e46cdc110c34d418ea6a6867037d37f0822e63
commitf8e46cdc110c34d418ea6a6867037d37f0822e63[log] [tgz]
authorAndy Bavier <andy@onlab.us>Fri Sep 15 07:40:31 2017 -0700
committerAndy Bavier <andy@onlab.us>Fri Sep 15 07:40:31 2017 -0700
treeb59af77cac9e59d02404c72af85bf2f923b0fdf7
parent7849a9861ab7423f239e180e4da524d3078549b6 [diff]
CORD-1905 Wait for head node to become available

Change-Id: If9a531d67f4dcb1071c523aafc325875ba8bfbc8
1 file changed
tree: b59af77cac9e59d02404c72af85bf2f923b0fdf7
  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: