On 23 June 2017 at 12:25, Michael Hudson-Doyle <michael.hud...@canonical.com > wrote:
> >>> 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. > It makes sense to do the switch to a MongoDB snap as part of the move to MongoDB 3.4. 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? > True. There's a juju-mongodb for trusty but is has 2.4.9 so a lack of snapd support for some arches on trusty is a moot point. - Menno
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
