Gitiles
Code Review Sign In
gerrit.opencord.org / cord / a10094b2a1e13d442634540434c1ed11e35f2ee7
commita10094b2a1e13d442634540434c1ed11e35f2ee7[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Sun Jul 23 13:54:12 2017 -0700
committerZack Williams <zdw@cs.arizona.edu>Mon Jul 24 21:48:27 2017 -0700
tree890ad6b108f16bf8d82bf5bdb976ac325f58810e
parent0a7ef163c24437e1b7a02d406ca35b8213270ede [diff]
Add `collect-diag` makefile target, documentation

Change-Id: I581db8b52bc2b9a4b7e4c850f9b432664fbc6c92
2 files changed
tree: 890ad6b108f16bf8d82bf5bdb976ac325f58810e
  1. .gitignore
  2. .gitmodules
  3. Jenkinsfile
  4. Jenkinsfile.ciab
  5. Jenkinsfile.imagebuilder
  6. LICENSE.txt
  7. Makefile
  8. README.md
  9. Vagrantfile
  10. ansible.cfg
  11. ansible/
  12. build.gradle
  13. buildSrc/
  14. config/
  15. docker_images.yml
  16. docs/
  17. elk-logger/
  18. genconfig/
  19. gradle.properties
  20. gradle/
  21. gradlew
  22. gradlew.bat
  23. image_logs/
  24. logs/
  25. milestones/
  26. podconfig/
  27. scenarios/
  28. scripts/
  29. settings.gradle
  30. 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: