Gitiles
Code Review Sign In
gerrit.opencord.org / cord / f02ad9c06cdf2eee75f330daafebf4993ad07e1a
commitf02ad9c06cdf2eee75f330daafebf4993ad07e1a[log] [tgz]
authorMatteo Scandolo <matteo.scandolo@gmail.com>Mon Sep 25 10:21:13 2017 -0700
committerMatteo Scandolo <matteo.scandolo@gmail.com>Mon Sep 25 10:37:27 2017 -0700
tree9be1e7eb24cb5ca541c54bba5f771d5f4ab7d666
parent63d3a68185e09162683313fff49ff8a953bebd31 [diff]
Fixing Swagger docs

Change-Id: Iebac8f1cd4491a5515d810683e371e76642fad06
1 file changed
tree: 9be1e7eb24cb5ca541c54bba5f771d5f4ab7d666
  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: