Creating an Action Restriction Window

Document created by Michael Scott Expert on Jan 14, 2016Last modified by fran.schwarzmann on Aug 15, 2016
Version 3Show Document
  • View in full screen mode

For some clusters or groups of devices, you might want to automate actions, but only during off-peak hours. Operations Manager includes a scheduling utility that you can use to restrict actions to a time specific window for a given scope of devices. You can use this to allow or disallow automation for a given window of time.


NOTE: The Operations Manager Economic Scheduling Engine continually calculates actions that cause your environment to converge on the desired state. These actions are in response to the environment at a given point in time. When you restrict the automation of a given action to a certain time window, Operations Manager will only calculate and perform actions that are appropriate for the environment during that scheduled window. You should review manual actions during time periods when automation is restricted, so you can manually adjust the environment in response to peak states.


By default, the global settings for all actions have no restriction windows set for them. If you globally set the VM Move action to Automated, then VMTurbo Operations Manager will automatically execute any recommended VM move actions whenever they arise — 24 hours a day, 7 days a week. Action restriction widows modify this, for global policies or as overrides to global policies scoped to specific groups.

 

For example, assume you want to always automate Resize for all but the most critical VMs. You would set Resize VMs to Automated at a global level. Then for a critical cluster, you could set a restriction window that overrides the automation (sets Resize to Manual) during peak hours (9:00 to 5:00 M-F).

You can also restrict action modes in reverse fashion. For example, if you want to automate Resize for only one set of VMs, you can set Resize to Manual at the global level, and for one cluster schedule it to be Automated for a given time window.


NOTE: You can enforce non disruptive mode as a general policy, and then schedule action windows to automate resize actions during downtimes. Be aware that scheduled actions do not respect the enforced non disruptive mode — Scheduled resize actions will execute during the scheduled window even if they require a reboot. This is useful for setting up certain action behaviors, but you must be aware that enforced non disruptive mode has no effect on scheduled actions.


Creating a Simple Action Restriction Window

  To schedule a time window for an automated action:

  1. Set the scope for this action.image
  2. Click View Schedule to open the restrictions windows panel and then click New Action Restriction Window .You can select the window start date beforehand in the calendar, or set it as you create the policy.
  3. Specify the settings for this restriction window.The date range determines how many days the window will be “open”, or be in effect. You should keep the following points in mind:
    • A non-recurring window has a start date, and no end date. The window will be open for the day you specify as the start date, and finish at the end of that day.
    • For recurring windows you specify a date range. The window will open during times within that range.
    • For daily recurrence the window will be open for the hours you specify.
    • For weekly recurrence the window will be open on the days of the week that you specify, for the hours you specify.
    • For monthly recurrence, the window will open one day each month — on the day you set for the Start Date. But the window recurrence remains in effect until the End Date. For example, if you specify January 1st 2013 for the start date, and December 31st 2013 for the end date, the window will be open on the first day of each month for that year.

 

For any given day, the window can be in effect from 00:00 through 24:00. If you want an action mode to span two days, you must specify two restriction windows. For example, to enable automation from 22:00 to 06:00, you must create two windows; one from 22:00 to 24:00, and another from 0:00 to 06:00.Note that you can set different label colors for your restriction windows. This is a good way to track windows of a similar type. For example, you could use red for windows on critical clusters, and green for windows on prototyping clusters.image

4.  When you have the settings you want, click Create.The restriction window appears in the calendar. When you select a day in the calendar, the Action      Restriction Windows list shows all the items for that day. Hover over an item to display details in a tooltip.

 

       image

Tie-break Results

It’s possible that different restriction windows will affect the same resource instance. In that case the most conservative setting wins. The following list is from most conservative to most aggressive:

  • Disabled
  • Recommended
  • Manual
  • Automate
2 people found this helpful

Attachments

    Outcomes