Below are the meeting notes for this week's Community Meeting, a text-based meeting held weekly in #community-meetings on our community slack, which you can join: https://community-slack.chef.io/
DevRel/Community
Kiah Tolliver shared
Let's get this party started with a few updates from DevRel.
Get ready because there's a LOT of content coming your way. We're beefing up on webinars and live streams. Below are upcoming online events that you shouldn't miss:
Upcoming Webinars:
Jan 19th - Making DevSecOps an Automated reality
Jan 20th - Scaling Infrastructure testing with Chef InSpec
Jan 27th - Chef InSpec Security Profile Basics
Feb 23rd - Gain Control & Visibility into Linux Laptops
Feb 24th - AWS Marketplace
March 30th - Are Scripts Slowing Down System Admins?
Next week’s live streams:
Jan 18th - Digging into InSpec Matchers
Jan 20th - Interview with Hackathon Winner Ambily KK
Tune in on YouTube & Twitch
This week’s releases
Chef Inspec
Kiah Tolliver shared
Chef InSpec Azure Cloud Resources Released This release has 8 new Azure resources with a few bug fixes.
Chef InSpec AWS Cloud Resources Released We released 18 new AWS Inpsec cloud resources and a few improvements
Chef Workstation
Kiah Tolliver shared
Chef Workstation 22.1.745 Released! This release contains all-around improvements to the kit as well as some significant performance improvements in knife.
Other releases
Kiah Tolliver shared
Chef Backend 2.3.16 Released! After a bit of a hiatus, we are back with a new release of Chef Backend. This release includes a giant pile of component upgrades to fix CVEs and the first part of the log4j fix.
Updates
Chef Automate
Ankur Mundhra shared
Hello community
This week the team has worked on:
- Finalised design for semantic versioning of Automate
- Fixed a bug to ensure that all code components are using Nginx 1.21
- Started pointing from stable channel in Habitat for building Automate
- Improved Automate HA CLI commands (example: validate-ha-infrastructure, provision-infrastructure)
Team Automate!
Chef Habitat
mwrockx shared
Hello from Habitat!
This week's updates:
-
Making progress on next core-plans refresh
-
Working on adding hart size and promotion times to package metadata shown in builder
-
Improve frontend scaling option form on-prem builder
-
New developers onboarding
-
Cleaning and automating API docs
Chef Infra Client
tas50 shared
Hey everyone!
The big news for this week is we officially started the development process of Chef Infra Client 18. chef/ohai is now 18 and chef/chef is also 18. There's new stable branches cut for 17.x and those will now get backported bugs and CVE fixes only along with 16 stable branches
The team started digging into the new Ruby 3.1 release. As usual there's lot of fun things to update and fix to get Ruby 3.1 building and chef running on this new release. It's going to be a great one though. There's some nice performance improvements and big changes to how stack traces are shown which will make errors in Infra Client significantly easier to diagnose
We're also wrapping up the initial work to read client.pem content from the Windows cert store
The team is digging into some issues that folks may have noticed with the archive_file resource failing to load libarchive properly. After a lot of digging it appears that we have some issues with omnibus itself that is resulting in omnibus packages leaking out into the system libraries. Lots of fun there and we hope to get to the bottom of it soon.
And last, but not least we're onboarding a new team member. She's not here yet, but we'll see if we can introduce folks next week
Oh, 1 last thing for Infra Client. We just merged builds for Amazon 2022 and our packages team is digging further into FreeBSD 13 which is blocked on the omnibus leakage issues
Chef Infra Server
Lincoln Baker shared
Not sure if Marc is around, so I'm happy to post
Updates on Chef server for this week
- Released Chef Backend 2.3.16 -
-
Supported Hosted Chef upgrade.
-
Continued work on supporting Opensearch -
External Opensearch Support · Issue #3068 · chef/chef-server
- Investigation of build pipeline failures -
WIP Fix license scout issue by lbakerchef · Pull Request #3067 · chef/chef-server
- Adding umbrella scenarios for Chef BackendChef Backend 2.3.16 Released!
Hello Chefs! Chef Backend 2.3.16 is now released and available on the downloads site. Fixes Chef Infra Client, which is used in the chef-backend-ctl reconfigure command, has been updated from 15.x to 16.17 to resolve EOL warnings when running. Enhancements chef-backend-ctl backup no longer backs up the Elasticsearch cluster to speed up backup times. Users restoring a backed-up cluster can instead run chef-server-ctl reindex --all from a frontend node to generate new data in Elasticsearch...
Chef Inspec
cwolfe shared
The Chef InSpec team has been working on:
- Continued work on expanding support for more containerization systems on the
virtualization
resource - PR now open for kubernetes and podman support - Adding support for SSL authentication with WinRM
- Fixing a bug in which the
--insecure
option toinspec exec
does not work with dependent profiles loaded with thehttps
protocol and a self-signed certificate - Fixed a bug in the regex matching the version numbers in the
package
resource when detecting whether it has the latest version
Chef Workstation
tas50 shared
Hi All! We had a Workstation release in early this week.
Work-in-progress
- The Community Tools team is almost done with updating kitchen-vra plugin to support vRA8. PR is created for the vmware-vra-gem, the PR for kitchen-vra is now available for review too.
- We are close to wrapping up Apple M1 support in Workstation, should be available in upcoming release
- Continuing on implementing
chef env
in Golang. We are finalising amongst feasible ways to record relevant paths. - Adding workstation install related telemetry
- Introducing test coverage report in PRs through GitHub workflow.
- Support for Chef ad hoc runs on AIX is almost complete, barring few issues that are being investigated.
- Taken up few issues 1) & 2) for fixing
Sous Chefs
ramereth shared
Hello from the Sous Chefs!
Here's the list of new releases in the past week:
-
firewall - 4.0.1: Remove extraneous task file that's no longer needed
-
maven - 6.0.0: Enable
unified_mode
and require Chef >= 15.3 -
mysql - 11.0.1: Cookstyle fixes
-
postfix - 6.0.5: Cookstyle fixes
-
sc-mongodb - 5.0.0: Enable
unified_mode
and require Chef >= 15 -
yum - 7.3.0: Add
flush_cache
option todnf_module
-
yum-epel - 4.3.0: Allow the cookbook to install EPEL on Rocky Linux
-
yum-mysql-community - 5.2.0: Switch to using
yum_repository
resource instead of template -
yum-remi-chef - 6.0.0:
-
Add missing remi-modular repo for DNF modules
-
Use DNF modules on supported platforms (CentOS 8+ / Fedora)
-
Add
yum_remi_
custom resources -
Fix repo priority on Amazon Linux
-
yum-remi-chef - 6.1.0: Bump yum dependency to >= 7.3 for proper cache flushing on module switch
Cinc Updates
ramereth shared
Hello from the Cinc Project!
Cinc Client
- Fixing Windows builds in Chef 17 is a top priority and will be hopefully fixed soon
Cinc Server
- @Alexey Hariton has joined and will be looking into making an upstream PR to fix paths used in the cookbooks
Cinc Workstation
- Looking into resolving issues with running
cinc -v
before releasing 22.1.745
We have started an etherpad to try and track discussion during our Bi-Weekly. Please feel free to add any topics for the next meeting in just under two weeks.
Other updates
tas50 shared
We merged some really cool new stuff to Supermarket this morning that will ship in the next release
Cookbook quality metrics are no longer using Foodcritic. Everything is cutover to Cookstyle so every public cookbook will get evaluated by all 250 Chef specific cops.
In the future, this will give us the ability to flag known broken cookbooks and cookbooks we know won't work on modern releases of Infra Client.
The team there is also just about to merge the upgrade of the bundled PostgreSQL release from 9.3 -> 13.4
That brings us up to current there and also gives us the ability to use the new jsonb data for storing and querying JSON directly
That's going to let us store the cookstyle results in JSON and better present them in the UI / future APIs
Very cool stuff happening in Supermarket now that we have a team looking after it again
Also expect a new cookstyle release this afternoon with a new cop to detect invalid cookbook names
See you next week!