Hi everyone, below you can find the updates from the Canonical Juju Team for the week starting on the 07/02/2022. Have a great weekend!
This is the 2nd week of my rotation with the Bootstack team.
- Fixed LP 196023, preventing model migration or juju upgrade on machines where a container had been removed.
- Updated documentation around agent introspection capabilities with juju.
- Working on LP 1960276 where upgrades can fail on private clouds with slow connectivity between the cloud and juju.
2 Likes
- Fixed test-unit-lxd by making it run on ephemeral AWS nodes instead of our pets (it hadn’t worked for months)
- Updating Pebble health checks API and CLI per code review: https://github.com/canonical/pebble/pull/86
2 Likes
- provide comments and suggestions to ‘Juju Service Locator’ specification
- provide a series of internal discussions on the Juju Network Model
- research and evaluate existing network models for network equipment and cloud infrastructures
2 Likes
- Collaborated on final review for update to juju.is homepage.
- Continued restructuring SDK bundle docs, portioning content out in a series of inter-connected Reference, Explanation, and How-to guides.
- Gave feedback on new SDK doc on from hooks to Ops.
- Assisted Daniele with Documentation workshop part II.
- Presented / led hands-on real docs practice at community workshop.
- Agreed to secondment in Multipass team. Coming up soon.
1 Like
- replace the use of the model cache in the unit agent to avoid (so far) undiagnosed issue where changes to charm URL are not propgated
- add unit test to complete a fix for migrating manual machines
- investigate / fix CI test failures
- more work to update dependencies to Go 1.17
- more prototyping for a strictly confined juju snap
1 Like
Did a long-running diagnostic exercise deploying a large bundle to OpenStack, which I ran through a series of upgrades and deliberate Mongo primary, switches looking to diagnose reported failures and performance issues.
A couple of patches:
1 Like