Wednesday, 2019-02-06

*** tetsuro has joined #openstack-meeting00:03
*** yamamoto has quit IRC00:04
*** whoami-rajat has quit IRC00:08
*** macza has quit IRC00:09
*** ijw has joined #openstack-meeting00:15
*** tetsuro has quit IRC00:16
*** tetsuro_ has joined #openstack-meeting00:16
*** iyamahat has joined #openstack-meeting00:20
*** ijw_ has joined #openstack-meeting00:21
*** ijw has quit IRC00:23
*** b1airo has quit IRC00:26
*** iyamahat has quit IRC00:27
*** bbowen has joined #openstack-meeting00:32
*** jamesmcarthur has joined #openstack-meeting00:35
*** jamesmcarthur has quit IRC00:40
*** rfolco has quit IRC00:40
*** mriedem has quit IRC00:43
*** macza has joined #openstack-meeting00:47
*** lbragsta_ has joined #openstack-meeting00:50
*** jamesmcarthur has joined #openstack-meeting00:52
*** lbragsta_ is now known as lbragstad__00:52
*** _alastor_ has quit IRC00:54
*** jamesmcarthur has quit IRC00:56
*** Swami has quit IRC00:57
*** rfolco has joined #openstack-meeting00:59
*** jamesmcarthur has joined #openstack-meeting01:04
*** mjturek has quit IRC01:06
*** mattw4 has quit IRC01:08
*** tetsuro_ has quit IRC01:08
*** tetsuro has joined #openstack-meeting01:09
*** bobh has joined #openstack-meeting01:15
*** bobh has quit IRC01:16
*** tetsuro has quit IRC01:33
*** dims has quit IRC01:40
*** _alastor_ has joined #openstack-meeting01:42
*** _alastor_ has quit IRC01:47
*** bobh has joined #openstack-meeting01:49
*** bobh has quit IRC01:52
*** armax has quit IRC01:53
*** TxGirlGeek has quit IRC02:08
*** dims has joined #openstack-meeting02:11
*** dims has quit IRC02:25
*** yamamoto has joined #openstack-meeting02:27
*** tetsuro has joined #openstack-meeting02:30
*** yamamoto has quit IRC02:32
*** dims has joined #openstack-meeting02:33
*** TxGirlGeek has joined #openstack-meeting02:35
*** sdake has quit IRC02:37
*** sdake has joined #openstack-meeting02:40
*** tetsuro has quit IRC02:46
*** tetsuro_ has joined #openstack-meeting02:46
*** lbragstad__ has quit IRC02:52
*** jamesmcarthur has quit IRC02:56
*** gyee has quit IRC03:00
*** ekcs has quit IRC03:00
*** jamesmcarthur has joined #openstack-meeting03:02
*** psachin has joined #openstack-meeting03:04
*** armax has joined #openstack-meeting03:10
*** sdake has quit IRC03:23
*** apetrich has quit IRC03:24
*** jamesmcarthur has quit IRC03:25
*** yamamoto has joined #openstack-meeting03:33
*** _hemna has joined #openstack-meeting03:38
*** macza has quit IRC03:45
*** tetsuro_ has quit IRC03:53
*** TxGirlGeek has quit IRC03:54
*** jamesmcarthur has joined #openstack-meeting03:56
*** imsurit_ofc has joined #openstack-meeting03:59
*** igordc has quit IRC04:02
*** jamesmcarthur has quit IRC04:03
*** _hemna has quit IRC04:09
*** sdake has joined #openstack-meeting04:10
*** rbudden has quit IRC04:12
*** macza has joined #openstack-meeting04:20
*** armstrong has joined #openstack-meeting04:24
*** armstrong has quit IRC04:29
*** jamesmcarthur has joined #openstack-meeting04:30
*** macza has quit IRC04:34
*** jamesmcarthur has quit IRC04:35
*** ijw_ has quit IRC04:49
*** janki has joined #openstack-meeting04:53
*** macza has joined #openstack-meeting05:00
*** macza has quit IRC05:05
*** jamesmcarthur has joined #openstack-meeting05:05
*** jamesmcarthur has quit IRC05:10
*** zbr|ssbarnea has joined #openstack-meeting05:13
*** zbr has quit IRC05:16
*** sdake has quit IRC05:25
*** hyunsikyang has joined #openstack-meeting05:27
*** sdake has joined #openstack-meeting05:35
*** macza has joined #openstack-meeting05:42
*** macza has quit IRC05:46
*** dkushwaha has quit IRC05:49
*** yamamoto has quit IRC06:01
*** jamesmcarthur has joined #openstack-meeting06:07
*** yamamoto has joined #openstack-meeting06:10
*** macza has joined #openstack-meeting06:10
*** jamesmcarthur has quit IRC06:11
*** macza has quit IRC06:15
*** sdake has quit IRC06:20
*** tetsuro has joined #openstack-meeting06:30
*** jamesmcarthur has joined #openstack-meeting06:44
*** jamesmcarthur has quit IRC06:48
*** sridharg has joined #openstack-meeting06:51
*** whoami-rajat has joined #openstack-meeting06:53
*** priteau has joined #openstack-meeting06:54
*** armax has quit IRC07:02
*** lpetrut has joined #openstack-meeting07:03
*** slaweq has joined #openstack-meeting07:07
*** priteau has quit IRC07:18
*** dtrainor has joined #openstack-meeting07:24
*** dtrainor_ has joined #openstack-meeting07:26
*** dtrainor has quit IRC07:29
*** pcaruana has joined #openstack-meeting07:29
*** markvoelker has joined #openstack-meeting07:39
*** yamamoto has quit IRC07:39
*** yamamoto has joined #openstack-meeting07:41
*** yamamoto has quit IRC07:41
*** yamamoto has joined #openstack-meeting07:41
*** apetrich has joined #openstack-meeting07:50
*** belmoreira has joined #openstack-meeting08:02
*** imsurit_ofc has quit IRC08:03
*** lpetrut has quit IRC08:07
*** lpetrut has joined #openstack-meeting08:08
*** rossella_s has joined #openstack-meeting08:08
*** kopecmartin|off is now known as kopecmartin08:09
*** e0ne has joined #openstack-meeting08:10
*** markvoelker has quit IRC08:12
*** e0ne has quit IRC08:33
*** ttsiouts has joined #openstack-meeting08:33
*** asmita has joined #openstack-meeting08:42
*** jamesmcarthur has joined #openstack-meeting08:45
*** ttsiouts has quit IRC08:47
*** ttsiouts has joined #openstack-meeting08:48
*** tetsuro has quit IRC08:48
*** jamesmcarthur has quit IRC08:50
*** ttsiouts has quit IRC08:52
*** asmita has quit IRC08:53
*** tssurya has joined #openstack-meeting08:54
*** Luzi has joined #openstack-meeting08:54
*** vishalmanchanda has joined #openstack-meeting08:57
*** e0ne has joined #openstack-meeting09:01
*** ociuhandu has quit IRC09:09
*** ttsiouts has joined #openstack-meeting09:09
*** markvoelker has joined #openstack-meeting09:09
*** ociuhandu has joined #openstack-meeting09:10
*** lpetrut has quit IRC09:14
*** ociuhandu has quit IRC09:15
*** markvoelker has quit IRC09:43
*** takamatsu_ has joined #openstack-meeting09:57
*** takamatsu has quit IRC09:57
*** aojea has joined #openstack-meeting09:59
*** takamatsu_ has quit IRC10:00
*** ociuhandu has joined #openstack-meeting10:03
*** takamatsu_ has joined #openstack-meeting10:03
*** ociuhandu has quit IRC10:07
*** yamamoto has quit IRC10:23
*** psachin has quit IRC10:24
*** slaweq has quit IRC10:40
*** markvoelker has joined #openstack-meeting10:40
*** jamesmcarthur has joined #openstack-meeting10:46
*** erlon has joined #openstack-meeting10:48
*** psachin has joined #openstack-meeting10:50
*** jamesmcarthur has quit IRC10:51
*** erlon_ has joined #openstack-meeting10:55
*** slaweq has joined #openstack-meeting10:57
*** erlon has quit IRC10:58
*** macza has joined #openstack-meeting10:59
*** slaweq has quit IRC11:01
*** macza has quit IRC11:03
*** ttsiouts has quit IRC11:13
*** markvoelker has quit IRC11:13
*** yamamoto has joined #openstack-meeting11:32
*** slaweq has joined #openstack-meeting11:38
*** takamatsu_ has quit IRC11:48
*** janki has quit IRC11:49
*** takamatsu_ has joined #openstack-meeting11:52
*** janki has joined #openstack-meeting11:54
*** yamamoto has quit IRC11:56
*** ttsiouts has joined #openstack-meeting11:58
*** raildo has joined #openstack-meeting12:09
*** markvoelker has joined #openstack-meeting12:09
*** janki has quit IRC12:23
*** takamatsu_ has quit IRC12:24
*** takamatsu has joined #openstack-meeting12:24
*** ociuhandu has joined #openstack-meeting12:35
*** ociuhandu has joined #openstack-meeting12:35
*** rf0lc0 has joined #openstack-meeting12:35
*** ociuhandu has quit IRC12:35
*** ociuhandu has joined #openstack-meeting12:36
*** Luzi has quit IRC12:37
*** yamamoto has joined #openstack-meeting12:37
*** Luzi has joined #openstack-meeting12:37
*** rfolco has quit IRC12:37
*** Luzi has quit IRC12:38
*** sdake has joined #openstack-meeting12:42
*** markvoelker has quit IRC12:42
*** jamesmcarthur has joined #openstack-meeting12:45
*** jamesmcarthur has quit IRC12:50
*** bobh has joined #openstack-meeting12:58
*** ociuhandu_ has joined #openstack-meeting13:09
*** erlon_ has quit IRC13:10
*** mmethot has quit IRC13:11
*** ociuhandu_ has quit IRC13:11
*** ociuhandu_ has joined #openstack-meeting13:12
*** ociuhandu has quit IRC13:12
*** mmethot has joined #openstack-meeting13:14
*** rf0lc0 is now known as rfolco13:14
*** bobh has quit IRC13:15
*** rbudden has joined #openstack-meeting13:16
*** TxGirlGeek has joined #openstack-meeting13:18
*** carlos_silva has joined #openstack-meeting13:21
*** sdake has quit IRC13:23
*** sdake has joined #openstack-meeting13:26
*** erlon_ has joined #openstack-meeting13:26
*** Luzi has joined #openstack-meeting13:27
*** sdake has quit IRC13:27
*** mriedem has joined #openstack-meeting13:32
*** TxGirlGeek has quit IRC13:33
*** sdake has joined #openstack-meeting13:34
*** janki has joined #openstack-meeting13:35
*** number80 has quit IRC13:35
*** slaweq has quit IRC13:35
*** sdake has quit IRC13:39
*** markvoelker has joined #openstack-meeting13:39
*** sdake has joined #openstack-meeting13:48
*** yamamoto has quit IRC14:00
*** sdake has quit IRC14:00
*** yamamoto has joined #openstack-meeting14:00
*** yamamoto has quit IRC14:00
*** sdake has joined #openstack-meeting14:01
*** yamamoto has joined #openstack-meeting14:01
*** samP has quit IRC14:02
*** samP has joined #openstack-meeting14:04
*** yamamoto has quit IRC14:05
*** yamamoto has joined #openstack-meeting14:06
*** ttsiouts has quit IRC14:09
*** psachin has quit IRC14:10
*** sdake has quit IRC14:12
*** _hemna has joined #openstack-meeting14:12
*** markvoelker has quit IRC14:13
*** ttsiouts has joined #openstack-meeting14:17
*** belmoreira has quit IRC14:20
*** belmoreira has joined #openstack-meeting14:21
*** eharney has joined #openstack-meeting14:27
*** sdake has joined #openstack-meeting14:35
*** _alastor_ has joined #openstack-meeting14:36
*** _alastor_ has quit IRC14:41
*** mjturek has joined #openstack-meeting14:42
*** dtrainor_ has quit IRC14:45
*** sdake has quit IRC14:50
*** awaugama has joined #openstack-meeting14:51
*** armstrong has joined #openstack-meeting14:51
*** macza has joined #openstack-meeting14:54
*** mjturek has quit IRC14:55
*** awaugama has quit IRC14:56
*** sdake has joined #openstack-meeting14:58
*** macza has quit IRC14:58
*** mjturek has joined #openstack-meeting14:58
*** janki has quit IRC15:00
*** bobh has joined #openstack-meeting15:03
*** macza has joined #openstack-meeting15:03
*** dmacpher has joined #openstack-meeting15:06
*** awaugama has joined #openstack-meeting15:09
*** macza has quit IRC15:09
*** markvoelker has joined #openstack-meeting15:10
*** Luzi has quit IRC15:11
*** diablo_rojo has joined #openstack-meeting15:19
*** macza has joined #openstack-meeting15:19
*** armax has joined #openstack-meeting15:20
*** erlon__ has joined #openstack-meeting15:23
*** artom has quit IRC15:26
*** erlon_ has quit IRC15:26
*** jamesmcarthur has joined #openstack-meeting15:26
*** ociuhandu_ has quit IRC15:28
*** ociuhandu has joined #openstack-meeting15:29
*** macza has quit IRC15:40
*** mjturek has quit IRC15:43
*** markvoelker has quit IRC15:43
*** zbr has joined #openstack-meeting15:46
*** zbr|ssbarnea has quit IRC15:47
*** wwriverrat has quit IRC15:54
*** mjturek has joined #openstack-meeting15:57
*** davidsha has joined #openstack-meeting15:58
*** raildo has quit IRC15:58
*** _alastor_ has joined #openstack-meeting16:04
*** raildo has joined #openstack-meeting16:05
*** zbr|ssbarnea has joined #openstack-meeting16:10
*** raildo has quit IRC16:11
*** zbr has quit IRC16:13
*** rossella_s has quit IRC16:16
*** jrbalderrama has joined #openstack-meeting16:17
*** ttsiouts has quit IRC16:18
*** ttsiouts has joined #openstack-meeting16:18
*** raildo has joined #openstack-meeting16:18
*** ttsiouts has quit IRC16:23
*** zbr has joined #openstack-meeting16:23
*** zbr|ssbarnea has quit IRC16:26
*** gyee has joined #openstack-meeting16:32
*** jamesmcarthur has quit IRC16:34
*** markvoelker has joined #openstack-meeting16:40
*** artom has joined #openstack-meeting16:41
*** jamesmcarthur has joined #openstack-meeting16:46
*** raildo has quit IRC16:46
*** raildo has joined #openstack-meeting16:53
*** sdake has quit IRC17:00
*** rbudden has quit IRC17:02
*** _hemna has quit IRC17:07
*** jrbalderrama has quit IRC17:08
*** tssurya has quit IRC17:09
*** macza has joined #openstack-meeting17:09
*** macza has quit IRC17:13
*** markvoelker has quit IRC17:13
*** sdake has joined #openstack-meeting17:13
*** ociuhandu_ has joined #openstack-meeting17:16
*** ociuhandu has quit IRC17:17
*** pcaruana has quit IRC17:19
*** rbudden has joined #openstack-meeting17:23
*** jamesmcarthur has quit IRC17:24
*** jamesmcarthur_ has joined #openstack-meeting17:25
*** macza has joined #openstack-meeting17:27
*** jamesmcarthur_ has quit IRC17:27
*** davidsha has quit IRC17:29
*** sdake has quit IRC17:31
*** macza has quit IRC17:32
*** e0ne has quit IRC17:33
*** jamesmcarthur has joined #openstack-meeting17:35
*** sdake has joined #openstack-meeting17:35
*** rbudden has quit IRC17:39
*** rbudden has joined #openstack-meeting17:40
*** macza has joined #openstack-meeting17:41
*** mattw4 has joined #openstack-meeting17:41
*** kopecmartin is now known as kopecmartin|off17:42
*** macza has quit IRC17:45
*** rbudden has quit IRC17:47
*** mjturek has quit IRC18:01
*** mjturek has joined #openstack-meeting18:01
*** mjturek has quit IRC18:04
*** mjturek has joined #openstack-meeting18:05
*** mjturek has quit IRC18:08
*** markvoelker has joined #openstack-meeting18:10
*** mjturek has joined #openstack-meeting18:11
*** rbudden has joined #openstack-meeting18:13
*** sdake has quit IRC18:17
*** sdake has joined #openstack-meeting18:19
*** _hemna has joined #openstack-meeting18:22
*** sridharg has quit IRC18:36
*** TxGirlGeek has joined #openstack-meeting18:38
*** cloudrancher has quit IRC18:38
*** mjturek has quit IRC18:39
*** ekcs has joined #openstack-meeting18:41
*** markvoelker has quit IRC18:43
*** ociuhandu_ has quit IRC18:47
*** cloudrancher has joined #openstack-meeting18:55
*** mjturek has joined #openstack-meeting18:56
*** mattw4 has quit IRC18:59
*** mattw4 has joined #openstack-meeting18:59
*** ijw has joined #openstack-meeting19:07
SotKanyone around for the storyboard meeting?19:07
diablo_rojoo/19:07
SotK#startmeeting storyboard19:08
openstackMeeting started Wed Feb  6 19:08:06 2019 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot.19:08
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:08
*** openstack changes topic to " (Meeting topic: storyboard)"19:08
openstackThe meeting name has been set to 'storyboard'19:08
SotK#link https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda19:08
SotKThere are no announcements and I think nothing new about migrations, so lets skip past those19:09
SotK#topic Story Attachments19:09
*** openstack changes topic to "Story Attachments (Meeting topic: storyboard)"19:09
fungithis is the hot topic of the week, to be sure19:09
* diablo_rojo has reviews to do19:09
diablo_rojoIt is indeed19:10
SotK#link https://review.openstack.org/#/q/status:open+topic:story-attachments Attachment changes19:10
SotKI implemented the basic functionality needed for story attachments19:11
SotKthere are some bits missing, for example if your backend has attachments disabled the webclient just hits a bunch of errors instead of behaving sensibly19:12
fungii call that "polish"19:12
*** bobh has quit IRC19:12
SotKyep, me too19:12
fungier, "polishing" perhaps so as not to be confused with the national language of poland ;)19:12
SotKon a similar note, you have to manually set the ACL on the swift container even if you let storyboard create it automatically19:13
diablo_rojoLooks like a solid start to me.19:14
diablo_rojoWay further than I would be if I was the primary dev on the hook ;)19:14
diablo_rojoSo thank you SotK!19:14
SotKnp :)19:14
SotKI started prototyping it and then accidentally made most of it and just decided to finish19:15
fungiin theory if sb can create a container it should also be able to set acls via the same api?19:15
SotKyep, should be trivial to add19:16
fungiagain, detail which can be ironed out later, if it just ends up as documentation i think that's perfectly fine too19:16
fungiand also irrelevant for deployments which don't expect to make use of private stories19:17
SotKthe default is fully private so it needs doing for every deployment19:17
SotKbut yeah, its not exactly onerous, it would just be neater to add it in19:17
fungioh, got it19:18
fungifail closed is safer anyway at least19:18
SotKindeed19:19
diablo_rojoindeed19:19
fungii've only just skimmed so far, but i like that this is all fairly bite-sized changes. nothing massive19:19
SotKyeah it turned out to be quite a bit easier than I expected since all the hard bits are handled by swift itself19:20
diablo_rojoYeah that is super appreciated19:20
SotKI also pushed my config file and a docker-compose.yml file which runs the services needed to test the patches to my github for now19:22
SotK#link https://github.com/ColdrickSotK/storyboard-environment Config for testing19:22
diablo_rojoOh cool19:22
SotKI intend to turn that into something more complete and push it to the storyboard repo in the near future19:23
diablo_rojoSounds good.19:23
*** bbowen has quit IRC19:24
fungithat'll be awesome for getting new contributors up to speed, i think19:24
SotKalong with some docs to go along with it, which hopefully will allow a quick way to get a development environment up and running without needing to remember to install and configure all of the things19:24
fungiabsolutely19:24
fungithat's a huge help19:24
diablo_rojoYes, super helpful19:26
SotKI think that's all I have on attachments19:26
SotKlooking forward to reviews :)19:26
fungithanks!!!19:27
SotK#topic Moving database closer to site19:28
*** openstack changes topic to "Moving database closer to site (Meeting topic: storyboard)"19:28
fungi#link https://etherpad.openstack.org/p/gCj4NfcnbW Database move from Trove to local MySQL service on storyboard.openstack.org19:28
fungithat's the current migration plan19:29
fungithe new xenial-based deployment is up and you can in theory test it out with a local /etc/hosts edit in the meantime19:29
*** e0ne has joined #openstack-meeting19:29
fungithough it's still using trove until the migration is performed19:29
fungii am also suddenly worried by the story jungleboyj just mentioned in #storyboard a few minutes ago, and would like to rule out any relationship to the db move before proceeding19:30
fungi#link https://storyboard.openstack.org/#!/story/2004948 Unable to create worklists ... I am getting a 500 error19:30
diablo_rojoYeah, somewhat concerning19:31
SotKme too, looks a bit suspicious19:31
fungionce we're comfortable with the maintenance plan (it's basically a reflection of what i did for storyboard-dev.o.o a few weeks ago), we just need to pick a quiet 5-ish minutes to do the move19:32
jungleboyjeharney:  Was seeing a number of HTTP 500's as well.19:32
jungleboyjThat was all in the last hour if you have logs.19:32
SotKthough, I expect that the code that threw that error could be improved significantly19:32
jungleboyjWe were trying to do some design for moving Cinder to storyboard but couldn't make much progress.19:33
fungijungleboyj: we definitely have logs, though the sql error is likely sufficient to track it down19:33
jungleboyjWe had a number of other questions that I will follow up on at some point in the storyboard channel.19:33
fungimuch appreciated!19:33
SotKindeed, sorry about the issues :(19:34
SotKthe plan looks sensible to me19:34
SotKbut yeah, we should make sure this is unrelated (or fix it if it is)19:34
diablo_rojojungleboyj, happy to help with suggestions for organization if you want help too19:35
fungiwell, we likely need to fix it either way19:35
SotKyeah, I realised that was terribly phrased after pressing enter19:35
fungiand even SotK and diablo_rojo have local shell accounts on the storyboard-dev server so doesn't just need me to look into it19:35
*** bbowen has joined #openstack-meeting19:35
jungleboyjdiablo_rojo:  Thanks.  I think we have come up with a plan going forward but would like to be able to set up a PoC first.19:36
SotKanything else on the db move?19:36
funginope, only other thing i haven't done yet is to test out the new deployment and confirm it seems to be serving the correct stuff19:36
diablo_rojojungleboyj, sounds good19:36
fungiservices are running but i haven't exercised it yet19:37
SotK#topic In Progress Work19:38
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"19:38
SotKI also sent various small patches to make things nicer and fix various issues that came up whilst working on attachments19:39
diablo_rojoI have several patches I need to update..19:39
*** markvoelker has joined #openstack-meeting19:40
SotKI still have to review one of yours I think19:40
SotKand I want to try to reproduce the weird login bug that fatema was seeing the other week to work out whats going wrong19:41
diablo_rojoI saw several reviews from you, but haven't checked if they were all covered :)19:41
diablo_rojoI have plenty of work to do either way19:41
SotKgood :)19:42
SotK#topic Open Discussion19:44
*** openstack changes topic to "Open Discussion (Meeting topic: storyboard)"19:44
SotKI'll leave this open for a minute or two in case anyone has anything they want to raise19:45
diablo_rojoThere's that Manila ML thread19:47
diablo_rojoabout issues19:47
diablo_rojoI was going to post on it about the migration and how they should keep storyboard in mind when planning/discussing things19:47
SotKoh I think I've missed that19:47
fungia new one? did i miss spotting it?19:47
diablo_rojouhh theres a link on the agenda19:47
diablo_rojoone sec19:47
fungii'll find19:48
SotKha so there is19:48
SotKsorry19:48
SotK#link http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002404.html19:48
fungithanks for spotting that!19:48
*** bobh has joined #openstack-meeting19:49
fungiokay, so i did read that one (and suggested they move from google spreadsheets to ethercalc for openness/inclusivity, and they seem interested in doing that too)19:49
fungioh, wait, it was another (neutron?) bug triaging thread where i recommended ethercalc... this is the one which spontaneously inticated they were moving there19:50
diablo_rojofungi, huh, I don't see a response from you on that thread19:50
diablo_rojoGot a link to that one?19:50
fungiand i remember it warming the cockles of my heart19:50
fungisure, just a sec19:50
diablo_rojoLol19:51
*** mattw4 has quit IRC19:51
fungihttp://lists.openstack.org/pipermail/openstack-discuss/2019-February/002372.html19:51
fungi#link http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002372.html [Neutron] - Bug Report for the week of Jan 29th- Feb4th.19:52
* SotK agrees that it may be worth emailing about keeping storyboard in mind19:53
fungiyes, absolutely19:53
diablo_rojoIts one of my pinned emails to reply to today19:53
diablo_rojostill digging out of the FOSDEM hole19:53
fungioh, speaking of neutron, it may be a worthwhile exercise to repeat the import attempt on storyboard-dev again now that it's a different server and db backend19:53
diablo_rojoOh good call19:54
diablo_rojoI can definitely add that to my list of things to do19:54
fungisince we can at least quickly rule those out and likely confirm the same behavior is still present19:54
diablo_rojoYeah totally19:55
*** jamesmcarthur has quit IRC19:55
diablo_rojoOne other thing.19:55
diablo_rojoIf we want to try to get another outreachy intern we need to apply by the 12th of March.19:55
diablo_rojoI don't know we can get anyone as awesome as fatema, but I think we should try :)19:56
SotKyeah I agree19:56
diablo_rojoWill put together an etherpad with the application info for you both to look over if you're willing to help me out :)19:56
diablo_rojoSotK, wanna be my co mentor again?19:56
SotKand this is significantly more time to prepare than we had last year I think19:56
diablo_rojoYep :)19:56
SotKsure, and I'll try to be more around this time too19:56
diablo_rojoWorked out pretty well last time, but I won't object to more help :)19:57
SotK:)19:58
SotKwe're almost out of time19:58
SotKanything else?19:58
fungii got nothin'19:59
SotKin that case, thanks for coming folks!19:59
SotK#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:00
openstackMeeting ended Wed Feb  6 20:00:01 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-02-06-19.08.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-02-06-19.08.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2019/storyboard.2019-02-06-19.08.log.html20:00
diablo_rojoThanks SotK !20:00
fungithanks SotK!!!20:03
*** erlon__ has quit IRC20:03
*** ijw has quit IRC20:05
*** ijw has joined #openstack-meeting20:06
*** markvoelker has quit IRC20:12
*** sdake has quit IRC20:13
*** aojea has quit IRC20:18
*** ijw has quit IRC20:19
*** sdake has joined #openstack-meeting20:23
*** ijw has joined #openstack-meeting20:24
*** armstrong has quit IRC20:27
*** cloudrancher has quit IRC20:27
*** cloudrancher has joined #openstack-meeting20:30
*** jamesmcarthur has joined #openstack-meeting20:41
*** jamesmcarthur has quit IRC20:41
*** jamesmcarthur has joined #openstack-meeting20:42
*** awaugama has quit IRC20:42
*** raildo has quit IRC20:56
*** timburke has joined #openstack-meeting20:57
*** zaitcev has joined #openstack-meeting20:57
*** sdake has quit IRC20:57
*** sdake has joined #openstack-meeting20:59
*** alecuyer has joined #openstack-meeting20:59
*** patchbot has joined #openstack-meeting21:00
*** e0ne has quit IRC21:00
*** vr42 has joined #openstack-meeting21:00
notmyname#startmeeting swift21:00
openstackMeeting started Wed Feb  6 21:00:52 2019 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
*** vintbra has joined #openstack-meeting21:01
notmynamewho's here for the swift team meeting?21:01
timburkeo/21:01
vr42me21:01
*** _hemna has quit IRC21:01
rledisezhi o/21:01
kota_o/21:01
alecuyerhello o/21:01
notmynamemattoliverau: tdasilva: clayg: ping21:01
notmynamezaitcev: ping21:01
zaitcevwhat21:01
claygwelcome back mr. notmyname !21:01
notmynameit's good to be back21:02
vr42hello all21:02
notmynamealso, I don't think you've ever called me mr before. please stop ;-)21:02
notmynamelet's get started then. lots to go over this week21:02
notmyname#link https://wiki.openstack.org/wiki/Meetings/Swift21:02
notmynameI've been gone a couple of weeks, so I've been trying to catch up with whatever I missed21:03
notmynameso if you had a question or needed me for something and I haven't responded, please ping me again21:03
notmyname#topic housekeeping21:03
*** openstack changes topic to "housekeeping (Meeting topic: swift)"21:03
notmynamea few general things up front21:04
notmynamefirst, big news!21:04
notmynamerledisez has agreed to be a core reviewer. (that happened about 2 minutes before the meeting started, so I haven't had a chance to click the buttons yet)21:04
timburkeyay! \o/21:04
kota_congrats!21:04
claygwoot!21:05
timburkewelcome aboard rledisez!21:05
alecuyercongrats :!21:05
rledisezthx for trusting me, i'll try to reach your high levels of skills on swift21:05
mattoliverauo/21:05
mattoliveraurledisez: congrats!21:05
notmynamerledisez: I'm happy you agreed, and I know you'll continue to do great to help manage and maintain the project21:06
tdasilvarledisez: congrats!21:07
notmyname(now the other housekeeping stuff to talk about will be much less exciting)21:07
rlediseznotmyname: I will. should I swear somewhere that i'll protect the codebase and so on? :D21:07
notmynamei didn't take the time while I was traveling to get the stable branches tagged, so I'm still working on that this week. it should be Real Soon Now (tm)21:07
notmynamerledisez: lol21:08
notmynameso expect that soon (and if you see a backport that doesn't have a review on it, that would be really helpful)21:08
notmynameI'd like to propose a new thing for us to do to help manage patches (it wasn't my idea originally, so I know it's pretty good ;-)21:09
notmynamewe've got the priority reviews page21:09
timburkei think there's just https://review.openstack.org/#/c/629402/ -- i keep meaning to take a look at it...21:09
*** markvoelker has joined #openstack-meeting21:09
patchbotpatch 629402 - swift (stable/pike) - object-server can 409 in response to x-if-delete-at - 1 patch set21:09
notmynamebut we've also got a lot of patches that people have been running in production before they have landed upstream21:10
notmynameI added a new section to the priority reviews page21:10
notmyname#link https://wiki.openstack.org/wiki/Swift/PriorityReviews21:10
notmynameso that we can write those patches down there21:10
claygmakes sense21:10
notmynameI do *not* think that patches listed there should necessarily be higher priority than others, but as reviewers, we can definitely consider the fact that they meet the "works in prod" bar21:11
claygthat's not nothing!21:11
notmynameso.... if you've got patches that your'e running in prod that haven't landed ( rledisez and alecuyer, I think you've got some), please update the wiki with a link to them21:11
rledisezhow should we fill this page? should we just put links (with irc nicknames), or do we talk about it here first?21:11
notmynamerledisez: just update. no need to wait for a meeting21:11
rledisezok, i got my answer ^21:11
timburkei get the impression https://review.openstack.org/#/c/633671/ maybe belongs there...21:11
patchbotpatch 633671 - swift - Fix decryption for broken objects - 6 patch sets21:11
*** slaweq has joined #openstack-meeting21:11
notmynameyeah, is that the one that zigo is running?21:12
timburkeyeah21:12
notmynamegreat! so we've got stuff to fill in already :-)21:12
notmynameok, last bit of housekeeping on the agenda is to raise awareness of the state of our gate21:12
notmynametimburke has been looking at this lately and saying our functests are bad and we should feel bad21:12
notmynameand zaitcev (?) found an issue today with probe tests21:13
timburkeit's sad-face. but hopefully getting better?21:13
zaitcevI think it was someone else21:13
notmynamelike I said, i've just been trying to catch up, but it's something that seems to be a problem recently. timburke, didn't you say 13 of 15 reviews you left were "recheck"?21:13
notmynamesomething crazy like that?21:13
timburkesomewhere around there21:14
timburkehttps://review.openstack.org/#/c/634456/ should definitely help, though; https://review.openstack.org/#/c/634976/ too21:14
patchbotpatch 634456 - swift - func tests: Be willing to retry PUTs (MERGED) - 3 patch sets21:14
patchbotpatch 634976 - swift - Fix flakey symlink setup/teardown (MERGED) - 1 patch set21:14
notmynameso that's the bad news (flakey tests in the openstack gate). but the good news is that it's all in our own tests! this means we can actually fix them pretty easily21:14
claygwooooohoooo!21:14
*** ijw has quit IRC21:14
timburkei also put up https://review.openstack.org/#/c/634362/ and https://review.openstack.org/#/c/634449/21:14
patchbotpatch 634362 - swift - Fix flakey func test setup - 1 patch set21:14
patchbotpatch 634449 - swift - Fix flakey func test teardown - 1 patch set21:14
claygnotmyname: how'd you phrase it?  "The best possible bad news"?21:14
notmynameheh21:14
notmynametimburke: would you say most of these are because the test environment is pretty resource constrained? or is it just bad test code?21:15
*** ijw has joined #openstack-meeting21:15
timburke"easily" -- one of the func test failures i observed was assertion failures about container listings following an object PUT... i'm still not sue how best to address that... it's an eventually consistent system!21:16
claygsome were just bad test code - like we'd assume a 201 on a result that retries on 503 where the second attempt might 202 - but I mean... you don't notice that stuff when everything "just works"21:16
timburkepretty sure it's mostly because of resource constraints in the gate21:16
*** ociuhandu has joined #openstack-meeting21:16
*** vishalmanchanda has quit IRC21:16
notmynameif anyone is wondering how they can help, first step would be to review some of the patches that timburke linked. otherwise, rerunning stuff in your saio and finding intermittent errors and digging in to them is good21:17
timburkei don't think i've *ever* gotten a 503 in a functest on my laptop, even when the fans make it sound like it wants to take off21:18
notmynameok, I'm at the end of my housekeeping list. any other general info things to bring up before we move on to a coupe of other topics?21:18
alecuyerdo you know the configuration of the test environment (CPU, RAM) ? (On SAIO I don't think I ever get errors on my laptop, but i could lower the VM specs)21:18
notmynamehonestly I don't. maybe we could find it in logs. or ask clarkb or fungi21:19
alecuyerok will do21:19
timburkethings like http://logs.openstack.org/71/633671/6/check/swift-dsvm-functional/28d266d/zuul-info/inventory.yaml might have some semi-useful info?21:19
timburkeaha! "cloud: ovh" -- it's *your* fault ;-)21:20
notmynamealecuyer: lowering your VM stats is likely a great idea. or maybe you know of a hosting provider that would give you a lot of small, cheap VMs.... ;-)21:20
alecuyerwoops :-)21:20
notmynamelol21:20
* clayg snickers21:20
alecuyerI will try that and tell you what results I get21:20
timburkei take that back -- that one passed21:20
notmynameok, let's move on21:21
notmyname#topic losf feature branch21:21
*** openstack changes topic to "losf feature branch (Meeting topic: swift)"21:21
notmynamelast week, kota_ and tdasilva and rledisez and alecuyer all met in europe and talked about LOSF21:21
notmynamefrom what I hear, it was great21:21
tdasilva+121:22
kota_+121:22
notmynamerledisez and alecuyer want some feedback from the community, but they also need to write some more docs and tests21:22
alecuyeryes it was :)21:22
notmynamekota_/NTT has been running the code and testing it out, too21:22
rledisezthx again kota_ for the effort you and your colleague put into testing losf21:22
kota_yup21:23
notmynameso, from what I gather, the question was raised about making a formal feature branch for tracking it (instead of keeping it in a few existing gerrit patches)21:23
*** sdake has quit IRC21:23
kota_currently the newest code is at https://github.com/alecuyer/swift/tree/master-losf21:23
rledisezactually, right now, it mostly happen on the github of alecuyer21:23
claygkota_: was there slides!?  tdasilva do you have slides!?21:23
kota_that follows recent master branch in swift upstream21:23
notmynamethe specific question I have for this meeting is "do we need to make feature/losf?" and more generally, what's the state of things21:23
tdasilvarledisez started a nice doc: https://docs.google.com/document/d/1KoLsqWiXv9u2rnMZ5Rh73Js-lwP5h2qRj9CuFJ2IJJc/edit#21:24
notmynameNTT slides are awesome :-)21:24
claygnoice21:24
rledisezalecuyer wrote the doc, I just read it ;)21:24
kota_clayg: I have, but not published. I'll send you if you want to look at.21:24
tdasilvasorry, i meant alecuyer!21:24
fungi#link https://docs.openstack.org/infra/manual/testing.html has details on our test environments21:24
notmynamerledisez: any chance that's linked on the ideas page? errr... I mean that for alecuyer then21:24
alecuyerGroup effort :) Kota also wrote some parts of it21:24
notmynamefungi: thanks21:25
claygkota_: yes pls21:25
*** mattw4 has joined #openstack-meeting21:25
notmynamekota_: even better, link to it on the ideas page!21:25
rledisezit is21:25
alecuyernotmyname:  Yes I think I did, checking (on one existing line)21:25
notmynamegreat21:25
rledisezsearch for "losf design doc"21:25
kota_clayg: alright, i'll send by E-mail. I'm not sure it could be okay to be public.21:25
notmyname#link https://wiki.openstack.org/wiki/Swift/ideas21:25
claygyesir21:26
timburkealecuyer: are we still likely to want something along the lines of https://review.openstack.org/#/c/561631/  as a pre-req?21:26
patchbotpatch 561631 - swift - WIP - abstract FS operations in replicator/reconst... (ABANDONED) - 2 patch sets21:26
rledisezkota_: from OVH point of you, it can be public, we have nothing to hide on LOSF (code is already public so…)21:26
alecuyertimburke:  indeed, currently I have that as the single pre-req on my branch. I still remember we discussed how it was not great ;) but currently, we depend on it21:27
kota_rledisez: exactly, it is.21:27
*** ijw has quit IRC21:27
notmynamealecuyer: I also heard that FOSDEM resulted in some promising stuff with regards to grpc and eventlet/golang21:27
*** ijw has joined #openstack-meeting21:27
claygORLY?21:28
timburkei really like the core *idea* -- just wanted to think more about how to build the abstraction21:28
notmynameclayg: YARLY!21:28
alecuyerYes somebody working on ember-csi has a workaround, which I was looking at earlier tonight, but not done with that and haven't tested, but it is promising21:28
timburkebut, woking code > ideas21:28
*** ijw has quit IRC21:28
alecuyersomething to discuss in another time but here it is :https://github.com/embercsi/ember-csi/blob/master/ember_csi/workarounds.py#L4621:29
claygalecuyer: why container storage abstraction be messing with eventlet?21:29
notmynameclayg: "openstack", IIRC21:29
tdasilvaoh yeah, alecuyer i was supposed to connect you online with geguileo21:29
alecuyerclayg: grpc messing with eventlet21:29
tdasilvahe hangs out on #openstack-cinder21:29
notmynametdasilva: and that person was going to patch eventlet? or grpc? there were going to be patches upstream somewhere, right?21:30
alecuyertdasilva:  he showed me the code at fosdem on his phone21:30
alecuyernotmyname:  he says he will propose a patch upstream in grpc21:30
tdasilvanotmyname, alecuyer: yep21:30
notmynamenice! that's great news21:30
claygwell it says native threads - so you know it's good21:30
kota_nice21:31
notmynameok... so do we need a feature/losf branch? or do we need to wait for a couple of other things first? or some other idea?21:31
notmynameIMO, it sounds like with 2 companies working on it, and some promising work otherwise, it might be time to make the feature branch21:31
rlediseznotmyname: is there strict requirements for having a feature branches? (and what would it be)21:32
kota_I supports creating a branch because it helps us to follow the newest master at least21:32
mattoliverauWell it'll be better to have the code closer to the project, tho FB come with a bunch of overhead and regular master merging21:32
*** ijw has joined #openstack-meeting21:32
notmynamethe downside is that we know it basically needs a "core sponsor" (likely kota_ at this point, and rledisez as he comes up to speed) just to make sure it doesn't get too stale21:32
rledisezI also prefer to see it on gerrit than on github, just to have all the tests running etc…21:32
notmynamerledisez: there's no strict requirements. just the social constraints we ourselves put on it21:33
notmynamebut I don't want a feature branch if nobody is going to look at it for a few months and nobody is going to keep it rebased against master21:33
notmyname*that's* the big cost21:33
timburkeooh yeah... making sure we know how to run with losf *in the gate* is a great reason to have a branch...21:34
claygfeature branch == merge commit at some point yeah?  if we want to split it up to cleanup/code/doc changes the merge commit that bring them in together has a small, but non-zero value21:34
notmynameso "do we make a feature branch" is basically asking "are we ready to work on it as a group and move it towards master"21:34
*** artom has quit IRC21:34
kota_it's not proposed-master branch yet in the feature branch, is it true?21:35
notmynamekota_: correct21:35
notmynamethis would be a development feature branch. not a review branch for an actual merge21:35
kota_i think the past feature branch is to speed up the new change set w/o taken care of the master broken.21:35
claygoic21:35
kota_yup21:35
notmynamemy concern is making sure someone will be able to continually thing about it as it relates to master (including continually merging master into it, or rebasing)21:36
* mattoliverau is a little distracted, and needs to take the toddler to a swimming lesson (first one so I need to be there or she won't get in) +1 to FB so long people are working on it.. I'd like to have it closer and a 1st class work (IE with Gerrit and zuul)21:36
alecuyerwe have said last week with rledisez that I will try to keep this rebased on master weekly21:36
notmynamemattoliverau: understood21:36
zaitcevI always hated feature branches, and hummingbird collapsed, but acoles made it work for encryption, so whatever21:36
notmynamethe point about having gate tests with a feature branch is great21:36
alecuyer(wherever it lives)21:36
claygzaitcev: what's the downside of the feature branch?21:37
notmynamezaitcev: hummingbird's issues were 99% social, not technical. and it's not "bad" that it didn't get merged. all the other feature branches we've done have ended up with pretty great things included in swift21:37
*** ijw has quit IRC21:37
timburkeand we had sharding... and s3api...21:37
zaitcevYes, sharding21:37
zaitcevclayg: mostly that I am too stupid to figure it out21:38
clayghaha!21:38
kota_oic, s3api also had the feature branch21:38
notmynamealecuyer: one logistical issue with a feature branch is that only a core reviewer can propose merge commits to it. you don't rebase the branch against master. master is merged in every so often21:38
zaitcevlike, how to add my own review and then not make it so git-review overwrites other reviews21:38
tdasilvai think there was another before sharding21:38
timburkekota_: yeah... i think we skipped the review branch, though?21:38
notmynamestorage policies were the first21:39
rlediseztdasilva: storage policies?21:39
tdasilvayep21:39
alecuyernotmyname: right, I'll have to learn how to work properly with that21:39
notmynameok ok, here's the full doc on it ;-)21:39
notmyname#link https://wiki.openstack.org/wiki/Swift/feature_branches21:39
alecuyerthanks :)21:39
kota_timburke: oh, might be. only one big patch proposed to the master maybe.21:39
timburkezaitcev: it should work more-or-less like master, particularly on the feature (as opposed to review) branch21:40
notmynamebased on who's been involved in LOSF so far, the core maintainer doing merges from master would likely be kota_. and rledisez could start doing it soon, too.21:40
*** ociuhandu has quit IRC21:40
notmynameso let me rephrase the question21:40
*** vintbra has quit IRC21:41
kota_I might make the effort, imo. Also I may need the rledisez's help tho.21:41
notmynamequestion in two parts (1) kota_ and rledisez are you willing to watch over a feature/losf branch and merge master in to it once every week or two? (2) for everyone else, are you ready to more actively watch the losf work and participate in discussing it?21:41
*** markvoelker has quit IRC21:42
rlediseznotmyname: tbh, I have no idea how much effort it takes, but as it's a goal for OVH to have it merged, I should take the time needed for that. with the help of kota_ I think we can manage to merge master on a regular basis. for the other part, i'll need to read the doc21:43
claygI'd certainly be ready to start advocating that since kota and rledisez are going to be working on the feature branch we NEED to more actively watch the losf work and participate in discussing it21:43
notmynamerledisez: kota_: got it21:43
notmynameclayg: got it21:44
notmynameand timburke sitting next to me, got it (he said the same thing)21:44
claygit'd be great to have a better picture of what that means realistically by the time we get to denver21:44
claygi mean... unless it was gunna be done by then?21:44
notmynameclayg: that is an excellent point21:45
timburkeplus, this definitely falls under the "Open patches that are running in production somewhere" heading...21:45
notmynameclayg: lol... right ... alecuyer: right? done by denver? ;-)21:45
rledisezclayg: i like your optimism ;)21:45
claygk21:45
kota_yup, we have a couple of month in Denver.21:45
alecuyernotmyname: hehe sure ;)21:45
notmynameok, I'll get the feature branch set up this week21:46
rlediseztimburke: i was shy to add it on the priorityreviews page, but I'll do it if you say so ;)21:46
kota_thanks notmyname21:46
claygwooooo!!! FB time21:46
rlediseznotmyname: thanks21:46
notmynameok, moving on21:46
notmynameone more topic in the last 15 minutes21:46
claygI'm doing the FB dance - y'all are missing out21:46
notmyname(thanks, everyone for being patient)21:46
notmyname#topic quadiron for libec21:46
*** openstack changes topic to "quadiron for libec (Meeting topic: swift)"21:46
notmynamevr42: thank you for being patient with us. we had a lot to cover21:47
vr42hello21:47
vr42no worries21:47
notmynametdasilva: can you into vr42 to us please? and the topic?21:47
tdasilvasure21:47
tdasilvaeveryone, vr42 is from Scality and he got in touch asking us about the possiblity of adding QuadIron to libec21:48
kota_nice21:48
tdasilva#link https://github.com/scality/liberasurecode/tree/feat/quadiron-fnt21:48
vr42QuadIron is an EC lib designed for managing a large number of parities21:48
notmynamecool21:48
vr42this is the original project page: https://github.com/scality/quadiron21:48
*** ijw has joined #openstack-meeting21:48
vr42some slides here: https://www.slideshare.net/Scality/quadiron-an-open-source-library-for-number-theoretic-transformbased-erasure-codes21:49
notmyname#link https://github.com/scality/quadiron21:49
alecuyerthanks21:49
notmyname#link https://www.slideshare.net/Scality/quadiron-an-open-source-library-for-number-theoretic-transformbased-erasure-codes21:49
notmyname(for the meeting notes)21:49
vr42ok21:49
vr42one interesting use case is for instance:21:49
vr42take your data, split in 10021:49
vr42generate 200 parities in systematic mode21:49
vr42that means you have 100 parities in clear21:49
vr42100 parities encoded21:50
kota_100+200!? wow21:50
vr42100+10021:50
kota_oic21:50
vr42for an overhead of 2, you can lose 100 drives21:50
tdasilvanow you really need that FB, huh ;)21:50
zaitcevBut we can't store several fragments on one device, right? Our naming scheme does not allow it if partition number is the same. Or does it21:50
notmynamekota_: lol, "only" 200 total ;-)21:50
vr42we do support systematic and non-systematic21:50
notmynamezaitcev: in this case, I don't think using it in swift is as much of a concern. they're "just" integrating with libec for now21:50
vr42yes, liberasurecode is a nice abstraction for us to integrate21:51
notmynamevr42: I think it's awesome that you're integrating with libec21:51
notmynamethat's exactly why it was written21:51
notmynameI've got a few questions (from a maintainer perspective, not ec/tech perspective)21:52
vr42yes21:52
claygzaitcev: we put the frag_index in the on-disk filename - node can have multiple frags if stuff has to move around but the proxy won't ever write them down that way.21:52
notmynamefirst off, what actually needs to be changed in the code to add quadiron? libec should probably allow new libraries without needing to change it's own code (but if not, that should probably be changed anyway)21:52
vr42I had to change a few things21:53
vr42actually for the better21:53
vr42I think21:53
*** ijw has quit IRC21:53
notmynamesecond, since we maintain libec, how do we maintain quadiron integration? how do we test it? can gate tests be added? what sort of lonter-term participation is scality envisioning?21:53
vr42if you want to look at the commit log: https://github.com/scality/liberasurecode/commit/1d414d625ce6b8117e6f2267ea05406cd1e4693421:53
kota_hard coded k+m upper limit, I suppose at leaset.21:53
vr42yes I changed that21:53
vr42and polished the APIs required to manage vectors of fragments rather than bitmaps (it was already there, just polished it)21:54
timburkeseems like it might be a good time to address https://github.com/openstack/liberasurecode/blob/master/src/erasurecode.c#L614 ...21:54
notmynamethird, are there any concerns about legal entangelments with quadiron? patents, trademarks, copyrights, licenses, etc?21:54
vr42no as far as we know it is patent free21:55
notmynamenice21:55
vr42we use a basic multiplicative FFT on a prime field21:55
*** slaweq has quit IRC21:55
vr42it is known in the field for decades21:55
notmynamehow do we test the integration?21:55
notmynameis it possible to integrate gates tests for it?21:56
vr42so, QuadIron itself is tested by CircleCI21:56
notmynameit's open source?21:56
vr42we have a fork of liberasurecode, we can also set a CircleCI on it21:56
notmynameok21:56
vr42QuadIron is open-source21:56
notmynameso the merged fork would have zuul tests in it so they can run with the other stuff in the gate (right?)21:56
vr42I have a question: in our PR, we have 2 different change sets21:57
vr421) is the minimal changes we had to do to libec to make it working (polishing, etc)21:57
vr422) is the quadiron backend code itself21:57
vr42should we make 2 PRs ? or 2 different commits in the same PR ?21:58
timburkenotmyname: we've done that sort of thing before (though after the fact), for isa-l and jerasure: https://review.openstack.org/#/c/604391/21:58
patchbotpatch 604391 - liberasurecode - Install Jerasure and ISA-L libs (MERGED) - 5 patch sets21:58
notmynametimburke: +121:58
notmynamevr42: does the first patch make sense on its own? would you have proposed it anyway?21:59
kota_vr42: liberasurecode is maintained under openstack namespace that means github's pr is not a way to push to upstream.21:59
*** mjturek has quit IRC21:59
kota_it's just a note.21:59
notmynamepersonally, I love the idea of integrating more ec libraries into libec. I think we should encourage that all the time. I'd love for scality to contribute this.21:59
kota_notmyname: +121:59
vr42I actually found a bug here https://github.com/scality/liberasurecode/commit/1d414d625ce6b8117e6f2267ea05406cd1e46934#diff-47d435f29c8b3e47130b1fbf03f1ef60R22622:00
notmynamedoes anyone else have concerns or questions about the mechanics of adding quadiron support to libec?22:00
vr42for backends with headers22:00
*** zbr|ssbarnea has joined #openstack-meeting22:00
vr42it was a case not managed22:00
timburkevr42: if proposed as two commits, it'll create two reviews (essentially, PRs) in gerrit, with the second depending on the first. that's fine. if you'd prefer it as a single commit, i'm sure we can work with that, too22:00
zaitcevvr42: as a reviewer I do prefer a user or caller, even a sample one, to be there for an api change. If you need a new method, for instance, it needs an explanation how it's used at the very least. But other than this, if you can separate cleanups into a separate commit, that's better.22:00
vr42ok22:00
notmynamevr42: if the first patch set would be good anyway, then it should likely be two separate patches. if not, then it should likely be squashed22:00
notmynamezaitcev: I agree22:01
vr42ok22:01
*** zbr|ssbarnea has quit IRC22:01
notmynamewe're running over our time a little bit, so let me try to sum up what happens next22:01
tdasilvagood docs on adding dependency in gerrit: https://docs.openstack.org/infra/manual/developers.html#adding-a-dependency22:01
tdasilvavr42: ^^^22:01
vr42ok thanks22:01
notmynameI'm not hearing any major concerns with scality proposing this integration (in fact, people are suggesting helpful ways to do it well)22:02
notmynameso vr42 should make the patch proposals to libec22:02
*** zbr has quit IRC22:02
notmynameone thing the community will be looking for is the ability to test this code in the gate22:02
vr42ok nice22:02
tdasilvavr42: let me know if you need help the ansible gate jobs, but what timburke linked above should be a good pointer22:03
notmynameand for the time being vr42 should consider the quadiron integration idea as a welcome one22:03
timburke+122:03
vr42tdasilva: I will reach out to you22:03
vr42tdasilva: in case22:03
vr42If you have any questions on QuadIron itself, feel free to ask22:04
notmynameare there any other questions about this? or concerns you'd like to raise now?22:04
vr42in forum.zenko.io22:04
vr42thanks folks22:05
notmynameof course, if someone wakes up tomorrow and has another question or concern about it, feel free to pm me about it22:05
notmynamevr42: thanks for coming (and being patient). and I'm looking forward to the quadiron integration!22:05
notmyname#topic other22:05
*** openstack changes topic to "other (Meeting topic: swift)"22:05
notmynameanything else from anyone else this week?22:05
notmyname(yes, we're 5 minutes over on time already)22:05
notmynamex up if you've got something to say22:06
notmyname(ie type an x)22:06
notmynameall right, let's call it done22:06
notmynamethank you everyone from coming this week. thank you for your work on swift!22:06
notmyname#endmeeting22:06
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"22:06
openstackMeeting ended Wed Feb  6 22:06:38 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-02-06-21.00.html22:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-02-06-21.00.txt22:06
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-02-06-21.00.log.html22:06
*** timburke has left #openstack-meeting22:06
*** alecuyer has left #openstack-meeting22:07
*** zaitcev has left #openstack-meeting22:08
*** ijw has joined #openstack-meeting22:11
*** vr42 has quit IRC22:11
*** ijw has quit IRC22:16
*** TxGirlGeek has quit IRC22:34
*** TxGirlGeek has joined #openstack-meeting22:35
*** sdake has joined #openstack-meeting22:38
*** bobh has quit IRC22:38
*** markvoelker has joined #openstack-meeting22:40
*** TxGirlGeek has quit IRC22:59
*** eharney has quit IRC22:59
*** ijw has joined #openstack-meeting23:03
*** mattw4 has quit IRC23:03
*** mattw4 has joined #openstack-meeting23:03
*** vintbra has joined #openstack-meeting23:07
*** ttsiouts has joined #openstack-meeting23:08
*** markvoelker has quit IRC23:13
*** TxGirlGeek has joined #openstack-meeting23:19
*** rbudden has quit IRC23:28
*** ijw has quit IRC23:29
*** ijw has joined #openstack-meeting23:30
*** vintbra has left #openstack-meeting23:34
*** mjturek has joined #openstack-meeting23:44
*** mjturek has quit IRC23:45
*** imacdonn has quit IRC23:49
*** imacdonn has joined #openstack-meeting23:49
*** mriedem has quit IRC23:56

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!