Gitiles
Code Review Sign In
gerrit.opencord.org / cord / bd37a06049e5f0c030d134f52e553f46cd2aad99
commitbd37a06049e5f0c030d134f52e553f46cd2aad99[log] [tgz]
authorScott Baker <smbaker@gmail.com>Fri Sep 08 13:51:55 2017 -0700
committerScott Baker <scottb@onlab.us>Mon Sep 11 15:37:57 2017 -0700
tree45319057b71dca3bfd9ce4043bf10465a8501254
parent9c6fef5bb100770e28a15d525be5d1b723f01de5 [diff]
CORD-1762 add addressmanager synchronizer image to new build system

Change-Id: Icb7a072ea3aa4d3c57c1ebaba3725341ea8daa3b
(cherry picked from commit 30333863ae0a33c1322b18a7f5f07b0f5e94e523)
4 files changed
tree: 45319057b71dca3bfd9ce4043bf10465a8501254
  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: