Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 881ece853eb390abc1dea9e388e4d0b9ba0c51da
commit881ece853eb390abc1dea9e388e4d0b9ba0c51da[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Tue Sep 26 18:31:41 2017 -0700
committerZack Williams <zdw@cs.arizona.edu>Wed Sep 27 09:10:26 2017 -0700
tree75d9af869c6bd5ed6149334c435c4f446ec7816f
parent05c420b351850af236d3dda0e46a06f181521c22 [diff]
[CORD-1929]
Make cord-bootstrap.sh more idempotent

Change-Id: I5ddd949b5fda8249cff4ba9717b2c0c8cc2969be
(cherry picked from commit 6924bed9c023319459fcee71d9db7afae98cb02c)
1 file changed
tree: 75d9af869c6bd5ed6149334c435c4f446ec7816f
  1. .gitignore
  2. .gitmodules
  3. Jenkinsfile
  4. Jenkinsfile.ciab
  5. Jenkinsfile.imagebuilder
  6. Jenkinsfile.newBuildSystem
  7. LICENSE.txt
  8. Makefile
  9. README.md
  10. Vagrantfile
  11. ansible.cfg
  12. ansible/
  13. build.gradle
  14. buildSrc/
  15. config/
  16. docker_images.yml
  17. docs/
  18. elk-logger/
  19. genconfig/
  20. gradle.properties
  21. gradle/
  22. gradlew
  23. gradlew.bat
  24. image_logs/
  25. logs/
  26. milestones/
  27. podconfig/
  28. scenarios/
  29. scripts/
  30. settings.gradle
  31. 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: