Using the puppet 4 future parser it is far more particular about
variables and their scoping. We don't set a serveradmin in this class
but then attempt to use it in the vhost template. This was fine under
puppet 3 as it would just look for this out of the current scope but
breaks under puppet 4.
Make this trivially happy on puppet 4 by setting a default that is sane.
Change-Id: Id415056cdfa693fd199e0b4a0c6b09e20faf23ef
We need to use Require all granted in our directory that hosts the
Kibana files otherwise we get 403 forbidden when trying to access the
content.
Change-Id: I2e14ba113705f3fabaa4920704589da0f9abe978
The kibana apache vhost file makes use of mod rewrite and mod proxy but
we don't enable those modules explicitly here. We happen to enable them
in other places that use this puppet module but that leads to races and
isn't explicit enough. Go ahead and explicitly enable the deps in this
puppet module so that it is self sufficient.
Change-Id: Ic05f26d61f2ac4b5adffee98782d1a02931d5731
The ruby version of Kibana reached its end-of-life in May 2015, remove
support for it from this puppet module.
Change-Id: I164ab9228e8ac8ada95d1ce2c0ee809cc01c9aa3
Order and intendation of those parameters are changed
to follow Puppet Style Guide recommendation [0].
Moreover, it will allow to an user to find much faster
a variable in a list of variables.
[0]. https://docs.puppetlabs.com/guides/style_guide.html
Change-Id: I7bd6abf2bc6b10da52fb4dad0c238b7b59cec54b
/opt/kibana was being chowned to 'kibana' on every run, but
/opt/kibana/<git_version> was a vcsrepo that was being checked out as
www-data. This caused a changed file resource for every file in the git
repo for every puppet run, causing a bunch of noise in the logs and
eventually running the puppetmaster out of disk space.
Also changed directory mode to 755 because 644 doesn't make a ton of
sense.
Change-Id: I3cc511c4a5ae561ec30478d96d9745611d4b5b65
In order to make Share work without relying on elasticsearch write perms
we patch dashLoader.js to construct the urls based on the logstash
dashboard since it is deterministic anyways. This is a massive hack but
maybe it will be less terrible once ES is upgraded and we can use
kibana4.
Change-Id: I64cc693e5e188c68e134b4769ccc519f6191f36c
We update the default logstash dashboard to remove excessively short
refresh period options, default the query result listing output to
be timestamp and message, default to a 15 minute query instead
of a 24 hour query, and default to a blank query instead of '*" because
the '*' forces you to delete it to add any new queries but they are
functionally equivalent.
Change-Id: Id68a1f1e496f5d729b21aa2be30a5e2b73ab65fd
Add support for the javascript version of kibana.
By default, this is done by serving both the kibana and also an
elasticsearch proxy from the same location. Allowed GETs and POSTs
for read-only access to elasticsearch are passed to a proxy and all
other requests are served from the kibana source directory.
An optional prefix, such as 'elasticsearch/', can be specified in which
case the reverse proxy to elasticsearch will be served from this
sub-path.
Change-Id: I13f9dff0bbd6498a36dc75b026c9042a9bb05e8f
In anticipation of puppet 4, start trying to deal with puppet 4 things
that can be helpfully predicted by puppet lint plugins. Also fix
arrow alignment errors not caught before.
Change-Id: Ie4df1a6316f10989af653d74aef5306bb79a8870
Version 0.2.0 doesn't exist on that repository.
It looks like the old kibana repo was renamed to kibana2 and then the
new kibana3 repo was renamed kibana.
Change-Id: I2c703fab5e802584eaea5e6dc51d5ea3cf8d84ff
Use mutliple discover nodes to determine elasticsearch cluster
membership. Put a timeout on recovery starting instead of the default
to recovery immediately. Describe cluster topology in elasticsearch yaml
config so that it can make smarter decisions. Round robin kibana
requests across each discover node.
Change-Id: I08ef9dd158ddf6a6ce01dfb2050626f543d45b10
Reviewed-on: https://review.openstack.org/34106
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Approved: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
We need to expand our elasticsearch install base. Update puppet to make
this possible.
Change-Id: Id0dae839b12ebf47715cf40a363832e0f661a94f
Reviewed-on: https://review.openstack.org/33910
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Approved: Clark Boylan <clark.boylan@gmail.com>
Tested-by: Jenkins
The new elasticsearch server needs to be able to connect back to
logstash over the elasticsearch ports. Also make kibana talk to the new
elasticsearch server.
Change-Id: I88af40c7885b263fcef5ff16210f073cd0a696a5
Reviewed-on: https://review.openstack.org/30354
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Approved: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Tested-by: Jenkins
Add a kibana module that installs kibana and flat configuration files,
and also disables the previous boring bland web frontend.
Change-Id: I772c66f07d2bc3a88128e101074be9d4162e3f8a
Reviewed-on: https://review.openstack.org/27089
Reviewed-by: Jesse Keating <jesse.keating@rackspace.com>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Approved: Clark Boylan <clark.boylan@gmail.com>
Tested-by: Jenkins
Clark Boylan