This list is basically unused, and its owners/moderators have asked
for it to be shut down. Once this merges (so that Puppet won't
recreate it), the list can be removed with the `rmlist` utility
(this will still leave the archives available but will remove it
from the list index and no longer accept subscriptions/posts).
Change-Id: Ieaf35b1e6875b26b6c20da8a9e9c2eedf200eaf8
Similar to the pinning introduced in
Ic465efb637c0a1eb475f04b0b0e356d8797ecdeb, use the "latest"
openstacksdk package and allow for passing of pinned versions if
required.
Update the devel test to also use the master of opensatcksdk
Change-Id: I4b437ca9024c87903bdd3569c8309cde725ce28e
This adds arguments to "install-ansible" to allow us to specify the
package name and version.
This is used to pin bridge.o.o to 2.7.0 (see
I9cf4baf1b15893f0c677567f5afede0d0234f0b2).
A new job is added to test against the ansible-devel branch. Added as
voting for now, until it proves to be a concern.
Change-Id: Ic465efb637c0a1eb475f04b0b0e356d8797ecdeb
Similar to run_all.sh (I299c0ab5dc3dea4841e560d8fb95b8f3e7df89f2),
produce a runtime stat for each run of the cloud launcher.
Although it won't directly highlight errors, problems tend to end this
playbook early. When graphed with grafana, we could have noticed a
large drop in the average runtime which would have suggested a
problem.
Change-Id: I8e5371cbc94e9a803ea5e64ae94aca293b834c73
The default of 8 processes does not appear to be sufficient to handle
the concurrent requests for openstack's log analyzer and ara
simultaneously under load.
Change-Id: I928fcbcc670c68bfb7b206949edca1a5e6daf35a
These names were taken from the citycloud web interface RC file, but
actually match what we already have in
playbooks/templates/clouds/nodepool_clouds.yaml.j2
Testing with this I can authenticate to openstackzuul-citycloud
Change-Id: Ic7aeb5c3a96e5594b8c9c396daaad7e79c1f5c63
It's designed to always be used from the latest version.
This trips an ansible lint rule (ANSIBLE0010) which we can ignore, as
we often have pip things that we want to install the latest release
of automatically.
Change-Id: Ieac93ab3a555f2423d4fbcf101d6d9681ae0e497
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
Convert ze01, ze02, ze03, etc to ze[0-9]* so that we can launch new zuul
executors as necessary without updating the groups file.
Change-Id: Id9896e89d8bc821de003994a96ae11517a76145d
The zuul mergers do not run a webserver so we remove them from the
webserver group. Convert zm01, zm02, zm03, etc to zm[0-9]* so that we
can launch new zuul mergers as necessary without updating the groups
file.
Change-Id: Ibe8cbea02990378f4ee5ba7880ee0c8a4e9b7bb9
We removed the mirror nodes from the webservers group to fix iptables
rule application on the nodes. Unfortunately we didn't update our test
that tries to assert mirrors should be in the webservers group. Update
the test results fixture to remove webservers as a valid group for a
mirror node.
Change-Id: Iba18e54f4df4a36c0247f65642faacca9d195769
The webservers group is meant to be mutually exclusive to any other
iptables modifications but was inadvertently expanded to include the
mirror servers by Iea8b2eb2e9c723aca06f75d3d3307893e320cced. Remove
the glob as it should not be there and is overriding the
mirror-specific firewall rules.
Change-Id: Ia1b702e5c9a2d433536edcec4bfaf6f47b1c0291
Our etherpad servers now have digits so we need them to have digits in
the groups file. Also we have etherpad-dev group_vars that are different
than the etherpad group_vars values so add a group for etherpad-dev to
ensure the correct hiera data is used on the dev server.
Change-Id: I9e34ef7969b8a562192a29d98ead6fc55f71d5f2
This mocks out enough of the Ansible inventory framework so we can
test the group matching against a range of corner cases as present in
the results.yaml file.
Change-Id: I05114d9aae6f149122da20f239c8b3546bc140bc
The constructed inventory plugin allows expressing additional groups,
but it's too heavy weight for our needs. Additionally, it is a full
inventory plugin that will add hosts to the inventory if they don't
exist.
What we want instead is something that will associate existing hosts
(that would have come from another source) with groups.
This also switches to using emergency.yaml instead of emergency, which
uses the same format.
We add an extra groups file for gate testing to ensure the CI nodes
get puppet installed.
Change-Id: Iea8b2eb2e9c723aca06f75d3d3307893e320cced
We've only been using nodepool.o.o as a zookeeper server for the past
year or so. Last week we transitioned to a three node zookeeper cluster
and stopped using nodepool.o.o. This server has since been deleted.
This is the last bit of cleanup to remove it from config management.
Change-Id: I9d0363393ed20ee59f40b210ea14fb105a492e20
It seems that the package module doesn't have a default value for the
state of a package. So not specifying it is essentially a no-op. Specify
state: present so that we really get the packages installed that we want
to have.
Change-Id: Ied9484c74922b9f48e14205b73ca95066a68a87f