stoney cloud: Notification Architecture: Difference between revisions
Jump to navigation
Jump to search
(Created page with "= Overview == = Requirements = Each service needs a notification entry in the form of: dn: ou=notifications,uid=<RESELLER>,ou=reseller,ou=configuration,ou=<SERVICE>,ou=servi...") |
No edit summary |
||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
The pages describes the notification architecture. | |||
= Requirements = | = Requirements = | ||
Revision as of 09:46, 8 November 2013
Overview
The pages describes the notification architecture.
Requirements
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
The following example shows the backup service 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 objectclass: organizationalUnit objectclass: sstNotificationObjectClass ou: notifications description: The sub tree stores the notification information for the (online) backup service for the reseller Reseller Ltd. with the uid 4000000. This information is used independently of the notification settings of the users. sstMailTo: Support stepping stone GmbH <support@stepping-stone.ch> sstNotificationWarning: quota sstNotificationWarning: schedule sstNotificationWarning: unsuccessful