Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 05c420b351850af236d3dda0e46a06f181521c22
commit05c420b351850af236d3dda0e46a06f181521c22[log] [tgz]
authorJianHao <itriA50355@itri.org.tw>Sun Sep 24 00:53:45 2017 +0800
committerPingping Lin <pingping@onlab.us>Mon Sep 25 18:18:23 2017 -0700
tree14b772fb789202963d902d8d3d0242a84bbac85e
parent8fa216c2aa8c0dbc393a14fbaed89181733901d6 [diff]
[MCORD-194] create mcord ciab config for 4.0 version.

Change-Id: Ib9633da6c4ddf847d78958f47c0fc180e89b18b5
(cherry picked from commit b4fe3a8029cb137e2e15864bc7d2dd853508bb51)
1 file changed
tree: 14b772fb789202963d902d8d3d0242a84bbac85e
  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: