Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 12d029c1270df8b5a4578a1e372885eae49c9ea8
commit12d029c1270df8b5a4578a1e372885eae49c9ea8[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Tue Oct 31 14:11:39 2017 -0700
committerZack Williams <zdw@opennetworking.org>Wed Nov 15 21:09:19 2017 +0000
tree8f94b2bc02d638d32a4beee923a6775cc4011554
parent1daf5ab014ddd51184981734205b708a3e336c37 [diff]
[CORD-1564]
Support multi-parent image builds

[CORD-2025]
Catch docker ConnectionError

[CORD-2257]
Catch 404 errors when image not available from DockerHub

Change-Id: I6b54bd9ecd16902d036e1da08a1f5dcc68da3c8d
(cherry picked from commit 053a80770c8e070e4653f600c1926757573efbdd)
1 file changed
tree: 8f94b2bc02d638d32a4beee923a6775cc4011554
  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: