New host detail page feedback (Foreman 3.0+)

This is the existing mapping in Foreman for BMC commands

                         :start    => 'on',
                         :stop     => 'off',
                         :poweroff => 'off',
                         :reboot   => 'soft',
                         :reset    => 'cycle',

the off command is implemented in various adapters on smart proxy, I can only speak about impitool , but you can easily find the definition for others. ipmitool describes it as

Power down chassis into soft off (S4/S5 state).
WARNING: This command does not initiate a clean shutdown of the operating system prior to powering down the system.

IMHO that’s not soft as you meant it, since it really means power off but in a way the machine still has some power so you can power it on e.g. with touching the keyboard. It’s not the ACPI command to initiate the power off through OS.

reset means cycle per the mapping above, cycle means the following:

Provides a power off interval of at least 1 second. No action should occur if chassis power is in S4/S5
state, but it is recommended to check power state first and only issue a power cycle command if the 
system power is on or in lower sleep state than S4/S5.` which basically does `off` waits a second and `on`

That’s probably useful when you want to make sure the disks stops rotating or RAM fully forgets. Anyway this is the mapping that wasn’t changed as part of this effort. However only unique statuses we kept to make it simpler.

For VMs we only expose on and off on the old host show page and on the compute resource page. The other operations are only accessible from the bulk action menu, there you can e.g. cycle the VM. We may consider adding this to the new host page too.

It looks like as an admin on the new page view I do not have the ability to edit ansible roles with the new host detail page, but I do with the old one. My admin role only checks the “admin” box, it does not grant each of the roles individually.

1 Like

There was a bigger chagne in Foreman 3.1 (and respective foreman_ansible version), however it still sufferfs from the same silly mistake. For the page without any role assigned, we don’t display the button to assign some roles. This is how it looks when at least some roles are assigned.

And this with no roles assigned

As a workaround, please either navigate to the host edit form - ansible roles tab or use CLI to assign at least one role.

cc @ezr-ondrej could your team add an edit roles button to the empty page?

2 Likes

Thanks for debugging Marek, I’ve opened an RM ticket and will get it on our teams backlog :slight_smile:

2 Likes

A fix was pushed to foreman_ansible:
assign_roles

4 Likes

Hi,
to giving feedback about the Foreman host details under “All Hosts” is since foreman 3.0 the column “environment” missing. → related to this issue - Foreman UI - new joined nodes are not displaying "OS" or "Environment" in hosts-tab - #20 by cooler22

after discussion with @ekohl this could be an issue new foreman_puppet plugin that doesn’t add the column and maybe that was missed in the extraction from core.

That’s really about the host list page, not the host detail page.

Having the Runtime widget (Config Retrieval and Runtime) overview has proven to be really helpful with tuning our installation properly for performance across a large installations, and if it’s not too heavy to keep such a widget on the new host detail page (or if there’s somewhere else to retrieve an average / overview of such stats) it would still prove to be extremely useful! Thanks!

3 Likes

Thanks for the feedback, I think the plan is to keep this chart based on the configuration reports in the respective tabs. FYI @lzap @MariSvirik @amirfefer

1 Like

The chart will definitely not be with Foreman 3.2 but we would like to get it back. It was quite heavy on resources thos as it needs to load 7 days of reports, parse all metadata (YAML) and draw the stuff. In the new design, this is not changing - it just needs to load whole report body (JSON).

Having said that, this should have been using Rails Cache from the day one, so at least we can ensure that once this is fetched once in 30 minutes (the puppet interval), we can grab it from cache quickly.

1 Like

I’ve found the need to go back to the old UI in order to check on broken templates

1 Like

Thanks @James_Shewey, could you please describe the flow in more details? Do you go to the templates tab and “Review” the e.g. provisioning template? Perhaps the list of associated templates would be a good addition to the new Details tab.

@Marek_Hulan - Yes that is correct. From host Host Overview, I then click the Legacy UI option, then click the templates tab and then click on the upside-down carat (^) symbol or down arrow and right click on “review” and open in new tab (Loading the page while losing the navigation interface has always felt clunky to me and that was my workaround).

It would definitely be great to have that on the details page. I don’t care if it gets buried somewhere as long as I will still be able to get to it when the old UI goes away.

As an aside, in Chrome, I am unable to change tabs when in a content view. So if I am on https://example.com/content_views/4#/versions, for example I have to manually go to the address bar and change the URL to https://example.com/content_views/4#/repositories in order to view/switch to the “Repositories” tab in 3.2.

If my understanding is correct the switcher will be fixed by a cherry pick, see Foreman core Maintainers meeting on 2022-04-06

1 Like

New UI has a great potential. If it will be possible to add some tiles with info from old hosts page, like HW, OS, Facts… all on tiles which you will be able to enable/disable and move as you like.

Totally, there’s a PR that adds the details tab, which should be full of information. They can be collapsed (and such preference will be stored for the user) so one could tailor, what all is relevant.

2 Likes

I would like to see the old button to “schedule remote job” on the host.
Now I have to go to “Monitor → Jobs”.
And what is the “>_ console" button”? Mine is disabled.

I’m not sure what version you’re on, but the button is still there in the top right corner.

IIRC that’s access to a serial line-like console for machines which support it. It is quite possible that previously it was hidden if unavailable, but now it is shown, but disabled.

Not sure if anyone has mentioned this yet, but the Web Console button is missing from the new UI, or I am at least not finding it. Need to revert to legacy/old ui to get to it.

if it’s a VM, it takes you to the relevant console (console output from AWS, VNC/SPICE etc)

newer version of REX already adds that to the kebab menu

2 Likes