Gitiles
Code Review Sign In
gerrit.opencord.org / cord / d3a527ca8d94b23ebc9037fbf312a88dbcd9e279
commitd3a527ca8d94b23ebc9037fbf312a88dbcd9e279[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Wed Sep 13 12:24:57 2017 -0700
committerZack Williams <zdw@cs.arizona.edu>Wed Sep 13 22:56:48 2017 -0700
treed6027c287eb865edddeaf40bb01b43294d847fa4
parent6683e0bd31dc7e1ac1efd56e586d92b389229931 [diff]
[CORD-1900]
Better implementation of podconfig file presence check

Change-Id: I90dc44c1d659896a7755f5d73652393b3032e6a5
1 file changed
tree: d6027c287eb865edddeaf40bb01b43294d847fa4
  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: