Gitiles
Code Review Sign In
gerrit.opencord.org / cord / ba3e246c4ae4952ab6ac474f8a4f747778f2b1c1
commitba3e246c4ae4952ab6ac474f8a4f747778f2b1c1[log] [tgz]
authorZack Williams <zdw@opennetworking.org>Fri Jan 19 11:52:31 2018 -0700
committerZack Williams <zdw@opennetworking.org>Mon Jan 22 14:54:05 2018 +0000
treec9ea2fdcd9e1785d6ef1f99a396574f5deaf1b58
parent04a7d58a5e59575e215186b67bd01b9b28a8aac9 [diff]
[CORD-2560]
Let the R-CORD `pod-test` run on preppedpod

Change-Id: If9d1d32470384d1a7d3edc4b4e05a4dbd61de38c
5 files changed
tree: c9ea2fdcd9e1785d6ef1f99a396574f5deaf1b58
  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. elk-logger/
  14. genconfig/
  15. image_logs/
  16. logs/
  17. milestones/
  18. podconfig/
  19. scenarios/
  20. scripts/
  21. 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: