Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 39c9aa90a23c69682c67572ae96be09beecf57a7
commit39c9aa90a23c69682c67572ae96be09beecf57a7[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Tue Oct 17 08:35:00 2017 -0700
committerZack Williams <zdw@cs.arizona.edu>Tue Oct 17 09:07:29 2017 -0700
tree9f15a717f4b3038d318595f966344e02b7bfe794
parentf87ef6e2b12b1efb37af3a90f2181cf4f5056383 [diff]
[CORD-2094] v2
Make SSH config key gen and copy not reliant on vagrant

Change-Id: I2df8e06b080321ff79a246381e93710479582457
3 files changed
tree: 9f15a717f4b3038d318595f966344e02b7bfe794
  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: