Gitiles
Code Review Sign In
gerrit.opencord.org / cord / afaa530a5ee16b1e09d2096d4bbf7acc6cc6289a
commitafaa530a5ee16b1e09d2096d4bbf7acc6cc6289a[log] [tgz]
authorAndy Bavier <andy@onlab.us>Tue Aug 15 08:56:15 2017 -0700
committerAndy Bavier <andy@onlab.us>Mon Aug 21 09:39:03 2017 -0700
treefe8e05049876fac330f10e54e11f2732b408a49c
parent1c891c2a7696186301e7362759b2292fd2b0ca3a [diff]
CORD-1729 Support "localhost" as build node for full POD / CiaB

Change-Id: I406393b5594799f60eab83a2e3a1910f6974fc87
8 files changed
tree: fe8e05049876fac330f10e54e11f2732b408a49c
  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: