Content moved to https://github.com/ancorgs/alp-system-management/blob/main/cockpit.md
-
-
Save ancorgs/dbd25f8910cce7ffdff0b3d9cdb3b937 to your computer and use it in GitHub Desktop.
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.
Is there any expectation of being able to use Cockpit (or any similar tool) to configure also some aspects of the so-called workloads
I would love to see that, but this would have to be done on per-workload basis. However, having a way to extend the management system by custom plug-ins sounds like a fair requirement for the future.