[openstack-dev] [Heat] Referencing VPC resources across templates

Simon Pasquier pasquier.simon at gmail.com
Thu Apr 4 08:57:03 UTC 2013

Thanks for the explanation.

My point is to understand the current limitations of Heat regarding VPC
resources and other resources making use of VPC.
I raised a couple of bugs on Launchpad:
 https://bugs.launchpad.net/heat/+bug/1163952 (Instance resource should
implement the SubnetId property)
https://bugs.launchpad.net/heat/+bug/1163991 (Instance resource should
implement the SecurityGroupIds property)
>From my understanding of Heat & Quantum, both should be possible to

I have additional questions concerning AWS::EC2::EIP
and AWS::EC2::EIPAssociation resources:
- The AWS::EC2::EIP resource doesn't use the InstanceId property. Is it on
- Is it feasible to implement the AllocationId property in
- Is it feasible to implement the NetworkInterfaceId property in

I guess you already looked at it but the AWS Cloudformation documentation
indicates several ways to provision elastic IP:


2013/4/4 Steve Baker <sbaker at redhat.com>

> On 04/04/2013 12:21 PM, Zane Bitter wrote:
> >>> I want to pass the VpcId value as a parameter to the second template
> >>> but the stack creation fails. Looking at the code, this use case
> >>> doesn't seem to be supported.
> >>> Am I right? If yes, is it something planned for a future release?
> >> What version of Heat are you running? There was actually a change
> >> released in grizzly-rc1 which addressed this issue:
> >> https://bugs.launchpad.net/heat/+bug/1142812
> >> https://review.openstack.org/#/c/23391/
> >
> > The issue is that it's then looked up using stack.resource_by_refid(),
> > which only looks at resources in the current stack:
> >
> https://github.com/openstack/heat/commit/63882b7bcbc55e411db26b4689f9cfe30d5a722b#L3R51
> >
> >
> > That's used to get the router_id from the VPC resource's metadata.
> > What you need is to use the supplied ID (which is the network_id)
> > directly so that you don't need to access the VPC resource at all. I
> > have no idea if that's possible with Quantum.
> Yes, a VPC consists of a Quantum net plus a router, but outside of Heat
> the net and router are not coupled so it will currently not be possible
> to pass in a VpcId.
> As an aside, if your templates are only going to be run on OpenStack I
> would recommend using the native quantum resources instead of VPC. The
> VPC resource types are there so that you can support AWS and OpenStack
> in a single template.
> cheers
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130404/3f807a6e/attachment.html>

More information about the OpenStack-dev mailing list