A schedule allows
operations, such as configuration import/export or tech support collection, to
occur during one or more specified windows of time.
A schedule contains
a set of time windows (occurrences). These windows can be one time only or can
recur at a specified time and day each week. The options defined in the window,
such as the duration or the maximum number of tasks to be run, determine when a
scheduled task will execute. For example, if a change cannot be deployed during
a given maintenance window because the maximum duration or number of tasks has
been reached, that deployment is carried over to the next maintenance window.
Each schedule checks
periodically to see whether the APIC has entered one or more maintenance
windows. If it has, the schedule executes the deployments that are eligible
according to the constraints specified in the maintenance policy.
A schedule contains
one or more occurrences, which determine the maintenance windows associated
with that schedule. An occurrence can be one of the following:
-
Absolute (One
Time) Window—An absolute window defines a schedule that will occur only once.
This window continues until the maximum duration of the window or the maximum
number of tasks that can be run in the window has been reached.
-
Recurring
Window—A recurring window defines a repeating schedule. This window continues
until the maximum number of tasks or the end of the day specified in the window
has been reached.