Gitiles
Code Review Sign In
gerrit.opencord.org / cord / d41093583026dc05da9aa4187aae50afb21bbf15
commitd41093583026dc05da9aa4187aae50afb21bbf15[log] [tgz]
authornosignal <nosignal@g2.nctu.edu.tw>Thu Oct 19 17:46:44 2017 +0800
committerAndy Bavier <andy@opennetworking.org>Thu Nov 09 14:28:25 2017 -0800
tree9bcb2bc32b65de7e4d9060f14aae70cbcb753980
parent08e22f9f1343aa4b668451bc3cb2b2266f4bd483 [diff]
Fix conifg.mk render issue

For podconfig with skipTags defined but has no options cause jinja2 NonType object not iterable Error.
To fix this issue, add a NonType check after skipTags defined check to avoid NonType object iteration.

Change-Id: I7b0ca533c52acbe07899edb64a18dad75b255889
1 file changed
tree: 9bcb2bc32b65de7e4d9060f14aae70cbcb753980
  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: