On 27.06.2014 17:30, Miloslav Trmač wrote:
2014-06-27 17:25 GMT+02:00 Stephen Gallagher <sgallagh(a)redhat.com
<mailto:sgallagh@redhat.com>>:
On 06/26/2014 02:59 PM, Miloslav Trmač wrote:
> Hello, 2014-06-19 16:43 GMT+02:00 Stephen Gallagher
> <sgallagh(a)redhat.com <mailto:sgallagh@redhat.com>
<mailto:sgallagh@redhat.com <mailto:sgallagh@redhat.com>>>:
>
> Please see the design page I've written at
>
https://fedorahosted.org/rolekit/wiki/Design/RolePackaging and
> comment on it here.
>
> The targets are named fedora-*, but the directory is
> /etc/server-role (no fedora); should this be consistent?
My intention there was to make the design non-fedora-specific, but
make it clear that the roles we're installing are clearly for Fedora
and probably won't work on other platforms without modification.
Makes sense.
I've also been toying with the idea that we should require roles to
include a journald messageid specific to the role, to make it easier
to track the logs all the way through. This won't be an F21 target, as
I need to talk to the journald devs about whether there's any way to
get journald to add a messageid automatically to messages generated by
any descendent of a unit (or just track them all the way through). I
suspect this isn't available today.
We don’t strictly need that: the role API gives anyone the set of
relevant units, and we can ask for all journal messages associated with
an unit (which, true, wouldn’t be exactly instantaneous). (Using the
same messageid for many different kinds of messages just to record an
association seems like kind of an abuse of the concept :) )
Yes, just to confirm, that's what we would do in Cockpit.
The only hurdle here is that roles like IPA don't (yet) allow us to
detect which units belong to their role. I believe Simo said it was
possible to remedy that somehow?
Stef