Comment 30 for bug 822979

fwiw, i've been using your es charm as part of a trusty stack, and wanted
to relay a few findings. first i'm not sure what the hold up is on pushing
this forward, the extant elasticsearch in the store is pretty broken for
non-ec2 and is suboptimal by using config to workaround lack of
implementation of relations.

also i realize its inherited (and complete baggage) but its unclear what
the distinction is between rest and cluster, they both seem to be identical
forms of provider side access via http. one of them should get dropped, are
both actually in use. also you've added a website / http relation isn't
conveying port which is a required part of that interface communications.
also missing a charm icon (i'd just grab the one off trunk).

On Mon, May 26, 2014 at 4:36 AM, Michael Nelson
<email address hidden>wrote:

> On Mon, May 26, 2014 at 9:26 AM, Michael Nelson
> <email address hidden> wrote:
> > On Sat, May 24, 2014 at 12:04 AM, Matt Bruzek
> > <email address hidden> wrote:
> >> Hello Michael,
> >>
> >> I tried using this branch on our enterprise servers that have a more
> >> limited networking (to simulate customer production environments). The
> >> install hook failed getting the GPG-KEY from elastsicsearch.org. Would
> >> it be possible to edit your code to check for the elasticsearch.tar.gz
> >> (or .deb) in the charm first and use that to install?
> >>
> >> This is a feature the current version of the elasticsearch charm that
> >> enables the charm to install on a limited network environment that could
> >> not reach elasticsearch.org.
> >
> > Hi Matt,
> >
> > I can do that, sure. FWIW, this branch was previously supporting
> > install of a local package, but we removed it when adding support for
> > a local repository. So assuming you're dealing with a limited network
> > environment without access to a local repository from which to install
> > elasticsearch and/or other packages, I'll add it back as an option.
>
> Just to be explicit, when we're deploying this in our restricted
> environment, the options we have set are:
>
> options:
> cluster-name: whatever-name
> install-ansible-from-ppa: false
> apt-repository: deb http://our.private.repo/ubuntu precise main
> apt-key-url: ""
>
> It might be worthwhile ensuring that if a non-default apt-repository
> is set, the apt-key-url is defaults to "" rather than the normal
> default at elasticsearch.org.
>
> --
> You received this bug notification because you are a member of charmers,
> which is subscribed to the bug report.
> https://bugs.launchpad.net/bugs/822979
>
> Title:
> Charm needed: Elastic Search
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/charms/+bug/822979/+subscriptions
>