18:00:05 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:05 Meeting started Thu Apr 15 18:00:05 2021 UTC. 18:00:05 This meeting is logged and archived in a public location. 18:00:05 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:05 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:06 #chair mboddu nirik smooge pingou mobrien nb 18:00:06 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:06 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:06 Current chairs: mboddu mobrien nb nirik pingou smooge 18:00:06 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:06 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:07 #info reminder: speak up if you want to work on a ticket! 18:00:08 #topic Tickets needing review 18:00:10 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:17 here 18:00:57 I'm kinda here too 18:01:46 who wants to modify tickets? 18:02:20 already started 18:02:33 .ticket 9876 18:02:34 nirik: Issue #9876: Only sysadmin-main members have access to maintainer-test instances - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9876 18:02:41 med/med/ops? 18:02:57 mobrien proposed a setup, I counter proposed another... 18:03:12 done 18:03:23 should we try a thread on the infra list to see if someone has another smarter idea? 18:03:28 or just go with one of those? 18:03:36 Let's go ahead with the vpn set up seems easier 18:03:49 Or thread 18:04:03 yeah, I think it should work... 18:04:07 i would go with a heads up to @pui 18:04:21 * i would go with a heads up to @puiterwijk to see if he has a better idea 18:04:27 sure. I'll try and catch him tomorrow morning my time. 18:04:49 otherwise I got nothing else 18:04:58 .ticket 9877 18:04:59 nirik: Issue #9877: Badge notification e-mail sent twice - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9877 18:05:24 no idea on this one. perhaps we have stg and prod buses crossing again? 18:05:27 low-gain/medium-pain/ops and tag whoever 'runs' badges (misc?) 18:05:38 yeah, +1 18:06:26 +1 18:06:50 i don't see any un-tagged releng tickets 18:07:06 me too neigthere 18:07:10 either. 18:07:11 sheesh 18:07:20 #topic work plans 18:07:20 #info everyone should note what things they are hoping to work on over the next day/week 18:07:33 I sitll need to catch up to my mail barge. 18:07:41 hi 18:07:46 .ticket 9059 18:07:47 ssmoogen[m]: Issue #9059: copr: ppc64le HW machines re-installed in new lab? - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9059 18:07:48 and then hopefully someday the archive hardlink finishes and I can swap that in 18:08:15 I have to finish deploying ipa stg 2 only got to it late today so didn't get very far 18:08:16 oh hey, it did finish finally. 18:08:22 Linked: 1711758 18:08:22 Saved: 1842508873728 18:08:59 that is my last 'assigned' ticket. I have to wait for optic cables to arrive in the US from Ireland (they were mailed to Aoife by mistake) 18:09:31 ssmoogen[m]: well traveled cables 18:09:53 yeah :) 18:10:06 my hope will be May to go in and try to get the cabling done and the COPR stuff can get 'done' as I can 18:10:20 They get to experience our lovely climate 18:10:36 thankfully they are optical so won't corrode 18:10:38 much 18:10:42 ssmoogen[m]: that would be great. What all is left there aside the copr stuff? the storinator, anything else? 18:11:17 storinator, aarch64, power64, 1 dell fx 18:12:06 ah, I thought we moved the aarch64's... perhaps we only talked about it. 18:12:09 plus some hardware we got for a 'rust' project i have no idea about beyond put it in a rack when it was not rack system 18:12:12 I should probably take something there to get some experience on it 18:12:24 nirik: there was 1 ampere box in the cloud 18:12:34 there are 2 caviums and 1 mustange 18:12:47 oh yeah, the maintainer test arm... ok. 18:13:13 there is one serial interface and then I need to get the apc's onto a network 18:13:16 hum... 2 caviums there? I thought we had all 4 of the ones we have in iad2? 18:13:36 no there was a loaner set that was sent for COPR 18:13:49 ok 18:14:13 well they are all loaner sets but that was the original intention so they were in the cloud. (they may have been for openstack instead.. they ended up being copr) 18:15:56 I will add that inventory to the private docs. [all the hardware is in the master invetory spreadsheet internal] 18:16:15 yeah, we also probibly want to update that big board thing... 18:16:58 I am at vaccination center, cant attend the meeting 18:17:10 good luck bhujji 18:17:39 bhujji: 👍 18:17:45 I am jealous! It will be months before I can get one here 18:17:59 * nirik got his first one saturday... 18:18:17 #topic Open Floor 18:18:17 nirik: mobrien[m] after this meeting I will be heading to pick up the car one more time from the automechanic 18:18:33 any items to discuss or tickets or pull requests or anything? 18:19:06 I have a pr but post freeze should be OK gimme a sec 18:19:23 * Southern_Gentlem wonders if ssmoogen[m] it taking the car out to a field and shooting it 18:19:49 Southern_Gentlem: I can't yet.. its a long walk from the field 18:19:56 https://pagure.io/fedora-infra/ansible/pull-request/544 I see you already commented nirik 18:19:57 I have to run out and take someone else to town, and tomorrow afternoon I will probibly go do a store run... 18:20:31 mobrien: yeah. can we get a run of that nowish so we can ping affected folks? 18:20:36 my only item I am going to put a PR in for would be to get the copr hardware using the right inventory playbook 18:21:02 that should get them able to take over the AMD boxes 18:21:27 nirik I can either make that an FBR or manually put it on the server and run it later? 18:21:28 I am working with Matt G when he is out of fire drills to see if we can get the s390x fw changes done this evening 18:21:56 mobrien: either way... if you can get one more +1 I guess freeze break 18:22:12 ssmoogen[m]: cool. So, there's another set of firewall changes I need to put in... 18:22:24 Ok FBR sounds good 18:22:35 * mobrien nudges smooge 18:23:25 staging: bugzilla2fedmsg01.stg needs to talk to the bugzilla staging broker... and os-node*.stg also (so we can move it to openshift and it can talk to it from there) 18:24:22 production: os-node* needs to be able to talk to prod bugzilla broker, so we can move prod from bugzilla2fedmsg01 to openshift. In this case tho, prod is working currently (unlike stg) 18:25:45 ok since ips for openshift may change with new OS hardware.. I would say make it 10.3.163.0 > bugzilla broker and 10.3.166.0 > bugzilla.stg broker 18:25:58 then you don't need to worry about having more hardware added or moved around 18:26:00 ssmoogen[m]: seems fine to me. 18:26:19 mobrien[m]: I have +1 the bfr 18:26:20 I could try filing that, or mobrien could, or we could just have you ask matt smooge ? :) 18:26:51 no we have to go through the process. no direct items to matt anymore 18:27:26 his management want these done via the internal tool from now on 18:28:49 makes perfect sense to me. :) 18:29:44 mobrien: you want to try it? or want me to? 18:29:54 * nirik digs up the port 18:30:07 i can walk someone through it later 18:30:24 roles/bugzilla2fedmsg/templates/bugzilla2fedmsg.ini has the hostnames and ports 18:30:38 ssmoogen[m]: Thanks! 18:31:17 ok, anything else to discuss? 18:31:25 quick question does anyone knwo the default account/password for the fedora cloud images? 18:31:41 is it something like fedora/fedora 18:31:43 I can do it in a little bit, let me know when you are available smooge 18:31:45 there is not any 18:32:03 You have to pass anything you want via cloud-init 18:32:28 They are fedora user but need to add auth of some sort 18:32:47 If its aws you will have defined a key pair 18:32:57 the account is locked, it depends on cloud-init to add a ssh key. 18:32:59 ah ok. 18:33:22 but you can fake it with libvirt... there's been some howtos 18:34:04 ok, thanks for coming everyone! 18:34:06 #endmeeting