infrastructure July 2021

infrastructure@lists.fedoraproject.org

24 participants
31 discussions

VDO
by Miroslav Suchý 04 Jul '26

04 Jul '26

After I seen the talk about VDO: https://www.youtube.com/watch?v=7CGr5LEAfRY I went ahead and tried it. I tried it on small (12GB) sample of Copr data and I saved 20-30% data. I then deployed it on production server retrace.fedoraproject.org and saved there 15% out of 2TB. Several notes: The RPM packages are only available for RHEL. Recently the public github has been updated with version of VDO, which should work on Fedora. No RPM available for Fedora yet though. Here are my notes: # vdo create --name=vdo1 --device=/dev/vdb --vdoLogicalSize=1T # mkfs.ext4 /dev/mapper/vdo1 Some slides suggest to use -E discard. This is not needed for new volumes. See vdo-devel mailing list for reasoning. # mount -o discard /dev/mapper/vdo1 /mnt/a Probably best scenario is to create vdo on whole disk and then make PV from whole VDO disk and put LVM on top of that. When you already have data, you cannot convert your disk to VDO. You need create new VDO disk, format it, mount it and copy the data. In my case, due limited space for migration I created a small LVM volume "vdosrv": # lvcreate -L 80G -n vdosrv vol0 I converted it to VDO which claims to have 2TB of vitual total size # vdo create --name=srv18 --device=/dev/vol0/vdosrv --vdoLogicalSize=2T # mkfs.ext4 /dev/mapper/srv18 See how many space is *actually* free. # vdostats # mkdir /mnt/srv18 # mount -o discard /dev/mapper/srv18 /mnt/srv18 Now I moved some data from old volume to /mnt/srv18. I shrank the FS of old volume, I shrank the old LV. And then I enlarged the new LV. # lvresize -L +400G /dev/vol0/vdosrv and let know vdo that it can use the new space: # vdo growPhysical -n srv18 I repeated this several times. I have to say that my experience is so far good. I hope that my notes help someone. Miroslav

10 14

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

Infrastructure and release engineering Documentation
by Mark O'Brien 10 Nov '21

10 Nov '21

Hi All, As some of you may be aware there has been chatter around having the documentation for infrastructure and release engineering centralised in one place. A possible solution to this is to move all of these under a new section on docs.fedoraproject.org called something like Infrastructure and Release Engineering (very original I know). We could then go about moving docs which are suitable from currrent locations to the new central point. Each doc should be updated before moving and the old document should be updated to only contain a link to the new doc to avoid a case of multiple versions of a doc (https://xkcd.com/927/ ). The following links contain the bulk of the documentation: https://fedora-infra-docs.readthedocs.io/en/latest/ https://docs.pagure.org/releng/ https://fedoraproject.org/wiki/Infrastructure These would be the suggested first steps with other docs to follow if/when these are completed. As I say this is just a possible solution so as always all feedback and suggestions are encouraged and welcomed. Thanks, Mark

4 8

Update hyperkitty to latest?
by Reon Beon 13 Oct '21

13 Oct '21

https://release-monitoring.org/project/53453/

2 2

Noggin 1.3.0 deployed to production
by Aurelien Bompard 28 Jul '21

28 Jul '21

Hey folks! I forgot to announce it here, but I deployed Noggin 1.3.0 to prod last week. Here are the highlights. Features - Add a page to manage registering users (PR#672 <https://github.com/fedora-infra/noggin/pull/672>). - Allow template override with a custom directory, see the TEMPLATES_CUSTOM_DIRECTORIES configuration value (PR#701 <https://github.com/fedora-infra/noggin/pull/701>). - Allow users to declare their Matrix IDs in addition to the IRC nicknames (#248 <https://github.com/fedora-infra/noggin/issues/248>). - Display on users’ profiles the agreements they have signed (#576 <https://github.com/fedora-infra/noggin/issues/576>). - Validate email addresses when changed in the mail or rhbz_mail attributes (#610 <https://github.com/fedora-infra/noggin/issues/610>). - Allow users to select multiple pronouns (#646 <https://github.com/fedora-infra/noggin/issues/646>). Bug Fixes - Don’t tell users signing up that their username is already taken when it can be the email address (PR#665 <https://github.com/fedora-infra/noggin/pull/665>). - Add the for attribute to checkbox labels (#658 <https://github.com/fedora-infra/noggin/issues/658>). Development Improvements - Start using pre-commit <https://pre-commit.com/> to run the simple checkers (linters, formatters, security checks). Run poetry install to install the new dependencies, and then run pre-commit install to setup the git hook. Also add the safety <https://pyup.io/safety/> tool (PR#659 <https://github.com/fedora-infra/noggin/pull/659>). As always, please report the issues you may encounter. Cheers! Aurélien

1 0

Ticket notifications in IRC
by Aurelien Bompard 27 Jul '21

27 Jul '21

Hey folks! We currently have messages posted on the #fedora-apps and #fedora-infrastructure IRC channels when there's a ticket change or a pull-request change. I don't know about the infrastructure channel, but it makes it difficult to have a development conversation in #fedora-apps, the signal/noise ratio is just too low. Are you all happy with this setup? I would like to propose we move those notifications to a different channel, such as #fedora-apps-activity (and #fedora-infrastructure-activity). Otherwise I can go have my development discussions in another channel, it's fine too. What do you think? Aurélien

6 13

[Fedocal] Reminder meeting : Websites & Apps Team Meeting
by jflory7＠fedoraproject.org 26 Jul '21

26 Jul '21

Dear all, You are kindly invited to the meeting: Websites & Apps Team Meeting on 2021-07-27 from 15:00:00 to 16:00:00 UTC At https://meet.jit.si/fedora-websites-apps-meeting The meeting will be about: Weekly team meeting for the Websites & Apps Team. This is part of the [Websites & Apps Community Revamp Objective](https://fedoraproject.org/wiki/Objectives/Websites_%26_Apps_Comm…. See [past discussion]( https://discussion.fedoraproject.org/t/planning-meeting-for-websites-apps-t…) to learn more about the Websites & Apps Team and how it came together. More information available at: [hackmd.io/Mxm2We3yTqKybLsdohadOA](https://hackmd.io/Mxm2We3yTqKybLsdohadOA?view) Source: https://calendar.fedoraproject.org//meeting/9990/

1 0

Questions about the Fedora Release Life Cycle
by Beatriz Michelson Reichert 22 Jul '21

22 Jul '21

Hi, I'm Beatriz and I'm a student at the Santa Catarina State University. Currently, I'm studying the Fedora Release Life Cycle, and would like to know if anyone could help me with some questions about this subject: 1. I understand that the services used to build composes (e.g., Koji, Bodhi, Pungi) use TLS. But it was unclear whether these certificates are generated internally or whether they are generated by a public CA (e.g., letsencrypt). 2. Do clients use the trust anchors from the ca-certificates package or do they have a list of their own? -- Best regards, Beatriz Santa Catarina State University - UDESC

2 2

[Fedocal] Reminder meeting : Fedora Infrastructure
by Damian Tometzki 21 Jul '21

21 Jul '21

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2021-07-22 from 16:00:00 to 17:00:00 UTC At fedora-meeting-3(a)irc.freenode.net The meeting will be about: Weekly Fedora Infrastructure meeting. See infrastructure list for agenda. Source: https://apps.fedoraproject.org/calendar/meeting/9675/

1 0

DNS patch request to enable ocp staging worker01-03
by David Kirwan 21 Jul '21

21 Jul '21

https://gist.github.com/davidkirwan/ae4038fa101dea3e8e1318ce3330970b Hi infra, can I please get a review on the patch above, we are configuring the ocpstaging worker machines to boot via dhcp. cheers -- David Kirwan Software Engineer Community Platform Engineering @ Red Hat T: +(353) 86-8624108 IM: @dkirwan

3 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure July 2021