Wire ServiceNetMap as a top level parameter
authorDan Prince <dprince@redhat.com>
Tue, 2 Jun 2015 14:33:01 +0000 (10:33 -0400)
committerDan Prince <dprince@redhat.com>
Wed, 3 Jun 2015 12:58:12 +0000 (08:58 -0400)
commitd413eb63f3d317c56b24282223f12dfacc0f9ae3
tree7e4fb4bbf4254b5ad2339cd79ed21e6307361a04
parenteaa5eb6a5985c52b484d58e22075b84caf2f2493
Wire ServiceNetMap as a top level parameter

This patch makes ServiceNetMap a top level parameter.

This is helpful to tools like Tuskar which don't support Heat
environments that contain both a resource_registry and default_parameters.

ServiceNetMap will in fact be utilized at the top level in some of
the VIP related patches that follow.

Change-Id: I375063dacf5f3fc68e6df93e11c3e88f48aa3c3a
compute.yaml
controller.yaml
overcloud-resource-registry-puppet.yaml
overcloud-without-mergepy.yaml