>>> +aeolus::provider{"ec2":
>>> + port => 3002,
>>> + login_user => 'admin',
>>> + login_password => 'password',
>>> + require =>
Aeolus::Site_admin["admin"] }
>>> +
>> This isn't going to work as-is. Now that we support multiple amazon
>> regions, the only way factory knows what region to use is by the
>> provider name. Once we support multi-provider deltacloud cores this
>> problem goes away, but for now, 'name' is where we have to specify this.
>>
>> So for now the ec2 provider needs to have the name 'ec2-us-east-1'
>> (provider type is still ec2 though).
>> See here for the list of valid ec2 provider names:
>>
https://github.com/aeolusproject/image_factory/blob/master/imagefactory/b...
>>
>>
>>
> OK No biggie, will just modify the patch to separate the provider type
> from the name and to update the name. By default do we want multiple
> deltacloudd instances setup for all the Amazon regions, or do we just
> want to stick with the one (ec2-us-east-1)?
>
> -Mo
I would vote for setting them all up, just because with the current
setup, it will kind of be a pain for the user (on a few levels). If
anyone strongly objects, I would roll with it though.
-j
OK Updated and resent, I created providers for the two ec2 us regions
(east and west). If we want to add more, its just as trivial as copying
and pasting a few lines of code in recipes/aeolus_recipe/aeolus_recipe.pp
-Mo