This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I649dc632aeca673a6d09db3d3d426fdf16eaf984
The logic in the Gemfile was relying on Zuulv2 variables to find out
whether the spec helper gem was already available on disk, and since
Zuulv3 has changed things it was failing to find it and downloading the
master version instead. This patch ensures the Gemfile looks for the gem
in the right place when running in CI.
Change-Id: I6efe6cc34950e382656e39b579ff57566ed1e91a
Instead of keeping a local copy of spec_helper_acceptance.rb and
requiring updates to all modules for any change, we can move it into the
common helper gem and require it from there. This will make it easier to
create and review changes that affect all puppet modules. Also change
the Gemfile to look for the gem in the local workspace if running in a
zuul environment.
Change-Id: I20bf542923065f7790993e29938c71bfc189e447
We do not need to check every package and file with beaker. It is safe
to assume that if puppet ran successfully then it also was able to find
and install every package and was able to apply every config file.
We still keep the service checks because it is possible for puppet to
declare a service to be running successfully only for it to die later.
Change-Id: I313fe7907b165e4c064cc37cf0c75051aabf103e
Add a params class so that puppet can distinguish between JRE packages
on different Ubuntu releases.
Change-Id: Ia1d22379d915d347c549c8cb8785920d97470f06
Add a xenial nodeset and update the spec helper to install puppet 3 from
the Ubuntu repos instead of from puppetlabs.
Change-Id: I2a590ac0d8eecfcd964cd7ffd1a6bdb540815cb9
The puppet syntax check complains about the '\%' in the cron command
string, but the % still does need to be escaped for the cron to work
properly. We double escape it here in the puppet string which will
result in a properly single-escaped command string in the crontab.
Change-Id: I3d97463a611c43ded12ddb788e9da5e13466e0c5
The logstash::indexer no longer sets up the mqtt output plugin for
logstash. So we don't need to keep the options around to enable it and
write the create the cert file. This commit removes those pieces.
Change-Id: I6ebdb5dc8fea8309609d837a758eeaf1dc5ee760
Depends-On: I6becec12604c61fe50d3e6b9c7ed9f9e9be311ae
The logstash mqtt plugin caused issues in production and we're not going
to use it. We'll be emitting mqtt notifications directly from the
gearman worker instead. So this commit removes the plugin install so we
can set enable_mqtt to true to install the cert.
Change-Id: I0a17444cce18dd4b63f1f924e393483f6d8fe8eb
Hopes are this fixes the bug where logstash stops processing events and
ends up stalled out requiring forceful stoppage. Has been running
successfully on logstash-worker01 for almost a day now.
Change-Id: I62f311c33d8f31f26baee887881d6b672b0f2916
This commit adds support for configuring the mqtt logstash output
plugin. This will enable us to push events from our logstash workers
to firehose.o.o. The plugin can be found here:
https://github.com/kompa3/logstash-output-mqtt (althought it's README
is from a template and you have to look at the inline docs for how
to use it)
and the gem is published on rubygems.org here:
https://rubygems.org/gems/logstash-output-mqtt/
Change-Id: I7255f6c256ab3e3ca33caf69b71bf4ffab02c1bb
elasticsearch-curator 4.0 introduced completely new everything. It will
take some work to support it and all of the new features so pin to 3.5.1
for now. This will keep index deletes working while we add the support.
Change-Id: Iea4e8794d2b953cfdd59ff7907420dffb3de4dff
There is a puppet kibana module now that configures apache for us so we
don't need to do that here. Remove the redundant config.
Change-Id: I9e25c637b645f28b167bf248ee213608a1dfe615
Depends-On: Ic05f26d61f2ac4b5adffee98782d1a02931d5731
When we switch from a single config to split configs, make sure the old
config is removed. Leaving it in place prevents logstash from starting,
since we have multiple inputs attempting to listen on the same port.
Change-Id: I12e9da295e892ec70bcd9717fbdc0526b0822b86
Add in proper support for conf.d configs. Create input at 00-input,
output at 99-output, and filters at user specifiable levels in between
using a new defined type for filters.
Co-Authored-By: Jonathan Harker <code@gentlydownthe.net>
Change-Id: Icbca7a6ba0c5a94a273ef158f707311b588483fd
Now that we install logstash 2.0, and its package manages service files
and user creation, update our beaker tests to reflect these changes.
Also, the logstash deb depends on the logrotate package, so make sure that's
installed.
Depends-On: Id50f98459b677460c28772c406c86482dcd0e9e4
Change-Id: I4c062c82d8d0aae5dd27036021a9464d788244d1
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: I4457f7c6dd3cfca24084a252f360c45d1aa2b2d7
This makes a whole host of changes. First we install logstash from the
deb packages that are now available. This package sets up the logstash
user, group, logrotate for log files, a conf.d dir, and an init script
for a service for us. This means all of that stuff can be removed from
puppet and be provided by the package instead.
In addition to cleanup related to the package we remove things that no
longer make sense with newer logstash. There is no more logstash web
service for example use kibana instead. Also the distinction between
agent and indexer is no longer strong and logstash has a separate
shipper tool which should be used in place of the agent (though backward
compat for the agent class is preserved by setting it up as an indexer
using an agent config).
Depends-On: I2354fbe9d3ab25134c52bfe58f562dfdf9ff6786
Change-Id: If3fa423a80a03d09993e58f6d68a3a212b457468
The curator project manages elasticsearch indices, with knowledge of the
naming format used by logstash and the ability to delete indicies
matching a given pattern.
Needed-By: Iba3c0726b789dcbcf58f2da071e6fa93d4cd67ae
Change-Id: Ic49c8649a0ad849a8d72900425e589e40b82a37f
Add acceptance tests for puppet-logstash module so that once the module
is applied we check if files were created, packages were installed and
users configured.
Co-Authored-By: Bruno Tavares <btavare@thoughtworks.com>
Change-Id: I0332e9caf732ab8874cd444a9faa42143d40e335
Use same target directory for zuul-cloner and
the regular git command.
Change-Id: I5f7667a2bede9ed5eb3979103891587d3df1ae12
Co-Authored-By: Fabien Boucher <fabien.boucher@enovance.com>
In anticipation of puppet 4, start trying to deal with puppet 4 things
that can be helpfully predicted by puppet lint plugins. Also fix lint
errors caught by the puppet-lint-absolute_classname-check gem and arrow
alignment errors not caught before.
Change-Id: Icb76cc5019c378524344640e9670229e142a9627
puppet-httpd is the openstack-infra version of puppetlabs-apache
(0.0.4) release.
This patchset will remove the puppetlabs-apache namespace from -infra
allowing for possible future patchsets to use newer puppetlabs-apache
modules.
Change-Id: Idff8228de0a5c309b02d95feb6e6f25aafaa5f2a
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
The http://ci.openstack.org/ documentation site has been deprecated,
replaced by redirects to corresponding paths within
http://docs.openstack.org/infra/ where other Project Infrastructure
documentation already resides.
Change-Id: Ic9151804ffca5903969c44ca0465645b4d6fc1ea
Over time this logfile can grow quite large filling disk. Rotate it
daily and keep one week worth of logs to keep a reasonable amount of
logs.
Change-Id: Ic5f3acf290d3febc8af83773eb120df774937f1b
Add a missing parameter into apache inclusion,
that was causing vhost_name to don't be passed properly
and generating the vhost incorrectly.
Change-Id: Ia39c005fffb82b5f1d75ac704cf24a1a2a978d6d
In the past it was common to do scope.lookupvar but now it is only
required when explicitly grabbing a different scope. All the
variables in kibana.vhost.erb are available from the class that
calls the template() function.
Change-Id: I100bb764b5742b1f3068e5b86813c825f9f71868
We need puppetlabs-apache 0.0.4 for this module. We will, hopefully,
soon move this and other modules on to openstackci-httpd.
Change-Id: I27546066cb071eb942bd669434483c5bdd77fb24
The strange looking syntax the head-of-file docs are in is in
compliance with the new puppet-strings system for inline documentation
This enables neato stuff like 'puppet string <modulename>' to get docs
on the command line, and generating html, which we could then ship to
somewhere.
Change-Id: Icb0be2c733e4d3ee6beff32780c171b9f750b06f