Comment 7 for bug 1517165

On Thu, Dec 10, 2015 at 12:46 PM, Kevin W Monroe
<email address hidden> wrote:
> Hey dbart, I'd like your thoughts on something.. You mentioned the
> previous charm no longer works because of an enterprise repo change, and
> I see that issue when running 'juju deploy mariadb' on ppc64le:
>
> unit-mariadb-0[10642]: 2015-12-10 17:17:55 INFO unit.mariadb/0.config-
> changed logger.go:40 W: Failed to fetch
> http://ftp.osuosl.org/pub/mariadb/repo/10.0/ubuntu/dists/trusty/InRelease
>
> Unable to find expected entry 'main/binary-ppc64el/Packages' in Release
> file (Wrong sources.list entry or malformed file)
>
> However, install continues and the charm installs mariadb from the
> archive instead of the maria enterprise repo:
>
> $ apt-cache madison mariadb-server
> mariadb-server | 5.5.46-1ubuntu0.14.04.2 | http://ports.ubuntu.com/ubuntu-ports/
>
> trusty-updates/universe ppc64el Packages
>
> My question for you: can we support a non-enterprise deployment of
> mariadb? Based on this current MP, the charm could check for 'token'
> and 'enterprise-eula', and if they look legit, install/enable the
> enterprise repo. If not, install from the ubuntu archives.
>
> This would allow for the same charm to be used to install both 'consumer
> grade' and 'enterprise grade' mariadb, depending on how the user
> configured the deployment. Thoughts?

Sure, we could update the charm to do this.

The only issue I see is that users will get MariaDB 5.5 instead of
10.0 on Trusty. MariaDB 5.5 does not have the POWER8 optimizations
MariaDB Enterprise 10.0 has. Even non-enterprise MariaDB 10.0 in newer
versions of Ubuntu doesn't have all of the optimizations. The first
non-enterprise version of MariaDB with all POWER8 optimizations is
MariaDB 10.1. But at least the charm will work even when no token or
eula are set.

Thanks.

--
Daniel Bartholomew, MariaDB Release Manager
MariaDB | http://mariadb.com