Gitiles
Code Review Sign In
gerrit.opencord.org / cord / b44e9b721655f7105ffb269cadcd504095514cec
commitb44e9b721655f7105ffb269cadcd504095514cec[log] [tgz]
authorZack Williams <zdw@cs.arizona.edu>Tue Oct 17 15:22:55 2017 -0700
committerZack Williams <zdw@cs.arizona.edu>Tue Oct 17 15:22:55 2017 -0700
tree1fbad2a55ba58735bcfbc1f438701ea401c2303a
parent522a4e1b7f9f7e6bb129cc147a241dd2dcfd279a [diff]
[CORD-2095]
Specifiy nfs connection for synced_folder override, to avoid using rsync

Change-Id: I11bb28a18f6455d9fe6f9ba261ce6ec040aa4233
1 file changed
tree: 1fbad2a55ba58735bcfbc1f438701ea401c2303a
  1. .gitignore
  2. .gitmodules
  3. Jenkinsfile.ciab
  4. Jenkinsfile.imagebuilder
  5. Jenkinsfile.newBuildSystem
  6. LICENSE.txt
  7. Makefile
  8. README.md
  9. ansible.cfg
  10. ansible/
  11. docker_images.yml
  12. docs/
  13. elk-logger/
  14. genconfig/
  15. image_logs/
  16. logs/
  17. milestones/
  18. podconfig/
  19. scenarios/
  20. scripts/
  21. 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: