Gitiles
Code Review Sign In
gerrit.opencord.org / cord / b364dceb75b0724717b8e4ff684aad093fdb04ea
commitb364dceb75b0724717b8e4ff684aad093fdb04ea[log] [tgz]
authorYou Wang <you@opennetworking.org>Mon Sep 11 13:46:43 2017 -0700
committerLuca Prete <luca@opennetworking.org>Mon Sep 11 14:43:35 2017 -0700
tree296c31c093fe1db83157e4c8159982a419d985e4
parentcebbd3187ae3c9523bc68c4a9f1ed524c6d224f0 [diff]
Fix Jenkins verifications for compute-node provisioning

Change-Id: Iaedd80577fd3607da9df0b00259986dba1a3cfa5
(cherry picked from commit 4e0c2ede8552a7fcbf0ceecd98f0cc9998d7919f)
1 file changed
tree: 296c31c093fe1db83157e4c8159982a419d985e4
  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: