Motivation
Running async actions in SUSE Manager lacks a user-friendly feedback. For instance, running a salt highstate on a system:
The example screenshots show the problem.
Firstly user clicks "schedule highstate" button
Then they get informed that the action has been scheduled together with the link to the action details
Going to action details reveals the status of the action (pending/completed/failed).
Except of clunky user experience (navigating through multiple screens), there is no real-time feedback.
Idea
Display the action status using a UI spinner after the action is performed.
The most naive implementation would be using a polling widget that asks the backend about the status of the action. More elaborate solution (maybe not so easy though) would be utilizing our existing websocket mechanism for notifications.
The spinner widget will be implemented either in the action button directly, or separately (next to the info text - see the second screenshot). This must be discussed with the UI people.
Impact
The feature is only useful for actions that aren't supposed to take too long and should be implemented for such only. Traditional clients without osad are out of game here: executing an action can take hours.
Examples of good candidates: - channel assignment - highstate - configuration file deploy - hardware refresh - package install/upgrade (tentative)
Looking for hackers with the skills:
This project is part of:
Hack Week 19
Activity
Comments
Be the first to comment!
Similar Projects
Bring to Cockpit + System Roles capabilities from YAST by miguelpc
Bring to Cockpit + System Roles features from YAST
Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.
Goals
The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.
Resources
A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit
Linux System Roles: https://linux-system-roles.github.io/