Gitiles
Code Review Sign In
gerrit.opencord.org / cord / a5fcefda2e0383bff199b34f30f94b811cb6f749
commita5fcefda2e0383bff199b34f30f94b811cb6f749[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Thu Jul 27 22:06:33 2017 -0700
committerZack Williams <zdw@cs.arizona.edu>Tue Aug 01 22:36:38 2017 -0700
treec4b21447170576e31b636285b2ce5053b80bb011
parentc8ee6460fa902f3b6e4184e58ff707d082aac7f0 [diff]
[CORD-1608]
Fix DNS and ansible timeout issues when building docker images

Change-Id: I549387d458c280ac769e9c3a06a5e035457c0815
8 files changed
tree: c4b21447170576e31b636285b2ce5053b80bb011
  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: