Gitiles
Code Review Sign In
gerrit.opencord.org / cord / f0a6eaef6328621987b7649d6f679f0d2be183fd
commitf0a6eaef6328621987b7649d6f679f0d2be183fd[log] [tgz]
authorYou Wang <you@opennetworking.org>Fri Sep 29 13:36:31 2017 -0700
committerAndy Bavier <andy@opennetworking.org>Fri Sep 29 14:17:12 2017 -0700
tree2987deb2c9d2a4e64bb69181139e577e6a055342
parenta67aaa1e45502449ea30c0285159437b79f6edc1 [diff]
Documentation update for POD configurations

Change-Id: I0a2b0e8aaf32289e940cd91e48bd2a7bdb32b846
(cherry picked from commit f9f91d36723a2b3f5d8f24795aebe1ffcd87d7d4)
1 file changed
tree: 2987deb2c9d2a4e64bb69181139e577e6a055342
  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: