Consuming MongoDB from a Snap

[Nicholas Skaggs]

On Fri, Jun 23, 2017 at 10:36 AM, Menno Smits <menno.smits at canonical.com>
wrote:

>
>
> On 23 June 2017 at 12:09, Andrew Wilkins <andrew.wilkins at canonical.com>
> wrote:
>
>>
>>> *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.
>>
>
> ​I imagine we would have a custom MongoDB snap for Juju rather than using
> this one as is. We want direct control over the snap. The niemeyer snap
> would probably be a good starting point though.
>
Long term, I think it would be interesting to switch the unit payload over
to a snap. One snap would get you the agent, and everything you need to run
it. Barring the issues with snaps, this would make the entire story quite
clean. I know we spoken about this in the past, but I think it makes sense
to keep in mind if you wish to migrate. Juju should bundle everything into
a juju server snap. On the client / bootstrap side, centos, windows, and
mac support is still something to keep in mind.

Nicholas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20170625/f920f63a/attachment.html>