it might be reasonable to allow the user to define a "url_base", and then the euca2ools would use this base and insert the region as ec2 does.
ie, by default 'url_base' would be 'ec2.amazonaws.com'.
When the user passes '--region us-east-1', then 'us-east-1.ec2.amazonaws.com' would be used.
This would allow the user (in a possibly contrived example) to use "regions" for Eucalyptus also, by simply setting up their dns entries for their separate cloud controllers.
Example:
url_base: cc.domain.com
no region flag: cc.domain.com
--region foo: foo.cc.domain.com
--region bar: bar.cc.domain.com
it might be reasonable to allow the user to define a "url_base", and then the euca2ools would use this base and insert the region as ec2 does.
ie, by default 'url_base' would be 'ec2.amazonaws. com'. 1.ec2.amazonaws .com' would be used.
When the user passes '--region us-east-1', then 'us-east-
This would allow the user (in a possibly contrived example) to use "regions" for Eucalyptus also, by simply setting up their dns entries for their separate cloud controllers.
Example:
url_base: cc.domain.com
no region flag: cc.domain.com
--region foo: foo.cc.domain.com
--region bar: bar.cc.domain.com