From: Steven Hardy Date: Thu, 23 Oct 2014 15:42:45 +0000 (+0100) Subject: Use parameter constraints for image, key and flavor X-Git-Tag: opnfv-6.0.0~2726^2 X-Git-Url: https://gerrit.opnfv.org/gerrit/gitweb?a=commitdiff_plain;h=928cd735f30752152e50a3b20145f899cb1b961c;p=apex-tripleo-heat-templates.git Use parameter constraints for image, key and flavor If you don't have (or provide) the wrong image, KeyName, or flavor, we fail at some later point (not always early, depending on what's wrong). Since Icehouse, Heat has had a "custom constraints" method of dynamically validating parameter values, by comparing the value provided with a list from the underlying service. Despite the name, there's nothing "custom" about the constraints, these ones are included in Heat by default (though they are pluggable, which is where the name comes from..) See the docs for more info: http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#custom-constraint Note, I've not considered network validation here, this could possibly be added in a subsequent patch. These constraints are evaluated via any of the following: - heat template-validate -f