Gitiles
Code Review Sign In
gerrit.opencord.org / cord / 9ae696bc2db008137ca919b6abafdabb1f4393fd
commit9ae696bc2db008137ca919b6abafdabb1f4393fd[log] [tgz]
authornosignal <nosignal@g2.nctu.edu.tw>Thu Oct 19 17:46:44 2017 +0800
committerAndy Bavier <andy@opennetworking.org>Thu Nov 09 15:34:33 2017 -0700
tree97c5aaa372d8cfbff3d1e5fd7631ef07a22f83bb
parent2bc46a46552c73acd2a74d2fb2f7c5a3e8620243 [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
(cherry picked from commit d41093583026dc05da9aa4187aae50afb21bbf15)
1 file changed
tree: 97c5aaa372d8cfbff3d1e5fd7631ef07a22f83bb
  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: