Changes

= 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

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

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

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

=== Maintenance - Configuration - OpenStack projects ===

The sub tree for the OpenStack projects specific monitoring service settings:

dn: ou=projects,ou=configuration,ou=monitoring,ou=services,dc=stoney-cloud,dc=org

objectclass: top

ou: projects

description: The sub tree for the OpenStack projects specific monitoring service settings.

The sub tree for the specific monitoring service settings for the OpenStack project Customer Ltd. - Public Systems with the uid 4100001.

dn: uid=4100001,ou=projects,ou=configuration,ou=monitoring,ou=services,dc=stoney-cloud,dc=org

objectclass: top

sstBelongsToResellerUID: 4000000

sstBelongsToCustomerUID: 4000001

The following table describes the different attributes:

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,uid=4000001,ou=projects,ou=configuration,ou=monitoring,ou=services,dc=stoney-cloud,dc=org

objectclass: top

sstBelongsToResellerUID: 4000000

sstBelongsToCustomerUID: 4000001

The following table describes the different attributes:

=== 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

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

sstIsActive: TRUE

sstIsDefault: TRUE

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

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:

== 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

ou: units

description: The sub tree for the units of the monitoring service.

=== Maintenance - Units example ===

In the example below, the service UID <code>sstBelongsToServiceUID: 1234567</code> points to [[stoney_conductor:_OpenLDAP_directory_data_organisation#Virtual_Machine | virtual machine]] with the <code>b543f88f-dffe-426f-86d3-c7ff85c16d2a</code> and the <code>uid: 1234567</code>.

dn: uid=4000003,ou=units,ou=monitoring,ou=services,dc=stoney-cloud,dc=org

objectclass: top

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

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

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

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

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

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

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

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

sstCronHour: 9 # 9 am

sstCronDuration: 60 # 60 minutes (one hour)

The following table describes the different attributes: