Feature #581
Better support for EC2 availability zones
Status: | Closed | Start date: | 04/18/2011 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | Daniel Molina | % Done: | 100% | |
Category: | Drivers - Auth | |||
Target version: | Release 3.6 | |||
Resolution: | fixed | Pull request: |
Description
The suggested multi-availability zone / EC2 site configuration does not seem to work well with EC2 compatible clouds with the different availability zones behind single front-end URL.
How about adding support for defining a default availability zone for each EC2 driver or defining the desired availability zone on the VM template? The tool "ec2-run-instances" used by the driver to launch a new instance already supports the choice of availability zone with the "-z <ZONE>" command line option.
Would anyone else find this type of feature useful? Especially the choice of availability zone in the VM Template's EC2 section is very easy to implement in the driver (if I haven't understood the driver code completely wrong - I still have relatively little experience with One). Am I missing any obvious gotchas here?
Associated revisions
feature #581: Better support for EC2 availability zones
History
#1 Updated by Tuomo Varis about 10 years ago
- File one_vmm_ec2.rb.patch added
Just realized I should have posted this as a "Request" instead of "Feature". Sorry.
Anyway, attached is a small patch to modify one_vmm_ec2.rb to support this behaviour in case someone is interested.
#2 Updated by Ruben S. Montero over 9 years ago
- Assignee changed from Javi Fontan to Daniel Molina
#3 Updated by Daniel Molina about 9 years ago
- Status changed from New to Closed
- Target version set to Release 3.6
- % Done changed from 0 to 100
- Resolution set to fixed
Hi Tuomo,
I have included this patch in master.
Thanks for the feedback