For pulse #22 we were at the sprints in the Hague, so this is the first post-sprint report.
Pulse #23 highlights: after the sprints in the Hague, the Charm Tech team is psyched with various improvements! These include new tools, library updates, enhanced service management in Pebble, and documentation refinements.
Charming
- Fleshed out spec OP050 for the new Juju CLI wrapper library for charm integration testing (comments welcome). The next step will be a PoC.
- Charm Tech is starting “Charm Tech AMA” with one charming team per pulse. This will be a good chance to ask questions of Charm Tech, talk about pain points, discuss best practices, and so on.
- Began investigating the current use of
charm(craft fetch-)lib
s and Python packages for sharing code between charms. Feel free to get in touch if this is a topic of particular interest to you or your team. - Working towards a python-libjuju release that uses v7 Charms API, where deployment is controlled by base argument instead of series. The series argument is deprecated, and support will be removed in Juju 4.0.
- Released a python-libjuju hotfix, juju==3.5.2.1, to address a breaking change in the websockets sub-dependency.
- Helped ensure that existing integration tests can be run against upcoming Juju 3.6.
- Posted about the idiom where the Pebble layer is declared in rockcraft.yaml.
- Last but not least, introducing our new team bot: prints-charming!
Pebble
-
Started working on a new feature to auto-restart services that failed too quickly, see the spec here, and the previous investigation here). After a recent more in-depth discussion, we are moving forward with it now, the implementation and tests will soon come and close community issue #240.
-
Started working on a Prometheus-style metrics endpoint for Pebble. Some PoCs (here and here) are done, and there have been some discussions with the KernOS team.
-
Started working on a spec for the ability to disable checks in Pebble layers.
Documentation
- Pebble: reusable content like “how to install Pebble” is removed (both doc pages and from the search result) #516. Also, we have started planning more how-to guides for Pebble.