Wednesday, 2020-11-18

*** jkulik has quit IRC00:02
*** jkulik has joined #openstack-meeting-alt00:02
*** eharney has quit IRC00:29
*** vishalmanchanda has quit IRC00:41
*** eharney has joined #openstack-meeting-alt00:43
*** rcernin has quit IRC01:43
*** rcernin has joined #openstack-meeting-alt02:20
*** rcernin has quit IRC02:24
*** rcernin has joined #openstack-meeting-alt02:28
*** rcernin has quit IRC02:31
*** rcernin has joined #openstack-meeting-alt02:32
*** yamamoto has quit IRC04:14
*** yamamoto has joined #openstack-meeting-alt04:14
*** yamamoto has quit IRC04:19
*** yamamoto has joined #openstack-meeting-alt04:19
*** zzzeek has quit IRC04:24
*** zzzeek has joined #openstack-meeting-alt04:25
*** yamamoto has quit IRC04:30
*** yamamoto has joined #openstack-meeting-alt04:43
*** zzzeek has quit IRC04:46
*** zzzeek has joined #openstack-meeting-alt04:49
*** yamamoto has quit IRC04:59
*** yamamoto has joined #openstack-meeting-alt05:03
*** yamamoto has quit IRC05:03
*** yamamoto has joined #openstack-meeting-alt05:03
*** yamamoto has quit IRC05:08
*** zzzeek has quit IRC05:47
*** zzzeek has joined #openstack-meeting-alt05:48
*** vishalmanchanda has joined #openstack-meeting-alt06:00
*** miniroy has quit IRC06:05
*** gyee has quit IRC06:08
*** yamamoto has joined #openstack-meeting-alt07:07
*** yamamoto has quit IRC07:18
*** yamamoto has joined #openstack-meeting-alt07:21
*** yamamoto has quit IRC07:22
*** ralonsoh has joined #openstack-meeting-alt07:31
*** slaweq has joined #openstack-meeting-alt07:43
*** yamamoto has joined #openstack-meeting-alt07:58
*** yamamoto has quit IRC08:12
*** lbragstad_ has joined #openstack-meeting-alt08:18
*** lbragstad has quit IRC08:22
*** tosky has joined #openstack-meeting-alt08:45
*** rcernin has quit IRC08:52
*** derekh has joined #openstack-meeting-alt09:10
*** rcernin has joined #openstack-meeting-alt09:15
*** slaweq has quit IRC09:17
*** slaweq has joined #openstack-meeting-alt09:19
*** rdopiera has joined #openstack-meeting-alt09:31
*** e0ne has joined #openstack-meeting-alt09:38
*** rcernin has quit IRC09:45
*** rcernin has joined #openstack-meeting-alt09:55
*** zzzeek has quit IRC09:56
*** zzzeek has joined #openstack-meeting-alt09:59
*** michael-mcaleer has joined #openstack-meeting-alt10:03
*** michael-mcaleer has quit IRC10:08
*** michael-mcaleer has joined #openstack-meeting-alt10:13
*** michael-mcaleer has quit IRC10:17
*** kevinz has quit IRC10:26
*** michael-mcaleer has joined #openstack-meeting-alt10:28
*** michael-mcaleer has quit IRC10:36
*** belmoreira has joined #openstack-meeting-alt10:46
*** michael-mcaleer has joined #openstack-meeting-alt11:02
*** lpetrut has joined #openstack-meeting-alt11:10
*** rcernin has quit IRC11:18
*** rcernin has joined #openstack-meeting-alt11:19
*** rcernin has quit IRC11:27
*** baojg has quit IRC11:30
*** baojg has joined #openstack-meeting-alt11:31
*** rcernin has joined #openstack-meeting-alt11:33
*** slaweq has quit IRC11:39
*** yamamoto has joined #openstack-meeting-alt11:39
*** e0ne has quit IRC11:44
*** slaweq has joined #openstack-meeting-alt11:45
*** rcernin has quit IRC11:46
*** rcernin has joined #openstack-meeting-alt11:52
*** rcernin has quit IRC11:55
*** zzzeek has quit IRC12:13
*** zzzeek has joined #openstack-meeting-alt12:16
*** e0ne has joined #openstack-meeting-alt12:18
*** zzzeek has quit IRC12:27
*** zzzeek has joined #openstack-meeting-alt12:28
*** sfernand has joined #openstack-meeting-alt12:37
*** yamamoto has quit IRC12:43
*** baojg has quit IRC12:48
*** baojg has joined #openstack-meeting-alt12:49
*** enriquetaso has joined #openstack-meeting-alt13:01
*** masahito has joined #openstack-meeting-alt13:03
*** yamamoto has joined #openstack-meeting-alt13:05
*** yamamoto has quit IRC13:05
*** yamamoto has joined #openstack-meeting-alt13:05
*** yamamoto has quit IRC13:10
*** yamamoto has joined #openstack-meeting-alt13:26
*** yamamoto has quit IRC13:26
*** yamamoto has joined #openstack-meeting-alt13:27
*** yamamoto has quit IRC13:31
*** rosmaita has joined #openstack-meeting-alt13:45
*** e0ne has quit IRC13:51
*** masahito has quit IRC13:52
*** sangeet has quit IRC13:52
*** rafaelweingartne has joined #openstack-meeting-alt13:53
*** sangeet has joined #openstack-meeting-alt13:55
*** zoharm has joined #openstack-meeting-alt13:57
*** abishop has joined #openstack-meeting-alt13:58
*** masahito has joined #openstack-meeting-alt13:58
*** ChuckPiercey has joined #openstack-meeting-alt13:58
*** ChuckPiercey has quit IRC13:59
*** ChuckPiercey has joined #openstack-meeting-alt13:59
*** geguileo has joined #openstack-meeting-alt14:00
rosmaita#startmeeting cinder14:00
openstackMeeting started Wed Nov 18 14:00:45 2020 UTC and is due to finish in 60 minutes.  The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: cinder)"14:00
openstackThe meeting name has been set to 'cinder'14:00
rosmaita#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: cinder)"14:00
rafaelweingartne\o14:00
*** e0ne has joined #openstack-meeting-alt14:01
abishopo/14:01
eharneyhi14:01
michael-mcaleerhi14:01
sfernandhi14:01
whoami-rajat__Hi14:01
e0nehi14:01
jungleboyjo/14:01
ChuckPierceyHi14:01
zoharmo/14:02
geguileohi! o/14:02
lsekio/14:02
rosmaitalooks like a good turnout14:03
rosmaita#link https://etherpad.openstack.org/p/cinder-victoria-meetings14:03
rosmaitaok, let's get started14:03
ChuckPierceyTopic: a couple of KIOXIA dev team questions14:03
rosmaita#topic announcements14:03
*** openstack changes topic to "announcements (Meeting topic: cinder)"14:03
enriquetasohi14:03
rosmaitaChuckPiercey: you are on the agenda for later14:03
rosmaitahi sofia!14:03
rosmaitahope your exams went well14:04
enriquetasoo/ :)14:04
enriquetasothanks!14:04
rosmaitareminder: next week's meeting (last meeting of the month) is videoconference14:04
rosmaitait will be recorded in bluejeans as usual, unless there are any objections?14:04
rosmaitai will send out connection info to the ML (though it has not changed from last time)14:04
*** thgcorrea has joined #openstack-meeting-alt14:04
rosmaita#topic announcements - upcoming events14:05
*** openstack changes topic to "announcements - upcoming events (Meeting topic: cinder)"14:05
rosmaitathis week is R-2114:05
rosmaitaWallaby Milestone-1 is at R-19 (yes, in 2 weeks)14:05
rosmaitai want to set some priorities for the next 2 weeks14:05
rosmaitapriority for M-1: adding mypy type-checking14:05
rosmaitahere are the patches14:05
rosmaita#link https://review.opendev.org/#/q/topic:mypy+(status:open+OR+status:merged)+project:openstack/cinder14:06
rosmaitathis is an important code quality initiative14:06
rosmaitaand it has been languishing despite the best efforts of eharney14:06
rosmaitaso, i propose that each cinder core will take over one of these patches14:06
rosmaitaexcept eharney, of course, but he will be available to answer questions that come up14:07
eharneyi'll bump those in merge conflict today14:07
rosmaitai was going to propose that whoever takes over the patch should fix the merge conflict14:07
eharneythat also works14:07
rosmaitaso this will be slightly weird, a reviewer will also be  a committer14:08
*** macz_ has joined #openstack-meeting-alt14:08
rosmaitabut i think that is the best way to handle minor changes14:08
rosmaitaand if a reviewer decides to make a major change, then they can't +2 the patch, but they can still be "in charge" of getting it merged14:08
rosmaitaso we will need to use common sense here14:08
rosmaitaso, to save people the embarrassment of volunteering, here's my proposal:14:09
rosmaitamypy: driver.py   https://review.opendev.org/736856   hemna14:09
rosmaitamypy: annotate volume manager   https://review.opendev.org/733621      whoami-rajat14:09
rosmaitamypy: annotate volume_utils / utils / exc   https://review.opendev.org/736855   rosmaita14:09
rosmaitamypy: annotate remotefs   https://review.opendev.org/733623   lseki14:09
rosmaitamypy: annotate lvm   https://review.opendev.org/733624   geguileo14:09
rosmaitamypy: annotate api.py    https://review.opendev.org/733622    rosmaita14:09
rosmaitaok, e0ne don't feel left out, you are heading up the v2 removal effort14:09
rosmaitaand you will likely be bugged for reviews14:10
e0nerosmaita: I'm sorry, I was busy with our internal release last week14:10
rosmaitais everyone clear on what i am asking for here?14:10
rosmaitae0ne: no need to apologize14:10
e0neso there were no community activity from my side14:10
rosmaitaummmm ... i could use an 'ack' from hemna whoami-rajat__ lseki geguileo ^^14:11
geguileorosmaita: yes, to do a massive downvote of eharney's patches, right?14:11
whoami-rajat__ack14:11
lsekiack 👍14:11
eharneygeguileo: no need to frown, just turn that downvote upside-down14:11
rosmaitathere you go14:12
geguileoeharney: rofl14:12
jungleboyj:-)14:12
*** linshiyx has joined #openstack-meeting-alt14:12
rosmaitajungleboyj and smcginnis, i suspect you will be bugged for reviews14:12
rafaelweingartnehello guys, are we going to have an open floor topic? I would like to ask your guidance in a patch that has been open for quite a while for Cinder14:12
jungleboyjrosmaita:  ++ Can do.14:12
*** simondodsley has joined #openstack-meeting-alt14:12
*** macz_ has quit IRC14:12
rosmaitarafaelweingartne: hopefully later in the meeting14:13
rosmaitacommunity goals are looking OK, details are on the agenda14:13
rafaelweingartnerosmaita: thanks :)14:13
rosmaitae0ne is heading up v2 removal, which we would like to have completed before M-214:14
rosmaitahe can maybe talk about that next week?14:14
e0nerosmaita: sounds good to me14:14
e0neneed to figure out what is going with grenade without v214:14
rosmaitagreat!14:14
rosmaita#topic announcements - midcycle14:14
*** openstack changes topic to "announcements - midcycle (Meeting topic: cinder)"14:14
rosmaitayeah, grenade will be ... interesting14:14
rosmaitaok the midcycle is supposed to be before specs freeze, which is coming up fast also14:15
rosmaitahere is my proposal:14:15
rosmaitahold it on Wednesday 9 December, 2 hours either 1300-1500 or 1400-160014:15
rosmaitathat way it overlaps with a time everyone has reserved on wednesday already14:15
rosmaitaso i expect most people will at least be able to attend for an hour14:16
e0ne+114:16
jungleboyjI would vote for 14:00 to 16:00.14:16
rosmaitaanyway, please check your calendars and we can verify/vote on a time next week14:16
jungleboyj++14:16
lseki++14:17
rosmaitaok and just to have it in the minutes:14:17
rosmaita"All Cinder Specs for features to be implemented in Wallaby must be approved by Friday 18 December 2020 (23:59 UTC)."14:17
rosmaitaand finally14:17
rosmaitaWallaby Milestone-2 is at R-12  (week of 18 January)14:17
rosmaitaok, but the big effort is getting mypy merged before M-114:18
rosmaitaand i forgot to mention the other part of my proposal about that14:18
rosmaitaanyone who asks for reviews in #openstack-cinder and has not reviewed one of the mypy patches will be shunned14:18
rosmaita#link https://review.opendev.org/#/q/topic:mypy+(status:open+OR+status:merged)+project:openstack/cinder14:18
rosmaitathe mypy patches for reference ^^14:19
rosmaitaok, that's all for announcements14:19
rosmaita#topic bug review14:19
*** openstack changes topic to "bug review (Meeting topic: cinder)"14:19
rosmaitamichael-mcaleer: that's you14:19
michael-mcaleerthanks rosmaita14:19
michael-mcaleer6 bugs this week, all in cinder (3 x cinder, 1 x enhancement, 1 x doc, 1 x driver)14:19
michael-mcaleercinder first14:19
michael-mcaleerCinder backup error using Erasure Code Pool #link https://bugs.launchpad.net/cinder/+bug/190371314:19
openstackLaunchpad bug 1903713 in Cinder "Cinder backup error using Erasure Code Pool" [Undecided,New]14:19
michael-mcaleerNot immediately obvious what is going on here, asked for more info from submitter14:20
michael-mcaleerimportance also not set, anyone have a suggestion on that?14:20
rosmaitae0ne: can you look at this one? ceph + backup, kind of in your domain there14:21
e0nerosmaita: sure, will take a look on it asap14:22
rosmaitaty!14:22
michael-mcaleerok next bug14:22
michael-mcaleercinder backup-import command fails, there is no way to repeat it #link https://bugs.launchpad.net/cinder/+bug/190369714:22
openstackLaunchpad bug 1903697 in Cinder "cinder backup-import command fails, there is no way to repeat it" [Undecided,Incomplete]14:22
michael-mcaleeragain not a lot of info provided here but its possible to discern what is going on in advance of logs coming back from submitter14:22
michael-mcaleerassume low importance because user can just change name of backup14:23
rosmaitasounds correct14:23
michael-mcaleerok, last cinder bug14:23
e0neI can check it with the latest master14:23
michael-mcaleerCinder backup - Volume metadata inconsistency #link  https://bugs.launchpad.net/cinder/+bug/190383914:23
openstackLaunchpad bug 1903839 in Cinder "Cinder backup - Volume metadata inconsistency" [Medium,Confirmed]14:23
michael-mcaleeropened by powermax team, our QE team spotted this in April and we are only getting round to investigating now14:24
eharneythis driver might be making invalid assumptions about how volume metadata works14:24
michael-mcaleermetadata is assumed to be unique to each volume here14:24
e0neit's a Backup Bug Day14:24
eharneyi don't think it's a bug that restoring a volume from backup restores its metadata14:25
rosmaita:)14:25
eharneyalso, this is end-user metadata and info used by the driver probably shouldn't be in that field14:25
michael-mcaleerok, im going to stay on topic of bugs and we can discuss the ins and outs of this one in a bug review, save some time14:25
eharneyyeah14:25
michael-mcaleernext up is an enhancement14:26
michael-mcaleerCinder - volume show for GVG #link https://bugs.launchpad.net/cinder/+bug/190384514:26
openstackLaunchpad bug 1903845 in Cinder "Cinder - volume show for GVG" [Wishlist,Triaged]14:26
michael-mcaleerConsider updating volume properties when its added to an Generic Volume Group.14:26
eharneymakes sense to consider since we do it w/ CGs14:26
michael-mcaleerthere is consistency group ID in there but no GVGs14:26
michael-mcaleeryeah14:26
michael-mcaleerset to enhancement/wish14:27
rosmaitasounds good14:27
michael-mcaleerlast cinder related bug is docs... Rocky Series Release Notes in Cinder Release Notes #link https://bugs.launchpad.net/cinder/+bug/190421914:27
openstackLaunchpad bug 1904219 in Cinder "Rocky Series Release Notes in Cinder Release Notes" [Low,Confirmed]14:27
michael-mcaleersimple fix here, incorrect designation of code snippet in the release notes14:27
*** tmazur has joined #openstack-meeting-alt14:27
michael-mcaleerand lastly the driver bug opened by ibm... os_type changed to 'linux' in python3 #link https://bugs.launchpad.net/cinder/+bug/190364814:28
openstackLaunchpad bug 1903648 in Cinder "os_type changed to 'linux' in python3" [Low,Triaged]14:28
michael-mcaleeragain a small fix here, ive set the tags for ibm so hopefully they see if if they didnt open it themselves14:28
smcginnisWe can't update old release notes, otherwise they show up as new. There's also an outstanding bug in reno that may be causing that one.14:28
rosmaitasmcginnis: thanks, the moral of the story is to make sure command line text is wrapped in `` in the releasenotes14:29
rosmaita(for future reviewers)14:30
rosmaitaok, thank you  michael-mcaleer14:30
michael-mcaleerwill I close that bug out and advise submitter on updating of release notes?14:30
michael-mcaleerno prob, thats all from me this week, thanks rosmaita14:30
rosmaitamichael-mcaleer: yes, that sounds good14:30
rosmaita#topic stable releases14:30
*** openstack changes topic to "stable releases (Meeting topic: cinder)"14:30
rosmaitawhoami-rajat__: that's you14:30
whoami-rajat__Hi, just to provide an update on the patches to be merged before the stable release which we decided to be on 26th Nov14:31
whoami-rajat__#link https://etherpad.opendev.org/p/stable-releases-review-tracker14:31
rosmaitaoops, forgot to mention that in the updates14:31
whoami-rajat__a lot of patches were merged in the past week, thanks to all the reviewers14:31
whoami-rajat__victoria looks good to go, ussuri has 1 patch remaining, train has 4 patches in which there's a -1 on hemna 's patch from smcginnis14:32
whoami-rajat__hopefully all patches will be merged before next cinder meeting to meet the release deadline on time14:33
whoami-rajat__that's all from my side14:33
rosmaitaok, stable cores: ^^14:33
rosmaitathanks, whoami-rajat__14:33
rosmaita#topic marking config options as 'advanced'14:34
*** openstack changes topic to "marking config options as 'advanced' (Meeting topic: cinder)"14:34
rosmaitajust want to bring to people's attention that this is possible14:34
rosmaitauseful for config options that should only have their values changed for very specific reasons14:34
rosmaitaanyway, take a look at this patch and read my comment14:34
rosmaita#link https://review.opendev.org/#/c/744746/14:35
rosmaita#topic v2 support removal from cinderclient and last call for comments14:35
*** openstack changes topic to "v2 support removal from cinderclient and last call for comments (Meeting topic: cinder)"14:35
rosmaitai sent an announcement to the ML14:35
rosmaita#link http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018697.html14:35
rosmaitaand, there has been no response14:36
rosmaitaso we have the green light to remove v2 support from the python-cinderclient this release cycle14:36
rosmaitahooray!14:36
jungleboyjOnward!14:36
rosmaita#topic restricting supported Ceph versions14:36
*** openstack changes topic to "restricting supported Ceph versions (Meeting topic: cinder)"14:36
abishopI know there are patches submitted to puppet-cinder and tripleo to prepare for v2 removal14:36
rosmaitaok, i also sent an email out about this to the ML asking for comments on the review14:37
rosmaita#link https://review.opendev.org/#/c/762592/14:37
rosmaitabut hemna raised an interesting question14:37
rosmaitabtw, thanks for geguileo for also responding to a comment about this on the ML14:38
rosmaitaso, i was looking at this like an announcement for how people should behave14:38
rosmaitathat is, do not use unsupported ceph versions and expect it to work14:38
rosmaitabut, hemna pointed out that if we don't enforce it in code, they could do it anyway14:38
eharneyi think the main goal is in fact to just say "don't do that"14:39
geguileoeharney: +114:39
rosmaitathat was my thought, too, but i wanted to check14:39
eharneywhich is the current state of affairs today -- and i don't recall us ever having issues that came up because someone was using an older version of ceph that we don't test14:39
eharneyhowever14:39
smcginnisThen if someone comes along and says "hey, this doesn't work", we can point to the docs.14:39
geguileobut I'm ok adding a patch to check it14:39
eharneywe are adding some advisory messages around the v2 clone API that says "since you are using this old version, your performance is worse"14:39
jungleboyjRTFM.  ;-)14:40
geguileolol14:40
geguileoeharney: once that patch merges we can have another patch that removes those and does a check on the setup, right?14:40
rosmaitaok, i think advisory is good for now, and if something needs code validation, then we can still add it at the appropriate time14:41
eharneygeguileo: not sure, that one is less straightforward since it also requires backend configuration14:41
geguileoeharney: can't we just check the cluster version?14:41
eharneyno14:42
geguileoeharney: isn't that enough?14:42
eharneybecause they still have lower perf if they don't manually set some options14:42
eharneyand even if they set the options, it won't be applied retroactively to old images, etc14:42
geguileoeharney: ok, we cannot remove it, but we could barf if the ceph cluster version is not the right one14:43
geguileo(which is what hemna was asking for)14:43
eharneyi don't buy that failing because they are using an old ceph version really accomplishes much for us14:44
rosmaitaok, let's continue discussion of this on the patch14:44
rosmaita#topic replication support for nvme connector - code structure14:44
*** openstack changes topic to "replication support for nvme connector - code structure (Meeting topic: cinder)"14:44
rosmaitazoharm: that's you14:44
zoharmhi all14:44
zoharmso we are working on upgrading the NVMe connector to also do replication14:44
zoharmthe main question in the high level, how do we structure it in regards to the existing NVMe connector?14:45
zoharmfor example, is it ok to tag alone the raid functionality for the connect/disconnect methods, if the connection properties specify replication?14:46
zoharmin a sense, this means expanding the connector to have two modes, and do one depending on whether the nvme volumes to connect to are replicated14:47
zoharmdoes this sound like the right way?14:47
geguileozoharm: sorry, I'm not quite following14:47
zoharmare there any other suggestions or issues with this?14:47
geguileozoharm: do you have an example of the connection_info dict?14:48
geguileoit's probably easier for me to understand what you are actually proposing like that14:48
zoharmyes, so basically, if the connection_info dict has a field "volume_replicas" with connection info for each nvme device in it14:48
zoharmthen, put them into raid14:48
zoharmfor bare nvme its:14:49
zoharmconnection_info:14:49
zoharm  nqn14:49
zoharm  portal14:49
rafaelweingartneIt might be easier to write down a spec and propose it there. Then, the discussion can happen within a context, and maybe with some examples on what you want to accomplish14:49
geguileozoharm: That idea does sound good to me14:49
zoharmok, just to finish this part14:49
zoharmif connection info looks like this:14:49
zoharmconection_info:14:49
geguileozoharm: and it would not conflict with adding multipathing to the nvme connector later on14:49
zoharm  volume_repliacs:14:49
zoharm    nqn, etc...14:50
zoharmyep geguileo14:50
zoharmso multipathing will be handled under a "portals" field for each nvme device14:50
rosmaitais the question whether it's better to complicate the connect_volume function in current connector, or subclass it with a new connector that does replication?14:50
zoharmwhich can have multiple portals14:50
geguileoyeah, volume_replicas would be a list of connection_info that just doesn't have the volume_replicas in it14:50
zoharmrosmaita, in a way yes, and if subclassing is better, how to do it right?14:51
geguileoI think sublcassing is probably better for readability14:52
geguileothe base nvme-of class can just do simle connections14:52
zoharmtrue, though biggest benefit for readability is breaking up into re-usable functions (which are usable by both bare nvme and replicated)14:52
geguileoand the raid version inherits from it and handles the replicas with specific code, but calls the base nvme-of class for individual connections14:52
zoharmright, however, if a single volume backends supports both simple and replicated volumes, this complicates things14:53
zoharmadditionally, a new connector and libvirt volume driver needs to be named and registered14:53
*** cliffparsons has quit IRC14:53
geguileozoharm: why a new libvirt volume driver?14:53
geguileozoharm: can't we just create a new os-brick connector?14:53
zoharmyes, and then we will need to tell nova to use it somehow14:54
*** cliffparsons has joined #openstack-meeting-alt14:54
rosmaitazoharm: best thing would be to write the way you think is correct in the spec, and say in the alternatives section why you don't like the other option14:54
rosmaitathen we'll have a better basis for discussion14:54
zoharmas far as i saw, this means adding it to libvirt/drivers14:54
geguileozoharm: you are correct14:55
zoharmbecause current nvme connector is referenced in the same way in its own libvirt driver14:55
zoharmso to make this work we would need to just duplicate this whole wrapping, and just change one name14:55
zoharmthis is another tradeoff for this approach14:55
zoharmalso it requires a code submission to nova :)14:55
geguileozoharm: you don't need to replicate the wrapping, you can just reference the same class in nova/virt/libvirt/driver.py14:56
geguileobut with the name of the new connector14:56
geguileoin libvirt_volume_drivers14:56
geguileo'nvmeof-raid=nova.virt.libvirt.volume.nvme.LibvirtNVMEVolumeDriver'14:57
rosmaitazoharm: you also had another question?14:57
zoharmyes, the problem is in that libvirtnvmevolumedriver14:57
rosmaitaabishop: i think we will not get to your topic this week, but i will put you first for next week14:58
zoharmit hardcodes which connector to use it seems14:58
abishopstory of my life :-/14:58
zoharmrosmaita my other question is very quick14:58
abishopfolks can read etherpad and check out review in meantime14:58
zoharmbut anyway i will take this offline in favor of time14:58
rosmaitaok, thanks!14:58
zoharmother question is simple14:58
rosmaita#topic open discussion14:58
*** openstack changes topic to "open discussion (Meeting topic: cinder)"14:58
*** lbragstad_ is now known as lbragstad14:59
rafaelweingartnerosmaita: I just have a question regarding https://review.opendev.org/#/c/666886/. It is a patch that has been on the making for quite a while.14:59
geguileozoharm: on second thought, I think it's probably best to use the existing connector14:59
rafaelweingartneBefore solving the conflicts, we would like to understand what we are missing there. for instance, a formal specification14:59
rosmaitarafaelweingartne: i completely lost track of that one15:00
rosmaitalet me look it over and leave some comments15:00
rosmaitacheck back in a few days?15:00
rafaelweingartneok15:00
rafaelweingartnethanks15:00
rosmaitaand we are out of time ...15:00
rosmaitathanks, everyone15:00
rafaelweingartneno problem, take your time15:00
rosmaita#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Wed Nov 18 15:00:42 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-11-18-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-11-18-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-11-18-14.00.log.html15:00
zoharmcan we continue a bit in #openstack-cinder?15:01
rosmaitasure15:01
e0ne#startmeeting horizon15:01
openstackMeeting started Wed Nov 18 15:01:37 2020 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: horizon)"15:01
openstackThe meeting name has been set to 'horizon'15:01
e0nehi everybody15:02
rdopierahey15:02
vishalmanchandahi all15:02
*** abishop has left #openstack-meeting-alt15:02
amotokihi15:03
e0nelet's start15:05
e0ne#topic Notices15:05
*** openstack changes topic to "Notices (Meeting topic: horizon)"15:05
e0neI created a poll to select a new time for our weekly meeting15:05
e0ne#link https://doodle.com/poll/a5eeh6h3v356w8ss15:05
e0neit should contain 13.00 utc, 14.00 utc and 15.00 Tue-Thu15:06
e0neI removed 14.00 utc on Wednesday because there is a conflict with cinder meeting15:07
e0neI hope, we'll find a suitable time for everybody15:07
e0netmazur, rdopiera: thanks for your votes!15:08
e0neI checked release goals for Wallaby15:08
e0ne#link https://governance.openstack.org/tc/goals/selected/wallaby/index.html15:09
e0nethere aren't anything we should do in horizon15:09
*** rosmaita has quit IRC15:11
e0newe'll reach Wallaby-1 in two weeks15:11
amotokimigriation to YAML policy format may be related to us indirectly.15:11
e0ne#link https://releases.openstack.org/wallaby/schedule.html15:11
vishalmanchandayes15:11
e0neamotoki: I expect it will go smoothly for us15:13
e0nejson => yaml migration in python is pretty easy15:13
amotokie0ne: yes. my policy-in-code support patch will cover it.15:13
amotokithe point is to still try to look up policy.json.15:13
amotokiit is suggested in the community goal (while cinder does not do so)15:14
amotokiperhaps it is better to have such fallback logic in horizon too.15:15
e0negood point. it'll help us with upgrades15:16
amotokianyway https://review.opendev.org/#/c/750134/ will cover the migration path.15:16
*** rafaelweingartne has quit IRC15:18
e0neamotoki: great15:18
e0neaccording to wallaby-1 milestone15:20
*** lpetrut has quit IRC15:21
e0neit would be good to drop deprecated features until it and release the first version of horizon in Wallaby cycle15:21
amotoki+115:21
amotokiaccording to L.13 in https://etherpad.opendev.org/p/horizon-release-priorities, do we drop openstack_dashboard/wsgi/django.wsgi in this release?15:21
e0neI'm ok with it15:22
e0newe've got openstack_dashboard/wsgi.py for a while15:23
amotokiyes, it was added in rocky and enough time has passed.15:24
e0ne+115:24
*** rosmaita has joined #openstack-meeting-alt15:24
e0neI +2'ed patches with OPENSTACK_NOVA_EXTENSIONS_BLACKLIST removal today15:24
e0nethe same for legacy neutron API usage15:25
amotokithanks. it is a long way :)15:25
e0ne#link https://review.opendev.org/#/c/759652/15:25
e0neamotoki: I hope, contrail/tsungen fabric plugin will be fixed in Wallaby to use a new APIs15:26
e0newe waited too long to not remove it from horizon15:26
amotokitotally agree15:27
e0neI thinks, that's all announcements this week15:27
e0ne#topic Bug deputy report15:28
*** openstack changes topic to "Bug deputy report (Meeting topic: horizon)"15:28
e0neamotoki: did you add that bugs into  the etherpad?15:28
amotokie0ne: yes. I added this section.15:29
e0nethanks!15:29
e0ne#link https://bugs.launchpad.net/horizon/+bug/190282115:29
openstackLaunchpad bug 1902821 in OpenStack Dashboard (Horizon) "When open a link for the detal of image as 'Open Link in New Tab', the new tab doesn't show the details of image." [Medium,Confirmed]15:29
amotokiit looks like AngularJS is not initialized properly but I didn't checked it in detail.15:30
e0neit's angularjs-related issue :(15:30
amotokiit would be nice if someone has time.15:30
e0netmazur: are you around?15:30
tmazure0ne: yes15:30
e0netmazur: you're our angularjs expert :)15:30
tmazurgive me a sec :)15:31
e0neI can take a look on this bug tomorrow morning, but I won't assign it to me before I'll be sure that I can fix it with a reasonable time15:31
vishalmanchandaI have assigned it to myself but if anyone else have quick solution for it.15:32
tmazurI will look into it later today15:32
vishalmanchandafeel free to push a patch.15:32
e0netmazur: thanks a lot!15:33
tmazurvishalmanchanda: ok!15:33
e0ne#link https://etherpad.opendev.org/p/horizon-release-priorities15:33
e0neoops15:33
e0ne#link https://bugs.launchpad.net/horizon/+bug/190332015:33
openstackLaunchpad bug 1903320 in OpenStack Dashboard (Horizon) "Port in OPENSTACK_KEYSTONE_URL" [Undecided,New]15:33
e0neI would like to mark it as 'won't fix'15:34
e0newe can't provide defaults that fits everybody15:34
vishalmanchandaIt's a duplicate bug  I think.15:34
vishalmanchandaI have seen a similar bug before.15:35
amotokiif it is valid for all CentOS/RHEL/Fedora packages, it is a valid bug15:35
amotokiotherwise, we cannot handle it :p15:35
e0nerdopiera: do you have any comments from your side?15:37
rdopierae0ne: no problem with won't fix for me15:38
amotokianother question is whether we would like to maintain the installation guide. we did not verify it for long.15:39
rdopierae use the 5000 explicit port in all our configs, as far as I know, and if not, we can update it15:40
e0neamotoki: it's something we definitely should do15:40
vishalmanchandaJFYI similar bug https://bugs.launchpad.net/horizon/+bug/189227915:42
openstackLaunchpad bug 1892279 in OpenStack Dashboard (Horizon) "Install and configure for Red Hat Enterprise Linux and CentOS in horizon" [Undecided,New]15:42
e0nevishalmanchanda: thank15:42
vishalmanchandae0ne: agreed with ivan.15:42
e0neI changed my mind15:45
e0neI agree now that we need to keep this bug and verify setup guide15:45
amotokilooking at vishalmanchanda's comment in https://bugs.launchpad.net/horizon/+bug/1892279 you assumed devstack configuration but it is about the defaults of Fedora/CentOS/REHEL package15:45
openstackLaunchpad bug 1892279 in OpenStack Dashboard (Horizon) "Install and configure for Red Hat Enterprise Linux and CentOS in horizon" [Undecided,New]15:45
amotokiso you cannot assume devstack configuration. it is a different thing.15:46
vishalmanchandayeah my bad:(15:46
e0neamotoki: +115:46
amotokivishalmanchanda: no problem. thanks for checking it.15:46
vishalmanchandaI have never used rhel & centos..15:47
amotokiit just marked the new one as duplicate of the previous bug vishalmanchanda pasted.15:47
rdopierayou are missing out on a lot of fun ;-)15:47
vishalmanchandareally.15:48
rdopierano, it's actually all pretty much the same15:48
amotokiI logged into RHEL6/CentOS6 yesterday :p15:48
rdopieradid you have to blow the dust from it first?15:49
tmazur:D15:49
amotoki:)15:49
vishalmanchanda🙂15:49
e0nerdopiera: :)15:49
amotokiVMs cannot have the dust ;p15:49
e0nefriendly reminder: we've to 10 minutes left15:50
amotokihttps://bugs.launchpad.net/horizon/+bug/1900851 is interesting. we still have a code incompatible with py3.15:51
openstackLaunchpad bug 1900851 in OpenStack Dashboard (Horizon) "Cannot Create Port with Fixed IP Address" [High,In progress] - Assigned to Akihiro Motoki (amotoki)15:51
amotokiit is just FYI15:52
amotokii think we covered all bugs we need to discuss today.15:52
e0neamotoki: thanks for bringing up these bugs!15:53
vishalmanchandaamotoki: nice.15:53
e0neI would like to continue these effort next week15:54
e0neis any volunteer to do the same for the next meeting?15:55
vishalmanchandaI can do that after next week15:55
vishalmanchandaas I was on holiday for some days in next week.15:56
amotoki I can cover one more week. I said I will push a note on a bug triaging during the PTG but I haven't pushed it yet.15:57
amotokiperhaps some doc would help us to do it, so let me push it first.15:57
vishalmanchandaamotoki: thanks.15:57
e0neamotoki, vishalmanchandaL thanks!15:57
e0newe're almost out of time! thanks a lot for a productive discussion15:58
e0nesee you next week15:59
vishalmanchandabye15:59
amotokithanks all!15:59
tmazurthanks everyone!15:59
rdopierathanks16:00
e0ne#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:01
openstackMeeting ended Wed Nov 18 16:01:02 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-11-18-15.01.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-11-18-15.01.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-11-18-15.01.log.html16:01
*** linshiyx has quit IRC16:05
*** macz_ has joined #openstack-meeting-alt16:13
*** rosmaita has left #openstack-meeting-alt16:22
*** belmoreira has quit IRC16:27
*** masahito has quit IRC16:33
*** e0ne has quit IRC17:21
*** e0ne has joined #openstack-meeting-alt17:22
*** e0ne has quit IRC17:33
*** yamamoto has joined #openstack-meeting-alt17:33
*** yamamoto has quit IRC17:37
*** baojg has quit IRC17:44
*** baojg has joined #openstack-meeting-alt17:45
*** e0ne has joined #openstack-meeting-alt17:57
*** derekh has quit IRC18:14
*** sarmienm has joined #openstack-meeting-alt18:16
*** sarmienm has quit IRC18:19
*** ralonsoh has quit IRC18:31
*** e0ne has quit IRC18:36
*** rdopiera has quit IRC18:38
*** ChuckPiercey has quit IRC19:03
*** rosmaita has joined #openstack-meeting-alt19:42
*** rosmaita has left #openstack-meeting-alt19:45
*** baojg has quit IRC19:46
*** baojg has joined #openstack-meeting-alt19:47
*** vishalmanchanda has quit IRC19:49
*** gyee has joined #openstack-meeting-alt20:10
*** ricolin has quit IRC20:40
*** slaweq has quit IRC20:58
*** rcernin has joined #openstack-meeting-alt21:13
*** thgcorrea has quit IRC21:19
*** slaweq has joined #openstack-meeting-alt21:31
*** tmazur has quit IRC21:48
*** zoharm has quit IRC21:50
*** yamamoto has joined #openstack-meeting-alt22:01
*** baojg has quit IRC22:03
*** baojg has joined #openstack-meeting-alt22:03
*** yamamoto has quit IRC22:10
*** yamamoto has joined #openstack-meeting-alt22:11
*** slaweq has quit IRC22:16
*** hrybacki has quit IRC22:26
*** vkmc has quit IRC22:26
*** hrybacki has joined #openstack-meeting-alt22:26
*** vkmc has joined #openstack-meeting-alt22:26
*** johnsom has quit IRC22:27
*** johnsom has joined #openstack-meeting-alt22:29
*** baojg has quit IRC23:08
*** baojg has joined #openstack-meeting-alt23:09
*** number80 has quit IRC23:13
*** number80 has joined #openstack-meeting-alt23:26
*** yamamoto has quit IRC23:32
*** raildo_ has quit IRC23:42

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!