13:01:02 <mnasiadka> #startmeeting kolla
13:01:02 <opendevmeet> Meeting started Wed Oct  4 13:01:02 2023 UTC and is due to finish in 60 minutes.  The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:01:02 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:01:02 <opendevmeet> The meeting name has been set to 'kolla'
13:01:07 <mnasiadka> #topic rollcall
13:01:08 <mnasiadka> o/
13:01:45 <SvenKieske> o/
13:01:47 <jangutter> o/
13:01:48 <bbezak> o/
13:01:52 <mmalchuk> o/
13:02:03 <frickler> \o
13:02:10 <mhiner> o/
13:03:59 <mnasiadka> #topic agenda
13:03:59 <mnasiadka> * CI status
13:03:59 <mnasiadka> * Release tasks
13:03:59 <mnasiadka> * Regular stable releases (first meeting in a month)
13:03:59 <mnasiadka> * Current cycle planning
13:04:00 <mnasiadka> * Additional agenda (from whiteboard)
13:04:00 <mnasiadka> * Open discussion
13:04:03 <mnasiadka> #topic CI status
13:04:21 <mnasiadka> After RMQ drama I think we're back into business as usual
13:05:44 <mnasiadka> There have been some post failures on pushing to quay.io
13:05:48 <mnasiadka> but let's monitor that
13:06:05 <mnasiadka> #topic Release tasks
13:06:53 <mnasiadka> I think none really, we're waiting for RDO to publish stable/2023.2
13:07:00 <mnasiadka> to switch to those repos
13:07:04 <mnasiadka> nothing apart this
13:07:11 <mnasiadka> #topic Current cycle planning
13:07:36 <mnasiadka> So, I didn't have time looking into LE or Podman
13:07:49 <mnasiadka> But I'll try to make kevko happier by doing it this week
13:08:02 <mnasiadka> anybody else having cycles to look into those two?
13:08:31 <SvenKieske> I'll try to, but probably later this week, at least not today I think, still other stuff to do
13:08:42 <mnasiadka> #link https://review.opendev.org/c/openstack/kolla/+/887347
13:09:11 <mnasiadka> and
13:09:13 <mnasiadka> #link https://review.opendev.org/c/openstack/kolla-ansible/+/741340
13:09:25 <mnasiadka> kevko: the k-a patch has a merge conflict - please update :)
13:09:47 <mnasiadka> SvenKieske: how are we with td-agent upgrade? need help?
13:10:36 <SvenKieske> I'd hope to finish that, I'm not aware of "more" issues then the currently known ones: file paths, user changes
13:10:47 <opendevreview> Juan Pablo Suazo proposed openstack/kolla master: Adds TAAS Neutron plugin to support OVS port mirrors  https://review.opendev.org/c/openstack/kolla/+/885151
13:11:17 <SvenKieske> I guess I asked last week about whether we care about UID|GID stability and never received an answer
13:12:04 <SvenKieske> I know there is some code which pins users to certain UIDs I can't imagine a way how this could work with the new fluent package
13:12:42 <SvenKieske> so in that area, if we care about it, help would be nice, I guess it might be configurable in the new fluentd-package, but I didn't have time to trace it down just yet
13:12:57 <mnasiadka> do we need to change the user?
13:13:11 <frickler> well we need some way of upgrading existing things I guess? pinning would be easier than having a migration script
13:13:30 <SvenKieske> yes, the new username is "_fluentd" if my memory is correct and this is going to be set during "postinst" phase during package install
13:13:46 <mnasiadka> fantastic
13:13:57 <SvenKieske> I did already mention this on IRC and in the changeset discussion with no feedback so far :)
13:14:09 <mnasiadka> well then we need to add that user with new UID
13:14:17 <mnasiadka> does that mean we need to change some permissions on upgrade? uhh
13:14:41 <SvenKieske> mhm
13:14:48 <SvenKieske> not sure what is stored in these paths tbh
13:14:54 <mnasiadka> do we have any other choice? I don't think so
13:15:44 <SvenKieske> question is what would be lost if we have /var/lib/fluentd/ instead of old path (don't nail me down on it, the important bit is /var/lib/$bla changes)
13:16:12 <mnasiadka> probably nothing, but if you don't wander this route - you won't find out I guess
13:16:21 <SvenKieske> actually don't know what fluentd stores there, beside in flight data, sockets etc
13:16:30 <SvenKieske> I'll check it out
13:19:26 <mnasiadka> we should be fine, some buffers, in flight data, sockets
13:20:04 <mnasiadka> I've also been working on https://review.opendev.org/c/openstack/kolla-ansible/+/897227 - it's a bugfix, but given the amounts of comments in the bug it seems to be important
13:20:11 <mnasiadka> Seems people are using nvmeof after all
13:21:12 <mnasiadka> #topic Additional agenda (from whiteboard)
13:21:21 <mnasiadka> let's go through that, there's some
13:21:30 <mnasiadka> (jsuazo) 844614: Deploy Glance and Cinder Backup with S3 backend support
13:21:39 <mnasiadka> #link https://review.opendev.org/c/openstack/kolla-ansible/+/844614
13:22:30 <jsuazo> That proposal has addressed all comments and should be ready to merge :D
13:22:57 <mmalchuk> confirm that
13:23:36 <mnasiadka> What about https://review.opendev.org/c/openstack/kolla-ansible/+/844998/1 ?
13:23:53 <mnasiadka> Should I abandon this?
13:24:15 <mmalchuk> yep
13:24:26 <jsuazo> Yes, those changes are included in the proposal
13:25:23 <mnasiadka> I still don't know if I like the s3_* variables
13:25:37 <mnasiadka> frickler: willing to have a review?
13:25:52 <mmalchuk> norm variables)
13:25:57 <SvenKieske> are they to short? :D
13:26:11 <mnasiadka> well, usually we should have role specific variables
13:26:11 <SvenKieske> just add it to the review and discuss there? :)
13:26:22 <mnasiadka> but if we want to make it easier for users
13:26:24 <mnasiadka> I guess it's ok
13:26:28 <kevko> \o/
13:26:29 <SvenKieske> could make sense
13:26:38 <kevko> sorry for delay
13:26:57 <mnasiadka> no worries kevko
13:27:00 <mnasiadka> next one
13:27:01 <mnasiadka> (jsuazo) 885417: Configures the tap-as-a-service neutron plugin
13:27:05 <SvenKieske> could also be more complicated for the users if they want different s3 URLs/buckets :)
13:27:09 <mmalchuk> the review is an year old, lets merge it
13:27:13 <mnasiadka> #link https://review.opendev.org/c/openstack/kolla-ansible/+/885417
13:27:45 <mnasiadka> SvenKieske: it's covered in the docs
13:27:56 <SvenKieske> ok :)
13:28:01 <mnasiadka> jsuazo: did we merge the Kolla side?
13:28:18 <mnasiadka> Ah no, we didn't
13:28:21 <jsuazo> not yet. its the next point on the list
13:28:28 <mnasiadka> #link https://review.opendev.org/c/openstack/kolla/+/885151
13:28:29 <mmalchuk> not yet
13:28:56 <jsuazo> Zuul failing on unrelated image builds, rebased again and waiting for the jobs to run
13:29:10 <mnasiadka> ok then
13:29:27 <jsuazo> But made the changes to make the installation simply through pip
13:29:32 <mmalchuk> we change from source to pypi and I'm not sure
13:29:32 <frickler> please don't rebase if there is no merge conflict
13:29:42 * frickler feels like a broken record repeating that
13:29:49 <mmalchuk> it work perfect from source
13:31:22 <mnasiadka> reviewed
13:31:35 <jsuazo> It did, but as the source is not very well maintained (branch,version and tag-wise) its simpler to do it through pip
13:31:36 <kevko> why you don't like rebase ?
13:31:36 <kevko> if no merge conflict
13:31:36 <frickler> because it breaks patch history and is plain unneccessary
13:31:36 <mmalchuk> frickler care about CI cpu's ;_
13:31:36 <frickler> CI can be triggered with a recheck comment just as well
13:31:36 <SvenKieske> I'm always a big fan of not doing unneccessary work :)
13:31:45 <frickler> and reviewers don't have to go looking what might have changed through umpteen unneeded rebases
13:31:45 <mmalchuk> frickler we don't have history) with git amend))
13:31:52 <mnasiadka> frickler: we need a recheck button ;-)
13:32:18 <mmalchuk> big and red )))))
13:32:32 <frickler> no, people need to think before they recheck and add a meaningful reason
13:32:41 <frickler> else I'll complain about that, too ;-P
13:33:00 <mnasiadka> haha
13:33:05 <mnasiadka> ok, let's move on
13:33:09 <SvenKieske> that's also true
13:33:14 <mnasiadka> (jsuazo) 875983: Enable the Fluentd Plugin Systemd
13:33:17 <SvenKieske> but what about that pip bit now?
13:33:23 <mnasiadka> #link https://review.opendev.org/c/openstack/kolla-ansible/+/875983
13:33:28 <mnasiadka> SvenKieske: nothing, should work
13:33:52 <SvenKieske> ok
13:34:44 <SvenKieske> the systemd plugin is waiting on your feedback, I did propose to make this dependent on "enable_central_logging" which defaults to "no"
13:35:17 <SvenKieske> ah no, I see the feedback was already addressed.
13:35:27 <jsuazo> Added a variable to opt in to the fluentd systemd, "enable_fluentd_systemd",it defaults to the value of "enable_central_logging"
13:36:08 <mnasiadka> reviewed, docs oneliner and reno fixup needed and looks fine
13:36:10 <SvenKieske> that sentence should go into the release notes imho
13:36:21 <SvenKieske> and|or in the docs
13:36:33 <SvenKieske> not sure how we cover every variable, I guess we don'
13:36:39 <SvenKieske> t have everything in the docs..
13:36:47 <mnasiadka> we don't, but let's try to make docs better, not worse :)
13:36:54 <jsuazo> agree, i'll add it while addressing the new coments
13:37:00 <SvenKieske> nice, ty
13:37:04 <mnasiadka> #topic Open discussion
13:37:07 <mnasiadka> thanks
13:37:12 <mnasiadka> so - anybody anything?
13:37:15 <mnasiadka> Ah right
13:37:18 <mnasiadka> I have one
13:37:21 <mnasiadka> PTG timing
13:38:37 <mnasiadka> frickler: you didn't vote on the poll - so can you state your preferences here please?
13:39:07 <frickler> I don't care, open to anything
13:39:20 <SvenKieske> yeah, good news: our downstream meetings are mostly canceled so I guess I should've (more) time for PTG :)
13:39:27 <mnasiadka> ok, seems everybody is open to anything
13:39:34 <SvenKieske> I did vote :)
13:39:48 <mnasiadka> usually we did a very late slot to allow US to join
13:39:52 <mmalchuk> me too
13:40:01 <mnasiadka> but I haven't seen anybody from US since long time
13:40:29 <mmalchuk> anybody is here?)
13:40:34 <jangutter> Does that mean we can do s/color/colour/g finally?
13:40:47 <kevko> i have something
13:41:07 <mnasiadka> seems not
13:41:14 <mnasiadka> Bobcat PTG was 13:00 - 17:00 UTC
13:41:30 <mnasiadka> so 15:00 - 19:00 CEST
13:41:53 <mnasiadka> are we sticking to that, or should we shift a bit earlier?
13:42:18 <frickler> if you are asking it that way, I'd say earlier
13:42:47 <mmalchuk> 12:59 UTC ?
13:42:59 <SvenKieske> one or two hours earlier would be nice I guess.
13:43:03 <mmalchuk> be more specific
13:43:20 <SvenKieske> 12:00 - 16:00 UTC ?
13:43:26 <mmalchuk> one hour is ok
13:43:40 <mnasiadka> ok, let's shift one hour
13:43:45 <mnasiadka> it's still east coast US friendly
13:44:02 <frickler> just note that that won't appear in the official timetable
13:44:10 <mmalchuk> still nobody from US
13:44:25 <frickler> but the TC has been being similar things, so it should be ok
13:44:25 <SvenKieske> mhm, is it to late to change the official timetable?
13:45:07 <frickler> yes
13:45:10 <SvenKieske> then we should at least send out an email etc. to notify ppl not living on IRC everyday ;)
13:45:39 <kevko> Guys, I need to go out of PC for 10 minutes ..but I would like to also ask several things, so let me ask now and we can discuss after several minutes ...
13:46:03 <SvenKieske> ok
13:46:16 <mnasiadka> 23-27 October 2023:
13:46:16 <mnasiadka> Monday - 12.00 - 15.00 UTC (general, Kolla and Kolla-Ansible)
13:46:16 <mnasiadka> Tuesday - 12.00 - 14.00 UTC (Kolla-Ansible)
13:46:16 <mnasiadka> Tuesday - 14.00 - 15.00 UTC (Operator Hour)
13:46:16 <mnasiadka> Thursday - 12.00 - 14.00 UTC (Kayobe)
13:46:24 <mnasiadka> Is that basically what we would like?
13:46:45 <SvenKieske> seems fine to me
13:46:48 <mnasiadka> 3 hours on Monday, 2+1 hours on Tuesday and Kayobe on Thursday
13:46:58 <frickler> +1
13:46:59 <mmalchuk> fine
13:47:00 <SvenKieske> not 12-16?
13:47:07 <SvenKieske> one hour less?
13:47:22 <frickler> with no topics to discuss, we'll be even faster
13:47:23 <SvenKieske> I don't know, just asking, my first PTG
13:47:28 <mnasiadka> well, last time we didn't have that many topics, we can do 12-16 and just finish earlier
13:47:54 <kevko> 1. Rabbitmq/erlang incompatibility ... We found incompatibility in erlang/rabbitmq in yoga.. For example now I am checking master rabbitmq ...paste here ->
13:47:55 <kevko> https://paste.openstack.org/show/b2voIvMhqW4IblzVE5jD/
13:48:19 <mnasiadka> 3.12 in Yoga?
13:48:36 <kevko> no ..
13:48:42 <kevko> that paste is for master
13:48:57 <mmalchuk> kevko may be move to etherpad ?
13:49:07 <kevko> because currently i've decided to check all debian images from master -> antelope -> ...
13:49:10 <mnasiadka> kevko: can you post a summary instead of shredded bits?
13:49:12 <kevko> okay i  will
13:49:23 <SvenKieske> mhm, but shouldn't master be on erlang vm 26 already?
13:49:23 <mnasiadka> that would be easier to understand and fix :)
13:49:40 <mnasiadka> probably should be, and kevko is only checking Debian
13:49:53 <mnasiadka> can we get a full view on all distros and then think if we need to fix anything?
13:49:57 <kevko> yeah, but question was that i think we should switch erlang/rabbit to novemberrain ..and pin every version in every branch to avoid this in future
13:50:09 <mnasiadka> rabbit is from novemberain
13:50:19 <kevko> and erlang should be also i think
13:50:22 <mnasiadka> erlang can't be switched, because they don't mirror aarch64
13:50:27 <kevko> special case is arm
13:50:38 <mnasiadka> and they use launchpad to build the packages
13:50:46 <mnasiadka> so why would we download from a mirror that downloads from launchpad?
13:50:59 <kevko> but arm has different config in kolla
13:51:17 <mnasiadka> what do you mean by different?
13:52:01 <kevko> repos.yaml
13:53:37 <mnasiadka> I don't understand, please describe the situation fully somewhere - so we can all analyse
13:53:41 <kevko> Second thing -  there is no option to configure logging in kolla-ansible .. (i mean, formatters, handlers ...etc ....) ..so i will probably propose a new shared role
13:53:47 <kevko> okay i will
13:54:05 <kevko> i will add to etherpad probably
13:54:10 <mnasiadka> kevko: that's a PTG topic most probably
13:54:33 <mmalchuk> big plans
13:54:45 <kevko> and last question ..is it ok to add repo for python3-podman for ansible collection which is installing this package  ?
13:54:57 <mnasiadka> sure
13:55:06 <kevko> because i will need to create a ticket for debian release team and kindly ask them to include my package into stable
13:55:13 <kevko> for now it is in unstable ..
13:55:13 <mnasiadka> ok, coming back to the topic
13:55:27 <mnasiadka> 3 hours times two for the PTG is enough, or do we prefer 4?
13:55:32 <mnasiadka> (I'm fine with both)
13:55:55 <mmalchuk> 3 hours for rabbitmq fair enough
13:56:16 <mnasiadka> For RabbitMQ 3 weeks are not enough
13:56:32 <mmalchuk> do we have more topics?)
13:56:39 * SvenKieske actually debugged some rabbit stuff earlier this day
13:57:01 <SvenKieske> I asked earlier today about the status of quorum queues
13:57:11 <mnasiadka> ok, let's go for 3 hours on Mon and Tue, I'm pretty sure you'll all be sleeping on those sessions anyway :)
13:57:25 <mmalchuk> sure
13:57:28 <SvenKieske> I did only find out it's apparently support in oslo now, but I think we didn't implement it yet in kolla?
13:57:45 <mnasiadka> SvenKieske: not yet in Kolla, feel free to propose ;)
13:58:05 <mnasiadka> ok then
13:58:08 <SvenKieske> might be a topic for PTG? or is it a no-brainer? :D
13:58:30 <mnasiadka> probably more implementation detail than topic for PTG, we could discuss if that should be default or not :)
13:58:37 <mnasiadka> but sure, add it to the list
13:58:38 <SvenKieske> okay then
13:58:45 <mnasiadka> the more topics we have, the less chance we finish in 7 minutes
13:59:01 <mnasiadka> kevko: does the PTG timeline suit you?
13:59:11 <SvenKieske> PTG board, btw:
13:59:20 <SvenKieske> #link https://etherpad.opendev.org/p/kolla-caracal-ptg
13:59:35 <mnasiadka> thanks SvenKieske
13:59:40 <mnasiadka> ok, time is up
13:59:43 <mnasiadka> thanks for coming :)
13:59:49 <mnasiadka> #endmeeting