Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 66ceea49e55c1e796d961b23134f224c1503a4bb
commit66ceea49e55c1e796d961b23134f224c1503a4bb[log] [tgz]
authorAndy Bavier <andy@onlab.us>Wed Jul 26 09:06:00 2017 -0700
committerAndy Bavier <andy@onlab.us>Wed Jul 26 12:00:25 2017 -0700
treeced03b461297a2872fbd3a052e0bc88d4e488fff
parenta10094b2a1e13d442634540434c1ed11e35f2ee7 [diff]
Add pull_docker_registry

Change-Id: I5a5f93d4a58c5e495994679155e9224e4da59847
1 file changed
tree: ced03b461297a2872fbd3a052e0bc88d4e488fff
  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: