Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 21e4fe4aa5591b9581769cfeaa052749446a41ce
commit21e4fe4aa5591b9581769cfeaa052749446a41ce[log] [tgz]
authorAndy Bavier <andy@onlab.us>Fri Sep 29 10:27:12 2017 -0700
committerAndy Bavier <andy@opennetworking.org>Sat Sep 30 10:58:06 2017 -0700
tree2c21ccc424f7bf09b20ac7582b0d0c3d6d8195f9
parentf0a6eaef6328621987b7649d6f679f0d2be183fd [diff]
CORD-1879 Remove unused Elastic Stack from the build

Change-Id: I596b8379fbba079e60387b3cce2a1a4044514c83
(cherry picked from commit 870892108291b0e66945b5b431580173aaf4e134)
2 files changed
tree: 2c21ccc424f7bf09b20ac7582b0d0c3d6d8195f9
  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: