Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 0a7ef163c24437e1b7a02d406ca35b8213270ede
commit0a7ef163c24437e1b7a02d406ca35b8213270ede[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Tue Jul 18 18:15:26 2017 -0700
committerZack Williams <zdw@cs.arizona.edu>Wed Jul 19 21:49:10 2017 -0700
tree4762e79e7cf1ecf0f96fc442a084e17b66c4db49
parent4dc6647b4a4cb1e7f515a02967fd9e4955c616ff [diff]
[CORD-1590]
`single` scenario, which is mock w/synchronizers

Change-Id: Ia2e40c2a105464aad93230f689cc295db835496f
11 files changed
tree: 4762e79e7cf1ecf0f96fc442a084e17b66c4db49
  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: