Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 674e01ba403f992af21af20d40d70c62c886c973
commit674e01ba403f992af21af20d40d70c62c886c973[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Wed Sep 27 16:07:48 2017 -0700
committerZack Williams <zdw@cs.arizona.edu>Wed Oct 04 23:07:46 2017 -0700
tree3bafaf9df3d340c890aaa2271369f4720242ff40
parent93ae63806df9c71834d15e64e753e23ef1945dc7 [diff]
Fix heading names and links. Additions to troubleshooting docs.

Change-Id: If8f9097c22e54233676352890f3c5431af9ba098
10 files changed
tree: 3bafaf9df3d340c890aaa2271369f4720242ff40
  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: