Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 4dc6647b4a4cb1e7f515a02967fd9e4955c616ff
commit4dc6647b4a4cb1e7f515a02967fd9e4955c616ff[log] [tgz]
authorAndy Bavier <andy@onlab.us>Tue Jul 18 17:13:24 2017 -0700
committerAndy Bavier <andy@onlab.us>Tue Jul 18 17:24:06 2017 -0700
tree9680fd8b6534b1dccac1202c557ae13019838f69
parentb0b5a14e002195c45fc7b8e71b53c0c0d5698844 [diff]
Add target to set up local scenario for GUI access, Ubuntu only

Change-Id: I2af0e6b307ae8dd7ac62454f7649a924fc50d03e
1 file changed
tree: 9680fd8b6534b1dccac1202c557ae13019838f69
  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: