Cockpit as 1:1 system management system

cockpit-01.md

Cockpit as 1:1 System Management Solution for ALP

Content moved to https://github.com/ancorgs/alp-system-management/blob/main/cockpit.md

zz_add_host.png

zz_kdump.png

zz_logs.png

zz_ntp.png

zz_yast2-kdump.png

Will the ALP configuration be split following the cascade approach we are adopting in Tumbleweed?
ALP will be based on TW; in order to have image-based update supported at some point of time I don't think that there is a way around that (unless you want to think of a completely new approach).

On transactional system: Currently cockpit on Micro works thanks to the fact that it does not need to write outside the writable directories (/etc/,...).
For updates, there is a transactional-update plugin being developed, but it has not yet been released for Micro 5.2 - should happen as a maintenance update.

Managing Multiple Systems from a Single Cockpit Interface
The focus - independently on upstream development - should be on 1:1 (pet) management. There are better ways for mass-management.