Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 6fb9a3e137275bdce162ac4e02952f93015759f0
commit6fb9a3e137275bdce162ac4e02952f93015759f0[log] [tgz]
authorAndy Bavier <andy@onlab.us>Tue Oct 17 10:48:41 2017 -0700
committerAndy Bavier <andy@opennetworking.org>Tue Oct 17 10:54:31 2017 -0700
tree2f28d23882e06c012dea9bb5233cad85c2384666
parent39c9aa90a23c69682c67572ae96be09beecf57a7 [diff]
Target for running M-CORD base tests

Change-Id: I18856120780e599c33a26bbed82ab65b0351e234
(cherry picked from commit 1b17e6ac5380a543d03abf25a045849d86d64992)
1 file changed
tree: 2f28d23882e06c012dea9bb5233cad85c2384666
  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: