*** dviroel is now known as dviroel|out | 00:59 | |
*** hemna8 is now known as hemna | 07:38 | |
*** dviroel|out is now known as dviroel | 11:15 | |
*** dasm|off is now known as dasm|rover | 12:44 | |
yuval_ | \ | 13:47 |
---|---|---|
rosmaita | #startmeeting cinder | 14:00 |
opendevmeet | Meeting started Wed Feb 2 14:00:53 2022 UTC and is due to finish in 60 minutes. The chair is rosmaita. 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 |
rosmaita | #topic roll call | 14:01 |
simondodsley | hi | 14:01 |
yuval_ | hey | 14:01 |
TusharTgite | hi | 14:01 |
eharney | howdy | 14:01 |
agarwchh | hi | 14:01 |
jungleboyj | o/ | 14:01 |
e0ne | hi | 14:01 |
fabiooliveira | o/ | 14:01 |
whoami-rajat | Hi | 14:01 |
tosky | o/ | 14:02 |
rosmaita | ok, tosky is here, so let's get started | 14:03 |
rosmaita | :) | 14:03 |
tosky | O.o | 14:03 |
rosmaita | #topic announcements | 14:03 |
rosmaita | next PTG is 4-8 April 2022 | 14:03 |
rosmaita | #link https://openinfra-ptg.eventbrite.com/ | 14:03 |
rosmaita | ot | 14:03 |
rosmaita | it's virtual and free, but you are asked to register anyway | 14:03 |
rosmaita | so please do | 14:04 |
rosmaita | this is week R-8 | 14:04 |
jungleboyj | It's virtually free? ;-) | 14:04 |
rosmaita | reminder that this week is the cinder driver features declaration | 14:04 |
rosmaita | #link https://releases.openstack.org/yoga/schedule.html#y-cinder-driver-features-declaration | 14:04 |
simondodsley | jungleboyj: too early in the morning for that... | 14:04 |
* jungleboyj laughs | 14:05 | |
rosmaita | next item: yoga os-brick release during R-7 week | 14:05 |
rosmaita | so, that's next week | 14:05 |
rosmaita | and to keep smcginnis happy, it is scheduled for thursday | 14:05 |
rosmaita | here is a handy dashboard for reviewers: http://tiny.cc/brick-patches | 14:06 |
jungleboyj | Bwah ha ha! | 14:06 |
rosmaita | so, not surprisingly, the review priorities over the next week are: 1. os-brick reviews, 2. stephenfin's alembic patches | 14:07 |
rosmaita | if anyone pings me with a review request, please indicate which os-brick or stephenfin patch you have reviewed | 14:07 |
rosmaita | "to get reviews, you need to do reviews" | 14:08 |
rosmaita | ok, also happening next week | 14:08 |
rosmaita | we will release from the stable branches during R-7 week | 14:08 |
rosmaita | whoami-rajat will talk more about that later | 14:08 |
rosmaita | now some stuff for the future | 14:08 |
rosmaita | (where the future is after next week) | 14:08 |
rosmaita | cinderclient release during R-5 week | 14:08 |
rosmaita | cinder feature freeze during R-5 week | 14:09 |
rosmaita | and ... Cinder 3rd Party CI Compliance Checkpoint around R-5 | 14:09 |
rosmaita | #link https://releases.openstack.org/yoga/schedule.html#y-cinder-ci-checkpoint | 14:09 |
rosmaita | about that ... you don't need me to tell you if your CI is working or not | 14:09 |
rosmaita | you should already know that | 14:10 |
rosmaita | any drivers declared 'unsupported' at RC-1 time, will be 'unsupported' in the yoga release | 14:10 |
rosmaita | so, if you don't want that to happen to you, take appropriate action now | 14:10 |
rosmaita | all the info you need is at the link above ^^ | 14:10 |
rosmaita | ok, then some other general events happening | 14:11 |
rosmaita | the TC is having a release cadence discussion tomorrow at 1600 utc | 14:11 |
rosmaita | #link http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026962.html | 14:11 |
rosmaita | there's probably a more recent email with a link to the videocong | 14:12 |
rosmaita | *videoconf | 14:12 |
rosmaita | if you are wondering what people are thinking, there is a long thread over 2 months: | 14:12 |
rosmaita | #link http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684.html | 14:12 |
rosmaita | #link https://lists.openstack.org/pipermail/openstack-discuss/2021-December/026137.html | 14:12 |
rosmaita | finally, Z cycle PTL self-nominations start next week | 14:13 |
rosmaita | they are always self-nominations, because if you could nominate other people ... well, you can imagine what would happen | 14:14 |
rosmaita | the nomination period will be 2022-02-08T23:45 through 2022-02-15T23:45 | 14:14 |
rosmaita | if you are curious about what being a PTL entails, you can look at the docs, or ask me or jungleboyj | 14:14 |
rosmaita | OK, that's it for announcements ... anyone have anything else people should be aware of? | 14:15 |
jungleboyj | Happy to answer questions. :-) | 14:15 |
jungleboyj | smcginnis is a resource as well. :-) | 14:15 |
rosmaita | yes, i only didn't mention him because he's not here | 14:16 |
rosmaita | but i'm sure he'd be happy to answer your questions if you PM him on irc | 14:16 |
rosmaita | ok, looks like no more announcements. | 14:18 |
rosmaita | just want to repeat two items: | 14:18 |
rosmaita | the review priorities over the next week are: 1. os-brick reviews, 2. stephenfin's alembic patches | 14:18 |
rosmaita | also, if anyone pings me with a review request, please indicate which os-brick or stephenfin patch you have reviewed | 14:18 |
rosmaita | i am completely serious about ^^ | 14:18 |
rosmaita | ok, let's move on | 14:18 |
rosmaita | Any tasks or ideas for Outreachy internships? | 14:18 |
rosmaita | don't think Sofia is here | 14:19 |
rosmaita | but the deadline to submit ideas is in one month (March 4) | 14:19 |
rosmaita | i think Sofia is away for this week and next | 14:20 |
rosmaita | i will look into what this would entail beyond having ideas and we can discuss next week | 14:20 |
agarwchh | rosmaita: can internship students pick the blueprints which has potential changes in cinder core | 14:21 |
rosmaita | #action rosmaita - info about Outreach internships | 14:21 |
rosmaita | agarwchh: i don't see why not | 14:21 |
rosmaita | the question is what support the cinder projects will give them in their work | 14:21 |
jungleboyj | ++ | 14:22 |
rosmaita | ok, agarwchh ... you are up next | 14:22 |
rosmaita | multiple volume group spec | 14:22 |
rosmaita | #link https://review.opendev.org/c/openstack/cinder-specs/+/821372 | 14:22 |
agarwchh | need to check on the multiple-volume-group spec, we got the spec updated. | 14:23 |
rosmaita | i took a quick look, the REST API section needs some more details | 14:23 |
rosmaita | also, i didn't think it was clear how you are going to prevent volumes being put into groups with conflicting requirements? | 14:23 |
agarwchh | We had put high level details which APIs will be impacted and what will be the new APIs | 14:24 |
rosmaita | i saw you responded to my question in a comment, but didn't see anything in the text | 14:24 |
simondodsley | I think I have to declare a vested interest in this spec | 14:24 |
rosmaita | agarwchh: i don't think you explicitly addressed the question of what will be in the group_id field in volume-show request for the new mv | 14:25 |
rosmaita | and what will be displayed there for an older mv but when the volume is in multiple groups | 14:25 |
rosmaita | because the older mv will not have a group list field | 14:25 |
agarwchh | group_id needs to be deprecated and replaced with groups, which will be the list of multiple associated group_id | 14:25 |
rosmaita | nope cannot do trhat | 14:25 |
rosmaita | *that | 14:25 |
rosmaita | please review the contributor docs about microversions | 14:26 |
agarwchh | introducing the new API microversion should help, | 14:26 |
agarwchh | for older version it will still return the single group | 14:27 |
agarwchh | in that case it should populate group_id | 14:27 |
rosmaita | with which group, though? | 14:27 |
agarwchh | rosmaita: the single group | 14:28 |
agarwchh | for older version it will be still 1-1 volume group | 14:28 |
rosmaita | someone can make a call to the API that supports mv 3.87 but ask for mv 3.22 | 14:28 |
rosmaita | you need to have a plan for a sensible response | 14:29 |
agarwchh | I need to check more on microversion how we can handle multiple scenarios, | 14:29 |
agarwchh | but overall i need to understand if we can start the work for this spec and plan for Z release | 14:30 |
rosmaita | well, it would be good to get the spec approved first | 14:30 |
rosmaita | you won't be allowed to merge any code until week R-1 | 14:31 |
agarwchh | sure, apart from microversion do you see any other open issues | 14:31 |
agarwchh | i can update the spec for those details | 14:31 |
rosmaita | well, yes, the whole issue of how you are going to decide which volumes can be in multiple groups, and which groups are ok for this | 14:31 |
rosmaita | that seems to be a really big deal | 14:32 |
rosmaita | the database and API work are easy, but i'm not clear on the logic | 14:32 |
agarwchh | sure, i have some details on that will add it to spec. | 14:32 |
rosmaita | ok, thanks | 14:32 |
agarwchh | thanks | 14:32 |
rosmaita | ok, any other comments | 14:32 |
agarwchh | nothing from my side | 14:34 |
rosmaita | thanks! let's move on to whoami-rajat | 14:34 |
rosmaita | #topic stable releases | 14:34 |
whoami-rajat | hi | 14:34 |
rosmaita | #link https://etherpad.opendev.org/p/cinder-stable-releases | 14:34 |
whoami-rajat | as rosmaita already mentioned, we are planning to do stable branch releases for last 3 releases i.e. victoria, wallaby and xena in the R-7 week which is same as of os-brick release | 14:35 |
whoami-rajat | I reviewed all of the patches and we are looking good, looks like most of the things in xena/wallaby were merged today | 14:36 |
whoami-rajat | I've created an etherpad to track all patches, so if you've something that you think is important to get in these releases, please do the appropriate backport and add the patch to the etherpad | 14:36 |
whoami-rajat | One question i had for dell team | 14:37 |
whoami-rajat | simondodsley gave a -1 on all of the dell patches in stable/xena regarding CI not running, was it running previously and stopped or it never ran on stable branches? | 14:38 |
rosmaita | not sure we have any dell people here | 14:39 |
whoami-rajat | ok | 14:40 |
whoami-rajat | i think that can be addressed on the patches in question | 14:40 |
simondodsley | i don't think they have ever run stable CIs | 14:40 |
simondodsley | that was why I raised the issue at the mid-cycle | 14:40 |
rosmaita | yeah, we haven't had that requirement previously, i don't think we can make it a requirement until Z | 14:40 |
jungleboyj | ++ | 14:40 |
jungleboyj | Yeah, we shouldn't be blocking patches on that right now. | 14:40 |
rosmaita | but it would be good for them to state explicitly on the review that the fix has been tested in the appropriate stable branch, etc. | 14:41 |
simondodsley | ++ | 14:41 |
whoami-rajat | ++ | 14:41 |
rosmaita | that goes for all proposed backports for vendor drivers ^^ | 14:41 |
rosmaita | #action rosmaita - email to vendor driver maintainers about explicitly test statement | 14:42 |
rosmaita | while i'm at it | 14:42 |
whoami-rajat | thanks rosmaita | 14:42 |
rosmaita | #action rosmaita - email to ML about driver compliance check upcoming | 14:42 |
rosmaita | np | 14:43 |
rosmaita | i notice that grenade seems to be broken in victoria, possibly also wallaby | 14:43 |
rosmaita | i didnt' have time to look at the ML this morning, is that a known issue? | 14:43 |
rosmaita | was just looking at https://review.opendev.org/c/openstack/cinder/+/827242 | 14:43 |
whoami-rajat | I saw the error related to devstack | 14:44 |
whoami-rajat | related to devstack not supporting py3.6 | 14:44 |
whoami-rajat | but it was merged in master, i think backports are proposed for stable branches | 14:44 |
rosmaita | you're right, i missed the error message | 14:45 |
rosmaita | "ERROR: This script does not work on Python 3.6 The minimum supported Python version is 3.7." | 14:45 |
rosmaita | ok, so same issue, will hopefully be fixed very soon | 14:45 |
whoami-rajat | so the victoria devstack patched failed at zuul https://review.opendev.org/c/openstack/devstack/+/827414 | 14:45 |
whoami-rajat | when it merged the gates should be unblocked | 14:45 |
whoami-rajat | merges | 14:46 |
rosmaita | great ... so people, no rechecks on stable branch patches until ^^ merges | 14:46 |
jungleboyj | ++ | 14:46 |
rosmaita | ok, thanks whoami-rajat | 14:47 |
whoami-rajat | np | 14:47 |
rosmaita | #topic operator survey -- resource count | 14:47 |
whoami-rajat | so that's all for stable branch release, stable cores can take a look at the etherpad for reviewing patches | 14:47 |
rosmaita | this is a followup from the midcycle last week | 14:48 |
rosmaita | geguileo needs to gather some data about number of volumes per project because it impacts dynamically determining usage | 14:48 |
rosmaita | (which is part of his quota redesign spec) | 14:48 |
rosmaita | here's what we came up with ... if you have comments, please let me know by tomorrow at 20:00 UTC | 14:49 |
rosmaita | https://rosmaita.wufoo.com/forms/cinder-resource-count-survey/ | 14:49 |
rosmaita | not sure geguileo is here | 14:49 |
geguileo | geguileo: he may be around | 14:50 |
rosmaita | hooray! | 14:50 |
rosmaita | my question is when should we close the survey? | 14:50 |
rosmaita | i think we need to give you time to look at the results before the PTG | 14:50 |
rosmaita | so you can decide on what direction to take with your spec | 14:50 |
geguileo | sounds good | 14:51 |
rosmaita | i think if we don't have an end date, people will procrastinate and not fill it in | 14:51 |
geguileo | definitely need an end-date for this purpose | 14:51 |
geguileo | so before PTG sounds good | 14:51 |
geguileo | 1 or 2 days earlier is enough | 14:51 |
rosmaita | oh, ok | 14:51 |
jungleboyj | Sounds good. | 14:52 |
rosmaita | let's make it wendesday of release week then | 14:52 |
rosmaita | that would be march 30 | 14:52 |
rosmaita | i will update the survey to say that it closes 1200 utc on 30 march | 14:53 |
rosmaita | ok, that's all i had | 14:54 |
rosmaita | #topic open discussion | 14:54 |
rosmaita | we need to pick a mypy patch of the week | 14:55 |
eharney | https://review.opendev.org/c/openstack/cinder/+/774288 is one option (RBD driver) | 14:57 |
rosmaita | ok, works for me | 14:57 |
eharney | e0ne left a comment there this morning i'm not sure i understand | 14:57 |
rosmaita | also, someone please look at this one: https://review.opendev.org/c/openstack/os-brick/+/786731 | 14:57 |
rosmaita | (already has one +2) | 14:57 |
jungleboyj | Looking. | 14:58 |
rosmaita | need a designated reviewer for https://review.opendev.org/c/openstack/cinder/+/774288 | 14:59 |
rosmaita | (other than me, i will review too) | 14:59 |
e0ne | eharney: please, ignore my previous comment for https://review.opendev.org/c/openstack/cinder/+/774288. I changed a vote | 14:59 |
rosmaita | e0ne: thanks for the quick response! | 14:59 |
eharney | great, thanks | 14:59 |
e0ne | np, I'm sorry for confusing you | 14:59 |
rosmaita | e0ne: do you want to remain as a reviewer for that patch? | 14:59 |
e0ne | rosmaita: I +2'ed on it | 15:00 |
rosmaita | \o/ | 15:00 |
rosmaita | thanks! | 15:00 |
rosmaita | ok, we are out of time | 15:00 |
rosmaita | thanks everyone | 15:01 |
jungleboyj | Thanks rosmaita ! | 15:01 |
whoami-rajat | thanks! | 15:01 |
rosmaita | don't forget: the review priorities over the next week are: 1. os-brick reviews, 2. stephenfin's alembic patches | 15:01 |
rosmaita | also, if anyone pings me with a review request, please indicate which os-brick or stephenfin patch you have reviewed | 15:01 |
rosmaita | #endmeeting | 15:01 |
opendevmeet | Meeting ended Wed Feb 2 15:01:59 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-02-02-14.00.html | 15:01 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-02-02-14.00.txt | 15:01 |
opendevmeet | Log: https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-02-02-14.00.log.html | 15:01 |
rosmaita | (i have to have the last word!) | 15:02 |
jungleboyj | Word | 15:02 |
rosmaita | :D | 15:03 |
*** dviroel is now known as dviroel|lunch | 16:09 | |
*** dviroel|lunch is now known as dviroel | 17:12 | |
*** dviroel is now known as dviroel|out | 21:22 | |
*** dasm|rover is now known as dasm|off | 22:01 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!