18:00:00 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:00 Meeting started Mon Jun 28 18:00:00 2021 UTC. 18:00:00 This meeting is logged and archived in a public location. 18:00:00 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:00 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:00 #chair mboddu nirik pingou mobrien nb 18:00:00 Current chairs: mboddu mobrien nb nirik pingou 18:00:00 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:00 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:00 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:01 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:01 #info reminder: speak up if you want to work on a ticket! 18:00:03 #topic Tickets needing review 18:00:05 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:08 Hello 18:01:39 morning 18:02:07 Morning nirik 18:02:47 .ticket 10058 18:02:48 nirik: Issue #10058: Help with removing survey banner to hyperkitty lists - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10058 18:03:05 low/low/ops and someone needs to do it then? 18:03:09 +1 18:03:52 Done 18:04:18 .ticket 10059 18:04:19 nirik: Issue #10059: Add a group as an owner of a package - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10059 18:04:28 waiting on reporter, low low ops? 18:04:40 +1 18:04:59 Done 18:05:56 .ticket 10062 18:05:58 nirik: Issue #10062: My account does not appear at fedorapeople.org and my blog is not in planet fedora - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10062 18:06:19 * nirik checks to see if they are in a group 18:06:46 they are 18:07:07 low low ops and needs some debugging I guess. 18:07:49 Okay 18:08:05 thats it for infra, releng? 18:08:13 Yeah, just one unretirement ticket 18:08:22 .releng 10183 18:08:24 mboddu: Issue #10183: Unretire rpms/irqbalance - releng - Pagure.io - https://pagure.io/releng/issue/10183 18:08:28 low, low, ops? 18:09:28 +1 18:09:58 That is all 18:11:06 nirik, I might have some more questions about some old tickets, is this a good place? :) 18:11:25 asaleh: sure! or hit me up directly, happy to answer. 18:11:32 .ticket 9692 18:11:33 asaleh: Issue #9692: STG: Move bvmhosts to new server - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9692 18:11:58 vmhost-x86-12.stg is down and needs onsite to bring back (we asked for it last visit, but they never got to it). 18:12:12 but vmhost-x86-11.stg is up and things could be moved to it. 18:12:38 nirik, ok, I made a comment about that on 9691 18:12:58 oh, this is the bvmhost version. 18:13:06 but with the 9692, it says "We have 1 new bvmhost and 1 old one which can be deployed for either new systems or to spread the load out over from the existing bvmhosts." 18:13:09 bvmhost -> build side, vmhost -> non build side 18:14:06 ok, so the new ones are: 18:14:12 yes, mobrien explained that to me, but the ticket is so sparse we didn't really know what do we mean with 'new' :) 18:14:45 yeah, so I can answer here, or should I update the ticket? or both? :) 18:16:33 just answer here and I figure out the ticket with Mark :) ... and I can ask followup questions :D 18:17:28 added to ticket, pasting here: 18:17:36 Existing bvmhost-x86: 18:17:36 bvmhost-x86-01.stg.iad2.fedoraproject.org 18:17:36 bvmhost-x86-02.stg.iad2.fedoraproject.org 18:17:36 bvmhost-x86-03.stg.iad2.fedoraproject.org 18:17:36 New bvmhost-x86: 18:17:37 bvmhost-x86-04.stg.iad2.fedoraproject.org 18:17:39 bvmhost-x86-05.stg.iad2.fedoraproject.org 18:17:41 There's 2 methods to do this: 18:17:43 either: 18:17:45 Destroy the old vm and adjust ansible and re-run playbook to recreate it. 18:17:49 or 18:17:51 migrate the existing vm and then adjust ansible so it's correct. 18:18:27 oh, and you can see whats on what host by looking in ansible or /var/log/virthost-lists.out on batcave01 18:19:13 bvmhost-x86-04.stg is older repurposed machine, so moving to bvmhost-x86-05.stg first might be best 18:19:21 does all that make sense? 18:20:26 ok, so really simmilar in spirit to the previous one, just we have no intention to then destroy any of the old bvmhosts, just spread the load better 18:21:14 we likely will retire the oldest hardware at some point... 18:21:25 so move entirely off the oldest stuff 18:23:01 added stats about whats 'oldest' to the tickets. 18:23:28 For my own curiosity, are our hypervisors RHEV, or are they just running KVM and using Virtual Machine manager as a GUI, like I have at home? 18:23:52 they are just using libvirt/kvm... 18:23:53 * mboddu got to go, need to reboot (hopefully it will) and then grab lunch before the FESCo meeting, also I have nothing else to report, thanks nirik 18:23:57 ansible manages the installs, etc 18:24:15 Excellent. I was curious. 18:24:26 asaleh: any others for now? 18:24:53 and many thanks for poking at the older tickets. Much appreciated! :) 18:25:50 nirik, there was one more about replacing a hdd, but I lost the number 18:25:54 maybe 18:26:07 I should update that one. I know the one you mean. 18:26:28 .ticket 9547 18:26:29 asaleh: Issue #9547: IAD2: bvmhost-a64-10 needs disk replacement - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9547 18:26:30 * nirik sometimes is bad about updating tickets like that where it's all internal back and forth 18:28:00 After tons of back and forth and games of telephone and email we found that we do in fact have a warnetee on these machines (which is 'parts only'). 18:28:00 A drive has been shipped to RHIT and on the next site vist they will hopefully install the drive and we can bring the machine back to life. :) 18:28:02 n.p. tickets that you can just close because they have been done are best (tickets that you need to update once a month because 'waiting on external' are not so good, but we can live with those as well) 18:28:08 * nirik updated the ticket with that too. 18:28:23 nirik, awesome! 18:28:26 nirik++ 18:28:26 asaleh: Karma for kevin changed to 39 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:28:33 asaleh++ 18:28:33 nirik: Karma for asaleh changed to 3 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:28:37 thanks for poking those. ;) 18:28:54 ok, if nothing else, lets close out... 18:29:04 +1 18:29:41 #endmeeting