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

Steve Baker sbaker at redhat.com
Thu Apr 4 23:35:21 UTC 2013

On 04/04/2013 09:57 PM, Simon Pasquier wrote:
> 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
> implement.
Yes, these both shouldn't be difficult to implement.
> 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 purpose?
> - Is it feasible to implement the AllocationId property in
> AWS::EC2::EIPAssociation?
> - Is it feasible to implement the NetworkInterfaceId property in
> AWS::EC2::EIPAssociation?
> I guess you already looked at it but the AWS Cloudformation
> documentation indicates several ways to provision elastic IP:
> http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/quickref-ec2.html#scenario-ec2-eip
Could you please raise 3 bugs for these? It helps for our tracking and

This all looks like it could be implemented early in the Havana cycle.


More information about the OpenStack-dev mailing list