Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 93ae63806df9c71834d15e64e753e23ef1945dc7
commit93ae63806df9c71834d15e64e753e23ef1945dc7[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Wed Oct 04 16:31:06 2017 -0700
committerZack Williams <zdw@cs.arizona.edu>Wed Oct 04 16:51:32 2017 -0700
tree379810cb7058af0ae30e7838b7dd5ed849d93ad1
parent804030bbfc6edde599875f5a716d173a56e0d51f [diff]
[CORD-2032]

Fix issue with clean-profile's deletion of cord_profile directory
breaking corddev VM

Change-Id: I0e74126b91ef9ce41be1ac1ee4d103f859d3356b
1 file changed
tree: 379810cb7058af0ae30e7838b7dd5ed849d93ad1
  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: