Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 8845ee5cd0dd2d5b61d5c1ef029c687ad2ba8a01
commit8845ee5cd0dd2d5b61d5c1ef029c687ad2ba8a01[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Wed Oct 04 23:13:26 2017 -0700
committerZack Williams <zdw@cs.arizona.edu>Thu Oct 05 12:45:31 2017 -0700
treef4c9e68cde6e61ec723189d6aa67857469083ca6
parent2c6ddf3145fb997a611c11e6fd0151fb56ca832a [diff]
[CORD-2035]
Fix mavenrepo and onos dependency issues

Change-Id: Ie65d5d61b1e7f1154a7cb936cf1e79bfcb64b9f1
3 files changed
tree: f4c9e68cde6e61ec723189d6aa67857469083ca6
  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: