Ansible System Role

software repos can be configured manually, or added through product registration

-
(should be a part of the repos below)

pci info exists, more through docs and command line, or goes to the TBD support module

firstboot sets it, we should document how to manually change but no cockpit module

Desktops have their own and better way to configure printers, we actually already tried to drop this module from TW.

YaST module was dropped from TW, automatic config is more reliable these days

(only on/off/test)

(only on/off/test)

very basic: set dump location (local, ssh, nfs) and test. Config would need serious rework (SUSE vs. RH)

This could be implemented using System Roles and a module to manage those in Cockpit.

This could be implemented using System Roles and a module to manage those in Cockpit.

Ensures needed packages are present. Configures /etc/exports, /etc/sysconfig/nfs, maybe others. Accomplishes "systemctl enable nfsserver"

Many customers use this. I would not want to deprive customers of this assistance, though as a support person I usually manually do the config file work.

This could be implemented as an extension to storage management or via System Roles.

Even if nobody ever has complained, every customer that is behind a proxy does use this module to setup the proxy

This could be implemented using System Roles and a module to manage those in Cockpit.

(wireguard, only client)

(wireguard, only client)

cockpit-networkmanager has VPN client setup, supports only wireguard

It's a Red Hat developed module, we'd need to explore it. Add and test to work with 389DS. It can also serve as the UI to manage it.

user/group settings available, anything else can be done on command line and via docs+editor

cockpit-machines pulls in libvirt and any related packages through dependencies

CPT-14 - Research how we could integrate supportconfig into cockpit Rejected
CPT-63 - Add subscription status tab to cockpit and allow the customer to introduce subscription information there Done

One of the issues that cause customers to suffer, not easy to use in command line.

First Boot Configuration Management

assuming without yast firstboot and if they want automation they wouldn't use Cockpit, this would be the wrong place

A module to handle system roles and execute them. Important to show Cockpit as the successor of Yast2 for configuration. Please Prioritize.

Filesystem level snapshots are a key feature in SLES and an important differentiator (RHEL and Ubunto do not yet have it). Having a way to create snapshots list & delete them and rollback to a previous one would be the way to facilitate it to customers.
Rollback available for transactional systems (Micro), non-transactionals need to use the boot menu.

not yet in Cockpit, probably something for Agama? We should evaluate.

Need to evaluate if this is a Cockpit feature or may happen somewhere else.

can be used without YaST module, while config may be harder. May be a selling point for some customers, need PM business case.

can be done on command line, needs evaluation how much it's used and how it contributes to usability, aka a PM business case

IBM seems interested in these features, needs priority PED-10826 - Consolidated Device Configuration - Cockpit part Code Released