Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 02bdb96fcf0d1aaffd68f98910ca4d2edb50a9cf
commit02bdb96fcf0d1aaffd68f98910ca4d2edb50a9cf[log] [tgz]
authorLarry Peterson <llp@opennetworking.org>Tue Sep 19 07:11:26 2017 -0700
committerLarry Peterson <llp@opennetworking.org>Tue Sep 19 07:11:26 2017 -0700
treef924cf4fcb6660c0ead47f36e6a15b8c886d84de
parentec723ad8b6b77cf1caa5aaaef67410f5c1670350 [diff]
fixed links in guide

Change-Id: I893bd890f0b4d111f55fab38db6b0f6b19229fc0
4 files changed
tree: f924cf4fcb6660c0ead47f36e6a15b8c886d84de
  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: