Gitiles
Code Review Sign In
gerrit.opencord.org / cord / ade809643ec73f554d8d81043c11586cdfa2f6d3
commitade809643ec73f554d8d81043c11586cdfa2f6d3[log] [tgz]
authorZack Williams <zdw@opennetworking.org>Wed Nov 29 16:22:13 2017 -0700
committerZack Williams <zdw@opennetworking.org>Thu Nov 30 17:41:38 2017 +0000
tree9148e9b5637dbe7d86171522c35784655d75562f
parenta7fd587285c670f29c5bd20b2fbaa79551346e1b [diff]
[CORD-2321]
Have `make clean-all` clean local scenario
Add/fix other local scenario targets

Change-Id: I4c2663c89ae5634c519126d713efc079f8c9c1a0
(cherry picked from commit e53c9cae99abdd0b84644a2827763ba94ac3cb1b)
1 file changed
tree: 9148e9b5637dbe7d86171522c35784655d75562f
  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: