infrastructure September 2019

infrastructure@lists.fedoraproject.org

37 participants
50 discussions

Fedora Infrastructure Meeting Agenda 2019-09-26
by Stephen John Smoogen 25 Sep '19

25 Sep '19

The infrastructure team will be having its weekly meeting tomorrow, 2019-09-26 at 15:00 UTC in #fedora-meeting-1 on the freenode network. We have a document at https://board.net/p/fedora-infra 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-26) #meetingname infrastructure #topic aloha #chair nirik pingou relrod smooge tflink cverna mizdebsk mkonecny abompard bowlofeggs ``` ### Determine who the next chair is #topic Next chair #info magic eight ball says: ### 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 We are looking for people to maintain Fedocal and Nuancier - mkonecny ``` ### 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 Summary of last week: (from bowlofeggs ) #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 #topic Fedora CoreOS related tickets #info for 2019-09-25 meeting #info https://github.com/coreos/fedora-coreos-tracker/blob/master/Fedora-Requests… ``` 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 #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.

1 0

Inquiry: Usage of whiteboard from security/CVE bugs
by Viliam Križan 25 Sep '19

25 Sep '19

Hello, Red Hat Product Security would like to inquire the usage of whiteboard from security/CVE bugs in Fedora Infrastructure. Is there any infrastructure tool that is reading and parsing the data from the Whiteboard field from mentioned bugs. The CVE bugs are are bugs filed in Bugzilla under "Security Response"/vulnerability, often having a CVE as an alias. For example: CVE-2019-1010222 https://bugzilla.redhat.com/show_bug.cgi?id=1735591 Thank you for your time. -- Viliam Križan / Red Hat Product Security DevOps

2 3

Meeting Agenda Item: Introduction Joakim
by Joakim Lönnegren 25 Sep '19

25 Sep '19

Hello World! Was really impressed when I installed Fedora on an old laptop and everything just works (Cockpit, FreeIPA, kvm). Wanted to come over and see if I can give back to the community. I'm a linux sysadmin and former C# developer. I'd be thrilled to learn about python, openshift, openstack and ansible. I have an RHCSA and I'm studying for the RHCE. Originally from Sweden but living in Brazil so I'm in the GMT -3 timezone. My IRC handle is joalon, I'll try to make it to the infra meeting this thursday, as well as the Fridays with Infra event. Best regards, Joakim Lönnegren

3 2

New docs project: Onboarding the community to Communishift
by Randy Barlow 25 Sep '19

25 Sep '19

Hey Kevin and Petr (and anyone else on the list who is interested), I've been talking with Ben Cotton about moving the elections application into Communishift[0]. We had a few back and forth e-mails, and it became clear that it would be helpful if we had quality documentation describing how community members can use Communishift. I think there may need to be a balance between documenting how to use OpenShift, and linking to already existing resources regarding the use of OpenShift. Perhaps some simple hello world type examples would be good to document, but it would probably be best to link to official OpenShift documentation for details on how to use OpenShift. On the other hand, there are likely to be some particularities with how we have deployed/configured Communishift that should be documented. Since we are hoping to hand off several infrastructure applications to the community, there may be some common patterns among those apps that would be good to document as well. It would also be good to document best practices suggestions for some common problems our users will need to solve: * How can they use persistent storage? * How can they use a database? * How can they back up the applications, persistent storage, and database? We do have a wiki page[1] for Communishift already that we can use as a starting point, but we probably want to move it to our documentation project as we extend it. Let me know if you are interested in participating in this project. [0] Communishift is an OpenShift instance hosted by Fedora Infrastructure for the community to use to host applications for Fedora. Fedora Infrastructure does not maintain or administrate any applications in Communishift, but rather administers the OpenShift deployment itself. [1] https://fedoraproject.org/wiki/Infrastructure/Communishift

6 8

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

25 Sep '19

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2019-09-26 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. Source: https://apps.fedoraproject.org/calendar/meeting/22/

1 0

Friday with Infra: elections
by Ben Cotton 23 Sep '19

23 Sep '19

Hi Infra team, I'd like to get some Friday (or another day) with Infra time in the coming month to get Elections moved to CommuniShift, that way I can make a few bug fixes that need done in advance of the elections coming up in December. Thanks, BC -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

2 1

[PATCH v2] rabbitmq: add coreos queue
by Jonathan Lebon 20 Sep '19

20 Sep '19

This is needed for CoreOS-specific messages. See https://pagure.io/fedora-infrastructure/issue/8227. Reviewed-by: Aurelien Bompard <abompard(a)redhat.com> --- roles/rabbitmq_cluster/tasks/apps.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/roles/rabbitmq_cluster/tasks/apps.yml b/roles/rabbitmq_cluster/tasks/apps.yml index 1f2f5af55..ec743defc 100644 --- a/roles/rabbitmq_cluster/tasks/apps.yml +++ b/roles/rabbitmq_cluster/tasks/apps.yml @@ -3,9 +3,12 @@ # -- name: CoreOS user +- name: CoreOS queue run_once: true include_role: - name: rabbit/user + name: rabbit/queue vars: username: coreos{{ env_suffix }} + queue_name: coreos{{ env_suffix }} + routing_keys: + - "org.fedoraproject.*.coreos.build.request.*" -- 2.21.0

2 1

[PATCH] rabbitmq: add coreos queue
by Jonathan Lebon 20 Sep '19

20 Sep '19

This is needed for CoreOS-specific messages. See https://pagure.io/fedora-infrastructure/issue/8227. --- roles/rabbitmq_cluster/tasks/apps.yml | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/roles/rabbitmq_cluster/tasks/apps.yml b/roles/rabbitmq_cluster/tasks/apps.yml index 1f2f5af55..8f4cfffa8 100644 --- a/roles/rabbitmq_cluster/tasks/apps.yml +++ b/roles/rabbitmq_cluster/tasks/apps.yml @@ -9,3 +9,13 @@ name: rabbit/user vars: username: coreos{{ env_suffix }} + +- name: CoreOS queue + run_once: true + include_role: + name: rabbit/queue + vars: + username: coreos{{ env_suffix }} + queue_name: coreos{{ env_suffix }} + routing_keys: + - "org.fedoraproject.*.coreos.*" -- 2.21.0

1 0

please review, patch for infrastructure issue 8156
by Karsten Hopp 19 Sep '19

19 Sep '19

Attached is a patch for https://pagure.io/fedora-infrastructure/issue/8156 There were lots of places where I didn't know if a certain conditional makes sense, for example checking for ansible_distribution == RedHat when we maybe have only Fedora machines and that playbook would never run on RHEL I've added a couple of FIXME lines where I though that a closer look might be required. Thanks, Karsten

2 1

Agenda for Thursday's meeting
by Randy Barlow 19 Sep '19

19 Sep '19

nirik suggested trying out board.net for the weekly meeting agenda, so I created a meeting agenda there: https://board.net/p/fedora-infra Feel free to add your own material to the agenda. Here is what it looks like at the time of this writing: --- title: Infrastructure Meeting template tags: Fedora, Infra, CPE --- # 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 (2019-09-19) at 15:00 UTC in #fedora-meeting-1. Please check the agenda at https://board.net/p/fedora-infra and mail updates to sysadmin-main members. ``` On the day of the meeting send the following ``` REMINDER: There will be a Fedora Infrastructure meeting today (2019-09-19) at 15:00 UTC in #fedora-meeting-1. Please check the agenda at https://board.net/p/fedora-infra and mail updates to sysadmin-main members. ``` ## Preamble The infrastructure team will be having its weekly meeting tomorrow, 2019-09-19 at 15:00 UTC in #fedora-meeting-1 on the freenode network. We have a document at https://board.net/p/fedora-infra 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-19) #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 We are looking for people to maintain Fedocal and Nuancier - mkonecny ``` ### 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 Summary of last week: (from relrod ) #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 #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 ```

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure September 2019