Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 819275bf899e8f582dd636537fc42b6cecbc963a
commit819275bf899e8f582dd636537fc42b6cecbc963a[log] [tgz]
authorJonathan Hart <jono@opennetworking.org>Tue Feb 13 13:34:11 2018 -0800
committerJonathan Hart <jono@opennetworking.org>Tue Feb 13 13:52:18 2018 -0800
tree6c0a600a78f22de135837295a95de46ef1f0082b
parenteb32621531be6a3028553fe2b5800a13f1f374ac [diff]
CORD-2718: Fixes to vrouter documentation.

* 'docker run' now doesn't allow -n; use --name instead
* bring down interface before using pipework
* notify there will be a warning
* show how to restart docker container

Change-Id: Icdbab7dce948bf8f3dfa6a7f3415784a959c7597
1 file changed
tree: 6c0a600a78f22de135837295a95de46ef1f0082b
  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. genconfig/
  14. image_logs/
  15. logs/
  16. milestones/
  17. podconfig/
  18. scenarios/
  19. scripts/
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: