add user facing doc for power scheduler #425
Conversation
| | `ditd-rds-530a-930p` | 05:30 | 21:30 (Mon-Thu), 23:59 (Fri) | mon-fri | DITD preferred RDS window | | ||
| | `ditd-win-patch-7a-7p` | 07:00 (23:30 mon after second tues) | 18:59 | mon-fri | weekday 7a-7p + Start at 23:30 on first monday after seecond tuesday for patching | |
There was a problem hiding this comment.
Schedules may be used by any resource. I don't believe we need rds or win-patch in there.
I really do not want hundreds of custom schedules. Why can't weekday-7a-7p work for the ditd-win-patch?
There was a problem hiding this comment.
Where's their justification for this (and expected duration)? Why cannot the existing schedules work for them?
There was a problem hiding this comment.
they specifically requested to power on windows instances for their patch slot on the monday after the second tuesday at 11:30pm, as their patch slot is Tuesday 12a - 6a.
There was a problem hiding this comment.
they specifically requested to power on windows instances for their patch slot on the monday after the second tuesday at 11:30pm, as their patch slot is Tuesday 12a - 6a.
We need to document these justifications with an eye towards standardized schedules. This is a what, not a why.
There was a problem hiding this comment.
they specifically requested to power on windows instances for their patch slot on the monday after the second tuesday at 11:30pm, as their patch slot is Tuesday 12a - 6a.
We need to document these justifications with an eye towards standardized schedules. This is a what, not a why.
Don: How about having customers who want a custom schedule to be required to submit a ticket through Service Now with a Business Justification and approval routing process before it gets implemented? That way there's an option for the customer to request one but that it doesn't guarantee automatic implementation of the request.
adds documentation for users whom want to schedule resources