We can use textwrap to break up the ridiculously long lines in the
logging configuration (with less images, it's less ridiculous than it
used to be, but it's still easier to parse). Only trick is to put
spaces between the arguments to give it somewhere to split (and better
for readability) and stop it splitting on words/hyphens.
Change-Id: I04840e98b0564dc531b74b96e8595f9d18b284af
This adds the centos7, debian-jessie and removes devstack-centos7-dib.
Change-Id: Ifcc8390b32713601fae98c96b761e313b7d2d6f3
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This change is related to https://review.openstack.org/#/c/292605/
its sets smtp configuration and email log error capabilities to both nodes
production/dev.
Change-Id: Ie4ae1379451059b525a07611867dd4d3f6d6a9ac
Clear out the meta-data provided by the rpm package, so pip does a
reinstall. Fix for If3f244ed4f62da25dc42813b4bda2f374f002517
Change-Id: Ic3bd801c0f57a2453d3563aaa4cf778aa0a9f9bf
As a follow up to adding #osic to accessbot [1], we'd like to add #osic
to meetbot as well.
[1] https://review.openstack.org/#/c/289557/
Change-Id: If590f16382b488ad85566952a89c5eb6adc284ac
In Ubuntu, the archive configures backports as something you must
explicitly request when installing packages. One does this by specifying
a package name of 'backports/$packagename'. But our reprepro mirrors of
backports do not have this flag set, and so, all systems get backported
versions of packages, instead of the one from the released stable
archive.
Change-Id: I8f266dc7045e971567ed934d1206c7b83cacd178
Now that we are running logstash 2.0 the logstash daemon can talk to
elasticsearch directly and load balance across the cluster. This means
we don't need a local elasticsearch daemon to do that for us. The big
savings here is in memory so stop installing and running elasticsearch
completely on the workers.
Note this will not uninstall an existing ES install you will need to
clean that up if a preexisting install is present.
Change-Id: I9b622674a74a26e7c3024e684e05291f43aec021
The old logstash config was not ruby 1.8 compatible and we got funny
results out of it. This version should work with ruby 1.8 and beyond.
Change-Id: Ibe824dda7c96e5b333329ce25f65a14d3ebdef9c
Configure routers and transports for storyboard based on
Mailman-style VERP addressing.
Messages accepted on the localhost interface with a sender address
matching "*-bounces@" (eg, "storyboard-bounces@storyboard.openstack.org"),
will be sent out with VERP addressing (eg
"storyboard-bounces+user=example.com@storyboard.openstack.org). This
way storyboard can perform bounce processing on messages it receives
back to that address.
Messages addressed to either "storyboard@", "storyboard-bounces@",
or "storyboard-bounces+user=example.com@" will be delivered to storyboard
by calling the '/path/to/storyboard inject $localpart' command.
Storyboard may then parse the message as appropriate.
Change-Id: I854006c19b22b233bae5017e4ad04c10a37e0adc
Depends-On: Id4f69580eb126d058ee699f4e7bfdb01cfc7409c
Logstash 2.0 defaults to HTTP elasticsearch output which means that the
elasticsearch output (no _http) does HTTP and a new elasticsearch_java
output exists if you want to continue doing the native api output. We
had been doing HTTP so just need to update the output name. The host
parameter is also deprecated and you must pass an array to the hosts
parameter instead so update that as well.
Note that this switches from using a local ES daemon to talking to the
cluster itself directly because new logstash is able to load balance
over http. This reduces the overhead necessary to have resilient ES
connections.
Note this is not compatbile with Logstash 1.3.3 which is what we are
currently running so this change should only go in as part of an upgrade
to Logstash 2.0 and beyond.
Change-Id: I788ecb936f9fa5a006332ed626f90c33a255d9bf
We have a playbook that does the logic of setting the hostname. Rather
than implementing that logic in launch-node - just use the playbook.
Change-Id: I1a6c0ff12803bdac35631cb3bb2c8fe70cbd1904