Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 37e7aa3138571fae458ee6bae5d9c19432bea159
commit37e7aa3138571fae458ee6bae5d9c19432bea159[log] [tgz]
authorZack Williams <zdw@opennetworking.org>Sun Dec 10 21:07:12 2017 -0700
committerZack Williams <zdw@opennetworking.org>Thu Feb 15 01:03:48 2018 +0000
tree3e4d86dd7df9fa6f1f90607feb5321b256bb194b
parentdc15ebe33a94e2daa1525dfb9363a0329a0b16c0 [diff]
[CORD-1650]
Use p-i/roles/interface-config to bring up network
Documentation updates

[CORD-1478]
Don't use Vagrant provisioner to configure network on the head node

Change-Id: I0564b706fdb18a91b5c0a3682cbac14a1cb919ba
10 files changed
tree: 3e4d86dd7df9fa6f1f90607feb5321b256bb194b
  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: