Open Stack

On 04/04/2013 09:56 PM, Zane Bitter wrote:
> On 04/04/13 03:01, Steve Baker wrote:
>> On 04/04/2013 12:21 PM, Zane Bitter wrote:
>>> 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.
>
> In that case, squash the two together into one giant mega-id and tease
> them apart again when you need to use them.
>
> Not saying it's pretty... but it will work and that data should be
> regarded as pretty much opaque to users anyway.

My early versions used compound resource IDs. I moved away from them
when I ended up with resources that had IDs which were 3 concatenated
UUIDs :/

It might be worth re-introducing this approach just for the VPC resource
type though.

cheers