We don’t really have much time for us to spend on external integrations.
So far I believe I’ve spent more time helping tweak some stuff in the Ansible integration, adding support for projects and remotes than I have helping the Juju folks with theirs
I’d certainly love to see the Ansible integration rewritten to use pylxd instead of shelling out to the CLI, but that’s mostly an implementation detail, from a functional point of view, it’s been working great in my experience. Note that I’m talking about the connector which lets you connect to existing instances over
lxc exec and
lxc file rather than through SSH.
I’ve not actually looked at those modules which let you directly create your instances through Ansible as that’s not really been something I’ve ever needed to do myself.
In general our posture has been that we’re extremely happy to assist with any needed information or missing API that those integrations may need to work properly. We’ve done some small changes here and there for terraform-lxd and answered a few questions for the Ansible and Puppet integrations. But the fact is, we’re not experts in any of those tools (or in some cases, languages) so it’s far better for someone who’s got great knowledge of Ansible, Terraform, Puppet or Juju to work on the integration themselves and reach out to us when they need help with something on the LXD side.