Wednesday, 2020-04-29

*** diablo_rojo has quit IRC00:01
*** rfolco has quit IRC00:24
*** diablo_rojo has joined #openstack-meeting-alt00:32
*** Liang__ has joined #openstack-meeting-alt00:59
*** yamamoto has joined #openstack-meeting-alt01:49
*** enriquetaso has quit IRC01:54
*** ircuser-1 has joined #openstack-meeting-alt02:05
*** apetrich has quit IRC02:09
*** yamamoto has quit IRC02:48
*** gyee has quit IRC02:52
*** ianychoi_ has joined #openstack-meeting-alt03:08
*** yamamoto has joined #openstack-meeting-alt03:08
*** ianychoi has quit IRC03:10
*** ircuser-1 has quit IRC03:40
*** masahito has quit IRC03:57
*** yamamoto has quit IRC04:10
*** yamamoto has joined #openstack-meeting-alt04:25
*** masahito has joined #openstack-meeting-alt04:43
*** masahito has quit IRC04:47
*** diablo_rojo has quit IRC04:51
*** yamamoto has quit IRC05:15
*** bnemec has quit IRC05:15
*** slaweq has joined #openstack-meeting-alt05:19
*** yamamoto has joined #openstack-meeting-alt05:21
*** tetsuro has joined #openstack-meeting-alt05:28
*** tetsuro has quit IRC05:32
*** links has joined #openstack-meeting-alt05:40
*** ysandeep|away is now known as ysandeep05:45
*** ysandeep is now known as ysandeep|brb05:55
*** slaweq has quit IRC06:06
*** bojleros has joined #openstack-meeting-alt06:31
*** slaweq has joined #openstack-meeting-alt06:41
*** ysandeep|brb is now known as ysandeep06:51
*** ttsiouts has joined #openstack-meeting-alt06:51
*** dustinc has quit IRC06:53
*** links has quit IRC07:03
*** links has joined #openstack-meeting-alt07:04
*** m5z has quit IRC07:05
*** mszwed has joined #openstack-meeting-alt07:06
*** yamamoto has quit IRC07:07
*** yamamoto has joined #openstack-meeting-alt07:09
*** ircuser-1 has joined #openstack-meeting-alt07:10
*** apetrich has joined #openstack-meeting-alt07:24
*** rcernin has quit IRC07:27
*** ysandeep is now known as ysandeep|lunch07:42
*** masahito has joined #openstack-meeting-alt07:50
*** masahito has quit IRC07:55
*** ccamacho has joined #openstack-meeting-alt08:05
*** ysandeep|lunch is now known as ysandeep08:26
*** e0ne has joined #openstack-meeting-alt08:38
*** ttsiouts has quit IRC08:50
*** ttsiouts has joined #openstack-meeting-alt08:51
*** yamamoto has quit IRC08:55
*** yamamoto has joined #openstack-meeting-alt09:09
*** yamamoto has quit IRC09:10
*** yamamoto has joined #openstack-meeting-alt09:10
*** Liang__ has quit IRC10:25
*** mszwed is now known as m5z10:34
*** yamamoto has quit IRC11:11
*** tetsuro has joined #openstack-meeting-alt11:16
*** yamamoto has joined #openstack-meeting-alt11:22
*** ttsiouts has quit IRC11:25
*** ttsiouts has joined #openstack-meeting-alt11:27
*** yamamoto has quit IRC11:29
*** ysandeep is now known as ysandeep|coffee11:29
*** derekh has joined #openstack-meeting-alt11:30
*** raildo has joined #openstack-meeting-alt11:39
*** ttsiouts has quit IRC11:43
*** raildo has quit IRC11:49
*** raildo has joined #openstack-meeting-alt11:50
*** tetsuro has quit IRC11:52
*** tetsuro has joined #openstack-meeting-alt11:53
*** tetsuro has quit IRC11:54
*** yamamoto has joined #openstack-meeting-alt12:04
*** rfolco has joined #openstack-meeting-alt12:14
*** ttsiouts has joined #openstack-meeting-alt12:16
*** bojleros has quit IRC12:18
*** ttsiouts has quit IRC12:21
*** danielarthurt has joined #openstack-meeting-alt12:21
*** derekh has quit IRC12:26
*** yamamoto has quit IRC12:36
*** yamamoto has joined #openstack-meeting-alt12:42
*** yamamoto has quit IRC12:43
*** ttsiouts has joined #openstack-meeting-alt12:55
*** links has quit IRC12:59
*** enriquetaso has joined #openstack-meeting-alt13:03
*** derekh has joined #openstack-meeting-alt13:12
*** yamamoto has joined #openstack-meeting-alt13:21
*** ttsiouts has quit IRC13:29
*** yamamoto has quit IRC13:29
*** yamamoto has joined #openstack-meeting-alt13:30
*** Liang__ has joined #openstack-meeting-alt13:53
*** bojleros has joined #openstack-meeting-alt13:55
*** bnemec has joined #openstack-meeting-alt13:56
*** Liang__ is now known as LiangFang13:57
*** rosmaita has joined #openstack-meeting-alt13:58
*** andrebeltrami has joined #openstack-meeting-alt13:59
*** sfernand has joined #openstack-meeting-alt13:59
rosmaita#startmeeting cinder14:00
openstackMeeting started Wed Apr 29 14:00:14 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
smcginniso/14:00
*** ttsiouts has joined #openstack-meeting-alt14:00
rosmaita#link https://etherpad.openstack.org/p/cinder-ussuri-meetings14:00
rosmaita#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: cinder)"14:00
whoami-rajatHi14:00
bojlerosHi14:00
lsekio/14:00
walshh_Hi14:00
sfernandHi14:01
e0nehi14:01
enriquetasohi14:01
LiangFanghi14:01
jungleboyjo/14:01
rosmaitalooks like a good turnout14:01
rosmaita#topic updates14:01
*** openstack changes topic to "updates (Meeting topic: cinder)"14:01
jungleboyjI read that as 'it looks like a burnout'14:01
jungleboyj:-)14:01
*** throne82 has joined #openstack-meeting-alt14:01
m5zhi =]14:02
rosmaitajungleboyj: you are about a week off from 4/2014:02
jungleboyj*Laughing*14:02
*** tosky has joined #openstack-meeting-alt14:02
rosmaitalet's start with a quote from smcginnis:14:02
rosmaita"Keep in mind that all work should now be transitioning to stabilization and getting things ready for the final RC deadline on May 7"14:02
jungleboyjI was thinking workwise, but I will let you go that direction.14:02
rosmaitaso that's the focus right now14:02
smcginnis;)14:02
rosmaitaupcoming deadlines:14:02
rosmaitaMay 7 (Thursday next week): Final RC deadline14:03
rosmaitawe will go over the RC stuff a bit later14:03
rosmaitaMay 13: Final Ussuri release14:03
e0nerosmaita: what about cinderlib? it doesn't have stable/ussuri branch yet14:03
rosmaitawe can celebrate by skipping the weekly meeting on may 1314:03
rosmaitae0ne: cinderlib is cycle-trailing14:03
rosmaitaso won't get stable branch until a few weeks from now14:04
e0nerosmaita: got it, thanks14:04
rosmaitathere will be a "community meeting" at our cinder meeting time on may 1314:04
rosmaitamostly project updates14:04
rosmaitaso you can attend that to get your weekly meeting fix14:04
rosmaitaJune 1-5: Victoria (Virtual) PTG14:05
rosmaita#link https://etherpad.opendev.org/p/cinder-victoria-ptg-planning14:05
rosmaitai've got the proposed cinder meeting times on the etherpad ^^14:05
rosmaitathere's also a link there the the main ethercalc where all the teams are scheduling stuff14:05
rosmaitawe are light on topics, so please add some14:06
*** yamamoto has quit IRC14:06
rosmaitaor else we can have a tempest scenario test hackathon14:06
rosmaitafinal deadline i want to mention14:06
rosmaitaJune 18: Victoria milestone 114:06
rosmaitawhich seems amazingly close14:06
rosmaitai see LiangFang has an item on the topics later14:06
rosmaitabut it would be good to get the volume local cache stuff done before then14:07
rosmaitaat least the os-brick changes14:07
rosmaitai'm mentioning it now because M-1 is only 2 weeks after the ptg14:07
enriquetasoprobably the NFS encryption patch too...14:07
rosmaitathat's right14:07
rosmaitawhat enriquetaso said14:08
rosmaitabut this week is rc reviews and bugfixes14:08
rosmaitaok, that's all the announcements14:08
rosmaita#topic victoria community goals14:08
*** openstack changes topic to "victoria community goals (Meeting topic: cinder)"14:08
rosmaitaok, usually we discuss at ptg, but the actual model is that they should be selected by now and we discuss how to implement at ptg14:09
rosmaitaso, i want to do a quick runthrough so that we don't get surprised by a goal that we absolutely hate14:09
rosmaitahttps://etherpad.opendev.org/p/YVR-v-series-goals14:09
rosmaitagood thing is, tosky's goal has already been selected and approved14:10
toskyand we are in a good shape14:10
rosmaitaand he's done most of the work on it already for cinder!14:10
rosmaitatosky: ++14:10
enriquetasotosky ++14:10
rosmaitaok, i will not be coy14:10
rosmaitai am worried about goal #614:11
rosmaitaadd container images14:11
toskyif I'm not mistaken, after merging https://review.opendev.org/#/c/709780/, there is just one legacy job left14:11
* tosky shuts up for now14:11
rosmaitamy feeling is that container images is a distro thing14:11
rosmaitaand i can see getting bindep worked out correctly for all distros being a big time-waster14:11
rosmaitabecause the goal is portrayed as "just add a dockerfile to your repo"14:12
rosmaitabut, that's just me14:12
*** ttsiouts has quit IRC14:12
rosmaitabut unless we have someone here who is really interested in working on this, i don't know that it's a good allocation of cinder resources14:13
rosmaitai would rather harden our testing14:13
rosmaitarather than have buggy code in a nice container14:13
e0neI still don't understand why we need it14:13
smcginnisWould be good to comment on that proposed goal.14:13
toskyon the other hand, if just one or two goals at most are going to be select, I would bet on 4 and 714:13
e0nethare are loci and kolla around14:13
rosmaita4 and 7 would be great14:13
*** bojleros has quit IRC14:13
rosmaitae0ne: exactly14:14
rosmaitamy fear of #6 is primarily the goal champions14:14
rosmaitathey are very enthusiastic14:14
e0nehttps://github.com/openstack/cinder/tree/master/contrib/block-box - we've got something:)14:14
jungleboyj:-)  So, there has been a lot of back and forth in the TC on that goal.14:14
*** bojleros has joined #openstack-meeting-alt14:14
jungleboyjIf people have an opinion it would be good to comment.14:14
rosmaitai'll leave a comment right after the meeting14:15
bojlerosi have just reconnected since my uplink was down14:15
rosmaitajust wanted to get a sense of the cinder community, because when i leave a comment, it could be taken as a comment on behalf of the team14:15
bojlerosrosmaita please let me know when we can discus my proposal14:16
rosmaitabojleros: 2 topics away14:16
bojlerosok14:16
smcginnisbojleros: https://etherpad.opendev.org/p/cinder-ussuri-meetings14:17
rosmaitaok, like tosky pointed out, the other goals look fine for cinder and not too resource intensive14:17
rosmaitaand as jungleboyj pointed out, if you have an opinion on any of the goals, please leave a comment on that etherpad14:17
rosmaita#topic review of rc-critical patches14:18
*** openstack changes topic to "review of rc-critical patches (Meeting topic: cinder)"14:18
rosmaita#link https://etherpad.opendev.org/p/cinder-ussuri-rc-backport-potential14:18
jungleboyjWow, dynamic config changes on there.  How long have we been talking about that?14:18
rosmaitaok, i need some help with some of these14:19
e0nebtw, it's not a list of approved goals14:19
rosmaitae0ne: that's right, these are proposed goals14:20
rosmaitabut it's not clear what the timeline for selection is14:20
rosmaitaand the tc selects14:20
whoami-rajati would need to do some testing on the rbd patch, my understanding and testing was a little off on that14:20
rosmaitaso if there are any you hate, it is really important to make that known pre-selection14:20
rosmaitawhoami-rajat: please put a note on the etherpad14:20
whoami-rajatrosmaita, ok14:21
rosmaitanow about these patches14:21
e0ne#link https://governance.openstack.org/tc/goals/selected/victoria/index.html14:21
rosmaitawe can still do backports and do a point release14:21
rosmaitawhat we want to get in now are critical fixes14:21
* jungleboyj should know when the selection is. It is soon.14:21
rosmaitaso i wanted to look at the "controversial" list14:22
rosmaitahttps://review.opendev.org/#/c/720722/14:22
rosmaitathis is a change to the virtuozzo driver to support a feature that is being delivered in ussuri14:23
*** yamamoto has joined #openstack-meeting-alt14:23
*** yamamoto has quit IRC14:23
*** priteau has joined #openstack-meeting-alt14:23
rosmaitavirtuozzo is 'unsupported' , but i think we still want it to be a working driver if we're keeping it in repo14:23
rosmaitaso i thnk this bugfix really needs to get into RC-214:24
*** yamamoto has joined #openstack-meeting-alt14:24
rosmaitaany thoughts?14:24
whoami-rajatsince we've added the feature in this realease, it would be better to have it in all drivers but that's just my opinion14:25
smcginnisI don't think we should be adding new features to unsupported drivers.14:26
jungleboyjWell, if we aren't removing it then we should make sure it work.14:26
e0nesmcginnis: good point14:26
rosmaitawell, it's not a driver feature, really14:26
rosmaitait's a cinder feature that entails a driver change14:26
smcginnisHow are we going to make sure the new features work if the driver isn't being tested?14:26
rosmaitaunit tests14:26
rosmaitabest we can do14:26
jungleboyjHmmm.14:26
smcginnisThen I change my stance on the decision to keep these drivers in tree. They should be removed.14:27
rosmaitagood ptg topic14:27
rosmaitabut i think at this point in the cycle, we are stuck with it14:27
smcginnisUnit tests are not failing due to that driver right now. Therefore according to what we had agreed to do with unsupported drivers, it really should not be touched.14:28
*** yamamoto has quit IRC14:28
jungleboyjrosmaita:  Yeah ... should discuss at the PTG.14:28
rosmaitawell, we could deny the patch and list it as a "known issue"14:29
rosmaitabut we will probably be facing this kind of situation again if we carry these unsupported drivers14:29
rosmaitawe have whoami-rajat's patch if someone really wants to use the driver14:29
rosmaitabut this is a good example of what we are up against, so should help us focus the discussion at the PTG14:30
rosmaitai have checked all the other drivers we have in-tree, this is the only one affected by the glance multi-store support14:31
rosmaitabut that was mostly a matter of luck14:31
whoami-rajatdo we have other unsupported drivers in which this change exists?14:31
jungleboyjGood question.14:32
rosmaitanot sure, would have to look14:32
rosmaitaactually, probably we do14:32
rosmaitaany of the ones being marked unsupported in ussuri are candidates14:32
rosmaitathe other removed-then-restored drivers used an inherited method14:32
rosmaitaso when that was fixed in the base class, everything was fine, no changes needed to the driver code14:33
rosmaitai don't want to drag this out, should we vote?14:33
whoami-rajatalso one more thing i want to point out14:34
whoami-rajatthis is the last change to happen in drivers regarding image as we've a wrapper now which will handle these changes from future14:34
whoami-rajats/image/upload image14:34
jungleboyjI personally think if this is needed for the driver to work and it is an outlier from the other restored drivers we should fix it and then discuss how we handle this in the future at the PTG.14:35
rosmaitajungleboyj: ++14:35
e0nejungleboyj:+114:35
* jungleboyj ducks to avoid the tomatoes smcginnis is throwing14:35
smcginnis:)14:35
rosmaitasmcginnis: are you ok with that? you can -1 the patch14:36
rosmaitai just would like to know in advance if you are going to -2 the backport14:37
rosmaitai think smcginnis is in a simultaneous meeting, we can return to this before end of meeting14:38
rosmaitaok, the other controversial patch is having trouble with it's own CI14:38
rosmaitaso i'm inclined to hold off on it14:39
jungleboyjThat is always a good sign.14:39
smcginnisrosmaita: Yeah. I didn't downvote the patch, I just didn't want to approve it.14:39
rosmaitasmcginnis: understood, i can respect that14:39
rosmaitaand you have definitely identified an issue we need to have a policy on14:39
rosmaitaok, so my final point here14:39
rosmaitayou can see that i am not convinced any of the proposed-as-release-critical patches really need to get in14:40
rosmaitaso if you have a counterargument, please either tell us now or on the etherpad *today*14:40
* rosmaita is waiting a minute to hear any counterarguments14:41
*** yamamoto has joined #openstack-meeting-alt14:41
*** yamamoto has quit IRC14:41
rosmaitaoh yeah, one more point14:42
*** yamamoto has joined #openstack-meeting-alt14:42
rosmaitaabout the approved for backport patches14:42
rosmaitaif you are the owner of one of these in master, you are responsible for proposing the backport to stable/ussuri14:42
rosmaitajust so we are clear about that14:42
rosmaitathey need to merge to master first, though14:43
rosmaitajust so we are also clear about that14:43
rosmaitaok, so reviewers, please keep an eye on the approved for backport patches and i will propose RC-2 as soon as they land14:44
rosmaitaany questions?14:44
rosmaita#topic improvement proposal for LVM volume driverĀ 14:44
*** openstack changes topic to "improvement proposal for LVM volume driverĀ  (Meeting topic: cinder)"14:44
rosmaitabojleros: that's you14:44
bojlerosyep14:45
whoami-rajatrosmaita, ++14:45
bojleroswhat do you think about this proposal ?14:45
bojleroswell , i'd like to keep it as small as possible in term of a change footprint , reuse as much as i can14:45
bojleroswithout breaking functionalitiest that already exists and are in production use14:45
bojlerosso therefore we are not talking about a new driver just new target_helper for lvm driver14:46
rosmaitathis looks very interesting14:46
*** yamamoto has quit IRC14:46
rosmaitacan we discuss in more detail at the PTG?14:46
bojlerosit has some limitations pointed in README.md but that's how the local storage works14:47
bojlerossure14:47
rosmaitaor is that too far in the future?14:47
bojleroswell , my primary point of interest is stein14:47
smcginnisThis seems similar to the block device driver that was removed because it couldn't support all base functionality.14:47
smcginnishttps://github.com/openstack/cinder/blob/icehouse-eol/cinder/volume/drivers/block_device.py14:47
bojlerossince this is the relase we are running right now , but idk if you will allow backporting so many releases behind14:48
jungleboyjWe don't allow backporting new drivers/features.14:48
e0nesmcginnis: that was my question14:48
bojlerossmcginnis what are the exact functionalites you are talinkg about ?14:49
smcginnisUnfortunately no, new features would not be eligible for backport. So this would be a feature of victoria, if we do it.14:49
rosmaitayeah, you may have to carry this as a local patch for stein, but you can look forward to having it there when you upgrade to victoria14:49
LiangFangbojleros: seems volume local cache can fit your requirement14:49
smcginnisbojleros: Looks like you may have it covered in the "Tested functionalities"14:49
bojlerosi am fine with that , we will have victoria one day, till then we will patch14:49
bojlerosi know the list but i want to know it exactly14:50
smcginnisAnyone remember the benchmarking the Griffith did for the LVM driver? I thought with some configuration tweaks he was able to show the existing LVM driver was at or close the performance level of a local block device.14:50
bojleroslocal storage will have some limitations that will not work , other can only be a nifty tricks as I described in my paper14:50
bojlerosit is not the lvm that gives a performance drop , it is iscsi14:51
e0nesmcginnis: AFAR, lv,+LIO was pretty close to block device briver14:51
smcginnisbojleros: Here are the minimum required features: https://docs.openstack.org/cinder/latest/contributor/drivers.html#minimum-features14:51
smcginnisSo it would need to support those operations at a minimum.14:51
e0nebojleros: did you test with LIO target on the same node?14:51
bojleroscreate/delete/attach/detach works14:51
bojleroscreate volume from snapshot works14:52
bojlerosach pardon14:52
bojlerosi ment image to volume and volume to image14:52
bojlerosextend works14:52
bojlerosit is greately inherited from lvm functionality itself , not only by target helper14:53
e0nebojleros: what about snapshots?14:53
bojlerosi havent tested it yet14:53
bojlerossince i do not use it14:53
e0neit's a hard requirement to support snapshots14:53
smcginnisThis concerns me a lot "you must ensure that vm is pinned or running in a single-host-AZ (you may also want to limit Cinder to a particular AZ) or without it your vm can be started on a host that does not contain your volumes"14:53
bojleroschanging volume type works with some remarks14:53
rosmaitaok, let's continue this discussion after reading through the paper14:54
bojlerosyep but that's the fundamental question about if cinder is going to deliver a direct attached storage or not14:54
e0nebojleros: also, your. driver must support remote volumes attachements14:54
smcginnisbojleros: Did you see e0ne's earlier question? Did you test LVM with LIO?14:54
bojlerosyep , tested14:54
e0neI was a maintainer of BlockDeviceDriver and I was happy to remove it:)14:55
bojlerosin term of performance we lose ~60% of rd iops14:55
bojlerosso you do not like this idea dont you ?? :)14:55
rosmaitabojleros: please add this to the PTG list ... that doesn't mean we can't discuss prior, though14:55
smcginnisI don't think it can work the way a Cinder driver is expected to behave.14:55
smcginnisSeems like maybe something that should be done in Nova and without Cinder.14:55
bojlerosthat's what we do right now as a workaround14:56
e0nesmcginnis: +114:56
bojlerosi have highligted some cons already14:56
rosmaitasounds like e0ne and smcginnis have some things you will need to look into14:56
bojlerosand this target_helper is a kind of option , you give user a freedom of choice14:57
smcginnisAlmost out of time. This does seem like it needs a larger PTG discussion.14:57
rosmaitaLiangFang: looks like we will not have time for discussion, but we do have the links on the agenda14:58
bojlerosok , gonna add it14:58
LiangFangrosmaita: I'm OK:)14:58
rosmaitaok, well you and enriquetaso have the priority items after RC-time is over in a week14:58
rosmaita#topic open discussion14:59
*** openstack changes topic to "open discussion (Meeting topic: cinder)"14:59
rosmaitafor 45 seconds ... anyone?14:59
bojlerosthank you for discussing my proposal ;)14:59
e0ne:)14:59
rosmaitabojleros: thanks for bringing it to us14:59
LiangFangbojleros: maybe you can take a look of volume local cache14:59
rosmaita#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Wed Apr 29 15:00:07 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-04-29-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-04-29-14.00.txt15:00
jungleboyjThanks!15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-04-29-14.00.log.html15:00
LiangFanggood to solve performance issues15:00
*** tosky has left #openstack-meeting-alt15:01
*** trident has quit IRC15:04
amotoki#startmeeting horizon15:04
openstackMeeting started Wed Apr 29 15:04:46 2020 UTC and is due to finish in 60 minutes.  The chair is amotoki. Information about MeetBot at http://wiki.debian.org/MeetBot.15:04
*** gshippey has joined #openstack-meeting-alt15:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:04
*** openstack changes topic to " (Meeting topic: horizon)"15:04
openstackThe meeting name has been set to 'horizon'15:04
*** rosmaita has left #openstack-meeting-alt15:04
amotokianyone around?15:05
*** trident has joined #openstack-meeting-alt15:05
e0nehi15:05
*** LiangFang has quit IRC15:05
amotokie0ne: hi15:06
amotokitoday is a start of the holiday week in my side, so I have less topics.15:06
amotoki#topic announcements/notices15:07
*** openstack changes topic to "announcements/notices (Meeting topic: horizon)"15:07
amotokinext week is a week of final RCs and intermediary releases15:07
amotokiwe will cut at least one release to import translations.15:08
amotokithe holiday week in Japan continues till Wed next week, but I will check reviews occasionally.15:09
amotokianything other to share?15:09
e0nea few words about PTG planning15:10
e0ne#link https://etherpad.opendev.org/p/horizon-v-ptg15:10
e0neI requested 3 timeslots for us15:11
amotokiI failed to find time to add topics last week15:11
amotokithanks for proposing the timeslots15:11
e0neThe last one on Wednesday is to cover some discussions in US timezone if needed15:11
e0neI'll send a mail to openstack-discuss@15:11
e0nethe main idea is to cover everything on Mon-Tue15:12
amotokiI haven't checked my conflict with other projects and my availability depends on the schedule as a whole15:12
e0ne 3 hours should be enough15:12
e0neamotoki: I tried to not conflict with neutron15:13
e0nefeel free to ping me if we need some other or more timeslots15:13
amotokie0ne: thanks for your consideration15:14
e0neI'll add few more topics to discuss later this week15:15
amotokihopefully me too :)15:16
e0ne:)15:16
amotokimoving on15:17
*** yamamoto has joined #openstack-meeting-alt15:18
amotoki#topic On-Demand agenda15:18
*** openstack changes topic to "On-Demand agenda (Meeting topic: horizon)"15:18
amotokiI am skipping others and moving to the on-demand agenda section this week :)15:18
amotokiI have a small topic on Django 3.015:19
amotokiI tried Django 3.0 a few weeks ago15:19
amotokiand noticed django-pyscss can be a blocker15:19
amotokihorizon support would be simple15:19
e0newhat is the issue with  django-pyscss?15:20
amotokiwe may hit a same problem on django-pyscss as what we had in pyscss15:20
amotokidjango-pyscss depends on a module which was dropped in Django 3.015:21
e0ne:(15:21
amotokidjango.utils.six was dropped15:21
rdopieramaybe it's time we switched to node tools15:21
e0nerdopiera: +1 for it in the long-term perspective15:22
amotokirdopiera: do you mean webpack or some?15:22
rdopieraI don't know, really, all I know is that most of the web tools are originally created for node.js (except for the ones that used to be for ruby), and that is the best supported version of them15:23
rdopierawe already require node for some of our tests15:23
e0nebtw, I've got django-pyscss2 fork :)15:24
amotokiyeah most tooling around JS world depends on node.js15:24
rdopierawe are fighting an uphill battle by trying to stick to python15:24
e0newebpack-based setup will be awesome! but I'm afraid  how muxh efforts  it  will require15:25
e0nes/muxh/much15:25
amotokiIIRC, legacy packaging like rpm does not allow us to use multiple versions in a single system and that's the background of xstatic modules, right?15:25
e0neor maybe npm wasn't good enough so xstatic-* was created15:26
rdopieraamotoki: not quite, xstatic was to track dependencies using python tools, they still don't ship multiple versions15:27
rdopieraI mean, on Debian xstatic is just a thin shim pointing to where the javascript library is installed in the system15:28
rdopierathe package itself doesn't contain javascript code15:28
rdopierae0ne: speaking of effort, is there a plan to get to a supported version of angular?15:29
amotokiwhat I am afraid is rpm or deb packaging does not allow us to use mixed versions of JS library. If project A requires JS module verX and project B requirs JS module verY, I am not sure they can handle it.15:29
e0nerdopiera: re-write everything15:29
rdopieraamotoki: we can't handle it right now either15:29
e0nelet's discuss the possibility of npm usage during the PTG15:30
rdopierae0ne: I was recently backporting a bunch of CVE patches to a version of jquery that works with horizon15:30
rdopierae0ne: but we will need to upgrade to a supported version sooner or later15:30
e0ne+++15:30
rdopieraproblem is, our angular doesn't work with jquery 315:30
rdopieraso, do we fork it?15:31
amotokiwe have many problems which affect each other :(15:31
amotokiwhat I hit in Django30 is just a piece of our issues.15:32
rdopieraso in the long run, either we fork and maintain our own angular, or we do the rewrite to something supported, and hope it will still be supported by the time we finish15:33
e0neor create our own framework15:33
e0nelike we discussed some time ago during the ptg15:33
amotokieither way sounds a tough road to us....15:33
amotokiit looks like better to explore our possibility before PTG for productive discussion in the pTG15:34
e0neamotoki: +115:35
rdopieraI remember that on some of the previous PTGs we also discussed the possibility of backporting the changes to the old Python views and ditching the angular views15:37
rdopierawhich would solve a lot of our problems, in my opinion15:38
amotokirdopiera: I am not sure we discussed an option to throw away angularjs impls explicitly.15:39
amotokiat least we agree that we have no priority on angularjs migration15:39
rdopieraI think it was in Dublin15:39
rdopierayeah, maybe we will get back to it again on the PTG15:39
amotokianyway I totally agree that we need to discuss the future of mixed usage of django and angular impls15:41
amotokianything to discuss?15:43
e0nenothing from me15:43
amotokiit was a good brainstorming discussion. let's add note to the ptg etherpad.15:43
amotokiokay, let's wrap up the meeting15:44
amotokithanks all15:44
amotoki#endmeeting15:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:44
e0nesee you next week!15:44
openstackMeeting ended Wed Apr 29 15:44:18 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-04-29-15.04.html15:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-04-29-15.04.txt15:44
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-04-29-15.04.log.html15:44
*** gyee has joined #openstack-meeting-alt15:53
*** ysandeep|coffee is now known as ysandeep|away16:12
*** sfernand has quit IRC17:19
*** apetrich has quit IRC17:22
*** priteau has quit IRC17:32
*** diablo_rojo has joined #openstack-meeting-alt17:33
*** throne82 has quit IRC17:39
*** e0ne has quit IRC18:07
*** derekh has quit IRC18:36
*** priteau has joined #openstack-meeting-alt19:44
*** priteau has quit IRC19:51
*** bojleros has quit IRC19:55
*** ccamacho has quit IRC20:59
*** slaweq has quit IRC21:01
*** slaweq has joined #openstack-meeting-alt21:09
*** slaweq has quit IRC21:14
*** raildo has quit IRC21:18
*** enriquetaso has quit IRC21:32
*** rcernin has joined #openstack-meeting-alt21:32
*** rcernin has quit IRC21:33
*** rcernin has joined #openstack-meeting-alt21:34
*** andrebeltrami has quit IRC21:39
*** Adri2000 has quit IRC22:26
*** gshippey has quit IRC22:34
*** Adri2000 has joined #openstack-meeting-alt23:00

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