Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 700f26614f86dc3f8ad076ad498336f4a64a2fbd
commit700f26614f86dc3f8ad076ad498336f4a64a2fbd[log] [tgz]
authorAndy Bavier <andy@onlab.us>Tue Sep 19 13:52:30 2017 -0700
committerAndy Bavier <andy@onlab.us>Wed Sep 20 08:44:18 2017 -0700
treef2fe39783a43013708723fa7d7555a64689f4af9
parent02bdb96fcf0d1aaffd68f98910ca4d2edb50a9cf [diff]
CORD-1911 Ensure that switches always get same IP address from MAAS DHCP

Change-Id: Ia2486ae44c0addeb96691b01e6e116e06680e331
1 file changed
tree: f2fe39783a43013708723fa7d7555a64689f4af9
  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: