It would be helpful if the start and stop process were able to handle two additional situations for servers:
- Starting a server without stopping it. In some cases, the server is best stopped by the team using it, and they may have circumstances where they don't need it stopped, but they always want it started if it was stopped
- Being able to have the stop time occur after midnight. Currently, no matter when you start a server it must stop at 11pm at the latest. A workaround is to fiddle with the timezone, but that's fairly confusing for other team coming along and very likely to result in human error. We have customers who support teams across multiple timezones, and servers often start at 9 or 10 in the morning, and turn off at 2 or 3 am, the next day. Because we must have a stop timer, and that must be before midnight, we cannot use the scale feature to adjust sizing and disk.
Comments (3 comments)