<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, May 25, 2015 at 6:22 AM, Tim Penhey <span dir="ltr"><<a href="mailto:tim.penhey@canonical.com" target="_blank">tim.penhey@canonical.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 22/05/15 17:26, Andrew Wilkins wrote:<br>
> Hi all,<br>
><br>
> Just a small announcement, in case anyone cares. In the EC2 provider,<br>
> from 1.24, we will start tagging instances and volumes with their<br>
> Juju-internal names and the Juju environment UUID. Instances, for<br>
> example, will have a name of "machine-0", "machine-1", etc.,<br>
> corresponding to the ID in "juju status". There is not currently an<br>
> upgrade step to tag existing resources, so only newly created resources<br>
> will be tagged.<br>
<br>
</span>What is the rationale behind not tagging existing machines? Surely it<br>
would be useful?<br></blockquote><div><br></div><div>It just hasn't been done yet. It should be. I needed to add tags to volumes,</div><div>so I just added them to machines while I was in the vicinity.</div></div></div></div>