Gitiles
Code Review Sign In
gerrit.opencord.org / cord / cb27b1ce4d936685e362b9a1596b09bb77b853d2
commitcb27b1ce4d936685e362b9a1596b09bb77b853d2[log] [tgz]
authorYou Wang <you@opennetworking.org>Wed Sep 13 13:44:23 2017 -0700
committerYou Wang <you@opennetworking.org>Wed Sep 13 13:44:23 2017 -0700
tree1f1410339630bdadea6ba01c14a08ca11a3b5164
parent4b0458a5a14ab0a46f6c5bf34d3983fad0d443ff [diff]
Fix quotation mark in pod installation doc

Change-Id: I7381c10a2657d40690ce998656c1707c7b53d7ed
1 file changed
tree: 1f1410339630bdadea6ba01c14a08ca11a3b5164
  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: