15:02:31 #startmeeting kolla 15:02:31 Meeting started Wed Jul 21 15:02:31 2021 UTC and is due to finish in 60 minutes. The chair is mgoddard. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:31 The meeting name has been set to 'kolla' 15:02:36 #topic rollcall 15:02:36 \o/ 15:03:19 0 15:03:21 -- 15:03:23 | 15:03:37 o/ 15:03:37 \/\ 15:04:36 [o] 15:04:37 #topic agenda 15:04:44 * Roll-call 15:04:46 * Agenda 15:04:48 * Announcements 15:04:50 * Review action items from the last meeting 15:04:52 * CI status 15:04:54 * Release tasks 15:04:56 * Xena cycle planning 15:04:58 * Open discussion 15:05:05 #topic announcements 15:05:42 None here 15:07:01 #topic Review action items from the last meeting 15:07:25 mgoddard email openstack-discuss about holiday and to cancel next week's meeting 15:07:27 mgoddard propose stable releases when backports merge 15:07:29 y 15:07:41 still waiting on those backports 15:07:59 what should I merge? 15:08:10 anything on stable 15:09:23 oh my 15:09:27 at least bugfix backports 15:09:39 ok, I will have a look 15:09:44 cool 15:10:43 https://review.opendev.org/c/openstack/kolla-ansible/+/799110 still not merge 15:10:48 #topic CI status 15:10:52 would be good to include in wallaby to unduck it 15:11:15 nothing has merged recently :) 15:11:34 well, many others merged :-( 15:11:57 and many more didn't 15:12:34 people are on holiday, busy, etc. 15:13:04 Kayobe CI broken 15:13:29 This approach seems to work: https://review.opendev.org/c/openstack/kayobe/+/800273 15:13:39 with dependent k-a fix: https://review.opendev.org/c/openstack/kolla-ansible/+/801267 15:14:45 I fixed the ipxe healthcheck issue yoctozepto spotted 15:14:51 https://review.opendev.org/c/openstack/kolla-ansible/+/801605/1 15:15:02 So waiting on reviews for that chain 15:15:10 I don't think there are any other CI issues? 15:16:00 I'm not up to date w.r.t CI nowadays 15:16:19 ok 15:16:27 #topic Release tasks 15:16:49 Can we just merge the new release process already? https://review.opendev.org/c/openstack/kolla/+/795320/3/doc/source/contributor/release-management.rst 15:18:36 Next milestone is R-8 Switch binary images to current release 15:18:38 in 3 weeks 15:18:53 also, request for cycle highlights went out on the ml 15:19:01 not due until september though 15:19:17 yup 15:19:32 #topic Xena cycle planning 15:19:45 I booked us some slots for the PTG 15:19:48 same as usual 15:20:02 13:00 - 17:00 UTC Monday and Tuesday for Kolla & Kolla Ansible 15:20:12 13:00 - 15:00 UTC Wednesday for Kayobe 15:20:37 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023540.html 15:20:49 PTG is Monday, October 18 to Friday, October 22, 2021 15:21:24 If anyone cannot make those slots and would like to change, please speak up and we can consider rescheduling 15:22:33 Anything else we should discuss for Xena? 15:22:46 I have two things 15:22:46 I suppose technically that was a Yoga topic 15:23:14 not sure if we are talking about functionality we want in Xena yet though 15:23:28 we should be ;-) 15:23:32 that's a valid topic 15:24:07 ok - 1. I'm still trying to get let's encrypt func into xena. Step one of this is https://review.opendev.org/c/openstack/kolla-ansible/+/741340 15:26:48 2. To move towards enabling scope for keystone (and enforce_new_defaults), we need be able to assign system scope to a role. AFAIK, this currently cannot be done using openstack ansible commands 15:28:08 2b - I wrote an email to openstack-discuss, and was told to use clouds.yaml file (based on OS_CLOUD environment variables). This is how it is done in devstack. 15:29:10 In the meantime, I have https://review.opendev.org/c/openstack/kolla-ansible/+/692179 updated and passing 15:32:57 we're still interested in letsencrypt 15:33:18 I'm trying to find a way to prioritise work on features 15:33:33 but we're quite under resourced at the moment 15:33:52 partially due to summer holidays 15:34:04 but also reduced reviewer activity 15:34:07 HELP WANTED 15:34:56 I missed your openstack-discuss mail 15:36:38 http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023746.html 15:36:42 thanks 15:38:41 Merged openstack/kolla master: docs: Update release management for Xena process https://review.opendev.org/c/openstack/kolla/+/795320 15:38:45 woop 15:40:41 I'm not sure what else to say on those topics 15:40:52 my brain is melting in 30 degree heat 15:41:12 boo to that! 15:41:14 bring back my English rain 15:41:41 Any more Xena topics? 15:42:26 I'm glad heat ended here 15:43:51 #topic Open discussion 15:43:57 Anything else today? 15:46:00 nuffing, I need to get back on review track 15:46:10 as a starting point - would it a possible pivot to move to clouds.yaml for KA deployment, or is that something we want to avoid? 15:46:42 clouds.yaml is the future; where do you want to put it here? 15:46:59 KA generates clouds.yaml 15:47:37 my only concern with clouds.yaml is admin credentials on disk 15:47:38 instead of each component registering user/role during deployment 15:48:00 I think openstack exporter does it too, but that is optional 15:48:08 ah, now I remember the issue 15:48:20 it would be a configuration option 15:48:58 clouds.yaml defines the creds to talk to keystone. Each component would still have to register users & roles 15:50:15 also kolla-toolbox runs on computes 15:50:24 I wouldn't want admin creds there 15:51:01 they are already in openstack config files I suppose 15:59:04 yeah, a compromised nova-compute is a gameover now 15:59:54 well, at least we should restrict where kolla-toolbox runs 16:00:01 wouldn't want to make the problem any worse 16:00:06 ++ 16:00:15 and ideally in future those creds could be constrained 16:00:32 we're out of time 16:00:34 thanks all 16:00:36 #endmeeting