14:06:35 #startmeeting kolla 14:06:35 Meeting started Wed Nov 2 14:06:35 2022 UTC and is due to finish in 60 minutes. The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:06:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:06:35 The meeting name has been set to 'kolla' 14:06:40 #topic rollcall 14:06:41 o/ 14:07:36 \o 14:08:08 kevko, mgoddard, hrw 14:08:24 O/ 14:08:32 \o 14:08:37 o/ 14:10:22 \o 14:12:32 #topic agenda 14:12:32 * CI status 14:12:32 * Release tasks 14:12:32 * Regular stable releases (first meeting in a month) 14:12:32 * Current cycle planning 14:12:33 * Additional agenda (from whiteboard) 14:12:33 * Open discussion 14:12:37 #topic CI status 14:12:58 whiteboard says green 14:13:22 I haven't seen any spectacular failures today, so let's assume it is 14:13:35 #topic Regular stable releases (first meeting in a month) 14:13:53 I think Wallaby went EM, so no more stable releases there 14:14:14 did we have a final release? 14:15:27 hmm, seems not since 6th Oct 14:16:01 I'll speak with the release team later if we can still do that - I was pretty sure we did 14:16:26 Argh, I missed one topic 14:16:35 #topic Release tasks 14:16:48 We can't branch yet, still kolla/kolla-ansible/kayobe needs opensearch 14:17:15 #topic Current cycle planning 14:17:34 what about other stable branch releases? 14:17:44 I can create a patch unless someone else wants to 14:17:52 Ah right, we should do other stable branch releases as we do every month 14:18:47 ok, so I'll do that 14:18:51 thanks 14:19:02 Ok, so current cycle for us is still Zed 14:19:21 We have opensearch to review and test - I'll try to do that this week 14:19:30 There's skyline that probably could get in 14:19:38 And the systemd patch in kolla-ansible 14:19:59 Anyone willing to review skyline or systemd patch thoroughly? 14:20:18 I will do skyline, but no timeline yet 14:22:09 ok then 14:22:17 systemd also waiting for somebody :) 14:22:37 I'll try to review all of them, but surely not everything at once 14:23:22 #topic Additional agenda (from whiteboard) 14:24:02 the first two were covered last week, left them to make sure jhorstmann adds Loki to the PTG etherpad, so I can groom that and paste as priorities in the whiteboard (will check later today) 14:25:09 m_hiner: I know you wanted to discuss systemd patch, but I don't know if we don't need to postpone that next week - usually it was mgoddard and yoctozepto reviewing your patch when they could - but with Radek not spending time here anymore - it seems I need to look into that in more depth 14:25:21 mgoddard: comfortable to talk about the systemd patch, or should we move it to next week? 14:26:31 I think the templating could be discussed right now 14:27:53 If it comes to me - I don't think allowing users to modify the template is required, what would be the case for it? 14:28:47 i wanted to review skyline also ...but don't know if i will have a time :( 14:30:12 I also think so, as it wouldn't have any significant use cases (at least as far as I can think of) 14:31:46 and also to when customizing the template file, the users would also have to edit the kolla_systemd_worker.py which uses that template 14:32:25 So let's leave it out, we can revisit if we can find a case for it 14:33:05 Seems the remaining review comments clarification - we need to move for the next meeting - I'll look at the patch and let's discuss it next week 14:33:08 m_hiner: is that ok? 14:34:02 yes, but please do 14:34:13 we would really like to have it merged already 14:35:28 I understand, but now there's less reviewers than last cycle, so it will be harder... 14:35:35 anyway, let's talk about it next week 14:35:45 alright 14:35:47 #topic Open discussion 14:36:48 Now the question is - should we have the meeting now at 3pm CET (which is 2pm UK time and 2pm UTC it seems)? 14:37:00 Or should I move it in the repository for an hour later? 14:37:14 (at least until next daylight saving changes) 14:37:37 I would like to stay at this time, since the largescale sig meeting is immediately following 14:38:02 i want to ask about splitting https://review.opendev.org/c/openstack/kolla-ansible/+/799229 , should I also create smaller patchest introducing container_worker? 14:38:09 mgoddard, kevko: anyone opposing? 14:38:53 ihalomi: looks huge, would be nice 14:39:16 as for meeting time, I don't mind 14:40:27 Ok then, let's try this for now 14:40:45 Any other open discussion topics? 14:41:15 just a question, did anyone ever discuss the ubuntu license terms? 14:41:28 these two patchest are ready to merge https://review.opendev.org/c/openstack/kolla-ansible/+/862883 , https://review.opendev.org/c/openstack/kolla-ansible/+/862751 14:41:53 if I read them correctly, Ubuntu may only be distributed unmodified, not patched like in our containers 14:42:29 https://ubuntu.com/legal/intellectual-property-policy 14:44:27 that's interesting... 14:44:45 Does it mean we need to stop publishing Ubuntu images? ;-) 14:45:20 that might be the result, but ianal and so on 14:46:03 Should we ask somebody? e.g. foundation? 14:46:07 that page claims it was last updated in 2015, so not a new situation 14:46:32 so my first thinking was surely this has somehow been discussed long ago 14:47:08 but if it hasn't, maybe TC first and have them talk to foundation if needed might be good 14:48:14 Ok, how do we contact the TC? a mail to the usual openstack-discuss ML will suffice? 14:48:31 I would usually just ask in #openstack-tc 14:48:43 highlight "tc-members" 14:49:10 frickler: is it "modified" if we just adding packages and code ? 14:49:41 kevko: that's my understanding, yes 14:49:57 well, we use the base Ubuntu image, we're not modifying it in theory - but let's ask just to be sure 14:50:30 i would say that if you change some code already landed in ubuntu or patch it somehow ...maybe yes ..but i don't know if it is our case ...hard question 14:51:20 we are not modifing the image ..we are just adding layers with changes ..not modifiing the first layer which is image ..vanilla image 14:51:52 but i don't care ubuntu :D 14:52:37 hmm, the layers argument might work, but might be good to have this checked by someone with more legal experience 14:52:41 ok then, I'll pick it up in some ,,spare'' time 14:53:21 #action mnasiadka ask TC for guidance regarding Ubuntu distribution policy (https://ubuntu.com/legal/intellectual-property-policy) 14:53:33 I guess that's all for today 14:53:35 thanks for coming! 14:53:37 mnasiadka: about your comment in patchset, where should i add it? is site.yml best options? 14:53:37 #endmeeting