On Fri, Dec 06, 2013 at 11:38:03AM +1100, Angus Salkeld wrote: > On 05/12/13 17:00 +0000, Steven Hardy wrote: > >On Thu, Dec 05, 2013 at 04:11:37PM +0000, ELISHA, Moshe (Moshe) wrote: > >>Hey, > >> > >>I really liked the v2 Heat API (as proposed in Create a new v2 Heat > >>API<https://blueprints.launchpad.net/heat/+spec/v2api>) and I think it > >>makes a lot of sense. > >> > >>One of the proposed changes is to "Remove template_url from the request > >>POST", so the template will be passed using the "template" parameter in the > >>request body. > >> > >>Could someone please elaborate how exactly Heat Orchestration Templates > >>written in YAML will be embedded in the body? > > > >In exactly the same way they are now, try creating a stack using a HOT yaml > >template, with --debug enabled via python heatclient and you'll see what I > >mean: > > > >wget > >https://raw.github.com/openstack/heat-templates/master/hot/F18/WordPress_Native.yaml > > > >heat --debug stack-create -P "key_name=userkey" -f ./WordPress_Native.yaml > >wp1 > > > >This works fine now, so there's nothing to do to support this. > > Given the talks about Heater/appstore/glance-templates it would be > good to be able to pass a references to one of those systems so > the user doesn't have to upload to glance, then send a copy to heat. > > so just pass a template_id like how nova.boot() takes an image_id.
Sure, that sounds like a good idea, when the template service exists. That's kinda orthogonal from this issue though, which is removing arbitrary user-provided URLs; I'm perfectly happy if we add template_id in future. Steve _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
