Gitiles
Code Review Sign In
gerrit.opencord.org / cord / d589e08290d534ef539d3d51df9483a1e3d145ab
commitd589e08290d534ef539d3d51df9483a1e3d145ab[log] [tgz]
authorZack Williams <zdw@opennetworking.org>Thu Mar 01 17:21:56 2018 -0700
committerZack Williams <zdw@opennetworking.org>Fri Mar 02 02:02:32 2018 -0700
treea4c58fab562ca85e653d3a88d3a82edc5639835f
parente916a17ab7d1ce48a3db52dd0e2a9dc6acac21a4 [diff]
[CORD-2795]
Fix kubespray inventory to use new location

[CORD-2797]
Pin kubespray release version

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