Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 1e6cf6e6310cc50b953affd1acecf61d081fbb52
commit1e6cf6e6310cc50b953affd1acecf61d081fbb52[log] [tgz]
authorAndy Bavier <andy@onlab.us>Thu Sep 07 08:25:20 2017 -0700
committerAndy Bavier <andy@onlab.us>Thu Sep 07 12:35:35 2017 -0700
treef5e79adb5380ca1b1a651dd13e6b788f5a2ad56c
parent7d17b9e6a8ed7d58bedd2fce76eb6935f07b8d8c [diff]
CORD-1876 Use standard upstream vagrant-libvirt plugin

Change-Id: I56865b1e337e988130058222aab766e367fb66e2
2 files changed
tree: f5e79adb5380ca1b1a651dd13e6b788f5a2ad56c
  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: