Juju and snappy implementation spike - feedback please

[John Meinel]

On Aug 9, 2016 1:06 AM, "Nicholas Skaggs" <nicholas.skaggs at canonical.com>
wrote:
>
>
>
> On Mon, Aug 8, 2016 at 11:49 AM, John Meinel <john at arbash-meinel.com>
wrote:
>>
>> If we are installing in '--devmode' don't we have access to the
unfiltered $HOME directory if we look for it? And we could ask for an
interface which is to JUJU_HOME that would give us access to just
$HOME/.local/share/juju
>>
>>
>> We could then copy that information into the normal 'home' directory of
the snap. That might give a better experience than having to import your
credentials anytime you want to just evaluate a dev build of juju.
>
> I agree this gets more difficult with the idea of sharing builds -- as
you say, you have to re-add your credentials for each new developer.In
regards to your thoughts on --devmode, it does give you greater access, but
some things are still constrained. The HOME interface doesn't allow access
to dot files or folders by default. So it's not useful in this instance. If
juju were to change where it stores it's configuration files (aka, not in a
dotfolder) this technically becomes not a problem as the current home
interface would allow this.

Sure. That's why I mention "We're in dev mode now, and can ask for a
JUJU_HOME interface vs the existing HOME one." We can also just ask for a
"give me the root filesystem" interface that doesn't get connected by
default.

I think not being able to publish your version of a snap and have it work
with the "standard" version of a snap is going to be a general issue for
anyone using snaps for development. So maybe it's a general snap property
that can give you access to a "named" common directory.

John
=:->

>>
>>
>> AIUI, the 'common' folder for a snap is only for different versions of
the exact same snap, which means that if I publish 'juju-jameinel' it won't
be able to share anything with 'juju-wallyworld' nor the official 'juju',
so there isn't any reason to use it.
>>
>> I don't know exactly how snap content interfaces work, but it might be
interesting to be able to share the JUJU_HOME between snaps (like they
intend to be able to share a "pictures" or "music" directory).
>>
>> If we *don't* share them, then we won't easily be able to try a new Juju
on an existing controller. (If I just want you to see how the new 'juju
status' is formatted, you'd rather run it on a controller that has a bunch
of stuff running.)
>
> It's worth mentioning / filing a bug about our needs with the snapcraft
folks to see what options might exist. I've started conversations a few
weeks ago and solved or got good bugs in on other juju issues. I think they
understand the application config limitations / issues, so we can push for
a resolution.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20160809/2c8ed8e8/attachment-0001.html>