Gitiles
Code Review Sign In
gerrit.opencord.org / cord / fcbc54bacd0c86eebdfd19ac90c48f779048b7a5
commitfcbc54bacd0c86eebdfd19ac90c48f779048b7a5[log] [tgz]
authorLuca Prete <luca@onlab.us>Tue Sep 12 14:37:33 2017 -0700
committerLuca Prete <luca@onlab.us>Tue Sep 12 14:37:33 2017 -0700
treee91c7de1ab0ccc0f616117a6f92ff91943cf32f9
parent225d965e92f1e73add82d1ae222d00c069be4ce6 [diff]
Fixing jenkins file relative paths

Change-Id: I1a7574606b8cb73576727924ca9695b9912410cf
1 file changed
tree: e91c7de1ab0ccc0f616117a6f92ff91943cf32f9
  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: