What has the Charm Tech team accomplished this pulse?
The highlights are: Scenario 7 is coming, Pebble docs are almost here, the future of Python-libjuju future is being charted.
Ops and Charming
- Plenty of work has been done towards Scenario 7: installation spec; context manager update, better network defaults, better secrets management, actions API update.
- A change has been contributed to Charmcraft base, allowing optimised YAML parser and generator to be used, leading to dramatic speed improvements when processing large relation data.
Pebble
- Significant effort to understand lock contention, leading to upcoming reduction in lock contention within the scope of the Pebble warnings API update.
- A concept of lanes has been introduced to group services and their dependencies, fixing the issue where the startup of independent services was affected by a single service failure.
- A long-standing bug that ate the tail of exec output in interactive mode has been fixed.
- An attempt at $VAR-style interpolation spec has been made and presented, with another iteration coming soon.
Python-libjuju
- A public discussion channel has been set up on matrix.
- A solid chunk of work done understanding who uses the library, what for, and how.
- An informational spec is being written, stay tuned.
Documentation
- Major Pebble docs update, planned to go live next pulse.
- Reviewed the “Write your first Kubernetes charm” tutorial to identify overlap and gaps with the Charm SDK ‘How to’ guides.
- The Juju SDK documentation structure is being reviewed, and we’ve contributed our part.
- Wrote the unit leadership how-to guide.
- Wrote the charm storage how-to guide.