Gitiles
Code Review Sign In
gerrit.opencord.org / cord / fb724fcf96b83d91474c630815c9041246b5fdaf
commitfb724fcf96b83d91474c630815c9041246b5fdaf[log] [tgz]
authorAndy Bavier <andy@onlab.us>Tue Aug 22 07:37:51 2017 -0700
committerAndy Bavier <andy@onlab.us>Tue Aug 22 07:37:51 2017 -0700
tree08620e99ecb21503a766a41992fdb1131509b2e2
parent9f17f260bb0075cade48163164c5a8aa5c78a36c [diff]
Revert deploy_docker_registry change

Change-Id: Ide79b43f77e33ca3e4d8f86252ecba693ce4deb7
2 files changed
tree: 08620e99ecb21503a766a41992fdb1131509b2e2
  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: