Migrate backups to new backup01.ord.rax.ci.openstack.org
We decided to start fresh backups on the new server, so this is ready
to go. I have performed an initial backup on each server so it has
accepted the host key of the new server and been tested (I also fixed
up review-dev.o.o, which was rebuilt but keys not updated ... todo:
add this to puppet, but since it changes so infrequently not high
priority).
Change-Id: I0872f9fcf4a334d32f632b3cb04801deefab4fd1
This server doesn't exist any more and is stopping firewall rules from
properly loading on logstach-worker servers.
Change-Id: I0e4b30881b660c4dc903c97e5939a5888c0a7948
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
We are granting abandon permissions for release managers so that
changes on EOL branches can be removed.
Change-Id: I7486fead3d1066e0c45cd3a9c2ff1545849bd7e3
Add some documentation on reprepo, including some recovery techniques
gleaned from the battlefield.
Change-Id: I3368dedc1b9a769a1c8f5e8fe831d059ff23875b
We don't actually use this region any more, remove it so we don't
attempt to access it with dynamic inventory with ansible.
Change-Id: Ic6d4474a61ee32d198f4d70800fd79b8bd80623f
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
As part of the "Gerrit ContactStore Removal" specification, now that
owners.py is checking foundation membership when generating voter
rolls it's fine for us to stop using requireContactInformation on
the ICLA and rip out our accompanying configuration.
Note that this should not be merged until the All-Projects config on
review.openstack.org and review-dev.openstack.org has been manually
adjusted to remove the "requireContactInformation = true" line from
the [contributor-agreement "ICLA"] section therein. Further, this
must be done by pushing the necessary edit directly into
refs/meta/config as there is no WebUI control nor API method to
alter contributor-agreement options.
Change-Id: I8c39a6bf43f5b12db3e8aab18bedbf7e1a0f0b7e
Story: #2001094
Task: #4867
The app_key config entry for zuul actually wants a path to a file, not
the key content itself. Write it to disk and update the config.
Do the file writing in site.pp and not puppet-zuul because it's an
arbitrary filename/content. A zuul user could have zero or many github
connections, and the connection data is stored in a hash in hiera, so
there's not a super great way to add key writing support to puppet-zuul
itself at the moment. It's also a single file.
Change-Id: I43f93f59b9a82186a60734810a277edeac67bbac
We're running a zuulv3 and it has several pieces. Make a place that we
can start documenting the sysadmin of the system. Once we go live we can
remove the old zuul.rst and move zuulv3.rst to take its place.
Change-Id: I3efaa8026f9d1c67e765ca79594b2768f0fa2fbf
While adding the last patch, I noticed the comment from doug about the
entries missing from the TOC that were added to a hidden section. I can
see no reason for these to be hidden, so add them to the main TOC.
Also, there's a warning about an invalid ref in the firehose document.
Fix it.
Change-Id: I86663407356aca0cadd633122a0257ad63d0297c
In order to demystify some of the initial setup around IRC nick
registration for new bots, start a new section in the IRC
documentation page for a recommended workflow and gotchas.
Change-Id: Ica9f24b725cc2d4425741b383f788a537992f80d
This installs the ptgbot Puppet module so it will run from the
eavesdrop.openstack.org server and generate its Web content there.
Include some rudimentary operational documentation.
Change-Id: I92ddbbb683dede2c325f70267bd5e26884a35c01
Depends-On: Idb1fc5273b67ab88e1c78578275969b04c781c7a
We want to start encrypting our gearman traffic for zuulv3, as such
we'll need to bring online a CA service. The idea here, is we create a
new CA for each interconnecting service we want SSL certs for.
As an example /etc/zuul-ca will be used to generate SSL certs for our
gearman service.
Change-Id: I8c341559292c78d5428fe16837f28494a76e65db
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Co-Authored-By: Jeremy Stanley <fungi@yuggoth.org>
This commit adds docs on event notifications as an example use case.
This is a common thing that people want to do with firehose events, so
it's good to document how to do it. This commit doesn't go into detail
on how to use/configure mqttwarn (since it can be quite involved) but
points people at the docs.
Change-Id: Ic5fff993e5f268e2dbd82062b4fb95483d69abf2
Now that we are running puppet in masterless mode, we don't need to tell
nodes where the puppetmaster is, or what their certname is, nor do we
need to keep running the puppetmaster in Apache. This patch cleans those
things up.
Change-Id: I663af0d9948f2ce3a47cc22ada47c3bbbbf316fa
Our current version of project-config no longer needs to use this class
to build nodepool nodes. Third party CI systems will have to update to
the latest version of project-config to prevent his change from breaking
them.
Change-Id: I14a45e700b33cfcaebb7f6242ad00a010935e36c
Depends-On: Ib241ea976ca0a3d661599f36e3f5a2d4eb023c08
Depends-On: Ib1c2f6085f9e8b40e6a78cfb898738b0950bc339
This commit adds documentation for the ansible events we're now
publishing into the firehose. This includes full schema documentation
explaining the topics and payloads.
Change-Id: I85e27f1c27895c8c25bb34072481f4f75911d815
This commit adds schema docs for launchpad messages generated by lpmqtt.
Due to inconsistencies and the lack of a defined schema from launchpad
this doc reads a little non-committal, but that's because nothing is
a guaranteed coming from launchpad and consuming the messages will
require flexibility to accommodate that.
Change-Id: I9b4b1bc27f9bdf81a5fdc53e0969be46a3ded005
This commit starts a new page for documenting the firehose schema. Right
now it only includes the schema for gerrit events, but it will be
expanded in future patches to include the other services reporting.
Hopefully this will serve as a better guide for people to actually being
able to consume events from firehose.
Change-Id: I2157f702c87f32055ba2fad842a05e31539bc857
This class is not used anywhere, which we know because it includes the
openstack_project::base class which doesn't exist. We also remove,
rather than update, the documentation's reference to it because pretty
soon devstack-gate won't need the openstack_project module at all.
Change-Id: I44ac578af7c659adef614f73b250523d1acf09c4
