14:00:32 <rosmaita> #startmeeting cinder
14:00:33 <openstack> Meeting started Wed Dec 18 14:00:32 2019 UTC and is due to finish in 60 minutes.  The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:34 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:36 <smcginnis> o/
14:00:36 <openstack> The meeting name has been set to 'cinder'
14:00:37 <whoami-rajat> Hi
14:00:43 <rosmaita> #topic roll call
14:00:48 <cmurphy> o/
14:00:50 <rosmaita> hello everyone
14:01:13 <eharney> hi
14:01:15 <tosky> o/
14:01:35 <LiangFang> hi
14:02:21 <rosmaita> looks like we have a quorum
14:02:26 <rosmaita> #topic updates
14:02:49 <LiangFang> o/
14:02:50 <rosmaita> the next 2 wednesdays are holidays in various places
14:03:11 <enriquetaso> o/
14:03:38 <rosmaita> so i'd like to propose not meeting and having the next meeting on 8 january 2020
14:03:46 <rosmaita> but, that is a long time
14:03:57 <rosmaita> so i'm open to hearing other opinions
14:04:00 <jungleboyj> o/
14:04:12 <eharney> that plan works for me
14:04:14 <rosmaita> though, personally, my family will be upset if we meet on 25 december
14:04:15 <m5z> +1
14:04:20 <jungleboyj> +1
14:04:45 <rosmaita> ok, sounds like no one is upset by lack of meetings
14:04:53 <rosmaita> i'll send something out to the ML
14:04:53 <jungleboyj> :-)
14:04:56 <LiangFang> +1
14:05:29 <rosmaita> also personally speaking, i will be offline a lot from 20 dec until 2 january
14:05:52 <rosmaita> and i think a lot of other cores are in a similar situation
14:06:04 <rosmaita> so review speed may be slowed a bit, please be patient
14:06:44 <rosmaita> ok, next item is stable branch releases
14:06:54 <rosmaita> just a reminder that we keep track of them here:
14:07:08 <rosmaita> #link https://etherpad.openstack.org/p/cinder-releases-tracking
14:07:38 <smcginnis> Sorry, a little late, but fyi I will be mostly out Dec 20 to Jan 2 as well.
14:07:40 <rosmaita> the release patches are linked there if you're super curious about what's in the propsed releases
14:07:54 <jungleboyj> Me as well.
14:08:05 <tosky> if I may, can we also have a new release of cinder-tempest-plugin (which is branchless, but it has releases) *after* we merge https://review.opendev.org/#/c/696610/ ?
14:08:10 <rosmaita> that will really slow review velocity!
14:08:24 <tosky> (if you think it was a shameless way to advertise that review, yes, it was)
14:08:35 <rosmaita> tosky: thanks for reminding me, i have not been paying attention to the plugin releases
14:09:08 <rosmaita> tosky just needs one more +2 on that review: https://review.opendev.org/#/c/696610/
14:09:33 <rosmaita> tosky: i'll put up a release patch as soon as that merges
14:09:34 <tosky> I guess that 0.3.1 would be fine as version number for it
14:09:37 <tosky> thanks!
14:09:51 <rosmaita> thank you
14:10:24 <rosmaita> in case people haven't noticed, tosky has been doing a lot of work organizing our zuul testing lately
14:10:35 <smcginnis> ++
14:10:40 <smcginnis> Thanks for all the work tosky!
14:10:51 <whoami-rajat> Thanks tosky , appreciate the work!
14:10:56 <jungleboyj> ++
14:11:00 <tosky> I added a point to the agenda to provide an update about the zuul v3 work
14:11:22 <rosmaita> ok, great, you can give us an update later
14:11:36 <rosmaita> ok, that's all for announcements
14:11:47 <rosmaita> #toipic policy popup team
14:11:57 <rosmaita> oops
14:12:08 <rosmaita> #topic  policy popup team
14:12:14 <rosmaita> cmurphy: that's you
14:12:16 <cmurphy> hi o/
14:13:00 <cmurphy> it's very early days, but with the policy popup team becoming official i wanted to stop in before the holidays and get you guys thinking about how you'd like to organize and track the work
14:13:12 <cmurphy> #link https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popup_Team
14:13:42 <cmurphy> some teams have specs or wiki pages for design documents, tracking could be done with storyboard, launchpad, an etherpad...
14:13:51 <cmurphy> whatever makes sense for this team
14:14:01 <rosmaita> we will probably use etherpad and launchpad
14:14:29 <cmurphy> sounds great
14:14:58 <rosmaita> are you planning to have meetings or just work over ML?
14:15:50 <cmurphy> would you like to have meetings? i was hoping not to have meetings but the barbican team also expressed interest in meeting
14:16:10 <rosmaita> no, my question was really just to make sure i didn't miss an email about meetings
14:16:15 <rosmaita> i am happy not to have meetings
14:16:37 <cmurphy> haha okay so far i haven't set up any meetings, you haven't missed anything
14:16:48 <rosmaita> my other question is that this would be mostly planning and thinking during ussuri -- this isn't a stealth community goal for ussuri, is it?
14:17:17 <cmurphy> i am hoping that at least a few of the teams make decent progress during ussuri
14:17:27 <cmurphy> if cinder isn't one of them that's okay
14:17:57 <cmurphy> planning is still progress
14:18:01 <rosmaita> ok, great
14:18:16 <rosmaita> i have the action item from our PTG to follow up on this
14:18:44 <rosmaita> my main concern is to understand what the impact on cinder is
14:18:56 <rosmaita> and then hand off the work to someone else
14:19:41 <rosmaita> but our team goal is to be clear on where the openstack in general is going on this so we can be in sync
14:20:07 <rosmaita> anyone have questions for cmurphy ?
14:20:27 <cmurphy> if you have any questions later i'll be lurking in your channel or you can ping me in #openstack-dev
14:20:49 <rosmaita> great, thanks for dropping by to keep us on track
14:21:19 <cmurphy> and if you could update the wiki page with any links under the design documents section or progress section that would help me a lot
14:21:38 <rosmaita> ok, i'll get something up there
14:21:44 <cmurphy> thanks rosmaita
14:21:45 <rosmaita> soon-ish
14:22:02 <rosmaita> #topic ceph job has been busted on stable/pike for awhile, fix or delete?
14:22:14 <rosmaita> #link http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011632.html
14:22:50 <rosmaita> the ceph job on stable/pike has been broken for awhile
14:23:01 <rosmaita> fixing it would require some backports
14:23:30 <rosmaita> consensus in that thread so far is to just drop the job from pike and probably ocata
14:23:33 <eharney> if it's non-voting anyway, then i guess turning it off is not terrible, we aren't backporting much to pike at this point
14:23:53 <tosky> but we decided to keep pike alive for a while
14:24:00 <tosky> isn't it https://review.opendev.org/#/c/684756/ enough?
14:24:24 <eharney> if so, then sure, no problem with just fixing it
14:25:29 <rosmaita> it does seem to make the ceph job pass
14:25:56 <jungleboyj> Guess it depends on whether people want to continue to support it.
14:27:13 <rosmaita> well, it looks like matt at least is interested in supporting it a bit
14:27:29 <rosmaita> i'll review that patch and reply to the ML encouraging his efforts
14:28:21 <rosmaita> #topic cinder-specs and the Swedish University Engagement Program
14:28:44 <rosmaita> #link http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011407.html
14:29:11 <rosmaita> don't have much to say here
14:29:24 <rosmaita> we have some specs in review sort of languishing
14:29:48 <rosmaita> i'd like to encourage people to get them cleaned up a bit
14:29:56 <rosmaita> we can put them in the untargeted section
14:30:02 <rosmaita> and see if someone can pick them up
14:30:06 * jungleboyj will try to take a look at those.  :-)
14:30:40 <rosmaita> my point is that if you personally have proposed a spec, or have an idea but no implementation time likely
14:30:55 <rosmaita> it would be good to get the spec to the point where someone else could grab it
14:31:12 <rosmaita> because there may be some students looking for work to do
14:32:14 <rosmaita> and on the topic of specs
14:32:27 <rosmaita> LiangFang: i'll get comments on your ssd caching spec today
14:32:32 <rosmaita> sorry about the delay
14:32:56 <rosmaita> i think except for that one, i've got comments on all the open specs
14:33:11 <rosmaita> (ping me if that's not the case)
14:33:30 <rosmaita> #topic wiki -> docs
14:33:35 <rosmaita> this is a quick one
14:33:48 <rosmaita> i was looking at a bug that cited the wiki as a reference
14:33:59 <tosky> and you want to nuke it?
14:34:01 <rosmaita> the page in question hadn't been updated since 2013
14:34:22 <rosmaita> well, i don't know if i can nuke a wiki page
14:34:35 <rosmaita> i don't have permissions to perma-delete anything
14:34:48 <tosky> it can be emptied and its content replaced with a link to the new location
14:35:01 <rosmaita> that's sort of what i was getting at
14:35:19 <jungleboyj> rosmaita: ++
14:35:26 <rosmaita> the problem with a complete empty is that sometimes there's stuff in there that hasn't made it to the "real" docs
14:35:42 <rosmaita> so i'd say, only empty a page if you have reviewed it carefully
14:35:56 <rosmaita> otherwise, please take a minute to edit it, sort of like this page:
14:36:08 <rosmaita> #link https://wiki.openstack.org/wiki/Cinder-multi-backend
14:36:22 <tosky> or https://wiki.openstack.org/wiki/CinderSupportMatrix ?
14:36:41 <rosmaita> exactly
14:37:27 <rosmaita> the wiki comes up a lot in google searches
14:37:34 <whoami-rajat> historical purposes
14:37:54 <rosmaita> so if you do see an outdated page, please add a link or a notice or whatever is appropriate
14:38:10 <rosmaita> or, if it's something we should have in the "real" docs,
14:38:20 <rosmaita> file a bug and tag "documentation"
14:38:42 <rosmaita> anyway, just a reminder
14:39:04 <rosmaita> #topic Status of Zuul v3 migration
14:39:10 <rosmaita> tosky: that's you
14:39:38 <tosky> there are a few open reviews which changes the legacy jobs into native Zuul v3 ones
14:39:42 <tosky> * https://review.opendev.org/#/c/672804/ (cinder-tempest-plugin)
14:39:45 <tosky> * https://review.opendev.org/#/c/697385/ (os-brick, depends on the previous review)
14:40:04 <tosky> * https://review.opendev.org/#/c/671945/ (cinder, WIP because I was hoping to fix another legacy job, but it can be make official)
14:40:36 <tosky> after those patches are merged (and backported when it makes sense, which means cinder and os-brick), what's left?
14:41:05 <tosky> * grenade jobs: the work on native grenade jobs restarted like yesterday, I need to resolve a new failure, but hopefully they should arrive soon
14:41:13 <tosky> (and I will take care of updating cinder as well)
14:41:19 <rosmaita> i think you are also working on the cinderlib jobs?
14:41:53 <tosky> cinderlib is fully zuulv3, I just need to fix the existing jobs so that they use the run-cinderlib-role
14:41:57 <rosmaita> looks like the cinderclient doesn't have any legacy jobs to deal with
14:42:14 <tosky> yes, I already fixed cinderclient a few months ago
14:42:27 <rosmaita> ah, that's why there's nothing to do :)
14:42:36 <tosky> the other reamin legacy job is legacy-dsvm-multibackend-matrix, which is a bit tricky, will work on it after grenade
14:43:02 <tosky> it does something that other jobs don't do (test, change configuration, retest), but it's a useful pattern
14:43:18 <tosky> I have a few questions for you all:
14:43:31 <tosky> * are there any other cinder components? It looks like "no" a this point
14:43:32 <whoami-rajat> tosky, i think there are only those 3 legacy jobs in cinder that all depends on grenade ?
14:43:51 <tosky> whoami-rajat: 3 grenade defined there, and another one defined in project-config
14:44:12 <tosky> I'm mentioning "backporting" many times because it's the only way to clean up those jobs from project-config
14:44:28 <whoami-rajat> tosky, oh, wasn't aware of the project-config one
14:44:41 <tosky> (hence my questions about which branches should be kept alive, because most probably we can't go back further than pike)
14:45:33 <tosky> the other question is: right now the cinder-tempest-plugin lio jobs, the devstack-plugin-ceph job, etc, all run all the tempest tests, including the API tests for the other components
14:45:55 <tosky> would it make sense to reduce them (removing for example networking jobs)? Or should we keep them? And which ones?
14:46:14 <tosky> just tempest.api.volume, tempest.scenario and of course cinder-tempest-plugin, or something else as well?
14:47:33 <tosky> and that's it
14:47:53 <rosmaita> when gmann introduced the integrated-storage job, that narrowed down some coverage
14:47:55 <whoami-rajat> tosky, don't we have few volume tests under tempest.api.compute ? not sure
14:48:18 <tosky> right, I could steal that configuration
14:48:33 <rosmaita> yeah, maybe we can review that first
14:48:44 <tosky> whoami-rajat: there are some, yes
14:48:44 <rosmaita> compute and networking are pretty important for us
14:48:48 <whoami-rajat> tosky, https://github.com/openstack/tempest/tree/master/tempest/api/compute/volumes
14:49:00 <tosky> oh, ok, also networking
14:49:20 <rosmaita> so while i'd like to have faster tests, i'm a bit wary about reducing coverage too much
14:49:25 <tosky> please note I'm talking about tempest.api.network
14:49:28 <tosky> not the scenario tests
14:49:46 <tosky> the specific cinder settings shouldn't really change the result of the network API tests
14:50:05 <rosmaita> that's true
14:50:40 <rosmaita> i think we could break some compute api stuff though
14:51:28 <tosky> this is the storage blacklist: https://opendev.org/openstack/tempest/src/branch/master/tools/tempest-integrated-gate-storage-blacklist.txt
14:52:39 <rosmaita> that looks pretty safe
14:54:09 <tosky> oki, I will see if it's possible to use it without duplicating it
14:54:25 <rosmaita> that would be great
14:55:28 <rosmaita> thanks for all your work on this, tosky
14:55:31 <rosmaita> anything else?
14:55:44 <jungleboyj> ++
14:55:46 <tosky> nothing else for now
14:55:52 <whoami-rajat> thanks tosky
14:55:55 <rosmaita> ok, thanks again
14:55:59 <rosmaita> #topic open discussion
14:56:23 <rosmaita> anyone?
14:56:45 <jungleboyj> Merry Christmas and Happy New Year!
14:57:16 <rosmaita> i should mention that e0ne mentioned that he couldn't be here today, but he's been working on reviewing 3rdPartyCI about who's running the cinder-tempest-plugin
14:57:28 <tosky> oh, nice
14:57:35 <rosmaita> he thinks he'll have some results to share later this week
14:57:52 <rosmaita> jungleboyj: ++
14:58:10 <rosmaita> and best wishes for any other holidays people may be celebrating
14:58:12 <jungleboyj> rosmaita:  That is good.
14:58:41 <rosmaita> ok, so this is our last cinder meeting of 2019 -- thanks for a great year, everyone
14:58:47 <LiangFang> Merry Christmas and Happy New Year! We will have a long time that no much meeting in daily work.
14:58:48 <rosmaita> next meeting will be 8 january 2020
14:58:55 <smcginnis> Thanks everyone!
14:59:02 <tosky> thanks! Happy holidays for anyone celebrating!
14:59:09 <jungleboyj> Thanks for another great year everyone!
14:59:11 <whoami-rajat> Merry Christmas and a Happy new year. Enjoy the vacations!
14:59:30 <walshh_> Thanks to everyone for all your help during the year.  Nollaig Shona duit!
14:59:40 <smcginnis> Happy Festivus for the rest of us.
14:59:56 <rosmaita> time's up, no airing of grievances
15:00:02 <rosmaita> #endmeeting