Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 602748e3c686ae4fb415b1b4fab84891f49b015e
commit602748e3c686ae4fb415b1b4fab84891f49b015e[log] [tgz]
authorZack Williams <zdw@opennetworking.org>Thu Dec 14 23:08:50 2017 -0700
committerZack Williams <zdw@opennetworking.org>Sat Dec 16 16:42:00 2017 +0000
tree3596269d84be56c45aad8c42ccea9cf2286fca1c
parentc90bce779f419ddb1b85e761526f5bce06fdf6a4 [diff]
[CORD-2434]
Remove build_tag from images that aren't labeled correctly

[CORD-2265]
Require >= v2 docker python module

Change-Id: I81a6665295f1152f56a0500af0d5e2a6a581232a
1 file changed
tree: 3596269d84be56c45aad8c42ccea9cf2286fca1c
  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: