Comment 4 for bug 1553256

On Fri, Mar 4, 2016 at 4:20 PM Charles Butler <email address hidden>
wrote:

> Michael - so i actually updated the ElasticSearch charm to work for ES2
> deployments.. there was just some config file twiddling that needed to
> happen
>

Hey Charles. I'm not sure if I'm missing something, or maybe it wasn't
clear what I wrote above, but you can't just update the existing trusty
elasticsearch charm to use elasticsearch 2 - at least I don't see how. I
mean, it's easy to update it and have it working for demos, but it's not
easy to update it and expect current elasticsearch deployments to survive
an upgrade-charm - unless you've done some pretty amazing work (which I'd
be very happy to see :) ).

>
> cs:~lazypower/trusty/elasticsearch (theres some ACL shenanigans going
> on here at the moment, sorry - i'll re-ping when its resolved and you
> can actually SEE the charm)
>

If that's just updating to use elasticsearch 2, I'd recommend the separate
elasticsearch2 charm I linked to above (I'm using it in production).

>
> Are we abandoning the ElasticSearch charms and moving to this es2 charm?
>

No - but it's stable. I'll keep fixing bugs etc on the elasticsearch charm,
but I don't personally see a way to upgrade-charm on an existing deployment
to run Elasticsearch 2. Let me know if you've solved that though...

Thanks!