Tomaž and Paul -- thanks for your quick responses. And Tomaž -- thanks for the patch, I'll give a try soon.
Grig 2010/12/10 Tomaž Muraus <[email protected]>: > I think that using availability zones in place of locations is a > reasonable solution, so I have attached a short patch which adds > availability zones to each region. > Thanks, > Tomaz > > On Sat, Dec 11, 2010 at 12:26 AM, Paul Querna <[email protected]> wrote: >> >> AZs actually map pretty well to what list_locations should have >> available to you. >> >> For each region, we are currently hard coding a single Location: >> def list_locations(self): >> return [NodeLocation(0, 'Amazon US N. Virginia', 'US', self)] >> >> So I'd be fine with list_locations actually returning a list of the >> Availability Zones. >> >> I had some thought at one point of making an Aggregate EC2 Driver, >> which would connect to all regions and combine all operations across >> all regions, ie list_nodes, but this is kinda hard to be feasible for >> things like create_node which need Region specific parameters for >> things like what AMI to boot. In that context a list_locations >> returning each region would of made sense, but for a practical matter, >> I think returning each AZ inside a region is a good change. >> >> Thanks, >> >> Paul >> >> >> >> On Fri, Dec 10, 2010 at 3:14 PM, Grig Gheorghiu >> <[email protected]> wrote: >> > Hello, >> > >> > I was looking for a way to launch EC2 instances via libcloud while >> > also specify an availability zone (AZ), such as us-east-1b or >> > us-east-1c for example. Libcloud supports the notion of EC2 location, >> > which is equivalent to an EC2 region from what I see, but there seems >> > to be no way of dealing with AZs. Or am I mistaken? >> > >> > Thanks, >> > >> > Grig >> > > >
