Sorry for the late response to this thread. Yes, I agree with the idea of having users set API_PROVIDER to point to Eucalyptus services.
Another direction is to use EC2_URL/S3_URL as an endpoint. Most Eucalyptus users already have those env variables set up and the 'aws' gem can parse the hostname, service path, and port from the URL. If EC2 driver doesn't set up endpoint explicitly assuming EC2_URL/S3_URL variables to point to it, then we may have one EC2 driver to support both Eucalyptus and EC2. Do we have some time estimate on when the EC2 driver will be committed to the core? Sang-Min -----Original Message----- From: David Lutterkort [mailto:[email protected]] Sent: Thursday, December 16, 2010 3:01 PM To: [email protected] Subject: RE: Eucalyptus and dynamic switching of driver/provider On Thu, 2010-12-16 at 14:30 -0800, Sang-Min Park wrote: > They go through separate endpoints. The endpoint for compute (EC2 api) > has a form: > http://192.168.23.71:8773/services/Eucalyptus > > And the endpoint for storage(Walrus, which exposes S3 API) has a form: > http://192.168.23.71:8773/services/Walrus The best approach then might be to make a separate euca driver, which subclasses the EC2 driver, and mostly differs in how API_PROVIDER is used to select the endpoint. It seems easiest to me to tell users to set API_PROVIDER=http://192.168.23.71:8773/services and then have the driver append Eucalyptus or Walrus as needed David
