You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by Eric Woods <wo...@gmail.com> on 2011/04/20 20:14:33 UTC
Re: [VOTE] release deltacloud 0.3.0 (RC3)
+1. Thanks.
- Eric W.
Re: [VOTE] release deltacloud 0.3.0 (RC3)
Posted by Carl Trieloff <cc...@redhat.com>.
+1
Carl.
Re: [VOTE] release deltacloud 0.3.0 (RC3)
Posted by Sang-Min Park <sa...@eucalyptus.com>.
+1. Yes David, it works as you described. Thanks!
Sang-min
On Mon, Apr 25, 2011 at 3:24 PM, David Lutterkort <lu...@redhat.com> wrote:
> On Wed, 2011-04-20 at 14:28 -0700, Sang-Min Park wrote:
> > David,
> >
> > There's one issue regarding Eucalyptus endpoint. In EC2 driver, the env
> > variables are deleted in global scope, whereas previously it was
> nullified
> > inside 'new_client' method. When a user starts the server with eucalyptus
> > driver (deltacloudd -i eucalyptus), the env. variables set by Eucalyptus
> > installation will be deleted when EC2 driver (base driver of Eucalyptus)
> is
> > loaded. This causes AWS to point to the default EC2 endpoint.
>
> That behavior is intentional - the EC2_URL etc. env variables are only
> used because the base library (aws) we use to talk to EC2 respects them;
> it's therefore an implementation detail that setting EC2_URL works.
>
> Users should set the API_PROVIDER environment variable to select an
> endpoint when the server is launched; they can also pass the -P option
> to deltacloudd.
>
> David
>
>
>
Re: [VOTE] release deltacloud 0.3.0 (RC3)
Posted by David Lutterkort <lu...@redhat.com>.
On Wed, 2011-04-20 at 14:28 -0700, Sang-Min Park wrote:
> David,
>
> There's one issue regarding Eucalyptus endpoint. In EC2 driver, the env
> variables are deleted in global scope, whereas previously it was nullified
> inside 'new_client' method. When a user starts the server with eucalyptus
> driver (deltacloudd -i eucalyptus), the env. variables set by Eucalyptus
> installation will be deleted when EC2 driver (base driver of Eucalyptus) is
> loaded. This causes AWS to point to the default EC2 endpoint.
That behavior is intentional - the EC2_URL etc. env variables are only
used because the base library (aws) we use to talk to EC2 respects them;
it's therefore an implementation detail that setting EC2_URL works.
Users should set the API_PROVIDER environment variable to select an
endpoint when the server is launched; they can also pass the -P option
to deltacloudd.
David
Re: [VOTE] release deltacloud 0.3.0 (RC3)
Posted by Sang-Min Park <sa...@eucalyptus.com>.
David,
There's one issue regarding Eucalyptus endpoint. In EC2 driver, the env
variables are deleted in global scope, whereas previously it was nullified
inside 'new_client' method. When a user starts the server with eucalyptus
driver (deltacloudd -i eucalyptus), the env. variables set by Eucalyptus
installation will be deleted when EC2 driver (base driver of Eucalyptus) is
loaded. This causes AWS to point to the default EC2 endpoint.
It works though when clients supply X-Deltacloud-Provider.
I think the best way to solve it is to move ENV.delete to inside a method
that's overriden by Eucalyptus driver (i.e., new_client).
Sang-min
On Wed, Apr 20, 2011 at 11:14 AM, Eric Woods <wo...@gmail.com> wrote:
> +1. Thanks.
>
> - Eric W.
>