18:00:00 <nirik> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:00 <zodbot> Meeting started Mon Jun 28 18:00:00 2021 UTC. 18:00:00 <zodbot> This meeting is logged and archived in a public location. 18:00:00 <zodbot> The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:00 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:00 <nirik> #chair mboddu nirik pingou mobrien nb 18:00:00 <zodbot> Current chairs: mboddu mobrien nb nirik pingou 18:00:00 <nirik> #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:00 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:00 <nirik> #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:01 <nirik> #info agenda is at https://board.net/p/fedora-infra-daily 18:00:01 <nirik> #info reminder: speak up if you want to work on a ticket! 18:00:03 <nirik> #topic Tickets needing review 18:00:05 <nirik> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:08 <mboddu> Hello 18:01:39 <nirik> morning 18:02:07 <mboddu> Morning nirik 18:02:47 <nirik> .ticket 10058 18:02:48 <zodbot> 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 <nirik> low/low/ops and someone needs to do it then? 18:03:09 <mboddu> +1 18:03:52 <mboddu> Done 18:04:18 <nirik> .ticket 10059 18:04:19 <zodbot> 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 <nirik> waiting on reporter, low low ops? 18:04:40 <mboddu> +1 18:04:59 <mboddu> Done 18:05:56 <nirik> .ticket 10062 18:05:58 <zodbot> 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 <nirik> they are 18:07:07 <nirik> low low ops and needs some debugging I guess. 18:07:49 <mboddu> Okay 18:08:05 <nirik> thats it for infra, releng? 18:08:13 <mboddu> Yeah, just one unretirement ticket 18:08:22 <mboddu> .releng 10183 18:08:24 <zodbot> mboddu: Issue #10183: Unretire rpms/irqbalance - releng - Pagure.io - https://pagure.io/releng/issue/10183 18:08:28 <mboddu> low, low, ops? 18:09:28 <nirik> +1 18:09:58 <mboddu> That is all 18:11:06 <asaleh> nirik, I might have some more questions about some old tickets, is this a good place? :) 18:11:25 <nirik> asaleh: sure! or hit me up directly, happy to answer. 18:11:32 <asaleh> .ticket 9692 18:11:33 <zodbot> asaleh: Issue #9692: STG: Move bvmhosts to new server - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9692 18:11:58 <nirik> 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 <nirik> but vmhost-x86-11.stg is up and things could be moved to it. 18:12:38 <asaleh> nirik, ok, I made a comment about that on 9691 18:12:58 <nirik> oh, this is the bvmhost version. 18:13:06 <asaleh> 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 <nirik> bvmhost -> build side, vmhost -> non build side 18:14:06 <nirik> ok, so the new ones are: 18:14:12 <asaleh> 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 <nirik> yeah, so I can answer here, or should I update the ticket? or both? :) 18:16:33 <asaleh> just answer here and I figure out the ticket with Mark :) ... and I can ask followup questions :D 18:17:28 <nirik> added to ticket, pasting here: 18:17:36 <nirik> Existing bvmhost-x86: 18:17:36 <nirik> bvmhost-x86-01.stg.iad2.fedoraproject.org 18:17:36 <nirik> bvmhost-x86-02.stg.iad2.fedoraproject.org 18:17:36 <nirik> bvmhost-x86-03.stg.iad2.fedoraproject.org 18:17:36 <nirik> New bvmhost-x86: 18:17:37 <nirik> bvmhost-x86-04.stg.iad2.fedoraproject.org 18:17:39 <nirik> bvmhost-x86-05.stg.iad2.fedoraproject.org 18:17:41 <nirik> There's 2 methods to do this: 18:17:43 <nirik> either: 18:17:45 <nirik> Destroy the old vm and adjust ansible and re-run playbook to recreate it. 18:17:49 <nirik> or 18:17:51 <nirik> migrate the existing vm and then adjust ansible so it's correct. 18:18:27 <nirik> oh, and you can see whats on what host by looking in ansible or /var/log/virthost-lists.out on batcave01 18:19:13 <nirik> bvmhost-x86-04.stg is older repurposed machine, so moving to bvmhost-x86-05.stg first might be best 18:19:21 <nirik> does all that make sense? 18:20:26 <asaleh> 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 <nirik> we likely will retire the oldest hardware at some point... 18:21:25 <nirik> so move entirely off the oldest stuff 18:23:01 <nirik> added stats about whats 'oldest' to the tickets. 18:23:28 <eddiejennings> 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 <nirik> 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 <nirik> ansible manages the installs, etc 18:24:15 <eddiejennings> Excellent. I was curious. 18:24:26 <nirik> asaleh: any others for now? 18:24:53 <nirik> and many thanks for poking at the older tickets. Much appreciated! :) 18:25:50 <asaleh> nirik, there was one more about replacing a hdd, but I lost the number 18:25:54 <asaleh> maybe 18:26:07 <nirik> I should update that one. I know the one you mean. 18:26:28 <asaleh> .ticket 9547 18:26:29 <zodbot> 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 <nirik> 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 <nirik> 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 <asaleh> 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 <asaleh> nirik, awesome! 18:28:26 <asaleh> nirik++ 18:28:26 <zodbot> asaleh: Karma for kevin changed to 39 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:28:33 <nirik> asaleh++ 18:28:33 <zodbot> nirik: Karma for asaleh changed to 3 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:28:37 <nirik> thanks for poking those. ;) 18:28:54 <nirik> ok, if nothing else, lets close out... 18:29:04 <eddiejennings> +1 18:29:41 <nirik> #endmeeting