Gitiles
Code Review Sign In
gerrit.opencord.org / cord / e4f82a92ece99b39ec435d8a85d027bf8a5eef5e
commite4f82a92ece99b39ec435d8a85d027bf8a5eef5e[log] [tgz]
authorMatteo Scandolo <matteo.scandolo@gmail.com>Wed Sep 13 13:54:44 2017 -0700
committerMatteo Scandolo <matteo.scandolo@gmail.com>Fri Sep 15 09:21:29 2017 -0700
tree7d2825bb134ededc68c6c67c8909a7362b89ab29
parentc1bc2e22462f543eb2e48ea62d4557cbdd70090e [diff]
[CORD-1795] Adding TOSCA docs

Change-Id: Iba892d4f0f9c232aea623a4266456380a9a98fae
3 files changed
tree: 7d2825bb134ededc68c6c67c8909a7362b89ab29
  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: