You blink and one quarter of a year goes by. However, you can always stay up to date with what’s been happening in the Foreman community in our monthly newsletter!
Foreman 3.2 is now generally available
Foreman 3.2 comes with over seventy bug fixes as well as a number of enhancements. If you’re ever experiencing issues in Foreman, often an upgrade will be enough for the issue to disappear.
Upgrade today to enjoy the latest fixes and enhancements.
For more information about this release, see the Foreman 3.2 release announcement.
Migrating Hosts to the new format in Foreman 3.2
The way Foreman handles configuration management reports is changing, they are now stored in more efficient way. If you upgraded to 3.2 and noticed there is a warning when you visit Configuration Reports page, you need to reconfigure your Ansible and Puppet callback to send reports to the new API. The old API and Configuration Reports screen will continue working in 3.2 normally, but it is planned to be removed in 3.3 so we recommend to migrate early.
For more information, see the tutorial: Migrating reports to the new format in Foreman 3.2.
Katello 4.4 is now generally available
Katello 4.4 comes with enhancements that include performance improvements for repository indexing: now up to six times faster than in previous releases. As well as this, there has been more progress around the host details page, as well as improvements to Inter Server Syncing for disconnected Foreman scenarios. For more details about the headline features, see Katello 4.4 Headline features.
For more information about the Katello release, including how to upgrade or install Katello 4.4, see the release announcement.
Merging Foreman and Katello release processes
The release team have had active discussions about merging the Foreman and Katello release processes to simplify the process for everyone. This conversation is ongoing. For more information, see the Proposal
AlmaLinux added to test platform
Since the sunset of Centos 8, we reviewed which platforms and OSes we would test Foreman against.
evgeni updated the list of operating systems after a few months:
Tested: CentOS 8 Stream, Almalinux 8 Supported: RHEL, Rocky
Katello Alternative Content Sources Redesign Proposal
iballou and MariSvirik participated in the most recent Foreman Community demo to talk through their latest thoughts on simplifying how alternative content sources are handled in Katello. Their proposal simplifies the flow greatly but at the cost of removing some customization options. Take a look at their presentation here:
If you have any feedback, let them know on the thread: RFC Katello Alternative Content Sources.
New default port for Smart Proxy
The discussion around adding Katello to a Foreman install has been ongoing for a number of years now, with all angles needing thorough exploration so that any move in this direction will be positive for both Foreman and Katello users.
As part of work towards this higher goal, ehelms started a discussion this month on the topic of requiring a new default port for Smart Proxy. Part of the change entails freeing up the Foreman default for smart-proxy (8443) on Katello installs by moving Candlepin to port 23443 and moving the reverse proxy on a foreman-proxy to 443. The latter still needing a few more releases before we can fully drop.
Community Demo #108
We had one action-packed community demo this month.
If you would prefer to read a summary of the demo, you can find one here.
Here are the demo time stamps so you can jump to any section that looks interesting.
Foreman user-focused demos
- Katello 4.4 GA Updates
- Alternate content access - direction change and simplified design
- Katello new host details: Column sorting, tab hiding & host collections
- ISS improvements and bug fixes
- Katello new host details: Packages
- 2 Bug fixes in the bookmarks
- Import ansible playbooks
- New features in host page
- DSL autocompletion in templates
Foreman developer-focused demos
- Adding ‘Breaking Change’ tag to foreman github
- GraphQL schema, associations and why we need
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!