incubator-deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Guiditta <jason.guidi...@gmail.com>
Subject Re: [PATCH 2/2] EC2: do not modify env variables EC2_URL and S3_URL
Date Tue, 19 Apr 2011 20:57:47 GMT
I've updated my local copy with these changes and can now connect to ec2 w/o
issue, thanks for the quick fix!

-j

On Tue, Apr 19, 2011 at 2:56 PM, David Lutterkort <lutter@redhat.com> wrote:

> On Mon, 2011-04-18 at 21:51 -0700, Sang-Min Park wrote:
> > Actually, I'd suggest:
> > ENV['EC2_URL'] = nil
> > ENV['S3_URL'] = nil.
> >
> > AWS overrides :endpoint_url if the environmental variables are set.
> > The typical eucalyptus installation will have the two env. variables set
> to
> > Eucalyptus/Walrus backend.
> > If a Eucalyptus user starts deltacloud process and if she switches to EC2
> > driver, AWS will attempt to connect Eucalyptus backend.
> >
> > If we set them nil, AWS will use the default endpoint for EC2 or the one
> set
> > through EC2 provider. I tested and confirmed it works.
>
> Good point - I've modified the driver to delete EC2_URL, S3_URL and
> ELB_URL from the environment.
>
> Users should use Deltacloud mechanisms to select endpoints; that we use
> AWS is an implementation detail, anyway.
>
> David
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message