Juju Team Updates - Week #7 2022

[pedroleaoc (Pedro Leão da Cruz)]

Hi everyone, below you can find the updates from the Canonical Juju Team for the week starting on the 14/02/2022. Have a great weekend!

cc @pedroleaoc @jameinel

[benhoyt]

• Reworked Pebble health checks API/CLI PR per latest review feedback
• Updated corresponding Python Operator Framework APIs and Juju SDK docs to match
• Reworked Pebble child process reaping to be deterministic and avoid time.Sleep hack

[anvial (Vitaly Antonenko)]

• prepared questions for discussion at Network Core meeting. Provided comments and suggestions to ‘Juju Service Locator’ specification
• investigated on ‘Juju Service Locator’ use cases to define their possible types
• triaged bugs

[wallyworld (Ian Booth)]

• 2.9.25 candidate release to QA
• various fixes for CI test failures
  • reworked upgrade test
  • fix upgrades when agent stream is used
  • race test fixes
  • Jenkins CI maintenance and job fixes
• fix display of storage Mount Point in Juju status
• work on secrets spec

[simonrichardson]

• 2.9.25 Release Jenkins fixes
• Investigation into data modeling query DSL, along with more data type modeling analysis.
• Allow the specifying of a branch when deploying charms/bundles.

[manadart (Joseph Phillips)]

Had further network modelling and data back-end design discussions.

Also did some work on ensuring that changes in substrate availability zones are dynamically reflected in provisioning distribution.

Some notable patches:

• Fixed a bug where, after upgrading Juju, floating IPs from Corosync/Pacemaker were stuck on containers.
• Removed the antiquated juju-bridge command.
• Patch to ensure that destroying machines with --force will work when the machine has a file-system that is linked to a storage instance.