Remove the puppetry for managing nameservers as we now use ansible
configured name servers without puppet.
We will need to follow this up with deletion of the existing
ns*.openstack.org and adns1.openstack.org servers.
Change-Id: Id7ec8fa58c9e37ce94ec71e4562607914e5c3ea4
In preparation for rebuilding openstack.org servers in the
opendev.org domain, switch to Ansible inventory hostgroup glob and
Puppetmaster global site manifest regular expression patterns which
match both domains.
Change-Id: I0408a4452b5dcd5be2ad7ef73790eb1bf33b39b3
Remove the Ansible inventory and Puppet global site manifest entries
for the old review.openstack.org and puppetmaster.openstack.org
servers. These have been deleted.
Change-Id: I4bfc6cfe357ad6a499c10455c26ee2fb97713b7d
We believe the relative_priority change has altered our workload
such that we have smaller jobs starting more frequently. Since
job starts are limited by the executors, we have developed a backlog
and need another executor to relieve the pressure.
Change-Id: I98052e0135c7ee615f1f187b9d0a250cdd1ff178
Rather than be beholden to a dynamic multi-cloud process for data that
is mostly static, just pre-generated it and check it in to git. This
will remove the need to run the openstack dynamic inventory at all.
Change-Id: Ib5c38e9addc55201fd68cbe5f09684391686904e
The mailman puppet module is tested and seems to be working on puppet
4[1]. Turn on the future parser for lists.katacontainers.io, which hosts
fewer mailing lists than lists.openstack.org does.
[1] https://review.openstack.org/601464
Change-Id: Iea7fbabf7cee579dcd19d4deb4d7537ed1b13bd9
Depends-On: https://review.openstack.org/601831
eavesdrop.o.o runs a number of different sites and bots, so on the one
hand it is a slightly complex service, but on the other hand these
modules are quite simple and similar to each other. Meetbot, accessbot,
and statusbot have tests and seem to work fine on puppet 4. Ptgbot does
not have tests, but that's why we should try this out sooner rather than
later so we have time to correct any issues before the PTG.
Change-Id: Id1af4b3ebf04f34c381eab5f818815734a296f7b
We run a cluster of elasticsearch nodes which may have additional
servers added to it or old servers replaced. Make this slightly easier
by matching them with a glob in groups.yaml so that we don't have to
edit this file to add new servers.
Change-Id: I8ce3e38f67c545642d561b2afdd6dbbfa677e67f
We run many git server backend nodes which may be replaced with new
servers. To simplify the process of adding or replacing git0* servers
stop explicitly listing them in groups.yaml and instead match them on a
glob.
Change-Id: I3dbf814122bbfc508b2a90a5f5a533226fa0bf8f
We run a cluster of zookeeper nodes. Lets match them with globs in
groups.yaml so that we don't have to edit groups.yaml if expanding the
size ofthe cluster or replacing nodes in the cluster.
Change-Id: Iff9048a9bc15e4f888e7caab54abb4d4a9d340d7
Replace all the explicit listings of nb01, nl01, etc with globs so that
we can launch new nodepool builders and nodepool launchers without
editing the groups file.
Change-Id: I3c32fb604109a3c65b2145b733fc0e2545e21045
Match the mirrors with a glob so that we can boot new mirrors in new
regions or replacements in existing regions without needing to
explicitly add them to groups.yaml first.
Change-Id: I3e7bf04a2d3a7602e46710840b0cec42c238c6c1
Match logstash-worker and logstash.o.o nodes with globs. This allows us
to launch new servers without needing to add them to the groups file
first.
Note that logstash.o.o is currently hosted by logstash01.openstack.org
so the existing groups.yaml content is broken for this host.
Change-Id: Iea9b5815a31355925979e6d4da5c578a64af7972