-
Notifications
You must be signed in to change notification settings - Fork 264
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.
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
Nightly period #12
Comments
For period 1 only specify the begin and no end time, that will work. |
Fantastic. It's true, I didn't try this solution before. Thank you! |
Too fine to be true. It does not works. SCHEDULEdescriptionString: Nightly-stop PERIODS:begintimeString: 19:00 descriptionString: Backup hours 2 LOG2018-03-09 - 11:00:16.434 - DEBUG : [ Instance EC2:i-xxxxxx (testserver) ] Anyone with suggestions is welcome! Thank you! |
Can you try this:
You can simulate and see your savings using the following period that shows the running hours/periods in a defined period.
|
I have the exact same issue. Two periods , one that stops at 02:00 (lets call it abc) and one that starts at 08:00 (lets call it xyz) So i assigned Schedule123 with periods {abc, xyz} but this doesnt work either. The state table for all tagged instances shows "any" state i really would like to get this fixed or a solution for this. |
In order configure this you need the following periods Tue-Sat, start 0:00, stop 2:00 A schedule containing these periods Starts at workdays at 8am and stops on the next day at 2am. Regards, |
Thanks for the reply, only issue with this is i have things running on these machines closer to 2am, if i run the proposed solution this will stop the instance at 23:59. If i am not mistaken? |
The latest maintenance release 2.2.2 that is on aws labs wil detect that there is an adjacent period at 0:00 and will keep the Instance running. |
amazing, thanks for that info. Will try that out and report back. edit this solution above worked. Thank you |
Closing due to time elapsed since last correspondence. Please re-open this if you are still having an issue. |
I have a similar situation. But here i don't want to mention the start or end time. I just want to mention the amount of time. Suppose if instance starts at 07:00 Hrs, it should be stopped after 2 Hours at 09:00 Hrs... or if it has started at 11:00 Hrs after 2 hours, it should stop at 13:00 Hrs. |
Hi to everyone.
I have some instances that must be up during night and stopped during the day.
For example, an instance that must start art 19.00 and stop at 10.00. I tried with:
begintime 19:00
endtime 10:00
It doesn't works, beginperiod must be lower than endtime
1st period
begintime 19:00
endtime 00:00
2nd period
begintime 00:00
endtime 10:00
Doesn't works too. Only the 2nd period is working, the 1st is ignored.
Maybe anyone has a solution?
Best regards,
The text was updated successfully, but these errors were encountered: