LXD and trusty-backports

[John Meinel]

For juju-2.0 we know that we want to be using LXD for containers.
However, I don't believe LXD itself is going to land in trusty-updates. It
*is* already in trusty-backports. My concern is that if we end up enabling
trusty-backports, that may cause conflicts with charms, as they may get
versions of code that they weren't expecting.

When we ran into this on Precise, we used 2 mechanisms.
cloud-archive[/tools] and a PPA for Juju (to give backported mongod).

It would seem for customer engagements, using the official archive is the
easiest sell, because if they are disconnected, we know they already have
to be mirroring archive.ubuntu.com. Anything else is one more thing we have
to teach them about.

I know we also ran into problems with enabling the cloud-archive
everywhere, because it started providing new versions of Django, etc that
MAAS needed, which broke charms.
We resolved that by pinning cloud-archive to lower priority and only
installing from it by direct request. Can we do the same for
trusty-backports?

Potentially we could also only enable it when you actually go to start an
LXD container on a machine, rather than always. Does that just cause
confusion when charm X fails because you have containers, but succeeds when
you don't?

Is there any plan to get LXD into trusty-updates so we don't have to worry
about this?

John
=:->
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20160120/c349b901/attachment.html>