Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 2b26e562705609f3e03d886414a0e864d76ed91e
commit2b26e562705609f3e03d886414a0e864d76ed91e[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Tue Sep 05 16:14:04 2017 -0700
committerZack Williams <zdw@cs.arizona.edu>Tue Sep 05 16:14:04 2017 -0700
treea3fa87c975694def7e772750a44581aae3bd71cb
parent800abd71b2c39fed33ca470b4e2cac77d3828ec0 [diff]
[CORD-1866]
Support for password SSH auth

Change-Id: I8dced53e8685d8e21a18e807cb6e23bf2814b169
4 files changed
tree: a3fa87c975694def7e772750a44581aae3bd71cb
  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: