June 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

[PATCH] bodhi update run: Attempt to get better Atomic images media name during updates run
by Sinny Kumari 14 Aug '18

14 Aug '18

From past few weeks, we have started producing Atomic composes media during Fedora 28 bodhi updates and updates-testing run. Media name of AH ISO are perfectly fine. But for cloud images media name[1] looks something like Fedora-AtomicHost-28_Update-20180620.1235.x86_64.qcow2 for qcow2. It will be nice to have media name like Fedora-AtomicHost-28-20180620.0.x86_64.qcow2 which is what we get during regular atomic twoweek compose run [2]. This patch (available in email attachment) attempts to fix the media name. Taken inspiration from releng issue [3] and ansible commit [4]. I am not sure how to test it locally, any pointers will be useful. [1] https://kojipkgs.fedoraproject.org/compose/updates/Fedora-28-updates-201806… [2] https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-28-2018062… [3] https://pagure.io/releng/issue/7113 [4] https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=40c32c…

3 9

[PATCH] OSTree: Force to create new ostree commit during updates compose run
by Sinny Kumari 03 Jul '18

03 Jul '18

This patch (available in email attachment) is to create new ostree commit when there is no content changes since last commit during updates compose run. By passing force_new_commit as True, pungi runs rpm-ostree command with option --force-nocache . More details are in releng ticket - https://pagure.io/releng/issue/7585 Thanks, Sinny

2 6

Fedora and PDC, road forward
by Pierre-Yves Chibon 02 Jul '18

02 Jul '18

Good Morning Everyone, So yesterday we held a meeting on #fedora-apps about the future of PDC in Fedora. We kept notes in etherpad at: http://etherpad.osuosl.org/pdc_fedora Here is the gist of it: What do we currently store in PDC: * modules data - the list of what modules have been built, what rpms are in them, and which ones are active or not. * Stream branches, branch ownership, retirement dates (EOL/SLE) * release/life-circle tracking * product and product versions (fedpkg gets active Fedora and EPEL releases from product versions endpont) * critpath boolean on packages (bodhi uses this) * metadata from composes (RPMS/images) * "dependency" data about which rpms depend on which other rpms and which containers include other rpms. This is not used by anything and can be de-prioritized, dropped. (It was originally going to be used in Freshmaker.) Endpoints: * release-component-relationships * release-components * List of all packages: fedora-packages uses this list to know what to index. It sets up the "for loop" from which fedora-packages pulls data from all our other systems. Endpoints: * global-components After some discussion the decision we reached was: * The "dependency" data in its current form can be dropped. It's something we'll need in the future but the data structure will most likely need to be adjusted so let's just drop the existing data and worry about this later. * The critpath boolean can just be imported into bodhi itself, especially considering that bodhi is the only tool using this flag. * The modules data is entirely going to move into MBS Everything else (ie: composes metadata, release/life-circle tracking, package/branches information) will need to find a new home. This new home will be a new django app using the Django Rest Framework (DRF) in which we will import the PDC apps as needed (potentially adjusting them where desired). - kellin has agreed to be the project leader for this work but needs a team to do the actual work. - pingou has agreed to look for said team If you have any worries, questions or suggestions or if you want to join the effort, please let us know :) Finally some links: Minutes: https://meetbot.fedoraproject.org/fedora-apps/2018-06-11/pdc_and_fedora.201… Minutes (text): https://meetbot.fedoraproject.org/fedora-apps/2018-06-11/pdc_and_fedora.201… Log: https://meetbot.fedoraproject.org/fedora-apps/2018-06-11/pdc_and_fedora.201… Have a nice day, Pierre

6 17

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

Planned Outage: PHX2 services down/disrupted 2018-07-03 21:00 UTC
by Stephen John Smoogen 28 Jun '18

28 Jun '18

There will be an outage starting at 2018-07-03 21:00UTC, which will last approximately 6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2018-07-03 21:00UTC' Reason for outage: There have been a set up of updates for EL7 and Fedora requiring reboots of infrastructure. We will be rebooting the Build and remote systems outside of PHX2 on this day. Affected Services: Various web services housed in PHX2 may be up or down during the outage window. This will affect builds and authentication for short periods of time. Contact Information: Ticket Link: https://pagure.io/fedora-infrastructure/issue/7065 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

[Fedocal] Reminder meeting : Staging Reboot
by smooge＠gmail.com 27 Jun '18

27 Jun '18

Dear all, You are kindly invited to the meeting: Staging Reboot on 2018-06-27 from 18:00:00 to 22:00:00 GMT The meeting will be about: Moving virthost servers to new ips More information available at: [https://pagure.io/fedora-infrastructure/issue/7048](https://pagure.io/fedor… Source: https://apps.fedoraproject.org/calendar/meeting/9267/

1 0

Re: Fwd: Red Hat bugzilla upgrade coming -- test now!
by Zach Villers 26 Jun '18

26 Jun '18

Acknowledged Sir! :) I'll add it on the meeting agenda this week. -- Zach Villers zach(a)mailup.net On Mon, Jun 25, 2018, at 9:25 AM, Ralph Bean wrote: > FWIW, there's a change to the way messaging works with BZ5. > > - Messages are published to a different queue. Someone will need to > update bugzilla2fedmsg to pull from the new right place. > - The message format changes, but I think it may only be additive. > Someone should verify that we don't need any further code changes. > > -Ralph > > ----- Forwarded message from Matthew Miller <mattdm(a)fedoraproject.org> ----- > > Date: Thu, 21 Jun 2018 11:26:48 -0400 > From: Matthew Miller <mattdm(a)fedoraproject.org> > To: devel-announce(a)lists.fedoraproject.org > Subject: Red Hat bugzilla upgrade coming -- test now! > User-Agent: Mutt/1.5.21 (2010-09-15) > Reply-To: devel(a)lists.fedoraproject.org > > Red Hat is planning on upgrading Bugzilla to BZ5 in September. There's > a test instance running now at http://bugzilla5.redhat.com/ > > Since Fedora is a major user and stakeholder here, it'd be helpful if > we make sure everything works for us. If you find any bugs, report at > https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&version=5.0 > > -- > Matthew Miller > <mattdm(a)fedoraproject.org> > Fedora Project Leader > _______________________________________________ > devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org > To unsubscribe send an email to devel-announce- > leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr… > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… > > ----- End forwarded message ----- > _______________________________________________ > infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org > To unsubscribe send an email to infrastructure- > leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr… > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature)

2 1

[Fedocal] Reminder meeting : Infra Office Hours
by cverna＠fedoraproject.org 25 Jun '18

25 Jun '18

Dear all, You are kindly invited to the meeting: Infra Office Hours on 2018-06-26 from 18:00:00 to 19:00:00 UTC At fedora-admin(a)irc.freenode.net The meeting will be about: Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features. Source: https://apps.fedoraproject.org/calendar/meeting/9255/

1 0

is copr-be.cloud.fedoraproject.org DOWN?
by Satish Patel 25 Jun '18

25 Jun '18

I am building some packages and failed on https://copr-be.cloud.fedoraproject.org/results/thm/lxc2.0/epel-7-x86_64/ is copr-be.cloud.fedoraproject.org down? if yes then do you know any ETA? ~S

4 7

Re: Public facing space for Anaconda CI logs
by Kevin Fenzi 25 Jun '18

25 Jun '18

On 06/25/2018 12:33 AM, jkonecny(a)redhat.com wrote: > On Sat, 2018-06-23 at 11:23 -0700, Kevin Fenzi wrote: >> On 06/22/2018 09:38 AM, Martin Kolman wrote: >> >>> Yeah, that looks good: >>> - lack of backup/mirroring should not be a problem (the results are >>> more or less >>> ephemeral anyway & we can easily back them up internally if needed) >>> - upload speed should not be an issue for the PR test logs & we >>> plan to publish daily logs >>> from kickstart test runs, so even if there was a ~hour delay for >>> uploding the logs it should not >>> make much difference for once-a-day run. >>> >>> Using the existing gitanaconda group should be fine as well, >>> thanks. :) >>> >>> BTW, how would you recommend to handle the automated log uploads to >>> this space ? >>> >>> Is there some interface where we can set a SSH public key, so that >>> the test runner >>> can upload the logs there or something similar ? >> >> Other groups (cockpit at least) have created a fas user. I'd suggest >> something with 'bot' in the name like 'anaconda-bot'. Then login and >> set >> it's ssh key and add it to the group. > > We already have bot user with name: installker ok. You should be able to use that as long as you add it to the group. kevin

1 0

Staging outage 2018-06-27 18:00 UTC -> 22:00 UTC
by Stephen John Smoogen 25 Jun '18

25 Jun '18

There will be an outage starting at 2018-06-27 18:00UTC, 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-06-27 18:00UTC' Reason for outage: We will be updating and rebooting staging servers to new kernels as well as giving them new ip addresses. Affected Services: All staging systems will be down for some period during the outage Contact Information: smooge(a)fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/7048 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. Steps involved: Staging Hosts Move Add entries into dns Rename/reboot virthost04 to virthost02.stg a. Change hostname on host b. Change ips on host c. Edit ansible guests and playbooks d. Reboot Rename/reboot virthost05 to virthost03.stg a. Change ip on host b. Change hostname on host c. Edit ansible guests and playbooks d. Reboot Rename/reboot virthost11 to virthost04.stg a. Change ip on host b. Change hostname on host c. Edit ansible guests and playbooks d. Reboot Rename/reboot virthost20 to virthost05.stg a. Change ip on host b. Change hostname on host c. Edit ansible guests and playbooks d. Reboot -- Stephen J Smoogen.

1 0

Fwd: Red Hat bugzilla upgrade coming -- test now!
by Ralph Bean 25 Jun '18

25 Jun '18

FWIW, there's a change to the way messaging works with BZ5. - Messages are published to a different queue. Someone will need to update bugzilla2fedmsg to pull from the new right place. - The message format changes, but I think it may only be additive. Someone should verify that we don't need any further code changes. -Ralph ----- Forwarded message from Matthew Miller <mattdm(a)fedoraproject.org> ----- Date: Thu, 21 Jun 2018 11:26:48 -0400 From: Matthew Miller <mattdm(a)fedoraproject.org> To: devel-announce(a)lists.fedoraproject.org Subject: Red Hat bugzilla upgrade coming -- test now! User-Agent: Mutt/1.5.21 (2010-09-15) Reply-To: devel(a)lists.fedoraproject.org Red Hat is planning on upgrading Bugzilla to BZ5 in September. There's a test instance running now at http://bugzilla5.redhat.com/ Since Fedora is a major user and stakeholder here, it'd be helpful if we make sure everything works for us. If you find any bugs, report at https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&version=5.0 -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr… _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… ----- End forwarded message -----

1 0

Public facing space for Anaconda CI logs
by Martin Kolman 23 Jun '18

23 Jun '18

Hi, I would like to ask if it would be possible to allocate some storage space that would be publically available (eq. fedorapeople.org, or similar) we could use store logs from our CI so that external contributors can access them. Why is this needed ? Our CI runs in internal vm hosts and internal open stack, both if which is not accessbile from the public internet, has no public IP or domain. At the same time we would like the make te test results available, so that for example an external contributor can see the results of tests we run on their pull request. What tests does the Anaconda CI run ? - unit tests & Pylint we run on all pull requests for Anaconda and related projects - periodically run kickstart tests[0], a battery of 130+ integration test, where each test is basically a full kickstart-configured installation run What kind of environment would be needed ? Basically just a simple file/static html storage would be needed, where we can SCP the log files to. The general idea is that tests results would be uploaded to this space whem the respective tests finish & there would a periodic cleanup task that would keep last N logs & remove old logs. What ammount of storage space would be needed for this ? While the unit tests & pylint runs we do on Pull requests don't produce that much data, the kickstart test suite is in a different class. Each of the 130+ tests is a full installation run, which produces a sizeable ammount of data as we gather a substantial ammount of logs from each test (anaconda logs, dnf logs, lvm & storage logs). This data is important to debug all the various issues that can happen in what is essentially a full instrumented installation run. Our measurements have shown that each full kickstart test run (~130 tests) produces ~800 MB of logs. Therefore we would like to request 16 GB of space to be available so that we can store ~10 last tests results from kickstart test, a reasonable number of PR test results & have some room to spare. Would this be possible ? Requesting 16 GB might seem like a lot but I'm afraid we can't reasonably reduce the space requirements for logs from kickstart tests runs without at the same time also making test runs harder to debug. Looking for your feedback & don't be afraid to ask any questions about this proposal. :) Best Wishes Martin Kolman [0] https://github.com/rhinstaller/kickstart-tests

2 3

How often is sshkey sync from FAS to fedorapeople.org
by Zamir SUN 23 Jun '18

23 Jun '18

Hi Infra team, Today at around 11:26 AM UTC+8 I updated my ssh key to FAS. However I cannot ssh into fedorapeople.org use the new key. After I am back with my laptop (around 21:00 UTC+8), I ssh to it and found it is still using my old key. So I temporary added the new one. So my question is, how often is the pubkey updated to fedorapeople.org? Thanks! -- Ziqian SUN (Zamir) GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E Want to know more about Fedora? Visit https://fedoraproject.org/wiki/ Ready to contribute? See https://whatcanidoforfedora.org/

2 2

Meeting Agenda Item: Introduction Mike Oliver
by Mike Oliver 22 Jun '18

22 Jun '18

IRC: mklvr Skills: Development: - Perl - Bash - Some Python System Administration: - Ansible, SaltStack, NGINX, MySQL, RabbitMQ, Containers (Docker and Buildah/Podman), Kubernetes, Jenkins, PHP, Django, StackDriver, RHEL6/7, DNS, SMTP, E-mail Deliverability, Cisco ASAs, OPNSense Interests: - Improving existing skill set - Learning more about Nagios and OpenShift Tickets: - I might be able to resolve #6527 - I'm going to do some research on #6441 and #6442 I hope to see you at the next Fedora Infrastructure meeting. In the meantime I'll checkout the Getting Started page on the wiki.

2 1

[PATCH] twoweek: Stop building F27 Atomic twoweek nightly compose
by Sinny Kumari 21 Jun '18

21 Jun '18

Since F28 release, we no longer do atomic twoweek release based on F27 content. This patch (available in email attachment) is to stop running cron job for building F27 twoweek nightly composes.

3 4

Agenda for 2018-06-21 Infrastructure Meeting 14:00 UTC
by Stephen John Smoogen 21 Jun '18

21 Jun '18

This shared document is for the next fedora infrastructure meeting. = Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2018-06-21 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-06-21) #meetingname infrastructure #topic aloha #chair nirik pingou puiterwijk relrod smooge tflink threebean = 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 bowlofeggs is on PTO for a long time #info tflink is on PTO for a longer time = 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 Relrod is on call from 2018-06-20->2018-06-26 #info Smooge is on call from 2018-06-27->2018-07-05 #info ?? is on call from 2018-07-06->2018-07-12 #topic Ursa-major? https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr… - threebean #topic Office hours - how did it go? - kevin #topic Flock again - kevin #topic pkgdb retirement - kevin #topic Tickets discussion #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket 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 = #topic Letsencrypt - relrod (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

Meeting Agenda Item: Introduction Diogo Nunes
by Diogo Nunes 19 Jun '18

19 Jun '18

IRC: dnunes My Skills: -- Software Development: - Python -- Infrastructure: - +7 years of Enterprise Linux usage and administration; - OpenVPN, DHCP, Apache, Satellite, pulp, and some other services - RHCSA/RHCE ( RHEL 6/7 ), Satellite 6 and RHEV 3 Certified: 140-176- 900 What I want to Learn: -- I want to improve mainly my python and everything that I can with Linux; Initial Questions: -- How to get started ? -- Can someone coach me ? Ty for the opportunity. -- Diogo Nunes [ED90 5C78 7E7D CD62 C46D 6108 3EA4 A072 DF2B 8CC3]

2 1

[Fedocal] Reminder meeting : Infra Office Hours
by cverna＠fedoraproject.org 18 Jun '18

18 Jun '18

Dear all, You are kindly invited to the meeting: Infra Office Hours on 2018-06-19 from 18:00:00 to 19:00:00 UTC At fedora-admin(a)irc.freenode.net The meeting will be about: Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features. Source: https://apps.fedoraproject.org/calendar/meeting/9255/

1 0

patch review: storage check for retrace.f.o
by Miroslav Suchý 15 Jun '18

15 Jun '18

I want to set up monitoring of free space on /srv of retrace.fedoraproject.org. It is huge volume therefore normal check_disk_/srv does not have sense. I created new check, but it is my first time working with nrpe. I would welcome if someone can review it, before I push it. Patch is in the attachment. Miroslav

2 1

Website deployment on Fedora openshift cluster
by Michael Scherer 15 Jun '18

15 Jun '18

Hi, I have been tasked with helping to deploy coreos.fedoraproject.org, and so I have a patch to review, Clement told me to send it here for merge/review. 1 patch is for the DNS repo, the other for ansible. I can't test any of them right now, so maybe I overlooked something (and as said on irc, the deadline is a bit tight, but I will take care of any errors arising) -- Michael Scherer

1 0

Proposed Agenda for 2018-06-14 Infrastructure Meeting 14:00 UTC
by Stephen John Smoogen 13 Jun '18

13 Jun '18

= Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2018-06-14 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-06-14) #meetingname infrastructure #topic aloha #chair nirik pingou puiterwijk relrod smooge tflink threebean = 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 # this is ongoing. #info smooge PTO 15 Jun -> 18 Jun #info Office hours = 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 Nirik is on call from 2018-06-07->2018-06-19 #info Relrod is on call from 2018-06-20->2018-06-26 #info Smooge is on call from 2018-06-27->2018-07-05 #info ?? is on call from 2018-07-06->2018-07-12 #topic Flock - nirik #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 = Meeting end stuff = #topic Open Floor -- Stephen J Smoogen.

1 0

Patch review request: zchunk patches for dnf, libsolv and librepo
by Jonathan Dieter 13 Jun '18

13 Jun '18

I've finally finished writing patches to integrate zchunk support into dnf/libsolv/librepo[1], and I'd greatly appreciate some code review. A vast majority of the code is in librepo, but libsolv has been expanded to support zchunk files and dnf has a tiny patch that passes the base cache directory to librepo to find source zchunk files to delta against. With these patches and a zchunk-enabled repository, you will download only the differences in your primary/filelists/other metadata. Partial downloads are validated and then continued, and each chunk is validated as it's downloaded, ending the download and moving to a new mirror if any chunk is corrupt. I would love to get these changes into Fedora 29, and the code is testable now, but with only three weeks until System-Wide change proposals are due, I'm not sure if I'm being ambitious. On another note, I would also like to finalize zchunk's API and make a stable ABI promise, but before I take that step I'd really love some feedback on its usability. Jonathan [1] https://github.com/rpm-software-management/dnf/pull/1107 https://github.com/openSUSE/libsolv/pull/270 https://github.com/rpm-software-management/librepo/pull/127

2 4

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

[release] fedmsg_meta_fedora_infrastructure: 0.26.0
by Pierre-Yves Chibon 11 Jun '18

11 Jun '18

Good Morning Everyone, I just cut a new release of fedmsg-meta-fedora-infrastructure: 0.26.0 Here is its changelog: 0.26.0 ------ Pull Requests - (@pypingou) #487 Add support for fedmsg message from pagure about PR assignee https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/487 - (@sinnykumari) #488 Update releng.atomic.twoweek fedmsg doc with multi-arch content https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/488 It is already available from pypi and I will be updating the RPMs in Fedora shortly. Happy messaging, Pierre

2 1

Meeting Agenda Item: Introduction janslow
by James Anslow 07 Jun '18

07 Jun '18

Hi all My IRC nick is janslow. I've volunteered in the infrastructure team in the past as an apprentice, but had to drop out for personal reasons. I'm hoping that I can start to contribute again and on a more regular basis. My purpose for wanting to volunteer is to keep my infrastructure knowledge relevant, and to expand it to new technologies and applications. I previously worked full time as a software developer and later DevOps engineer, mainly programming in PHP and generic web development languages and frameworks, with mostly Jenkins and Bamboo for CI. On the infra side I have worked maintaining CentOS and Debian boxes in both traditional bare-metal and IaaS/"Cloud" environments, both for smaller projects and at scale for larger blue chip corporates. Hope to see you at today's meeting. J

1 0

QA/Development downtime 2018-06-07 2300 UTC - 2018-06-08 0300 UTC
by Stephen John Smoogen 06 Jun '18

06 Jun '18

Outage: db-qa server - 2018-06-07 23:00 UTC There will be an outage starting at 2018-06-07 23:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2018-06-07 23:00 UTC' Reason for outage: Currently the database server on the fedora qa network has only 2 CPUs and limited ram. This is causing problems with waiverdb/resultsdb and other tools needing to get builds in place. The databaseserver will be moved to a different virtual server and given 8 additional cpus and more ram. Affected Services: Bodhi - Waiverdb Greenwave Resultsdb Taskotron OpenQA QA Services Unaffected Services: Fedorapeople Mailing lists Koji buildsystem Ticket Link: Contact Information: Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen.

1 0

[PATCH] bodhi-pungi: enable atomic artifacts during updates runs
by Dusty Mabe 05 Jun '18

05 Jun '18

Now that we have updates-testing passing. Let's enable it for the updates runs as well. --- roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index 8a489ae44..631e07af7 100644 --- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 +++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 @@ -181,7 +181,7 @@ ostree = { } [% endif %] -[% if release.id_prefix == 'FEDORA' and release.version_int >= 28 and request.name == 'testing' %] +[% if release.id_prefix == 'FEDORA' and release.version_int >= 28 %] global_ksurl = 'git+https://pagure.io/fedora-kickstarts.git?#origin/f[[ release.version_int ]]' global_release = '!RELEASE_FROM_LABEL_DATE_TYPE_RESPIN' image_name_format = '%(release_short)s-%(variant)s-%(disc_type)s-%(arch)s-%(version)s-%(date)s%(type_suffix)s.%(respin)s.iso' -- 2.14.3

2 2

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

Re: infrastructure Digest, Vol 144, Issue 5
by Aditya Mukherjee 05 Jun '18

05 Jun '18

Please remove me from this list. Thanks. On 5 Jun 2018 5:10 am, <infrastructure-request(a)lists.fedoraproject.org> wrote: > Send infrastructure mailing list submissions to > infrastructure(a)lists.fedoraproject.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > infrastructure-request(a)lists.fedoraproject.org > > You can reach the person managing the list at > infrastructure-owner(a)lists.fedoraproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of infrastructure digest..." > > Today's Topics: > > 1. Re: Migrating fedmsg to AMQP: a proposal (Jeremy Cline) > 2. Meeting Agenda Item: Introduction Innocent Asiimwe > (Innocent Asiimwe) > 3. Re: Migrating fedmsg to AMQP: a proposal (Ken Dreyer) > > > ---------------------------------------------------------------------- > > Date: Mon, 4 Jun 2018 14:30:59 +0000 > From: Jeremy Cline <jeremy(a)jcline.org> > Subject: Re: Migrating fedmsg to AMQP: a proposal > To: Fedora Infrastructure <infrastructure(a)lists.fedoraproject.org>, > Michael Bonnet <mikeb(a)redhat.com> > Message-ID: <01000163cb3553f7-dc122a05-66bb-45c7-8363-23ebe8590585-000 > 000(a)email.amazonses.com> > Content-Type: multipart/signed; micalg=pgp-sha256; > protocol="application/pgp-signature"; > boundary="jHoSkhHphgVOG8vWarTggGMP9aTb87Ggr" > > This is an OpenPGP/MIME signed message (RFC 4880 and 3156) > --jHoSkhHphgVOG8vWarTggGMP9aTb87Ggr > Content-Type: multipart/mixed; boundary="vipAwbxR7XhIe2JI5JsHFy2yg6HjAy > ukS"; > protected-headers="v1" > From: Jeremy Cline <jeremy(a)jcline.org> > To: Fedora Infrastructure <infrastructure(a)lists.fedoraproject.org>, > Michael Bonnet <mikeb(a)redhat.com> > Message-ID: <2757f424-a91c-b7f4-bb85-9720306d69c5(a)jcline.org> > Subject: Re: Migrating fedmsg to AMQP: a proposal > References: <CAHmoxtXHdgHwbGrRqFanJC5iLacDezO1SwEf_b=_0zFBt3mqOQ@mail. > gmail.com> > <CAD-DQxS8gm8jofrXX8oMGrqFZKQ44_KEkCwWTbh6Pwo3p0oONw(a)mail.gmail.com> > <01000163ad746b7e-5fb1fc93-2117-4b1e-bd8b-d8f1d602b8fc- > 000000(a)email.amazonses.com> > <CACZP5mtW3c1Ot+2vkdPwunPs0Ve9dj2EVxpr5=c3se9KuzPEhg(a)mail.gmail.com> > In-Reply-To: <CACZP5mtW3c1Ot+2vkdPwunPs0Ve9dj2EVxpr5=c3se9K > uzPEhg(a)mail.gmail.com> > > --vipAwbxR7XhIe2JI5JsHFy2yg6HjAyukS > Content-Type: text/plain; charset=utf-8 > Content-Language: en-US > Content-Transfer-Encoding: quoted-printable > > On 06/01/2018 05:45 PM, Michael Bonnet wrote: > > On Tue, May 29, 2018 at 12:51 PM, Jeremy Cline <jeremy(a)jcline.org> wrot= > e: > >=20 > >> Hi, > >> > >> On 05/29/2018 09:31 AM, Jeffrey Ollie wrote: > >>> On Thu, May 24, 2018 at 11:16 AM, Aurelien Bompard < > >>> abompard(a)fedoraproject.org> wrote: > >>> > >>>> > >>>> What do you think of this proposal? Any blind spots? > >>>> > >>> > >>> Not that I disagree, but please add/expand a section as to why AMQP (= > and > >>> RabbitMQ) was chosen over other messaging technologies. > >> > >> Thanks for the feedback, I've added a small section[0]. It is, perhaps= > , > >> a little wishy-washy. I don't want to give the impression that we > >> couldn't implement this with a different messaging protocol or a > >> different broker. We definitely could. AMQP has short-comings, to be > >> sure, but the RabbitMQ extensions (mainly pulisher acks) cover the mos= > t > >> important ones in my opinion. > >> > >> I did some research, but I'd definitely welcome feedback on protocols > >> and brokers. I've read all or nearly all of the AMQP 0.9, ZeroMQ, and > >> STOMP protocols, and I skimmed through the MQTT protocol, but I've not= > > >> looked closely at the AMQP 1.0 protocol and I'm by no means a message > >> protocol expert. > >> > >=20 > > I think moving to a broker-based architecture is a great idea! Your > > document does a great job explaining the advantages it brings, and it c= > ould > > help increase the adoption of event-based workflows. > >=20 > > Regarding protocols, my preference would be for STOMP. It's has very wi= > de > > support, with libraries in pretty much every language, and being entire= > ly > > text-based makes it *much* easier to debug than other protocols. The > > message delivery semantics are well-defined, and the protocol spec has = > the > > nice property of being readable in one sitting. Some brokers provide th= > e > > ability to translate between protocols, so it may not be difficult to > > support more than one, but I would suggest STOMP as the reference proto= > col. > > I had a hard time justifying choosing STOMP over AMQP because most > brokers just map the other protocol they focus on onto STOMP. It's true > the the spec is short, but it leaves a lot up to individual > implementations as far as I can tell (like how topic matching works, for > example). > > While debuggability is important, I'm not certain we'll ever need to dig > into the wire protocol. In the unlikely event that we need to, I'd go > about it the same way (e.g. tcpdump/wireshark) and Wireshark knows how > to parse the AMQP protocol. Based on my super simple test (capture a > single message being published) it seems very easy to inspect. Have you > had a different experience here? > > > --=20 > Jeremy Cline > XMPP: jeremy(a)jcline.org > IRC: jcline > > > --vipAwbxR7XhIe2JI5JsHFy2yg6HjAyukS-- > > --jHoSkhHphgVOG8vWarTggGMP9aTb87Ggr > Content-Type: application/pgp-signature; name="signature.asc" > Content-Description: OpenPGP digital signature > Content-Disposition: attachment; filename="signature.asc" > > -----BEGIN PGP SIGNATURE----- > > iQIzBAEBCAAdFiEEfjR9J//2iFvH1Gi7kiMwj6myRtsFAlsVTR0ACgkQkiMwj6my > Rtv/eQ//fU41kjzEXd7AVVO263VxBVGkk5cR85bKXk7mqF7wGevDh2URoiHfBaMd > Qs638uc4Iskxrpzk+JsPjeH4Y1jI69zIzHTK/CnsFPBdnRuIwlG+PFB+jjxerf8a > g0cyyKkitKbBIbKDpXvFumVQNeSFVlr4RdICyDgshXzayxifKOJN5OtoqgwiaAj8 > 2SoqnySMaMGzhji84dlUXknmEZm7Ilz9jBsJzA7uhNowQLQxov6AZCdvp4JlWV1n > Y12NjABFsk0rrzw3A4XjGDGQqCRNUtkscXlBVd3dqU9+TccSpUU0Bxzz6Kjnd9xj > UEsRcjwygXrDa0ZXz6XYeqlYiQi0xczC98gr1LOngB/VY8yBGhCVEhQ8dGdH+BJS > BvlbUzDUt2MfieXtHOp8PwEPjEaI3Ornq1/FGzouh+4uBaeSZgyvFbtNAsNv//Vh > jBQARSFICg0kLvuQUp1adXYtnAr56XXJzsmSeCJAV9I0l2yuMuXMszDzHzUHNRDU > GKY5Tks8AxogEVJugX7SbpMgsWd58+astSF8nl5aqi49gdprAY7/ivghQ/tHS4A1 > gk7nhq8rfzhoA1uVauh2EZa+TAYN9tySyqJKWsKYD6NkMZC7AiSXgBPSR4GvPDlU > Gmaitp1AgpoaOZf/6bMcWlEZvN5tB7aXpRnSu7YPSo7AriR6mY4= > =Pwwm > -----END PGP SIGNATURE----- > > --jHoSkhHphgVOG8vWarTggGMP9aTb87Ggr-- > > ------------------------------ > > Date: Mon, 4 Jun 2018 22:02:47 +0300 > From: Innocent Asiimwe <innocent.asiimwe(a)andela.com> > Subject: Meeting Agenda Item: Introduction Innocent Asiimwe > To: infrastructure(a)lists.fedoraproject.org > Message-ID: > <CAD8GFgYVnoeFFp6davtpav3L1Y-=-aCgt04D=-_6=qM+7oKMOQ@mail. > gmail.com> > Content-Type: multipart/alternative; > boundary="0000000000005924f1056dd59470" > > --0000000000005924f1056dd59470 > Content-Type: text/plain; charset="UTF-8" > > Dear all, > > IRC handle: asiimwe > > skills I possess: > > - python programming > - bash scripting > - Using ansible > - Using packer > - Using terraform > - Using jenkins, travis and circleci for CI/CD > - linux and windows server system administration > > skills I want to learn > > - go programming language > - new devops and system administration workflows > - Building tools used in devops > - maintaining large infrastructures > - Effectively contributing to open source > > I am currently working at andela(andela.com) as a software developer and > devops engineer. (entry level) > > I would like to work on maintaining the Fedora infrastructure and building > tools used in the same. > > regards, > Innocent > > --0000000000005924f1056dd59470 > Content-Type: text/html; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > <div dir=3D"ltr"><span style=3D"color:rgb(34,34,34); > font-family:arial,sans-= > serif;font-size:12.8px;font-style:normal;font-variant- > ligatures:normal;font= > -variant-caps:normal;font-weight:400;letter-spacing: > normal;text-align:start= > ;text-indent:0px;text-transform:none;white-space: > normal;word-spacing:0px;ba= > ckground-color:rgb(255,255,255);text-decoration-style: > initial;text-decorati= > on-color:initial;float:none;display:inline">Dear all,</span><div > style=3D"c= > olor:rgb(34,34,34);font-family:arial,sans-serif;font- > size:12.8px;font-style= > :normal;font-variant-ligatures:normal;font-variant- > caps:normal;font-weight:= > 400;letter-spacing:normal;text-align:start;text-indent: > 0px;text-transform:n= > one;white-space:normal;word-spacing:0px;background-color: > rgb(255,255,255);t= > ext-decoration-style:initial;text-decoration-color:initial"><br></div><div > = > style=3D"color:rgb(34,34,34);font-family:arial,sans-serif; > font-size:12.8px;= > font-style:normal;font-variant-ligatures:normal;font- > variant-caps:normal;fo= > nt-weight:400;letter-spacing:normal;text-align:start;text- > indent:0px;text-t= > ransform:none;white-space:normal;word-spacing:0px; > background-color:rgb(255,= > 255,255);text-decoration-style:initial;text-decoration-color:initial">IRC > h= > andle: asiimwe</div><div style=3D"color:rgb(34,34,34); > font-family:arial,san= > s-serif;font-size:12.8px;font-style:normal;font-variant- > ligatures:normal;fo= > nt-variant-caps:normal;font-weight:400;letter-spacing: > normal;text-align:sta= > rt;text-indent:0px;text-transform:none;white-space: > normal;word-spacing:0px;= > background-color:rgb(255,255,255);text-decoration-style: > initial;text-decora= > tion-color:initial"><br></div><div style=3D"color:rgb(34,34,34); > font-family= > :arial,sans-serif;font-size:12.8px;font-style:normal;font- > variant-ligatures= > :normal;font-variant-caps:normal;font-weight:400;letter- > spacing:normal;text= > -align:start;text-indent:0px;text-transform:none;white- > space:normal;word-sp= > acing:0px;background-color:rgb(255,255,255);text- > decoration-style:initial;t= > ext-decoration-color:initial">skills I possess:</div><div > style=3D"color:rg= > b(34,34,34);font-family:arial,sans-serif;font-size:12.8px; > font-style:normal= > ;font-variant-ligatures:normal;font-variant-caps: > normal;font-weight:400;let= > ter-spacing:normal;text-align:start;text-indent:0px;text- > transform:none;whi= > te-space:normal;word-spacing:0px;background-color:rgb(255, > 255,255);text-dec= > oration-style:initial;text-decoration-color:initial"><ul><li > style=3D"margi= > n-left:15px">python programming</li><li style=3D"margin-left:15px">bash > scr= > ipting</li><li style=3D"margin-left:15px">Using ansible</li><li > style=3D"ma= > rgin-left:15px">Using packer</li><li style=3D"margin-left:15px">Using > terra= > form</li><li style=3D"margin-left:15px">Using jenkins, travis and > circleci = > for CI/CD</li><li style=3D"margin-left:15px">linux and windows server > syste= > m administration</li></ul><div>skills I want to learn</div></div><div > style= > =3D"color:rgb(34,34,34);font-family:arial,sans-serif;font- > size:12.8px;font-= > style:normal;font-variant-ligatures:normal;font-variant- > caps:normal;font-we= > ight:400;letter-spacing:normal;text-align:start;text- > indent:0px;text-transf= > orm:none;white-space:normal;word-spacing:0px;background- > color:rgb(255,255,2= > 55);text-decoration-style:initial;text-decoration-color:initial"><ul><li > st= > yle=3D"margin-left:15px">go programming language</li><li > style=3D"margin-le= > ft:15px">new devops=C2=A0and system administration workflows</li><li style= > =3D"margin-left:15px">Building tools used in devops</li><li > style=3D"margin= > -left:15px">maintaining large infrastructures=C2=A0</li><li > style=3D"margin= > -left:15px">Effectively contributing to open source</li></ul><div>I am > curr= > ently working at andela(<a href=3D"http://andela.com/" target=3D"_blank" > st= > yle=3D"color:rgb(17,85,204)">andela.com</a>) as a software developer and > de= > vops=C2=A0engineer. (entry level)</div></div><div > style=3D"color:rgb(34,34,= > 34);font-family:arial,sans-serif;font-size:12.8px;font- > style:normal;font-va= > riant-ligatures:normal;font-variant-caps:normal;font- > weight:400;letter-spac= > ing:normal;text-align:start;text-indent:0px;text- > transform:none;white-space= > :normal;word-spacing:0px;background-color:rgb(255,255, > 255);text-decoration-= > style:initial;text-decoration-color:initial"><br></div><div > style=3D"color:= > rgb(34,34,34);font-family:arial,sans-serif;font-size:12. > 8px;font-style:norm= > al;font-variant-ligatures:normal;font-variant-caps: > normal;font-weight:400;l= > etter-spacing:normal;text-align:start;text-indent:0px; > text-transform:none;w= > hite-space:normal;word-spacing:0px;background-color: > rgb(255,255,255);text-d= > ecoration-style:initial;text-decoration-color:initial">I would like to > work= > on maintaining the Fedora infrastructure and building tools used in the > sa= > me.</div><div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif; > fon= > t-size:12.8px;font-style:normal;font-variant-ligatures: > normal;font-variant-= > caps:normal;font-weight:400;letter-spacing:normal;text- > align:start;text-ind= > ent:0px;text-transform:none;white-space:normal;word- > spacing:0px;background-= > color:rgb(255,255,255);text-decoration-style:initial;text- > decoration-color:= > initial"><br></div><div style=3D"color:rgb(34,34,34); > font-family:arial,sans= > -serif;font-size:12.8px;font-style:normal;font-variant- > ligatures:normal;fon= > t-variant-caps:normal;font-weight:400;letter-spacing: > normal;text-align:star= > t;text-indent:0px;text-transform:none;white-space: > normal;word-spacing:0px;b= > ackground-color:rgb(255,255,255);text-decoration-style: > initial;text-decorat= > ion-color:initial">regards,</div><div style=3D"color:rgb(34,34,34); > font-fam= > ily:arial,sans-serif;font-size:12.8px;font-style:normal; > font-variant-ligatu= > res:normal;font-variant-caps:normal;font-weight:400;letter- > spacing:normal;t= > ext-align:start;text-indent:0px;text-transform:none;white- > space:normal;word= > -spacing:0px;background-color:rgb(255,255,255);text- > decoration-style:initia= > l;text-decoration-color:initial">Innocent</div><br></div> > > --0000000000005924f1056dd59470-- > > ------------------------------ > > Date: Mon, 4 Jun 2018 16:59:25 -0600 > From: Ken Dreyer <ktdreyer(a)ktdreyer.com> > Subject: Re: Migrating fedmsg to AMQP: a proposal > To: Fedora Infrastructure <infrastructure(a)lists.fedoraproject.org> > Cc: Michael Bonnet <mikeb(a)redhat.com> > Message-ID: > <CAD3FbMX=A+FO_Cc6wqXqjWr9DhjNdu_7mcUvPai=tUK > tVmxBTQ(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > On Mon, Jun 4, 2018 at 8:30 AM, Jeremy Cline <jeremy(a)jcline.org> wrote: > > I had a hard time justifying choosing STOMP over AMQP because most > > brokers just map the other protocol they focus on onto STOMP. It's true > > the the spec is short, but it leaves a lot up to individual > > implementations as far as I can tell (like how topic matching works, for > > example). > > It's nice to give the flexibility to clients by exposing both. I > haven't seen a problem with topic matching in my experience so far. > > One thing I found with AMQP vs STOMP is that it's possible for AMQP > clients to (accidentally) emit "binary" message bodies, and then > ActiveMQ does not translate or expose these as plaintext JSON for > STOMP clients. It just looks like an empty message body to STOMP > clients, or possibly garbage. The solution was for clients to > translate the messages to text/json prior to sending. (Of course if > you never enable STOMP on your broker at all, maybe this won't be a > problem :) > > - Ken > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org > To unsubscribe send an email to infrastructure-leave@lists. > fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: ${hyperkitty_url} > > > ------------------------------ > > End of infrastructure Digest, Vol 144, Issue 5 > ********************************************** >

2 1

Meeting Agenda Item: Introduction Innocent Asiimwe
by Innocent Asiimwe 04 Jun '18

04 Jun '18

Dear all, IRC handle: asiimwe skills I possess: - python programming - bash scripting - Using ansible - Using packer - Using terraform - Using jenkins, travis and circleci for CI/CD - linux and windows server system administration skills I want to learn - go programming language - new devops and system administration workflows - Building tools used in devops - maintaining large infrastructures - Effectively contributing to open source I am currently working at andela(andela.com) as a software developer and devops engineer. (entry level) I would like to work on maintaining the Fedora infrastructure and building tools used in the same. regards, Innocent

1 0

Updates for AtomicHost artifacts in bodhi pungi runs
by Dusty Mabe 03 Jun '18

03 Jun '18

[PATCH 1/5] bodhi-pungi: f29 will be new branched target [PATCH 2/5] bodhi-pungi: convert image-build to use non branched [PATCH 3/5] bodhi-pungi: only provide one repo to lorax [PATCH 4/5] bodhi-pungi: s/Atomic/AtomicHost/ [PATCH 5/5] bodhi-pungi: add vagrant box creation The commit messages should give a good idea of what is related to each one. The biggest thing is working around a lorax/dnf bug for now in patch 3.

4 10

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

Old deltarpms are being thrown away on each compose (was Re: dnf and deltarpm)
by Jonathan Dieter 01 Jun '18

01 Jun '18

On Thu, 2018-05-31 at 22:34 +0100, Tomasz Kłoczko wrote: > Just checked on few mirrors usual location of f28 updates > (/pub/linux/dist/fedora/linux/updates/28/Everything/x86_64/drpms) and > in this directory there are at the moment only 56 files from May 31 > and nothing older. So not two drpm per RPM package but only generated > files out of last batch of updates. (CC'ing the Fedora infrastructure list) This is a bug. It looks like we're throwing away any drpms not generated in this compose, when we should be keeping them. I've just created: https://pagure.io/fedora-infrastructure/issue/7008 Jonathan

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure June 2018