Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 1b96a9571e6476efd841a8198635d6f673765870
commit1b96a9571e6476efd841a8198635d6f673765870[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Mon Jul 17 16:48:01 2017 -0700
committerZack Williams <zdw@cs.arizona.edu>Mon Sep 25 12:15:17 2017 -0700
tree1dad5e30b5eaeb09f5bee2ff22fd8394aee9eb4e
parentf02ad9c06cdf2eee75f330daafebf4993ad07e1a [diff]
[CORD-1569]
Autogenerate documentation of build system variables

Change-Id: I839f46d681e8f6954316f0ea4e9a79395501459f
26 files changed
tree: 1dad5e30b5eaeb09f5bee2ff22fd8394aee9eb4e
  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: