Gitiles
Code Review Sign In
gerrit.opencord.org / cord / c8ee6460fa902f3b6e4184e58ff707d082aac7f0
commitc8ee6460fa902f3b6e4184e58ff707d082aac7f0[log] [tgz]
authorLarry Peterson <llp@onlab.us>Wed Jul 26 21:36:27 2017 -0700
committerLarry Peterson <llp@onlab.us>Thu Jul 27 22:14:29 2017 -0700
tree26841c56b79c395ef0f085d00210ec7a128c2b67
parent66ceea49e55c1e796d961b23134f224c1503a4bb [diff]
expanded guide content

Change-Id: I7f0229023e493bf85876e5b5632ee7e611d5aa85
7 files changed
tree: 26841c56b79c395ef0f085d00210ec7a128c2b67
  1. .gitignore
  2. .gitmodules
  3. Jenkinsfile
  4. Jenkinsfile.ciab
  5. Jenkinsfile.imagebuilder
  6. LICENSE.txt
  7. Makefile
  8. README.md
  9. Vagrantfile
  10. ansible.cfg
  11. ansible/
  12. build.gradle
  13. buildSrc/
  14. config/
  15. docker_images.yml
  16. docs/
  17. elk-logger/
  18. genconfig/
  19. gradle.properties
  20. gradle/
  21. gradlew
  22. gradlew.bat
  23. image_logs/
  24. logs/
  25. milestones/
  26. podconfig/
  27. scenarios/
  28. scripts/
  29. settings.gradle
  30. 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: