Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 32295d5534f170180b1febbd1158167c53598273
commit32295d5534f170180b1febbd1158167c53598273[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Mon Aug 28 22:49:37 2017 -0700
committerZack Williams <zdw@cs.arizona.edu>Fri Sep 15 11:41:16 2017 -0700
treed0205b63c103da332cb1ecc51d5904e818f6f2a6
parente4f82a92ece99b39ec435d8a85d027bf8a5eef5e [diff]
[CORD-1811]
Create a separate Vagrant SSH config file, check if it's included in
~/.ssh/config, rather than overwriting.

Add clean-openstack target

Change-Id: Ifcaf78c40ccb77ad2231cb2013cfdf540ffba365
4 files changed
tree: d0205b63c103da332cb1ecc51d5904e818f6f2a6
  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: