User Tools

Site Tools


menu:operate:compliance:schedules

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
menu:operate:compliance:schedules [2020/05/19 12:19]
pgels [Create a schedule]
menu:operate:compliance:schedules [2020/05/19 12:28] (current)
pgels [Edit a schedule]
Line 1: Line 1:
 +===== Policy Schedules =====
 +
 +Policy schedules allow you to check a policy for compliance on regular intervals. This can be once every few hours, days, specific days of the week or even the month. This is a feature that will be available from Compliance Phase 2.
 +
 +{{:​menu:​operate:​compliance:​compliance_schedules.png|}}
 +
 +At the main schedule page you will see the list of schedules that are currently in operation. A schedule with status 1 is active and enabled, a schedule with status 0 is inactive and disabled and will not be used when calculating a node's next schedule time. A schedule can be repeating, or non-repeating. A non-repeating schedule will automatically be disabled once its nodes have been scheduled. You can enable it back on again manually when you want to use the schedule again. ​
 +
 +At this form you can create, edit and delete schedules like in most other forms in NetYCE.
 +
 +==== Time interval ====
 +
 +A time interval determines the next interval for this schedule. Whenever a node is scheduled, it calculates the first date in the future that matches this interval. There are four different types:
 +
 +  * **Hour of day**: This schedule will be for every day, at certain hours of the day. You can specify multiple hours (separated by a comma, for example 16,20), and even ranges of hours (separated by a dash, for example 4-6). The first and last checkbox are shortcuts for 0:00 and 23:00 respectively. ​
 +  * **Every x days**: This schedule will take place every x days. Only one number is allowed, and you can set the schedule time for up to the whole hour.
 +  * **Day of week**: This will schedule based on the day of the week, denoted by its two-letter abbreviation:​ mo, tu, we, th, fr, sa and su. Commas to denote multiple days and dashes to denote ranges are also supported. First and last are shortcuts for monday and sunday respectively. You can also set the schedule time for up to the whole hour.
 +  * **Day of month**: This will schedule based on the day of the month, from 1 to 31, where non-existing days like February 30th will be ignored. Commas to denote multiple days and dashes to denote ranges are also supported. First is a shortcut for the first day of the month, and last for the last, depending on what month it is. You can also set the schedule time for up to the whole hour.
 +
 +==== Create a schedule ====
 +
 +{{:​menu:​operate:​compliance:​policy_schedule_create.png|}}
 +
 +A policy schedule takes one policy. You can select it in the grid. A policy can only have one schedule, so the next time you open this form, that policy won't be among the selections anymore.
 +
 +In this form you can also edit the time interval, and set if the schedule should be enabled or repeating. A schedule that is not enabled will not be used in calculating the policy'​s next schedule time. A repeating schedule will be scheduled over and over again. A non-repeating schedule will be disabled after being scheduled.
 +
 +When you submit this form and the schedule is enabled, a flag is set. The nccmd daemon will pick up this flag, and schedule all of the policy'​s nodes (as designated by its node groups) to the next schedule time. 
 +
 +==== Edit a schedule ====
 +
 +{{:​menu:​operate:​compliance:​policy_schedules_edit.png|}}
 +Editing a schedule works the same as with creating one, only that you can't change the policy. If you want to change the policy: create a new schedule. ​
 +
 +In this form you can edit the time interval, and set if the schedule should be enabled or repeating. A schedule that is not enabled will not be used in calculating the policy'​s next schedule time. A repeating schedule will be scheduled over and over again. A non-repeating schedule will be disabled after being scheduled.
 +
 +When you change the time interval and the schedule is enabled, a flag is set. (Note that this only happens if you change the time interval or enable the schedule, so you won't have to worry if you simply open and close the form). The nccmd daemon will pick up this flag, and schedule all of the policy'​s nodes (as designated by its node groups) to the next schedule time. 
  
menu/operate/compliance/schedules.txt ยท Last modified: 2020/05/19 12:28 by pgels