My hot take on 2.9, purely from a feature slate POV:
- I’m happy that I am able to deploy focal for KVM nodes now
- The UI exposing cloud-init user data inclusion for deployment is great - where previously this was simply hard-coded to point at another tool’s orchestration script, I’m now offered the convenience and additional flexibility of being able to use cloud-init directly
For the future my focus is around:
- Migrating away from virsh onto LXD
- Revisiting the relationship between MAAS, Juju and LXD and looking for ways to make them more synergistic (and mourning the death of the Juju composition GUI)
- something something Kubernetes
(Rambling off-topic grumble follows)
I guess I’m doing things that aren’t regular use-cases (stateful workloads on diverse hardware) so I’ll never be satisfied here, but seeing MAAS slowly adding functionality to the UI either by exposing cli functions or through embracing actions that make the UI uniquely powerful, is wonderful to me.
Watching Juju seemingly back away from the same thing through abandonment of the composition UI and focus on the monitoring stack gives me cause to again look around for something else for what MAAS/Juju/LXD together represented to me as a bright future, but is being dropped in favor of solving (yet) another already solved problem related to specific Kubernetes ops.