We want our base ansible roles to run on these nodes. However,
k8s-on-openstack manages firewall rules via openstack security
groups, so we don't want to run those there.
There was a discussion about making a minimal set of roles that
are run by default and then a group containing servers that got
the full set ... but that would require a duplicate entry for 99%
of our servers in the inventory, while the "only run a subset" is
the exception case.
Change-Id: I2cbf364305f758cecf11df41398d3d2c05222fda
In order to support different instance names for the OpenStackID
servers, create Ansible inventory host groups for them. Add the
group name for the production server to the Puppet global site
manifest like was already done for the dev server. Also adjust the
production server node name regex and globs to support an enumerated
naming pattern in the openstack.org domain. Finally, fix a benign
missing backslash in the openstackid-dev node name regex for
consistency.
Change-Id: Iaa30f2fa2c196ad84a8ac18b48b7390b1f4905b9
The old Trusty-based storyboard-dev.openstack.org server has been
replaced by a new Xenial-based storyboard-dev01.opendev.org
instance. As the original is being deleted, remove it from the
inventory and tighten up our hostname match patterns accordingly.
Change-Id: I9805381ebd640c8d5aeb3012e9ebe8448eaf5a3b
Use group variables and a node name pattern to divorce the
openstackid-dev service from the instance name of the server which
provides it. Also update the inventory matches to be consistent with
the pattern in the global site manifest.
Change-Id: I335f7ebaa5a446a83a4725bbcc0240f91cd14341
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
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
