Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 9081fcc8a4f7b5d2b933b4aea6088a6dc950cdfc
commit9081fcc8a4f7b5d2b933b4aea6088a6dc950cdfc[log] [tgz]
authorLuca Prete <luca@onlab.us>Tue Sep 12 14:37:33 2017 -0700
committerLuca Prete <luca@opennetworking.org>Tue Sep 12 14:38:52 2017 -0700
tree47e831ecc9b91b053847cddcf003ab7f96d1cc0b
parent7b4a1e87ccc16e182b0e65f6be1a11600435f225 [diff]
Fixing jenkins file relative paths

Change-Id: I1a7574606b8cb73576727924ca9695b9912410cf
(cherry picked from commit fcbc54bacd0c86eebdfd19ac90c48f779048b7a5)
1 file changed
tree: 47e831ecc9b91b053847cddcf003ab7f96d1cc0b
  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: