Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Naming convention of hostnames and azure VM objects #13

Open
fberson opened this issue Dec 1, 2016 · 1 comment
Open

Naming convention of hostnames and azure VM objects #13

fberson opened this issue Dec 1, 2016 · 1 comment

Comments

@fberson
Copy link

fberson commented Dec 1, 2016

The naming os computer hostnames and azure VM names is not very consistent and does not allow customers to add a custom prefix. I would like to suggest introduce 3 new variables to be able to provide the prefix for each of the three roles, as an example for RD Gateway:

       "gatewayHostNamePrefix": {
         "type": "string",
          "defaultValue": "RDGW-",
          "metadata": {
          "description": "Hostname prefix for RD Gateway Servers"
         }

Use those to construct the computername like below

       "osProfile": {
  "computerName": "[concat(parameters(' gatewayHostNamePrefix'),'0', copyindex(1))]",

And use the same convention for the VM names in Azure as well to make things consistent

"type": "Microsoft.Compute/virtualMachines",
"name": "[concat(parameters(gatewayHostNamePrefix'),'0', copyindex(1))]",
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants