Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 299098d19d2546d553d9ee8725f8cd9d9f5aee58
commit299098d19d2546d553d9ee8725f8cd9d9f5aee58[log] [tgz]
authorZack Williams <zdw@opennetworking.org>Thu Apr 19 22:15:52 2018 -0700
committerZack Williams <zdw@opennetworking.org>Thu Apr 19 22:15:52 2018 -0700
tree51061b18b8c0ce51a59830627e78777e06c74e89
parentd082a601fc64f91f799a1a169e48d5328a8b9546 [diff]
[CORD-2950] Fix ansible 2.5.1 breakage by using union operator instead of iterating over docker image lists

Change-Id: I7b651d881870b7f0daff02d28f1b1213073aa51d
2 files changed
tree: 51061b18b8c0ce51a59830627e78777e06c74e89
  1. .gitignore
  2. .gitmodules
  3. Jenkinsfile
  4. Jenkinsfile.ciab
  5. Jenkinsfile.imagebuilder
  6. Jenkinsfile.newBuildSystem
  7. LICENSE.txt
  8. Makefile
  9. README.md
  10. ansible.cfg
  11. ansible/
  12. docker_images.yml
  13. docs/
  14. genconfig/
  15. image_logs/
  16. logs/
  17. milestones/
  18. podconfig/
  19. scenarios/
  20. scripts/
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: