Continuous scheduling for automated suspension and resumption of cloud resources

Patent metadata

Field	Value
Publication number	US-12081397-B2
Application number	US-202218059566-A
Country	US
Kind code	B2
Filing date	Nov 29, 2022
Priority date	Nov 29, 2022
Publication date	Sep 3, 2024
Grant date	Sep 3, 2024

Abstract

In some implementations, a scheduling system may receive a scheduling tag to define a custom schedule that includes one or more downtime windows for a cloud resource over a scheduling period. The scheduling system may determine a regular continuous schedule for the cloud resource that recurs over multiple scheduling periods based on the one or more downtime windows defined in the scheduling tag. The scheduling system may determine at a current scan time, whether a target state for the cloud resource is a running state or a suspended state based on the one or more uptime windows and the one or more downtime windows included in the regular continuous schedule. The scheduling system may align a current state of the cloud resource with the target state.

First claim

What is claimed is:

1. A system for automated suspension and resumption of cloud resources based on continuous scheduling, the system comprising:
one or more memories; and
one or more processors, coupled to the one or more memories, configured to:
receive a scheduling tag to define a custom schedule that includes at least one first window for a cloud resource over a scheduling period,
wherein the scheduling tag includes a value to express the at least one first window using a syntax that is compatible with an external metadata format supported by the cloud resource;

determine a regular continuous schedule for the cloud resource that recurs over multiple scheduling periods based on the at least one first window defined in the scheduling tag,
wherein the regular continuous schedule includes a plurality of windows including the at least one first window and at least one second window,
wherein the at least one second window covers time periods during the scheduling period that are not covered by the at least one first window,
wherein each of the plurality of windows has a corresponding target state for the cloud resource, each target state corresponding to one of uptime and downtime for the cloud resource;

determine, at a first scan time and within a target window of the plurality of windows, whether the cloud resource is in alignment with a target state for the cloud resource in accordance with the regular continuous schedule;
align, based at least in part on the determination at the first scan time, the cloud resource with the target state corresponding to the target window;
determine, at a second scan time after the first scan time and within the target window, whether the cloud resource is in alignment with the target state for the cloud resource corresponding to the target window; and
align, based at least in part on the determination at the second scan time, the cloud resource with the target state corresponding to the target window.

2. The system of claim 1 , wherein the target window comprises one or more uptime windows, and wherein the one or more processors, to align the cloud resource with the target state corresponding to the target window based at least in part on the determination at the scan time, are configured to:
determine that the target state for the cloud resource corresponding to the target window is a running state based on the second scan time being within the one or more uptime windows; and
resume the cloud resource based on determining, at the second scan time, that the cloud resource is in a suspended state.

3. The system of claim 1 , wherein the target window comprises one or more downtime windows, and wherein the one or more processors, to align the cloud resource with the target state corresponding to the target window based at least in part on the determination at the second scan time, are configured to:
determine that the target state for the cloud resource corresponding to the target window is a suspended state based on the second scan time being within the one or more downtime windows; and
suspend the cloud resource based on determining, at the second scan time, that the cloud resource is in a running state.

4. The system of claim 1 , wherein the one or more processors are configured to perform a point-in-time evaluation to determine the target state corresponding to the target window and align a current state of the cloud resource corresponding to the target window with the target state at periodic intervals.

5. The system of claim 1 , wherein the target window comprises one or more uptime windows, and wherein the value of the scheduling tag defines the one or more uptime windows according to a multi-day syntax that specifies a starting time and an ending time associated with multiple days, a single-day syntax that specifies a starting time and an ending time associated with a single day, or an overnight syntax that specifies a starting time on a first day and an ending time on a second day.

6. The system of claim 1 , wherein the one or more processors are further configured to:
receive an override to define a scheduled state for the cloud resource corresponding to the target window that takes precedence over the target state associated with the regular continuous schedule during a temporary time window specified in the override; and
align a current state of the cloud resource corresponding to the target window with the scheduled state defined in the override during the temporary time window specified in the override.

7. The system of claim 6 , wherein the override is a global override applicable to all cloud resources in a cloud infrastructure that includes the cloud resource.

8. The system of claim 6 , wherein the override is a resource-specific override applicable to only the cloud resource associated with the override.

9. The system of claim 1 , wherein the one or more processors are further configured to:
adjust the regular continuous schedule to include a buffer period that is associated with a running state of the cloud resource corresponding to the target window.

10. The system of claim 9 , wherein the buffer period has a duration that is based on an estimated time required for the cloud resource corresponding to the target window to start up.

11. A method for continuous scheduling for cloud resources, comprising:
receiving, by a scheduling system, a scheduling tag to define a custom schedule that includes at least one first window for a cloud resource over a scheduling period,
wherein the scheduling tag includes a key indicating that the scheduling tag defines one or more downtime windows;

determining, by the scheduling system, a regular continuous schedule for the cloud resource that recurs over multiple scheduling periods based on the one or more downtime windows defined in the scheduling tag,
wherein the regular continuous schedule includes a plurality of windows including the at least one first window and at least one second window,
wherein the at least one second window covers time periods during the scheduling period that are not covered by the at least one first window,
wherein each of the pluarity of windows has a corresponding target state for the cloud resource, each target state corresponding to one of uptime and downtime for the cloud resource;

determining, by the scheduling system, at a first scan time and within a target window of the pluarity of windows, whether the cloud resource is in alignment with a target state for the cloud resource corresponding to the target window in accordance with the regular continuous schedule;
aligning, by the scheduling system and based at least in part on the determination at the first scan time, the cloud resource with the target state corresponding to the target window;
determining, by the scheduling system and at a second scan time after the first scan time and within the target window, whether the cloud resource is in alignment with the target state for the cloud resource corresponding to the target window; and
aligning, by the scheduling system and based at least in part on the determination at the second scan time, the cloud resource with the target state corresponding to the target window, wherein aligning the cloud resource with the target state comprises:
resuming the cloud resource corresponding to the target window based on determining, at the second scan time, that the cloud resource is in a suspended state and that the target state for the cloud resource corresponding to the target window is a running state;
suspending the cloud resource corresponding to the target window based on determining, at the second scan time, that the cloud resource is in the running st

Assignees

• Capital One Services Llc

Inventors

• Mottley Clayton
• Tramblian Loreeg
• Mayes Cameron
• Maxwell Amy Ann
• Ho Kevin
• Graham Torrance
• Wright Robert

Classifications

• H04L41/0886

  Fully automatic configuration · CPC title

• H04L41/0816 Primary

  the condition being an adaptation, e.g. in response to network events · CPC title