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
https://github.com/ansible/ansible/pull/14882 landed, so the inventory
will understand that an empty cache means the inventory needs
refetching. Zero out the file, and start consuming inventory from the
master branch of ansible since mordred controls that file anyway.
Change-Id: I2a4f4b21c50bfa94a229dd109e3d21f47552f0a1
Shade supports all of the TODO items in here now, so use it. Also,
we have ansible playbooks that do the work of running puppet - and since
we're on puppet apply now, we can use them.
Change-Id: I6f57e9a31bf835ef2e22db1f5531d92e99806cf4
In order for individuals to be able to run launch node commands without
becoming root, make these group owned and group writeable by admin.
Change-Id: I0a2fa336919be24d41a6a9c0a88b91a87536cbcc
Running puppet remotely in an ad-hoc manner on disabled hosts is mildly
complex. To facilitate, have a wide open playbook that we always run
with --limit - and a shell script to help us type less.
Change-Id: I629072dcada38d0465d351b1b99828466405372f
This is no longer needed as pabelanger is now an infra-root.
Change-Id: I6939c2ee9e3662c08441dd0ddad3e84a47bd0192
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Due to the possibility for multiple OSIC clouds we need to distinguish
between them in our clouds.yaml. Do that now before it becomes a problem
later and refer to the current cloud as osic-cloud1.
Change-Id: I3f35db2911a44200f0486e71fc215d021aa7c227
The max-repo-count setting in the cgitrc adjusts how many repos should
be displayed on each page. In the puppet-cgit module we have a default
of 600, which was intended to be enough for all the repos to be shown
on git.openstack.org without a second page. We're now at over 1,000
repos, so you now need to page through them and this is not an optimal
experience. Since cgit can handle loading thousands of repos on the
main page, add the setting to our local configuration and bump it up
to 1500.
Change-Id: I7a2ea185f0876806ecfd17bedd84dbcd9769b124
After switching to ubuntu-trusty and project that use
other-requirements.txt for bindep, log uploads will fail. So rather
then forcing all projects to include curl in other-requirements.txt,
we'll install it with puppet.
Our entry point is ::openstack_project::single_use_slave.
Change-Id: Icade064bd32c2179836f4d1c3d2ec91425422d02
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
