Skip to content

Add enableCrossZoneUpgrade and prioritizeUnhealthyInstances properties to RollingUpgradePolicy for VMSS #11184

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.

Sign up for GitHub

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

Merged
fengzhou-msft merged 5 commits into from
Nov 23, 2020
Merged

Add enableCrossZoneUpgrade and prioritizeUnhealthyInstances properties to RollingUpgradePolicy for VMSS #11184

Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
da11558
Adding new VMSS rolling upgrade properties, enableCrossZoneUpgrade an…
Oct 13, 2020
0289096
remove white spaces
Oct 14, 2020
d6d57fc
Merge pull request #2 from Azure/compute-2020-12
kimberlyyipc Nov 10, 2020
0080e80
modified description
Nov 11, 2020
8a9920d
update description
Nov 11, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions specification/compute/resource-manager/Microsoft.Compute/stable/2020-12-01/compute.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9154,6 +9154,14 @@
"pauseTimeBetweenBatches": {
"type": "string",
"description": "The wait time between completing the update for all virtual machines in one batch and starting the next batch. The time duration should be specified in ISO 8601 format. The default value is 0 seconds (PT0S)."
},
"enableCrossZoneUpgrade": {
"type": "boolean",
"description": "Enable rolling upgrade across multiple zones during UD walk within the limit of MaxBatchInstanceCount or BatchInstancePercent"
},
"prioritizeUnhealthyInstances": {
"type": "boolean",
"description": "Enable rolling upgrade to start with the batch which has most unhealthy VMs in percentage. If enableCrossZoneUpgrade is not enabled, the rolling upgrade will start from the most unhealthy availability zone,and within the zone, walk the UD that has the most unhealhty VMs first"
}
},
"description": "The configuration parameters used while performing a rolling upgrade."
Expand Down