Gitiles
Code Review Sign In
gerrit.opencord.org / cord / b0b5a14e002195c45fc7b8e71b53c0c0d5698844
commitb0b5a14e002195c45fc7b8e71b53c0c0d5698844[log] [tgz]
authorAndy Bavier <andy@onlab.us>Mon Jul 17 17:32:55 2017 -0700
committerAndy Bavier <andy@opennetworking.org>Tue Jul 18 14:47:03 2017 -0700
tree025b10c7ea73f307a23c7c1490cc4560508919ac
parent2f56eee1687401579768c1222c01dda1426444db [diff]
CORD-1563 Clean up Vagrantfile for CiaB

Change-Id: Ida1704eb1c5c7c695312c1e16ad0d7593251aa6c
5 files changed
tree: 025b10c7ea73f307a23c7c1490cc4560508919ac
  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: