Mailing-List: contact deltacloud-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: deltacloud-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of sang-min.park@eucalyptus.com
 designates 74.125.149.211 as permitted sender)
From: Sang-Min Park <sang-min.park@eucalyptus.com>
References: <1292537989.11329.62.camel@avon.watzmann.net>
In-Reply-To: <1292537989.11329.62.camel@avon.watzmann.net>
MIME-Version: 1.0
Thread-index: Acudb1v29tWv1yUTQnOCfLfnlvpTGgAAMzYg
Date: Thu, 16 Dec 2010 14:30:22 -0800
Message-ID: <241c87089db916ffa8caa110fa2e30fe@mail.gmail.com>
Subject: RE: Eucalyptus and dynamic switching of driver/provider
To: David Lutterkort <lutter@redhat.com>, deltacloud-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

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

We use the same environment variable as EC2 to expose the URL (e.g.,
EC2_URL, S3_URL, EC2_ACCESS_KEY, etc).
The rightscale's aws gem was able to speak to Eucalyptus and I recently
tested 'aws' gem and confirmed it speak to Eucalyptus without changes.


-----Original Message-----
From: David Lutterkort [mailto:lutter@redhat.com]
Sent: Thursday, December 16, 2010 2:20 PM
To: deltacloud-dev@incubator.apache.org
Cc: Sang-Min Park
Subject: Eucalyptus and dynamic switching of driver/provider

Hi Sang-Min,

Since we are going through some pain with (a) rewriting the EC2 driver
and (b) making it possible to select the driver and endpoint
dynamically, I was wondering if you could explain what the best approach
for Eucalyptus is.

IOW, with Eucalyptus, do storage and compute requests go through the
same endpoint, so that users could set
API_PROVIDER=http://euca.example.com/ and be done or are there separate
endpoints for compute and storage ?

David