Re: [Openstack] Thinking about Backups/Snapshots in Nova Volume

2011-07-20 Thread Thorsten von Eicken
+1 On 7/20/2011 2:27 PM, Chuck Thier wrote: > Yeah, I think you are illustrating how this generates much confusion :) > > To try to be more specific, the base functionality should be: > > 1. Create a point in time backup of a volume > 2. Create a new volume from a backup (I guess it seems reasonab

Re: [Openstack] Cross-zone instance identifiers in EC2 API - Is it worth the effort?

2011-07-08 Thread Thorsten von Eicken
On 7/8/2011 5:32 PM, Lorin Hochstein wrote: I don't think that the OpenStack project should commit to maintaining EC2 compatibility at all costs, only as long as the benefits outweigh the development costs. In particular, if Amazon deliberately started making changes to break the API, that woul

Re: [Openstack] Cross-zone instance identifiers in EC2 API - Is it worth the effort?

2011-07-07 Thread Thorsten von Eicken
On 7/7/2011 8:53 AM, Soren Hansen wrote: > 2011/7/7 Vishvananda Ishaya : >> I think we should move toward ec2 being a compatibility layer that is >> translated into the os api. This compatibility layer would sit at the top >> level zone and could maintain its own database for conversion of ids,

Re: [Openstack] Cross-zone instance identifiers in EC2 API - Is it worth the effort?

2011-07-07 Thread Thorsten von Eicken
FYI, there's nothing in the EC2 API that limits instance identifiers (or other IDs) to 32 bits. The IDs are strings, so it's trivial for EC2 to add another digit when running out of 32-bit IDs. TvE On 7/7/2011 7:57 AM, Soren Hansen wrote: > 2011/7/7 Jay Pipes : >> Multiple zones is currently o

Re: [Openstack] Feedback on Portable Configuration Drive Blueprint

2011-06-21 Thread Thorsten von Eicken
On 6/21/2011 1:09 PM, Scott Moser wrote: > On Tue, 21 Jun 2011, Thorsten von Eicken wrote: > >>>> 3. How does one send the configuration drive content? What is the API >>>> call where we provide the configuration information and what is the >>>> expec

Re: [Openstack] Floating IP in OS API

2011-06-21 Thread Thorsten von Eicken
Thanks for the links, I added the following questions & comments to the etherpad. If that's the wrong place, let me know... 1. The LIST response must contain the full deatil of each IP. Otherwise one has to do N further requests to get them, which doesn't scale at all. In this case, since there is

Re: [Openstack] Feedback on Portable Configuration Drive Blueprint

2011-06-21 Thread Thorsten von Eicken
Comments inline below. On 6/20/2011 1:40 PM, Scott Moser wrote: > On Fri, 17 Jun 2011, Thorsten von Eicken wrote: >> We're very much looking forward to the new "portable configuration >> drive" functionality and would like to provide feedback. If this is not >>

[Openstack] Feedback on Portable Configuration Drive Blueprint

2011-06-17 Thread Thorsten von Eicken
We're very much looking forward to the new "portable configuration drive" functionality and would like to provide feedback. If this is not the best forum, please point me to it. The blueprint is: https://blueprints.launchpad.net/nova/+spec/configuration-drive We reviewed the initial work in: http

Re: [Openstack] Feedback on HTTP APIs

2011-06-03 Thread Thorsten von Eicken
On Jun 2, 2011, at 5:04 PM, Thorsten von Eicken wrote: We neither hate nor love UUIDs, but we like them when they provide value and we also accept alternatives. What we do hate is ambiguity and in

Re: [Openstack] Feedback on HTTP APIs

2011-06-02 Thread Thorsten von Eicken
We neither hate nor love UUIDs, but we like them when they provide value and we also accept alternatives. What we do hate is ambiguity and in certain cases UUIDs help. Look at the hrefs returned in this sample resource and picture what you'd store in your database as unique identifier to refer

Re: [Openstack] Getting pagination right

2011-05-27 Thread Thorsten von Eicken
On 5/27/2011 6:05 AM, Jay Pipes wrote: > > But, it sounds like folks aren't really concerned about the > consistency of the view as much as the scalability concerns, and I'm > perfectly cool with ditching OFFSET in favour of a last-record marker. > THere's consistency and consistency. We need some