Gitiles
Code Review Sign In
gerrit.opencord.org / cord / e78067511121fce7fbe9b40cce5e31f5f604d5e1
commite78067511121fce7fbe9b40cce5e31f5f604d5e1[log] [tgz]
authorAndy Bavier <andy@onlab.us>Mon Oct 02 10:44:16 2017 -0700
committerAndy Bavier <andy@opennetworking.org>Mon Oct 02 11:27:07 2017 -0700
tree68f7a25136136878488dbb57b9fbd772ca8197d5
parent870892108291b0e66945b5b431580173aaf4e134 [diff]
VTN does not configure nodes until switches are connected

Change-Id: I20ec07d41c22af288a64b940e8697df9590127e6
(cherry picked from commit 2e29a4c594e45424167aeda4b0a974a440ad413e)
1 file changed
tree: 68f7a25136136878488dbb57b9fbd772ca8197d5
  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: