Latest on the LXD Provider!

[Mark Shuttleworth]

On 10/11/15 11:06, Simon Davy wrote:
> We've been using lxd with the manual provider, really been impressed
> with what lxd brings to the table.

Yes, it's a really dramatic leap forward in distributed systems dev and
test, glad you like it :)

> Couple of questions
>
>  - do you have plans to support applying user-defined lxd profiles to
> the lxd containers that juju creates? This would be great in dev, and
> in special cases (e.g. give your charm access to the gpu, or bind
> mount a host dir)

This would map nicely to the generic ideas of machine-type or machine
constraints, so should be achievable. Why not write up a proposal? We'd
want it to feel just like choosing a particular machine type on your
cloud, only in this case you'd be choose a "container machine type".

>  - likewise, will users be able to specify base lxd image to use?

Actually, we'd like to be able to do that on any cloud, not just on LXD.
Essentially saying something like:

  juju deploy somecharm --image f67d90bad257

I'm paraphrasing, but the idea is to tell Juju not to lookup the image
("trusty", "precise") the way it normally would, but just to trust you
and wing it with that base image. This wants to be done in a way which
works for LXD and on any cloud that can provide a named snapshot or
image for launch.

For LXD development purposes, this would let you have a base image with
all the main dependencies you're going to need pre-defined, so the
actual charm install is super-fast.


> Many thanks for this work, it has the potential to really benefit our
> daily usage of juju.

Enjoy :)

Mark