[RFE - Azure] Custom naming convention when creating VMS

[Peter Jose De Sousa]

Hi,

We're seeing a requirement in field when creating new VMs on Azure with juju that these new VMs follow a naming convention. Ideally, this would be a static naming convention as a first pass e.g. MY-NAMING-CONVENTION-{NUMBER}

Then moving to a 'progammable' one later e.g. {MY-CONTROLLER-ID}-{MY-VM-NAME-OR-ID} where the variables are substitued by the provider in juju, e.g. the azure provider.

Cheers,

Peter

[Ian Booth (wallyworld)]

Assuming {NUMBER} is like for units where it's monotonically increasing, there would need to be a place to store the previously used number etc. There's an argument that doing this work could be considered holistically across all providers, not just Azure, given the need to tweak the model to deal with the next number to use etc.

It's not necessarily super hard to do, but not totally trivial either given the doc and testing that would need to go along with it.

[Ian Booth (wallyworld)]

I may have read this wrong - I guess by NUMBER you just mean the current machine number we currently use. And you want to supply your own prefix for that.

Sorry for the misinterpretation.

[Peter Jose De Sousa (pjds)]

Thanks @Ian, you got it!

Just writing a comment to note that this requirement may extend beyond Azure into Openstack, as it's a requirement across the organisation.

[Jeff Hillman (jhillman)]

I also have a customer that this is a huge requirement for. Simply naming machines machine-x is against many policies.

[Nicolas Vinuesa (nvinuesa)]

I have merged the patch for the bug https://bugs.launchpad.net/juju/+bug/2046546 which was derived from this one. We didn't implement any new feature, i.e. we didn't add a way to have custom prefixes, but at least the machine names will be unique and the format is the same as in all other providers.