Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 1c7ebef6ab6a9a1c354bf083b6ffe53a54a36a8e
commit1c7ebef6ab6a9a1c354bf083b6ffe53a54a36a8e[log] [tgz]
authorgopinath <gopinath@opennetworking.org>Wed Sep 06 09:57:52 2017 -0700
committergopinath <gopinath@opennetworking.org>Wed Sep 06 09:57:52 2017 -0700
tree13f64d290dc02c19f3e0270b0cf1fa857abb4db3
parentfb96e927ced8acb86fdafce40fa0b54acebd394b [diff]
Forcing Vagrant destroy during clean

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