You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add rollout option to osconfig patch deployment
* Add test
* Set properties to required and correctly specify exactly one of
* Fix typos
Signed-off-by: Modular Magician <[email protected]>
Description: `Rollout strategy of the patch job.`,
861
+
MaxItems: 1,
862
+
Elem: &schema.Resource{
863
+
Schema: map[string]*schema.Schema{
864
+
"disruption_budget": {
865
+
Type: schema.TypeList,
866
+
Required: true,
867
+
ForceNew: true,
868
+
Description: `The maximum number (or percentage) of VMs per zone to disrupt at any given moment. The number of VMs calculated from multiplying the percentage by the total number of VMs in a zone is rounded up.
869
+
During patching, a VM is considered disrupted from the time the agent is notified to begin until patching has completed. This disruption time includes the time to complete reboot and any post-patch steps.
870
+
A VM contributes to the disruption budget if its patching operation fails either when applying the patches, running pre or post patch steps, or if it fails to respond with a success notification before timing out. VMs that are not running or do not have an active agent do not count toward this disruption budget.
871
+
For zone-by-zone rollouts, if the disruption budget in a zone is exceeded, the patch job stops, because continuing to the next zone requires completion of the patch process in the previous zone.
872
+
For example, if the disruption budget has a fixed value of 10, and 8 VMs fail to patch in the current zone, the patch job continues to patch 2 VMs at a time until the zone is completed. When that zone is completed successfully, patching begins with 10 VMs at a time in the next zone. If 10 VMs in the next zone fail to patch, the patch job stops.`,
@@ -320,6 +327,11 @@ The `group_labels` block supports:
320
327
Schedule recurring executions.
321
328
Structure is documented below.
322
329
330
+
*`rollout` -
331
+
(Optional)
332
+
Rollout strategy of the patch job.
333
+
Structure is documented below.
334
+
323
335
*`project` - (Optional) The ID of the project in which the resource belongs.
324
336
If it is not provided, the provider project is used.
325
337
@@ -733,6 +745,33 @@ The `week_day_of_month` block supports:
733
745
A day of the week.
734
746
Possible values are `MONDAY`, `TUESDAY`, `WEDNESDAY`, `THURSDAY`, `FRIDAY`, `SATURDAY`, and `SUNDAY`.
735
747
748
+
The `rollout` block supports:
749
+
750
+
*`mode` -
751
+
(Required)
752
+
Mode of the patch rollout.
753
+
Possible values are `ZONE_BY_ZONE` and `CONCURRENT_ZONES`.
754
+
755
+
*`disruption_budget` -
756
+
(Required)
757
+
The maximum number (or percentage) of VMs per zone to disrupt at any given moment. The number of VMs calculated from multiplying the percentage by the total number of VMs in a zone is rounded up.
758
+
During patching, a VM is considered disrupted from the time the agent is notified to begin until patching has completed. This disruption time includes the time to complete reboot and any post-patch steps.
759
+
A VM contributes to the disruption budget if its patching operation fails either when applying the patches, running pre or post patch steps, or if it fails to respond with a success notification before timing out. VMs that are not running or do not have an active agent do not count toward this disruption budget.
760
+
For zone-by-zone rollouts, if the disruption budget in a zone is exceeded, the patch job stops, because continuing to the next zone requires completion of the patch process in the previous zone.
761
+
For example, if the disruption budget has a fixed value of 10, and 8 VMs fail to patch in the current zone, the patch job continues to patch 2 VMs at a time until the zone is completed. When that zone is completed successfully, patching begins with 10 VMs at a time in the next zone. If 10 VMs in the next zone fail to patch, the patch job stops.
762
+
Structure is documented below.
763
+
764
+
765
+
The `disruption_budget` block supports:
766
+
767
+
*`fixed` -
768
+
(Optional)
769
+
Specifies a fixed value.
770
+
771
+
*`percentage` -
772
+
(Optional)
773
+
Specifies the relative value defined as a percentage, which will be multiplied by a reference value.
774
+
736
775
## Attributes Reference
737
776
738
777
In addition to the arguments listed above, the following computed attributes are exported:
0 commit comments