information needed for Mariadb Enterprise edition

[Antonio Rosales]

On Thu, May 26, 2016 at 1:34 PM, Daniel Bartholomew <dbart at mariadb.com> wrote:
> On Tue, May 24, 2016 at 6:38 PM, Daniel Bartholomew <dbart at mariadb.com> wrote:
>> On Thu, May 19, 2016 at 7:46 PM, Kevin Monroe
>> <kevin.monroe at canonical.com> wrote:
>>> I recently took a look at the mariadb charm on ppc64le and ran across some
>>> interesting bits.  I'm looping in the charm maintainer (dbart) for extra
>>> insights.
>>>
>>> First, MariaDB has both enterprise and community versions available for this
>>> charm to deploy.  Rajith, as you saw in the readme, you should be able to
>>> obtain credentials from the MariaDB Portal
>>> (https://mariadb.com/user/login?destination=my_portal/download).  However, there was a recent change in the package signing key [0] that
>>> may affect installation.  Daniel, are these "enterprise.yaml" creation
>>> instructions in the charm readme still valid?:
>>>
>>> http://bazaar.launchpad.net/~charmers/charms/trusty/mariadb/trunk/view/head:/README.md#L46
>>>
>> No. Those are old instructions. I submitted an updated version of the
>> charm way back in November, but it looks like it never made it into
>> the charm store. As a first step, the version of the charm currently
>> in my repo (revision 28) should immediately be pushed to the charm
>> store: lp:~dbart/charms/trusty/mariadb/trunk
>>
>> The correct readme is here:
>>
>> http://bazaar.launchpad.net/~dbart/charms/trusty/mariadb/trunk/view/head:/README.md#L24
>>
>> ...but the instructions there won't work unless the charm in the store
>> is updated.
>>
>
> After looking into the issues some more, I've uncovered some new ones
> relating to deployment of MariaDB Enterprise on POWER8 with the
> updated version of the charm my launchpad repo. It's probably best to
> keep the old charm in the store as-is until I have the new version I'm
> working on ready. I should have it done early next week. POWER8
> deployment issues with the old charm, as long as you don't configure
> the enterprise.yaml file, and just 'juju deploy mariadb' are now
> resolved AFAIK thanks to some modifications I made today to the
> community MariaDB repositories.

While you are in the midst of updating have you taken a look at
Resources and Terms in Juju 2.0?

Resources is documented at:
https://jujucharms.com/docs/master/developer-terms

Terms is under final review at:
https://github.com/juju/docs/pull/1122/files
Specifically,
https://github.com/mbruzek/docs/blob/abd31c0962d73efea76a1381a857a279e27d384d/src/en/developer-resources.md


Thanks for the work on the MariaDB charm. If you have any questions
please post here or in #juju at Freenode.
-Antonio

>
> Thanks.
>
> --
> Daniel Bartholomew, MariaDB Release Manager
> MariaDB | http://mariadb.com
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju



-- 
Antonio Rosales
Ecosystem Engineering
Canonical