Mailing-List: contact libcloud-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: libcloud@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of samslists@gmail.com
 designates 209.85.212.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=BwsxknKQMIneXn47Fopx/rRzKbBk5cyXGBtgCVNdQw26y4u52nGmo2mFVjRttp9bYa
         0e+EvoaELkcCPa+K33IjJBILgn54ARvMazU4FSGCADrx3jcx1cxo5AXcUVsTWgvS+8Yd
         Fd+bnJnpJfE63vgG4ZnjtUHDW4Y9JsQZ17Qp8=
MIME-Version: 1.0
In-Reply-To: <BANLkTimwujX3Vw693Cn1JaJR3P1FecTVNw@mail.gmail.com>
References: <BANLkTikS-7X54TWCKQkZF4Q=4tXCzXEyww@mail.gmail.com>
	<BANLkTimDupU-S3FtqX-DbZsbraO7Oj3zSw@mail.gmail.com>
	<BANLkTimO+f0o7WBWBM9Y3a-KoE+jhpF1Lw@mail.gmail.com>
	<BANLkTimwujX3Vw693Cn1JaJR3P1FecTVNw@mail.gmail.com>
Date: Fri, 8 Apr 2011 16:27:47 -0700
Message-ID: <BANLkTingQX9FEy3n2eCAF=x-HY2MTO2wXA@mail.gmail.com>
From: "Sam's Lists" <samslists@gmail.com>
To: libcloud@incubator.apache.org
Content-Type: multipart/alternative; boundary=bcaec5014c5be236be04a0709243
Subject: Re: [libcloud] Trouble naming an AWS EC2 node...

--bcaec5014c5be236be04a0709243
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Apr 8, 2011 at 4:08 PM, Tomaz Muraus <tomaz@cloudkick.com> wrote:

> In this case, I think we should add a name tag after creating a node so
> it's consistent with other drivers.
>
>
I agree, this  would be the best thing to do.  It looks like the code to set
a tag is in the repo., but not the current release.  But I don't think it's
called to set the name automatically.  (I'm running the released code, so
I'm not sure).

In the meantime, it would probably be worth documenting that the name is not
set for an ec2 instance.  It might save someone else a lot of time trying to
figure out why things aren't working.

Thanks

--bcaec5014c5be236be04a0709243--