@tom Do you guys have something in place to support 5.x yet? I don't mind if 
you pull my bits forward for the 5.x stuff (mainly in the elasticsearch.yml 
template), either way, will you make sure whatever you decide to push upstream 
supports 5.x please?

Thanks


> On Aug 22, 2017, at 5:00 AM, [email protected] wrote:
> 
> Send Juju mailing list submissions to
>    [email protected]
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>    https://lists.ubuntu.com/mailman/listinfo/juju
> or, via email, send a message with subject or body 'help' to
>    [email protected]
> 
> You can reach the person managing the list at
>    [email protected]
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Juju digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: Elasticsearch Charm Promulgation (Tom Haddon)
>   2. Re: Elasticsearch Charm Promulgation (Tom Haddon)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 21 Aug 2017 14:53:10 +0100
> From: Tom Haddon <[email protected]>
> To: Kevin Monroe <[email protected]>
> Cc: James Beedy <[email protected]>, Juju email list
>    <[email protected]>
> Subject: Re: Elasticsearch Charm Promulgation
> Message-ID: <20170821135310.GB7478@tenaya>
> Content-Type: text/plain; charset=us-ascii
> 
>> On Fri, Aug 18, 2017 at 01:35:11PM -0500, Kevin Monroe wrote:
>> Hey James!
>> 
>> First up, thanks so much for bringing the ES charm up to v5.x!  Can you
>> tell me if the source for cs:~jamesbeedy/elasticsearch-7 is the same as
>> what we've got here:
>> 
>> https://github.com/charms/charm-elasticsearch
>> 
>> Or is that source waiting on this PR to bring it in line with your es-7
>> charm:
>> 
>> https://github.com/charms/charm-elasticsearch/pull/2
>> 
>> The PR LGTM, so I'll merge it on your ack.  Let me know if there are other
>> outstanding bits that need to go into this repo.  Once that's done, I
>> propose we push this to the ~elastic-ops namespace of which you're a member:
>> 
>> https://launchpad.net/~elastic-ops
>> 
>> And then promulgate the ~elastic-ops charm rev.  As Rick and others have
>> mentioned, teams help distribute ongoing maintenance to people that have a
>> vested interest in certain charms.
> 
> We've been working off https://code.launchpad.net/elasticsearch-charm which
> we've pushed to the charmstore here
> https://jujucharms.com/u/elasticsearch-charmers/elasticsearch/
> 
> This seems to be based off a similar version to the one James has on github,
> and the ~elastic-ops team you mention above is already a member of the
> elasticsearch-charm project.
> 
> We're using this charm on xenial successfully, so maybe it'd be worth trying
> to work together to get
> https://jujucharms.com/u/elasticsearch-charmers/elasticsearch/ as the
> promulgated upstream charm.
> 
>> @Simon / Bret:  you are on the ~onlineservices-charmers team that owns the
>> current promulgated ES charm.  Would you be willing to relinquish
>> maintainership to ~elastic-ops (and would you like to be members of that
>> team)?
> 
> I checked with some of the ~onlineservices-charmers team and they were happy
> for https://jujucharms.com/u/elasticsearch-charmers/elasticsearch/ to replace
> the current promulgated charm (which only supports precise and trusty). We
> should test that you can successfully charm upgrade from theirs to this charm
> (on trusty) - I'm happy to take that on, and will update here once we've done
> so.
> 
>> Thanks!
>> -Kevin Monroe
>> 
>> On Mon, Aug 14, 2017 at 12:12 PM, Rick Harding <[email protected]>
>> wrote:
>> 
>>> I'd also encourage you to test an upgrade path from the current charm to
>>> yours to help comfort any current users of the charm that if there's a
>>> change it'll go smoothly for users.
>>> 
>>> On Mon, Aug 14, 2017 at 1:00 PM Tim Van Steenburgh <
>>> [email protected]> wrote:
>>> 
>>>> Hey James, my point was that if you want to replace the existing
>>>> top-level ES charm with your own, we would need agreement from the
>>>> maintainers of the existing charm.
>>>> 
>>>> On Mon, Aug 14, 2017 at 12:45 PM, James Beedy <[email protected]>
>>>> wrote:
>>>> 
>>>>> @tim yeah ... possibly I'm not looking for promulgation then, and just
>>>>> need to push it and grant everyone because its already promulgated?
>>>>> 
>>>>> On Mon, Aug 14, 2017 at 9:29 AM, Tim Van Steenburgh <
>>>>> [email protected]> wrote:
>>>>> 
>>>>>> There's already a top-level elasticsearch charm.
>>>>>> https://jujucharms.com/elasticsearch/
>>>>>> 
>>>>>> On Mon, Aug 14, 2017 at 12:13 PM, James Beedy <[email protected]>
>>>>>> wrote:
>>>>>> 
>>>>>>> Request for promulgation of Elasticsearch. The Elasticsearch charm can
>>>>>>> be found at cs:~jamesbeedy/elasticsearch-7.
>>>>>>> 
>>>>>>> Thanks,
>>>>>>> 
>>>>>>> James
>>>>>>> 
>>>>>>> --
>>>>>>> Juju mailing list
>>>>>>> [email protected]
>>>>>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>>>>>>> mailman/listinfo/juju
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> --
>>>> Juju mailing list
>>>> [email protected]
>>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>>>> mailman/listinfo/juju
>>>> 
>>> 
>>> --
>>> Juju mailing list
>>> [email protected]
>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>>> mailman/listinfo/juju
>>> 
>>> 
> 
>> -- 
>> Juju mailing list
>> [email protected]
>> Modify settings or unsubscribe at: 
>> https://lists.ubuntu.com/mailman/listinfo/juju
> 
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 22 Aug 2017 08:54:14 +0100
> From: Tom Haddon <[email protected]>
> To: Kevin Monroe <[email protected]>
> Cc: James Beedy <[email protected]>, Juju email list
>    <[email protected]>
> Subject: Re: Elasticsearch Charm Promulgation
> Message-ID: <20170822075414.GA3024@tenaya>
> Content-Type: text/plain; charset=us-ascii
> 
>> On Mon, Aug 21, 2017 at 02:53:10PM +0100, Tom Haddon wrote:
>> [...]
>> I checked with some of the ~onlineservices-charmers team and they were happy
>> for https://jujucharms.com/u/elasticsearch-charmers/elasticsearch/ to replace
>> the current promulgated charm (which only supports precise and trusty). We
>> should test that you can successfully charm upgrade from theirs to this charm
>> (on trusty) - I'm happy to take that on, and will update here once we've done
>> so.
> 
> I've tested an upgrade on trusty from the existing upstream elasticsearch
> charm to cs:~elasticsearch-charmers/trusty/elasticsearch and it seems to work
> okay:
> 
> https://pastebin.ubuntu.com/25368096/
> 
> Thanks, Tom
> 
> 
> 
> ------------------------------
> 
> -- 
> Juju mailing list
> [email protected]
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/juju
> 
> 
> End of Juju Digest, Vol 79, Issue 18
> ************************************

-- 
Juju mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Reply via email to