Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 94b7b749245a30a4c6e0c85e11e62d61f5ee366e
commit94b7b749245a30a4c6e0c85e11e62d61f5ee366e[log] [tgz]
authorKailash Khalasi <kailash@onlab.us>Wed Dec 06 15:40:53 2017 -0800
committerAndy Bavier <andy@opennetworking.org>Thu Dec 07 02:52:01 2017 +0000
treef7273ce18c53464a1061b93a9e2d6453ac342fe3
parenta2b8541bd4d2fbc76b74305995a2b3b937ef2baf [diff]
updating 'pod-test' documentation to specify which profile is supported

Change-Id: I6af2272c99f984b3728ca34b4d3ddd118f17eac7
(cherry picked from commit dafc17ceffa052ce88ca40de63de4f17a34f52d5)
1 file changed
tree: f7273ce18c53464a1061b93a9e2d6453ac342fe3
  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: