Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 300b3d5c2c4476e56b2e176539fd49291c7cb044
commit300b3d5c2c4476e56b2e176539fd49291c7cb044[log] [tgz]
authorMatteo Scandolo <matteo.scandolo@gmail.com>Fri Sep 15 15:31:30 2017 -0700
committerLarry Peterson <llp@opennetworking.org>Mon Sep 18 16:53:42 2017 -0700
tree24a127b86e1e81dfc78086a1a6466e586598ca4c
parent5e0c8e0f23794b207de37ed4861015521bb224ea [diff]
Documenting mock and single scenario workflow

Change-Id: Ic2c2d6aee3c2485e7f3511e980d72b6abf435193
(cherry picked from commit 47055b38687ac577e6b4b0ed72cc7473093ad788)
3 files changed
tree: 24a127b86e1e81dfc78086a1a6466e586598ca4c
  1. .gitignore
  2. .gitmodules
  3. Jenkinsfile
  4. Jenkinsfile.ciab
  5. Jenkinsfile.imagebuilder
  6. Jenkinsfile.newBuildSystem
  7. LICENSE.txt
  8. Makefile
  9. README.md
  10. Vagrantfile
  11. ansible.cfg
  12. ansible/
  13. build.gradle
  14. buildSrc/
  15. config/
  16. docker_images.yml
  17. docs/
  18. elk-logger/
  19. genconfig/
  20. gradle.properties
  21. gradle/
  22. gradlew
  23. gradlew.bat
  24. image_logs/
  25. logs/
  26. milestones/
  27. podconfig/
  28. scenarios/
  29. scripts/
  30. settings.gradle
  31. 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: