Changes
/* Maintenance Unit Example */
sstServicePriority: 3
sstServiceAutomated: TRUE
sstCronRepeatType: monthly # repeat type is monthly
sstCronInterval: 1 # repeat every month
| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:none;padding:0.097cm;"| <center></center>
| style="border-top:none;border-bottom:0.002cm solid #000000;border-left:0.002cm solid #000000;border-right:0.002cm solid #000000;padding:0.097cm;"| The maintenance service level. The possible maintenance service levels:
* <code>3</code>: Maintenance P3 [per Unit]: The Security Advisories will be installed once a month at the desired moment during the working hours (Mo. - Fr. Monday to Friday from 09:00 - 12:00 and 13:00 - 17:00).* <code>2</code>: Maintenance P2 [per Unit]: The Security Advisories will be installed once a month at the desired moment during the extended working hours (Mo. - Fr. Monday to Friday from 07:00 - 12:00 and 13:00 - 19:00).* <code>1</code>: Maintenance P1 [per Unit]: The Security Advisories will be installed once a month at the desired moment around the clock (Mo. - Su. Monday to Sunday from 00:00 - 24:00).
For more information on these maintenance service levels, visit stepping stone GmbH [http://www.stepping-stone.ch/infrastructure-as-a-service/maintenance/ web page].
If the attribute <code>sstServiceAutomated</code> is set to <code>TRUE</code>, the <code>sstServicePriority</code> will be ignored. And we will have automated maintenance windows in the form of:
* Maintenance Automated (vcs_gitlab) [per Unit]: The Security Advisories will be installed once a month at the desired moment around the clock (Monday to Sunday from 00:00 - 24:00).
|-
If the attribute <code>sstServiceAutomated</code> does not exist, presume <code>FALSE</code>.
|-
