Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 5e62544aa1042a9abf50226452aa5eeb612fdfb9
commit5e62544aa1042a9abf50226452aa5eeb612fdfb9[log] [tgz]
authorAndy Bavier <andy@onlab.us>Wed Nov 29 13:42:37 2017 -0700
committerPingping Lin <pingping@onlab.us>Wed Nov 29 23:15:41 2017 +0000
treeb8dd86a2ffb1437fb0e9f8a1e5ffa343ebce2c95
parent932aa4156360c9e0ee5cdfea3a3b03f759c9895f [diff]
CORD-2319 Change ng4t to ng40

Change-Id: Ib2dfc6461c812d206edbace8c85f3294ea4352fb
(cherry picked from commit 27ee4c824db90a1fdaedb71065cc3deeb7a23bce)
4 files changed
tree: b8dd86a2ffb1437fb0e9f8a1e5ffa343ebce2c95
  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: