On 07/09/2014 10:58 AM, Tollef Fog Heen wrote:
]] "Jóhann B. Guðmundsson"
On 07/09/2014 08:33 AM, Tollef Fog Heen wrote:
]] "Jóhann B. Guðmundsson"
If we manage to do that, introduce "rolefulfilment=" in units which we
would define those standardized predefined set of roles as in for
httpd.service we might have rolefulfilment=web server, for postgresql,
rolefulfilment=database server etc. so you could list/query etc the
machine primary role and at the same time list the daemon/service who
fulfills that role
It's not useful to know that a machine is a database server. It's
useful to know if it's a postgres server or a mysql server or an oracle
server, be it for monitoring or for connecting to it.
Yes it is and if you dont see the benefits of knowing the roles of
your machine or containers and using roles in your infrastructure I
cannot help you.
I know and use roles in my infrastructure, so that's not my question.
I'm objecting to the use of a predefined list of roles, since that will
not match my infrastructure,
Precisely it does not meet *your* particular needs.
and I'm wondering what the use case for a
very restricted list like that is.
An list of strictly defined roles is needed for proper integration with
wide variety of components and system policies ( think for example RBAC
here ) etc.
JBG
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
