Canonical Juju

Remove KVM provider and use LXD --vm

Bug #1936188 reported by Simon Richardson
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

Given that LXD now has support for virtual machines[1], we should converge the code path to use LXD for containers and vms. We can dogfood our own tooling and give better feedback to tooling et al.

1. https://discuss.linuxcontainers.org/t/running-virtual-machines-with-lxd-4-0/7519

Tags: lxd-cloud
Simon Richardson (simonrichardson)
Changed in juju:
status: New → Triaged
John A Meinel (jameinel)
Changed in juju:
importance: Undecided → Low
Revision history for this message
Stéphane Graber (stgraber) wrote :

Related to https://bugs.launchpad.net/juju/+bug/1897746

On our recent call, the suggestion was to use the existing `virt-type` constraint and extend it to the lxd provider with two supported values, "container" (default) and "vm".

Juju could then start making use of that instead of the kvm provider.

tags: added: lxd-cloud
Revision history for this message
Erik Lönroth (erik-lonroth) wrote :

To be able to leverage LXD capability to spawn instaces with their own kernel is a game changer for many situations.

I think this feature is massive.

Revision history for this message
Simon Déziel (sdeziel) wrote :

@erik-lonroth, it's now possible to ask Juju (3.1.0) to spin up VMs. This was added by Simon Richardson via https://github.com/juju/juju/pull/15004. I just tested it and it works!

I'd guess that removing the KVM provider is the only remaining thing to do for this bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.