Hello Stephen,
Stephen Gallagher [2018-08-21 16:01 -0400]:
* In general, the consensus was that there are two places in Server
Edition
that we should focus new features around Cockpit and Ansible. Anything we want
to declare a "Server Feature" should integrate with one or both of these. We
also would like to see Cockpit provide an Ansible-based "desired state
configuration" feature that would produce an Ansible playbook that would
replicate the current state of the system for any part of it that Cockpit
understands. (I will be writing up an RFE for Cockpit shortly).
This was discussed on and off at several occasions already. This does not work
in general, as for most pages (like NetworkManager, Logs, Storage, Software
Updates, containers and so on) there is no well-defined discernible "desired
state configuration".
However, some pages *do* have that, in particular Firewall and SELinux
booleans. For the latter there are some initial designs and ideas here:
https://github.com/cockpit-project/cockpit/issues/8657
It's not entirely clear yet whether these should go into the pages themselves,
or whether there would be a standalone cockpit-ansible kind of Application that
collects well-defined state from the system and presents it on one page in one
or a series of playbooks. But this at least a good place to start/continue the
discussion.
Pitti