On 23 June 2017 at 12:09, Andrew Wilkins <andrew.wilk...@canonical.com> wrote:
> On Fri, Jun 23, 2017 at 7:47 AM Menno Smits <menno.sm...@canonical.com> > wrote: > >> We've had some discussion this week about whether Juju could use MongoDB >> from snap instead of a deb. This would make it easier for Juju to stay up >> to date with the latest MongoDB releases, avoiding the involved process >> getting each update into Ubuntu's update repository, as well as giving us >> all the other advantages of snaps. >> >> Two concerns were raised in this week's tech board meeting. >> >> *1. Does snapd work on all architectures that Juju supports?* >> >> The answer appears to be "yes with some caveats". For xenial onwards >> there are snapd packages for all the architectures the Juju team cares >> about. >> > > Ah, I thought the question was rather whether or not the mongo snap > existed for all of those architectures. I don't think it does. IIANM, the > snap comes from https://github.com/niemeyer/snaps/blob/master/ > mongodb/mongo32/snapcraft.yaml, which (if you look at the "mongodb" part, > appears to only exist for x86_64). So we would need to do some work on that > first. > Mongo 3.2 upstream doesn't support s390x. 3.4 does though, so I don't see any immediate reason why a snap of 3.4 couldn't support all arches we care about. I was asking about snaps in the context of moving to 3.4, really. https://packages.ubuntu.com/xenial/snapd >> >> For trusty only amd64, armhf and i386 appear to be supported. >> >> https://packages.ubuntu.com/trusty-updates/snapd >> >> This is probably ok. I think it's probably fine to start saying that new >> Juju controllers, on some architectures at least, need to be based on >> xenial or later. >> > > Since the controller machine isn't designed for workloads, it seems fine > to me to restrict them to latest LTS. > Eh well, there is no juju-mongodb3.2 package for trusty at all is there? Cheers, mwh One issue would be upgrades: we would either have to continue supporting > both snaps and debs for mongodb, or we would have to disallow upgrading > from a system that doesn't support snaps. That would OK as long as there > are no workloads on the controller, as we could use migration. > > *2. Does snapd work inside LXD containers?* >> >> Although it's rarely done, it's possible to set up a Juju HA cluster >> where some nodes are running inside LXD containers so this is something >> we'd need to consider. >> > > It would suck if we couldn't test using the lxd provider, though. > > From xenial onwards, snapd does indeed work inside LXD containers. I >> followed Stephane's instructions using a xenial container and successfully >> installed a number of non-trivial, working snaps including Gustavo's >> mongo32 snap. >> >> https://stgraber.org/2016/12/07/running-snaps-in-lxd-containers/ >> >> >> There is of course more testing to be done but it seems like having >> Juju's MongoDB in a snap is certainly doable. >> >> - Menno >> >> -- >> Juju-dev mailing list >> Juju-dev@lists.ubuntu.com >> Modify settings or unsubscribe at: https://lists.ubuntu.com/ >> mailman/listinfo/juju-dev >> > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/juju-dev > >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
