Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 8e5413d87549238c6cfd9e651ef33878ee010dfc
commit8e5413d87549238c6cfd9e651ef33878ee010dfc[log] [tgz]
authorYou Wang <you@opennetworking.org>Fri Jan 19 15:27:07 2018 -0800
committerAndy Bavier <andy@opennetworking.org>Mon Feb 12 20:40:59 2018 +0000
treebd8c4e3838c8b37648b4804bda2b797c65717719
parentd47c2fee5d72bf9137f5d52855252cf05805af69 [diff]
Documentation fixes

Change-Id: I7524a11ab6c45d38c4fcc1af1009951caa173333
(cherry picked from commit 2793cd11070e1ad0ef9d2e17ed2ca8a71dacb27f)
2 files changed
tree: bd8c4e3838c8b37648b4804bda2b797c65717719
  1. .gitignore
  2. .gitmodules
  3. Jenkinsfile.ciab
  4. Jenkinsfile.imagebuilder
  5. Jenkinsfile.newBuildSystem
  6. LICENSE.txt
  7. Makefile
  8. README.md
  9. ansible.cfg
  10. ansible/
  11. docker_images.yml
  12. docs/
  13. elk-logger/
  14. genconfig/
  15. image_logs/
  16. logs/
  17. milestones/
  18. podconfig/
  19. scenarios/
  20. scripts/
  21. 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: