Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 5f40f9c9019446732f5bb981874c37c23abca2a8
commit5f40f9c9019446732f5bb981874c37c23abca2a8[log] [tgz]
authorLuca Prete <luca@onlab.us>Fri Sep 29 09:03:02 2017 -0700
committerLuca Prete <luca@onlab.us>Fri Sep 29 09:03:02 2017 -0700
tree38061b576e5fb8076ceb730f09f02425bbaa0d7d
parent5875fc45cfeb458f5f66488b2250a06d585d0cf8 [diff]
Fixing docs Makefile

Change-Id: If2175940fa23e324fd5c330cba012c383ad9abe4
2 files changed
tree: 38061b576e5fb8076ceb730f09f02425bbaa0d7d
  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: