Zaza migration to Juju 3.x by default

Hello All

I’m writing on behalf of the OpenStack Engineering team to let you that zaza will start using Juju 3.x by default once the pull request openstack-charmers/zaza#608 gets merged. It’s worth to mention that juju-2.9 remains compatible and tested in the CI to prevent regressions.

If you are a user of this library, please make sure you are using a juju version compatible with the python-libjuju installed. Zaza doesn’t pin python-libjuju at all, hence if you don’t want to use the latest version available in Pypi, then we encourage you to use a constraints file.

Known Issues