14:00:09 <whoami-rajat> #startmeeting cinder 14:00:09 <opendevmeet> Meeting started Wed Jan 5 14:00:09 2022 UTC and is due to finish in 60 minutes. The chair is whoami-rajat. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:09 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:09 <opendevmeet> The meeting name has been set to 'cinder' 14:00:22 <jungleboyj> o/ 14:00:27 <walshh_> hi 14:00:36 <felipe_rodrigues> hi 14:00:49 <andrebeltrami[m]> hello 14:00:54 <rfluisa> o/ 14:00:59 <yuval> Hey 14:01:01 <whoami-rajat> Brian is yet to be back from vacation so as discussed in last meeting of 2021, I will be taking today's meeting 14:01:04 <SachinMore> hi 14:01:05 <enriquetaso> hi 14:01:09 <sfernand> hi 14:01:17 <jungleboyj> whoami-rajat: Thank you. 14:01:24 <sfernand> happy new year folks 14:01:25 <whoami-rajat> np 14:01:26 <whoami-rajat> Happy new year everyone! 14:01:46 <whoami-rajat> and i missed roll call... 14:01:58 <whoami-rajat> #link https://etherpad.opendev.org/p/cinder-yoga-meetings 14:02:09 <eharney> hi 14:02:12 <whoami-rajat> hope everyone had a great vacation time 14:02:32 <caiquemello[m]> o/ 14:03:00 <LeoCampelo> o/ 14:03:10 <jungleboyj> :-) 14:03:12 <ecsantos[m]> o/ 14:03:55 <whoami-rajat> looks like a great turnout 14:04:00 <whoami-rajat> let's get started 14:04:06 <whoami-rajat> #topic announcements 14:04:13 <whoami-rajat> Simon Dodsley (simondodsley on IRC) has been added to the cinder-specs core team 14:04:19 <whoami-rajat> congratulations simondodsley 14:04:34 <enriquetaso> congrats! 14:04:48 <jungleboyj> Congratulations. Well deserved! 14:05:02 <simondodsley> thank you 14:05:02 <whoami-rajat> #link http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026431.html 14:05:38 <whoami-rajat> thanks simon for all your contributions! 14:05:42 <whoami-rajat> moving on 14:05:48 <whoami-rajat> next announcement 14:05:51 <whoami-rajat> Paramiko new release 2.9.1 broke ssh connection failing tempest-full-py3 job 14:06:24 <whoami-rajat> people may or may not be aware but paramiko's new release changed some ssh related functionalities which broke tempest tests 14:06:38 <whoami-rajat> as the tests wasn't able to ssh instances 14:06:55 <yuval> yes, I saw it in our internal CI 14:07:20 <whoami-rajat> the revert patch was merged and gate was fixed, this can continue until we've changes to adapt to the new release changes 14:07:29 <whoami-rajat> #link https://review.opendev.org/c/openstack/requirements/+/823128 14:08:07 <whoami-rajat> yuval, do we have a proper fix available for it? 14:08:32 <yuval> no, we roll back to our previous tempest version 14:08:46 <whoami-rajat> ok 14:09:15 <whoami-rajat> so let's constraint to not use the latest paramiko lib to avoid tempest failure 14:09:25 <whoami-rajat> next announcement 14:09:26 <whoami-rajat> Log4j vulnerability 14:09:40 <whoami-rajat> there has been a lot of discussion around Log4j recently everywhere 14:10:02 <whoami-rajat> Jeremy Stanley sent out a mail to openstack-discuss mentioning the impact on openstack 14:10:12 <whoami-rajat> #link http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026490.html 14:10:44 <whoami-rajat> looks like the networking-odl driver was affected due to a third party dependency but I'm not an expert there 14:10:50 <fungi> yeah, any additional info anyone has they could reply with would be much appreciated 14:10:56 <whoami-rajat> for details you can read the mail from him 14:11:12 <whoami-rajat> everyone ^^ 14:11:27 <fungi> my understanding is that opendaylight is implemented in java, and uses log4j, so needs to be updated if you've got it installed 14:11:30 <whoami-rajat> if anyone has any idea of more vulnerabilities inside openstack, they can reply to the ML with the details 14:12:25 <fungi> yep, thanks! 14:12:47 <whoami-rajat> thanks for the details fungi 14:13:08 <whoami-rajat> next announcement 14:13:09 <whoami-rajat> Milestone 2 week (Jan 03 - Jan 07 R-12) 14:13:19 <whoami-rajat> so we are in the week of M-2 14:13:36 <whoami-rajat> Elod sent out a mail regarding release specific deadlines that need to be addressed in this week 14:13:48 <whoami-rajat> #link http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026479.html 14:14:07 <whoami-rajat> 1) All projects should have deliverable files 14:14:24 <whoami-rajat> which i checked and we have for our projects python-cinderclient, cinder, os-brick, cinderlib and cinder-tempest-plugin 14:14:35 <whoami-rajat> 2) Libraries need to be released at least once per milestone period 14:15:00 <whoami-rajat> which I'm not sure about if we are going to release os-brick for M-2, i checked and we didn't release it last cycle in M-1 or M-2 14:15:31 <whoami-rajat> also need to go through the patches that needs to be released 14:15:49 <yuval> if I have a patch set for os-brick, and its not merged in M-2 - it means it wont get in yoga release? 14:16:08 <whoami-rajat> i will discuss with Brian once he's back from vacation 14:16:27 <whoami-rajat> yuval, we will be releasing os-brick before the final yoga release 14:16:49 <yuval> ok thanks, what it means date wise? 14:17:33 <whoami-rajat> which should be 2 weeks (Feb 21 - Feb 25) before RC-1 (Mar 07 - Mar 11) 14:17:36 <whoami-rajat> yuval, Feb 21 - Feb 25 14:17:49 <yuval> ok thanks 14:17:53 <whoami-rajat> np 14:18:26 <whoami-rajat> that's all i had for announcements 14:18:39 <whoami-rajat> anyone else has anything? 14:19:11 <SachinMore> hi, the kioxia dev team has a query 14:19:38 <whoami-rajat> SachinMore, you can ask that in the open-discussion (later during the meeting) 14:19:58 <SachinMore> ok, thanks 14:20:02 <whoami-rajat> ok, moving on to topics 14:20:07 <whoami-rajat> #topic Yuval from lightbits labs says hello - working to add lightbits driver to the cinder project 14:20:11 <whoami-rajat> yuval, that's you 14:20:14 <yuval> Hey yes 14:20:39 <yuval> lightbits labs is working on a storage sulotion for nvme over tcp 14:21:01 <yuval> and part of the work we want to make the product be able to communicate with cinder driver 14:21:24 <yuval> so we created a cinder driver its running for few years now 14:21:38 <yuval> mainly tested with rocky to Train 14:22:02 <yuval> and currently developed env with kolla and xena 14:22:27 <yuval> there are 3 PR currently waiting for review in cinder, os-brick and nova 14:22:34 <yuval> and we are working on a thrid party CI 14:22:59 <yuval> maybe someone have a question? 14:23:05 <whoami-rajat> yuval, can you add links to the patches on the etherpad? 14:23:40 <yuval> yes I will 14:23:44 <enriquetaso> #link https://review.opendev.org/c/openstack/os-brick/+/821603 14:23:56 <whoami-rajat> thanks, i remember simondodsley and Gorka planning to work on nvme this cycle 14:24:06 <whoami-rajat> maybe it was mostly focused on multipathing, not sure 14:24:21 <simondodsley> yuval, does your driver support multipathing and if so which sort - ANA or DM? 14:24:27 <yuval> if we can help in anyway we are open for questions 14:24:28 <enriquetaso> #link https://review.opendev.org/c/openstack/cinder/+/821602 14:24:44 <whoami-rajat> yuval, sorry for the wrong deadline, os-brick release deadline is Feb 07 - Feb 11 14:24:56 <whoami-rajat> you can follow the yoga cycle release schedule here 14:24:58 <whoami-rajat> #link https://releases.openstack.org/yoga/schedule.html 14:25:06 <yuval> simon let me get back to you with a proper answer 14:25:46 <simondodsley> i ask because there are a lot of changes to NVMe multipathing in the works currently 14:25:46 <yuval> whoami-rajat thank you, so we need to pass the zuul test and some human review till that date Feb07 14:26:46 <whoami-rajat> yuval, cinder and os-brick have separate deadlines, you need to have the third party CI in place and driver code ready before Jan 17 14:26:50 <simondodsley> yuval, you will need your third-party CI to start reporting on your driver and other general cinder patches by R-10 14:26:56 <simondodsley> lol 14:27:24 <yuval> when is R-10? 14:27:36 <simondodsley> Jan 17 14:27:54 <tosky> yuval: reference page: https://releases.openstack.org/yoga/schedule.html 14:27:55 <yuval> ok 14:28:19 <sfernand> Jan 17 - Jan 21 14:28:29 <sfernand> milestone is https://releases.openstack.org/yoga/schedule.html#y-cinder-driver-deadline 14:28:36 <yuval> Yes, I saw it, thank you. currently we have a dedicated cluster for the CI and we manage to connect with jenkins-gerrit-trigger 14:29:02 <yuval> simon regarding multipath - we support it using ANA 14:29:49 <yuval> we still didnt figure out how to post comments 14:30:04 <yuval> do I need a special priv or a regular user will do? 14:30:19 <whoami-rajat> a regular user can post comments 14:30:26 <simondodsley> OK - then please test against the current multipath patches in os-brick so that the ANA changes there are validated 14:31:03 <yuval> can you link me the patches? 14:32:56 <whoami-rajat> yuval, you can find the patches in gerrit with project as os-brick https://review.opendev.org/q/project:openstack%252Fos-brick 14:33:27 <whoami-rajat> so please review the lightbits driver and related os-brick code, I've added links to the etherpad, thanks enriquetaso for providing links 14:33:41 <whoami-rajat> we can discuss details in the review or #openstack-cinder channel 14:33:45 <simondodsley> I think there are 3 open nvme patches from kioxia 14:34:00 <SachinMore> yes 14:34:32 <whoami-rajat> moving on to next topic 14:34:43 <whoami-rajat> #topic Spec status 14:34:52 <whoami-rajat> #link https://etherpad.opendev.org/p/cinder-yoga-specs 14:35:15 <whoami-rajat> so most of the specs made it into yoga, some of which that didn't make it required additional work or had open review comments 14:35:31 <whoami-rajat> two of the patches didn't have both so let's discuss them 14:35:43 <whoami-rajat> 1) Spec to introduce additional task status field 14:35:50 <whoami-rajat> #link https://review.opendev.org/c/openstack/cinder-specs/+/818551 14:36:14 <whoami-rajat> I haven't gone through the spec but i think this is trying to add a task field as nova does 14:36:41 <whoami-rajat> Brian had a comment that we need to discuss this more and that we can do in midcycle-2 14:36:51 <whoami-rajat> 2) Update original resource's az 14:37:01 <whoami-rajat> #link https://review.opendev.org/c/openstack/cinder-specs/+/778437 14:37:20 <whoami-rajat> This spec is aimed at adding a new cinder-manage command to update availability zone 14:37:50 <whoami-rajat> i think this can be done without a spec but that's just my opinion 14:39:01 <whoami-rajat> let's discuss these again when the whole team is back, most probably next week 14:39:26 <jungleboyj> ++ 14:39:54 <whoami-rajat> that's all the topics we had, moving on to open discussion 14:39:57 <whoami-rajat> #topic open discussion 14:40:13 <whoami-rajat> SachinMore, i think you had a query to ask 14:40:45 <SachinMore> I did, but our dev guy is not able to join 14:40:54 <SachinMore> so it will have to wait 14:40:59 <yuval> I have a q 14:41:17 <yuval> its related to third party ci - is it ok? 14:41:42 <whoami-rajat> SachinMore, ok, we've weekly meetings so you can also add your topic to next weeks meeting agenda 14:41:47 <whoami-rajat> yuval, sure, go ahead 14:42:24 <yuval> lets say I am running a test on a patch set - the overall env -meaning the other projects like nova neutron 14:42:38 <yuval> they need to be in which branch - xena master? 14:42:45 <yuval> or some yoga release? 14:43:12 <simondodsley> i would say that you should always run the master branch for every project 14:43:25 <yuval> or I shouldnt do integration tests on cinder internal? 14:43:32 <whoami-rajat> yuval, do you mean which release you should run the tempest suite against? the current development cycle is yoga 14:43:49 <whoami-rajat> as simon said ^^ 14:43:51 <simondodsley> which is the current master branch 14:44:06 <yuval> ok, master in opendev not master on github 14:44:15 <simondodsley> same - its a mirror 14:44:22 <whoami-rajat> github is a mirror opendev 14:44:23 <yuval> I see 14:45:05 <yuval> I am currently using kolla with dev mode 14:45:12 <yuval> and running with master 14:45:17 <yuval> so that is ok right? 14:45:53 <yuval> when I get a new patch set - I will check it out in my cinder dir, and run tempest 14:46:29 <simondodsley> Using Software Factory to build your CI is probably a better way to go. That seems to be thje general direction now 14:47:06 <yuval> and regarding the logs - which files should I expose? 14:47:16 <yuval> tempest logs 14:47:27 <simondodsley> If you use SF then it is all done for you 14:48:01 <jungleboyj> simondodsley: Is there documentation somewhere on the best practices for doing that? 14:48:07 <jungleboyj> Using SF? 14:48:30 <yuval> I am afraid 17 Jan is to close to change CI framework 14:48:41 <simondodsley> Sadly not. We are currently rebuilding our CI to support NVMe and are using SF - we will try and document this as much as possible for the community 14:48:43 <yuval> but I will sure take a look 14:48:58 <jungleboyj> simondodsley: That would be great! 14:49:05 <yuval> Agree 14:50:16 <whoami-rajat> i think simondodsley also gave a presentation on software factory 14:50:37 <whoami-rajat> can't remember which PTG or midcycle it was but recording should be available in the cinder channel 14:50:49 <simondodsley> At one of the last PTGs one of the Pure guys gave a presentation (it's recorded) but it was high level, not implementation detail 14:50:57 <whoami-rajat> https://www.youtube.com/channel/UCJ8Koy4gsISMy0qW3CWZmaQ 14:50:59 <jungleboyj> whoami-rajat: Oh, that is right. 14:51:06 <whoami-rajat> ok 14:51:46 <whoami-rajat> jungleboyj++ for uploading all the videos 14:52:07 <jungleboyj> :-) My pleasure. 14:53:08 <yuval> there are also meeting with video? 14:53:17 <whoami-rajat> 7 minutes left, do we have anything else for open discussion? 14:53:26 <jungleboyj> Once a month we do the meetings in video. 14:53:35 <whoami-rajat> yuval, last meeting of every month is video + all PTG, midcycles are in video 14:53:42 <jungleboyj> Then we record all the Project Team Gathering meetings and mid-cycles. 14:54:01 <yuval> and what framework is use zoom? 14:54:26 <whoami-rajat> Bluejeans as of now but we might shift to something else in future 14:54:51 <yuval> I see ok 14:57:34 <whoami-rajat> looks like there's nothing else to discuss, we can close 3 minutes early 14:57:43 <whoami-rajat> Thanks everyone for attending and happy new year once again! 14:57:47 <whoami-rajat> #endmeeting