Meeting notes for May 28th, 2020

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

bennyVasquez shared

Just a few things going on with us this week…

  • the new Learn Chef platform is set to launch Monday! Be on the lookout for notifications for all of that awesomeness.
  • We’re down to the very last recording of breakout sessions for #chefconf2020 ! The folks from Tap Here! Will be presenting at 12pm PDT / 3pm EDT Using Chef Effortless to Build DevOps Teams.
  • All of the recordings will be available next Tuesday afternoon to folks who’ve registered for ChefConf , so make sure you sign up. We also have keynotes from our leadership team, and a community panel in the afternoon with our very own @john , @Xorima , @BobChaos , and @ramereth joining me for a conversation about everything the community has accomplished in the last year.

This week’s releases

Chef Automate

tas50 shared

Automate 2 shipped 20200520145933 which let's you filter on SAML groups and includes a bunch of bug fixes https://discourse.chef.io/t/automate-2-version-20200520145933-released/17162

Chef Habitat

sdmacfarlane shared

Habitat 1.6.39 is hot off the presses. This includes the buildah container export support. Release notes will be up shortly.

Chef Infra Client

tas50 shared

First off Chef Infra Client 15.11.3 shipped. This includes the latest InSpec, 3 important bootstrapping fixes, backported resource fixes, and aarch64 packages. It also comes with a special long term support OpenSSL with hardening improvements

https://discourse.chef.io/t/chef-infra-client-15-11-3-released/17155

Chef Infra Client 16 also shipped with 16.1.16 (great version number there). This includes that same hardening OpenSSL release as well as bootstrapping fixes and a fix for a super painful Rubygems regression in Ruby 2.7 that @lamont tracked down for the Rubygems team. Turns out they slipped in a massive perf regression at the last minute.

https://discourse.chef.io/t/chef-infra-client-16-1-16-released/17163

Other releases

tas50 shared

And last for the Chef team, we shipped Cookstyle 6.6 which includes 4 new cops and some improvements to the autocorrect / detection in existing cops

https://discourse.chef.io/t/cookstyle-6-6-released-with-4-new-chef-cops/17165

El Jeffe shared

Releasing a new version of Habitat cookbook today that allows for the use of A2 embedded builder for Habitat. Thanks @dbright for catching that

Updates

Chef Automate

Alex Pop shared

:waveguy: from the Automate team!

  • Main focus for the past week was to polish the products that will be presented at ChefConf next week.
  • We also fixed a bug to show delete missing nodes checkboxes for admin users.
  • Released changes to the existing compliance profiles.
  • More compliance report shrinking merged, with up to 98% reduction for some large (e.g. 9MB) reports.

Chef Habitat

sdmacfarlane shared

Greetings from the Habitat team! This week has largely been a continuation of the research and design from previous weeks.

  • Builder-graph work is continuing, ~1k lines of code deleted in the latest refactor/cleanup.
  • Benchmarking Builder installations to derive system requirements for different scales of implementation

Chef Infra Server

prajakta shared

Hello Chefs!!

  • We are getting ready to release an rc build of Chef Infra Server 14 (It will be in current with 14.0.x tag). This will enable elasticsearch instead of solr for search. This build uses Adopt Open JDK instead of Oracle JDK. There will be a full reindex necessary to get data into elasticsearch.
  • We did some more work on the integration test pipeline.
  • We are working on fixing the habitat builds.
  • We are continuing to make progress on signing with aws signature v4 instead of v2.

That is it for us!

Chef Infra Client

tas50 shared

  • Started merging PRs for Chef Infra Client 16.2. So far we have a new homebrew_update resource thanks to @damacus and a new property that let's you control the SSL verification behavior per resource now thanks to @jaymzh
  • Lamont spent a ton of time digging into wonderful Rubygems regression so chef-client startup times should be back to 15.x levels and we're unblocked for Workstation (it was REAL slow)
  • We're also continuing to work with some internal teams that are contributing new resources to the client so expect more new resources in the coming releases. @mattray has a giant pile of NTP like resources and some interesting file like resources that provide some nice sugar

Chef Inspec

schwad shared

We are proud to have merged up a new minor version of InSpec: 4.19! We are juuust on the verge of releasing imminently and were hoping to have it out before the community meeting, but it will be out any moment!

With this latest version we are super excited to have introduced:

  • Reporter plugins - it is now possible to code your own plugin to determine how InSpec will report result data. You can see the developer documentation for a guide on how to implement a reporter plugin. Already we have tested this out with a mock pdf reporter and have been seeing neat work on a much more powerful HTML reporter!
  • inspec archive will now pack your profile into a tar.gz that includes the JSON form of the profile as the file inspec.json . This file can be used to programatically examine what’s inside the profile without needing to load it in InSpec ( https://github.com/inspec/inspec/pull/5017 )
  • When providing YAML config for waivers, InSpec now accepts a variety of date formats. Previously only YYYY-MM-DD was recognised. If you want to be sure the waivers expire at 5pm UTC-time, you can now do that!

Looking forward to more fun updates next week!

Chef Workstation

mparadise shared

Hello from Workstation! We've been continuing ChefConf preparations and look forward to releasing Chef Workstation next week and letting you all get your hands on the new upgrade tools. (And hearing how it goes, of course!)

Sous Chefs

tas50 shared

  • There was a good number of releases this last week with dhcp, java, mariadb, ruby_rbenv, graphite, and grafana
  • New cookbook dpkg_autostart was adopted from the old hw-cookbooks repo and updated to work with Chef Infra Client 16
  • Another round of Cookstyle and file standardization changes went out. You'll notice a .vscode dir in the cookbooks now that will suggest you install the Chef extension to help with authoring and linting the cookbooks.
  • @bodumin rolled out some new markdown linting to make sure links are valid in readmes

Other updates

ramereth shared

  • For folks using the openstack cookbooks, I pushed up cookbooks for the Rocky and Stein releases to the supermarket. I'm currently working on getting the cookbooks ready for Train.

jaymzh shared

  • One release worth noting: I cut a new release of taste-tester last Friday that has significant fixes to SSH tunnel handling, for those of you using that.

Cinc Updates

ramereth shared

Hello from the Cinc Project!

  • Released Cinc Client 15.11.3 and 16.1.16

  • Fixed an issue with the cinc-wrapper on Cinc Client where providing an empty run list was not working properly (see https://gitlab.com/cinc-project/distribution/client/-/issues/21 )

  • Working on adding Gitlab runners for building on aarch64 and ppc64le for Cinc Client. Hoping to have some builds next week for those platforms.

  • On the cinc-server side, @jgitlin has made some good progress this week: We now have a successful build pipeline which patches the wordmark branch of upstream chef-server to produce a working cinc-server-core package. Next steps will be to rebase the PR @jgitlin sent to @prajakta off the latest tag, and to get updated GitLab MRs to @ramereth with the fixed build process.

  • @BobChaos has been looking at fixing merge conflicts we have in auditor whenever we rebase with upstream

  • We've thanks to our users testing out our unstable Cinc Workstation build, we have a few more issues documented that we need to fix. We hope to look into those in closer detail soon.

See you next week!

This topic was automatically closed after 3 days. New replies are no longer allowed.