Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 093cded5ff1603f153258479dcd1c4b2c62a58e7
commit093cded5ff1603f153258479dcd1c4b2c62a58e7[log] [tgz]
authorScott Baker <smbaker@gmail.com>Thu Sep 14 09:33:56 2017 -0700
committerScott Baker <scottb@onlab.us>Fri Sep 15 08:22:32 2017 -0700
tree4641bd692716210cce8eea4823cc8eecbf97d51f
parentdcac43bad2864a81a900a8d489bc4c25d6f9af2e [diff]
CORD-1790 Add cord-in-a-box workflow

Change-Id: Ic3fa5e9d971e4c303aa7127c743ad457c34bde0c
(cherry picked from commit 015503e672ab1fa3541dfff9073315784a9e157d)
1 file changed
tree: 4641bd692716210cce8eea4823cc8eecbf97d51f
  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: