Yeah, I'm not sure *how much* of the zone information would be sensitive,
though. Ie, is it okay to expose a unique identifier and nothing more? Or do
we want to expose _nothing_?
- Chris
On Jul 8, 2011, at 2:28 PM, Sandy Walsh wrote:
> Isn't there a concern of leaking internal Zone information to the outside
> world (particularly in the Service Provider model)? If so, we're back to the
> mapping table.
>
> And, when multi-instance boot commands are more common ("provision me 10
> servers" vs. 1), then more people will be searching by Reservation Id,
> Project Id or Owner Id (I suspect). So, how long will this be a problem for?
>
> Do the same quirks apply to EC2 Reservation ID's as Instance ID's?
>
> -S
> ________________________________________
> From: openstack-bounces+sandy.walsh=rackspace....@lists.launchpad.net
> [openstack-bounces+sandy.walsh=rackspace....@lists.launchpad.net] on behalf
> of Chris Behrens [chris.behr...@rackspace.com]
> Sent: Friday, July 08, 2011 5:43 PM
> To: George Reese
> Cc: <openstack@lists.launchpad.net>; Ed Leafe; Chris Behrens
> Subject: Re: [Openstack] Cross-zone instance identifiers in EC2 API - Is it
> worth the effort?
>
> On Jul 8, 2011, at 5:11 AM, George Reese wrote:
>
>> I would just like to re-iterate that I think the entire UUID approach is
>> flawed and issues like this are one of the key reasons why.
>
> The only problem I'm aware of is that developers using the EC2 API are not
> adhering to the spec. If everyone treated them as strings, as they are
> supposed to be, then we wouldn't have to have this discussion.
>
> That said, I do have a particular problem with the current UUID
> implementation in that I wish some sort of unique zone identifier were a part
> of it. Accompany that with some other changes to zones and we could have
> more efficient zone routing. A side effect of that would be that it is less
> work to come up with an ID that, if truncated, would also be unique to EC2.
> Taking Ed Leafe's approach, you could remove the recursive zone checks.
>
> I'm not sure I'd vote for that route, though. It implies we kludge UUID
> generation just for EC2 in the heart of nova, which I think is completely
> wrong. I'm pretty much with Vish on everything he's said so far in this
> thread.
>
> - Chris
>
> This email may include confidential information. If you received it in error,
> please delete it.
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
This email may include confidential information. If you received it in error,
please delete it.
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
