Changes

Jump to: navigation, search

stoney cloud: Notification Architecture

942 bytes added, 08:04, 5 December 2013
/* OpenLDAP directory */
Each service needs a notification entry in the form of:
dn: ou=notifications,uid=<RESELLER>,ou=reseller,ou=configuration,ou=<SERVICE>,ou=services,dc=stoney-cloud,dc=org
and a settings entry in the form of:
dn: ou=settings,uid=<RESELLER>,ou=reseller,ou=configuration,ou=<SERVICE>,ou=services,dc=stoney-cloud,dc=org
The following example shows the backup service notification entry for the reseller with the uid 4000000:
dn: ou=notifications,uid=4000000,ou=reseller,ou=configuration,ou=backup,ou=services,dc=stoney-cloud,dc=org
objectclass: top
** backup schedule
** backup unseccessful
 
The following example shows the backup service settings entry for the reseller with the uid 4000000:
<pre>
dn: ou=settings,uid=2000000,ou=reseller,ou=configuration,ou=backup,ou=services,o=stepping-stone,c=ch
description: This sub tree stores the information about what can be modified in which scope.
objectclass: top
objectclass: organizationalUnit
objectclass: sstServiceSettingsObjectClass
ou: settings
preferredlanguage: de-CH
sstmailfrom: Support stepping stone GmbH <support@stepping-stone.ch>
sstnotificationwarningmediumadd: TRUE
sstnotificationwarningmediumchange: FALSE
sstquotachange: TRUE
sstsendcredentialsto: login
sstvolumecapacitydefault: 1073741824
sstvolumecapacitymax: 536870912000
sstvolumecapacitymin: 1073741824
sstvolumecapacitystep: 1073741824
</pre>
= Source Code =
486
edits