commit | 00165d9aa193bceef7764ba87a1ec5b2c5ba9a9e | [log] [tgz] |
---|---|---|
author | Luca Prete <luca@onlab.us> | Thu Oct 05 14:36:58 2017 -0700 |
committer | Luca Prete <luca@opennetworking.org> | Thu Oct 05 14:39:03 2017 -0700 |
tree | b2f0ee02c8c657966cfbf6f96b983725cabb17bf | |
parent | fe5f1a0720266ffd4d82fe06fe56c02529e73ed5 [diff] |
Fixing Jenkinsfile for CORD 3.0 Change-Id: I1ffbb62e9ef52b42724e84f618395f6a53e4fb9a (cherry picked from commit 3252640238f2a3052dbd4bd9ccf23f7fab1d60c0)
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: