Upcoming change in 1.24: tags in EC2

Dimiter Naydenov dimiter.naydenov at canonical.com
Fri May 22 08:10:41 UTC 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 22.05.2015 11:07, Andrew Wilkins wrote:
> On Fri, May 22, 2015 at 3:47 PM, Dimiter Naydenov 
> <dimiter.naydenov at canonical.com
> <mailto:dimiter.naydenov at canonical.com>> wrote:
> 
> On 22.05.2015 08 <tel:22.05.2015%2008>:26, Andrew Wilkins wrote:
>> Hi all,
> 
>> Just a small announcement, in case anyone cares. In the EC2 
>> provider, from 1.24, we will start tagging instances and volumes 
>> with their Juju-internal names and the Juju environment UUID. 
>> Instances, for example, will have a name of "machine-0", 
>> "machine-1", etc., corresponding to the ID in "juju status".
>> There is not currently an upgrade step to tag existing resources,
>> so only newly created resources will be tagged.
> 
>> The environment UUID can be used to identify all instances and 
>> volumes that are part of an environment. This could be used to
>> for billing purposes; to charge the infrastructure costs for a
>> Juju environment to a particular user/organisation.
> 
>> We will be looking at doing the same for OpenStack for 1.24
>> also.
> 
>> Cheers, Andrew
> 
> 
> I assume we won't tag instances with a Name tag if there already
> is one, right? Otherwise it's a bad UX.
> 
> 
>> Not sure I follow. We're creating the instances; they have not
>> had names up until now (in EC2). When we get to adding these tags
>> to existing instances, I agree that we should not replace the
>> existing name if it has one.
Yes, of course - if we're creating them, that's fine. Sorry, I was
thinking of tagging existing entities (e.g. Subnets as belonging to a
space, without creating them).

> 
> For OpenStack, we should use instance names the same way (and only
> if the name is not already set), as tags not supported widely yet.
> 
> 
>> On OpenStack we will continue to set names as we did before.
>> There we will just set additional metadata for the environment
>> UUID.
> 
> 
> 
> -- Juju-dev mailing list Juju-dev at lists.ubuntu.com
> <mailto:Juju-dev at lists.ubuntu.com> Modify settings or unsubscribe
> at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
> 
> 

- -- 
Dimiter Naydenov <dimiter.naydenov at canonical.com>
Juju Core Sapphire team <http://juju.ubuntu.com>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJVXuSBAAoJENzxV2TbLzHw4t8H/1+UZEHeY0BnvxPgZjxgc+g+
aKQSO86BvB1CQ8RDS9NYYp3Tj1Viy9R3nEEsRQCBEH7m7n9Hicem+1bJKmqm8PRI
WSx4hw8C5vD6r1GDgnbTMyxu7YehZPa1I73olZg2csPCjG6bATGJaZnsXKjsyDp6
ZmHyX/On9zf4h6+u2EFX4zYtI3X9eLyHWiGKEukuh89IpsntmkMrKWcKO7xId2g5
YWMl5ZmyXtBNnNeid+4wc5ktsZg3QkG+GL6ID2qehAo2QLlWEDtOLw4oPq8ZxkQ8
FUekTVxzdYAA2c8Tx5s+8F2DF68oxsQwR+SKLVZAzqrujSEed95LLeJLhmN8OzQ=
=nSUd
-----END PGP SIGNATURE-----



More information about the Juju-dev mailing list