August 2017 - 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] Another oldschool badges cron mapping
by Justin W. Flory 13 Sep '17

13 Sep '17

Hey folks, I have another quick and simple patch attached for the ansible.git repo. This one adds a mapping for the DotNet SIG's FAS group to their new badge that was just pushed up. Let me know if anything else is needed. Thanks! -- Cheers, Justin W. Flory jflory7(a)gmail.com

3 3

proxy01 logs
by Stephen John Smoogen 07 Sep '17

07 Sep '17

Proxy01 paged on a disk space issue this evening. Half of the disk space usage was journal logs. I vacuumed them down to 30 days which gave us about 2GB free. The other disk usage is koji.fedoraproject.org and kojipackages.fedoraproject.org which are using 1.8GB of disk space in the last 24 hours. The lion share of this log is 10.5.125.62 - - [31/Aug/2017:04:02:16 +0000] "POST /kojihub HTTP/1.1" 200 4118 "-" "koji/1" (with the POST being the size of whatever koji02.phx2.fedoraproject.org. is pushing to koji.fedoraproject.org (which somehow sounds weird).) -- Stephen J Smoogen.

2 2

Delta RPMs for F26
by Ron Yorston 04 Sep '17

04 Sep '17

Hello, Over on the users mailing list we've been wondering why delta RPMs don't seem to be available for F26. Any ideas, infrastructure people? Ron

2 1

[release] fedmsg_meta_fedora_infrastructure: 0.21.0
by Pierre-Yves Chibon 24 Aug '17

24 Aug '17

Good Morning Everyone, I just cut a new release of fedmsg_meta_fedora_infrastructure: 0.21.0 ------ Pull Requests - (@ralphbean) #440 Test and handle output from "modular" compose messages. https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/440 - (@pypingou) #441 Add support for the CI messages: ci.pipeline.complete https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/441 It is already uploaded to pypi and the RPMs for F28, F27, F26, F25 and epel7 are building. Seeing the changelog, I will be pushing it to staging and production fairly quickly (also because I know that the CI pipeline folks are waiting on this for their work). Happy messaging, Pierre

1 0

Plans for Thursday 2017-08-24 Fedora Infrastructure Meeting
by Stephen John Smoogen 23 Aug '17

23 Aug '17

= 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 (2017-08-24) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 dgilmore threebean pingou puiterwijk pbrobinson = Let new people say hello = #topic New folks introductions = 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 PHX2 Colo Trip, Dec 4th - 9th #info FLOCK at Cape Cod Aug 29th - Sep 1st #info beta freeze coming up 2017-09-05 - everyone #info Moving .stg. ips ongoing = 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 = Apprentice office hours = #topic Apprentice Open office hours 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.) #topic Learn about: Nothing was put here this week = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

Bodhi 2.10.1 in production
by Jeremy Cline 23 Aug '17

23 Aug '17

Hey folks, Bodhi 2.10.1 is now running in production. The change log: https://bodhi.fedoraproject.org/docs/release_notes.html At this time, the Greenwave integration is configured to be off. When Greenwave is ready, we'll be able to flip on the integration. -- Jeremy Cline XMPP: jeremy(a)jcline.org IRC: jcline

4 7

[release] fedmsg-1.0.0
by Jeremy Cline 22 Aug '17

22 Aug '17

Hey folks, I've tagged fedmsg-1.0.0[0] and it's available on PyPI[1]. The headlines for this release are re-organized documentation[2] and Python 3 support. Since this is the first release with Python 3 support and the test coverage is approximately 60 percent, it's likely there are still issues. Please report any issues you encounter :) [0] https://github.com/fedora-infra/fedmsg/releases/tag/1.0.0 [1] https://pypi.python.org/pypi/fedmsg/1.0.0 [2] https://fedmsg.readthedocs.io/en/stable/ -- Jeremy Cline XMPP: jeremy(a)jcline.org IRC: jcline

1 0

[release] pagure-dist-git: 0.6
by Pierre-Yves Chibon 21 Aug '17

21 Aug '17

Good Morning Everyone, I just cut a new release of pagure-dist-git with the following changelog: * Mon Aug 21 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.6-1 - Update to 0.6 - Added a new version of the package sources logo (Ryan Lerch) - Add a log statement when querying PDC (Ralph Bean) - Simplify the gitolite rules for forks and add tests for them - Make the project flake8 valid - Slightly change text to make it less confusing, per mattdm +1 (Paul W. Frields) - Add support for the provenpackager group in pagure-dist-git - Adjust the logic to group the users and groups in a single line - Some package do not allow provenpackager access - Simplify the index_auth template so it renders faster I have tested it in stg and it behaves as expected so prod is now also running it. Happy packaging, Pierre

1 0

pungi->bodhi - where should pungi configs be stored?
by Dusty Mabe 17 Aug '17

17 Aug '17

I just created an issue in the releng pagure about $SUBJECT. Please read and weigh in on that topic. https://pagure.io/releng/issue/6971 Dusty

1 0

[PATCH] Stop nightly testing dnf composes
by lubomir.sedlar＠gmail.com 17 Aug '17

17 Aug '17

From: Lubomír Sedlář <lsedlar(a)redhat.com> When Pungi gained the ability to use DNF instead of Yym, a compose was set up to run depsolving and generate diffs against the real rawhide compose. Since regular rawhide is now using DNF, so there's nothing to compare anymore and we can get rid of this. Signed-off-by: Lubomír Sedlář <lsedlar(a)redhat.com> --- roles/releng/files/rawhide | 1 - 1 file changed, 1 deletion(-) diff --git a/roles/releng/files/rawhide b/roles/releng/files/rawhide index 78c56fd..e715fbd 100644 --- a/roles/releng/files/rawhide +++ b/roles/releng/files/rawhide @@ -1,5 +1,4 @@ # rawhide compose MAILTO=releng-cron(a)lists.fedoraproject.org 15 5 * * * root TMPDIR=`mktemp -d /tmp/rawhide.XXXXXX` && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && LANG=en_US.UTF-8 ./nightly.sh && sudo -u ftpsync /usr/local/bin/update-fullfiletimelist -l /pub/fedora-secondary/update-fullfiletimelist.lock -t /pub fedora fedora-secondary -15 17 * * * root TMPDIR=$(mktemp -d /tmp/rawhide-dnf.XXXXXX) && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && LANG=en_US.UTF-8 ./nightly-dnf.sh 15 18 * * * root TMPDIR=$(mktemp -d /tmp/rawhide-modular.XXXXXX) && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && LANG=en_US.UTF-8 ./nightly-modular.sh -- 2.9.5

1 0

SSH known_hosts changed
by Patrick Uiterwijk 16 Aug '17

16 Aug '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all, As of right now, the ssh known_hosts file has been basically rewritten to use SSH CA certificates. The actual SSH keys for our servers should not have changed, but the known_hosts file has been shortened signifcantly. Do note that for some servers (specifically cloud), might have now switched from their ECDSA to RSA keys, which means that if you only had the host-specific known_hosts line, you might need to add the CA. You should be able to replace your entire ~/.ssh/known_hosts for Fedora with https://admin.fedoraproject.org/ssh_known_hosts . Please let me know if you find any hosts that don't work yet, as they should just need the hostname or domain in the list. Patrick -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJZlKCOAAoJEIZXmA2atR5Qw8MQAKqTrC1s8sMD6ujKPMIKNDrD aacmoyVIXq2gcvM/C4J/wp8yemIAXEv410xJ7+SP9fOcC49oThjqVca5pAq/Y9nS x4HWCDUNN4aQptwGOA2cwbjwopc44ClLV/oKW5NA1QEiSEfro5Op1/PM7n4iCMs4 3JWX9pSERVzuU52ewYzOubYYaaDpfOx49FW+LfmhZmFDj+NJIYet/USqmXFdDvLZ iVpWCVZ/k6DmVudofwTwa1iTgbxlx3NK6NaGHBV1D1saBg5qmUOx2g6KZlT78XH2 8SgioFZ9KYGahtDAP251BIejfHFR52/A7CBMZutN+JKriYaSRKbJZywQS5pzzz/q ay6qGs3qflSF7mGkpbpyzkFi96kFy2rHOhdnXb237kROCwSqAXRchpAYLPhf5uaZ BNPy0EPylbTBDsNff2uucCMa+BpErysKrA8R5TIt/7WdmzMBZlks0xwOhx5C9pJh Jaucy309j1GAXh0cNlMxqjuVAhrYoLbGygevFJTd++m5vrShqNfUvUV23oFwOcJd U1bjEax0GzJLz8egW0b5RyN/9TCfmEyPZ1IEsRpyKdfgeHn+i5OmyNNnIdgtarEd kzm6liilcEo+PIwGtjM5LuQLGoz8k0KlZl9wAEO9lEg8JdMqxK0ta9gjFs4QO5MK cE7/fpE6IpIfjS2kPtVV =yULk -----END PGP SIGNATURE-----

1 0

[release] fedmsg_meta_fedora_infrastructure: 0.20.0
by Pierre-Yves Chibon 16 Aug '17

16 Aug '17

Good Morning Everyone, I just cut a new release of fedmsg_meta_fedora_infrastructure: 0.20.0 ------ Pull Requests - (@mizdebsk) #426 Add processor for new Koschei message topic https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/426 - (@pypingou) #437 Add processor for the fedmsg messages published by ci.centos.org https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/437 Uploaded to pypi, will be updating the RPM shortly. Pierre

1 0

[release] fmn-1.4.0
by Jeremy Cline 16 Aug '17

16 Aug '17

Hey all, Yesterday afternoon I tagged a new FMN release and pushed it to stg[0]. The changelog for this release can be found on GitHub[1]. [0] https://apps.stg.fedoraproject.org/notifications/ [1] https://github.com/fedora-infra/fmn/releases/tag/1.4.0 -- Jeremy Cline XMPP: jeremy(a)jcline.org IRC: jcline

1 0

Infra tags changes
by Patrick Uiterwijk 15 Aug '17

15 Aug '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all, As of a bit ago, I have made a few small changes to the Infrastructure tags in koji. The basic change is that now, after you tagged it $dist-infra-candidate (or built for the "$dist-infra" target), it will still get signed, but NOT tagged into $dist-infra. Instead, the build will be tagged into $dist-infra-stg. This is an additional set of tags that gets put into a set of repositories enabled on staging, but not production, machines. This allows you to test the build thoroughly. After you have tested the build, you can promote it to production. For instructions on that, see the Promoting topic in [1], but in short it's really just a koji move. If you need any more information, just let me know. Regards, Patrick [1]: https://infrastructure.fedoraproject.org/infra/docs/docs/sysadmin-guide/sop… -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJZjdYTAAoJEIZXmA2atR5QnIcP/3OqZDGzq9cV+2xCzzOQH5fL toWCLUwFKolVpD1PCauN7jhGEWt2wLaQlnO7MCWCN7vv+f4pu4zS6vwNt8zNPEFI V3Zs10P45s/m4SAOoOOggGtNz7RoVTh9Mg1ZVTmqJixafT8GI/tJir3W2WxcS3mC MPHbRRi5GbFgC47Em0XTJPtf+cCY1BtqMuW8MwC5IKA+MVRHsZhsCbezpowcqMMi 1At/1UuHTkhoCjcb3+bEoIGJLSivoYeK2Z2TXld2o8J9oOGxY8EGJ4RDPTmMQQZK ZQ/W2EiEGGM8QCE67XVf5Ff8tE7/y0a1381y6d34wbgz5Hk4bvZ2WKXcjcefLy2w yo2+EqCHDaWVBf6g9SgvUBN8jmIOP/35s4LLfDkySzl8WQOpQgt3NE4jKpUQYLOW sxETK/E7E8qvtunsY+rEpoTj0ovzZnKNpmHI8Gx2IbxGeKRsjKYuA5AtGz/nb0Tv 0AbWJPl9Wn8ujA8kkpEssT5eQfiuiiot8c0W4QnwXE+3FU4Tf5mCYZEW05ulxoeU Jr0mG6SzywwdfD6LHZZa0lQsqriYCgv3rS4jlDOOLiMHY8ulfvk1wJxYnhufzL04 pGWA+DGQVy25K7boA2Bgr+q6bGEkkkg4b9bL1JGvPqSa4Bs4/03VwnBcBgYYTDwa L301mf7iJMuMqBxg+/8P =G2qN -----END PGP SIGNATURE-----

2 2

[Fedocal] Reminder meeting : Bodhi stakeholder's meeting
by bowlofeggs＠fedoraproject.org 14 Aug '17

14 Aug '17

Dear all, You are kindly invited to the meeting: Bodhi stakeholder's meeting on 2017-08-15 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

bodhi-2.10 beta in staging
by Jeremy Cline 14 Aug '17

14 Aug '17

Hey all, As of a few minutes ago, the Bodhi-2.10 beta is running in stg[0]. Check out the release notes[1] for the features and bugfixes included in this release and take them for a test drive! [0] https://bodhi.stg.fedoraproject.org/ [1] https://bodhi.stg.fedoraproject.org/docs/release_notes.html#id1 -- Jeremy Cline XMPP: jeremy(a)jcline.org IRC: jcline

1 0

Proposal: Use a calendar to limit rate of change
by Randy Barlow 12 Aug '17

12 Aug '17

Hello! I was chatting with puiterwijk this morning (well, I guess his afternoon ☺) about the difficult week the systems team has had. There were quite a few changes all happening at once this week: * The update/reboot cycles * RHEL 7.4 was released * Pagure over dist-git was turned on * Bodhi was reconfigured to talk to Pagure instead of Pkgdb * A fedmsg update * More things? Patrick told me that it's been a huge amount of work for him and I assume others this week, because many of the above didn't go so smoothly. I think it's expected and frankly normal for updates to not go smoothly - we are all stretched pretty thin and we don't have a formal QE team to make sure that our infra apps are ready to ship. Thus, I think we should expect changes like the above to be "bumpy" and instead should develop a plan to help smooth out the bumps. I propose that we use our infra calendar (or even a new calendar if preferred) to more formally schedule infrastructure changes, with the goal being to avoid weeks like this one (where so many large changes landed at once). i.e., if I want to make a Bodhi deployment on Monday and I see that there's a Pagure deployment already scheduled for Monday, I should consider a different day. Of course, we can always have exceptions. Sometimes we might have "flag days" where we do want/need two apps to upgrade together. Or maybe sometimes we do want to take advantage of an update/reboot cycle to sneak in an app upgrade, if the systems team is comfortable of course. That's fine when needed, but when not needed I think spreading out the changes will help our systems team avoid insane weeks like this one. Thoughts?

2 1

How to contribute?
by Reza Seyf 12 Aug '17

12 Aug '17

Hello group, I'm new to this mailing list and I want to ask for help to contribute in Fedora infrastructure. Is there any ways to figure out how do you work in infrastructures of Fedora project? Thanks. Reza

3 3

Meeting Agenda Item: Introduction Yoann
by YLB 10 Aug '17

10 Aug '17

Hello world! :-) A quick intro following the checklist on the wiki: - My IRC handle: vbird. - Skills I have: Linux sysadmin for roughly 15 years (including 13+ in a professional capacity); PHP developer in my early years; system scripting (mostly bash and Perl); VoIP / SIP with Asterisk (at a time it still looked like a revolution!); virtualisation (but mostly proprietary products); dozens of irrelevant technos that--if mentioned--would probably make some of us suddenly feel older; Indian food cooking (says my wife...) - Skills I'd like to learn (or improve): Python (a bit rusty), Ruby, Ansible, Docker & OpenShift, KVM, OpenStack, anything else that could be fun playing with. - Associations I have: not a lot anymore (I was more active when I was younger). Self-employed with customers mostly in the financial sector. - Location & timezone: Luxembourg, CET/UTC+1 (or CEST/UTC+2 in the summer.) - What to work on: first things first, joining the fi-apprentice group to have a look at how things work here. Cheers, Yoann E. A. Le Bihan [[ www.Yoann.info ]]

1 0

[patch] Add oldschool mapping for LXQt SIG badge to FAS group
by Justin W. Flory 10 Aug '17

10 Aug '17

Hi all, Attached is a patch to the ansible repo to add a mapping for the LXQt SIG FAS group to their badge. The purpose of doing this is that it automatically awards the badge to all current members of the SIG when the cronjob runs. If someone could review this and merge it in, it would be appreciated. :) Thanks! -- Cheers, Justin W. Flory jflory7(a)gmail.com

2 1

Metrics for Mailman & HyperKitty
by Aurelien Bompard 10 Aug '17

10 Aug '17

Hey folks! Unless I'm mistaken, we currently don't have many useful technical metrics about Mailman and HyperKitty. I've started writing a simple script that would collect those and output something we can eventually graph. It currently uses the "key: value" format that I've seen a lot of monitoring tools use, but I can adapt that to whatever we need. I'm currently getting the following values : - mailinglist count in HyperKitty - email count in HyperKitty - email senders count in HyperKitty - user count in HyperKitty - async task queue size - number of async tasks run per minute - async tasks average exec time - size of the archiving queues in mailman and hyperkitty (should be zero most of the time) - Mailman's shunt queue (for messages it failed to handle, usually encoding problems) Do you think there would be other values that we would need? My aim is to detect issues with the server usage (say, a spam attack) as well as anticipate growth. Another useful metric would be the number of emails sent by the system, but I guess we already have a Postfix plugin somewhere, so I'm trying to stay mailman & hyperkitty-specific here. Currently the plugin takes between 5 and 10 seconds to collect the data. I don't know how precise we want our metrics but a run every five minutes seems sufficient to me. It also depends on how we can set that in collectd, which I don't know (yet!). Thanks! Aurélien

2 3

[release] pdc-updater: 0.6.0
by Ralph Bean 10 Aug '17

10 Aug '17

A new pdc-updater release! There are a few bugfixes related to the MBS, but crucially there is a new handler for propagating retirement: When a `dead.package` file gets committed, the code here (on pdc-backend0*) will update the EOL of that branch in PDC, indicating retirement. 0.6.0 ----- Pull Requests - (@ralphbean) #57, srpm_nevra must not be set when arch is src. https://github.com/fedora-infra/pdc-updater/pull/57 - (@ralphbean) #62, Force creation of parent with type during initialization. https://github.com/fedora-infra/pdc-updater/pull/62 - (@ralphbean) #60, Populate the dist_git_branch value... https://github.com/fedora-infra/pdc-updater/pull/60 - (@ralphbean) #61, Also construct container tags from stable updates tags. https://github.com/fedora-infra/pdc-updater/pull/61 - (@mprahl) #63, Add a handler so that PDC branches are EOL'd when the branch is retired https://github.com/fedora-infra/pdc-updater/pull/63 - (@mprahl) #64, Add some missing doc strings to RetireComponentHandler https://github.com/fedora-infra/pdc-updater/pull/64 - (@ralphbean) #66, Some changes to the retirement handler... https://github.com/fedora-infra/pdc-updater/pull/66 Commits - 6118478b5 srpm_nevra must not be set when arch is src. https://github.com/fedora-infra/pdc-updater/commit/6118478b5 - 600b6175e Populate the dist_git_branch value... https://github.com/fedora-infra/pdc-updater/commit/600b6175e - 17edf56ad Also construct container tags from stable updates tags. https://github.com/fedora-infra/pdc-updater/commit/17edf56ad - 7a022d494 Force creation of parent with type during initialization. https://github.com/fedora-infra/pdc-updater/commit/7a022d494 - b7341977a Add a handler so that PDC branches are EOL'd when the branch is retired https://github.com/fedora-infra/pdc-updater/commit/b7341977a - 31f7caf33 Break retirement out into its own staticmethod. https://github.com/fedora-infra/pdc-updater/commit/31f7caf33 - e2eeec935 Write an init method. https://github.com/fedora-infra/pdc-updater/commit/e2eeec935 - e132ab502 Add Docstrings to RetireComponentHandler https://github.com/fedora-infra/pdc-updater/commit/e132ab502 - e2d52896c Add the audit function to the RetireComponentHandler handler https://github.com/fedora-infra/pdc-updater/commit/e2d52896c - bcb112faa Add some missing doc strings to RetireComponentHandler https://github.com/fedora-infra/pdc-updater/commit/bcb112faa - 3a2cef32e Make these two work functions re-try-able. https://github.com/fedora-infra/pdc-updater/commit/3a2cef32e - fe8af401d Check pagure instead of cgit. https://github.com/fedora-infra/pdc-updater/commit/fe8af401d - e1b0542b4 Fix those mocks. https://github.com/fedora-infra/pdc-updater/commit/e1b0542b4

1 0

[release] fedmsg-0.19.1
by Jeremy Cline 10 Aug '17

10 Aug '17

Hey all, Last night I tagged the 0.19.1 release of fedmsg to fix a few critical issues found in 0.19.0. It's currently only built into the Fedora infra repositories. It will be making its way out to Fedora and EPEL testing repositories near you in the next day or two. Change log: https://github.com/fedora-infra/fedmsg/releases/tag/0.19.1 -- Jeremy Cline XMPP: jeremy(a)jcline.org IRC: jcline

1 0

Plans for Thursday 2017-08-10 Fedora Infrastructure Meeting
by Stephen John Smoogen 09 Aug '17

09 Aug '17

We will have our normal Thursday Fedora Infrastructure Meeting at 1800 UTC on #fedora-meeting. The agenda currently looks as follows on the gobby page. Please add or update as needed. = Meeting start stuff = #startmeeting Infrastructure (2017-08-10) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 dgilmore threebean pingou puiterwijk pbrobinson = Let new people say hello = #topic New folks introductions = 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 PHX2 Colo Trip coming up, Dec 4th - 9th #info FLOCK at Cape Cod Aug29->Sep01 #info Fedora F27 Rebuild (going on now) #info Updated of all servers has been messy kevin/smooge/patrick/relrod #info Bodhi 2.9.0 released. Deployment planned for Monday - bowlofeggs = 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 Update cycles. Lessons learned? #info the last couple of updates cycles have been hard #info different reasons each time but how can we do better? = Apprentice office hours = #topic Apprentice Open office hours 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.) #topic Learn about: Nothing was put here this week = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

Duplicates in package owner alias cronjob?
by Ralph Bean 09 Aug '17

09 Aug '17

I'm confused about something. Can any postfix experts help debug? On Friday I put a new package-owner-alias cronjob in place on bastion (that Matt Prahl wrote). It generates the package owner list from pagure over dist-git instead of generating it from pkgdb. https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=eb241f… Kevin saw that the hourly cronjob is spitting out some errors from the postfix command. However, when I inspect the file, I don't find any duplicates: $ cat /etc/postfix/package-owner | awk ' { print $1 } ' | uniq -d Anybody know what's wrong with that file/output? -Ralph

4 6

Aug status update for Fedora Infrastructure Apprentices
by Kevin Fenzi 09 Aug '17

09 Aug '17

You are getting this email because you are in the 'fi-apprentice' group in the fedora account system (or are reading this on the infrastructure list). Feel free to reply just directly to me, or cc the infrastructure list for everyone to see and comment on. https://fedoraproject.org/wiki/Infrastructure_Apprentice At the first of every month(or so), I am going to be sending out an email like this one. I would like feedback on how things are going for you. I'd like to ask for everyone to send me a quick reply with the following data or anything related you can think of that might help us make the apprentice program more useful. 0. Whats your fedora account system login? 1. Have you logged in and used your fi-apprentice membership to look at our machines/setup in the last month? Do you plan to? 2. Has it helped you decide any area you wish to focus on or contribute to more? 3. Have you looked at or been able to work on any of the fi-apprentice 'easyfix' tickets? https://pagure.io/fedora-infrastructure/issues?status=Open&tags=easyfix 4. Do you still wish to be a member of the group? If not (for whatever reason) could you provide any hints to help others down the road? 5. Is there any help or communication or ideas you have that would help you do any of the above? 6. What do you find to be the hardest part of getting involved? Finding things to work on? Getting attention from others to help you? Finding tickets in your interest area? 7. Have you been able to make any weekly irc meetings? Do you find them helpful or interesting? Do you have any suggestions for changing them? 8. Have you logged into our Gobby instance and read/seen/added to our meeting agenda? https://fedoraproject.org/wiki/Gobby 9. What are the top 5 commands you run by number? You can get these with something like: history | awk '{print $2}' | sort | uniq -c | sort -nr | head -5 (or something more clever of your own devising) Any other general feedback is also quite welcome, including improvements to this email, the wiki page, etc. Note that we recently revamped the getting started and other pages. Please do take a minute to re-read them and let me know if they are more clear or need further adjustments. Any folks I do not hear from in the next week will be removed from the group. (Note that it's easy to be readded when you have time or whatever and it's nothing at all personal, we just want to keep the group up todate with active folks). Thanks, and looking forward to your feedback! kevin

15 14

[release] fedmsg_meta_fedora_infrastructure: 0.19.0
by Pierre-Yves Chibon 09 Aug '17

09 Aug '17

Good Morning Everyone, I just cut a new release of fedmsg_meta_fedora_infrastructure: 0.19.0 ------ Pull Requests - (@Metonimie) #427, Correcting the displayed link for ask.stg.* https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/427 - (@ sayanchowdhury) #428, Add support for PR reviews in Github processor https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/428 - (@pypingou) #424, Be a little less obvious when the assignee is missing https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/424 - (@ralphbean) #433, Turns out that pungi has an icon. Who knew? https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/433 - (@pypingou) #436, Adjust the scm links to the deployment of pagure over dist-git https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/436 Uploaded to pypi, will be updating the RPM shortly. Pierre

1 0

Meeting Agenda Item: Introduction Martin Smola
by Martin Smola 08 Aug '17

08 Aug '17

Hi all, Let me introduce myself. My name is Martin Smola and I am coming from Czech Republic. IRC: martincz What skills you have to offer and which you would like to learn. I know HTML, CSS, Bash, Linux advanced. I would like to learn more Linux to be professional, born shell and Perl, Python, OpenStack just for now but I am opened to everything what will be useful for my life. In past I got Cisco CCNA1 and CCNA2. I made some migrations of WAR file with big MySQL database for Tomcat, which I put to my installed CentOS and deployed there. I made as well migration of Firebird database with my cleaned minimal installation of CentOS. I work with Cisco Switches L2 and L3. I installed Apache and put websites there. I can help myself or with my friend Google. I have root privileges to all our CentOS and Windows servers. I can manage group policy and AD as well. i work with Synology NAS as well. I help end users with obviously Application problem. I learn RHCSA and I want to pass the exam soon and start learn RHCE. I hope someone of you will take me under his wings. Regards, Martin Smola

1 0

[Release] pagure: 3.5
by Pierre-Yves Chibon 08 Aug '17

08 Aug '17

Good Morning Everyone, I just cut a new pagure release: 3.5 Here is its changelog: * Tue Aug 08 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 3.5-1 - Update to 3.5 - Fix login when groups are managed outside - Fix the ordering of the issues by priority using JS and its documentation - Indicate the issue/PR status in the title of its link - Correct typo in waiting page template: 'You task' -> 'Your task' (Hazel Smith) - Fix redirect in search (Carl George) - Fix removing users of a project - Allow customizing the HTML title globally - Drop the new line character and the '# end of body' message when loading the config - Scroll to the comment section on clicking reply. (shivani) - only show issues on the My Issue page if the issue tracker is on for the project (Vivek Anand) - Update the refresh-gitolite action of pagure-admin for the new interface (turns out this wasn't in fact merged in 3.4) - Add a configuration key to make pagure case sensitive - Add an USER_ACLS configuration key - Document the different API token ACLs configuration keys - Fix syncing groups from external account sources (Patrick Uiterwijk) Most changes being related to dist-git, I upgrade stg.pagure.io as well as production. I have adjusted pkgs01.stg (which seems to be down for the moment) to benefit from the new features so we can test them there before updating prod. Happy hacking! Pierre

1 0

Meeting Agenda: Introduction Patrick Kuny
by Patrick Kuny 08 Aug '17

08 Aug '17

- IRC Handle: netcronin - Github: netcronin - Email: pmk62810(a)gmail.com - What skills you have to offer and which you would like to learn. - Beginner Ansible and Chef skills, beginner Perl and Bash Scripting. - Beginner experience in Linux Administration - experience setting up various services: HTTP(S), FTP, SFTP, GlusterFS replication, Zabbix monitoring, Chef cookbooks, Ansible playbooks, General Server Administration (Fail2Ban, SELinux, iptables, FirewallD, etc.) - Worked specifically with moving open-source technology stacks to Docker containers. - Studying for RHCSA - Interested in automation, general Linux administration - Run a small homelab for testing (automated via Ansible, of course) - Network knowledge - Work for Cerner Corporation in Kansas City, MO as a System Engineer - Central Timezone - Also plan to join the Fedora Ambassadors program - Interested in teaching and mentoring new users/infra members eventually, once I've earned it. - What you want to learn - Anything the team needs help with, especially Linux admin work and best practices surrounding it. - Interested in Fedora Infrastructure Apprentice program. Both joining and helping out with. - Any initial questions you have for the team - Nothing specific. Lurking in IRC and have read the last few meeting minutes, as well as looking over the architecture topology. Bear with me as I may ask some dumb qu Thanks, Patrick Kuny C: 816.507.5495 [image: https://www.linkedin.com/in/patrick-kuny-3855964b] <https://www.linkedin.com/in/patrick-kuny-3855964b>

1 0

[Release] mdapi: 2.10.1 and 2.10.2
by Pierre-Yves Chibon 08 Aug '17

08 Aug '17

Good Morning Everyone, I just cut a couple of new mdapi releases: 2.10.1 and 2.10.2. Here are their changelog: * Tue Aug 08 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.10.1-1 - Update to 2.10.1 - Fix the srcpkg endpoints * Tue Aug 08 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.10.1-1 - Update to 2.10.1 - Fix the srcpkg endpoints This second release was required because someone pushed to a stable Fedora release (f25 in this case) an upgrade of python3-aiohttp from 1.0.5 to 2.2.0 which as you can see is a major version upgrade and of course lead to some API changes. This is currently happily working in prod and stg. Happy querying! Pierre

1 0

Meeting Agenda Item: Introduction Kai Bojens
by Kai Bojens 07 Aug '17

07 Aug '17

Hello everybody, please let me introduce myself. My IRC nick is 'profnixer' (Fedora Account: kbojens) and I'd like to join the Infratructure Apprentice group. I'm a Linux sysadmin for more than twenty years now and have gained some experience in almost everything but networking. However, my main focus is everything related to web hosting (mail, web, database, HA) and of course some desktop stuff. So, I know how to use Bash, Perl, git, saltstack some rudimentary C and sometimes even python. For the start I'd like to see if I can solve some of the low hanging fruits in 'easyfix' like the mapping for example.

1 0

[release] MirrorManager2: 0.8.1
by Adrian Reber 07 Aug '17

07 Aug '17

A new release of MirrorManager2 is available: 0.8.1 - Revert namespace changes https://github.com/fedora-infra/mirrormanager2/pull/214 - move-devel-to-release: fix the script to work with f26 https://github.com/fedora-infra/mirrormanager2/pull/213 - Initial conversion to Fedora Bootstrap https://github.com/fedora-infra/mirrormanager2/pull/204 - umdl: various fixes found in production https://github.com/fedora-infra/mirrormanager2/pull/211 Adrian

1 0

Big HyperKitty schema change
by Aurelien Bompard 07 Aug '17

07 Aug '17

Hey folks! There's a pretty big DB schema change that I'd like to do in HyperKitty, and since it involves a primary key I expect a downtime of several hours, possibly a day (more precise testing going on) The good news it that mailman will keep running, only the web UIs will be down (HyperKitty & Postorius, the admin UI). It's a change that I've put off for a while, but the more we wait the longer the downtime will be (because it depends on the size of the email table). What time do you think would be the less worse for such a change? After freeze break next week? After General Availability (whenever that is) ? Another time? I have a feeling that after freeze break is better because the folks who use the web UIs to read email may also be those who will need to communicate more after the GA, to discuss communication and reviews. I don't mind starting the migration on a weekend of course, to impact less people. Thanks for your input. Aurélien

3 5

Meeting Agenda Item: Introduction Toni Rantala
by T. Rantala 06 Aug '17

06 Aug '17

Hello everyone! I'm currently a service desk specialist, typical level 1 or 2 phone support job but I also do server monitoring few days a month. Mainly monitoring Windows servers but there are some RHEL and UNIX machines as well. Really some basic stuff, restarting servers and services, making sure nothing runs out of free space, investigating why some process is eating up all the RAM or CPU and stuff like that. I started out with Linux with Fedora 14 some years ago at school, gave up Linux for gaming and came back when F20 was released and have used it ever since for everything else but gaming. I've been doing some translations for Fedora in the Finnish group and now I'm trying to give more back to the community and help any way I can. I'm looking forward to learn much, much more about Linux (maybe something about security too, Linux and security are the two things I'm most interested in) and hopefully get a job as a Linux SysAdmin in the future. I believe being a part of Fedora community and seeing the real life tickets is way more valuable than just spinning up a few VMs and practicing on my own. I will have to do a lot of studying and asking "stupid" questions around before I can actually contribute but I will do my best. IRC handle and FAS: bombandealer Best regards Toni

1 0

Meeting Agenda Item: Introduction James Cassell
by James Cassell 06 Aug '17

06 Aug '17

Hello, I'm a systems administrator for my day job. I'm currently working on using ansible to automate machine provisioning and management in a vmware virtualized environment. The linux machines are mostly CentOS 6 with some CentOS 7 and a couple RHEL 6 boxes. These are in a predominantly windows environment, with Microsoft Active Directory domains. (In a previous job, I worked with chef in a debian environment.) I'm hoping to help out any way I can and "learn by doing." I'm specifically looking to do tasks with ansible and to learn best practices. I have not been active with Fedora for several years, but in the past, I've helped with the wiki, submitted lots of bodhi feedback, and helped with testing releases. Outside of Fedora, I've contributed an implementation of the sieve imap4flags extension to the cyrus imapd project. This was mostly done in C, but also included a bit of yacc/bison... I'm competent at programming but haven't done much of it as a day job. I expect I will end up learning python as it's becoming ubiquitous. IRC Handle: cyberpear I look forward to helping and learning! I've also just joined the fi-apprentice group and am looking around. V/r, James Cassell

2 1

Syncing and archiving old releases
by Stephen John Smoogen 04 Aug '17

04 Aug '17

In the past, we would normally begin syncing soon to be EOL releases over to Archives so that the mirrors would be ready for it. We haven't done this for a bit and a couple of mirrors have complained that /pub/fedora is larger than they want to keep. I would like to get an official policy to them about how many releases that a mirror should expect to be in /pub/fedora and when we plan to archive off releases. The steps for syncing/hardlinking releases was the following: log into a box with read-write access to the the release tree. sudo su -s /bin/bash ftpsync cd /pub/fedora/linux/releases ls -l /pub/archive/fedora/linux/releases/ # to see if tree is already synced If I were to archive off 23 I would now do the following: cp -lr 23/ /pub/archive/fedora/linux/releases/ this should hardlink everything across so we save disk space. cd ../updates cp -lr 23/ /pub/archive/fedora/linux/updates/ cd testings cp -lr 23/ /pub/archive/fedora/linux/updates/testing/ cd /pub/fedora-secondary/releases cp -lr 23/ /pub/archive/fedora-secondary/releases/ cd ../updates/ cp -lr 23/ /pub/archive/fedora-secondary/updates/ cd testing cp -lr 23/ /pub/archive/fedora-secondary/updates/testing/ Make any changes to scripts which do fullfilelist to make it know about new trees. Announce the mirroring to mirrors-list and then wait 2 weeks. After two weeks are done, have mirrormanager point to the archive tree. Remove the data out of /pub/fedora and /pub/fedora-secondary Hardlink the file in a previous archived directory to the empty directory Update the fullfilelist Email mirrorlist about the changes being completed ====== What should we tell the lists that the number of releases which will be in the main repository now? And how many releases should I archive off after F24 goes EOL next week? -- Stephen J Smoogen.

4 6

Re: Aug status update for Fedora Infrastructure Apprentices
by Athos Ribeiro 03 Aug '17

03 Aug '17

On Aug 2, 2017 7:46 PM, "Kevin Fenzi" <kevin(a)scrye.com> wrote: > > 0. Whats your fedora account system login? athoscr > > 1. Have you logged in and used your fi-apprentice membership to look at > our machines/setup in the last month? Do you plan to? > yes > 2. Has it helped you decide any area you wish to focus on or contribute > to more? yes > > 3. Have you looked at or been able to work on any of the fi-apprentice > 'easyfix' tickets? not lately > 4. Do you still wish to be a member of the group? If not (for whatever > reason) could you provide any hints to help others down the road? > yes. See the easyfixes, join IRC. > 5. Is there any help or communication or ideas you have that would help > you do any of the above? > no > 6. What do you find to be the hardest part of getting involved? Finding > things to work on? Getting attention from others to help you? Finding > tickets in your interest area? > Organizing time spent in Fedora activities. > 7. Have you been able to make any weekly irc meetings? Do you find them > helpful or interesting? Do you have any suggestions for changing them? > yes/yes/not at all > 8. Have you logged into our Gobby instance and read/seen/added to our > meeting agenda? https://fedoraproject.org/wiki/Gobby > yes > 9. What are the top 5 commands you run by number? You can get these with > something like: > > history | awk '{print $2}' | sort | uniq -c | sort -nr | head -5 > > (or something more clever of your own devising) > This is actually interesting. I believe some of them change a lot depending on what I am working on. 265 ls 196 git 125 vim 105 cd 54 make -- Athos Ribeiro http://www.ime.usp.br/~athoscr

1 0

Documentation review for fedmsg
by Jeremy Cline 03 Aug '17

03 Aug '17

Hey folks, I recently started re-writing the fedmsg documentation. Since its primary users are people in Fedora Infrastructure, I'd love your feedback on the first draft. There's a pull request[0] where you can leave comments on the diff, but I also built the documentation so you can see what it really looks like. The current docs: https://fedmsg.readthedocs.io/en/latest/ The proposed docs: http://jcline-fedmsg.readthedocs.io/en/reorg-docs/ I'm particularly interested in how you find the organization of the proposed docs. Is the order weird/unexpected/confusing? Is there a section you think is missing? Do they go into enough detail? Any feedback would be greatly appreciated (either on GitHub or here via email). [0] https://github.com/fedora-infra/fedmsg/pull/453 -- Jeremy Cline XMPP: jeremy(a)jcline.org IRC: jcline

2 1

Where do we want to put pagure?
by Pierre-Yves Chibon 03 Aug '17

03 Aug '17

Good Morning Everyone, As pagure over dist-git is coming closer and closer I realized we didn't talk about the most important part of the project: where do we want to put it? In stg I put it under src.stg.fp.o/pagure so it stands nicely on the side of everything else on the server and to be sure it is not going to conflict. But, do we want to follow the same path in production or do we want to deploy it at src.fp.o/ directly? Thoughts? Pierre

9 10

Plans for Thursday 2017-08-03 Fedora Infrastructure Meeting
by Stephen John Smoogen 02 Aug '17

02 Aug '17

= 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 (2017-08-03) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 dgilmore threebean pingou puiterwijk pbrobinson = Let new people say hello = #topic New folks introductions = 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 PHX2 Colo Trip rescheduled til later #info FLOCK at Cape Cod Aug29->Sep01 #info Fedora F27 Rebuild done #info Update/reboot for Infra Aug 7->Aug 10 = 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 (2017-07-27) Service Level Expectations (SLE) #info questions from the floor? = Apprentice office hours = #topic Apprentice Open office hours 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.) #topic Learn about: Nothing was put here this week yet = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

Meeting Agenda Item: Introduction Jonathan Lozada De La Matta
by Jlozada2426 02 Aug '17

02 Aug '17

IRC Handle: jlozadad I been working on linux for the last 7 years or so and I was wondering how I can help the project. I use ansible for mostly everything I do. I want to be able to expand my skills in python. I was interested in mostly working in ask.fedora and see on how I can help there or if there is another solution that can work better. Jonathan Lozada De La Matta Linux System Administrator

1 0

[Release] mdapi: 2.10
by Pierre-Yves Chibon 02 Aug '17

02 Aug '17

Good Morning Everyone, I just cut a new release of mdapi: 2.10. Here is its changelog: * Wed Aug 02 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.10-1 - Update to 2.10 - Fix displaying the proper basename - Expose the upstream URL as present in the metadata in the JSON returned - Fix the JSONP support of the branches endpoint The upstream url will allow us to include the information on pagure over dist-git as we had it in pkgdb. This is now live in stg and prod. Happy querying, Pierre

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure August 2017