Hello Stephen, all,
Stephen Gallagher [2021-04-19 12:44 -0400]:
I'm CCing Martin on this because it occurs to me that we really
have some more formal blocker criteria for Cockpit functionality in
the Server Edition.
Thanks for reviewing that! I compared that list against the other Recommends:
that we have.
== Storage ==
cockpit-storaged is by itself only a recommends of cockpit, but explicitly
mentioned in comps. ✔
* It must be possible to enumerate all physically-attached drives.
* It must be possible to partition, format and mount physically attached drives.
* It must be possible to enumerate all network-attached drives.
* It must be possible to connect to a remote iSCSI target.
⚠ That would be udisks2-iscsi, which is only a Recommends and not in comps.
* It must be possible to connect to a remote NFS mount point.
* It must be possible to view the currently-active mount points on the system.
== Network ==
* It must be possible to configure the network to use automatic or
static IP addressing.
* It must be possible to enable or disable the firewall.
* It must be possible to allow or revoke access to individual ports
through the firewall.
* It must be possible to add custom network routes for a device.
The only thing I spotted is that NetworkManager-team is only a Recommends. Not
sure how important that is.
== Services ==
* It must be possible to start, stop and restart system services.
* It must be possible to configure whether a system service starts
automatically at boot.
* It must be possible to mask system services so that they cannot be started.
== Software Updates ==
Again, cockpit-packagekit is only a Recommends of cockpit, but explicitly in
* It must be possible to install available software updates on a live
* It must be possible to choose to install security updates only.
⚠ However.. The new "tracer" feature is only a Recommends, so it may be prudent
to add python3-tracer to comps as well to move from a static "reboot
recommended" to an "offer service restarting if that is sufficient".
== SELinux ==
* It must be possible to configure SELinux in enforcing or permissive mode.