You can change the following parameter values specified during storage
cluster configuration after configuring the storage cluster. Note that parameters
other than the following cannot be changed.
-
controlNetworkAllowedIpv4AddCidrBlocks
-
computeNetworkAllowedIpv4AddCidrBlocks
-
computeNetworkAllowedIpv6AddCidrBlocks
-
billingCode
Note:
- The settings of the parameters
controlNetworkAllowedIpv4AddCidrBlocks,
computeNetworkAllowedIpv4AddCidrBlocks, and
computeNetworkAllowedIpv6AddCidrBlocks are reflected in the settings of the
Network Security Group.
- The setting of the billingCode parameter is reflected in the
billingCode tag assigned to each resource.
Precautions on procedures
-
In the following procedure, long command lines begin on a new
line delimited by "\".
-
Recording console outputs (for example, by using a script
command, redirecting operation, or the tee command) can help to confirm the
execution result or handle errors.
-
See Exporting the configuration file (Cloud for
Microsoft Azure) in the VSP One SDS Block and SDS Cloud System Administration to obtain configuration files for the
current configuration from VSP One SDS Block.
-
Connect to any environment in which the Linux jq and Azure CLI command
execution are available (Example: controller node and Cloud Shell).
-
Create a backup file of the parameter file.
cp VMConfigurationFile.parameters.json \
VMConfigurationFile.parameters_backup.json
-
In the configuration file you retrieved, check the current values of the
parameters whose settings you want to change.
Enter the name of the parameter to be changed in <parameter-name>.
jq '.parameters.<parameter-name>.value' \
VMConfigurationFile.parameters.json
-
For the parameter to be changed, rewrite the value of the parameter in the
configuration file with the following command.
Enter the new value in <new-setting-value>.
jq '.parameters.<parameter-name>.value = <new-setting-value>' \
VMConfigurationFile.parameters_backup.json > \
VMConfigurationFile.parameters.json
-
Execution example for changing the value of
controlNetworkAllowedIpv4AddCidrBlocks:
jq '.parameters.controlNetworkAllowedIpv4AddCidrBlocks.value = ["192.168.1.0/24","192.168.10.0/24"]' \
VMConfigurationFile.parameters_backup.json > \
VMConfigurationFile.parameters.json
-
Execution example when changing the value of
billingCode:
jq '.parameters.billingCode.value = "VSPOneSDSBlock2"' \
VMConfigurationFile.parameters_backup.json > \
VMConfigurationFile.parameters.json
-
Verify that the parameter value of the configuration file has been replaced
successfully.
jq '.parameters.<parameter-name>.value' \
VMConfigurationFile.parameters.json
-
Using the rewritten configuration file, execute the following command to
deploy.
az deployment group create \
--name mainTemplate \
--resource-group <storage-cluster-resource-group-name> \
--template-file VMConfigurationFile.json \
--parameters VMConfigurationFile.parameters.json
-
Verify the result of the deployment.
Verify that the CLI execution was successful. Alternatively, in
the Azure portal, go to the Deployments window of
storage cluster resource group to verify that deployment was successful.
-
(Only when changing the billingCode) Since the OS disk tag setting is not
changed in step 7, execute the following command.
az resource list --resource-type "Microsoft.Compute/disks" \
--resource-group <storage-cluster-resource-group-name> \
--query "[?tags.BillingCode!='<new-setting-value>'].id" \
--output tsv | \
xargs -I {} az resource tag --ids {} \
--tags "BillingCode=<new-setting-value>"
-
Execution example for changing the value of billingCode
az resource list --resource-type "Microsoft.Compute/disks" \
--resource-group ResourceGroupName \
--query "[?tags.BillingCode!='VSPOneSDSBlock2'].id" \
--output tsv | \
xargs -I {} az resource tag --ids {} \
--tags "BillingCode=VSPOneSDSBlock2"