Foreman Community Demo #107

Every few weeks we host a Community Demo to showcase new & interesting developments from the Foreman community. We encourage participation from any member of the community (although you do need a Google account), so if you’ve been working on something cool, please do come show it off.

This post is a wiki, so if you have something to show, add yourself to this table!

Expected In

We’ve added a new column to indicate the release in which community members might expect the feature that is being demoed to appear. This column should be taken as a guide rather than gospel. Unforeseen circumstances might drag a feature out a release or two. The best way to know for sure what is in a release is to check out the release announcement! :slight_smile:

If you have any feedback about the change to the format, feel free to comment here :slight_smile:

Depending on where it would be a better fit, please add yourself to one of the following tables:

Foreman user-focused demos

Speaker Time Topic Redmine Issue Expected in Version
@orabin 3 mins Introductions
@Ron_Lavi 10 mins new Reports plugin & Reports tab on host page, migration post here Foreman 3.2
@adiabramovitch 3 mins new reports dashboard widgets Foreman 3.2
@Partha_Aji 5 mins Import/Export repositories 34338 Katello 4.3
@cintrix84 2 mins Module Stream Host Details 34382 Katello 4.4
@jeremylenz 5 mins Packages - Install Packages modal 34191 Katello 4.4

Foreman developer-focused demos

Speaker Time Topic Redmine issue Expected in version

Due to conflicts for most of the presenters the community demo is moving this week (one time only) to a hour earlier.

1 Like

Can we share in the intro that our browser’s compatibility has been officially updated in Foreman 3.3?

Community Demo 107

Here is a summary of last week’s community demo.
This is a wiki. Please correct any misunderstandings.

Browser support from Foreman 3.3 and higher

It’s been a few weeks since Ron Lavi described the challenges of maintaining browser compatibility. After a few weeks to allow for discussion, it is now official that Foreman 3.3 and higher will support the latest versions of Safari, Firefox, and Edge, Chrome / Chromium browsers.

New reports plugin: information and migration process @Ron_Lavi

@Ron_Lavi also talked about the changes and necessary actions because of the new reports plugin. Although the old reporting method will still be used and available in Foreman 3.2, it’s advisable to start migrating old reports to prepare for the changes as soon as possible. Ron talked us through a forum post by @lzap . Lukas has documented the process here

The reports page in Foreman has a deprecation notice that guides you to that page also.

Ron also talked about plans to reuse the same reports table across community reports.

Reports plugin widget on host page @adiabramovitch

In addition to what @Ron_Lavi explained, @adiabramovitch showed us that there is a new widget that corresponds with the new host report plugin for the host details page.
It has the same functionality as the previous widgets but the data comes from the new reports plugin.

Importing/Exporting Specific Repositories @Partha_Aji

Partha demoed how it is now possible to export and import a single repository.
The procedure uses the same hammer import export endpoints you’re familiar with, and takes advantage of the Content View Version workflow to allow users to export a single repository, then import it to another Foreman/Katello instance.

To export, use the repository ID to target the repository for export.

We can now import it in a new organization in Foreman/Katello.

New Module Stream tab - host details @cintrix84

@cintrix84 compares and contrast the old and new module stream layout in the host’s details page. To locate the module stream tab, navigate to Hosts > All Hosts and then select a content host, and then click the Module Streams tab to view an orderly list.

Action options and filtering options will be added at a later date.

Content host package installation improvements @jeremylenz

Jeremy walks us through a pretty significant workflow improvement to package installation.

Jeremy outlined the disadvantages to the currently available package installation method for content hosts. This process also includes having to know the package name and manually enter it into the UI.

In the new host details page, there’s a dedicated Packages sub-tab in the Content tab. This helps orient you as it lists what packages are already installed.

To install a new package, there’s a dedicated Install Packages button in the menu. This opens a modal where you can select from a list of possible packages to install rather than having to know and then manually enter the package name.

This tables calculates all the possible packages that you can install, and removes the list of already installed packages.

Filtering options and scoped searching is available.

When you’ve selected the package to install, the default installation method is via remote execution.

Thanks to everyone who came and demoed. Special thanks to @Ori_Rabin for covering for me.