Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 535769e1aafac8561c020974324f15d5a06c9efb
commit535769e1aafac8561c020974324f15d5a06c9efb[log] [tgz]
authorLuca Prete <luca@onlab.us>Fri Sep 01 16:16:35 2017 -0700
committerLuca Prete <luca@onlab.us>Fri Sep 01 16:16:35 2017 -0700
treedce8759447662d12788a5702f3894863ef481ee0
parente2d51fda7f9d6b706daef9d430e18fd8feee5dec [diff]
Fixing new build system Jenkinsfile

Change-Id: I0a35392a8ffcd0cf3033b3c6ec516a05e5c4b19d
1 file changed
tree: dce8759447662d12788a5702f3894863ef481ee0
  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: