Hello, Pau Garcia wrote:
On dt., 2021-03-23 at 15:04 +0000, J-M Roth wrote:
* VERY DANGEROUS: Using groups: It is not clear from the system view that a state/config channel is applied to a system via a group. ...
This is in the works, here you can see how this will be implemented and some mockups: https://github.com/uyuni-project/uyuni-rfc/blob/master/accepted/00076-state…
That rfc describes and seems to address the issue pretty well.
* System shows ok if there are non-compliant packages.
Do you think showing a yellow warning icon would be an acceptable solution?
I think this could be handled together with what I propose below, if it finds acceptance:
* In general, the system list/overview page could provide an even more holistic view by making more distinctions in the "Updates" column (or adding another "Status" perhaps) - Show a warning for very old OS (see above) - Show a warning if system contains non-compliant packages (see above) - Show a warning if product does not exist at all (instead of green, see above) - Reboot required could be shown in that same list (like after an SP migration) - State apply failures could also reflect in that list
I'll add this to our usability backlog. Again, if you file a feature request via Support, you will be able to track the progress.
Thanks, let me however go into more detail here. The global system list is largely update-centric currently, so it will almost always show red or yellow in the "Updates" column since the systems are never totally up-to-date, compared to the online repos at least. This may be different if you use Content Lifecycle. In other words, "Systems > System List > All" is mostly the same as "Systems > System List > Out of Date" all the time. Even the columns are identical in both views. The goal here would be to have "Systems > System List > All" provide a more holisitic overview of all managed systems. I've taken the liberty to use my modest image editing skills to illustrate what I mean more or less: https://pasteboard.co/K02UnR6.png Host 1: There are critical updates (red U), also it contains non-compliant packages (N-C). Host 2: This host has expired (the are no new patches / EOL). Host 3: No information for this host could be found ("(none)"). Host 4: This host is OK regarding all the mentioned criteria, however it requires reboot. Also, states didn't apply correctly lately. One should make sure that users are not experiencing an epileptic crisis when viewing this screen though. Maybe options could be included that would allow disabling display of the secondary states like non-compliant packages or state application failures on this screen. I'll leave this to UX experts.
* Software Channel Management
Software > Manage > Channels page could show the sync policy for the individual channels. Currently there is no overview of the sync policies of the individual channels. You have to click on each one, open it and take a look.
If I understood you correctly, you should be able to find that information under Admin > Products > Products. There are icons showing whether a base channel and all its child channels are synchronized.
I mean the internal channels, not the repos. For the internal channels to contain up-to-date information, they have to be synced from the repos either manually or via schedule on Software > Manage > Channels > channel > Repositories > Sync. Currently, the list at Software > Manage > Channels only shows the channels and how many packages they contain. It does not show if they are up-to-date or when they were last synced. That information can only be obtained by drilling down into each of them manually one-by-one. The Channel Overview page could simply contain more columns with more details about the individual channel state (like the last synced time). It's a small usability fix. Best regards, J-M Roth