Gitiles
Code Review Sign In
gerrit.opencord.org / cord / f8cd29f73a0cdaf234d9b23b0a73e5cb917ffdc5
commitf8cd29f73a0cdaf234d9b23b0a73e5cb917ffdc5[log] [tgz]
authorMatteo Scandolo <matteo.scandolo@gmail.com>Thu Sep 07 13:57:26 2017 -0700
committerMatteo Scandolo <teo@opennetworking.org>Thu Sep 07 17:30:57 2017 -0700
tree0f0859a563d0ab01c3197928e59edf55048101af
parent40a366314c5268f22780f798a23135b7141010a6 [diff]
[CORD-1796] Generating swagger docs

Change-Id: Ib99abd91e0d5eee4ddce5db6f675eeb2c919ee8b
2 files changed
tree: 0f0859a563d0ab01c3197928e59edf55048101af
  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: