Gitiles
Code Review Sign In
gerrit.opencord.org / cord / c0ad92df8eb47ce3e57b41de3d61022c0a9acb01
commitc0ad92df8eb47ce3e57b41de3d61022c0a9acb01[log] [tgz]
authorMatteo Scandolo <teo@opennetworking.org>Tue Nov 28 16:47:44 2017 -0800
committerMatteo Scandolo <teo@opennetworking.org>Wed Nov 29 04:08:36 2017 +0000
tree6a7141edda277abc57c0eeffbf44dd17f0c4dd06
parent9b089a6493441c768c725d0b63a08215de748b2e [diff]
[CORD-2310] Getting the local scenario to work

Change-Id: Ifeb58af51efab684cc8313d1476b5860bfc5d1ff
(cherry picked from commit 40f641e3b703854069ecf835bb17be60db1e27ba)
1 file changed
tree: 6a7141edda277abc57c0eeffbf44dd17f0c4dd06
  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: