18:03:50 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:03:50 Meeting started Tue Jun 20 18:03:50 2023 UTC. 18:03:50 This meeting is logged and archived in a public location. 18:03:50 The chair is nirik. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:03:50 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:03:50 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:03:56 #chair nirik nb smooge phsmoura 18:03:56 Current chairs: nb nirik phsmoura smooge 18:03:59 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:03:59 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:04:04 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:04:08 #info agenda is at https://board.net/p/fedora-infra-daily 18:04:12 #info reminder: speak up if you want to work on a ticket! 18:04:20 #topic Tickets needing review 18:04:25 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:04:50 .ticket 11373 18:04:51 nirik: Issue #11373: Requesting resources for Multimedia SIG - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/11373 18:05:00 low low ops. just needs doing 18:05:31 .ticket 11374 18:05:32 nirik: Issue #11374: ppc64le build died with No space left on device - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/11374 18:05:41 hello. Sorry Im late, got disconnected 18:05:45 This is a weird one... needs more investigation. I haven't had a chance yet. 18:05:53 no worries. :) 18:06:16 med med ops. 18:06:25 .ticket 11375 18:06:26 nirik: Issue #11375: fedora-messaging staging is broken(?) - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/11375 18:06:34 here 18:06:38 I looked at this a little, but not sure whats going on. 18:06:42 med med ops I guess? 18:06:56 +1 18:07:04 +1 18:07:40 2 releng ones... 18:07:48 .releng 11492 18:07:49 nirik: Issue #11492: F39 System-wide change: Drop libuser - releng - Pagure.io - https://pagure.io/releng/issue/11492 18:08:13 I think this has no releng impact. will close it thanking them 18:08:44 .releng 11493 18:08:45 nirik: Issue #11493: Unretire qxmpp - releng - Pagure.io - https://pagure.io/releng/issue/11493 18:08:48 low low ops 18:09:14 #topic work plans / upcoming tasks 18:09:55 I'm considering switching batcave01 to rhel9 on thursday afternoon. Will look at it more today and decide. If so, I guess I'll file an outage about it. 18:10:05 sounds good 18:10:26 Otherwise, my todo list is long. ;) Lots to do... 18:10:42 Nothing new here. Keep testing dnf count me, getting close to the end I guess 18:10:59 cool. How is it all looking? 18:12:04 good. Im having trouble to test one of the functions, but its progressing 18:12:15 glad to hear it. 18:12:25 o/ still looking on awx/aap, and wondering what are the next step? can we consider deploying it on stg and is there anything I can do to help on that regards? 18:12:27 ok, I don't know that I had much else... 18:13:20 me neither 18:14:32 darknao: I suppose we could... but since we have no seperate stg ansible setup, seems a bit odd. I guess it would let us test things/integrate. 18:14:55 or we can yolo it and deploy on prod directly 18:15:01 So, I guess we need to install the operator, then push ansible changes to configure it? or ? 18:15:23 would it be possible to run a set of .dev.fedoraproject.org systems in the cloud that the awx configured? 18:15:26 yeah, I was kinda thinking that, since we don't have to move to it until we want, prod makes a bit more sense 18:15:51 we could set it up with access to whatever set of things we want. 18:16:25 yes, the operator first, then we can use ansible to configure ansible if we want to 18:16:42 ok I didn't know if that would make things easier or harder so it was more a 'hmmm' question to get feedback on 18:16:43 we will need to make a choice beetween AAP or AWX 18:17:09 * nirik is reminded of our openshift3 install setup... we had ansible-openshift-ansible 18:17:55 I'm not fully sure of the tradeoffs/pros/cons... I'd prefer AWX since its completely open, but if it has limitations we don't want I could be talked into AAP 18:17:58 darknao, which one would you prefer AWX or AAP 18:19:17 nirik, from my testing AWX is just a more upstream version of AAP not a lot of functionality differences just moves more quicker then AAP 18:19:19 features wide, it's pretty much the same. AWX is a little bit easier to deploy as you don't need subscription. AAP require subscription to use it (this is one of the rare RH software that actually require subscription to use the product) 18:19:54 darknao, I have managed both so able to help out with this 18:19:58 and if we set up a execution node (batcomputer01) we need access to the automation-platform repository 18:20:08 Then probibly in the spirit of upstream first I'd suggest we try AWX first and if it provides too much pain, we can move back to AAP... 18:21:37 +1 18:21:55 I have a awx instance running with the operator for more than 2 years, and never had any issues with upgrades or anything 18:22:16 cool. 18:22:42 to me, this is as stable as AAP, at least for my use case 18:23:00 darknao: so I can install the operator... can you then do an ansible pr to configure ? or perhaps we need to discuss config options? 18:24:19 we'll also need an API key from AWX to configure it with ansible 18:24:59 but yeah, I guess we need to figure out how we want to configure it first 18:25:39 How about this (since we are getting to the end of this standup): I'll file a ticket on it and we can sort our steps or questions there? 18:25:58 sounds good to me 18:25:59 nirik, +1 to the ticket 18:26:06 ok. I assume that can be generated on install/configure? I guess I should go look at the docs on it... 18:27:40 what does AWX actually stand for ? :) 18:27:51 yeah I think the operator create a secret key on install, but not sure.. I usually create one linked to my user myself 18:27:59 Ansible Web eXecution? 18:28:25 anyhow. I will file that ticket and help as I can moving things forward at least to where we can play around with it. ;) 18:28:31 Anything else from anyone? 18:28:36 im good 18:30:17 Thanks everyone! 18:30:17 #endmeeting