Fedora Infrastructure Meeting 2017-10-26 1800 UTC
by Stephen John Smoogen
Here is the current agenda. Thank you for your patience
= 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 (2017-10-26)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik dgilmore threebean pingou puiterwijk
pbrobinson maxamillion
= 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
= 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 PHX2 Colo Trip, Dec 4th - 9th
#info Infrastructure will be down during that trip.
#info Final freeze has started. PLEASE TEST ANY RCs.
#info EU daylight savings Oct 29/ US daylight savings Nov 5
#info Kevin is out this week.
#info bodhi-3.0.0 was released and installed
#info stay tuned for bodhi-4.0.0, which will be re-written in fortran
and will somehow involve lots of matrices
#info NFS problems seem to have shown up
= 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 Ticket cleanup
#info none this week.
= Apprentice office hours =
#topic Apprentice Open office hours
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.)
#topic Learn about:
#info none this week
= Meeting end stuff =
#topic Open Floor
#endmeeting
--
Stephen J Smoogen.
6 years, 5 months
Meeting Agenda Item: Alan Treviño
by atrevino1989@gmail.com
Hi everyone !
My name is Alan Treviño I'm from Mexico, I would like to contribute to
infrastructure team as I had been working in different IT sectors for
some 7 years as web dev, QA (automation) and a little bit of support
engineering, I think this mix fits ok with the team.
Right now I'm doing some cool stuff with python and selenium at work
(company name: Enroute), I really want to learn more about you guys and
how you work to start contributing !
I have experience with Java, PHP and Python and had been user of fedora
since 24v but worked with SLES and bunch other Linux server distros as
QA (installing, configuring, etc.).
What am I expecting to learn?
Just increase my programming skills and also be more comfortable with
tasks related to servers (troubleshoot, configuration, deployments,
script crafting, etc.)
My IRC user is "atrevino"
Best regards!
Alan Treviño
6 years, 5 months
FBR: pygments2 on pagure01
by Pierre-Yves Chibon
Good Morning Everyone,
I would like to apply the following patch to ansible and then restart apache:
diff --git a/ roles/distgit/pagure/tasks/main.yml b/ roles/distgit/pagure/tasks/main.yml
index b3ee3b4..235efff 100644
--- a/ roles/distgit/pagure/tasks/main.yml
+++ b/ roles/distgit/pagure/tasks/main.yml
@@ -10,6 +10,7 @@
- pagure-milters
- pagure-webhook
- python-psycopg2
+ - python2-pygments2
- redis
- libsemanage-python
- python-fedora-flask
diff --git a/ roles/pagure/frontend/tasks/main.yml b/ roles/pagure/frontend/tasks/main.yml
index 7349b33..f5cee6b 100644
--- a/ roles/pagure/frontend/tasks/main.yml
+++ b/ roles/pagure/frontend/tasks/main.yml
@@ -12,6 +12,7 @@
- pagure-milters
- pagure-webhook
- python-psycopg2
+ - python2-pygments2
- redis
- libsemanage-python
- mod_ssl
Note that this impacts both src.fp.o and pagure.io but src.fp.o already has
python2-pygments2 in fact, so nothing changes there, this is only correcting the
playbook. In practice only pagure01 and pagure-stg01 are impacted by this change
currently.
Thoughts?
Thanks,
Pierre
6 years, 5 months
FBR: Bodhi 3.0
by Patrick Uiterwijk
Hi all,
So, let's do this.
Can I get +1s for the first steps to switch to Bodhi 3.0?
1. The underneath patch and deploy with Ansible
2. Updating bodhi*.phx2 to bodhi 3.0
I will need to do more changes, like updating the sync script.
Would people be fine if I just make further changes and send a summary
at the end?
None of them should be hard to revert.
Regards,
Patrick
commit e64d275f6ad1e830f2374b0309f85d5dda697944 (HEAD -> master)
Author: Patrick Uiterwijk <patrick(a)puiterwijk.org>
Date: Tue Oct 24 16:16:50 2017 +0200
Deploy Bodhi3 config to production
Signed-off-by: Patrick Uiterwijk <patrick(a)puiterwijk.org>
diff --git a/roles/bodhi2/backend/tasks/main.yml
b/roles/bodhi2/backend/tasks/main.yml
index a8acf50ee..bc5a6b239 100644
--- a/roles/bodhi2/backend/tasks/main.yml
+++ b/roles/bodhi2/backend/tasks/main.yml
@@ -20,23 +20,14 @@
- fedmsg-hub
- fedmsg-relay
- python-mock
- - python2-fedmsg-atomic-composer
- sigul
- python-alembic
- python-scandir
- python2-productmd
- compose-utils
- python-fedmsg-meta-fedora-infrastructure
- tags:
- - packages
- - bodhi
-
-- name: Install pungi (staging)
- package: name={{item}} state=present
- with_items:
- pungi
- pungi-utils
- when: env == "staging"
tags:
- packages
- bodhi
diff --git a/roles/bodhi2/base/templates/production.ini.j2
b/roles/bodhi2/base/templates/production.ini.j2
index 74c0b6e0c..31ced4b88 100644
--- a/roles/bodhi2/base/templates/production.ini.j2
+++ b/roles/bodhi2/base/templates/production.ini.j2
@@ -113,25 +113,13 @@ releng_fedmsg_certname =
shell-bodhi-backend03.phx2.fedoraproject.org
# will act as a masher as well.
#masher = None
-# Where to initially mash repositories
-#mash_dir = /var/cache/bodhi/mashing
-{% if ansible_hostname == 'bodhi-backend01' %}
-mash_dir = /mnt/koji/mash/updates
-{% else %}
-# mash_dir =
-{% endif %}
-
-# Where to symlink the latest repos by their tag name
-#mash_stage_dir = /var/cache/bodhi/mashed
-{% if ansible_hostname == 'bodhi-backend01' %}
-mash_stage_dir = /mnt/koji/mash/updates
-{% else %}
-# mash_stage_dir =
-{% endif %}
-
-mash_conf = /etc/bodhi/mash.conf
-
-createrepo_cache_dir = /var/cache/createrepo
+mash_dir = /mnt/koji/compose/updates/
+mash_stage_dir = /mnt/koji/compose/updates/
+pungi.basepath = /etc/bodhi
+pungi.conf.rpm = pungi.rpm.conf.j2
+pungi.conf.module = pungi.module.conf.j2
+pungi.labeltype = Update
+pungi.extracmdline = --notification-script=/usr/bin/pungi-fedmsg-notification
## Our periodic jobs
#jobs = clean_repo nagmail fix_bug_titles cache_release_data
approve_testing_updates
6 years, 5 months
[PATCH] start running f27 atomic/cloud pungi runs
by Dusty Mabe
Also stop running f25 runs.
---
roles/releng/files/twoweek-updates | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/roles/releng/files/twoweek-updates b/roles/releng/files/twoweek-updates
index 1fef504..b44fae7 100644
--- a/roles/releng/files/twoweek-updates
+++ b/roles/releng/files/twoweek-updates
@@ -2,14 +2,14 @@
MAILTO=releng-cron(a)lists.fedoraproject.org
15 8 * * * root TMPDIR=`mktemp -d /tmp/twoweekF26.XXXXXX` && pushd $TMPDIR && git clone -n https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f26 && LANG=en_US.UTF-8 ./twoweek-nightly.sh RC-$(date "+\%Y\%m\%d").0 && popd && rm -rf $TMPDIR
-#Fedora 25 two-week updates nightly compose
+#Fedora 27 two-week updates nightly compose
MAILTO=releng-cron(a)lists.fedoraproject.org
-15 5 * * * root TMPDIR=`mktemp -d /tmp/twoweekF25.XXXXXX` && pushd $TMPDIR && git clone -n https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f25 && LANG=en_US.UTF-8 ./twoweek-nightly.sh RC-$(date "+\%Y\%m\%d").0 && popd && rm -rf $TMPDIR
+15 5 * * * root TMPDIR=`mktemp -d /tmp/twoweekF27.XXXXXX` && pushd $TMPDIR && git clone -n https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f27 && LANG=en_US.UTF-8 ./twoweek-nightly.sh RC-$(date "+\%Y\%m\%d").0 && popd && rm -rf $TMPDIR
#Fedora 26 CloudImage nightly compose
MAILTO=releng-cron(a)lists.fedoraproject.org
15 9 * * * root TMPDIR=`mktemp -d /tmp/CloudImageF26.XXXXXX` && pushd $TMPDIR && git clone -n https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f26 && LANG=en_US.UTF-8 ./cloud-nightly.sh RC-$(date "+\%Y\%m\%d").0 && popd && rm -rf $TMPDIR
-#Fedora 25 CloudImage nightly compose
+#Fedora 27 CloudImage nightly compose
MAILTO=releng-cron(a)lists.fedoraproject.org
-15 7 * * * root TMPDIR=`mktemp -d /tmp/CloudImageF25.XXXXXX` && pushd $TMPDIR && git clone -n https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f25 && LANG=en_US.UTF-8 ./cloud-nightly.sh RC-$(date "+\%Y\%m\%d").0 && popd && rm -rf $TMPDIR
+15 7 * * * root TMPDIR=`mktemp -d /tmp/CloudImageF27.XXXXXX` && pushd $TMPDIR && git clone -n https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f27 && LANG=en_US.UTF-8 ./cloud-nightly.sh RC-$(date "+\%Y\%m\%d").0 && popd && rm -rf $TMPDIR
--
2.9.5
6 years, 5 months
bodhi-3.0.0-0.0.beta deployed to stg
by Randy Barlow
bodhi-3.0.0-0.0.beta[0] has been deployed to staging. We plan to ask for
an FBR to deploy the final release when it is ready, but we plan to keep
this in testing through Monday, with a theoretical Tuesday production
deployment (assuming ACKs and testing goes well).
This is a major release as it is backwards incompatible in how
repositories are layed out, and technically the bodhi CLI also has a
backwards-incompatibility too (the USERNAME env variable is no longer
used, as it clashed with GDM's). Patrick plans to rework the sync script
when we deploy to production so this will not impact our users.
The primary purpose of this release is to switch to Pungi instead of
mash for repository composition. This allows many things, but the big
one is modular repository mashing, which is why we will be asking for a
Freeze Break.
[0] https://bodhi.stg.fedoraproject.org/docs/release_notes.html
6 years, 5 months
FBR: Modules and the package list
by Ralph Bean
Karsten Hopp reported an issue with the MBS that his module builds of
modules/krb5 and modules/udisks2 failed, because the MBS failed to tag
them into f27-modular-updates-candidate at the end of the build. The
module names weren't in the pkg list.
I've added them directly to get him going again, but the root is an
issue in the pkg list sync script. Here's a patch that should make it
work going forwards.
Any +1'd for the following fix? (Tested by hand against the udisks2
and krb5 modules. I also checked that the patch doesn't accidentally
add the krb5 package to the list for f27 proper, which would be
wrong.)
diff --git a/roles/bodhi2/backend/templates/owner-sync-pagure.j2 b/roles/bodhi2/backend/templates/owner-sync-pagure.j2
index 6131b13..b3400bf 100755
--- a/roles/bodhi2/backend/templates/owner-sync-pagure.j2
+++ b/roles/bodhi2/backend/templates/owner-sync-pagure.j2
@@ -401,9 +401,13 @@ if __name__ == '__main__':
namespace = info['namespace']
pkgs = []
for pkg, branches in namespace_to_projects[namespace].items():
- # The tag and branch names are the same for "old-style" branches
if info['branch'] in branches or tag == ('f' + RAWHIDE):
+ # The tag and branch names are the same for "old-style" branches
pkgs.append(pkg)
+ elif namespace == 'modules':
+ # Add modules to f27-modular-updates even if their only branch is '2.4'
+ pkgs.append(pkg)
+
# This is a special project, not in dist-git, but which needs to be in
# the package list.
if namespace == 'rpms':
6 years, 5 months
Fedora Infrastructure Meeting 1800 UTC
by Stephen John Smoogen
= 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 (2017-10-19)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 dgilmore threebean pingou
puiterwijk pbrobinson maxamillion
= 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
= 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 PHX2 Colo Trip, Dec 4th - 9th
#info Infrastructure will be down during that trip.
#info Final freeze has started. PLEASE TEST ANY RCs.
#info EU daylight savings Oct 29 / US daylight savings Nov 05
= 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 Ticket cleanup
= Apprentice office hours =
#topic Apprentice Open office hours
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.)
#topic Learn about:
= Meeting end stuff =
#topic Open Floor
#endmeeting
--
Stephen J Smoogen.
6 years, 5 months
fedmsg-stg on irc changes
by Kevin Fenzi
Greetings.
As some of you know (and perhaps some of you do not) we have a live feed
of (most) fedmsgs gatewayed to irc.freenode.net.
Up until today both staging and production fedmsgs have been going to
#fedora-fedmsg. This is a pretty handy feature, as you can join the
channel and use your irc client to highlight messages you might care
about, or see whats going on in general in fedora or watch for some
message you know should be coming along.
However, due to the volume, the staging messages are often lost in the
noise and it makes it more difficult to watch them.
So, to help with this, I have created a new channel:
#fedora-fedmsg-stg that now gets all the staging messages only.
#fedora-fedmsg will keep getting the production ones (only now).
If this doesn't work out we can revist it, but hopefully it will be of
help to folks who are looking for messages in staging.
kevin
6 years, 5 months