infrastructure February 2019

infrastructure@lists.fedoraproject.org

32 participants
32 discussions

Re: [ansible] [distgit/pagure] Drop --autoreload from our systemd service file
by Todd Zullinger 28 Feb '19

28 Feb '19

Hi, Pierre-YvesChibon wrote: > [distgit/pagure] Drop --autoreload from our systemd service file I noticed a few recent commits using this bracket prefix style and I wanted to give a heads-up about how this can cause problems, in case it's not well-known. (If I've mentioned it before, please forgive my memory lapse.) Using brackets to prefix the commit message will cause grief for any patches which are applied via 'git am', as the contents within the brackets will be stripped. Even after the ansible repo is available via pagure, there are likely still times when someone will attach a patch to a bug or send it with git send-email. If this [prefix/area] convention is more widely adopted in the ansible repo, it's worth keeping in mind the potential for surprise (and subtle loss of commit message details) it will likely cause down the road. The prefix stripping can be avoided by passing the '--keep-non-patch' option to git am. However, there's no config variable to allow that to be easily set per repo, so it'd be very easy to forget. This has been discussed on the git list in the past. One of the more recent discussions was from 2015: https://public-inbox.org/git/5655D3DA.1050403@informatik.uni-hamburg.de/T/#u I had a recent bug report filed about this as well: https://bugzilla.redhat.com/show_bug.cgi?id=1671640 (as evidence that it surprises others still). Hope this is helpful, -- Todd

2 1

Meeting Agenda for 2019-02-28 Infrastructure meeting
by Stephen John Smoogen 27 Feb '19

27 Feb '19

= Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2019-02-27 at 15:00 UTC in #fedora-meeting-1 on the freenode network. We have a gobby document at https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure… which can be edited for the agenda (see: https://fedoraproject.org/wiki/Gobby ) 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-02-27) #meetingname infrastructure #topic aloha #chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mkonecny mizdebsk = 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 nirik will have sparse hours due to house move #info Mass update/reboots planned for 2019-02-26 -> 2019-02-28 #info Beta Freeze Begins 2019-03-05 #info Pagure 3.2.0/3.2.1 was deployed to stg/prod/pkgs. #info Taskotron Staging re-deployed on F29, mostly working #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 smooge is on call from 2019-02-14 -> 2019-02-21 #info puiterwijk is on call from 2019-02-21 -> 2019-02-28 #info smooge is on call from 2019-02-28 -> 2019-03-07 #info ?????? is on call from 2019-03-07 -> 2019-03-14 #info ?????? is on call from 2019-03-14 -> 2019-03-21 #info Summary of last week: (from smooge ) #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 #topic Priorities for next week? #info please put tickets needing to be focused on here #topic Discuss: Is the Fedora pastebin still useful? - relrod #info how many users are using it? #info should we look at converging with CentOS one so simpler setup? = 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 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.

1 0

[Fedocal] Reminder meeting : Fedora Infrastructure
by smooge＠gmail.com 27 Feb '19

27 Feb '19

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2019-02-28 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before or view it at https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure… Source: https://apps.fedoraproject.org/calendar/meeting/22/

1 0

Planned Outage - Fedora Core Services 2019-02-27 20:00 UTC
by Stephen John Smoogen 22 Feb '19

22 Feb '19

There will be an outage starting at 2019-02-27 20:00 UTC, which will last approximately 4-6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-02-27 20:00UTC' Reason for outage: Fedora Infrastructure would like to update and reboot all core systems and services. This will update kernels, glibc, and systemd plus many other services on the affected systems. Affected Services: All systems under fedoraproject.org will be affected. Important databases and authentication will be updated and rebooted first. Then other non-build systems will follow. Then build systems will finalize the update/reboot cycle Ticket Link: https://pagure.io/fedora-infrastructure/issue/7591 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen.

1 0

Planned Outage - Fedora Staging Updates/Reboots 2019-02-26 20:00 UTC
by Stephen John Smoogen 22 Feb '19

22 Feb '19

There will be an outage starting at 2019-02-26 20:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-02-26 20:00UTC' Reason for outage: Fedora Infrastructure would like to update and reboot all fedora staging and all web proxies. This will update kernels, glibc, and systemd plus many other services on the affected systems. Affected Services: First all systems under stg.fedoraproject.org and stg.phx2.fedoraproject.org will be updated and rebooted. If that shows no problems then a rolling update of proxies and virtual hosts they are on which may affect web access for short periods of time. If problems appear then updates on 'remote' systems will be delayed til the next day or later. Ticket Link: https://pagure.io/fedora-infrastructure/issue/7590 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen.

1 0

[PATCH] - add fedora-bootstrap-1.5.0 to apps.fp.o/global
by Ryan Lerch 21 Feb '19

21 Feb '19

Add the latest release of Fedora Bootstrap (1.5.0) to apps.fp.o/global

2 1

Anitya 0.15.0 (stg.release-monitoring.org) deployed on staging
by Michal Konecny 21 Feb '19

21 Feb '19

Hi everybody, I want to announce that the Anitya 0.15.0 was deployed on staging (https://stg.release-monitoring.org/) Feel free to test it. This version will stay in staging for some time till certificates for fedora messaging will be solved. Main change in this version is migration from fedmsg <http://fedmsg.com/> to Fedora messaging <https://github.com/fedora-infra/fedora-messaging>. Full changelog could be found here https://github.com/release-monitoring/anitya/releases/tag/0.15.0 Regards, mkonecny

1 0

Fedora Infrastructure Meeting Agenda for 2019-02-21
by Stephen John Smoogen 20 Feb '19

20 Feb '19

This shared document is for the next fedora infrastructure meeting. Send on IRC a day before meeting (#fedora-noc #fedora-admin #fedora-releng #fedora-apps) REMINDER: There will be a Fedora Infrastructure meeting tomorrow (20yy-mm-dd) at 15:00 UTC in #fedora-meeting-1. Please update the gobby2 document at infinote.fedoraproject.org with any agenda items https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure… On the day of the meeting send the following REMINDER: There will be a Fedora Infrastructure meeting today (2019-02-14) at 15:00 UTC in #fedora-meeting-1. Please update the gobby2 document at infinote.fedoraproject.org with any agenda items https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure… = Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2019-02-21 at 15:00 UTC in #fedora-meeting-1 on the freenode network. We have a gobby document at https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure… which can be edited for the agenda (see: https://fedoraproject.org/wiki/Gobby ) 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-02-21) #meetingname infrastructure #topic aloha #chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mkonecny = 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 nirik will have sparse hours due to house move #info Mass branching happened and it was ... #info Mass update/reboots planned for 2019-02-26 -> 2019-02-28 #info Beta Freeze Begins 2019-03-05 #info Anitya (release-monitoring.org) 0.15.0 was released and deployed on staging #info Pagure 3.2.90 was deployed to stg.pagure.io. Please test #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 smooge is on call from 2019-02-14 -> 2019-02-21 #info puiterwijk is on call from 2019-02-21 -> 2019-02-28 #info ?????? is on call from 2019-02-28 -> 2019-03-07 #info ?????? is on call from 2019-03-07 -> 2019-03-14 #info ?????? is on call from 2019-03-14 -> 2019-03-21 #info Summary of last week: (from smooge ) #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 #topic Priorities for next week? #info please put tickets needing to be focused on here #topic Discuss: Is the Fedora pastebin still useful? - relrod #info how many users are using it? #info should we look at converging with CentOS one so simpler setup? = 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 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.

1 0

[Fedocal] Reminder meeting : Fedora Infrastructure
by smooge＠gmail.com 20 Feb '19

20 Feb '19

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2019-02-21 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before or view it at https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure… Source: https://apps.fedoraproject.org/calendar/meeting/22/

1 0

FAS query question
by Ben Cotton 20 Feb '19

20 Feb '19

Infra team, In the interests of reducing our app load, I'm checking out possible replacements for our elections app. One of the candidates is Helios, which would apparently require me providing a CSV of eligible voters for each election. Do we have a programmatic way of getting email addresses out of FAS for different queries? For example, for some elections, we might want the cla_fpca group, while other elections may require cla_fpca+1 and others may require a specific group. If that functionality doesn't exist, what does the effort to add it look like? -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis

5 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure February 2019