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
This adds a connection to the opendaylight Gerrit server to zuul
so that we can perform cross-community testing.
Change-Id: I846983e873072c2235a4c49e36f602a47d06cfce
We've launched mirror02.us-west-1.packethost.openstack.org while we
figure out why mirror01 keeps getting shut off.
Change-Id: Idd74488f47f92fb44c3b4ff935b192c9f743e512
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This brings online our 11th zuul-executor, and opens the required
firewall ports.
Change-Id: If0ee569a2d14caeeb912b7382160f47d460650ab
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Logging of #StarlingX IRC channel.
Update in common.yaml file to include #StarlingX IRC channel in the list of channels being logged.
Change-Id: Ic9949f409ab21cc6bf3b88b700a6ce66f00ac166
Signed-off-by: Hazzim Anaya <hazzim.i.anaya.casas@intel.com>
While meetbot seems to be added, it looks like statusbot may
have been missed. This change adds statusbot to the
openstack-security channel.
Change-Id: Ifdbbb786191867add0450a0c59640fcabd6747b5
While meetbot seems to be added, it looks like statusbot may
have been missed. This change adds statusbot to the
openstack-helm channel.
Change-Id: Ifa42586e2badb25d868cd95baee50b088b28426a
This reverts commit c7bb14bba6ec00fff61879154a3f5f143c98767b.
SSH connectivity isn't quite working yet. Revert until we can get that
sorted out.
Change-Id: If2a88a61ed592f927980c71486ed0b7e3cb848d0
This adds a connection to the opendaylight Gerrit server to zuul
so that we can perform cross-community testing.
Change-Id: I840b24ebe52c50840180f2dda40a3f8669baa347
mirror01.regionone.limestone.o.o is the old host, mirror02 is newest.
Change-Id: Ieb100c5f9c3d01d1dadf1a42e89f0073dc61026b
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Infracloud is sadly deceased. The upside is we can delete a lot of code
we don't need anymore. This patch removes infracloud nodes from
site.pp so that the puppet-apply test no longer bothers to validate
them, removes the infracloud modules from modules.env so that we don't
bother to install those modules in puppet-apply and puppet functional
tests, and removes the infracloud-specific data from the public hiera.
Additionally stop the puppetmaster from trying to run the infracloud
ansible playbook and finally remove the chocolate region from nodepool's
clouds.yaml (vanilla was already done).
This patch leaves the run_infracloud.sh script and the
infracloud-specific ansible playbooks as well as the infracloud
manifests in the openstack_project puppet module. It's possible those
tools could come in handy in the future if we ever have another
infracloud, and leaving those tools in place doesn't add confusion about
which hosts are actually active nor does it leave cruft that gets
unnecessarily tested.
Change-Id: Ic760cc55f8e17fa7f39f2dd0433f5560aa8e2d65
Enable logs and add statusbot for oooq channel in IRC which is
used for tripleo-quickstart discussions.
Change-Id: I8409ae810982bb1199a8ee6d2b6097e0293657cb
'#openstack-placement' is a new IRC channel for disussing the
placement service. It has been extracted from openstack-nova to make
that channel less noisy. We would like statusbot and meetbot in the
channel so that we can be aware of status and have meetings local to the
channel if necessary.
The depends on are the project-config changes for accessbot and
gerritbot.
Depends-On: https://review.openstack.org/559768
Change-Id: I0002c2c753b04c8cc02bd5ac1a1ab528bf775591
In discussions at the last PTG[1] and in subsequent First Contact
SIG meetings[2] we've decided that the #openstack-101 channel
should be removed and rolled into the #openstack-dev channel.
Why? Good qustion:
- No one is good at sitting in and watching the #openstack-101
channel outside of OUI training periods.
- It would be better for new contributors to ask questions in
a channel that people with the answers already activly monitor.
- 101 is an American-ism, that not everyone in the world would
understand.
This means that during OUI trainings there will be more noise in
openstack-dev. However, trainings mostly happen the weekend
before a summit, so at a very quiet time. And would mean trainees
would already have practice and now where to come for questions.
There is another patch[3] which will remove openstack-101 from
the accessbot.
Finally, as per renaming instructions[4], once these patches
land, a redirect will need to be created, the topic updated and
current residents of the channel will need to be informed to
relocate.
[1] https://etherpad.openstack.org/p/FC_SIG_Rocky_PTG
[2] https://wiki.openstack.org/wiki/First_Contact_SIG#Meeting_Agenda
[3] https://review.openstack.org/559250
[4] https://docs.openstack.org/infra/system-config/irc.html#renaming-an-irc-channel
Change-Id: I24710f24e7e640aabbf22353c25c24d2a8af9287