Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 4c3e4159bcc6d7929486684612fbdd574dac84da
commit4c3e4159bcc6d7929486684612fbdd574dac84da[log] [tgz]
authorAndy Bavier <andy@onlab.us>Thu Sep 14 07:38:50 2017 -0700
committerAndy Bavier <andy@onlab.us>Thu Sep 14 07:38:50 2017 -0700
tree33c32f66d0b6559f12c8411a11cf1622893ada2b
parent6d1d6b1c9f1e2486247261f527d03a1ab3e58963 [diff]
Fix counting nodes in 'Deployed' state

Change-Id: I739387426695886b5ede0b865ea749c8c8fc4458
1 file changed
tree: 33c32f66d0b6559f12c8411a11cf1622893ada2b
  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: