18:59:42 #startmeeting 18:59:42 Meeting started Thu Jun 11 18:59:42 2020 UTC. The chair is rvandegrift. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:59:42 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:59:48 hi all 18:59:51 hello! 19:00:47 first item on the agenda: stretch and lts. Noah is planning to keep building ec2 images, what do others think? 19:02:05 azure will go on as well 19:02:42 At least based on the marketplace listings, stretch still seems more popular than buster on ec2. 19:03:17 But those metrics don't reflect usage of the AMIs listed on the wiki 19:04:34 zigo's list message made it sounded positive for the openstack images too 19:04:46 hi all 19:04:46 for azure we don't have any numbers. i could check the mirrors 19:04:57 i could also do some digging on the azure side 19:05:08 i should be able to pull those numbers for stretch 19:05:39 any of the gce folks around? if not, I can follow up to ask them 19:06:13 I doubt there's anything really meaningful in these metrics, I just find it curious that stretch is still so popular. 19:06:24 ...And people complain that debian stable is so "stale" 19:07:19 would be interesting stats for sure 19:07:55 #action rvandegrift follows up with gce folks to find out their position on lts for stretch 19:08:05 noahm: don't ask. 5 years of support are clearly not enough 19:08:21 GCP is not using yet what we produce and default img is buster already 19:08:35 by what we produce I mean FAI 19:10:11 kuLa: I think they are - a buster vm I just started yesterday has fai logs 19:10:51 kuLa: they do, but they don't use our toolset around it 19:10:57 oooh that would be interesting that I missed it somehow but it's a good news 19:11:15 thx for the info guys 19:11:19 so if everyone agrees that they'll do stretch lts images, do we need to announce anything? or just keep publishing 19:11:23 either way, they are producing the images, not us. So they can keep doing what they're doing regardless of our decisions. 19:11:32 true 19:12:28 rvandegrift: probably no need for an announcement, but I may update the Marketplace listing in EC2 once LTS support starts. 19:12:30 rvandegrift: just keep publishing. and maybe add the end-of-support date to the description 19:13:36 sounds good. any other lts issues? 19:14:38 well, there's still jessie. not sure what to do there. 19:14:47 It hasn't been updated in ... ages. At least on ec2. 19:15:05 But, we can ignore that for a little longer. No need to discuss here. 19:15:50 okay, sounds good 19:16:51 next agenda item: cloud-init updates for stable 19:18:13 noahm's email reports that release managers are onboard, but want some additional testing - what platforms have been tested and which remain? 19:18:28 i've been doing extensive testing on azure 19:18:49 chillysurfer: do you have a specific test suite, or are you doing ad-hoc testing? 19:18:54 i've ported the cloud-init upstream sru testing to debian with good success 19:19:05 noahm: mostly adhoc testing, but i've adopted upstream's sru testing 19:19:23 so in other words, upstream signs off based on those tests, they're good enough for me 19:19:26 (at the moment) 19:19:35 ... signs off based on those tests on ubuntu, that is.. 19:19:42 I've done a little testing on ec2. Nothing comprehensive, but I can prioritize that and get to it in the next week or so. 19:19:55 We need thorough testing on openstack. 19:20:00 #info azure test results at https://salsa.debian.org/trstringer/azure-debian/-/tree/master/ 19:20:42 it would be nice to standardize this though so we don't have different clouds having different levels of testing 19:21:09 yup 19:21:20 unfortunately my scripts as of right now have a lot of azure-isms in it 19:22:39 these scripts? https://salsa.debian.org/trstringer/azure-debian/-/blob/master/buster/sru_validate_debian_debian-10_10_0.20200511.260_with_cloud-init_20.2-2_bp.sh 19:23:11 noahm: yeah exactly. sru_*.sh are the ones i ported from upstream 19:23:47 ok. mostly looks like the az* calls handle launching and sshing to the instance, right? Should be easy enough to port. 19:24:02 But that looks like a good start for something cross-cloud. 19:24:41 yeah all of those az_* are wrappers. i think az_vm_ssh is mostly what i used, which was just a wrapper around me doing an ssh proxy jump to destination vms 19:25:22 but those could be replaced with ssh calls 19:26:10 #info chillysurfer's cloud-init test script: https://salsa.debian.org/trstringer/azure-debian/-/blob/master/buster/sru_validate_debian_debian-10_10_0.20200511.260_with_cloud-init_20.2-2_bp.sh 19:26:48 I will post details of EC2 testing to the mailing list within the next week. 19:26:51 Who can test openstack? 19:27:59 I think zigo mention some tests, but I can't find it on the list. I'll send him a note to find out 19:28:14 #action rvandegrift follow up on cloud-init update testing on openstack 19:28:39 rvandegrift: thanks 19:28:40 any other items related to cloud-init stable update? 19:32:09 next item: we had some discussion about delegations. we can talk about that here. but I propose to wait until we have a (probably online) sprint 19:32:30 imo, it isn't pressing - but if folks disagree, that's okay too 19:32:52 has there been any planning on the next sprint? 19:33:31 nothing formal - I've been thinking about ways we might do it without travel, assuming that still looks bad in the fall 19:34:01 I don't have anything to contribute to the delegates discussion beyond what's been on the mailing list. 19:34:55 we can try jitsi.debian.social for a remote sprint. 19:36:08 no one is rushing to object, so we'll skip further delegation discussions for now 19:37:02 that's the end of my agenda - does anyone have other items to discuss? 19:38:23 zigo wnted to have something 19:38:43 yeah but I don't think he managed to join 19:38:55 I still want to come up with a real plan for keeping the buster (stable) FAI configuration isolated from the unstable/testing configuration, but I'm not prepared to talk about it right now. 19:40:23 ah yes - zigo wanted to talk about rescue images, but it seems like an initial agreement was reached. we can wait for him to follow up since he didn't make it 19:41:35 I think we're done for today, thanks everyone. next meeting will be July 7 at the same time 19:41:55 #endmeeting