Instance naming and tagging

Juju now tags instances and volumes created by supported providers with the Juju environment UUID, and related Juju entities. Instances will be tagged with the names of units initially assigned to the machine. Volumes will be tagged with the storage-instance name, and the owner (unit or service) of said storage.

Instances and volumes are now named consistently across EC2 and OpenStack, using the scheme:

juju-<env>-<resource-type>-<resource-ID>

...where <env> is the human-readable name of the environment as specified in environments.yaml; <resource-type> is the type of the resource ("machine" or "volume") and <resource-ID> is the numeric ID of the Juju machine or volume corresponding to the IaaS resource.

Names in Amazon AWS for example appear like this: named instances in Amazon ...and tags like this: tagged instances in Amazon

User-defined tags

Juju also adds any user-specified tags set via the "resource-tags" environment setting to instances and volumes. The format of this setting is a space-separated list of key=value pairs contained in the relevant section of your environments.yaml file:

resource-tags: key1=value1 [key2=value2 ...]

Alternatively, you can change the tags allocated to new machines in a bootstrapped environment by using the 'juju set-env' command

juju set-env resource-tags="origin=evilnick owner=Canonical"

user tagged instances in Amazon

You can change the tags again by simply running the above command again with different values. Changes will not be made to existing machines, but the new tags will apply to any future machines created.

These tags may be used, for example, to set up chargeback accounting.

Any tags that Juju manages will be prefixed with "juju-"; users must avoid modifying these, and for safety, it is recommended none of your own tags start with "juju"

© 2018 Canonical Ltd. Ubuntu and Canonical are registered trademarks of Canonical Ltd.