Gitiles
Code Review Sign In
gerrit.opencord.org / cord / fa32eb4a18447f864e92e9746b8c08009421cf16
commitfa32eb4a18447f864e92e9746b8c08009421cf16[log] [tgz]
authorMatteo Scandolo <matteo.scandolo@gmail.com>Thu Sep 07 13:57:26 2017 -0700
committerMatteo Scandolo <teo@opennetworking.org>Fri Sep 08 13:18:28 2017 -0700
tree3ab52ded11a8e7100a44b59919936a48f137bb51
parent1e6cf6e6310cc50b953affd1acecf61d081fbb52 [diff]
[CORD-1796] Generating swagger docs

Change-Id: Ib99abd91e0d5eee4ddce5db6f675eeb2c919ee8b
(cherry picked from commit f8cd29f73a0cdaf234d9b23b0a73e5cb917ffdc5)
2 files changed
tree: 3ab52ded11a8e7100a44b59919936a48f137bb51
  1. .gitignore
  2. .gitmodules
  3. Jenkinsfile
  4. Jenkinsfile.ciab
  5. Jenkinsfile.imagebuilder
  6. LICENSE.txt
  7. Makefile
  8. README.md
  9. Vagrantfile
  10. ansible.cfg
  11. ansible/
  12. build.gradle
  13. buildSrc/
  14. config/
  15. docker_images.yml
  16. docs/
  17. elk-logger/
  18. genconfig/
  19. gradle.properties
  20. gradle/
  21. gradlew
  22. gradlew.bat
  23. image_logs/
  24. logs/
  25. milestones/
  26. podconfig/
  27. scenarios/
  28. scripts/
  29. settings.gradle
  30. 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: