Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 05be6a6e6c14e709367ddc12fc2431dbbd0d1a3e
commit05be6a6e6c14e709367ddc12fc2431dbbd0d1a3e[log] [tgz]
authorZack Williams <zdw@opennetworking.org>Fri Jan 19 07:51:33 2018 -0700
committerZack Williams <zdw@opennetworking.org>Fri Jan 19 07:51:33 2018 -0700
treeeb8f924686ba7d6fcbff450bc65c2358084dfe2b
parentd552444a981d9aa07a7a8ecb22548566eeb39c37 [diff]
[CORD-2559]
Remove duplicate venb-synchronizer from docker_images.yml

Change-Id: I963d2009b1fd5f7df6d2f641dfbe9dde6a6534c9
1 file changed
tree: eb8f924686ba7d6fcbff450bc65c2358084dfe2b
  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: