Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 2d04b0da060037d2244c98776e5117fc9e6f8d53
commit2d04b0da060037d2244c98776e5117fc9e6f8d53[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Mon Sep 25 14:19:55 2017 -0700
committerZack Williams <zdw@cs.arizona.edu>Mon Sep 25 14:19:55 2017 -0700
treed413f1aa7d4f4cb74d955e4a70aad49d5d523dfe
parent1b96a9571e6476efd841a8198635d6f673765870 [diff]
Use bash as the shell when building docs for pushd/popd

Change-Id: I4485959f0d451ea23a260d9c18bd6c79040c2e46
1 file changed
tree: d413f1aa7d4f4cb74d955e4a70aad49d5d523dfe
  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: