[openstack-dev] [Heat] Referencing VPC resources across templates
simon.pasquier at bull.net
Fri Apr 5 07:19:48 UTC 2013
Le 05/04/2013 01:35, Steve Baker a écrit :
> 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
> 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
>> - 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:
> Could you please raise 3 bugs for these? It helps for our tracking and
Sure, I just wanted to double-check first with you guys :)
BTW I've completed my code review and I identified a couple of other
things that could be improved. I'll raise bugs for these too.
> This all looks like it could be implemented early in the Havana cycle.
I might be able to tackle some of them.
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
Bull, Architect of an Open World
Phone: + 33 4 76 29 71 49
More information about the OpenStack-dev