Table of Contents
Services management
Introduction
This features aims to have a better management of services provided by Hosts (mail, samba, funambol…).
Requirements
- An host can have more than one service.
- An host with a service can have additonnals properties.
- A domain can inherit services from his associated hosts.
- A domain can inherit 0 or more services from his associated hosts.
- A domain which have inherit a service from a host can have additionals properties.
- A user can inherit services from his domain.
- A user which have inherit a service from a domain can have additionals properties
- A user can inherit 0 or more services from his associated hosts.
- Any properties can be :
- A text [with validation expression]
- A ENUM
- A link to an entity
- A link to an entity with a defined service
- Properties added to an host by a service are defined by the service
- Properties added to an domain by an inherited service are not the same than those of the host
- Properties added to an user by an inherited service are not the same than those of the domain
Technical specifications
When creating an Host, the application will look into the ServiceHost table to see which service are available for an host. A combobox (or checkbox?) will be added to add service to an host. When added a js function will automaticly add to the form all properties listed into ServicePropertyHost. The widget property will be defined by the serviceproperty_type. Each type will have a template. A specific type will be a foreign key to an obm entity (for exemple when a domain have the imap service, a property will be the imap servers linked to this domain).
The same method will be used for the domain and user creation.
The fact that a user cannot have the mail service if the domain doesn't have the mail service will be hardcoded. The database schema doesn't currently support this kind of limitation.
Initial Services
Here is some services :
* Host
- IMAP
- SMTP-IN
- SMTP-OUT
- PDC (SAMBA)
- OBM-SYNC
- external url
- external prefix
- external protocol
- Funis
- LDAP
* Domain
- Mail
- IMAP Servers
- SMTP-IN Servers
- SMTP-OUT Servers
- Samba
- SID
* User
- Mail (only if the domain have the domain have the mail service)
- quota
- IMAP server
- Samba (only if the domain have the domain have the samba service)
- home directory
- home drive
- logon script
This is not an exhaustive list
Validate
- Mehdi : Ok
- Anthony : -
- Pierre : OK. User need tests. email kep in User
- Thomas : -
- Raphael : Some data like Service or ServiceProperties can be hardcoded, and not in the database schema
Service description
Backup service
OBM 2.4
Service :
| Service name | Associated entity |
|---|---|
| backup | domain entity |
| backup_ftp | host entity. Need to run FTP service |
ServiceProperty :
| serviceproperty_service | serviceproperty_property | serviceproperty_entity_id | serviceproperty_value |
|---|---|---|---|
| backup | backup_ftp | Domain entity ID | Host ID |
| backup_ftp | login | Host entity ID | login |
| backup_ftp | password | Host entity ID | password |
| backup_ftp | root | Host entity ID | FTP root default '/' |
Improvement
Better solution consist to :
- create backup service link to domain
- create ftp, service instead of backup_ftp, link to host
- declare host with ftp service enabled
- attach ftp service host enabled to domain, used by backup service
- properties login, password and root are linked to backup service
This solution need to allow domain administrator to update backup properties which are linked to Domain, without allowing domain administrator to update all of his domain properties.
