Documentation #457
open
Documentation #63: Admin Documentation
Document Machine<->Services Associations
10%
Description
Pilou suggested using a table to know which machine performs which service (and optionally which services are lost when a machine is down).
As it could bring a lot of lines for the many services, I suggest using categories an subcategories, like:- Mail
- MTA
- Mailing-Lists
- MailSync (Fetchmail)
- MailRetrieval (IMAP/POP/Webmail)
- MailFiltering (antivirus/antispam)
- MailManipulation (SIEVE/Procmail?)
When the need for details arrise, the cell could have the role name. For example, Orfeo would have for MTA the role MX1, while Toushirou would have _MX2, and so on. It could be interesting to find a way to have both a view of roles and of software names to implement them.
The service list in the user wiki can be used as a source to build this documentation.
It should also specify if the service is under a Configuration Management system.
Updated by Marc Dequènes over 6 years ago
- Assignee set to Marc Dequènes
- Branch set to hosts_services_457
I added a graphviz view using simplified service names, without all the detail of the machinery. I think this is sufficient to find which services are affected by a machine outage, or which hosts contributes to the service.
I also added major services dependencies (using dashed lines), meaning the whole or a complete part of the service (due to visual aggregation to simplify the view) would be unusable if the dependency is down.
This does not address the whole ticket but I think it could be useful and could give the users a basic understanding of the infrastructure.
Updated by Marc Dequènes over 4 years ago
- % Done changed from 0 to 10
I updated the services on the graph, and the labels too. I also combined several services that are shared between Orfeo and Toushirou to get an easier to read visual.