Strictly confined juju snap available for testing

[erik-lonroth (Erik Lönroth)]

I’ll give it a try:

1. The distribution of juju via snap is not working well with centos. We gave up on that and are now left with the only option to just distribute the binary.

Juju client on centos with NFS homes

Looking for advice on how to install the juju client on centos7 where users has home directories on NFS. The NFS situation (which is common) causes issues with snap versions, but perhaps that has changed over time since we last tried this a few years ago? Otherwise, is there a recommended way to distribute the Juju client in a shared environment? Are there RPM:s? Are there Appimages?

2. Our multiuser environment with NFS, ActiveDirectory integrations (LDAP/kerberos) makes it impossible to build charms with charmcraft. This is true on Ubuntu + Centos (likele all other distros too). This is a client side issue.

3. The same issue is true since juju also installs the “ubuntu” user via the machine agent. It breaks all distros that does not have the ubuntu user natively (and frankly irritates the f*ck out of other distro-ambasadors. Juju is offending to centos-users (and all other distros). This is a server side issue.

What DevOps tools does Juju help you to avoid?

It is. That’s also part of a two side problem : The user is named ubuntu, which makes little sense on other distros and causes confusion. The ubuntu user has its home directory in /home which is badly aligned with systems that for example have ldap or nfs home directories or autofs. Introducing the ‘juju’ user with a home directory in let’s say under: /usr/local/juju-home would resolve those issues.

4. snapcraft - I don’t know how to build charms in anything except single-user ubuntu machines installed with snap. That is just making the whole tool ubuntu specific altogether. This is just wrong since it will never expand juju outside of this at all.