I ll be deleting the fas3_server role from our ansible repository
since it is currently not used and we are moving away from FAS.
See the file diff below.
Please let me know, if for any reason we should keep this role.
roles/fas3_server/files/accounts.conf | 31 ----
roles/fas3_server/files/copr.repo | 8 -
roles/fas3_server/tasks/main.yml | 55 ------
roles/fas3_server/templates/production.ini | 198 ---------------------
4 files changed, 292 deletions(-)
delete mode 100644 roles/fas3_server/files/accounts.conf
delete mode 100644 roles/fas3_server/files/copr.repo
delete mode 100644 roles/fas3_server/tasks/main.yml
delete mode 100644 roles/fas3_server/templates/production.ini
I found out that the freezelist script did not work with ansible
2.7.10. Once the script changed to use the new api, it complained
about 2 non valid yaml file (error syntax error: found character
'\t' that cannot start any token) in the vars. So I replaced the tabs
character by spaces.
See the attached patch +1s ?
= Preamble =
The infrastructure team will be having its weekly meeting tomorrow,
2019-04-18 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a gobby document at
which can be edited for the agenda (see:
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
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-04-18)
#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:
= Status / Information / Trivia / Announcements =
(We put things here we want others on the team to know, but don't need to
(Please use #info <the thing> - your name)
#topic announcements and information
#info Final Freeze Started on 2019-04-16
#info Please do not make changes to unfrozen machines without 2 +1 from
= Things we should discuss =
We use this section to bring up discussion topics. Things we want to talk
as a group and come up with some consensus /suor decision or just
problem or issue. If there are none of these we skip this section.
(Use #topic your discussion topic - your username)
#info nirik is on call from 2019-04-11 -> 2019-04-18
#info ????? is on call from 2019-04-18 -> 2019-04-25
#info ????? is on call from 2019-04-25 -> 2019-05-02
#info Summary of last week: (from nirik )
#topic Monitoring discussion
#info Go over existing out items and fix
#topic Tickets discussion
Go thru each ticket one by one
#topic Priorities for next week?
#info please put tickets or projects needing to be focused on here
Put all topics for discussion under here
= Apprentice office hours =
#topic Apprentice Open office minutes
#info A time where apprentices may ask for help or look at problems.
Here we will discuss any apprentice questions, try and match up people
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
that we have. Just going over what it is, how to contribute, ideas for
etc. Whoever would like to do this, just add the i/nfo in this section. In
event we don't find someone to teach about something, we skip this section
and just move on to open floor.)
= Meeting end stuff =
#topic Open Floor
Stephen J Smoogen.
Can I get +1s for the patch underneath?
This will switch from /srv/web/docs (synced from externally built docs
sources) to /srv/docs (mount point for doc build outputs built in
This is tested in staging, and the contents in the new location have
diff --git a/roles/rsyncd/files/rsyncd.conf.sundries
index f6fe92e4f..8cf5cd222 100644
@@ -24,7 +24,7 @@ hosts allow = 10.5.126.0/255.255.255.0
comment = Docs Site
-path = /srv/web/docs
+path = /srv/docs
uid = root
gid = root
read only = yes
I would like to start discussion about "How to express information about
release freeze to Bodhi".
This question is relelated to Bodhi issue
The initial plan was to just add some argument to cli "bodhi releases
create/edit", something like:
>> bodhi releases edit --name F29 --frozen true)
but I would like to consider other options, if any, before I start working
In triaging ticket last week, we noticed there are several related to
the pagure to bugzilla sync script.
This script runs once a day (at 18utc) and syncs the point of
contact/watchers/committers/etc to bugzilla components.
Here's a meta ticket for issues:
That lists the other 4 tickets outstanding on it.
The script is in our ansible repo:
In addition to the 4 tickets theree's a number of other issues with the
* It fires of a query for every single package/container/module against
fedora-scm-requests to see if there's an override for it. We should
bundle this information up somehow, or move the overrides to a better
place or do something to end those 25,000 queries.
* Some folks wanted to add the 'packager' group to their package, with
the idea being that they wanted anyone in packager group to be able to
push changes. This "works", but the script then tries to mail
devel(a)lists.fedoraproject.org as the 'address' for 'packager'.
It would be nice to filter this out on a configurable set of groups.
* We have a small number of things we don't manage in the script: the
distribution component, the various spins components, basically anything
thats not a package/module/container/rpm. It would be nice to manage
those from the script too so we had a nice place to create/remove them.
Anyhow, given all these issues, I thought it would be interesting to try
and get a small team together sometime next week and attack re-doing
this script. I'd be happpy to help from the sysadmin side of things, but
I would love to get a few python savvy folks involved. Any takers?
Of course anyone is welcome to look at the script and provide
patches/ideas. Please add them to the above 'meta' ticket. :)