CLOUD SCHEDULER
The present disclosure is related to devices, systems, and methods for a cloud scheduler. An example method can include receiving a schedule associated with an automation task to be performed in a virtualized environment via a REST API, wherein the task is associated with a target, associating the schedule with a partition, storing the schedule in a cache store responsive to determining that the schedule is to be invoked within a threshold time period, and receiving the schedule from the cache store and invoking the target responsive to the schedule becoming overdue.
1 . A method, comprising:
receiving a schedule associated with an automation task to be performed in a virtualized environment via a REST API, wherein the task is associated with a target;
associating the schedule with a partition;
storing the schedule in a cache store responsive to determining that the schedule is to be invoked within a threshold time period; and
receiving the schedule from the cache store and invoking the target responsive to the schedule becoming overdue.
2 . The method of claim 1 , wherein the target is a hypertext transfer protocol (HTTP) endpoint.
3 . The method of claim 1 , wherein the partition is a hash-key configured to be associated with a plurality of schedules.
4 . The method of claim 1 , wherein the method includes updating a configuration store with a result of the invocation of the target.
5 . The method of claim 4 , wherein the method includes updating the configuration store with a next invocation time associated with the target according to the schedule.
6 . The method of claim 1 , wherein the method includes re-invoking the target, according to a strategy defined in a configuration of the schedule, responsive to a failure to invoke the target.
7 . The method of claim 1 , wherein the method includes receiving, via the REST API:
a name of the schedule;
a description of the schedule;
a cron expression associated with the schedule; and
an expiration time of the schedule.
8 . A non-transitory machine-readable medium having instructions stored thereon which, when executed by a processor, cause the processor to:
receive a schedule associated with an automation task to be performed in a virtualized environment via a REST API, wherein the task is associated with a target;
associate the schedule with a partition;
store the schedule in a cache store responsive to determining that the schedule is to be invoked within a threshold time period; and
receive the schedule from the cache store and invoke the target responsive to the schedule becoming overdue.
9 . The medium of claim 8 , wherein the target is a hypertext transfer protocol (HTTP) endpoint.
10 . The medium of claim 8 , wherein the partition is a hash-key configured to be associated with a plurality of schedules.
11 . The medium of claim 8 , including instructions to update a configuration store with a result of the invocation of the target.
12 . The medium of claim 11 , including instructions to update the configuration store with a next invocation time associated with the target according to the schedule.
13 . The medium of claim 8 , including instructions to re-invoke the target, according to a strategy defined in a configuration of the schedule, responsive to a failure to invoke the target.
14 . The medium of claim 8 , including instructions to receive, via the REST API:
a name of the schedule;
a description of the schedule;
a cron expression associated with the schedule; and
an expiration time of the schedule.
15 . A system, comprising:
an API engine configured to receive a schedule associated with an automation task to be performed in a virtualized environment via a REST API, wherein the task is associated with a target;
a partition engine configured to associate the schedule with a partition;
a store engine configured to store the schedule in a cache store responsive to determining that the schedule is to be invoked within a threshold time period; and
an invocation engine configured to receive the schedule from the cache store and invoke the target responsive to the schedule becoming overdue.
16 . The system of claim 15 , wherein the target is a hypertext transfer protocol (HTTP) endpoint.
17 . The system of claim 15 , wherein the partition is a hash-key configured to be associated with a plurality of schedules.
18 . The system of claim 15 , wherein the invocation engine is configured to update a configuration store with a result of the invocation of the target.
19 . The system of claim 18 , wherein the invocation engine is configured to update the configuration store with a next invocation time associated with the target according to the schedule.
20 . The system of claim 15 , wherein the invocation engine is configured to re-invoke the target, according to a strategy defined in a configuration of the schedule, responsive to a failure to invoke the target.