This is the connection for Gerrit's Gerrit. We can connect to it
directly with the Gerrit driver now that we support entirely
HTTP-based Gerrits and we have an account. Use that so we can
set up some third-party CI testing.
Change-Id: I7b91b4e67594ce62772e3e450a1236095d4ef1c9
This reverts commit 01bef804de2d65f9ce4cda80e937a718c7ee7628.
This was missing an option, and also our password doesn't work.
Change-Id: I317c29034efaae62ea74a5c16ec25bed98c1e3cc
The #openstack-election IRC channel is used in the execution of
official OpenStack project duties involving technical elections, so
should be publicly logged. Also, its denizens would appreciate
receiving infrastructure status updates, as these may impact their
activities.
Depends-On: https://review.opendev.org/682440
Change-Id: I54a2feed3cf7265d700082f3ce04b82aa36e56e5
Analysis of IRC channel logs indicates the following have seen 5 or
fewer non-bot comments posted in the past 12 months and are likely
of no value to continue logging:
5 #openstack-vpnaas
2 #swift3
2 #openstack-ko
1 #openstack-deployment
1 #midonet
0 #openstack-valet
0 #openstack-valence
0 #openstack-swg
0 #openstack-mogan
We're currently at Freenode's 120 channel maximum, so remove them
from logging and free up available slots for new channels which wish
to have logging added. In addition, the Neutron team has asked to
have #networking-sfc and #openstack-fwaas removed from logging as
those channels's discussions are being folded back into
the #openstack-neutron channel now:
http://lists.openstack.org/pipermail/openstack-discuss/2019-September/009480.html
While we're here, go ahead and remove the same channels from the
statusbot configuration if they're listed in it.
Change-Id: If1f65be378fa247014e175c75e1562d4755ef497
This is the connection for Gerrit's Gerrit. We can connect to it
directly with the Gerrit driver now that we support entirely
HTTP-based Gerrits and we have an account. Use that so we can
set up some third-party CI testing.
Change-Id: I10e279218de985a0c17ea6b5bc46f3eebefcfb39
This change will add our IRC bots to the newly formed Ansible SIG,
in addition, it removes #dox in order to stay within the 120
channel limit.
The dox project has not seen a commit in 2 years and the channel
is pretty much empty/abanonded.
Change-Id: I3acd3cb77a9f71eb80921f4cbf2162113f40efea
This mirror will be manually configured with kafs (see
https://review.opendev.org/623974). This should be a nice distant
geographic counterpoint to the IAD RAX server.
This will need to be manually configured with a custom kernel for now,
but fixes are making their way upstream and this host will be
converted when available.
Depends-On: https://review.opendev.org/667529
Change-Id: I6a22933029c096c781c93c33e6edf03bf59223c9
This removes the groups servers from our inventory as well as our
manifests/modules. We don't run the groups service anymore as many
groups migrated to meetup.com independent of us and the others have
transitioned there.
Change-Id: I7cb76611e6d30e7189821923f36a38dec9ea7241
The server has been removed, remove it from inventory.
While we're here, s/graphite.openstack.org/graphite.opendev.org/'
... it's a CNAME redirect but we might as well clean up.
Change-Id: I36c951c85316cd65dde748b1e50ffa2e058c9a88
This reverts commit 0cddc2ae9b23a6d44ff6e0761c70126dc0923970.
This server is going to remain in the openstack.org domain.
Change-Id: I0d5a4f1e07d9782085bdbe875f466c564b1c681c
This adds a new xenial health api server to our inventory. This server
will be used to replace the old trusty health.openstack.org server.
Change-Id: Id6cf8230f82464c4466692cac324a1e39ba595af
This change will convert kdc03 to a master from a hot standby and will
remove kdc01 from management.
Cutover plan:
Disable kdc01 in ansible emergeny file
Stop run-kprop cron on kdc01
Stop kadmind on kdc01
Execute run-kprop.sh on kdc01
Merge this change
Wait for puppet to convert kdc03 to the master
Confirm that run-kprop works from kdc03 to kdc04
Update dns records as documented in our kerberos docs
Test kadmin works
Delete old kdc01 server
Change-Id: Ib14b11fa1f0a6bc11b0f615ce5b6f6be214b5629
This new Xenial server is being added as a kerberos standby node but
will be used to replace kdc01 as the master once fully configured and
happy as a standby. This replaces the old trusty server.
Note that the server wasn't added to opendev.org as we don't have a
kerberos realm for that domain so that would be a separate activity for
the future.
Change-Id: I4cc5fcd7504c98a7bcd9dc4f2ad57bb5bf8b54bd
The Xenial replacement for the old openstackid.org server is
openstackid01.openstack.org. Now that it exists, add it to our
Ansible inventory and cacti host list.
Change-Id: I198f02907230655bfc4e374a540648e9f1b7cf5f
Update the docs, test flags, cacti entries, and inventory for our new
pbx server. We have replaced the old Trusty node with a Xenial node.
Change-Id: Ifb1e156afbcb38474cbc9f0bc78ae45fdd74444b
Now that both staging and production storyboard servers are running
on enumerated Xenial servers in opendev.org, remove the old
inventory entry for the production server, clear out testing hints
for trusty and tighten up the inventory globs and node regular
expressions accordingly. Also get them swapped into cacti in place
of the old production server entry.
Change-Id: I5e66abb95751f69a337434e08d09dcc3b107e123
We are currently well under our rate limits for github and logging the
rate limit adds a number of requests to github for each github event
processed. This can be reenabled if we suspect rate limit based
failures, but until then let's reduce the number of requests and
simplify our logging.
Change-Id: I02878f9749737d297680cd324d6dafeefc44a005
Puppet4 is a lot more picky about scoping of variables. In our hiera
lookups we rely on the $group var to specify where to find hiera data
files, but this group var is set on a per node basis. This means that
top level hiera lookups produce warnings like:
Undefined variable 'group';
(file & line not available)
And lookups will break if they need keys in the group/node specific data
files.
Avoid this problem entirely by removing top level lookups. We only had
one for our elasticsearch_nodes var which we can easily set statically
in site.pp and not rely on hiera for.
Change-Id: Ifa3740f0f31c3fa9a2d8faa355101d3a5671afff
This causes a massive sad for zuul, resulting in ability to clone
the repos and indefinitely hung job.
Change-Id: I96b2bd883b63079f5032c5715960c25b61940f16
So that we can make gerrit build jobs using zuul to do the cloning
and not git modules inside of the jobs themselves, add gerrit's
git server as a git driver source.
Change-Id: I4a64e6627805d568030d3864f3d331a4e8f9ab8b
Since meetbot can only be on 120 channels, let's free up
two valuable meetbot watch slots by consolidating common
meeting channels.
We have no meeting happening in #openstack-meeting-cp nor
in #openstack-meeting-5 right now. With some IRC meetings
having moved to team channels, we have a lot more available
slots in the other "common" meeting rooms.
Additionally, to make it clearer that those channels are
abandoned, we should probably set up a topic/redirection so
that people do not needlessly hang out there (those two
channels never gathered a large group of lurkers anyway).
Change-Id: Ibf77bc6dc857f0e80c2c737523f66eadd659586a
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
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
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
In order to talk to limestone clouds we need to configure a custom CA.
Do this in ansible instead of puppet.
A followup should add writing out clouds.yaml files.
Change-Id: I355df1efb31feb31e039040da4ca6088ea632b7e
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Co-Authored-By: James E. Blair <corvus@inaugust.com>
Change-Id: Id8b347483affd710759f9b225bfadb3ce851333c
Depends-On: https://review.openstack.org/596503
stackalytics.openstack.org does not resolve and seems very dead. Remove
its node from site.pp and remove it from the docs to avoid confusion
about what servers we're really managing. We can always add it back when
the time comes to try again.
Change-Id: I733130ebe97ae7e06ca57b3c8e3a8708fcfa069c