Add Patch Window capability to traffic based autostopping
this fiscal quarter
D
Distinguished Unicorn
For traffic based autostopping at scale, we need all VM's to power onprior to their patch window and then shut down after patch window is complete. Currently, the only way to do this is to bulk disable the rules which is a cumbersome effort. This should be done in the rule itself so that the patching can occur.
Log In
Canny AI
Merged in a post:
Mass maintenance functionality for AutoStopping rules
A
Atomic Porpoise
Currently you can only modify AutoStopping rules on an individual basis, it would be great if Harness could add in functionality that would allow you to mass assign one time maintenance windows for uptime to accommodate things like patching, or other maintenance events that need to be run off hours where the servers need to be briefly online outside of the typical AutoStopping functionality.
IE. allow us to mass apply a one time maintenance window to multiple AS rules at once.
A
Abhijeet Sharma
this fiscal quarter
This is a planned item for Q3 FY25. With this, we will support APIs for bulk-update of AutoStopping rules in terms of:
- enable/disable
- toggle dry_run
- add/remove scheduled uptime/downtime to multiple AS-rules
D
Distinguished Unicorn
We would also want this for schedule based, as of right now it would require being on all, for instance, Saturdays versus just one Saturday per month
This post was marked as
in progress
I
Implicit Squirrel
Absolutely agree with these, we have a number of fixed rules, but then when events like maintenance are going on, we have to have temporary rules to turn things on at night, or over weekends, etc. so having a temporary one-time rule that automatically deleted a week after the event (just so you can see it was scheduled), would be great.