Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 323d35e613ba9610c75f4125741f07bfcef3e449
commit323d35e613ba9610c75f4125741f07bfcef3e449[log] [tgz]
authorAndy Bavier <andy@onlab.us>Thu Sep 14 07:38:50 2017 -0700
committerLuca Prete <luca@opennetworking.org>Thu Sep 14 08:05:22 2017 -0700
tree3daeb2d42ce596c794c747ee7d4935bfe400cc4b
parentd3a527ca8d94b23ebc9037fbf312a88dbcd9e279 [diff]
Fix counting nodes in 'Deployed' state

Change-Id: I739387426695886b5ede0b865ea749c8c8fc4458
(cherry picked from commit 4c3e4159bcc6d7929486684612fbdd574dac84da)
1 file changed
tree: 3daeb2d42ce596c794c747ee7d4935bfe400cc4b
  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: