| *** dviroel|afk is now known as dviroel | 11:19 | |
| *** dasm|ruck|afk is now known as dasm|ruck | 13:31 | |
| whoami-rajat | #startmeeting cinder | 14:00 |
|---|---|---|
| opendevmeet | Meeting started Wed Jun 8 14:00:13 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 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
| opendevmeet | The meeting name has been set to 'cinder' | 14:00 |
| whoami-rajat | #topic roll call | 14:00 |
| eharney | howdy | 14:00 |
| tosky | hi | 14:00 |
| fabiooliveira | hi | 14:01 |
| simondodsley | hi from Berlinb | 14:01 |
| felipe_rodrigues | o/ | 14:01 |
| whoami-rajat | I think Fernando is also in Berlin and was asking if someone else was there too from cinder team simondodsley | 14:02 |
| simondodsley | Yuval from LightBits is also here | 14:02 |
| enriquetaso_ | hi | 14:02 |
| whoami-rajat | oh cool | 14:02 |
| *** enriquetaso_ is now known as enriquetaso | 14:02 | |
| enriquetaso | hi | 14:03 |
| whoami-rajat | #link https://etherpad.openstack.org/p/cinder-zed-meetings | 14:03 |
| whoami-rajat | we've a good amount of people and a long agenda today so let's get started | 14:04 |
| whoami-rajat | #topic announcements | 14:04 |
| whoami-rajat | first, Cinder midcycle-1 summary | 14:05 |
| whoami-rajat | #link https://wiki.openstack.org/wiki/CinderZedMidCycleSummary | 14:05 |
| whoami-rajat | I've prepared a summary of our first mid cycle held last week, it is quite a short one but has links to the recordings | 14:06 |
| whoami-rajat | second, Release name change after Zed | 14:06 |
| whoami-rajat | so the new release naming is official | 14:06 |
| whoami-rajat | #link https://governance.openstack.org/tc/reference/release-naming.html | 14:06 |
| whoami-rajat | I've taken an example from the above doc | 14:06 |
| rosmaita | o/ | 14:07 |
| whoami-rajat__ | hope I'm back | 14:08 |
| whoami-rajat__ | internet issue | 14:08 |
| geguileo | whoami-rajat__: you are back | 14:08 |
| whoami-rajat__ | thanks! | 14:08 |
| whoami-rajat__ | so we were on the release naming | 14:09 |
| whoami-rajat__ | I've taken an example from the above doc | 14:09 |
| whoami-rajat__ | the first release after Zed will be named in this format -- OpenStack 2023.1 Axxxx | 14:09 |
| whoami-rajat__ | Where “2023” is the year of the release, “1” represents the first release of the year and “Axxxx” is the release name. | 14:09 |
| whoami-rajat__ | and this will continue for subsequent releases | 14:10 |
| whoami-rajat__ | more info is in the governance doc | 14:10 |
| whoami-rajat__ | next announcement, RBAC new design discussion | 14:10 |
| geguileo | having the date there is nice | 14:10 |
| whoami-rajat__ | yeah would be easy to track releases | 14:10 |
| whoami-rajat__ | #link http://lists.openstack.org/pipermail/openstack-discuss/2022-June/028878.html | 14:10 |
| rosmaita | the big change is that the stable branch will use the date version, so stable/2023.1 for the Axxxxx release | 14:10 |
| whoami-rajat__ | ^^ everyone | 14:11 |
| whoami-rajat__ | so TC is rethinking the design of RBAC and there will be a discussion in summit in the ops meetup to get operators feedback | 14:12 |
| geguileo | rosmaita: I don't like that :-( | 14:12 |
| whoami-rajat__ | we might see some changes after that so better to hold any RBAC related work but rosmaita is already aware | 14:12 |
| whoami-rajat__ | #link https://etherpad.opendev.org/p/ops-meetup-berlin-2022-planning#L74 | 14:13 |
| whoami-rajat__ | #link https://etherpad.opendev.org/p/rbac-operator-feedback | 14:13 |
| geguileo | new changes on the SRBAC work? I can't believe it! };-) | 14:13 |
| rosmaita | and so early in the cycle :D | 14:13 |
| geguileo | lol | 14:14 |
| rosmaita | luckily, i have prepared for such a contingency by not working on it yet | 14:14 |
| whoami-rajat__ | no surprises there | 14:14 |
| whoami-rajat__ | rosmaita, :D | 14:14 |
| whoami-rajat__ | moving on to the final announcement | 14:14 |
| geguileo | can we add something to the RBAC operator feedback? | 14:14 |
| whoami-rajat__ | Register blueprint for your new driver | 14:14 |
| geguileo | or did that meeting already happen? | 14:14 |
| rosmaita | meeting happens friday | 14:15 |
| whoami-rajat__ | it will happen on 16 or 17 june i guess | 14:15 |
| rosmaita | as long as you say scope is a bad idea, feel free to leave comments :P | 14:15 |
| whoami-rajat__ | oh friday 10t | 14:15 |
| rosmaita | sorry, Rajat, we are having an interleaved discussion | 14:15 |
| geguileo | whoami-rajat__: yeah, sorry | 14:15 |
| whoami-rajat__ | no issues, good to have things cleared out | 14:16 |
| *** whoami-rajat__ is now known as whoami-rajat | 14:16 | |
| whoami-rajat | finally able to change IRC nick! | 14:17 |
| whoami-rajat | so last announcement | 14:17 |
| whoami-rajat | I sent out a mail to the ML addressing driver vendors to register blueprints for the new drivers proposed to Zed | 14:17 |
| whoami-rajat | for better tracking | 14:17 |
| whoami-rajat | #link http://lists.openstack.org/pipermail/openstack-discuss/2022-June/028879.html | 14:17 |
| whoami-rajat | I've mentioned the drivers we discussed during midcycle there, if there are more we will get a response on the thread which is good | 14:18 |
| whoami-rajat | and request to the reviewers to focus on driver reviews as we've a bunch of drivers which will probably consume a lot of time to review | 14:19 |
| rosmaita | whoami-rajat: ++ | 14:19 |
| whoami-rajat | and we might miss deadline otherwise | 14:19 |
| whoami-rajat | that's all for announcements, anyone has anything else? | 14:20 |
| rosmaita | about the drivers | 14:20 |
| whoami-rajat | rosmaita, yes | 14:20 |
| rosmaita | we should prioritize the YADRO driver, since it's been posted since the day before the yoga deadline | 14:20 |
| rosmaita | looks like it is passing tests now (or the last time i looked) | 14:21 |
| whoami-rajat | ack, sounds good | 14:21 |
| whoami-rajat | tests I assume third party CI and not only Zuul? | 14:21 |
| geguileo | should take this opportunity to take notes on mistakes people do when developing their new drivers to improve our docs? | 14:21 |
| rosmaita | yuval had a bunch of suggestions from his driver whose name escapes me | 14:22 |
| whoami-rajat | geguileo, +1 but I've seen mistakes that are already documented :( but good practice | 14:22 |
| rosmaita | (he is at the summit, not here) | 14:22 |
| whoami-rajat | lightbits lightos driver? | 14:22 |
| geguileo | whoami-rajat: in that case the comment is just adding a link to the doc ;-) | 14:22 |
| rosmaita | that's it | 14:22 |
| whoami-rajat | geguileo, yes! | 14:23 |
| geguileo | rosmaita: the suggestions was for our docs or for our driver interface? | 14:23 |
| geguileo | s/was/were | 14:23 |
| whoami-rajat | good suggestions, I will prepare an etherpad with the BP links and driver patches to prioritize better | 14:23 |
| rosmaita | geguileo: mostly docs, but possibly some interface suggestions too | 14:23 |
| rosmaita | https://etherpad.opendev.org/p/cinder-drivers-documentation | 14:23 |
| rosmaita | we can gather suggestions there and then put up a big patch ^^ | 14:24 |
| whoami-rajat | good idea | 14:25 |
| simondodsley | I think the major miss is the Software Factory stuff | 14:26 |
| simondodsley | there is nothing out there and yet it is the preferred method now (supposedly) | 14:26 |
| geguileo | yeah, looks like the big pain is still the CI | 14:26 |
| rosmaita | ++ | 14:26 |
| simondodsley | yep -also look slike the latest Zull is not consistent in the way it is assigning interfaces to vms | 14:27 |
| simondodsley | so one day the iSCSI ports on on one interface and the next day they are on another. | 14:27 |
| simondodsley | That causes all sorts of failures | 14:27 |
| rosmaita | somehow datacore is running their CI jobs in 18 minutes | 14:27 |
| geguileo | rosmaita: how???? | 14:28 |
| simondodsley | physically impossible | 14:28 |
| whoami-rajat | devstack installation takes more time than that :D | 14:28 |
| rosmaita | yes, we need to look more closely | 14:28 |
| simondodsley | ++ | 14:28 |
| geguileo | whoami-rajat: that's what I was thinking | 14:28 |
| enriquetaso | ++ | 14:28 |
| rosmaita | one result i saw was runnning tests in 40 cores | 14:28 |
| geguileo | simondodsley: the interfaces issue sounds like a nightmare | 14:28 |
| * geguileo wants 40 cores | 14:28 | |
| simondodsley | yes it is, especially when I have multiple card types for different data planes | 14:29 |
| rosmaita | cinder could use 40 cores! think of the review bandwidth | 14:29 |
| simondodsley | lol | 14:29 |
| geguileo | lol | 14:29 |
| whoami-rajat | okay, so we can continue discussion on this later (in open discussion or cinder channel) and move on to topics (we've a bunch of them) | 14:29 |
| geguileo | ok | 14:30 |
| whoami-rajat | thanks! | 14:30 |
| whoami-rajat | #topic Opinion on low attendance at mid cycle and how we can improve it in future | 14:30 |
| whoami-rajat | So i was thinking about this and I've mentioned some possible reasons on the etherpad | 14:30 |
| whoami-rajat | what i wanted to ask is, if the notifications are not clear (IRC, mail) and we should add additional things like a calendar invite? | 14:31 |
| simondodsley | an invite would be good, but could the ML deal with that? | 14:31 |
| rosmaita | i think the notificaions were clear, and it was listed on the openstack release schedule | 14:32 |
| simondodsley | I think it was just too close to the summit IMHO | 14:32 |
| rosmaita | calendar invite wouldn't hurt (don't know about simondodsley's email question, though) | 14:32 |
| geguileo | the calendar invite could be like the ping | 14:32 |
| whoami-rajat | simondodsley, yeah i mentioned that as a reason (people might be traveling to summit) | 14:32 |
| geguileo | we have a list of people who want the invite and we just create the invite for those instead of the mailing list... | 14:33 |
| whoami-rajat | geguileo +1, we could create a special list of people who would like to receive a calendar invite | 14:33 |
| simondodsley | maybe not travelling exactly, but prepping for the sumit and clearing backlog | 14:33 |
| rosmaita | i think simondodsley is right though, people preparing for summit were probably distracted from participating | 14:33 |
| whoami-rajat | yeah that too could be a reason | 14:34 |
| rosmaita | i don't know how they pick the summit dates anymore | 14:34 |
| whoami-rajat | so if this was a one time thing then we can continue with our current reminder system but if people are interested in getting calendar invites, they can provide their emails | 14:35 |
| geguileo | whoami-rajat: I'd like the calendar invite, since I always create it myself | 14:36 |
| geguileo | if it's not in my calendar, it's not happening. I even have this meeting in my calendar | 14:36 |
| whoami-rajat | rosmaita, me neither, last time i attended it was summit + PTG ... | 14:36 |
| simondodsley | speakng of PTG, do you all know its in Columbus in October? | 14:37 |
| enriquetaso | cool | 14:37 |
| zaitcev | News to me. | 14:37 |
| rosmaita | Fabulous Columbus, Ohio | 14:37 |
| simondodsley | Announced at Summit | 14:37 |
| rosmaita | middle of the week because Ohio State plays at home at the end of the week | 14:37 |
| simondodsley | I think 17-19 | 14:38 |
| simondodsley | clashes with an international trip for me sadly | 14:38 |
| whoami-rajat | geguileo, cool, I've created this etherpad so people can write their emails and i will send a calendar invite from next time https://etherpad.opendev.org/p/cinder-calendar-invite-for-events | 14:38 |
| whoami-rajat | everyone ^^ | 14:38 |
| enriquetaso | whoami-rajat++ | 14:39 |
| geguileo | whoami-rajat++ | 14:39 |
| whoami-rajat | There's an email also about the PTG with subject "Save the Date: PTG October 2022" | 14:39 |
| geguileo | simondodsley: thanks for the heads up on the PTG | 14:39 |
| whoami-rajat | simondodsley, thanks for providing summit announcements to us! | 14:40 |
| whoami-rajat | this topic seems sorted so moving on to the next one | 14:41 |
| whoami-rajat | #topic cinderlib status | 14:41 |
| simondodsley | its why im here | 14:41 |
| whoami-rajat | rosmaita, that's you | 14:41 |
| rosmaita | ok, we have cinderlib release coming up | 14:41 |
| geguileo | simondodsley: I thought you were here to talk about nvmeof over FC | 14:41 |
| whoami-rajat | :D | 14:41 |
| rosmaita | so was looking at the repo to see that everything is working correctly | 14:41 |
| rosmaita | and | 14:41 |
| simondodsley | no - just for the beer | 14:42 |
| rosmaita | there are a few problems | 14:42 |
| geguileo | simondodsley: lol | 14:42 |
| geguileo | rosmaita: :-( | 14:42 |
| rosmaita | first one is we are supposed to be running requirements-check, but we can't run the normal one because of our trailing deliverable status | 14:42 |
| rosmaita | think i have that partially fixed | 14:42 |
| rosmaita | #link https://review.opendev.org/c/openstack/cinderlib/+/845026 | 14:42 |
| rosmaita | problem now is that we have cinder in requirements.txt | 14:43 |
| whoami-rajat | rosmaita, don't we have a template for projects that are cycle trailing ? | 14:43 |
| rosmaita | don't think so | 14:43 |
| whoami-rajat | ok | 14:43 |
| rosmaita | i don't think there are enough of them | 14:43 |
| rosmaita | anyway, what i want to ask geguileo is what would happen if we remove cinder from requirements.txt | 14:44 |
| rosmaita | cinderlib tox doesn't use cinder from there, installs it from git | 14:44 |
| geguileo | rosmaita: yes, but if cinder's not there then the pypi package won't have it as a dependency, right? | 14:45 |
| rosmaita | right | 14:45 |
| rosmaita | i think we probably need it | 14:45 |
| geguileo | that's kind of a BIG THING | 14:45 |
| rosmaita | just wanted to verify before i go talk to the requirements team | 14:45 |
| rosmaita | we will need an exception to get cinder into global-requirements, i think | 14:46 |
| rosmaita | #action rosmaita work out cinder in requirements.txt with requirements team | 14:46 |
| rosmaita | ok, next item is weird cinderlib-tox-py36 job failures | 14:46 |
| geguileo | rosmaita: thanks! | 14:47 |
| whoami-rajat | thanks rosmaita | 14:47 |
| *** dviroel is now known as dviroel|lunch | 14:47 | |
| rosmaita | "Task Install any sibling python packages failed" | 14:47 |
| rosmaita | https://zuul.opendev.org/t/openstack/builds?job_name=cinderlib-tox-py36&project=openstack%2Fcinderlib | 14:47 |
| rosmaita | i have no idea, seems to be happening for cinderlib-lvm-functional job too | 14:47 |
| rosmaita | https://zuul.opendev.org/t/openstack/builds?job_name=cinderlib-lvm-functional&project=openstack/cinderlib | 14:47 |
| rosmaita | also seems to be happening on ubuntu and centos | 14:47 |
| geguileo | rosmaita: you may need to add the required-projects part | 14:48 |
| rosmaita | i was hoping tosky might have some ideas | 14:48 |
| rosmaita | oh | 14:48 |
| rosmaita | ok, i will take a look and see if that's an easy fix | 14:48 |
| rosmaita | because the cinderlib-ceph-functional job is great! | 14:48 |
| rosmaita | ok, last thing is cinderlib-tox-py39 | 14:49 |
| rosmaita | which i cannot reproduce locally | 14:49 |
| rosmaita | but here's an example if someone wants to look | 14:49 |
| geguileo | rosmaita: me should look | 14:49 |
| rosmaita | #link https://zuul.opendev.org/t/openstack/build/3576fdbc672e4dbba200b832bfb122ea | 14:49 |
| rosmaita | geguileo: ty | 14:50 |
| rosmaita | ok, i lied | 14:50 |
| rosmaita | here is the actual last item | 14:50 |
| rosmaita | we don't seem to be using upper-constraints | 14:50 |
| rosmaita | #link https://opendev.org/openstack/cinderlib/src/commit/82b8c25c973a25ee62c1121ce087ff095afc6961/tox.ini | 14:50 |
| rosmaita | possibly i am missing something though | 14:50 |
| geguileo | rosmaita: those are all related to the cinderlib database metadata plugin | 14:51 |
| rosmaita | i was hoping the py39 failure was using a too new library or something (though not being able to reproduce it locally kind of nixes that idea) | 14:51 |
| geguileo | which probably points to what you thought of the library | 14:51 |
| rosmaita | ok | 14:52 |
| geguileo | rosmaita: I'll look into it tomorrow, ping me again tomorrow end of day if I haven't gotten back to you | 14:52 |
| rosmaita | geguileo: great! | 14:52 |
| rosmaita | geguileo: should i try a patch changing the pip install command to use constraints? | 14:52 |
| rosmaita | (independently of the db metadata plugin problem) | 14:53 |
| geguileo | rosmaita: that's a good question | 14:54 |
| geguileo | rosmaita: doesn't cinderlib use constraints? | 14:54 |
| rosmaita | i don't think so | 14:54 |
| rosmaita | https://opendev.org/openstack/cinderlib/src/commit/82b8c25c973a25ee62c1121ce087ff095afc6961/tox.ini | 14:54 |
| geguileo | rosmaita: mmmm, only for reno and docs, that's unconventional | 14:54 |
| rosmaita | yeah | 14:55 |
| rosmaita | ok, let me see if the trick you came up with for cinder works for cinderlib | 14:55 |
| geguileo | yeah, I think we should add it | 14:55 |
| rosmaita | ok, i'll put up a patch after the meeting and let's see what happens | 14:56 |
| whoami-rajat | cool, thanks rosmaita and geguileo | 14:56 |
| rosmaita | ok, that's all, other than to remember that release must happen on or before 23 June | 14:56 |
| whoami-rajat | sure | 14:56 |
| whoami-rajat | let's quickly get over the last topic | 14:57 |
| whoami-rajat | #topic Add some information file about how tempest works | 14:57 |
| whoami-rajat | enriquetaso, that's you | 14:57 |
| rosmaita | this sounds like a good idea, even before hearing enriquetaso's ideas! | 14:57 |
| enriquetaso | :P | 14:57 |
| enriquetaso | My original question was how do we track dependencies between tempest and the plugins? I know the CI uses the Tempest master branch to run tests, but maybe some users are using an old version of Tempest. | 14:57 |
| enriquetaso | And tosky kindly answered me that you just assume that you always use tempest and all plugins from master. | 14:58 |
| enriquetaso | So eharney suggested I add some kind of info that explains how this works. | 14:58 |
| eharney | what's proposed there doesn't answer the question that i had in this area, i think | 14:58 |
| eharney | it's not clear what the correct process is when we are adding tests to cinder-tempest-plugin that require newly landed changes in tempest | 14:58 |
| eharney | just saying "assume it's all running master" means that people who want to install tempest and our plugin themselves from pip will just break | 14:59 |
| tosky | I'm not sure | 14:59 |
| rosmaita | maybe we can invite gmann to the next meeting to talk us through this | 14:59 |
| geguileo | eharney: oh, right! | 14:59 |
| eharney | this has come up twice recently w/ new test work, i think we need to understand it | 14:59 |
| whoami-rajat | that's a good question for the QA team, maybe we can ask gmann and kopecmartin | 14:59 |
| tosky | that's up the releasing process, usually tempest and the plugins are tagged together | 14:59 |
| enriquetaso | good idea rosmaita | 14:59 |
| eharney | tosky: and requirements.txt etc... which we are currently ignoring | 15:00 |
| tosky | the answer from the QA team will be "use master" | 15:00 |
| tosky | fine | 15:00 |
| eharney | if the answer is "only the gate runs matter" we need to document that that is the case | 15:00 |
| gmann | hi, i am in another meeting but I can check after meeting | 15:00 |
| whoami-rajat | thanks gmann | 15:00 |
| whoami-rajat | and we're out of time | 15:00 |
| eharney | but i think this is supposed to be installable and used in other contexts | 15:00 |
| enriquetaso | i've proposed a patch already but based on this conversation | 15:00 |
| gmann | sure, we can discuss here after meeting | 15:01 |
| enriquetaso | #link https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/845050 | 15:01 |
| enriquetaso | sure | 15:01 |
| rosmaita | gmann: actually, in #openstack-cinder | 15:01 |
| whoami-rajat | we can continue discussion in cinder channel | 15:01 |
| gmann | yes | 15:01 |
| enriquetaso | sounds good to me! | 15:01 |
| whoami-rajat | as rosmaita said | 15:01 |
| whoami-rajat | thanks everyone for joining | 15:01 |
| whoami-rajat | #endmeeting | 15:01 |
| opendevmeet | Meeting ended Wed Jun 8 15:01:46 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:01 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-06-08-14.00.html | 15:01 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-06-08-14.00.txt | 15:01 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-06-08-14.00.log.html | 15:01 |
| *** whoami-rajat__ is now known as whoami-rajat | 15:38 | |
| *** dviroel|lunch is now known as dviroel | 16:05 | |
| *** dviroel is now known as dviroel|afk | 20:27 | |
| *** dasm|ruck is now known as dasm|ruck|afk | 21:05 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!