Gitiles
Code Review Sign In
gerrit.opencord.org / cord / c4a4051e56d0c0044574f80c6993121b0212b65e
commitc4a4051e56d0c0044574f80c6993121b0212b65e[log] [tgz]
authorAndy Bavier <andy@onlab.us>Thu Aug 10 07:06:25 2017 -0700
committerAndy Bavier <andy@onlab.us>Thu Aug 10 07:06:25 2017 -0700
tree486ad6eb1de5d1c8ae4b0ae6e0d4d539f31f4415
parent37efb3d2a7dbb591df7999b5ab4f645365fd1fe9 [diff]
Shebang in first line

Change-Id: Ica298516fa2f4af8fc0ace5d050bd8ab3fe5ac2b
6 files changed
tree: 486ad6eb1de5d1c8ae4b0ae6e0d4d539f31f4415
  1. .gitignore
  2. .gitmodules
  3. Jenkinsfile
  4. Jenkinsfile.ciab
  5. Jenkinsfile.imagebuilder
  6. LICENSE.txt
  7. Makefile
  8. README.md
  9. Vagrantfile
  10. ansible.cfg
  11. ansible/
  12. build.gradle
  13. buildSrc/
  14. config/
  15. docker_images.yml
  16. docs/
  17. elk-logger/
  18. genconfig/
  19. gradle.properties
  20. gradle/
  21. gradlew
  22. gradlew.bat
  23. image_logs/
  24. logs/
  25. milestones/
  26. podconfig/
  27. scenarios/
  28. scripts/
  29. settings.gradle
  30. 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: