Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 4775df202daf25ac3c0efa140b8d6bd3c63c5608
commit4775df202daf25ac3c0efa140b8d6bd3c63c5608[log] [tgz]
authorAndy Bavier <andy@onlab.us>Fri Jan 05 10:52:30 2018 -0700
committerAndy Bavier <andy@onlab.us>Fri Jan 05 14:50:19 2018 -0700
treeb4a633cf58e27de60fd55e96eae2e2c8978c88b8
parent8b1bd3658cd0312aa4770fbb9412909b2d6eaef5 [diff]
CORD-2473 Allow PODCONFIG or PODCONFIG_PATH

Change-Id: Ie62f2c2936fe95d02706364e80d2aa25724b2003
3 files changed
tree: b4a633cf58e27de60fd55e96eae2e2c8978c88b8
  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: