Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 63d3a68185e09162683313fff49ff8a953bebd31
commit63d3a68185e09162683313fff49ff8a953bebd31[log] [tgz]
authorAndy Bavier <andy@onlab.us>Thu Sep 21 17:52:19 2017 -0700
committerAndy Bavier <andy@onlab.us>Thu Sep 21 18:02:40 2017 -0700
treeb7d702e525187e6ff3c12945835758425322fa84
parent81a63d2c8e0a3d2d7613b0f4712419a98cdd4db7 [diff]
CORD-1921 Fix formatting of commands

Change-Id: Id47a896f4c8993bcb51b09918578c82bd2fbc575
1 file changed
tree: b7d702e525187e6ff3c12945835758425322fa84
  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: