> Euca2ools is designed to be generic and one of the design goals was to
> not assume a specific endpoint or endpoints. The endpoint could be AWS
> or any Eucalyptus installation including the UEC or any other EC2
> compatible service.
>
> I do not think the proposed fix is in the scope of what the upstream can
> provide.
I hope that this issue can be addressed under bug 485106. Given a suitable
config file, EC2_URL can be defined there.
In general, though, I hope we can move away from expecting people to set
configuration in environment variable. Basically, given a suitable
configuration file (which could be installed by default or be well
documented), the user should not have to worry about such things.
On Tue, 24 Nov 2009, Neil Soman wrote:
> Euca2ools is designed to be generic and one of the design goals was to
> not assume a specific endpoint or endpoints. The endpoint could be AWS
> or any Eucalyptus installation including the UEC or any other EC2
> compatible service.
>
> I do not think the proposed fix is in the scope of what the upstream can
> provide.
I hope that this issue can be addressed under bug 485106. Given a suitable
config file, EC2_URL can be defined there.
In general, though, I hope we can move away from expecting people to set
configuration in environment variable. Basically, given a suitable
configuration file (which could be installed by default or be well
documented), the user should not have to worry about such things.