Gitiles
Code Review Sign In
gerrit.opencord.org / cord / fb96e927ced8acb86fdafce40fa0b54acebd394b
commitfb96e927ced8acb86fdafce40fa0b54acebd394b[log] [tgz]
authorLuca Prete <luca@onlab.us>Tue Sep 05 16:35:12 2017 -0700
committerLuca Prete <luca@opennetworking.org>Tue Sep 05 16:35:32 2017 -0700
tree8c9d93476d85aaebadc5d3ac0c1bbfe2d8f1014c
parent2b26e562705609f3e03d886414a0e864d76ed91e [diff]
Adding vagrant provider to the new build jenkins file

Change-Id: Ia82a4516b92ef106a55e475f61df3f7da13cbd78
1 file changed
tree: 8c9d93476d85aaebadc5d3ac0c1bbfe2d8f1014c
  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: