Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 969eaa957503b088e3e2fb26702837bba6363a1a
commit969eaa957503b088e3e2fb26702837bba6363a1a[log] [tgz]
authorZack Williams <zdw@opennetworking.org>Tue Dec 19 14:47:42 2017 -0700
committerZack Williams <zdw@opennetworking.org>Fri Dec 22 11:00:59 2017 -0700
tree89b0730792e5dc7dfb28823df412ff3ec0f93a0e
parent240795ccc3c6d3a57ad0ec1d2499917ea93115aa [diff]
[CORD-2221]
Move wiki "Troubleshooting a Build" documentation to guide

Change-Id: I99f8097c80e441d06925b3aa3f99589b1ebcf3b4
1 file changed
tree: 89b0730792e5dc7dfb28823df412ff3ec0f93a0e
  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: