May 2018 - infrastructure - Fedora mailing-lists

About JS framework
by Pierre-Yves Chibon 17 Oct '22

17 Oct '22

Good Morning Everyone, Our infrastructure is mostly a python store, meaning almost all our apps are written in python and most using wsgi. However in python we are using a number of framework: * flask for most * pyramid for some of the biggest (bodhi, FAS3) * Django (askbot, Hyperkitty) * TurboGears2 (fedora-packages) * aiohttp (python3, async app: mdapi) While this makes sometime things difficult, these are fairly standard framework and most of our developers are able to help on all. However, as I see us starting to look at JS for some of our apps (fedora-hubs, wartaa...), I wonder if we could start the discussion early about the different framework and eventually see if we can unify around one. This would also allow those of us not familiar with any JS framework to look at the recommended one instead of picking one up semi-randomly. So has anyone experience with one or more JS framework? Do you have one that would you recommend? Why? Thanks for your inputs, Pierre

10 12

Fedora Infrastructure Authentication Roadmap
by Kevin Fenzi 29 Jun '18

29 Jun '18

Greetings. Sorry it took so long to write this up and send it out, but here's our proposed plan for authentication moving forward. Please do feel free to comment or suggest changes/improvements here. Any mistakes are mine alone. :) Fedora Project Auth roadmap Background/History The Fedora project created its own authentication/user/group management system at nearly the beginning of its existance. FAS (Fedora Account System) (version 1) and then a rewrite (FAS2). At each of these points other solutions were investigated and found unacceptable for various reasons. Over the last few years, several additional applications have been added next to FAS2 to provide additional functionality: ipisilon has been added as a identity provider, and FreeIPA has been added for kerberos authentication. FAS2 is still the authoritative source of authentication data. FAS2 is currently deployed on RHEL6 servers and won't run on RHEL7. Also during the last few years, a new FAS re-write has been slowly in the works. FAS3 is written in a modern framework and has a number of functionality and interface improvements over FAS2. Additionally it can run on RHEL7. Goals and Critera Maintaining authentication applications is difficult and time consuming work, and it has always been a goal to try and move to more industry standard applications as much as possible given our goals and critera. The last time we looked, Some of those goals/critera include: * User self service registration * User self service password reset * FPCA acceptance requirement * Basset integration (may not be needed anymore) * Allow Self Service groups with their own sponsors/admins * Allow group requirements (other group first, etc) Plan: On discussion with FreeIPA developers and looking at how things are setup now, we came up with a plan to get what we need, but reduce the footprint and maintance we need to do. Many of the features we were hoping to use in FAS3 have now been implemented upstream in FreeIPA (2fa, fasClient syncing better, etc). Basically we will: * A new small wrapper type project is written (Community Account Information API) or CAIAPI. This small app provides the Critera listed above, talking at first to FAS2 on the backend then, later switching to talking to FreeIPA on the backend and providing a json API to consumers. * Switch anything we have using the direct FAS api to use CAIAPI instead. * Move to FreeIPA being the canonical source for authentication data. This should just be a switch to CAIAPI, and no consumers should even notice. * FreeIPA still provides kerberos auth. Note that kerberos will remain limited to use at ipsilon and koji. * Ipsilon provides identity auth for applications, preferably with OIDC (still provides others) * A new small website that uses the CAIAPI json to provide end user access / management. This thing would be in flask and needs a name still. Since https://fedoraproject.org/wiki/Infrastructure/fas_freeipa FreeIPA has matured and our understanding of the work required to make CAIAPI and a small web consumer has clarified. Pros: * IPA handles all the storing of credentials, replication and such and we just use it. * Our maint goes from needing to maintain FAS2 or FAS3 to just CAIAPI (a much smaller api) and a very small web application. * Easier to audit 2 small apps. * We can try and share the CAIAPI with other open source communities (Gnome? CentOS? others?) Open Source Communities already using FreeIPA would be easy to add this to. * We can stop using fasClient in favor of ipa-client setup (no more heavy syncing) * The heavy security aspects will be handled by upstreams we don't need to fully maintain (FreeIPA, sssd, ipsilon, etc). Cons: * We still need to write the CAIAPI/webapp, although Patrick may have CAIAPI already somewhat implemented. * It feels very sad to have spent so long on FAS3 and never deploy it, but sometimes thats just the way things go. ;(

6 7

Infrastructure office hours
by Clement Verna 12 Jun '18

12 Jun '18

Dear all, I would like to get feedback about starting a weekly infrastructure office hours which would be used to help anyone with contributing to Fedora's infrastructure. This would be a dedicated IRC meeting where people would be available to answer questions, help setting up development environment or even maybe work together on an issue. It could also be used to add more details to the issues we have in our backlog to help new contributor to get started. Note that we already have a general "ask whatever, whenever" on #fedora-apps and #fedora-admin where anybody can "ask whatever, whenever" :-), but this does not seems to work since we have very few requests. So do you think that having a dedicated meeting where you know that people are available would improve the situation ? Thanks Clément

7 9

Fedora and PDC
by Pierre-Yves Chibon 11 Jun '18

11 Jun '18

Good Morning Everyone, We have been informed thst week at the upstream devs working on the product-definition-center (PDC) are moving away from the project and are going to leave it without a maintainer. Since we adopted PDC for a variety of data flows, this puts us in an awkward position. :( Ralph and I met up on Tuesday to brainstorm the list of things we actively use PDC for today and to come up with a contingency plan for how to handle them. One overarching option is for us (fedora-infra) to take ownership of the PDC codebase as a whole. We didn't fully explore this option, figuring that the codebase is large and contains lots of tables, endpoints, and codepaths that we didn't use nor which we plan to use. Instead, below we've got the four things we use PDC for and some options for what to do with each. With the exception of /modules/, one common pattern that we like is to investigate splitting out the "django apps" that make up PDC into their own projects. We're calling these "pdc-lite", for fun. See more below. * Modules The data in the /modules/ PDC endpoint is *also* in the MBS db. Ralph's team is going to just use that and stop using pdc anything for modules. We're going to need to patch pungi, mbs for local builds, and a few other places. This should be a relatively low-pain transition. * Stream branches, branch ownership, retirement dates? - SLA/EOL are currently stored in PDC. - Queried by releng scripts for retirement, fedrepo-req for new branches, etc.. option #1 git repo full of yaml file similar to the override repo compiled into a single JSON blob Single place for all retired packages This feels like the lowest tech option. git gives us change control for free... but people easily get lost in the "UX" of navigating a gigantic git repo full of plaintext files. option #2 pagure's DB/API pagure knows nothing about branches currently, so that would be bigger lift option #3 PDC internally is composed of ~20 "django apps" https://github.com/product-definition-center/product-definition-center/tree… We could pick the 2 or 3 that comprise the branches feature, copy them out, and turn them into their own service: the "branch definition center": BDC. That would be the "pdc-lite" approach mentionned above, ie: PDC with only the "app" of interest * release/life-circle tracking? option #1: PDC lite with just that app of interest option #2: JSON/yaml file on the proxies option #3: pkgdb-lite option #4: ??? compose tracking? impacted: fedfind option #1: PDC-lite with just that app of interest option #2: Drop this entirely? Adam probably really wants to keep the record of composes. option #3: ??? The "pdc-lite" options are attractive, across the board. One thing we get from this is greater clarity when discussing things formerly in PDC. If something is in the branch-definition-center, the compose-definition-center, or the release-definition-center.. you know what you're talking about. Today, when talking about whether or not something should be or is in "PDC", it is easy to get confused. I propose we start the discussion on the list and plan for a meeting sometime late next week to discuss it further with the interested parties (please signal yourself) What do you think? Pierre and Ralph

10 23

Migrating fedmsg to AMQP: a proposal
by Aurelien Bompard 05 Jun '18

05 Jun '18

Hey folks! Jeremy and I have been working on a proposal to migrate fedmsg from our current brokerless architecture to a broker-based architecture. The overview and reasons for the migration are described on this page: https://fedmsg-migration-tools.readthedocs.io/en/latest/migration/overview.… Head there if you want the details. The plan has the following requirements: * No flag day. * Don't disrupt any services or applications. * Don't break any services outside of Fedora's infrastructure relying on these messages. The first step is to deploy a broker in Fedora to use. In order to avoid a flag day, bridges from AMQP to ZeroMQ and ZeroMQ to AMQP have been implemented and will be deployed. In order to validate that the bridges are functioning, a small service will be run during the transition period that connects to fedmsg and to the AMQP queues to compare messages. After the bridges are running, applications are free to migrate. There are several options when migrating and each has advantages and disadvantages. We have written a new library called fedora-messaging that has the following features: * A method to define message schemas and offer automatic validation of messages using those schemas. * Boilerplate for typical publishers and consumers. Head over to the document for a demo! What do you think of this proposal? Any blind spots? Thanks! Aurélien

5 9

Meeting Agenda Item: Introduction Chandrakant Kumar
by chandrakant kumar 01 Jun '18

01 Jun '18

Hello, I have gone through Fedora Infrastructure Getting Started wiki [1] and Fedora Infra docs [2] and wanted to introduce myself to this group. Your IRC handle chankuma What skills you have to offer Proficient in Python and Bash, I have also built web applications with django and flask. What you want to learn Systems administration skills, Infrastructure automation. [1] https://fedoraproject.org/wiki/Infrastructure/GettingStarted [2] https://pagure.io/infra-docs

2 1

FAS: SSH key type: Is it still required to use a RSA key?
by Christian Stadelmann 01 Jun '18

01 Jun '18

Today I added a ssh key to my account on FAS [1]. It says I should upload a RSA key, this is part of the help text: "Warning: In case of having ECDSA key please upload the two types of keys because some of our servers may not accept ECDSA keys." Is this warning still true? If yes, does it apply to the pagure instance on src.fedoraproject.org (ssh: pkgs.fedoraproject.org) too? I'm asking because I thought I'll stop using old pre quantum computer aera crypto and try ed25519 instead. [1] https://admin.fedoraproject.org/accounts/user/edit/genodeftest

2 2

Looking up module information via Koji
by Owen Taylor 31 May '18

31 May '18

My understanding is that with the planned retirement of the PDC: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr… Querying for module information should be done using the MBS and/or Koji APIs. Various code that I maintain (in OSBS, fedmod, and random tooling) wants to do module build lookups - different variations of "look up the modulemd for latest build of a NAME:STREAM[:VERSION]". Variations generally being exactly what "latest" means here. The code generally already is using Koji and the MBS api is quite limited, so I've chosen to do the lookups via Koji. https://fishsoup.net/misc/get-module-builds Is a test tool that incorporates most of the capability that I needed across my uses. It's distinctly more than a couple of lines of code - I can cut-and-paste it for now, but what's the right long-term home? Is there a simpler way? My best idea right now is that if the 'base_version' and'status' part of my code was simplified to simply be "tag" and avoid reliance on the tag structure of Fedora, then this might make a reasonable addition to the Koji CLI and API - there are some things that using raw tags for the query makes trickier, but it's probably workable. Thanks for any input! Owen

1 1

Librepo/dnf zchunk integration question
by Jonathan Dieter 31 May '18

31 May '18

Zchunk works by comparing an old version of the file with the one you want to download, but when dnf refreshes a repository, it downloads the new file into a temporary directory with no information passed to the handle about where the old files are. I've been trying to keep my code changes in libsolv and librepo to make zchunk integration as universal as possible. Up until now, I have managed to do so without changing librepo's API, but I don't see any way to fix this except to have dnf pass information about the old directory (or, even better, the cache directory) to the handle, which will mean an API change. It would also mean that other utilities would probably need to do the same. Is there something I'm missing in dnf's interaction with librepo that would allow me to work around this, or do I just need to bite the bullet and propose a librepo API change? Jonathan

1 0

Infrastructure Meeting 2018-05-31 14:00 UTC
by Stephen John Smoogen 31 May '18

31 May '18

= Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2018-05-31 at 14:00 UTC in #fedora-meeting-1 on the freenode network. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. 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 (2018-05-31) #meetingname infrastructure #topic aloha #chair smooge relrod nirik pingou puiterwijk tflink = 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 relrod PTO 9 Jun - 19 Jun #info smooge PTO 8 Jun, 15 Jun -> 18 Jun #info bodhi-3.8.0 deployed = 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 2018-05-29->2018-06-04 #info Nirik is on call from 2018-06-05->2018-06-11 #info Smooge is on call from 2018-06-11->2018-06-15 #info (!Smooge|!Relrod) is on call from 2018-06-15->2018-06-18 #topic Fedora web dev clinic resurrection (https://communityblog.fedoraproject.org/friday-fedora-web-dev-clinic/) - cverna #topic Tickets discussion #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=2 Go thru each ticket one by one = 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 none this week = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

openshift outages this week (both stg and prod!)
by Kevin Fenzi 29 May '18

29 May '18

Greetings. I'd like to have a outage for staging openshift tomorrow starting at 21UTC and running hopefully only an hour or so. I want to reinstall it and try and enable some new features we want to work with (cri-o containers, some storage for registery). Is that ok for all staging openshift users? Sorry for the short notice. Then, I'd like to have an outage for our production openshift on thursday starting at 21UTC. I'd like to reinstall it also from the ground up. It's currently 3.6 and the vm's are not sized correctly for the newer versions. I had hoped I could take each vm out, reinstall it and then readd it, but once I got to the master nodes it started to become too much hassle. I'd like to just reinstall it with 3.9 and reinstall all apps via their playbooks. I'll file the outages in a few and try and @ as many folks as I think might be interested in this, but if you have any issues, please chime in here or there. Thanks! kevin

1 0

Fedora Infrastructure Meeting 2018-05-23 1400 UTC Agenda
by Stephen John Smoogen 24 May '18

24 May '18

This shared document is for the next fedora infrastructure meeting. = Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2018-05-24 at 14:00 UTC in #fedora-meeting-1 on the freenode network. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. 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 (2018-05-24) #meetingname infrastructure #topic aloha #chair smooge relrod nirik pingou puiterwijk tflink = 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 more hardware installed #info relrod PTO 9 Jun - 19 Jun #info smooge PTO 8 Jun #info Problem with mirrormanager and newest rsync found/fixed #info armv7 Builders downgraded to fedora 27 - kevin #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 reminder and discussion - kevin #topic Tickets discussion #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=2 Go thru each ticket one by one = 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 none this week = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

[Fedocal] Reminder meeting : Bodhi stakeholder's meeting
by bowlofeggs＠fedoraproject.org 22 May '18

22 May '18

Dear all, You are kindly invited to the meeting: Bodhi stakeholder's meeting on 2018-05-22 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Source: https://apps.fedoraproject.org/calendar/meeting/4671/

1 0

Meeting Agenda Item: Introduction afdez
by Alexis Fernández 21 May '18

21 May '18

Hello, everyone, I'm going to introduce myself according to the Fedora guide to start contributing to this awesome project: - IRC nick: afdez. - Skills: - Programming: Bash, PHP, SQL, Java, HTML, - Sysadmin: Databases, Networks, Unix Server Administration, Centos, FreeBSD, FreeNas, Fedora, Arch Linux. Certs related: MTCNA, LPIC1. - Want to learn: Python, security related topics, sysadmin related topics. - I own different systems to test, workstation, servers and core versions. (Laptops, desktops and Rpis). - I have experience in professional software development for 8 years and the last 3 as Linux system administrator. - I'm willing to help in any area you think I can be of use. Thanks in advance.

1 0

Modularity WG + f2 + Infra
by Randy Barlow 18 May '18

18 May '18

Greetings! At the hackathon we did recently, we talked about the need for one of us to attend the Modularity WG meetings so we could be more aware of what work is coming our way before it's a surprise, and I volunteered to be that person. For $reasons, today was the first of the WG meetings I was able to attend. There were two items of interest: New service =========== I learned that Factory 2 is developing a new service called Ursa Major. I gathered that its mission is to make it so that RPMs that depend on modules can get those modules pulled into their buildroot. Ralph, is the above correct? If so, what time frame do you anticipate us needing to get this service deployed to infrastructure? Meetings ======== The modularity WG suggested that it was probably not that beneficial for me to attend their meetings as an infra liason, as they are not actually particularly familiar with the infrastructure side of things. They suggested instead that we interface with Factory 2. A suggestion was made that perhaps we could have an agenda item on *our* meeting, perhaps once a month, where we invite modularity WG and factory 2 to talk with us about what is coming our way, or about issues that need dealing with. I thought this was a fine suggestion, so I wanted to ask you all what you thought about it?

5 4

Factory2/Infra sync up meeting - May 2018
by Pierre-Yves Chibon 18 May '18

18 May '18

Greeting, Last Monday Ralph and I had our monthly meeting for Factory2/Infra sync up. We went over the event that lead to disabling gating in bodhi last week (see fesco ticket: https://pagure.io/fesco/issue/1872) If this situation happens again we encourage a stronger reach out for help from the folks involved (in this case Ralph or Dan Callaghan (dcallagh) who hangs on #fedora-admin and was around while the discussion was happening), by stronger we are putting down a phone call or a text as valid means. We talked about PDC, as you may recall PDC is being decomissioned upstream leaving us with no maintainer upstream. Since the team is currently quite busy with other priorities we agreed to restart this discussion in early June with all parties who expressed interest on the thread on this list. Finally, Ralph explained the new workflow they put in place to deploy their images in our openshift. This is all documented in: https://pagure.io/infra-docs/pull-request/109 Folks are welcomed to take a look at it and comment with their thoughts on the process. In short:images are built and hosted in quay, the latest tag is automatically added if the image passes testing, openshift in staging is configured to pull from the latest tag. Then a "prod" tag can be manually added to an images that openshift will pull in prod. @patrick: with your security officer hat, does this sound good to you ^? If not, the Factory crew is willing to look at other options. Hoping this is helpful, Pierre

2 3

Bodhi 3.8.0b0
by Randy Barlow 17 May '18

17 May '18

Greetings! I have deployed bodhi-3.8.0b0[0] to staging[1]. It's mostly a feature release. I do have one critical bugfix[2] that I plan to include in 3.8.0 so this is not the final beta, but I had built this beta before I had the decision to include that bug so I figured I'd go ahead and get it deployed. Happy testing! [0] https://bodhi.stg.fedoraproject.org/docs/user/release_notes.html [1] https://bodhi.stg.fedoraproject.org/ [2] https://github.com/fedora-infra/bodhi/issues/2368

1 0

Re: IRC oncall
by Zach Villers 17 May '18

17 May '18

Well, we have talked about mentoring in the past, but we run into issues with it. It's hard for someone just learning to spend tons of time being mentored and we can't (and don't want to!) force them to either. So we don't know who is going to be around for a while or who has time. Not what folks are asking, but you can pick up a lot just by hanging out and watching the on-call person mutter to themselves in IRC ( not sure that is the right phrase umm... ) I don't know if this will translate for everyone, but there is a concept of "rubber duck" problem solving, where if you have a particularly difficult issue, and you explain it to someone, it helps you solve the problem more easily. I don't know if this is how everyone works and it really doesn't help if someone is jumping up and down and quacking while your are trying to think. I guess my point is, just hanging out unobtrusively when you can is fairly helpful all around. do some kind of intensive mentoring> I wonder what it would be like if there were an apprentice slot for each oncall shift? For example, an apprentice is scheduled to be paged with the oncall sysadmin, then at the least can shadow the syasadmin, help with communication on IRC, do initial troubleshooting & monitoring with the apprentice auth/access level, etc. If I recall, alerts are pretty easily accessible. You can poke around on Nagios if there are issues. Obviously if everything is down/red, it's not a good time to ask for help with your ssh access. Well, depends on the stuff I guess. It means that the oncall person not only has to watch for and respond to pings on irc and triage tickets, but then explain/teach a apprentice. If there is time and willing apprentice thats great! If things are really busy, it could be too much work to do at once. I'm open to ideas here... we should all try and figure better ways to get stuff done and learn and have a good time doing it. :) kevin A couple ideas; - stream your terminal session when working an outage ( could be hard to find a 100% foss version that is secure ) - plan some outages in stage for apprentices to work at some time when tickets are low and nothing urgent is planned ( I don't know that I've ever heard of such a time, but in theory it could exist ) Of course, it's late here, so this may all turn out to be nonsense, but good discussion anyway. -Zach #aikidouke

3 2

Fedora Infrastructure Meeting 2018-05-17 1400 UTC Agenda
by Stephen John Smoogen 17 May '18

17 May '18

This shared document is for the next fedora infrastructure meeting. Please update the Gobby or read it at https://gobby.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure-me… = Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2018-05-17 at 14:00 UTC in #fedora-meeting-1 on the freenode network. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. 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 (2018-05-17) #meetingname infrastructure #topic aloha #chair smooge relrod nirik pingou puiterwijk tflink = 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 relrod moving hosts to new boxes #info relrod PTO 9 Jun - 19 Jun #info Pagure updated #info Aarch64 Builders downgraded to fedora 27 - kevin #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 Tickets discussion #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=2 Go thru each ticket one by one = 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 none this week = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

IRC oncall
by Kevin Fenzi 16 May '18

16 May '18

Greetings everyone. As those of you who frequent IRC probably already know, we are trying out having a Fedora Infrastructure "oncall" person for IRC reuqets/queries/pings. You can find out who this is by asking zodbot: zodbot: oncall smooge (Stephen Smoogen) is oncall. If I do not respond please file a ticket and then we would really appreciate it if you directed your IRC ping to the nick listed in oncall or (as the reply says) just file a ticket. Why are we doing this? Well, there are 4 of us who are full time paid sysadmin/ops folks for Fedora Infrastructure and we were finding that a large portion of time for everyone was being taken up by IRC interrupts. Sometimes interrupting multiple people for non urgent tasks. We could of course just ignore IRC, but that prevents us from handling urgent interrupts where we do want to look at something quickly. Additionally, when the oncall person doesn't know how to solve or handle some issue, they can talk to whoever does know and learn how to do it and document it. With this setup, the oncall person can plan on watching IRC and everyone else can focus on tasks that require more concentration. If your issue is not time sensitive or urgent, do also just consider filing a ticket and we will triage it and work it as soon as we are able. Thanks in advance for helping us out here. kevin

4 4

[Release] pagure 4.0.2 and 4.0.3
by Pierre-Yves Chibon 15 May '18

15 May '18

Good Morning Everyone, Yesterday I cut two new releases of pagure: 4.0.2 and 4.0.3. These are important releases, 4.0.2 addresses a CVE that was reported earlier in the day, it's not a "sky is falling" type of CVE but still nicer to have it fixed. Basically, anyone with an API key that allowed to modify project could create git branches on any project. This has been mitigated by having a dedicated ACL for creating git branches. So if you have an API token that you use to create git branches you will need to get a new one with this new ACL. 4.0.3 is correcting bugs introduced by backporting some more fixes to 4.0.2 than just this CVE but not backporting enough, so 4.0.3 basically makes 4.0.2 work. Here are the corresponding changelogs for these releases: 4.0.3 (2018-05-14) ------------------ - Backport utility method from the 4.1 code to fix the 4.0.2 release 4.0.2 (2018-05-14) ------------------ .. note:: This release fixes CVE-2018-1002151 - Fix showing the list of issues in a timely fashion (Patrick Uiterwijk) - Fix stats for commits without author (Lubomír Sedlář) - Explain how to fetch a pull request locally and some grammar fixes (Todd Zullinger) - Drop the constraint on the requirement on straight.plugin but document it - Fix the requirement on bcrypt, it's optional - Make API endpoint for creating new git branch have its own ACL fixes CVE-2018-1002151 All known pagure instance have been upgraded to 4.0.3 Happy coding, Pierre

1 0

FBR: Change to category based crawling
by Adrian Reber 13 May '18

13 May '18

As discussed previously I would like to change the crawler to crawl each category separately. The goal is to reduce the load on the database by distributing the crawling better over the whole day and to reduce the chance of mirrors being disabled because of the high database load. This should also remove the need for mirror administrators to create multiple hosts in MirrorManager to work around the 4 hours timeout per host. Attached is my patch. Please +1. This affects mm-crawler01 and mm-crawler02. Adrian

3 4

[release] pdc-updater: 0.9.2
by Ralph Bean 11 May '18

11 May '18

A new release of pdc-updater is out, fixing a bug in the retirement handler. https://pagure.io/fedora-infrastructure/issue/6928 0.9.2 ----- Pull Requests - #86, Merge pull request #86 from fedora-infra/dont-overwrite https://github.com/fedora-infra/pdc-updater/pull/86 Commits - 65ebd4ad9 Don't overwrite `branch`. https://github.com/fedora-infra/pdc-updater/commit/65ebd4ad9

1 0

Bodhi stakeholders' meeting
by Randy Barlow 10 May '18

10 May '18

Greetings! I would like feedback from you about the usefulness and/or format/schedule of the Bodhi stakeholders' meeting. I've been holding this meeting about once every 4 weeks. It started off pretty well with lots of seemingly interested participation, but over time it seems that fewer people attend. I would like to identify why the attendance is lower so I can adjust to it. Here are some thoughts: Is the meeting too often? ========================= I've thought perhaps about reducing it to once every 3 months instead of once every 4 weeks. Perhaps this way there would be more to discuss? Is the time of the meeting bad? =============================== I know it is a bad time for our west coast North America friends. Is it also a bad time for others? I could try to move it to be later in the day if that would help. Is it boring? ============= Is the meeting just not relevant to you? Does it lack purpose? Other ===== Other thoughts? Proposal ======== I've been considering reducing it to once every 3 months and making it later in the day for west coast people. I've also considered if it would be good to make it be part of the weekly infrastructure meeting on that 3 month schedule (i.e., just have an agenda item once every 3 months to focus on Bodhi in the established infra meeting). Thoughts on this?

2 1

Bodhi 3.7.0-0.0.beta deployed to stg
by Randy Barlow 10 May '18

10 May '18

Greetings! I just deployed a Bodhi 3.7.0 beta[0] build to stg[1]. This is a pretty targeted release with only 4 patches, all aimed at improving the developer experience with respect to package gating. Testing is appreciated! [0] https://bodhi.stg.fedoraproject.org/docs/user/release_notes.html#v3-7-0[1] https://bodhi.stg.fedoraproject.org/

2 5

Slow Pagure.io
by Vít Ondruch 09 May '18

09 May '18

Hi, Pagure.io is so slow for me to that point that I simple can't open ticket to report it. IOW, I am trying to load https://pagure.io/fedora-infrastructure/issues in my browser and it does not work, it just waits for response :/ ~~~ $ curl https://pagure.io/fedora-infrastructure/issues -o /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 107k 100 107k 0 0 30755 0 0:00:03 0:00:03 --:--:-- 30764 $ traceroute pagure.io traceroute to pagure.io (152.19.134.147), 30 hops max, 60 byte packets 1 _gateway (192.168.0.1) 3.274 ms 4.385 ms 4.320 ms 2 * * * 3 ip-86-49-1-161.net.upcbroadband.cz (86.49.1.161) 22.197 ms 22.094 ms 22.066 ms 4 cz-brn-pop40-ra2-vla2191.net.upc.cz (84.116.220.246) 121.057 ms 124.204 ms 124.182 ms 5 cz-brn-pop40-ra1-vla2110.net.upc.cz (84.116.221.41) 126.583 ms 126.456 ms 126.449 ms 6 cz-prg01a-ra4-vla2109.net.upc.cz (84.116.221.37) 126.402 ms 111.096 ms 116.115 ms 7 de-fra04a-rc1-ae33-0.aorta.net (84.116.135.5) 110.803 ms 137.982 ms 137.875 ms 8 de-fra04d-rc1-ae26-0.aorta.net (84.116.138.238) 137.842 ms 137.777 ms 137.724 ms 9 * * * 10 us-nyc01b-rd2-ae9-0.aorta.net (84.116.140.170) 138.336 ms 138.298 ms 115.267 ms 11 us-nyc01b-ri2-ae3-0.aorta.net (84.116.137.194) 114.465 ms 112.698 ms 110.019 ms 12 nyc2-brdr-01.inet.qwest.net (63.235.40.165) 136.127 ms 136.117 ms 136.086 ms 13 dca-edge-23.inet.qwest.net (67.14.6.158) 159.519 ms 159.547 ms 161.527 ms 14 65.120.78.78 (65.120.78.78) 136.700 ms 135.992 ms 135.886 ms 15 uncmanning-to-rtp-ip-asr-gw.ncren.net (128.109.19.90) 132.844 ms 137.504 ms 136.760 ms 16 core-m-v1214.net.unc.edu (152.19.255.66) 135.283 ms 136.117 ms 138.533 ms 17 152.19.255.70 (152.19.255.70) 128.737 ms 128.655 ms 128.518 ms 18 152.19.255.166 (152.19.255.166) 147.476 ms 132.950 ms 137.336 ms 19 vmhost1-rsa.fedora.ibiblio.org (152.19.134.147) 126.626 ms !X 130.794 ms !X 121.215 ms !X ~~~ The strange thing is that the pagure title page or the project overview can be loaded just fine and neither the tools above shows any suspicious behavior to me. Vít

5 8

Re: Planned Outage - Ibiblio Servers (fedorapeople.org, torrent01.fedoraproject.org) 2018-05-09 12:00 UTC
by Stephen John Smoogen 08 May '18

08 May '18

This outage has been cancelled for the time being. A new ticket and announcement will be created when it has been rescheduled. On 7 May 2018 at 13:02, Stephen John Smoogen <smooge(a)gmail.com> wrote: > Planned Outage - Server updates - 2018-05-09 12:00 UTC > > There will be an outage starting at 2018-05-09 12: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 '2018-05-09 12:00UTC' > > Reason for outage: > > Ibiblio is moving systems to a newer rack with 10G SFP+ networks. > Systems will need to be powered down, moved over to the new racks, > powered back up, configured to use the new networks in failover mode. > > Affected Services: > > download-ib01.fedoraproject.org > pagure-proxy01.fedoraproject.org > proxy04.fedoraproject.org > noc02.fedoraproject.org > unbound-ib01.fedoraproject.org > ns02.fedoraproject.org > people02.fedoraproject.org > proxy12.fedoraproject.org > smtp-mm-ib01.fedoraproject.org > torrent02.fedoraproject.org > > Torrent and people will be down during that time. Systems configured > to use download-ib02 will also be. > > Ticket Link: > > https://pagure.io/fedora-infrastructure/issue/6915 > > Please join #fedora-admin or #fedora-noc on irc.freenode.net > or add comments to the ticket for this outage above. > > -- > Stephen J Smoogen. -- Stephen J Smoogen.

1 0

Meeting Agenda Item: Introduction Alexander Marek
by Alexander Marek 08 May '18

08 May '18

To whom this may concern, My name is Alex and I'm studying Cybersecurity, with plans to go into the IT/Information Security field. Recently I've been studying for my Red Hat Certified System Administrator certification and hope I can bring my new skillset to help benefit my favourite distribution. I plan to pass my Offensive Security Certified Professional certification by the end of August. Alongside this, I'm currently taking college courses part time. Hopefully I can be useful, and I'm looking forward to seeing what the Fedora Project has in store! Regards, Alexander Marek IRC Handle: apmarek

1 0

Introduction
by Alexander Marek 08 May '18

08 May '18

To whom this may concern, My name is Alex and I'm studying Cybersecurity, with plans to go into the IT/Information Security field. Recently I've been studying for my Red Hat Certified System Administrator certification and hope I can bring my new skillset to help benefit my favourite distribution. I plan to pass my Offensive Security Certified Professional certification by the end of August. Alongside this, I'm currently taking college courses part time.Hopefully I can be useful, and I'm looking forward to seeing what the Fedora Project has in store! Regards, Alexander Marek

1 0

Planned Outage - Ibiblio Servers (fedorapeople.org, torrent01.fedoraproject.org) 2018-05-09 12:00 UTC
by Stephen John Smoogen 07 May '18

07 May '18

Planned Outage - Server updates - 2018-05-09 12:00 UTC There will be an outage starting at 2018-05-09 12: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 '2018-05-09 12:00UTC' Reason for outage: Ibiblio is moving systems to a newer rack with 10G SFP+ networks. Systems will need to be powered down, moved over to the new racks, powered back up, configured to use the new networks in failover mode. Affected Services: download-ib01.fedoraproject.org pagure-proxy01.fedoraproject.org proxy04.fedoraproject.org noc02.fedoraproject.org unbound-ib01.fedoraproject.org ns02.fedoraproject.org people02.fedoraproject.org proxy12.fedoraproject.org smtp-mm-ib01.fedoraproject.org torrent02.fedoraproject.org Torrent and people will be down during that time. Systems configured to use download-ib02 will also be. Ticket Link: https://pagure.io/fedora-infrastructure/issue/6915 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

[release] Anitya v0.12.0
by Jeremy Cline 07 May '18

07 May '18

Hi folks, I've tagged Anitya v0.12.0[0]. I don't have access to the PyPI project and it's not packaged for the Fedora repository, so it's only available from GitHub at the moment. I don't have an ETA for when it's deployed to Fedora's infrastructure, either. [0] https://anitya.readthedocs.io/en/0.12.0/release-notes.html -- Jeremy Cline XMPP: jeremy(a)jcline.org IRC: jcline

1 0

[PATCH] Add version 1.2.0 of Fedora Bootstrap
by Ryan Lerch 07 May '18

07 May '18

This patch adds version 1.2.0 of fedora bootstrap into apps.fp.o/global for use in Fedora apps. This version of Fedora bootstrap uses the stable 4.0.0 release of Bootstrap. cheers, ryanlerch

3 2

Meeting Agenda: Introduction
by nrasool＠gmail.com 03 May '18

03 May '18

Greetings all, My name is Nabil Rasool and I work in Information Security. Hoping to offer 5-10 hours a week, potentially more. I was a CS major in college so have coded in C++ in the past. I’d like to learn more about Fedora and help out in any way I can. I don’t have any particular outstanding issues that I’d like to work on off the bat but will hopefully have something after a couple of meetings. I’m also interested in the fi-apprentice group and learn the infrastructure. Lastly, I think this is a great project and would love to contribute. I’m looking forward to being at the meeting tomorrow. V/r, Nabil IRC handle: piston

1 0

Fedora Infrastructure Meeting 2018-05-03 1400 UTC Agenda
by Stephen John Smoogen 03 May '18

03 May '18

The infrastructure team will be having its weekly meeting tomorrow, 2018-05-03 at 14:00 UTC in #fedora-meeting on the freenode network. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. 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 (2018-05-03) #meetingname infrastructure #topic aloha #chair smooge relrod nirik pingou puiterwijk tflink = 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 Fedora 28 released! Kudos to everyone! #info Freeze is over #info Pagure 4.0 being deployed #info New openshift being deployed #info Bodhi updates are happening #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 Tickets discussion #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=2 Go thru each ticket one by one = 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 none this week = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

Fedora 28 Final freeze now in effect!
by Kevin Fenzi 02 May '18

02 May '18

Greetings. we are now in the infrastructure freeze leading up to the Fedora 28 release. This is a final release freeze. We do this to ensure that our infrastructure is stable and ready to release the Fedora 28 when it's available. You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script: git clone https://infrastructure.fedoraproject.org/infra/ansible.git ansible/scripts/freezelist -i inventory Any hosts listed as freezes is frozen until 2018-05-01 (or later if release slips). Frozen hosts should have no changes made to them without a sign-off on the change from at least 2 sysadmin-main or rel-eng members, along with (in most cases) a patch of the exact change to be made to this list. Thanks, kevin

1 1

FBR: Update libmodulemd on bodhi-backend01
by Patrick マルタインアンドレアス Uiterwijk 01 May '18

01 May '18

Hi, I have had to update libmodulemd on bodhi-backend01, because it requires the "modulemd_objects_from_file" function in libmodulemd, which was added in version 1.2, but it is lacking a (versioned) requirement on libmodulemd, and due to the freeze we still had modulemd v1.1. This should not have any impact, other than that we can actually send out module updates again. Any +1s or complaints? Regards, Patrick

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure May 2018