Proposal: Implementation of Server Roles

[Stephen Gallagher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've finally gotten around to putting together my thoughts on how (at
a high level) the roles should be implemented. NOTE: this is
specifically about the Roles as a concept, not the implementation of
the logic within the roles, except for a couple restrictions I make on
input and output format.

Please see the design page I've written at
https://fedorahosted.org/rolekit/wiki/Design/RolePackaging and comment
on it here.

I will be the first to admit that the "First-Boot Configuration"
approach is a bit of a hack, but it's a hack that will work regardless
of installation during anaconda or a live system (it defers the
configuration step to a systemd unit that runs just prior to the first
start-up of the role). The implication here is strong: while the UI
that prepares the configuration may be interactive, the content fed
into rolekit is non-interactive.

Comments and clarifications requested.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlOi9v8ACgkQeiVVYja6o6NO+wCfXtPdDdb3nSkrooM+NCeoK4gw
JsUAn3j0jUtV8NDhAjuRzBaW2iF0A7LX
=7qj0
-----END PGP SIGNATURE-----