Difference between revisions of "stoney monitoring: OpenLDAP directory data organisation"
From stoney cloud
| [checked revision] | [checked revision] |
(→Maintenance - Configuration - Customers) |
(→Maintenance - Configuration - OpenStack projects) |
||
| Line 44: | Line 44: | ||
description: The sub tree for the customer specific monitoring service settings. | description: The sub tree for the customer specific monitoring service settings. | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=== Maintenance - Configuration - Service (Puppet) roles === | === Maintenance - Configuration - Service (Puppet) roles === | ||
Revision as of 20:45, 18 January 2024
Contents
Abstract
This document describes the OpenLDAP directory data organisation for the stoney monitoring service.
Data Organisation
The following chapters explain the data organisation of the stoney cloud OpenLDAP directory, in this case we looking at the stoney monitoring service.
Maintenance
The following LDIF shows the monitoring entry of the whole OpenLDAP directory tree for the stoney cloud:
dn: ou=monitoring,ou=services,dc=stoney-cloud,dc=org objectclass: top objectclass: organizationalUnit ou: monitoring description: The sub tree for the monitoring (configuration management) service.
Maintenance - Configuration
The sub tree for the configuration of the monitoring service:
dn: ou=configuration,ou=monitoring,ou=services,dc=stoney-cloud,dc=org objectclass: top objectclass: organizationalUnit ou: configuration description: The sub tree for the configuration of the monitoring service.
Maintenance - Configuration - Reseller
The sub tree for the reseller specific monitoring service settings:
dn: ou=reseller,ou=configuration,ou=monitoring,ou=services,dc=stoney-cloud,dc=org objectclass: top objectclass: organizationalUnit ou: reseller description: The sub tree for the reseller specific monitoring service settings.
Maintenance - Configuration - Customers
The sub tree for the customers specific monitoring service settings:
dn: ou=customers,ou=configuration,ou=monitoring,ou=services,dc=stoney-cloud,dc=org objectclass: top objectclass: organizationalUnit ou: customer description: The sub tree for the customer specific monitoring service settings.
Maintenance - Configuration - Service (Puppet) roles
The sub tree for the service (Puppet) roles specific monitoring service settings:
dn: ou=roles,ou=configuration,ou=monitoring,ou=services,dc=stoney-cloud,dc=org objectclass: top objectclass: organizationalUnit ou: roles description: The sub tree for the service (Puppet) roles specific monitoring service settings.
The sub tree of the specific monitoring service settings for the stoney office service (Puppet) role called 'stoney_office' (Puppet roles don't contain spaces).
dn: ou=stoney_office,ou=roles,ou=configuration,ou=monitoring,ou=services,dc=stoney-cloud,dc=org objectclass: top objectclass: organizationalUnit objectclass: sstServiceConfigurationObjectClass ou: stoney_office description: The sub tree of the specific monitoring service settings for the stoney office service (Puppet) role called 'stoney_office'. sstIsActive: TRUE sstIsDefault: TRUE
The following table describes the different attributes:
| Attribute | Objectclass | |
|
Description |
| ou | organizationalUnit | |
|
The name of the service (Puppet) role.
For example: |
| description | organizationalUnit | |
|
The description of the leaf.
For example: |
| sstIsActive | sstServiceConfigurationObjectClass | |
|
Is the entry active? Either TRUE (yes) or FALSE (no).
The default value is |
| sstIsDefault | sstServiceConfigurationObjectClass | |
|
Contains the leaf a default entry? Either TRUE (yes) or FALSE (no).
If |
Legend:
- x: Mandatory in all cases.
Maintenance - Configuration - service (Puppet) roles - Defaults
This sub tree stores the default settings for the stoney monitoring service settings for the stoney office service (Puppet) role called 'stoney_office'.
The configuration below tells us the following:
- We have a monitoring window range (as
sstCronMinuteEndandsstCronHourEndare set). - The monitoring window is executed every 2nd Wednesday of every month.
- The monitoring windows can start a 03:00 and must end at 05:00 and takes half an hour (30 minutes).
- A reminder will be sent to 'Support stepping stone AG <support@stepping-stone.ch>'.
The lookup of the default settings for the stoney monitoring service is as follows:
- Service roles:
ou=defaults,ou=stoney_office,ou=roles,ou=configuration,ou=monitoring,ou=services,dc=stoney-cloud,dc=org. - OpenStack project:
ou=defaults,uid=4100000,ou=roles,ou=configuration,ou=monitoring,ou=services,dc=stoney-cloud,dc=org. - Customer:
ou=defaults,uid=4000001,ou=roles,ou=configuration,ou=monitoring,ou=services,dc=stoney-cloud,dc=org. - Reseller:
ou=defaults,uid=4000000,ou=reseller,ou=configuration,ou=monitoring,ou=services,dc=stoney-cloud,dc=org.
For example: If no monitoring values or only a subset of monitoring values are set by the provisioning api (or provisioning script), an missing values are first looked up in the service roles sub tree. If there are still missing values, the next lookup occurs in the OpenStack project subtree. Once again, if there are still missing values, the next lookup occurs in the customer sub tree. If there are still missing values, the final lookup occurs in the reseller sub tree. If there are still missing values, the provisioning api (or provisioning script) must inform the calling instance (this would normally be a human).
dn: ou=defaults,ou=stoney_office,ou=roles,ou=configuration,ou=monitoring,ou=services,dc=stoney-cloud,dc=org objectclass: top objectclass: organizationalUnit objectclass: sstMaintenanceDefaultsObjectClass objectclass: sstNotificationObjectClass objectclass: sstRelationship ou: defaults description: This sub tree stores the default settings for the stoney monitoring service settings for the stoney office service (Puppet) role called 'stoney_office'. Please be aware, that this is the production definition. The integration (test) definition is the same, except that the sstCronOccurrenceInMonth attribute is 1 instead of 2 (a week before). sstIsActive: TRUE # MAY: The default is always TRUE, otherwise why bother? sstServicePriority: 3 # MAY: We always set this, in case sstServiceAutomated is set to FALSE (as a fall-back position) sstServiceAutomated: TRUE # MAY: Depending on the reseller, we either have TRUE or FALSE. If sstServiceAutomated is not set, we presume FALSE sstCronRepeatType: monthly # MAY: repeat type is monthly sstCronInterval: 1 # MAY: repeat every month sstCronOccurrenceInMonth: 2 # MAY: second occurence sstCronDayOfWeek: 3 # MAY: Wednesday sstCronMinute: 0 # MAY: 0 Minutes past the hour sstCronMinuteEnd: 0 # MAY: 0 Minutes past the hour (new attribute, for if we have a range: 03:00 - 05:00) sstCronHour: 3 # MAY: 3 am sstCronHourEnd: 5 # MAY: 5 am (new attribute, for if we have a range: 03:00 - 05:00) sstCronDuration: 30 # MAY: 30 minutes (half an hour) sstNotificationWarning: reminder # MAY: We alway set this (Multi-valued attribute). sstInformPersonUID: 1000482 # MAY: Support stepping stone AG (support@stepping-stone.ch) sstResponsiblePersonUID: 1000482 # MAY: Support stepping stone AG (support@stepping-stone.ch) sstResponsibleDeputyPersonUID: 1000482 # MAY: Support stepping stone AG (support@stepping-stone.ch)
The following table describes the different attributes:
| Attribute | Objectclass | |
|
Description |
| description | sstMaintenanceDefaultsObjectClass | |
|
The description of the leaf. |
| sstIsActive | sstMaintenanceDefaultsObjectClass | |
|
Is the entry active? Either TRUE (yes) or FALSE (no).
|
| sstServicePriority | sstMaintenanceDefaultsObjectClass | |
|
The monitoring service level. The possible monitoring service levels (1, 2 or 3):
For more information on these monitoring service levels, visit stepping stone GmbH web page. If the attribute
|
| sstServiceAutomated | sstMaintenanceDefaultsObjectClass | |
|
A monitoring window is either executed automatically:
or manually:
If the attribute |
| sstCronRepeatType | sstMaintenanceDefaultsObjectClass | |
|
How often is a cron job to be repeated. Valid values are: daily, weekly, monthly, yearly.
|
| sstCronInterval | sstMaintenanceDefaultsObjectClass | |
|
The interval of a cron job. This attribute is dependant on the attribute sstCronRepeatType. Valid values are: 1 - 12. For example: 2 could be every two days, weeks, months or years (depending on the value of the attribute sstCronRepeatType.
|
| sstCronOccurrenceInMonth | sstMaintenanceDefaultsObjectClass | |
|
The occurence of the day in a month a cron job is to be executed. Valid values are: 1 - 4. For example: 3 would be the third occurence. If you use a value higher than 4, the calculation will fail in months, which only have 4 same days (for example February will never have 5 Mondays ...).
|
| sstCronDayOfWeek | sstMaintenanceDefaultsObjectClass | |
|
Day of week (0 - 6), where Sunday is 0. For example: 1, which means Monday.
|
| sstCronMinute | sstMaintenanceDefaultsObjectClass | |
|
The number of minutes past the hour that the monitoring window must start.
Valid values are: If the attribute |
| sstCronMinuteEnd | sstMaintenanceDefaultsObjectClass | |
|
The number of minutes past the hour that the monitoring window must end (minus the duration defined with attribute sstCronDuration>/code>). Valid values are: <code>0 - 59.
For example: If this attribute is set, it is interpreted as the end of a monitoring window minute range, while |
| sstCronHour | sstMaintenanceDefaultsObjectClass | |
|
The hour the monitoring window must start.
Valid values are: If the attribute |
| sstCronHourEnd | sstMaintenanceDefaultsObjectClass | |
|
The hour the monitoring window must end (minus the duration defined with attribute sstCronDuration>/code>).
- 23. For example: 9, which means 9 am, while 17 means 5 pm.
If this attribute is set, it is interpreted as the end of a monitoring window hour range, while |
| sstCronDuration | sstMaintenanceDefaultsObjectClass | |
|
The duration of the monitoring window in minutes. Valid values are: 15 - 1440 (15 minutes to 24 hours). For example: 60, which means 60 minutes (one hour).
|
| sstNotificationWarning | sstNotificationObjectClass | |
|
This multi-valued attribute will be used to turn single notifications on or off. Currently, the only allowed value is reminder. The value (name) corresponds with the template dn.
|
| sstInformPersonUID | sstRelationship | |
|
Stores the UID of the person to be informed if necessary. This UID can be used to look up the persons mail address, preferred language, name, surname or other information.
As this attribute is multi-valued, the lookups will continue, even if this attribute is set. |
| sstResponsiblePersonUID | sstRelationship | |
|
Stores the UID of the person who is responsible for the system or service. This UID can be used to look up the persons mail address, preferred language, name, surname or other information. |
| sstResponsibleDeputyPersonUID | sstRelationship | |
|
Stores the UID of the deputy of the person who is responsible for the system or service. This UID can be used to look up the persons mail address, preferred language, name, surname or other information. |
| sstBelongsToResellerUID | sstRelationship | |
|
Stores the reseller UID the leaf belongs to. A unique integer value with 7 digits or more. In the case of OpenStack Domains (resellers), the value of sstBelongsToResellerUID corresponds with the value of uid.
For example: For the service (Puppet) roles this attribute must not be set, as the content of this value must be taken from either the OpenStack project, the customer or the reseller. |
| sstBelongsToCustomerUID | sstRelationship | |
|
Stores the customer UID the leaf belongs to. A unique value with 7 digits or more, must correspond with the uid entry. Each reseller is also a customer in the LDAP directory. Therefore, the value of the attribute sstBelongsToCustomerUID should always be set to the customer UID, that reflects the reseller for the OpenStack Domains.
For example: For the service (Puppet) roles this attribute must not be set, as the content of this value must be taken from either the OpenStack project, the customer or the reseller. |
Legend:
- x: Mandatory in all cases.
Maintenance - Units
The sub tree for the units of the monitoring service:
dn: ou=units,ou=monitoring,ou=services,dc=stoney-cloud,dc=org objectclass: top objectclass: organizationalUnit ou: units description: The sub tree for the units of the monitoring service.
Maintenance - Units example
Each monitoring unit has its own leaf. A monthly monitoring window is the norm.
Maintenance window every month on the second Tuesday of the month between 09:30 and 10:30, starting on Tuesday, the 14th of April 2015.
The sstBelongsToServiceUID lookup is as follows:
- OpenStack unit (server):
ou=units,ou=openstack,ou=services,dc=stoney-cloud,dc=org. - Virtual Machine:
ou=virtual machines,ou=virtualization,ou=services,dc=stoney-cloud,dc=org. - vServer:
ou=vservers,ou=services,dc=stoney-cloud,dc=org. - Dedicated Server:
ou=dedicated servers,ou=services,dc=stoney-cloud,dc=org(not implemented yet). - External Server:
ou=external servers,ou=services,dc=stoney-cloud,dc=org(not implemented yet).
The idea is, that we presume, that most of the monitoring units belong to OpenStack units (servers) running on our OpenStack based stoney cloud installation.
In the example below, the service UID sstBelongsToServiceUID: 1234567 points to virtual machine with the b543f88f-dffe-426f-86d3-c7ff85c16d2a and the uid: 1234567.
dn: uid=4000003,ou=units,ou=monitoring,ou=services,dc=stoney-cloud,dc=org objectclass: top objectclass: sstMaintenanceObjectClass objectclass: sstRelationship uid: 4000003 description: The monitoring leaf for the virtual machine with the uid 1234567. sstIsActive: TRUE sstBillable: TRUE sstServicePriority: 3 sstServiceAutomated: TRUE sstCronRepeatType: monthly # repeat type is monthly sstCronInterval: 1 # repeat every month sstCronStartDate: 20150414 # starting on Tuesday, the 14th of April 2015 sstCronOccurrenceInMonth: 2 # second occurence sstCronDayOfWeek: 2 # Tuesday sstCronMinute: 30 # 30 Minutes past the hour sstCronHour: 9 # 9 am sstCronDuration: 60 # 60 minutes (one hour) sstInformPersonUID: 4000002 sstResponsiblePersonUID: 4000002 sstResponsibleDeputyPersonUID: 4000002 sstNotificationWarning: reminder sstIsMultiTenant: FALSE sstBelongsToServiceUID: 1234567 sstBelongsToResellerUID: 4000000 sstBelongsToCustomerUID: 4000001
Other possible monitoring windows range from daily monitoring windows to bi yearly monitoring windows. The following examples just show the relevant attributes.
Maintenance window every day between 09:30 and 10:30, starting on Monday, the 5th of January 2015.
sstCronRepeatType: daily # repeat type is daily sstCronInterval: 1 # repeated every day sstCronStartDate: 20150105 # starting on the fifth of January 2015 sstCronMinute: 30 # 30 Minutes past the hour sstCronHour: 9 # 9 am sstCronDuration: 60 # 60 minutes (one hour)
Maintenance window every second day between 09:30 and 10:30, starting on Monday, the 5th of January 2015.
sstCronRepeatType: daily # repeat type is daily sstCronInterval: 2 # repeat every second day sstCronStartDate: 20150105 # starting on the fifth of January 2015 sstCronMinute: 30 # 30 Minutes past the hour sstCronHour: 9 # 9 am sstCronDuration: 60 # 60 minutes (one hour)
Maintenance window every two weeks on Monday between 09:30 and 10:30, starting on Monday, the 13th of April 2015.
sstCronRepeatType: weekly # repeat type is weekly sstCronInterval: 2 # repeat every second week sstCronStartDate: 20150413 # starting on Monday, the 13th of April 2015 sstCronDayOfWeek: 1 # on Monday sstCronMinute: 30 # 30 Minutes past the hour sstCronHour: 9 # 9 am sstCronDuration: 60 # 60 minutes (one hour)
Maintenance window every six months on the 15. of the month between 09:30 and 10:30, starting on Wednesday, the 15th of April 2015.
sstCronRepeatType: monthly # repeat type is monthly sstCronInterval: 6 # repeat every six months sstCronStartDate: 20150415 # starting on Wednesday, the 15th of April 2015 sstCronDayOfMonth: 15 # on the 15th day of the month sstCronMinute: 30 # 30 Minutes past the hour sstCronHour: 9 # 9 am sstCronDuration: 60 # 60 minutes (one hour)
Maintenance window every six months on the third Monday of the month between 09:30 and 10:30, starting on Monday, the 20th of April 2015.
sstCronRepeatType: monthly # repeat type is monthly sstCronInterval: 6 # repeat every six months sstCronStartDate: 20150420 # starting on Monday, the 20th of April 2015 sstCronOccurrenceInMonth: 3 # third occurence sstCronDayOfWeek: 1 # Monday sstCronMinute: 30 # 30 Minutes past the hour sstCronHour: 9 # 9 am sstCronDuration: 60 # 60 minutes (one hour)
Maintenance window every year on the 15th of March between 09:30 and 10:30, starting on Wednesday, the 11th of March 2015.
sstCronRepeatType: yearly # repeat type is yearly sstCronInterval: 1 # repeat every year sstCronStartDate: 20150311 # starting on Wednesday, the 11th of March 2015 sstCronDayOfMonth: 11 # on the 11th day of the month sstCronMinute: 30 # 30 Minutes past the hour sstCronHour: 9 # 9 am sstCronDuration: 60 # 60 minutes (one hour)
Maintenance window every year on the third Monday of March between 09:30 and 10:30, starting on Monday, the 16th of March 2015.
sstCronRepeatType: yearly # repeat type is yearly sstCronInterval: 1 # repeat every year sstCronStartDate: 20150316 # starting on Monday, the 16th of March 2015 sstCronMonthOfyear: 3 # third month of the year sstCronOccurrenceInMonth: 3 # third occurence sstCronDayOfWeek: 1 # Monday sstCronMinute: 30 # 30 Minutes past the hour sstCronHour: 9 # 9 am sstCronDuration: 60 # 60 minutes (one hour)
Maintenance window every two years on the third Monday of March between 09:30 and 10:30, starting on Monday, the 16th of March 2015.
sstCronRepeatType: yearly # repeat type is yearly sstCronInterval: 2 # repeat every two years sstCronStartDate: 20150316 # starting on Monday, the 16th of March 2015 sstCronMonthOfyear: 3 # third month of the year sstCronOccurrenceInMonth: 3 # third occurence sstCronDayOfMonth: 1 # Monday sstCronMinute: 30 # 30 Minutes past the hour sstCronHour: 9 # 9 am sstCronDuration: 60 # 60 minutes (one hour)
The following table describes the different attributes:
| Attribute | Objectclass | |
|
Description |
| uid | sstMaintenanceObjectClass | |
|
A unique integer value with 7 digits or more. For example: 4000003.
|
| description | sstMaintenanceObjectClass | |
|
The description of the leaf. |
| sstIsActive | sstMaintenanceObjectClass | |
|
Is the entry active? Either TRUE (yes) or FALSE (no).
|
| sstBillable | sstRelationship | |
|
It the entry billable? Either TRUE (yes) or FALSE (no). All hierarchical levels must have sstBillable: TRUE to actually have an invoice generated and sent. If the attribute sstBillable doesn't exist, the default is TRUE. This way, we are forced to set a reseller, customer or product manually to sstBillable: FALSE if we want to avoid sending them an invoice.
|
| sstCancellationDate | sstRelationship | |
|
The cancellation date of a reseller, customer or service in the form of [YYYY][MM][DD] (ISO 8601). For example: 20201231.
The attribute |
| sstServicePriority | sstMaintenanceObjectClass | |
|
The monitoring service level. The possible monitoring service levels (1, 2 or 3):
For more information on these monitoring service levels, visit stepping stone GmbH web page. If the attribute
|
| sstServiceAutomated | sstMaintenanceObjectClass | |
|
A monitoring window is either executed automatically:
or manually:
If the attribute |
| sstCronRepeatType | sstMaintenanceObjectClass | |
|
How often is a cron job to be repeated. Valid values are: daily, weekly, monthly, yearly.
|
| sstCronInterval | sstMaintenanceObjectClass | |
|
The interval of a cron job. This attribute is dependant on the attribute sstCronRepeatType. Valid values are: 1 - 12. For example: 2 could be every two days, weeks, months or years (depending on the value of the attribute sstCronRepeatType.
|
| sstCronStartDate | sstMaintenanceObjectClass | |
|
The first time a cron job is executed. This date is stored in the form of [YYYY][MM][DD] (ISO 8601). For example: 2010314 (the 14th of March 2015).
|
| sstCronDuration | sstMaintenanceObjectClass | |
|
The duration of the monitoring window in minutes. Valid values are: 15 - 1440 (15 minutes to 24 hours). For example: 60, which means 60 minutes (one hour).
|
| sstCronMinute | sstMaintenanceObjectClass | |
|
The number of minutes past the hour that the monitoring window must start.
Valid values are: If the attribute |
| sstCronMinuteEnd | sstMaintenanceObjectClass | |
|
The number of minutes past the hour that the monitoring window must end (minus the duration defined with attribute sstCronDuration>/code>). Valid values are: <code>0 - 59.
For example: If this attribute is set, it is interpreted as the end of a monitoring window minute range, while |
| sstCronHour | sstMaintenanceObjectClass | |
|
The hour the monitoring window must start.
Valid values are: If the attribute |
| sstCronHourEnd | sstMaintenanceObjectClass | |
|
The hour the monitoring window must end (minus the duration defined with attribute sstCronDuration>/code>).
- 23. For example: 9, which means 9 am, while 17 means 5 pm.
If this attribute is set, it is interpreted as the end of a monitoring window hour range, while |
| sstCronDayOfWeek | sstMaintenanceObjectClass | |
|
Day of week (0 - 6), where Sunday is 0. For example: 1, which means Monday.
|
| sstCronDayOfMonth | sstMaintenanceObjectClass | |
|
The day of the month a cron job is to be executed. Valid values are: 1 - 31. For example: 3 is the third of the month.
|
| sstCronMonthOfyear | sstMaintenanceObjectClass | |
|
The month of the year a cron job is to be executed. Valid values are: 1 - 12. For example: 3 would be March.
|
| sstCronOccurrenceInMonth | sstMaintenanceObjectClass | |
|
The occurence of the day in a month a cron job is to be executed. Valid values are: 1 - 4. For example: 3 would be the third occurence. If you use a value higher than 4, the calculation will fail in months, which only have 4 same days (for example February will never have 5 Mondays ...).
|
| sstInformPersonUID | sstRelationship | |
|
Stores the UID of the person to be informed if necessary. This UID can be used to look up the persons mail address, preferred language, name, surname or other information. |
| sstResponsiblePersonUID | sstRelationship | |
|
Stores the UID of the person who is responsible for the system or service. This UID can be used to look up the persons mail address, preferred language, name, surname or other information. |
| sstResponsibleDeputyPersonUID | sstRelationship | |
|
Stores the UID of the deputy of the person who is responsible for the system or service. This UID can be used to look up the persons mail address, preferred language, name, surname or other information. |
| sstNotificationWarning | sstMaintenanceObjectClass | |
|
This multi-valued attribute will be used to turn single notifications on or off. Currently, the only allowed value is reminder. The value (name) corresponds with the template dn.
|
| sstIsMultiTenant | sstMaintenanceObjectClass | |
|
If this singe-valued attribute is set to TRUE, we know that this is a multi tenant capable system or service. For example stoney backup, stoney storage or stoney wiki). The monitoring notification system will therefore know, that it must inform the tenants differently. |
| sstBelongsToServiceUID | sstMaintenanceObjectClass | |
|
Stores the UID of the service the leaf belongs to. This UID can be used to look up other information. A unique value with 7 digits or more. 4000123.
|
| sstBelongsToResellerUID | sstRelationship | |
|
Stores the reseller UID the leaf belongs to. A unique value with 7 digits or more. For example: 4000000.
|
| sstBelongsToCustomerUID | sstRelationship | |
|
Stores the customer UID the leaf belongs to. A unique value with 7 digits or more. For example: 4000001.
|
Legend:
- x: Mandatory in all cases.
