Individually tag instance in Azure VMSS
up vote
0
down vote
favorite
Is it possible to individually tag a specific vm instance in a scale set?
Something like this command:
az resource tag --tags "name=hostname.example.com ip=10.0.0.10" --id "/subscriptions/{SUBSCRIPTION_ID}/resourceGroups/{RESOURCE_GROUP}/providers/Microsoft.Compute/virtualMachineScaleSets/{SCALESET_ID}/{SCALESET_INSTANCE}"
SCALESET_INSTANCE is what I get when querying the instance metadata service as follows:
curl -s -H Metadata:true "http://169.254.169.254/metadata/instance/compute/name?api-version=2017-08-01&format=text"
However the response I get is:
az resource: error: argument --ids: invalid ResourceId value: <FULL_ID_PATH>
Tried using:
az resource tag -g {RESOURCE_GROUP} --resource-type "Microsoft.Compute/virtualMachines" -n {SCALESET_INSTANCE}
But no luck either, response is:
The Resource 'Microsoft.Compute/virtualMachines/{SCALESET_INSTANCE} under resource group '{RESOURCE_GROUP}' was not found.
azure-vm-scale-set
asked Nov 19 at 8:31
J00MZ
315312
add a comment |
up vote
0
down vote
favorite
Is it possible to individually tag a specific vm instance in a scale set?
Something like this command:
az resource tag --tags "name=hostname.example.com ip=10.0.0.10" --id "/subscriptions/{SUBSCRIPTION_ID}/resourceGroups/{RESOURCE_GROUP}/providers/Microsoft.Compute/virtualMachineScaleSets/{SCALESET_ID}/{SCALESET_INSTANCE}"
SCALESET_INSTANCE is what I get when querying the instance metadata service as follows:
curl -s -H Metadata:true "http://169.254.169.254/metadata/instance/compute/name?api-version=2017-08-01&format=text"
However the response I get is:
az resource: error: argument --ids: invalid ResourceId value: <FULL_ID_PATH>
Tried using:
az resource tag -g {RESOURCE_GROUP} --resource-type "Microsoft.Compute/virtualMachines" -n {SCALESET_INSTANCE}
But no luck either, response is:
The Resource 'Microsoft.Compute/virtualMachines/{SCALESET_INSTANCE} under resource group '{RESOURCE_GROUP}' was not found.
azure-vm-scale-set
asked Nov 19 at 8:31
J00MZ
315312
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Is it possible to individually tag a specific vm instance in a scale set?
Something like this command:
az resource tag --tags "name=hostname.example.com ip=10.0.0.10" --id "/subscriptions/{SUBSCRIPTION_ID}/resourceGroups/{RESOURCE_GROUP}/providers/Microsoft.Compute/virtualMachineScaleSets/{SCALESET_ID}/{SCALESET_INSTANCE}"
SCALESET_INSTANCE is what I get when querying the instance metadata service as follows:
curl -s -H Metadata:true "http://169.254.169.254/metadata/instance/compute/name?api-version=2017-08-01&format=text"
However the response I get is:
az resource: error: argument --ids: invalid ResourceId value: <FULL_ID_PATH>
Tried using:
az resource tag -g {RESOURCE_GROUP} --resource-type "Microsoft.Compute/virtualMachines" -n {SCALESET_INSTANCE}
But no luck either, response is:
The Resource 'Microsoft.Compute/virtualMachines/{SCALESET_INSTANCE} under resource group '{RESOURCE_GROUP}' was not found.
azure-vm-scale-set
asked Nov 19 at 8:31
J00MZ
315312
Is it possible to individually tag a specific vm instance in a scale set?
Something like this command:
az resource tag --tags "name=hostname.example.com ip=10.0.0.10" --id "/subscriptions/{SUBSCRIPTION_ID}/resourceGroups/{RESOURCE_GROUP}/providers/Microsoft.Compute/virtualMachineScaleSets/{SCALESET_ID}/{SCALESET_INSTANCE}"
SCALESET_INSTANCE is what I get when querying the instance metadata service as follows:
curl -s -H Metadata:true "http://169.254.169.254/metadata/instance/compute/name?api-version=2017-08-01&format=text"
However the response I get is:
az resource: error: argument --ids: invalid ResourceId value: <FULL_ID_PATH>
Tried using:
az resource tag -g {RESOURCE_GROUP} --resource-type "Microsoft.Compute/virtualMachines" -n {SCALESET_INSTANCE}
But no luck either, response is:
The Resource 'Microsoft.Compute/virtualMachines/{SCALESET_INSTANCE} under resource group '{RESOURCE_GROUP}' was not found.
azure-vm-scale-set
azure-vm-scale-set
asked Nov 19 at 8:31
J00MZ
315312
asked Nov 19 at 8:31
J00MZ
315312
asked Nov 19 at 8:31
J00MZ
315312
asked Nov 19 at 8:31
J00MZ
315312
asked Nov 19 at 8:31
J00MZ
315312
315312
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
It's impossible to individually tag instance in Azure VMSS as there is no resource type for VMSS instance, just for the type of Microsoft.Compute/virtualMachineScaleSets.
About the az resource tag command: az resource tag --tags vmlist=vm1 --id /subscriptions/{SubID}/resourceGroups/{ResourceGroup}/providers/xxxxxxx, the --id is used for using a resource identifier which is different from instance metadata service.
Overall, Azure virtual machine scale sets let you create and manage a group of identical, load balanced VMs. It works as an entirety, it seems that we do not need to add the tags for the individual instances.
answered Nov 20 at 3:18
Nancy Xiong
2,100116
Feature request then: Support tags for individual machines in a Scaleset. In AWS for example, an instance in an auto scaling group is exactly the same as any other instance and can be referenced individually by it's instance ID. Additionally, as shown above, Azure itself has a unique "name" identifier for each instance in a Scaleset, why not just add this as it's resource identifier as well?
– J00MZ
Nov 21 at 4:22
1
Welcome to vote it, I have posted this feature request here.
– Nancy Xiong
Nov 21 at 5:26
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
It's impossible to individually tag instance in Azure VMSS as there is no resource type for VMSS instance, just for the type of Microsoft.Compute/virtualMachineScaleSets.
About the az resource tag command: az resource tag --tags vmlist=vm1 --id /subscriptions/{SubID}/resourceGroups/{ResourceGroup}/providers/xxxxxxx, the --id is used for using a resource identifier which is different from instance metadata service.
Overall, Azure virtual machine scale sets let you create and manage a group of identical, load balanced VMs. It works as an entirety, it seems that we do not need to add the tags for the individual instances.
answered Nov 20 at 3:18
Nancy Xiong
2,100116
Feature request then: Support tags for individual machines in a Scaleset. In AWS for example, an instance in an auto scaling group is exactly the same as any other instance and can be referenced individually by it's instance ID. Additionally, as shown above, Azure itself has a unique "name" identifier for each instance in a Scaleset, why not just add this as it's resource identifier as well?
– J00MZ
Nov 21 at 4:22
1
Welcome to vote it, I have posted this feature request here.
– Nancy Xiong
Nov 21 at 5:26
add a comment |
up vote
1
down vote
accepted
It's impossible to individually tag instance in Azure VMSS as there is no resource type for VMSS instance, just for the type of Microsoft.Compute/virtualMachineScaleSets.
About the az resource tag command: az resource tag --tags vmlist=vm1 --id /subscriptions/{SubID}/resourceGroups/{ResourceGroup}/providers/xxxxxxx, the --id is used for using a resource identifier which is different from instance metadata service.
Overall, Azure virtual machine scale sets let you create and manage a group of identical, load balanced VMs. It works as an entirety, it seems that we do not need to add the tags for the individual instances.
answered Nov 20 at 3:18
Nancy Xiong
2,100116
Feature request then: Support tags for individual machines in a Scaleset. In AWS for example, an instance in an auto scaling group is exactly the same as any other instance and can be referenced individually by it's instance ID. Additionally, as shown above, Azure itself has a unique "name" identifier for each instance in a Scaleset, why not just add this as it's resource identifier as well?
– J00MZ
Nov 21 at 4:22
1
Welcome to vote it, I have posted this feature request here.
– Nancy Xiong
Nov 21 at 5:26
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
It's impossible to individually tag instance in Azure VMSS as there is no resource type for VMSS instance, just for the type of Microsoft.Compute/virtualMachineScaleSets.
About the az resource tag command: az resource tag --tags vmlist=vm1 --id /subscriptions/{SubID}/resourceGroups/{ResourceGroup}/providers/xxxxxxx, the --id is used for using a resource identifier which is different from instance metadata service.
Overall, Azure virtual machine scale sets let you create and manage a group of identical, load balanced VMs. It works as an entirety, it seems that we do not need to add the tags for the individual instances.
answered Nov 20 at 3:18
Nancy Xiong
2,100116
It's impossible to individually tag instance in Azure VMSS as there is no resource type for VMSS instance, just for the type of Microsoft.Compute/virtualMachineScaleSets.
About the az resource tag command: az resource tag --tags vmlist=vm1 --id /subscriptions/{SubID}/resourceGroups/{ResourceGroup}/providers/xxxxxxx, the --id is used for using a resource identifier which is different from instance metadata service.
Overall, Azure virtual machine scale sets let you create and manage a group of identical, load balanced VMs. It works as an entirety, it seems that we do not need to add the tags for the individual instances.
answered Nov 20 at 3:18
Nancy Xiong
2,100116
edited Nov 20 at 5:08
answered Nov 20 at 3:18
Nancy Xiong
2,100116
answered Nov 20 at 3:18
Nancy Xiong
2,100116
answered Nov 20 at 3:18
Nancy Xiong
2,100116
2,100116
Feature request then: Support tags for individual machines in a Scaleset. In AWS for example, an instance in an auto scaling group is exactly the same as any other instance and can be referenced individually by it's instance ID. Additionally, as shown above, Azure itself has a unique "name" identifier for each instance in a Scaleset, why not just add this as it's resource identifier as well?
– J00MZ
Nov 21 at 4:22
1
Welcome to vote it, I have posted this feature request here.
– Nancy Xiong
Nov 21 at 5:26
add a comment |
Feature request then: Support tags for individual machines in a Scaleset. In AWS for example, an instance in an auto scaling group is exactly the same as any other instance and can be referenced individually by it's instance ID. Additionally, as shown above, Azure itself has a unique "name" identifier for each instance in a Scaleset, why not just add this as it's resource identifier as well?
– J00MZ
Nov 21 at 4:22
1
Welcome to vote it, I have posted this feature request here.
– Nancy Xiong
Nov 21 at 5:26
Feature request then: Support tags for individual machines in a Scaleset. In AWS for example, an instance in an auto scaling group is exactly the same as any other instance and can be referenced individually by it's instance ID. Additionally, as shown above, Azure itself has a unique "name" identifier for each instance in a Scaleset, why not just add this as it's resource identifier as well?
– J00MZ
Nov 21 at 4:22
Feature request then: Support tags for individual machines in a Scaleset. In AWS for example, an instance in an auto scaling group is exactly the same as any other instance and can be referenced individually by it's instance ID. Additionally, as shown above, Azure itself has a unique "name" identifier for each instance in a Scaleset, why not just add this as it's resource identifier as well?
– J00MZ
Nov 21 at 4:22
1
1
Welcome to vote it, I have posted this feature request here.
– Nancy Xiong
Nov 21 at 5:26
Welcome to vote it, I have posted this feature request here.
– Nancy Xiong
Nov 21 at 5:26
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53370880%2findividually-tag-instance-in-azure-vmss%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
