Re: Elasticseach Charm Promulgation - things to keep in mind

2017-08-30 Thread James Beedy
Also - https://bugs.launchpad.net/elasticsearch-charm/+bug/1714126 On Wed, Aug 30, 2017 at 6:47 PM, James Beedy wrote: > Elasticsearch >= 5.x is non-compat with kibana <= 5.x. The current default > configs for https://jujucharms.com/u/elasticsearch-charmers/elasticsearch > may break any bundles

Re: Elasticseach Charm Promulgation - things to keep in mind

2017-08-30 Thread James Beedy
Elasticsearch >= 5.x is non-compat with kibana <= 5.x. The current default configs for https://jujucharms.com/u/elasticsearch-charmers/elasticsearch may break any bundles that have elasticsearch + kibana not pinned to a specific charm store uri/rev upon promulgation. This probably won't affect man

Re: Elasticseach Charm Promulgation

2017-08-24 Thread Haw Loeung
Hi James, On Tue, Aug 22, 2017 at 09:31:05AM -0700, James Beedy wrote: > @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 p

Re: Elasticseach Charm Promulgation

2017-08-23 Thread Tom Haddon
On Tue, Aug 22, 2017 at 09:31:05AM -0700, James Beedy wrote: > @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 > upst

Re: Elasticseach Charm Promulgation

2017-08-22 Thread James Beedy
@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, ju