16:02:07 #startmeeting Infrastructure (2021-04-15) 16:02:07 Meeting started Thu Apr 15 16:02:07 2021 UTC. 16:02:07 This meeting is logged and archived in a public location. 16:02:07 The chair is dtometzki. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:02:07 The meeting name has been set to 'infrastructure_(2021-04-15)' 16:02:08 #meetingname infrastructure 16:02:08 The meeting name has been set to 'infrastructure' 16:02:08 #chair nirik smooge siddharthvipul mobrien zlopez pingou bodanel dtometzki 16:02:08 #info Agenda is at: https://board.net/p/fedora-infra 16:02:08 #info About our team: https://docs.fedoraproject.org/en-US/cpe/ 16:02:08 Current chairs: bodanel dtometzki mobrien nirik pingou siddharthvipul smooge zlopez 16:02:08 #topic aloha 16:02:24 .hi 16:02:26 dtometzki: dtometzki 'Damian Tometzki' 16:02:31 .hi 16:02:32 darknao: darknao 'Francois Andrieu' 16:02:38 hello todether and welcome 16:02:42 .hi 16:02:43 austinpowered: austinpowered 'T.C. Williams' 16:02:47 hello 16:02:50 .hi 16:02:52 nils: nils 'Nils Breunese' 16:02:57 nope 16:03:00 .hello nphilipp 16:03:00 nils: nphilipp 'Nils Philippsen' 16:03:18 .hello zlopez 16:03:19 Zlopez[m]: zlopez 'Michal Konečný' 16:03:28 hello 16:03:32 .hi 16:03:34 mobrien: mobrien 'Mark O'Brien' 16:03:35 morning 16:03:47 .hi 16:03:48 bodanel: bodanel 'Bogdan Benea' 16:04:24 hi all 16:04:50 good crowd today. :) 16:05:02 howdy 16:05:43 fine and you ? 16:05:52 hello 16:06:29 #topic New folks introductions 16:06:29 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 16:06:30 #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted 16:07:04 Any new folks today? 16:07:08 Yes, me 16:07:16 Hello everyone 16:07:28 My name is Antonio and I live in Madrid, Spain 16:07:37 hello ayustae 16:07:49 Hi ayustae 16:07:49 welcome ayustae 16:07:57 I work as IT Consultant 16:08:20 And have experience in AWS, Openshift, Ansible, Python (and of course Linux) 16:08:45 I discovered this group two weeks ago and would like to contribute to it 16:09:10 welcome ayustae! 16:09:32 welcome ayustae 16:09:34 bienvenidos 16:09:50 Thank you very much :) 16:09:55 welcome ayustae and a good start here 16:10:27 Hello. My name is Cosmin and I'm from Toulouse France. I'm a SW working for Continental. Im workgin with Go,Kube,Docker, Kaflka. I have an experience with Python(flask django). 16:10:28 #topic Next chair 16:10:28 #info magic eight ball says: 16:10:28 #info chair 2021-04-22- mobrien 16:10:28 #info chair 2021-04-29 - zlopez 16:10:28 #info chair 2021-05-06 - ??? 16:10:50 Oh sorry tupanu 16:10:58 welcome tupanu 16:11:25 Thank you 16:11:29 welcome tupanu 16:12:41 anyone want to take the 05-06 ? 16:13:14 welcome tupanu. 16:14:10 you can put me next chair 16:14:17 welcome tupanu 16:14:41 welcome tupanu! another fellow from Toulouse ;) 16:14:43 volunteer for the chair on 05-06 16:14:52 ? 16:15:38 Thank you darkno ;) 16:16:16 dtometzki, me 16:16:21 For the new colleagues chair is where the meeting leads 16:16:51 the infrastructure meeting every thrusday 16:17:26 many thanks bodanel 16:17:44 #info chair 2021-05-06 - bodanel 16:18:58 #topic announcements and information 16:18:58 #info CPE Infra&Releng EU-hours team has a Monday through Thursday 30 minute meeting going through tickets at 1030 Europe/paris in #centos-meeting 16:18:58 #info CPE Infra&Releng NA-hours team has a Monday through Thursday 30 minute meeting going through tickets at 1800 UTC in #fedora-meeting-3 16:18:58 #info work is being done on getting COPR proper powerPC systems 16:18:59 #info final freeze started on April 06th at 1400 UTC 16:19:47 any additional announcements and information ? 16:22:00 No, then we will go to the next topic in 1 minute 16:22:06 .hi 16:22:07 nb: nb 'Nick Bebout' 16:22:15 hi nb 16:22:58 #topic announcements and information 16:22:59 #info CPE Infra&Releng EU-hours team has a Monday through Thursday 30 minute meeting going through tickets at 1030 Europe/paris in #centos-meeting 16:22:59 #info CPE Infra&Releng NA-hours team has a Monday through Thursday 30 minute meeting going through tickets at 1800 UTC in #fedora-meeting-3 16:22:59 #info work is being done on getting COPR proper powerPC systems 16:22:59 #info final freeze started on April 06th at 1400 UTC 16:23:20 #topic Oncall 16:23:20 #info https://fedoraproject.org/wiki/Infrastructure/Oncall 16:23:20 #info darknao is on call for 2021-04-15 to 2021-04-22 16:23:20 #info mobrien is on call for 2021-04-23 to 2021-04-29 16:23:20 #info ??? is on call for 2021-04-30 to 2021-05-06 16:23:31 sorry my misstake 16:23:51 oh, that's me :) 16:23:53 what is the expectation of oncall? is there a certain level of availability needed? or just "someone to keep an idea on IRC" 16:23:57 .oncalltakeeu 16:23:57 darknao: Error: You don't have the alias.add capability. If you think that you should have this capability, be sure that you are identified before trying again. The 'whoami' command can tell you if you're identified. 16:24:21 .admin capability add darknao +alias.add 16:24:21 nb: Kneel before zod! 16:24:25 darknao try now? 16:24:34 .oncalltakeeu 16:24:34 darknao: Error: You don't have the alias.add capability. If you think that you should have this capability, be sure that you are identified before trying again. The 'whoami' command can tell you if you're identified. 16:24:41 nb it is keep an eye on irc, if you can help with the issue do and if you can't ask them to raise a ticket 16:24:42 nb: basically someone to tell people to file tickets. ;) 16:24:46 last days there were no action with on call 16:24:59 and not to bother non oncall directly 16:25:11 yeah, it's been quiet... too quiet? :) 16:25:27 it was very quite 16:25:52 probably nobody can log in anywhere to complain :) 16:26:15 Anyone available for the week 2021-04-30 to 2021-05-06 ? 16:26:20 dtometzki I could do it 16:26:55 #info nb is on call for 2021-04-30 to 2021-05-06 16:27:03 many thanks nb 16:27:08 dang it, late again 16:27:12 .hello computerkid 16:27:13 computerkid: computerkid 'Grayson Penland' 16:27:22 hello computerkid 16:27:25 o/ 16:28:05 dtometzki actually, I cannot do 04-30, but i could do the others 16:28:10 I'll be mostly offline on Friday the 30th 16:28:23 will be helping with covid vaccine clinic at work 16:28:43 I can stay on the extra day 16:29:01 Thanks mobrien 16:29:28 Thanks mobrien 16:30:23 #topic Monitoring discussion [nirik] 16:30:23 #info https://nagios.fedoraproject.org/nagios 16:30:23 #info Go over existing out items and fix 16:30:34 nirik your part ? 16:30:42 nothing new really to report this week. 16:30:46 all the same old things 16:30:54 ok great 16:31:40 #topic Learning topic discussion 16:31:40 #topic Ideas for upcoming learning topics 16:31:40 #info "New fedora badge process" on 15th April, 2021 16:31:55 oh wait, that's me 16:32:00 yes 16:32:21 So, I'm going to cover the process of pushed a Fedora badge to the badges system for manual awarding 16:32:46 I'm not going to talk about how to make automatic badges, because honestly I've never learned how 16:33:09 sorry could you short explain for what the fedora badge is ? 16:33:13 oh yeah 16:33:25 So we have a badges system, badges.fedoraproject.org 16:33:55 You can get badges by doing different things like testing packages, participating in events, going to meetings, etc 16:34:17 you can see my badges page for example, badges.fedoraproject.org/user/computerkid 16:34:46 To make a badge you file a ticket with pagure.io/fedora-badges 16:35:25 Once someone designs the artwork(usually just a volunteer) a sysadmin has to come in and push it 16:35:43 and for what is that good ? 16:35:47 to push it you have to be in sysadmin-badges I think 16:35:55 dtometzki a badge? 16:36:01 yes 16:36:18 It's essentially an incentive to contribute. Like a gameification 16:36:28 there's even a leaderboard 16:36:53 https://badges.fedoraproject.org/leaderboard 16:37:14 Let me find an example ticket 16:38:31 To push a badge you have to know some things from the ticket. 16:38:32 https://pagure.io/fedora-badges/issue/783 16:39:42 thanks computerkid 16:39:47 you have to find the Title of the badge, the description, the latest SVG file and PNG file of the artwork for that badge, who needs access to push that badge, and what category it should be in 16:40:02 and the URL to the pagure issue where that badge was made 16:40:23 What category the badge is in, indicated by the color ring around the outside of it's picture. Blue = Content, Orange = Development, Pink = community, so on. 16:40:36 Check the badge index for more. https://badges.fedoraproject.org/explore/badges 16:41:13 To get this badge in the system you first need to clone the git repo, 16:41:31 and download the SVG and PNG of the badge 16:42:08 So I just start at the bottom and scroll up till I find them 16:42:42 Which repo? 16:42:46 now i know what i will read today evening :-) 16:43:15 Then give them names, so in this case they were FWD-organizer-2020.png/svg 16:43:31 sorry Zlopez[m] it's https://pagure.io/fedora-badges.git 16:44:01 So in that repo there is an svg/ and a png/ folder 16:44:16 So drop the SVG and PNG in there once they are named 16:44:30 Next do the whole git add, git commit, git push 16:44:38 this is assuming you have commit rights 16:45:16 After that you SSH into the batcave server with all the ansible playbooks and run manual/push-badges.yml 16:45:29 Which is also on a cron to run every 15 minutes 16:45:40 (yeah, I was about to say there is a cron) 16:46:14 After that you can double check that it pushed, like https://badges.fedoraproject.org/pngs/fwd-organizer-2020.png 16:46:33 That's synced with the repo using the ansible playbook 16:46:50 So now the files are in the server, we just need to get it into it's own badge 16:47:14 There are two ways to do this, the GUI way, and the CLI way. I prefer GUI, so I'm going to explain that one 16:48:03 If you are a badges sysadmin you can go into badges.fedoraproject.org and click admin, which has a big page full of forms 16:48:18 There's one labeled 'Add badges' 16:48:38 You put in the Name, URL to PNG, URL to Issue thread, and Description. There is a Tags and issuer field, but we can ignore those for now. 16:49:49 The URL to PNG is https://badges.fedoraproject.org/pngs/your-badge-here.png, the issue thread is pagure.io/fedora-badges/issues/issue-number, and the description and name you should be able to find in the issue. 16:50:04 Once you fill those in there's a button to submit it 16:50:16 Click that, and you've made a badge! 16:51:52 Next we have to go to https://badges.fedoraproject.org/explore/badges and find the one you just made, it should be in the uncatagoriesed section which is usually empty 16:52:26 Click into it, and you'll see it has no tags, which is why it doesn't have a category 16:52:37 Next I normally tag it, and to do that I find a similar badge, E.I. the one for the year before if it's an event, or just something from the same catagory and grab the tags 16:52:57 great, thanks for your detailed Information computerkid was very interesting for me as a new here 16:53:00 the tags are what sort it into categories, so a content badge has the tag content, for example 16:53:08 Thanks dtometzki 16:53:24 indeed thanks. :) 16:53:42 Thanks computerkid 16:53:46 once it has a tag it will go into the correct category. Then once it's tagged, I go back to admin and give authorization to it. So I just put in the badge name, and the person it needs access email, e.i. computerkid@fedoraproject.org 16:53:53 and then you close the ticket and you're done 16:53:54 That's it 16:53:59 Any questions? 16:53:59 Does anyone have a new learning topic for the next meeting ? 16:54:06 Sorry if I ran too long 16:54:18 no problem 16:54:43 Nice explanation computerkid 16:55:03 :D 16:55:14 I assume there is also some guide that is describing the process 16:55:20 Oh yeah 16:55:25 I meant to link that 16:55:31 https://docs.pagure.org/infra-docs/sysadmin-guide/sops/badges.html 16:56:11 I tried to simplify it, because that page is so long 16:56:56 nice, thanks computerkid 16:57:32 computerkid++ 16:57:55 computerkid++ 16:58:18 would be great to line up the next talk... anything anyone wants to hear about or talk on? 17:00:03 nirik: It would be probably nice to have talk about the onboarding process to fedora infra 17:00:48 Zlopez[m]: sure, although that might be more of a 'working session' to fix things than a talk. ;) 17:00:51 if we have a question about how to update a vagrant image used for testing, we can ask it here ? 17:00:52 I was not sure if this was the correct place to ask but, yes please, having the onboarding process explained would be awesome 17:01:24 nirik: Just talk about what we have right now and how it works currently 17:02:04 sure, I'm all for it, just saying we should also work on it. ;) 17:02:10 Asmodee[T]: Which vagrant image are you talking about? 17:02:52 nirik: Yeah, we should :-) 17:03:10 so, sure, sign me (and hopefully others will help) for that next week... 17:03:15 nirik is it ok for you to prepare some information on the onboarding process ? 17:03:45 Zlopez[m]: I would have to prepare the question, but didn't know where to ask when I got stuck. it was for fedora-messaging or else I don't remember exactly 17:04:10 dtometzki: sure. Happy to. 17:04:23 Asmodee[T]: In this case the best place would be probably the project itself 17:04:23 #info "Onboarding process to fedora infra" on 22th April, 2021 - nirik 17:05:08 nirik, i see a message about zodbot isnt available in #fedora-meeting 17:05:18 As another topic that I would be interested in, is the flatpak build chain 17:05:47 dtometzki: yep. fixed. 17:05:57 thanks 17:06:09 Zlopez[m]: I am not sure of all the parts of that myself... perhaps we could invite otaylor to talk on it... 17:06:33 nirik: otaylor would be a best for this 17:07:16 Zlopez[m], can you ask otaylor for a date ? 17:08:21 then we can fix the session next time 17:09:23 I can ask him 17:09:42 I will update the agenda 17:09:50 i think move to the next topic because our meeting time ended 17:09:53 #topic Open Floor 17:10:10 thanks Zlopez[m] 17:10:27 any open floor topics to discuss ? 17:11:08 * nirik has nothing off hand 17:11:23 when no, then i will close the meeting in 1 minute 17:11:52 thank you dtometzki for chairing 17:13:19 Many thanks for the participation and have a nice day 17:13:28 Thank you very much 17:13:31 Good bye 17:13:36 thank you. have a nice day. byt 17:13:42 #endmeeting