Gitiles
Code Review Sign In
gerrit.opencord.org / cord / b5cde1d25b29f4a58f4627d88e4569744042d8c0
commitb5cde1d25b29f4a58f4627d88e4569744042d8c0[log] [tgz]
authorZack Williams <zdw@opennetworking.org>Mon Dec 04 16:57:04 2017 -0700
committerZack Williams <zdw@opennetworking.org>Tue Dec 05 08:03:39 2017 -0700
tree0950ce009e37717ee8d43b3bd5481b328e2bb7d4
parentfbc8b0f28ccf6ffa6f68ec77735a75307d901aef [diff]
[CORD-2341]
Update build variable glossary for 4.1 release

[CORD-2346]
Fix `make clean` for documentation

Change-Id: Ia4d5037ce2644f74f62c79ef90cf5d3243b27ffd
2 files changed
tree: 0950ce009e37717ee8d43b3bd5481b328e2bb7d4
  1. .gitignore
  2. .gitmodules
  3. Jenkinsfile.ciab
  4. Jenkinsfile.imagebuilder
  5. Jenkinsfile.newBuildSystem
  6. LICENSE.txt
  7. Makefile
  8. README.md
  9. ansible.cfg
  10. ansible/
  11. docker_images.yml
  12. docs/
  13. elk-logger/
  14. genconfig/
  15. image_logs/
  16. logs/
  17. milestones/
  18. podconfig/
  19. scenarios/
  20. scripts/
  21. 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: