15:04:43 #startmeeting fedora_cloud_meeting 15:04:43 Meeting started Thu Mar 17 15:04:43 2022 UTC. 15:04:43 This meeting is logged and archived in a public location. 15:04:43 The chair is davdunc. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 15:04:43 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:04:43 The meeting name has been set to 'fedora_cloud_meeting' 15:05:02 #topic roll_call 15:06:16 * mhayden waves 15:06:20 👋🏻 15:06:38 hey mhayden do you have a conflict? are you joining today? 15:07:14 i'm here for this meeting at least. my calendar has been double-booked a lot this week but not right now (please don't tell anyone) 😉 15:07:37 haha. it won't go out in the notes. Promise! 15:07:44 🤭 15:07:48 #chair mhayden 15:07:48 Current chairs: davdunc mhayden 15:08:14 I am between laptops today, spilled tea on one and sparks came out of the other. 15:09:24 ugh, no improvement there yet? 15:09:46 I got a Mac from work. It's not a laptop to me yet. 15:10:17 so I am with you today from an old XPS 15 running Silverblue. 15:10:23 could be a lot worse. 15:12:05 .hello ngompa 15:12:06 Eighth_Doctor: ngompa 'Neal Gompa' 15:12:10 haha, i just switched my personal laptop to silverblue last night 15:12:16 #chair ngompa 15:12:16 Current chairs: davdunc mhayden ngompa 15:12:22 awesome. 15:12:24 okay. 15:12:32 I don't think that makes me a char? 15:12:34 *chair 15:12:41 my IRC nick is Eighth_Doctor 15:12:50 #topic Action Items 15:13:00 #chair Eighth_Doctor 15:13:00 Current chairs: Eighth_Doctor davdunc mhayden ngompa 15:13:24 all good. we can have as many aliases as you need to participate in their Eighth_Doctor 15:13:35 :D 15:14:36 okay. we have a lot of things on the action list here, but none from last meeting, I suppose. 15:14:52 not sure what that's about. I think zodbot must have let me donw. 15:14:54 down* 15:15:07 ah. 15:15:19 first one: davdunc to add c7g instance types to AWS testing 15:15:58 That's been updated for access through an account in the partner engineering team at RH. 15:16:26 second one: davdunc to add status update to fcos ticket on kernel bug for xen instance types is completed. 15:16:41 That one is a big one. 15:17:20 jforbes is carrying a revert patch to the kernel while we wait for Amazon EC2 to update the Xen versions from 4.2 to 4.11 15:17:41 completed and waiting for the ec2 team to tell us that the status is complete. 15:18:55 Someone needs to test 5.17 during test week just to make sure I didn't forget the revert there. Since it is another branch of os-build, and I am not willing to do the revert in os-build 15:19:10 #topic Issue:365 Please publish AWS aarch64 AMI for Fedora 35 15:19:11 They gave and estimate of 12 weeks, which will be after the 5.17 rebase 15:19:28 jforbes: thanks. 15:20:26 jforbes: we don't use os-build in the fedora cloud group, but we can track it with you and help make sure it's complete. 15:21:09 #action davdunc to track the 5.17 rebase and verify os-build is functional with ELN. 15:22:12 I think you're confusing os-build and osbuild 15:22:18 oh. 15:22:22 yes I am. 15:22:35 os-build is the branch in the fedora kernel source tree in the CKI project 15:22:36 .hi 15:22:37 dustymabe: dustymabe 'Dusty Mabe' 15:22:43 thanks Eighth_Doctor thanks. 15:22:48 #chair dustymabe 15:22:48 Current chairs: Eighth_Doctor davdunc dustymabe mhayden ngompa 15:22:53 osbuild is a tool that we're not using :) 15:23:08 thanks for clarifying Eighth_Doctor 15:23:20 so we _do_ use it and we will be testing with the kernel. 15:23:36 Action remains the same. 15:23:57 yup, just not the way you originally expected :) 15:24:04 haha. 15:24:58 still need to test the ELN builds for cloud too. 15:25:00 jforbes: i tested yesterday (since I had a need for something) a revert against 5.17 rc8 15:25:35 unfortunately it's not a clean revert this time since some other code changed, but some manual inspection I was able to copy/paste the appropriate line to the right place and confirm the "revert" still works in latest 5.17 15:25:48 ugh! 15:26:00 thanks for handling this jforbes 15:27:20 I know this is extra work for you. Hopefully this will be resolved quickly - I'll let the Amazon kernel team know that this is getting increasingly complex. 15:27:56 Anyone else have anything they want to add while we have jforbes attention? 15:28:21 okay. 15:28:26 davdunc: regarding c7g instance types - is that something new? 15:28:43 should we enable them in our community account and add an FCOS test for it? 15:28:57 dustymabe: c7g is a new instance type. It's in preview. There is a way to test them for FCOS, yes. 15:29:34 does the account need special permission or are they just available? 15:29:48 dustymabe: talk to tumeya@ the AWS PEM. He can set you up with the account access for preview. 15:30:08 actually... I'll start a thread with you and him. 15:30:26 +1 - and you should have the account ID already? 15:30:40 dustymabe: we'll have to use a different account id. 15:30:55 I do have something to ask about Fedora on AWS in general if I could? 15:30:58 you'll need to add the account to the jenkins config. 15:31:05 Eighth_Doctor: shoot. 15:31:07 we need a separate account? 15:31:38 dustymabe: no... nothing you have to create. You just need access to a specific test account where the preview access is provided. 15:31:58 davdunc: I've heard from a developer that it's difficult to ensure they're using the latest Fedora content like they can for some others because there's some kind of alias thing you can use instead of having to pick the exact AMI 15:31:58 so IAM credentials for the test. 15:32:02 and Fedora doesn't have that 15:32:10 hmm - yeah we (FCOS) might hold off then til it's out of preview 15:32:12 can we get that sort of thing set up for Fedora AMIs? 15:32:34 Eighth_Doctor: it is something we can set up, yes. There are details on this. 15:32:41 img-mash supports it. 15:32:42 I'm not sure what the terminology is for what he's talking about, I heard ARN but I'm not sure that's right 15:32:52 AMI Public Parameters. 15:32:52 sweet 15:33:17 okay. that brings us full circle to the topic I actually set. ;) 15:33:34 #link https://pagure.io/cloud-sig/issue/365 15:34:50 the publication through our current deployment methods are not working with Azure, Google, nor are they working for the aarch64 images in EC2. 15:35:08 ehh. IIUC they should work fine for aarch64 AWS images 15:35:09 so we need to incorporated img-mash as soon as possible. 15:35:19 dustymabe: they did. 15:35:24 what changed? 15:36:20 obudai updated the infra ticket, but I can't find it right away. 15:36:34 got ya, yeah link me to it when you find it 15:36:51 mohan also asked that we move on to get away from Python 2.7 15:37:05 That seems more than reasonable. 15:38:02 so we decided earlier to move to img-mash for now, while osbuild (the tool) does not support the partitioning requirements me have. 15:38:13 we* have. 15:39:07 Eighth_Doctor: can you link that issue from the osbuild request? 15:39:16 yes, one sec 15:39:19 thanks. 15:39:48 #link https://github.com/osbuild/osbuild/issues/517 15:40:06 that actually dovetails nicely into something I wanted to (lightly) bring up 15:40:06 but img-mash has all of the bases covered as it supports all of the public clouds and integrates well with koji. 15:40:37 kiwi is the build tool 15:40:41 img-mash is the upload tool 15:40:46 sorry right. 15:41:12 I've started writing kiwi descriptions for CentOS Hyperscale, and have an initial draft PR up for that: https://pagure.io/centos-sig-hyperscale/kiwi-descriptions/pull-request/1 15:41:40 that will feed into making the initial Fedora Cloud kiwi descriptions as I feel out how everything should work 15:41:50 the img-mash is something that we can gate well. The actual build (and osbuild replacement) is the kiwi tool. The img-mash gives us the hybrid support we need for consistent uploads and we can deploy it to infra. 15:42:00 yeah 15:42:27 #link https://github.com/SUSE-Enceladus/mash 15:42:38 #link https://github.com/SUSE-Enceladus/mash-client 15:43:20 and related: img-proof for simple testing in the public cloud 15:43:23 #link https://github.com/SUSE-Enceladus/img-proof 15:43:43 the stuff that mhayden has done to bring in cloud provider Python SDKs is a major boon here 15:43:54 so the actual request is to build with kiwi from koji, then we can test with a combination of img-proof and hopefully we can incorporate avocado for testing before we update the images in each location with img-mash 15:44:02 thanks! still working on those but got 6-7 more in last week 15:44:23 yeah, that's the strategy, davdunc 15:44:31 mhayden: it's greatly appreciated :D 15:44:38 yea. I am still working on the awscli, but I have been CVE'ed to death this past couple of weeks. 15:44:59 mhayden: that's amazing work you are doing there. 15:45:27 okay. 15:45:46 #action davdunc to package img-mash for the uploads 15:46:01 awesome 15:46:05 this went on my todo list a couple weeks back. 15:46:15 that's the first step in my opinion. 15:46:28 yup 15:47:26 after that, we can plumb it in to replace our uploader 15:47:31 fedimg 15:47:57 yup 15:48:06 once that is completed, we can integrate kiwi, which Eighth_Doctor has already packaged... thank you very much! 15:48:13 :D 15:48:48 and then we can add the img-proof and avocado testing for validations and QA 15:48:55 yep 15:48:59 super. 15:49:14 and I think that covers the plan. 15:49:21 Any questions or concerns? 15:50:23 okay. In addition to the standard image uploads, I am expecting that we will also publish the ELN to the public clouds as well. 15:51:14 any objections there? I think this is what the cloud WG should be doing too, facilitating the efforts of those who don't care to be expert in cloud instances. 15:51:27 yeah I think that makes sense 15:52:00 awesome. I am going to update the ticket with that plan of action. 15:52:47 #topic F36 release readiness 15:53:08 #link https://fedoraproject.org/wiki/Cloud/Release_Checklist 15:53:28 I am going to add to this list later today. 15:54:10 I want to get out a blog post this weekend on what new components are relevant to the cloud base. 15:54:39 cloud-init is in there. what else is topic worthy? 15:54:47 Network Manager? 15:55:04 (we'll get to vagrant in a minute) 15:55:07 davdunc: specifically with regards to f36? 15:55:10 yes. 15:55:23 there's the UEFI thing but I don't think that is f36 15:55:45 UEFI thing? 15:55:50 we've been hybrid boot since F35 15:56:26 that's f35, but worth discussion. 15:56:53 Eighth_Doctor: UEFI by default 15:57:04 F37 we should probably go full UEFI. 15:57:06 i.e. pushing other components in the stack to default to it 15:57:30 I think it's a bit radical, but I'd like to at least pursue that. 15:58:12 if we went to uefi by default, mostly it wouldn't cause too much harm for current versions of Xen even. 15:58:35 we would be leaving behind some legacy deployments though. 15:58:43 that's why it's called "default" 15:59:34 pjones: if only there was support for polyglot boot everywhere, we could just let the images do their own thing. 15:59:43 we should at least do a Change to "officially" deprecate it 15:59:53 even if we don't basically nothing to the image 16:00:08 at least in EC2, you have to register them to boot classic or UEFI and there is no default. 16:00:24 we'll probably start registering AMIs to boot UEFI 16:00:25 davdunc: that's a thing you could do to the images without any downside other than a few megabytes. 16:00:37 pjones: we did it in F35 16:00:42 okay so.... 16:01:10 so now we want to officially register them as UEFI and that will leave behind ~100 instance types in EC2. 16:02:01 but I personally don't see that as a concern as it is the bottom 25% in terms of popularity and price. 16:02:45 okay. I think we can wind that down. let's keep chatting on that in #fedora-cloud 16:02:57 #topic Open Floor 16:03:08 I want to bring up the vagrant image issue 16:03:15 are we setting this meeting against US/Eastern or UTC? 16:03:24 iirc we should be on US/Eastern 16:03:41 US/Eastern, I thought. 16:03:57 the FPC meeting is also set to US/Eastern and so we wound up having a collision today, so someone is not on Eastern when they should be 16:04:11 I see. 16:04:33 we should figure that out later and make sure we're coordinated on that 16:04:38 okay. 16:04:44 we'll add it to the technical document. 16:05:40 alright then. we are over time. I'll call this meeting and we will work on list and in chat. 16:05:45 Thanks everyone. 16:05:53 #end_meeting 16:06:18 #endmeeting