Sites
Sites are intended to describe geographical locations and facilities. Alternatively Sites can be used to define a Customer in a customer/supplier organizational model.
Site :
- has a unique short name (unique identifier)
- has a (nicer) display name , and an optional description
- has a list of scopes to notify in case a notification is targeted at the site (e.g. local users, escalation groups)
- can declare itself as member of groups of sites (sitegroups)
- is a scope in itself (can be used as a target for notifications)
- has a list of app for which the site wants to be notified (notify_apps)
- has a list of apps or services hosted/provided by the side
Nota: A user who has a site defined in his profile is not automatically added to the site scope.
Nota2: see apps for internal/external apps
Site Data Model
sites:
- name: site01
display: Site Number 1
description: Test Site01
#is_enabled: true
#delete: no
# sitegroups membership (can be declared also in sitegroups objects)
sitegroups:
- mygroup01
# notification for this site goes to scopes :
notify_to:
- user01
- u:user02
- user03
- g:usergroup01
- site:site02
- sg:sitegroup07
- app:app33
# external apps (notify the apps => notify this site)
notify_apps:
- app01
- appl02
- site03:shared_app_from_site03
# locally defined users
users:
- login: user0101
email: user0101@test.test
mobile: "0601020304"
name: Test User local site site01
description: A test user from site01
# locally hosted apps (will be named with site prefix site01:)
# if no prefix wanted for a global app, declare in apps: section
apps:
- name: app0101
- name: app0102
- name: app0103
Site Example
sites:
- name: clinic17
display: Private Hospital 17
sitegroups:
- hospital
notify_to:
- g:demo
Site Scope: site
Scope
site:clinic17
Alternate names:
s:clinic17
Scope usage
predefined_message:
- name: clinic17_outage
(...)
notify_to:
- site:clinic17
- user:joe