Gitiles
Code Review Sign In
gerrit.opencord.org / cord / c648005df5dcb29f703da2f4430c498a08cb25a0
commitc648005df5dcb29f703da2f4430c498a08cb25a0[log] [tgz]
authorgopinath <gopinath@opennetworking.org>Wed Sep 06 09:57:52 2017 -0700
committerLuca Prete <luca@opennetworking.org>Mon Sep 11 14:14:44 2017 -0700
tree1a5d6b7380c4f42a873d581acbd6c0bf54ed3dcb
parentcdab5659c0e3360be29cfac65fec950a89f82ca9 [diff]
Forcing Vagrant destroy during clean

Change-Id: I2248c389831254e00ff5615ef48a016c961177fe
(cherry picked from commit 1c7ebef6ab6a9a1c354bf083b6ffe53a54a36a8e)
1 file changed
tree: 1a5d6b7380c4f42a873d581acbd6c0bf54ed3dcb
  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: