Remove unsafe "unset" defaults
authorSteven Hardy <shardy@redhat.com>
Wed, 9 Dec 2015 18:23:08 +0000 (18:23 +0000)
committerSteven Hardy <shardy@redhat.com>
Wed, 9 Dec 2015 18:26:03 +0000 (18:26 +0000)
commit293f19b2a41386e1eea47a9e6add24b006c69c42
treeb51c3a2dfd32638d97585c7ca5ac4021dafa6f21
parent99bd9970d6bedee8228a6c8ff3d6f45aa1380e22
Remove unsafe "unset" defaults

All of our sensitive parameters are defaulted to easily predictable
values, which is very bad from a security perspective because we don't
force clients to make sane choices thus risk deploying with the
predictable default values.  tripleoclient supports generating random
values for all of these, so remove the defaults, for non-tripleoclient
usage we can create a developer-only environment with defaults.

Related-Bug: #1516027
Change-Id: Ia0cf3b7e2de1aa42cf179cba195fb7770a1fc21c
Depends-On: Ifb34b43fdedc55ad220df358c3ccc31e3c2e7c14
overcloud.yaml
puppet/cinder-storage.yaml
puppet/compute.yaml
puppet/controller.yaml
puppet/swift-storage.yaml