Foreman 3.0, the Puppet extraction, managing Python content with generic classes, and much more!
Foreman Community Survey 2021
With ten minutes of your time, you could help shape the future of Foreman by completing the Foreman Community Survey. We don’t collect data past what we outline in our privacy statement. This means that we rely on you to tell us what you like, what works, and what is missing from Foreman that would make your life better and easier. Important decisions related to Foreman have been made through analysing what you’ve told us in the past, so please use this opportunity to make your voice heard.
Foreman 3.0 Branching
This week, the Foreman community is preparing to branch for Foreman 3.0 - the first milestone update for a year. As you’re probably aware, the major change in this upcoming release is the extraction of Puppet from Foreman core, as outlined in the roadmap discussion the road to making Puppet optional.
Following up on his Puppet in Foreman 3.0 release post, @ezr_ondrej came along to the most recent community demo and outlined what exactly this will mean for the community. You can rewatch @ezr_ondrej’s talk, and if you’ve any further questions, we would love to hear from you on our community discourse.
Keep an eye out for the Foreman 3.0 release candidates that will start appearing in the next few days. Evaluating release candidates is a great way to give back to the community and to ensure that the forthcoming Foreman 3.0 release is as stable as possible.
Running Foreman under a subfolder?
@tbrisker raised the issue that functionality that allowed users to run Foreman beneath a subfolder, for example https://example.com/foreman/ rather than https://foreman.example.com has been broken for some time. In this RFC, he proposes that we remove attempts to support this functionality as part of the Foreman 3.0 release.
Do you need to run Foreman under a subfolder? If so, please reply and let us know why this matters to you.
docs.theforeman.org
For a long time now, we have been preparing to make docs.theforeman.org the official Foreman guides. These guides are a combination of both Red Hat and ATIX enterprise customer documentation that has been open sourced so that the wider Foreman community has access to high-quality docs. We do our best to maintain these docs to a high standard, and should have an increasing level of input from some professional writers who will help. You can help by raising PRs against anything you think is missing or wrong. At the moment, we are aiming to make docs.theforeman.org the official home of Foreman documentation for the Foreman 3.0 release. You can find the source here.
Katello 4.1.2 has been released!
This latest release provides four new bug fixes, with the notable addition of pulp_rpm version 3.14, which provides a solution for filelists and changelog metadata that were not being parsed properly. For more information, see the release announcement.
UX updates
During the most-recent community demo, @MariSvirik came along once again to give an update into the thinking behind further design changes proposed for the Search bar. You can help shape the future design of the Search bar in Foreman by watching her presentation and providing your thoughts about the design. There will also be a further blog post later this week:
New toast alerts
In our community demo #97, @laviro talked about new confirmation modals. These new toast notifications have since been merged!
React-redux folder structure update
As part of previous discussions and during a July demo, there has been discussion around the React-Redux folder structure. The result of this discussion was to use the slice pattern - you can read more about it here.
Foreman UX Group Meetings
If you’re interested in keeping up to date and discussing the Foreman user experience, there are regular meetings where the current proposals are regularly discussed. @laviro and the others add these to our community events calendar. The meetings are open to all and the next meetings take place on August 9 and August 23.
Using generic classes to manage Python content with Foreman/Katello
This month @rverdile demoed new support in Katello for the Python content type using generic classes. These generic classes open up a lot of potential for adding future content types.
He followed this demo with an enhancement that showed how to index/upload/remove Python content and content view publish.
Katello Alternative Content Sources?
An alternate content source (ACS) is a filesystem or network path where Pulp will look to first when downloading content during a sync or on-demand content fetch. A repository with a slower connection might need to be the authoritative figure who determines the repository structure, but a faster ACS could be defined so that the actual content downloads (which is potentially much larger in size that the repodata) over a faster connection. With Katello in mind, this could be helpful for speeding up smart proxy synchronizations.
With the introduction of Pulp 3 to Katello @iballou is looking to feedback on the proposed design for Katello Alternative Content Sources.
Community Demo Listing Page
Thanks to @laviro who contributed a nice search bar to our new demo listings page on theforeman.org.
Thank you
Thank you to everyone who asked and answered questions, opened issues, and made the Foreman community a vibrant place to be over the last month!