16:02:37 #startmeeting fedora_cloud_meeting 16:02:38 Meeting started Tue Dec 8 16:02:37 2020 UTC. 16:02:38 This meeting is logged and archived in a public location. 16:02:38 The chair is dustymabe. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:38 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:02:38 The meeting name has been set to 'fedora_cloud_meeting' 16:02:42 #topic roll call 16:02:45 .helo2 16:02:53 .hello2 16:02:54 cyberpear: cyberpear 'James Cassell' 16:02:58 .hello2 16:02:59 roshi: roshi 'Mike Ruckman' 16:03:00 .hello2 16:03:02 otubo: otubo 'Eduardo Otubo' 16:03:05 * King_InuYasha waves 16:03:08 .hello ngompa 16:03:09 King_InuYasha: ngompa 'Neal Gompa' 16:03:19 .hello davdunc 16:03:19 davdunc: davdunc 'David Duncan' 16:03:32 .hello2 16:03:33 jdoss: jdoss 'Joe Doss' 16:04:31 #chair cyberpear roshi otubo King_InuYasha davdunc jdoss 16:04:31 Current chairs: King_InuYasha cyberpear davdunc dustymabe jdoss otubo roshi 16:04:46 #topic Action items from last meeting 16:04:55 I don't see any action items from our last meeting 16:05:10 #topic OpenStack cloud image: include and enable qemu-guest-image 16:05:19 #link https://pagure.io/cloud-sig/issue/319 16:05:40 we got a request to add the qemu-guest-agent to our cloud image 16:05:53 looks like jdoss voiced some concern in the ticket 16:06:05 Is that just to add it or to start it for every provider? 16:06:33 I'm not totally sure. I'm not sure if you can just include it and not have it enabled 16:06:50 the systemd unit can be set to condition activation on kvm 16:06:51 * dustymabe vaguely remembers something about it being activated only if it would be useful for the machine 16:06:52 If it is just adding the package that isn't as bad as having a service running on GCP or AWS that is isn't needced. 16:07:14 jdoss: at least for GCP we can remove it from the package set, because we have a separate GCP image 16:07:45 King_InuYasha: that's good to know 16:07:50 The blanket add package and have the service running for everyone feels bad. 16:08:21 jdoss: yeah, assuming it's only activated when useful, then that would be a little more palatable? 16:08:48 I don't think it's a big package so ya that works to help them with their usecase. 16:09:09 they should be able to enable it via userdata or something? 16:10:04 King_InuYasha: is the condition you talk about part of the existing rpm? 16:10:10 or were you talking about doing something extra? 16:10:24 dustymabe: if it's not there now, we should add it 16:10:28 I think it already is, though 16:11:14 here's what I see: https://paste.centos.org/view/3aeedcad 16:12:04 so it does it indirectly? 16:12:15 but yeah, it doesn't have a virtualization condition 16:12:34 King_InuYasha: because of the 16:12:34 I think what that means is that if the device exists, it'll get started 16:12:42 BindsTo=dev-virtio\x2dports-org.qemu.guest_agent.0.device 16:12:44 After=dev-virtio\x2dports-org.qemu.guest_agent.0.device 16:12:54 That's how I am reading it. 16:12:56 yeah 16:13:04 I think we're fine to preload this unconditionally 16:13:10 got ya, ok 16:13:12 sounds like we just need to add the package and move on with our lives. 16:13:20 yup 16:13:22 WFM 16:13:28 on the EC2 side, that would be considered a lot of overhead on the instance. 16:13:32 maybe related: the cloud-init in openstack vs plain libvirt/qemu problem is annoying... otherwise, you could have the same image, I'd suppose... is it possible to have cloud-init be inert on plain qemu? (or have I just not tried it recently enough?) 16:13:54 davdunc: how so? 16:14:03 cyberpear: it looks like it will be inert on any system that doesn't have dev-virtio\x2dports-org.qemu.guest_agent.0.device 16:14:05 would that device be present and start this service? 16:14:11 on EC2? 16:14:21 interesting 16:14:30 jdoss, it would not, but it will affect boot time in the search. 16:15:31 a lot of overhead meaning a few MS to see if the dev is present or not? I can see what you are saying. 16:15:43 minimal, I know, but these add up. 16:15:46 ya for sure. 16:15:48 .hello2 16:15:50 michaelgugino: michaelgugino 'Michael Gugino' 16:15:55 It's a good point. 16:16:00 * jdoss waves at Michael 16:17:00 #proposed since the unit appears to be inert on any system that can't take advantage of the service, we propose to add qemu-guest-agent to the base package set. We won't include it on GCP since we have a separate image for GCP already. In the future we may make other images specific to cloud providers, in which case we'll also remove it from those variants. 16:17:43 @chair michaelgugino 16:17:46 dustymabe: +1 16:17:47 sigh 16:17:50 #chair michaelgugino 16:17:50 Current chairs: King_InuYasha cyberpear davdunc dustymabe jdoss michaelgugino otubo roshi 16:17:53 dustymabe: +1 16:18:43 +1 16:19:14 going once.. 16:19:27 hu 16:19:39 anybody else want to weigh in? 16:19:41 dustymabe: I arrived late 16:19:50 welcome danken 16:20:09 are you adjourning? 16:20:17 nope 16:20:23 we're in the middle of a topic 16:20:33 #agreed since the unit appears to be inert on any system that can't take advantage of the service, we propose to add qemu-guest-agent to the base package set. We won't include it on GCP since we have a separate image for GCP already. In the future we may make other images specific to cloud providers, in which case we'll also remove it from those variants. 16:21:33 #topic open floor 16:21:45 I don't think there are any other meeting tickets 16:22:08 anybody with anything for open floor? 16:23:32 oh, I almost forgot 16:23:36 * dustymabe checks calendar 16:23:56 a few clerical items 16:24:02 1. the next scheduled meeting is on the 22nd 16:24:29 I won't be around, and a lot of people will probably be AFK that time of year 16:25:03 2. I'm due to have a baby any time in the next 3 weeks. After that I won't be around for some time. 16:25:16 Anybody else want to volunteer to run meetings (or rotate running meetings) in the meantime? 16:26:39 I could run some meetings 16:29:16 sorry for my earlier noise. is this a good time to raise my request to enable qemu-guest-agent in the Fedora cloud image? 16:29:44 danken: :) 16:29:51 hmm 16:29:54 we already discussed it and agreed to include it 16:30:06 did you also already discussed our request for ipv6-by-default? 16:30:06 mostly because it appears to be inert on any nodes where it won't be useful 16:30:20 danken: we did not discuss that one, was there a ticket opened for it? 16:30:33 I believe so, lemee check 16:31:00 i may have missed it 16:31:20 ahh I see, will add the meeting label 16:31:27 https://pagure.io/cloud-sig/issue/320 16:32:02 #topic fedora cloud image: enable ipv6 (accept RAs by default) 16:32:08 #link https://pagure.io/cloud-sig/issue/320 16:32:27 It appears the network manager config in the cloud image sets `ipv6.method: ignore` 16:32:48 honestly we should probably just stop configuring the network at all and just let NM defaults apply 16:33:02 that sounds right. 16:33:27 anybody with any opinions here? 16:33:41 ... unless an NM default is later found to be buggy 16:34:09 can't hurt to build one for testing. 16:34:11 but to me - it would better be fixed in NM... 16:34:55 yeah we should be able to apply it to rawhide and we'll get an image for testing 16:35:06 danken: unfortunately we won't be able to update existing f33 images 16:35:11 davdunc: I'd love to consume a build with qemu-guest-agent and ipv6 and test it 16:35:18 we only do a new release on major Fedora releases right now 16:35:50 danken: what is your Fedora account nickname? is it mdbarroso ? 16:35:53 dustymabe: I see. 16:36:02 mine is danken... 16:36:29 but mdbarroso is in my team and should be CCed 16:37:29 #proposed we should/will remove networking configuration from the cloud images and let NetworkManager default configs apply, which should get us in a situation where ipv6 is no longer ignored. 16:37:57 +1 16:38:55 dustymabe: +1 16:39:14 dustymabe: +1 16:39:52 #agreed we should/will remove networking configuration from the cloud images and let NetworkManager default configs apply, which should get us in a situation where ipv6 is no longer ignored. 16:40:04 #topic open floor 16:40:17 anybody want to volunteer to run through making either of those two changes to the cloud base image? 16:41:08 dustymabe: I'd like to do it if I can get assistance from someone else, like @King_InuYasha 16:41:47 :D I need the experience. 16:42:38 davdunc: I can help you :) 16:42:48 dustymabe: awesome! 16:42:59 can you schedule some time (calendar invite) and I'll help you step through it? 16:43:09 will do. 16:43:32 #action davdunc to make changes to the cloud base image to include qemu-guest-agent and drop the networking configuration 16:43:42 anymore items for open floor? 16:46:22 michaelgugino: maybe we can get updates on the image uploading bits in the new year? 16:46:42 dustymabe: for sure, updates. I plan to hack on it soon. 16:47:03 King_InuYasha: any progress with ericedens on the packaging front? 16:47:32 also anyone want to volunteer to add the GCP links to the download page? https://pagure.io/cloud-sig/issue/314 16:48:03 dustymabe: never heard back from him 16:48:05 #info we have a PR open to rebase cloud-init to the new upstream version: https://src.fedoraproject.org/rpms/cloud-init/pull-request/11 16:48:33 King_InuYasha: I have a meeting with him later today (if he's not out). Want me to add you ? 16:48:46 sure 16:48:52 depending on the time 16:48:56 after 2pm 16:49:00 (EST) 16:49:15 starts at 2pm, is that OK 16:51:05 ok I'll close out the meeting and coordinate with King_InuYasha outside of this 16:51:07 #endmeeting