commit | 416574f6e75487dbb6f3937ffb0fe7ea7081fb1c | [log] [tgz] |
---|---|---|
author | Luca Prete <luca@onlab.us> | Tue Oct 24 17:22:09 2017 -0700 |
committer | Luca Prete <luca@opennetworking.org> | Tue Oct 24 17:29:07 2017 -0700 |
tree | cb45610b62cdf9da712a653750a1bad7366652c4 | |
parent | a3a19c8ef11a3ae7af7ed823f90f31f8add214a8 [diff] |
increasing timeout for compute nodes provisioning Change-Id: I21746a535b8c1cfc999e572ae02000c7828e7daf (cherry picked from commit 49c818ccbce7b74d372a9a7a0ee16ad9b1cb66d5) (cherry picked from commit be198b8ef3abcfc128930ae9f5b766864924a65b)
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: