Freeze Break Request: Fix typo in bodhi status variable
by Kevin Fenzi
Greetings.
We have a variable in:
vars/all/FedoraBranchedBodhi.yaml
thats used in our bodhi config to set the proper policies.
The template uses 'predeta' and 'postbeta'... but the variable was
updated to 'preBeta', which isn't going to work.
I'd like to apply the following and run the bodhi backend playbook:
diff --git a/vars/all/FedoraBranchedBodhi.yaml
b/vars/all/FedoraBranchedBodhi.yaml
index 91f82f2..f0cca9a 100644
--- a/vars/all/FedoraBranchedBodhi.yaml
+++ b/vars/all/FedoraBranchedBodhi.yaml
@@ -1,2 +1,2 @@
-#options are: preBeta, postBeta, current
-FedoraBranchedBodhi: preBeta
+#options are: prebeta, postbeta, current
+FedoraBranchedBodhi: prebeta
kevin
4 years, 7 months
Changes to the weekly meetings
by Stephen John Smoogen
At the last meeting, it was decided that the chair of the Fedora
Infrastructure meeting would be rotated between Infrastructure chairs.
These are currently:
abompard bowlofeggs cverna mizdebsk mkonecny nirik pingou puiterwijk
relrod smooge tflink
If you would like to NOT be running a meeting, please remove yourself
from the chair list so that it will be easier to see who gets it next.
Things that still need to be set up is a git page where the hackmd can
point to with joint ownership between multiple people.
--
Stephen J Smoogen.
4 years, 7 months
FBR: Allow sysadmin-osbs to SSH into bastion and batcave
by Mikolaj Izdebski
Resolves https://pagure.io/fedora-infrastructure/issue/8182
---
inventory/group_vars/bastion | 2 +-
inventory/group_vars/batcave | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/inventory/group_vars/bastion b/inventory/group_vars/bastion
index 37b6d3e85..aeacc87e4 100644
--- a/inventory/group_vars/bastion
+++ b/inventory/group_vars/bastion
@@ -23,7 +23,7 @@ custom_rules: [
# TODO - remove modularity-wg membership here once it is not longer needed:
# https://fedorahosted.org/fedora-infrastructure/ticket/5363
-fas_client_groups:
sysadmin-ask,sysadmin-atomic,sysadmin-web,sysadmin-main,sysadmin-cvs,sysadmin-noc,sysadmin-releng,sysadmin-dba,sysadmin-hosted,sysadmin-tools,sysadmin-spin,sysadmin-cloud,fi-apprentice,sysadmin-badges,sysadmin-troubleshoot,sysadmin-qa,sysadmin-centos,sysadmin-ppc,sysadmin-koschei,sysadmin-secondary,sysadmin-fedimg,sysadmin-veteran,sysadmin-mbs,modularity-wg,pungi-devel,sysadmin-upstreamfirst,sysadmin-releasemonitoring,sysadmin-gnome,sysadmin-copr,sysadmin-coreos,sysadmin-dbgserver
+fas_client_groups:
sysadmin-ask,sysadmin-atomic,sysadmin-web,sysadmin-main,sysadmin-cvs,sysadmin-noc,sysadmin-releng,sysadmin-dba,sysadmin-hosted,sysadmin-tools,sysadmin-spin,sysadmin-cloud,fi-apprentice,sysadmin-badges,sysadmin-troubleshoot,sysadmin-qa,sysadmin-centos,sysadmin-ppc,sysadmin-koschei,sysadmin-secondary,sysadmin-fedimg,sysadmin-veteran,sysadmin-mbs,modularity-wg,pungi-devel,sysadmin-upstreamfirst,sysadmin-releasemonitoring,sysadmin-gnome,sysadmin-copr,sysadmin-coreos,sysadmin-dbgserver,sysadmin-osbs
#
# This is a postfix gateway. This will pick up gateway postfix config in base
diff --git a/inventory/group_vars/batcave b/inventory/group_vars/batcave
index d415cd225..2fe5f4745 100644
--- a/inventory/group_vars/batcave
+++ b/inventory/group_vars/batcave
@@ -8,7 +8,7 @@ tcp_ports: [ 80, 443, 8442, 8443 ]
# Neeed for rsync from log01 for logs.
custom_rules: [ '-A INPUT -p tcp -m tcp -s 10.5.126.13 --dport 873 -j
ACCEPT', '-A INPUT -p tcp -m tcp -s 192.168.1.59 --dport 873 -j
ACCEPT' ]
-fas_client_groups:
sysadmin-ask,sysadmin-atomic,sysadmin-cvs,sysadmin-main,sysadmin-web,sysadmin-noc,sysadmin-hosted,sysadmin-releng,sysadmin-qa,sysadmin-tools,sysadmin-cloud,sysadmin-bot,sysadmin-centos,sysadmin-koschei,sysadmin-datanommer,sysadmin-fedimg,fi-apprentice,sysadmin-regcfp,sysadmin-badges,sysadmin-mbs,sysadmin-veteran,sysadmin-coreos,sysadmin-upstreamfirst,sysadmin-releasemonitoring,sysadmin-fpdc,sysadmin-messaging,sysadmin-libravatar,sysadmin-gnome,sysadmin-copr
+fas_client_groups:
sysadmin-ask,sysadmin-atomic,sysadmin-cvs,sysadmin-main,sysadmin-web,sysadmin-noc,sysadmin-hosted,sysadmin-releng,sysadmin-qa,sysadmin-tools,sysadmin-cloud,sysadmin-bot,sysadmin-centos,sysadmin-koschei,sysadmin-datanommer,sysadmin-fedimg,fi-apprentice,sysadmin-regcfp,sysadmin-badges,sysadmin-mbs,sysadmin-veteran,sysadmin-coreos,sysadmin-upstreamfirst,sysadmin-releasemonitoring,sysadmin-fpdc,sysadmin-messaging,sysadmin-libravatar,sysadmin-gnome,sysadmin-copr,sysadmin-osbs
ansible_base: /srv/web/infra
freezes: false
--
2.21.0
4 years, 7 months
Fedora 31 Beta Release Readiness meeting
by Ben Cotton
Dear all,
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 31
Beta Release Readiness meeting. This meeting will be held on
Thursday, 2019-09-12 at 19:00 UTC.
We will meet to make sure we are coordinated and ready for the release
of Fedora 31 Beta. Please note that this meeting will be held even if
the release is delayed at the Go/No-Go meeting on the same day two
hours earlier.
You may receive this message several times in order to open this
meeting to the teams and to raise awareness, so hopefully more team
representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams.
For more information, see
https://fedoraproject.org/wiki/Release_Readiness_Meetings.
View the meeting on Fedocal:
https://apps.fedoraproject.org/calendar/meeting/9614/
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
4 years, 7 months
Rotating on-call duties to all sysadmin-main
by Stephen John Smoogen
Currently the on-call duties are being cycled at the Infrastructure
meeting but have been mostly rotating between 2-3 people over the last
couple of months. It was brought up at the last infrastructure meeting
to start rotating this through the people who are in sysadmin-main.
The reasons for making it this way is that the people there should be
able to make changes to nagios and most systems which need high level
changes. Suggestions on how to implement this would be to have people
shuffled by a program and then run through for 6 or so weeks until the
next shuffle is needed. People who have PTO etc during this can work
out with another sysadmin-main who can do it instead.
Other suggestions are possible. Please discuss and come up with an
answer by the 2019-09-19 meeting.
--
Stephen J Smoogen.
4 years, 7 months
FBR: upgrading pagure
by Pierre-Yves Chibon
Good Morning,
I've just cut a new pagure bugfix release: 5.7.9 the changelog can be found at:
https://docs.pagure.org/pagure/changelog.html#id1
It's basically four small bug fixes one of which we have already hotfixed, so
this release drops the hotfix but not the fix :)
In addition, I'd like to include this configuration file on our dist-git
instance:
diff --git a/ roles/distgit/pagure/templates/pagure.cfg b/ roles/distgit/pagure/templates/pagure.cfg
index 0aa7c7764..34f4854dd 100644
--- a/ roles/distgit/pagure/templates/pagure.cfg
+++ b/ roles/distgit/pagure/templates/pagure.cfg
@@ -279,6 +279,7 @@ CROSS_PROJECT_ACLS = [
'pull_request_create',
'pull_request_comment',
'update_watch_status',
+ 'pull_request_merge',
]
ADMIN_API_ACLS = [
Which is meant to allow cross-project API token to merge pull-request. I'd like
to use one of these for monitoring CI on PRs and builds.
+1s?
Thanks,
Pierre
4 years, 7 months
Meeting Agenda 2019-09-05
by Stephen John Smoogen
## Preamble
The infrastructure team will be having its weekly meeting tomorrow,
2019-09-05 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a hackmd.io document at https://hackmd.io/@ssmoogen/HyqIIdlmS
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
## Introduction
We will use it over the week before the meeting to gather status and
info and discussion items and so forth, then use it in the irc meeting
to transfer information to the meetbot logs.
### Meeting start stuff
```
#startmeeting Infrastructure (2019-09-05)
#meetingname infrastructure
#topic aloha
#chair nirik pingou puiterwijk relrod smooge tflink cverna mizdebsk
mkonecny abompard bowlofeggs
```
### Let new people say hello
```
#topic New folks introductions
#info This is a place where people who are interested in Fedora
Infrastructure can introduce themselves
#info Getting Started Guide:
https://fedoraproject.org/wiki/Infrastructure/GettingStarted
```
### Status / Information / Trivia / Announcements
(We put things here we want others on the team to know, but don't need
to discuss)
(Please use ```#info (the thing - your name)```
```
#topic announcements and information
#info smooge will be on PTO 2019-09-07 -> 2019-09-15
#info we are in F31 beta freeze
#info pagure updates to 5.7.?
#info
#info
```
### Things we should discuss
We use this section to bring up discussion topics. Things we want to talk about
as a group and come up with some consensus /suor decision or just brainstorm a
problem or issue. If there are none of these we skip this section.
(Use ```#topic your discussion topic - your username)```
```
#topic Oncall
#info https://fedoraproject.org/wiki/Infrastructure/Oncall
#info relrod is on call from 2019-08-29 -> 2019-09-05
#info ?????? is on call from 2019-08-05 -> 2019-09-12
#info Summary of last week: (from cverna )
#topic Monitoring discussion
#info https://nagios.fedoraproject.org/nagios
#info Go over existing out items and fix
#topic Tickets discussion
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
```
Go thru each ticket one by one
### Put all topics for discussion under here
```
#topic Where to put these docs in the future?
#info infinote is going away and this is my 'private hackmd'
#info a new central doc place would be good. can someone set this up?
```
Here we will discuss any apprentice questions, try and match up people looking
for things to do with things to do, progress, testing anything like that.
### Learn about some application or setup in infrastructure
(This section, each week we get 1 person to talk about an application
or setup that we have. Just going over what it is, how to contribute,
ideas for improvement, etc. Whoever would like to do this, just add
the i/nfo in this section. In the event we don't find someone to teach
about something, we skip this section and just move on to open floor.)
```
#info
```
### Meeting end stuff
```
#topic Open Floor
#endmeeting
```
--
Stephen J Smoogen.
4 years, 7 months
