Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 144027fe2249450b7a95b2171e0dcf8540703789
commit144027fe2249450b7a95b2171e0dcf8540703789[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Mon Sep 25 18:01:47 2017 -0700
committerZack Williams <zdw@cs.arizona.edu>Wed Sep 27 14:17:23 2017 -0700
tree53bcbcc1261c243cb31a5f1b04592fdcb0d7e4db
parent6924bed9c023319459fcee71d9db7afae98cb02c [diff]
[CORD-1924]
Documentation followup patch

Change-Id: I4387182ca58fa3fbb6ebda12f94f46e1a847e68f
22 files changed
tree: 53bcbcc1261c243cb31a5f1b04592fdcb0d7e4db
  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: