Wednesday, 2019-02-13

*** markvoelker has quit IRC00:06
*** jamesmcarthur has joined #openstack-meeting00:10
*** _alastor_ has quit IRC00:11
*** jamesmcarthur has quit IRC00:16
*** david-lyle has joined #openstack-meeting00:18
*** manjeets has quit IRC00:18
*** manjeets has joined #openstack-meeting00:19
*** dklyle has quit IRC00:21
*** sdake has quit IRC00:26
*** tetsuro has joined #openstack-meeting00:26
*** isq_ has joined #openstack-meeting00:29
*** yamahata__ has quit IRC00:30
*** armax has joined #openstack-meeting00:32
*** sdake has joined #openstack-meeting00:46
*** macza has quit IRC00:49
*** Liang__ has joined #openstack-meeting00:52
*** jamesmcarthur has joined #openstack-meeting00:53
*** ekcs has joined #openstack-meeting00:54
*** jamesmcarthur has quit IRC00:54
*** mriedem is now known as mriedem_away00:57
*** mriedem_away has quit IRC01:00
*** markvoelker has joined #openstack-meeting01:03
*** jamesmcarthur has joined #openstack-meeting01:04
*** gyee has quit IRC01:07
*** gyee has joined #openstack-meeting01:10
*** sdake has quit IRC01:14
*** sdake has joined #openstack-meeting01:17
*** diablo_rojo has quit IRC01:17
*** bbowen_ has quit IRC01:25
*** JangwonLee has joined #openstack-meeting01:28
*** bbowen_ has joined #openstack-meeting01:29
*** sdake has quit IRC01:29
*** jamesmcarthur has quit IRC01:30
*** Liang__ has quit IRC01:31
*** sdake has joined #openstack-meeting01:32
*** jamesmcarthur has joined #openstack-meeting01:33
*** markvoelker has quit IRC01:35
*** phuochoang has quit IRC01:37
*** sdake has quit IRC01:39
*** gyee has quit IRC01:47
*** armax has quit IRC01:51
*** jamesmcarthur has quit IRC01:53
*** jamesmcarthur has joined #openstack-meeting01:54
*** jamesmcarthur has quit IRC02:05
*** tetsuro has quit IRC02:05
*** jamesmcarthur has joined #openstack-meeting02:16
*** hongbin has joined #openstack-meeting02:21
*** armax has joined #openstack-meeting02:23
*** jamesmcarthur has quit IRC02:28
*** macza has joined #openstack-meeting02:35
*** ekcs has quit IRC02:37
*** macza has quit IRC02:39
*** vishakha has joined #openstack-meeting02:58
*** jamesmcarthur has joined #openstack-meeting02:59
*** jamesmcarthur has quit IRC03:06
*** sdake has joined #openstack-meeting03:06
*** bswartz has joined #openstack-meeting03:22
*** jamesmcarthur has joined #openstack-meeting03:26
*** jamesmcarthur has quit IRC03:30
*** sdake has quit IRC04:15
*** enriquetaso has quit IRC04:28
*** lbragstad has quit IRC04:32
*** janki has joined #openstack-meeting04:32
*** macza has joined #openstack-meeting04:43
*** macza has quit IRC04:48
*** armax has quit IRC04:48
*** rbudden has quit IRC04:54
*** hongbin has quit IRC04:55
*** tetsuro has joined #openstack-meeting04:59
*** cloudrancher has joined #openstack-meeting05:47
*** psachin has joined #openstack-meeting05:49
*** cloudrancher has quit IRC05:52
*** markvoelker has joined #openstack-meeting06:00
*** markvoelker has quit IRC06:04
*** tetsuro has quit IRC06:09
*** imacdonn has quit IRC06:13
*** sridharg has joined #openstack-meeting06:19
*** sdake has joined #openstack-meeting06:28
*** factor has quit IRC06:29
*** Luzi has joined #openstack-meeting06:43
*** diablo_rojo has joined #openstack-meeting06:50
gmann#startmeeting fc_sig07:00
openstackMeeting started Wed Feb 13 07:00:26 2019 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.07:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:00
*** openstack changes topic to " (Meeting topic: fc_sig)"07:00
openstackThe meeting name has been set to 'fc_sig'07:00
gmannPing list: gmann, mattoliverau, cmurphy, tonyb07:00
diablo_rojoo/07:00
cmurphyheya07:00
*** markvoelker has joined #openstack-meeting07:00
mattoliverauo/07:00
tonyb\o07:00
gmannwe have full strength today. let's start. i will host meeting today to help diablo_rojo not to awake so late07:01
gmannlet's go through the home work item07:02
gmann#topic New Contributor Patches07:02
*** openstack changes topic to "New Contributor Patches (Meeting topic: fc_sig)"07:02
diablo_rojoWell..not have to think quite as hard07:02
gmann#link https://review.openstack.org/#/q/reviewedby:%22Welcome%252C+new+contributor!+(10068)%22+is:open+-project:+openstack-dev/sandbox+AND+-project:openstack-dev/ci-sandbox07:02
gmannwho all did home work ?07:02
gmanni did not find any new patch getting attention07:02
mattoliverauI did.. well a quick look anyway07:03
diablo_rojoI reviewed efried's patch in the contributor guide repo instead?07:03
gmannthanks.07:03
* tonyb did the homework but there wasn't anything I felt I could help with07:03
gmanndiablo_rojo: that is merged ?07:03
mattoliverauthere was an openstack client one I delegated ;)07:03
gmannmattoliverau: thanks, i saw your reply there.07:04
gmann#topic Ask.openstack.org Contribution Questions07:04
*** openstack changes topic to "Ask.openstack.org Contribution Questions (Meeting topic: fc_sig)"07:04
gmannthere is no new question on that.07:05
gmannso passing it ?07:05
mattoliverauI didn't see one, tho diablo_rojo probably asked some more no doubt :)07:05
mattoliveraui'm ok to move on07:06
gmannok07:06
gmann#topic Sandbox Bot07:06
*** openstack changes topic to "Sandbox Bot (Meeting topic: fc_sig)"07:06
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002291.html07:06
gmann#link https://review.openstack.org/#/c/636466/107:06
gmanntonyb: your turn07:06
*** apetrich has joined #openstack-meeting07:06
tonybOh yeah so ...07:07
diablo_rojoI did not ask any new one actually.07:07
tonybI sent the rough design to the list and got reasonable feedback07:07
*** sdake has quit IRC07:07
mattoliveraunice one tonyb07:07
tonybSo now t'all can add 'Bot-Reviewer: Simple' and 'Depends-On: https://review.openstack.org/636466'07:08
tonyblike https://review.openstack.org/#/c/636545/07:08
tonyband test out the bot07:08
tonybcurrently the bot is in 2 halves07:08
tonybone runs in the check pipeline and just logs what it'd do07:08
*** apetrich has quit IRC07:08
*** imsurit_ofc has joined #openstack-meeting07:08
mattoliverauoh nice07:08
diablo_rojoWOOHOO!07:08
tonybhttp://logs.openstack.org/45/636545/2/check/bot-reviewer/8cb4696/job-output.txt.gz#_2019-02-13_05_59_29_76004607:09
gmanngreat07:09
tonyband the second part is runnign on my laptop every 10 mins and actually votes07:09
tonyblike https://review.openstack.org/#/c/636545/07:09
tonyblook for 'OpenStack bot-reviewer'07:09
tonybcurrently it's really dumb07:09
tonybit just looks for tagged chnages and replies to PS 1 with 'please publish a new patchset'07:10
tonyband then replies to patchset 2 with +2+W07:10
tonybanything >2 it says 'uum I'm a dumb bot runnign away'07:10
mattoliveraulol07:11
diablo_rojoSounds like its most of the way there07:11
diablo_rojoLol07:11
mattoliveraugreat start tho07:11
diablo_rojoYeah. Very good progress.07:11
tonybonce we/I play withthe bot a little and tweak it 'til I'm reasonably happy I can more it out of the sandbox repo into project-config07:11
tonybif you want to actually hack on the bot gho for it just bas it on https://review.openstack.org/#/c/636466/07:12
diablo_rojoWhat do you need us to do besides review the patches?07:12
tonybideas, reviews and light testing07:12
gmanntonyb:  thanks, nice work. you want more review/testing on sandbox patch or after moving to project-config07:12
* mattoliverau plans to have a play tomorrow :)07:13
tonybgo nuts07:13
gmannok, let's review the 636466 and testing, feedback.07:14
tonybI got lots out of it so it was well worth the hours I put in07:14
* diablo_rojo will also send garbage patch tomorrow to play with bot07:14
gmannnice, thanks again.07:14
mattoliverauthat's awesome effort tonyb, thanks!07:15
gmanntonyb: anything else on this ?07:15
tonybIt doesn't look like the +W is workign as expected07:15
tonybnope07:15
gmanntonyb: you mean it does not merge after +W ?07:15
tonybI'm pleased with the progress07:15
tonybgmann: yeah07:15
gmanni see07:15
tonybWe probably need to think about exactly how we're going to use it in OUI and the contributor guide and teach it more tricks07:16
gmannok, let's check on gerrit. thanks07:16
gmannmoving next07:16
gmann#topic Summit + Forum Planning07:16
*** openstack changes topic to "Summit + Forum Planning (Meeting topic: fc_sig)"07:16
gmann#link https://etherpad.openstack.org/p/FC_SIG_Denver_forum_topics07:16
gmannthanks mattoliverau for creating the etherpad. it is empty so let's put the ideas07:17
mattoliverau+107:17
gmann#topic Reqs for Organisations Contributing to OpenStack07:17
*** openstack changes topic to "Reqs for Organisations Contributing to OpenStack (Meeting topic: fc_sig)"07:17
mattoliverausandbox bot hacking and brainstorming ;)07:17
gmannmattoliverau: your follow up patch is merged, anything else to do in this ?07:18
gmannmattoliverau: +1, we can get more ideas for that.07:18
mattoliverauNot that I'm aware of, though I haven't really looped back round on it.07:18
cmurphyi did https://review.openstack.org/633939 since last meeting07:18
mattoliverauI was kinda at sleep school for the baby all weekend + parts of friday and monday, so I'm all over the place this week07:19
*** belmoreira has joined #openstack-meeting07:19
gmanncmurphy: thanks, that nice.07:19
gmanni saw "Will wait for Board of Directors Individual elections to be done before presenting to board"07:19
gmanndiablo_rojo: ^^ its time for that now ?07:19
mattoliveraucmurphy: nice! the power of an action item works07:19
cmurphymattoliverau: ikr07:19
diablo_rojoI think the election is done so I just need to push to get on the Agenda07:20
gmannthanks07:20
mattoliveraudiablo_rojo: cool.. sounds like an action item ;)07:20
diablo_rojoIdeally not for the one at the summit so I don't have to leave OUI07:20
diablo_rojomattoliverau, yeah...quite possibly07:20
gmann#action diablo_rojo to present the organization contributor guide to board07:21
mattoliverau\o/07:21
gmannanything else on this or move next ?07:21
diablo_rojoNothing else from me07:22
gmann#topic Help Wanted List07:23
*** openstack changes topic to "Help Wanted List (Meeting topic: fc_sig)"07:23
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002345.html07:23
gmannas you all have observed the discussion on help-wanted-list ^^, there are idea of adding the help-wanted list under FC SIG07:23
gmanncmurphy: diablo_rojo and myself replied in that.07:24
gmannas summary if i am not wrong : diablo_rojo is ok to add under FC SIG, gmann want it under project team , cmurphy :  under TC07:24
gmannhere we can discuss if it is suitable to keep under FC SIG or not07:25
diablo_rojoI am fine with it not living with us. It had just sounded like living with the TC wasn't an option anymore and I thought living with us made the most sense.07:25
mattoliverauso under all the things07:25
diablo_rojoLiving with us but written by the projects I guess was what I was thinking07:26
gmanndiablo_rojo: i agree on not under TC which make me worried of not success again.07:26
mattoliverauDepends on how granular the help wanted list will be07:26
mattoliverauif it's at the "oh project X need help" then that's one thing07:26
*** jamesmcarthur has joined #openstack-meeting07:26
gmannon being under FC SIG, i think we will get challenge of not uptodate, help from team on maintaining, mentor mapping etc07:26
mattoliverauif its a list of things in each project that projects need help on, then in each project agrigated to somewhere makes sense07:27
mattoliveraumaybe we manage the agrigation.. ie in the collab guide?07:27
gmannmattoliverau: it can be list which need help and mostly it will be from project team side. or some horizontal team where less contributors07:27
gmannSIG and pop-up team can be asking to add in this list based on need.07:28
diablo_rojoI would agree that it would be challenging to keep projects involved07:28
mattoliverauSo maybe a help_wanted (or better name) in each developer docs. And then agrigate the list up to collab guide / help wanted.07:29
*** aojea has joined #openstack-meeting07:29
* mattoliverau is just brainstorming07:29
mattoliverauthough we'd need a way for cross project or even sigs can get on the list.. so not just dev docs07:29
mattoliverauor just projects07:29
*** imsurit_ofc has quit IRC07:30
cmurphyimo the projects who want help and are willing to put up the personhours to do mentoring should apply to be on the list and be approved (by somebody tc or otherwise) the same way we do with the current help wanted list07:30
*** imsurit_ofc has joined #openstack-meeting07:30
*** jamesmcarthur has quit IRC07:31
* mattoliverau wont lie I am ignorant on how the current help_wanted works. 07:31
diablo_rojoSeems like the format of the psotings just needs to change to be a specific implemention with completion criteria and a mentor07:31
gmannadditional from current way, it will be mentoring-mapping to that list.07:31
diablo_rojoAnd there needs to be a TC member/champion to beat on the drum07:31
mattoliveraudoes needing a tc champion make it hard to do it outside the tc?07:32
mattoliverauor they just want others to manage and then defer to them when the time comes?07:32
cmurphyi think that's still part of the question07:34
*** markvoelker has quit IRC07:34
mattoliveraukk07:34
gmannyeah, with our FC hat on we can at least conclude that whether the FC a good place to do that or not considering our mission and challenges to do that07:35
*** e0ne has joined #openstack-meeting07:36
gmannwhere it can be otherwise is next question.07:36
diablo_rojoI think if the TC doesn't own it, I would vote for it to live here. But if it can stay with the TC I think that makes the most sense for visibility + who should be managing it?07:37
gmannok07:38
cmurphyI didn't get the impression from the thread that the TC wasn't willing to still own it, just that it wasn't working in its current form07:38
mattoliverauAny ideas on how it's currently used, ie does it tend be a call to arms of existing devs, or does it attract new contributors. I guess it could be a nice carrot for us and new contributors07:38
mattoliverauI guess both.07:38
mattoliverauok07:38
diablo_rojoPerhaps I misread then :)07:38
cmurphymattoliverau: it's this https://governance.openstack.org/tc/reference/help-most-needed.html07:38
cmurphyit's a vague shout in the dark07:39
diablo_rojomattoliverau, I dont think it gets used at all really07:39
diablo_rojoExactly.07:39
gmannyeah07:39
gmanni am also ok with under TC but with mentor mapping as entry criteria.07:39
mattoliverauhmm. then I'd agrue and say it's a great thing to have.. but yes it needs more visibility.. maybe moving it to the contributor guide or the community portal and away from TC pages is step 1. no matther who ends up managing it.07:40
cmurphythere's no explicit guidance on what work items need be done, no incentive to join the effort, no criteria for removing an item from the list, and while there's a "sponsor" there's no mentor07:40
gmannmattoliverau: but we need owner for that.07:40
diablo_rojoI think requiring all of those things would keep the list short without having to cap it.07:41
gmannyeah, prioritizing and keep the list short can be challenge  but let's see when we have process short out07:42
diablo_rojoI also think that there should maybe be a lifespan for each item.07:42
diablo_rojoTo make sure things don't go stale07:42
diablo_rojoIf it hasnt been completed in 2 releases or something, it should be removed and have to go through the process again.07:42
cmurphythat seems fair07:43
diablo_rojoSomeone want to summarize this on the thread?07:44
gmannhttps://www.irccloud.com/pastebin/Agc1z0lx/07:44
gmannmultiline :)07:44
gmannis that ok for all  ?07:45
diablo_rojoYeah I think so?07:45
tonybgmann: you can just click 'paste as messages' instead of creating a snippet07:45
gmannyeah just pressed enter in hurry07:45
tonybgmann: Ahh okay07:45
*** kopecmartin|off is now known as kopecmartin07:46
*** asmita_ has joined #openstack-meeting07:46
cmurphythanks gmann07:46
gmanni can add the summary of our discussion on ML07:46
gmannthanks all.07:47
gmann#topic People to Reach Out To07:47
*** openstack changes topic to "People to Reach Out To (Meeting topic: fc_sig)"07:47
diablo_rojoThanks gmann!07:47
gmannhas anyone get any reply/success on this ?07:47
diablo_rojoNo success from me sadly07:47
gmannme too.07:48
mattoliveraume either07:48
gmannone idea is try to catch people (their company active developer) during summit/PTG and talk. but in positive way so that they do not get offended.07:48
*** slaweq has joined #openstack-meeting07:48
gmann#action gmann to summaries the "Help- Wanted List" discussion over ML reply.07:49
mattoliverauthats true, I real life contributor hunt :)07:49
mattoliverau*a07:49
diablo_rojoIf we can find them in person yeah, chatting directly would be good07:50
mattoliverauor if there company has a booth.07:50
mattoliveraubut positive and nice is the key.07:50
diablo_rojo+207:50
mattoliverauesp the china summit07:50
gmannnice. let's plan from this summit as start.07:51
diablo_rojoCould also invite them to whatever FC SIG sessions we have07:51
gmann+1. that can be nice.07:51
gmannwe can chat about it over summit also, no specific action item on this. ok ?07:52
mattoliveraukk07:52
gmann#topic open discussion07:52
diablo_rojoOkay07:52
*** openstack changes topic to "open discussion (Meeting topic: fc_sig)"07:52
gmannone thing from me, i mentioned in last meeting also. I will be moving to canada on 20th feb07:53
diablo_rojoEveryone got flights/hotels/registration sorted for Denver?07:53
mattoliverauoh nice07:53
* tonyb does07:53
cmurphygmann: awesome07:53
gmannit should be for long term if things are shorted out for next financial year07:53
tonybgmann: Oh cool!07:53
tonybgmann: which city?07:53
diablo_rojoWoohoo! gmann hope all goes well :)07:53
cmurphydiablo_rojo: not officially approved yet07:53
mattoliveraunot yet, still waiting to hear.07:54
* cmurphy hi5 mattoliverau07:54
gmannthanks07:54
mattoliverau:)07:54
gmanntonyb: currently winnipeg (my wife university )07:54
* tonyb thinks about TZ overlap and meeting times07:54
gmannplan is for vancouver if all well next financial year07:54
cmurphyfrustrating thing about the combined summit/ptg is now ptg attendance is tied to cfp acceptance again :(07:54
diablo_rojocmurphy :/07:55
gmannyeah07:55
tonybcmurphy: yeah it's all so confusing07:55
gmanntonyb: current time will be like 1 AM for me.07:56
tonybgmann: Yeah07:56
* mattoliverau hears alot of crying, he may need to go save his better half soon.07:56
tonybI guess as of March'ish we'll need to move the meeting07:56
tonybwhich I'm sure will be good for diablo_rojo and cmurphy ;P07:57
cmurphyi'll be moving to the US beginning of April so maybe would be good to re-doodle this meeting soonish07:57
diablo_rojoWon't need to account for Europe anymore so we can focus on US + AUS07:57
gmanncmurphy: +107:57
mattoliverau+107:57
tonybcool07:57
mattoliveraugood for me as it'll be out of baby + toddler bed rutuine and craziness :)07:58
gmann+107:58
gmannlet's wait till april once cmurphy is moved to USA  ?07:58
mattoliverauonly about a minute to go07:58
gmannyeah. let's discuss it over next meeting.07:59
tonybokay07:59
cmurphygmann: we could do it sooner, sounds like either way one of us will miss a couple of meetings07:59
gmannthanks all for joining. have good day/night.07:59
gmanncmurphy: yeah07:59
*** rubasov has left #openstack-meeting07:59
mattoliverauthanks gmann for charing07:59
gmann#endmeeting07:59
diablo_rojoThanks gmann07:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"07:59
openstackMeeting ended Wed Feb 13 07:59:49 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/fc_sig/2019/fc_sig.2019-02-13-07.00.html07:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/fc_sig/2019/fc_sig.2019-02-13-07.00.txt07:59
cmurphythanks gmann07:59
openstackLog:            http://eavesdrop.openstack.org/meetings/fc_sig/2019/fc_sig.2019-02-13-07.00.log.html07:59
* mattoliverau gotta go o/07:59
tonybmattoliverau: see you on Saturday! (I hope)08:02
*** ralonsoh has joined #openstack-meeting08:05
*** tetsuro has joined #openstack-meeting08:09
*** diablo_rojo has quit IRC08:10
*** macza has joined #openstack-meeting08:14
*** macza has quit IRC08:19
*** markvoelker has joined #openstack-meeting08:31
*** asmita_ has quit IRC08:33
*** niska has quit IRC08:54
*** tetsuro has quit IRC08:57
*** niska has joined #openstack-meeting08:59
*** tssurya has joined #openstack-meeting09:00
*** markvoelker has quit IRC09:04
*** niska has quit IRC09:06
*** e0ne has quit IRC09:06
*** e0ne has joined #openstack-meeting09:07
*** ociuhandu has quit IRC09:07
*** yamamoto has quit IRC09:10
*** yamamoto has joined #openstack-meeting09:12
*** sunnaichuan has joined #openstack-meeting09:15
*** niska has joined #openstack-meeting09:17
*** ociuhandu has joined #openstack-meeting09:20
*** ociuhandu has quit IRC09:25
*** macza has joined #openstack-meeting09:31
*** ociuhandu has joined #openstack-meeting09:34
*** e0ne has quit IRC09:34
*** macza has quit IRC09:35
*** ociuhandu has quit IRC09:38
*** aojea has quit IRC09:40
*** aojea has joined #openstack-meeting09:47
*** aagate has quit IRC09:55
*** markvoelker has joined #openstack-meeting10:02
*** ociuhandu has joined #openstack-meeting10:12
*** ralonsoh has quit IRC10:16
*** yamamoto has quit IRC10:30
*** erlon has joined #openstack-meeting10:31
*** ralonsoh has joined #openstack-meeting10:32
*** markvoelker has quit IRC10:34
*** ralonsoh has quit IRC10:45
*** ralonsoh has joined #openstack-meeting10:45
*** e0ne has joined #openstack-meeting10:46
*** oneswig has joined #openstack-meeting10:50
*** e0ne_ has joined #openstack-meeting10:50
*** imsurit_ofc has quit IRC10:52
*** imsurit_ofc1 has joined #openstack-meeting10:52
*** e0ne has quit IRC10:52
*** imsurit_ofc1 is now known as imsurit_ofc10:54
*** janders has joined #openstack-meeting10:58
*** b1airo has joined #openstack-meeting10:59
oneswig#startmeeting scientific-sig11:00
openstackMeeting started Wed Feb 13 11:00:12 2019 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot.11:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.11:00
*** openstack changes topic to " (Meeting topic: scientific-sig)"11:00
openstackThe meeting name has been set to 'scientific_sig'11:00
b1airoevening11:00
oneswigGreetings Earthlings11:00
oneswig#chair b1airo11:00
openstackCurrent chairs: b1airo oneswig11:00
jandersgood evening11:00
oneswig#link Agenda for today https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_February_13th_201911:00
b1airohmm, never noticed the info command before, what does that do...?11:00
oneswigHi janders11:00
b1airo#info11:01
b1airo#help11:01
b1airo#help info11:01
* oneswig wonders what that big red button does11:01
jandersboom!11:01
jandersgreat balls of fire11:01
b1airopush it! push it!11:01
oneswigha.  Kids must have coloured in the light switch again :-)11:01
b1airoyes, i subscribe to the "don't ask for permission..." doctrine11:02
*** ociuhandu has quit IRC11:02
b1airoi think there's something about maybe apologising afterwards11:02
oneswigA good mantra, except possibly when driving.11:02
jandersor handling nukes11:03
oneswigso true!11:03
b1airomy nana had a "vertical takeoff" button in one of her cars i remember quite clearly. had disappointing results, i.e., nothing11:03
*** verdurin has joined #openstack-meeting11:03
*** ociuhandu has joined #openstack-meeting11:03
oneswigOver here we had a research computing cloud conference yesterday, was a good session as usual11:04
jandersa friend had a star trek voice in his GPS. Instead of "arriving at destination" it had "initiate docking sequence"11:04
b1airoheh, nerd status plus11:04
oneswigjanders: So impressive, except possibly when going on a first date.11:04
verdurinMorning.11:04
oneswigHi verdurin, morning11:05
oneswigGood work yesterday11:05
*** ralonsoh has quit IRC11:05
verdurinYes, I thought it was a good day.11:05
*** yamamoto has joined #openstack-meeting11:05
oneswigMe too.  We should perhaps compare notes in AOB.11:05
jandersregarding research computing & cloud - does AlaSKA ingest data straight from Telescope/FPGAs?11:06
b1airosounds intriguing11:06
janders(was chatting to Radioastronomy guys this arvo)11:06
oneswigjanders: only simulated ones.11:06
jandersI was wondering if radioastronomy is a good use case for dual-interconnect bare-metal clouds11:06
janders(ingest via 100GE/ROCE, write to IB parallel FS)11:07
oneswigWe generate artificial streams of UDP data ("SPEAD" packets) due to our lack of actual telescope11:07
oneswigjanders: exactly so.11:07
b1airoit's all just white noise anyway, amirite?11:07
* b1airo ducks11:07
oneswigb1airo: the noise is far, far louder than the signal11:08
oneswigThere was that famous snowflake analogy11:08
jandersI will see if we can find some common ground.. I think they might really need some kit in the middle of WA desert - which might be doable but not sure how popular with the execs11:08
oneswighttps://www.goodreads.com/quotes/865839-the-total-amount-of-energy-from-outside-the-solar-system11:08
jandersedge computing is a hot topic and 1Tbps links are rather expensive11:08
jandersno snowflakes in Western Australia, I don't think11:09
oneswigjanders: kit in the desert is a desperate measure, not to be taken lightly, from what I've heard.11:10
ildikovedge computing is indeed a hot topic, I'm happy to learn if you have a use case :)11:10
oneswigHi ildikov!11:10
ildikovoneswig: hi :)11:10
oneswigMany, I'd say11:10
ildikovI'm just lurking11:10
*** janders_ has joined #openstack-meeting11:10
oneswigLurk away :-)11:10
oneswigNext topic might benefit from some Foundation input11:11
ildikovalso co-leading the edge working group and we're always hungry for cool new use cases!11:11
oneswig#topic OpenStack at ISC11:11
*** openstack changes topic to "OpenStack at ISC (Meeting topic: scientific-sig)"11:11
janders_ildikov: good to know11:11
b1aironothing cool about a containerised data-centre in the middle of Western Australia desert, except the concept and science, obviously11:12
oneswigildikov: perhaps we should set aside a session to discuss edge use cases11:12
janders_+111:12
ildikovsounds good to me11:12
b1airoyeah, seems very relevant for research/science orgs11:12
ildikovwe have some examples here: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases11:12
oneswigOK, there's a BoF opportunity to gather people attending ISC in Frankfurt in June11:13
oneswigDeadline next Wednesday (20th February)11:13
oneswigIt would be good to gather panelists for a BoF proposal11:14
*** janders has quit IRC11:14
*** yamamoto has quit IRC11:14
janders_I don't think it's likely I will make it to the ISC but I can ask around the other teams who's going11:14
oneswigWe've contacted a couple of people from EOSC and ELIXIR federations, but I think we need 5 or so people to put their names to it.11:14
ildikovI support the idea11:15
oneswigjanders_: please do and if I get a response, mail it due to the tight timing.11:15
janders_I just texted the main suspect11:15
oneswigildikov: great - would you or anyone else from the Foundation be interested in attending?11:16
oneswigFrankfurt's practically your back yard :-)11:16
ildikovoneswig: do you have a link with info about ISC?11:16
oneswig#link https://www.isc-hpc.com/bof-sessions-2019.html11:16
ildikovI need to check in with the team before committing, but it's indeed an easy trip11:16
b1airolooks to me like a good opportunity to engage potential new community members, and so far as i can tell OpenStack hasn't figured on the programme yet11:16
oneswigThat's the one11:16
ildikovoneswig: I'll get back to you on it this week. Would that work?11:17
oneswigb1airo: agreed.  It's a good way to find the people on the HPC fringes of our space.11:17
oneswigildikov: yes, that would be great.11:17
oneswigb1airo: Are you going on behalf of NESI?11:17
ildikovoneswig: cool, will let you know as soon as I can11:18
b1airoi will if we run this11:18
oneswigfantastic.11:18
oneswigI'll ask DK if he's going to be there, he usually has plenty of interesting things to talk about.11:19
b1airountil someone blocks my expense account anyway...11:19
b1airoDK Panda?11:19
oneswigb1airo: I assume that's what happened last time? :-P11:19
oneswigb1airo: yes11:19
b1airohe ran a BoF last year, so seems likely he'll be proposing same again: https://2018.isc-program.com/presentation/?id=bof126&sess=sess18611:20
b1airoha, just noticed Christian Kniep was on that one too. bit of a small world this isn't it..11:21
oneswigThat's the one, I think you're right about the small world.11:21
oneswigWe should try to broaden it :-)11:22
b1airo+111:22
oneswigIf anyone else here is interested in participating, or could suggest someone to invite, please let me know11:22
oneswigI'll put together some wording based on the SC BoF proposal.11:23
oneswigAny more to add?11:23
b1airowas just about to say the same thing, actually just digging for the last SC one now...11:23
oneswigThanks b1airo11:25
oneswig#topic Update on Summit/Forum/PTG11:25
*** openstack changes topic to "Update on Summit/Forum/PTG (Meeting topic: scientific-sig)"11:25
oneswigMartial has booked us a half-day session at the PTG.  Not sure which day but towards the end of the week.11:26
oneswigI'm hoping for Thursday (I need to head home Thursday night...)11:26
oneswigWe'll apply for the usual format of meeting + BoF/lightning talks as well.11:27
*** yamamoto has joined #openstack-meeting11:28
oneswigI don't think there was anything to add on that update for now.11:28
janders_sounds good!11:29
oneswig#topic Manila + GPFS user experiences11:29
*** openstack changes topic to "Manila + GPFS user experiences (Meeting topic: scientific-sig)"11:29
oneswigSo I found somebody who has tried the Manila driver for GPFS11:29
oneswigAnd had a few minutes discussion with them about it.11:29
* b1airo grabs popcorn11:30
oneswig#link This report makes a fairly neutral reference to it https://cloud.ac.uk/reports/spectrumscale/11:30
*** markvoelker has joined #openstack-meeting11:30
oneswigThe people who wrote it are a team from Birmingham University in the UK (Simon and Radoslaw)11:30
oneswigThey did an evaluation on Manila + GPFS about 18 months ago11:31
janders_great find, thank you11:31
oneswigTheir conclusion was that the plugin doesn't add much value.  It had some limitations, in particular requiring flat networking.11:32
b1airoah yes, i now remember speaking to Simon (presumably at a Summit)11:32
verdurinYes, as I recall the verdict was not all that positive.11:32
oneswigThe model of re-exporting NFS via Ganesha is not the most efficient.  Simon referred to 3 tiers of memory buffering to tune and balance - Ganesha, GPFS, kernel buffer cache.  He thought there might be more promise in automating the management of CES (Cluster Export Services) within GPFS to achieve a similar effect.11:33
janders_I haven't used Manila in my GPFS days, so this sounds possible (and insane)11:34
janders_flat networking requirement..11:34
oneswigAlthough he was wondering if multiple instances of CES (one per tenancy) would work from a single GPFS instance11:34
janders_sigh sounds like there isn't many options for RDMA storage for OpenStack :(11:34
oneswigRadoslaw pointed out the documentation has not updated since 2017 (think we spotted that last time).  It does seem like this driver is in maintenance mode at best.  Simon mentioned he thought the team at IBM were working on other projects and not giving it attention.11:35
oneswigI guess the choice for it would be to take on refreshing the driver and adding the features desired - or do something outside of OpenStack's purview.11:36
janders_..and to add to this, I heard goss that IBM are pulling out from OpenStack/GPFS work to focus on k8s integration11:36
verdurinYes, agree with that impression from IBM.11:36
janders_given OpenStack and K8S are quite tightly coupled at times, it's an interesting statement11:37
b1airowould CES be the only path to multi-tenancy, i.e., secure sub-tree isolated exports/mounts ?11:37
oneswigb1airo: I don't know enough about GPFS to answer that but why don't I put you in touch with the horses mouth (so to speak).11:37
verdurinb1airo: there's a reason we're now looking at Lustre to complement our GPFS.11:38
oneswigI didn't think to ask if they knew of anyone else who has tried this driver.11:39
b1airofair enough verdurin . having to manage it via lnet seems a bit icky to me though11:39
*** macza has joined #openstack-meeting11:39
b1airothanks oneswig11:40
verdurinb1airo: there's no ick-free approach, sadly.11:40
janders_+1 :(11:40
oneswigno problem, a shame not to find a live user though11:40
*** janki has quit IRC11:40
*** janki has joined #openstack-meeting11:40
oneswigOK, thats all I had on it.11:40
oneswig#topic AOB11:41
*** openstack changes topic to "AOB (Meeting topic: scientific-sig)"11:41
oneswigThat Docker vulnerability.11:41
oneswig#link https://www.theregister.co.uk/2019/02/11/docker_container_flaw/11:42
*** raildo has joined #openstack-meeting11:42
oneswigIt's not quite as straightforward as writing to /proc/self/exec - there's some kind of race condition loophole that must be exploited, it seems11:43
*** macza has quit IRC11:44
oneswigOne of our team was doing a demo of Magnum on bare metal yesterday.  It was exciting enough as it was but I haven't seen if there are patched Magnum root images available yet.11:45
oneswigverdurin: what was your impression of the day yesterday?11:46
*** imsurit_ofc has quit IRC11:46
b1airoon that note, can you configure Magnum to dedicate a host to only one pod?11:46
oneswigb1airo: will ask11:47
verdurinoneswig: as Phil said, it's good to see the talks evolving to what you might call a higher-level view11:47
verdurinWas impressed with the demos in the session I chaired.11:48
oneswigme too, there were some useful things emerging.  And entirely new ways of deploying Slurm in the cloud as well :-)11:49
oneswigThere did seem to be a lot more attention from public clouds to meeting HPC requirements.11:50
verdurinYes, more depth in their approach than before.11:51
b1airowhich were those?11:51
janders_new ways of deploying Slurm... what's the best example or two?11:51
janders_always interesting to hear11:52
oneswig#link this was one - Terraform for Oracle cloud https://cluster-in-the-cloud.readthedocs.io/en/latest/11:52
janders_terraform - nice! :)11:53
oneswigThe interesting piece of this work was scheduling different job steps to different resource classes (eg, GPU, high memory).  One possible flaw was that nodes were provisioned specifically to run each job.11:54
oneswigjanders_: I wanted to ask, why the project is limited to one cloud, and whether it's possible to write portable Terraform.11:55
oneswigBe good to hear a data point on that from someone with extensive experience of trying11:55
janders_indeed! :)11:55
verdurinoneswig: yes, my impression is that running Terraform across multiple clouds isn't as straightoforward as you would hope11:56
*** e0ne has joined #openstack-meeting11:56
*** e0ne has quit IRC11:57
*** e0ne_ has quit IRC11:57
oneswigPerhaps I'll find the presenter and ask him.11:58
b1airothe job step mapping thing sounds like documentation we need on our systems11:58
*** raildo_ has joined #openstack-meeting11:58
b1airoother commercials there?11:58
oneswigGoogle and Azure, don't think I saw anyone from AWS11:59
oneswigOK we are nearly out of time, any more?11:59
oneswigtime at the bar - thanks everyone12:00
oneswig#endmeeting12:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"12:00
openstackMeeting ended Wed Feb 13 12:00:12 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_sig/2019/scientific_sig.2019-02-13-11.00.html12:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_sig/2019/scientific_sig.2019-02-13-11.00.txt12:00
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_sig/2019/scientific_sig.2019-02-13-11.00.log.html12:00
b1airocheers all12:00
*** raildo has quit IRC12:01
verdurinBye12:02
verdurinThere was an AWS person present, who had to leave early.12:03
b1airoi think i missed what the event actually was?12:03
*** sdake has joined #openstack-meeting12:03
verdurinhttps://cloud.ac.uk/workshops/feb2019/12:04
*** markvoelker has quit IRC12:04
oneswigb1airo: this was it https://cloud.ac.uk/workshops/feb2019/12:05
b1airolooks like it was a nice agenda - would've been hard to pick tracks12:07
*** e0ne has joined #openstack-meeting12:08
*** JangwonLee has quit IRC12:08
*** e0ne has quit IRC12:12
*** sdake has quit IRC12:16
*** janders_ has quit IRC12:17
*** e0ne has joined #openstack-meeting12:22
*** rmascena__ has joined #openstack-meeting12:27
*** yamamoto has quit IRC12:28
*** raildo_ has quit IRC12:30
*** yamamoto has joined #openstack-meeting12:36
*** oneswig has quit IRC12:51
*** janki has quit IRC13:00
*** markvoelker has joined #openstack-meeting13:01
*** mriedem has joined #openstack-meeting13:08
*** jrbalderrama has joined #openstack-meeting13:10
*** e0ne has quit IRC13:11
*** jamesmcarthur has joined #openstack-meeting13:14
*** rbudden has joined #openstack-meeting13:16
*** e0ne has joined #openstack-meeting13:17
*** e0ne_ has joined #openstack-meeting13:20
*** e0ne has quit IRC13:23
*** enriquetaso has joined #openstack-meeting13:24
*** janki has joined #openstack-meeting13:28
*** jamesmcarthur has quit IRC13:29
*** markvoelker has quit IRC13:34
*** vishakha has quit IRC13:35
*** eharney has quit IRC13:37
*** e0ne_ has quit IRC13:40
*** lbragstad has joined #openstack-meeting13:41
*** e0ne has joined #openstack-meeting13:45
*** mjturek has joined #openstack-meeting13:46
*** jamesmcarthur has joined #openstack-meeting13:50
*** e0ne_ has joined #openstack-meeting13:50
*** e0ne has quit IRC13:51
*** mjturek has quit IRC13:51
*** mjturek has joined #openstack-meeting13:54
*** mjturek has quit IRC13:59
*** mjturek has joined #openstack-meeting14:00
*** hyunsikyang has quit IRC14:01
*** mjturek has quit IRC14:01
*** mjturek has joined #openstack-meeting14:02
*** e0ne_ has quit IRC14:04
*** sdake has joined #openstack-meeting14:07
*** mpiwowarczy has joined #openstack-meeting14:08
*** sdake has quit IRC14:09
*** sdake has joined #openstack-meeting14:10
*** sdake has quit IRC14:13
*** sdake has joined #openstack-meeting14:14
*** rfolco has quit IRC14:18
*** b1airo has quit IRC14:18
*** eharney has joined #openstack-meeting14:22
*** sdake has quit IRC14:23
*** jamesmcarthur has quit IRC14:26
*** e0ne has joined #openstack-meeting14:29
*** markvoelker has joined #openstack-meeting14:31
*** awaugama has joined #openstack-meeting14:35
*** e0ne_ has joined #openstack-meeting14:35
*** e0ne has quit IRC14:35
*** rfolco has joined #openstack-meeting14:37
*** lpetrut has joined #openstack-meeting14:38
*** e0ne_ has quit IRC14:41
*** yamamoto has quit IRC14:44
*** yamamoto has joined #openstack-meeting14:49
*** yamamoto has quit IRC14:49
*** yamamoto has joined #openstack-meeting14:50
*** yamamoto has quit IRC14:50
*** e0ne has joined #openstack-meeting14:50
*** sridharg has quit IRC14:54
*** e0ne_ has joined #openstack-meeting14:55
*** liuyulong has joined #openstack-meeting14:55
*** jamesmcarthur has joined #openstack-meeting14:55
*** e0ne has quit IRC14:55
*** yamamoto has joined #openstack-meeting15:00
*** yamamoto has quit IRC15:00
*** verdurin has quit IRC15:02
*** markvoelker has quit IRC15:04
*** verdurin has joined #openstack-meeting15:05
*** janki has quit IRC15:21
*** _alastor_ has joined #openstack-meeting15:22
*** cloudrancher has joined #openstack-meeting15:22
*** _alastor_ has quit IRC15:26
*** rossella_s has quit IRC15:26
*** ralonsoh has joined #openstack-meeting15:27
*** armax has joined #openstack-meeting15:35
*** ganso has joined #openstack-meeting15:39
*** lseki has joined #openstack-meeting15:39
*** Adri2000 has quit IRC15:48
*** Adri2000 has joined #openstack-meeting15:51
*** carlos_silva has joined #openstack-meeting15:53
*** ociuhandu has quit IRC15:55
*** Luzi has quit IRC15:55
*** ociuhandu has joined #openstack-meeting15:55
*** rosmaita has joined #openstack-meeting15:56
*** lpetrut has quit IRC16:00
jungleboyj#startmeeting Cinder16:00
openstackMeeting started Wed Feb 13 16:00:39 2019 UTC and is due to finish in 60 minutes.  The chair is jungleboyj. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
whoami-rajatHi16:00
yikunhello16:00
jungleboyjcourtesty ping jungleboyj diablo_rojo, diablo_rojo_phon, rajinir tbarron xyang xyang1 e0ne gouthamr thingee erlon tpsilva ganso patrickeast tommylikehu eharney geguileo smcginnis lhx_ lhx__ aspiers jgriffith moshele hwalsh felipemonteiro lpetrut lseki _alastor_ whoami-rajat yikun rosmaita enriquetaso hemna _hemna16:00
rosmaitao/16:01
eharneyhi16:01
rajiniro/16:01
*** markvoelker has joined #openstack-meeting16:01
enriquetasoo/16:01
smcginniso/16:01
xyanghi16:01
gansohi16:02
erlonhola!16:02
jungleboyj@!16:02
carlos_silvahi16:02
_pewp_jungleboyj ï¼¼( ï½¥_ï½¥)16:02
lsekihello16:02
e0ne_hi16:03
jungleboyjNice.  Have a good number of people showing up.16:03
jungleboyjOk.  Lets get started then.16:03
jungleboyj#topic announcements16:04
*** openstack changes topic to "announcements (Meeting topic: Cinder)"16:04
jungleboyjWe had a great mid-cycle last week.16:04
jungleboyjIt was a small team on site and had some good remote participation.16:05
jungleboyjThank you to all who participated.16:05
jungleboyj#link https://etherpad.openstack.org/p/cinder-stein-mid-cycle-planning16:05
jungleboyjNotes from the event are available above.16:05
*** sdake has joined #openstack-meeting16:05
jungleboyjI will work on doing the usual summary out in our Wiki for future reference.16:05
*** cloudrancher has quit IRC16:06
*** cloudrancher has joined #openstack-meeting16:06
jungleboyjIf you are a vendor, please take some time to look through the notes as there were topics that will impact all of you in there.16:06
*** cloudrancher has quit IRC16:06
jungleboyjAnd from the past to the future.16:07
jungleboyjOur participation at Denver PTG has been confirmed.16:08
*** ianychoi has quit IRC16:08
enriquetaso\o/16:08
jungleboyjI hope that we will have a good group there again.16:08
jungleboyjHow many are hoping to be there?16:08
smcginnisI'll be there.16:08
*** davidsha has joined #openstack-meeting16:09
jungleboyj:-)16:09
rosmaitame too16:09
e0ne_I hope, I'll be there16:09
jungleboyjrosmaita: Awesome.16:09
enriquetasoI'll be there too16:09
jungleboyje0ne_:  Good.  That will be good.  Appreciate all your efforts to make the mid-cycle remotely.16:09
jungleboyjenriquetaso:  Awesome.  Will be good to meet you.16:09
*** mjturek has quit IRC16:10
e0ne_jungleboyj: thanks for organizing it!16:10
jungleboyje0ne_:  Welcome.  I am glad it went smoother than the last one I organized.  ;-)16:10
smcginnishah16:10
jungleboyjThough smcginnis initially scared me trying to get on the wifi.  Thankfully it was PEBKAC16:11
*** macza has joined #openstack-meeting16:11
smcginnisOr poor user interface design. :P16:11
jungleboyjAnyway, hope to see many of you in Denver.  Please try to plan for it.16:11
jungleboyjsmcginnis:  It made sense to me.  ;-)16:11
jungleboyjOk, that was all I had for announcements.16:12
jungleboyj#topic Change in multi-attach test enablement may cause 3rd Party CIs to fail16:12
*** openstack changes topic to "Change in multi-attach test enablement may cause 3rd Party CIs to fail (Meeting topic: Cinder)"16:12
jungleboyj#link http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002536.html16:12
jungleboyjmriedem: Sent this out to the mailing list and mentioned it on our IRC channel.  Just wanted to make one last note of it.16:13
*** mjturek has joined #openstack-meeting16:13
jungleboyjIf you own a CI, please make sure that it is not failing due to the changes in the multi-attach tests.16:13
jungleboyjI haven't had a chance to go through and audit who all is hit by this.  Will be trying to do that soon though.16:13
*** woojay has joined #openstack-meeting16:14
jungleboyjSo, please take time to make sure you are not impacted.16:14
jungleboyjAlso, a general note that we are going to be going through and taking a look at CIs and how they are running in the last part of Stein here.  So, be aware.  :-)16:15
jungleboyj#topic Planning for Train Mid-Cycle16:15
*** openstack changes topic to "Planning for Train Mid-Cycle (Meeting topic: Cinder)"16:15
jungleboyj#link https://etherpad.openstack.org/p/cinder-train-mid-cycle-planning16:15
jungleboyjSo, we decided at the mid-cycle to just start planning the next one.  It was productive as the previous ones had been.16:16
smcginnisFor those that were not able to participate in this last one - I found it very productive and we were able to make a lot of decisions and work through things.16:16
*** _alastor_ has joined #openstack-meeting16:16
jungleboyjWe are hoping that if we start planning early people will be more likely to be able to attend.16:16
smcginnisHopefully this is enough time to make an argument to your management to be able to be a part of the next one.16:16
smcginnisThe more people we have involved, the better.16:16
jungleboyjsmcginnis:  ++16:16
jungleboyjWe have proposed a number of dates in the etherpad.  If you are available for the dates and would like to come, please indicate your availability.16:17
*** walshh_ has joined #openstack-meeting16:17
jungleboyjYou don't have to have approval, just want to try to schedule it when the most people are likely to be available.16:17
jungleboyjLenovo is willing to host again as it worked quite well, but if others are interested in hosting, that is ok as well.16:18
jungleboyjDon't need all the details now but would like to do some initial planning.16:18
* e0ne_ wants mid-cycle/ptg in Europe16:20
jungleboyje0ne_:  Want to host?  :-)16:20
e0ne_:)16:20
jungleboyjWe also talked about when in the week it was scheduled.  It sounds like some people would prefer to have it at the beginning or end of the week, rather than the middle.16:20
jungleboyjWe are open to changing things there.16:21
jungleboyje0ne_ did us being on the east coast of the USA time wize at least make things a little better?16:22
e0ne_jungleboyj: absolutely16:22
jungleboyjOk.  Good.16:22
jungleboyjsmcginnis: or rosmaita Anything to add there?16:22
smcginnisNope16:23
e0ne_jungleboyj: I'm going read mid-cycle this week, maybe I'll add few comments16:23
jungleboyje0ne_:  Great.  Thank you!16:24
jungleboyjOk.  So, that was all I had on the agenda for today.16:25
jungleboyj#topic Open Discussion16:25
*** openstack changes topic to "Open Discussion (Meeting topic: Cinder)"16:25
rosmaitajust thanks to Lenovo for great hosting16:25
jungleboyjrosmaita:  Welcome.  I am really glad it worked so well.16:25
smcginnisYes, thanks!16:25
smcginnisjungleboyj: Hope you got some good work time out there too.16:26
jungleboyjwhoami-rajat:  How was the remote connection?16:26
jungleboyjWere you able to follow pretty well?16:26
whoami-rajatjungleboyj: Yes. it was great. Thanks for hosting.16:26
jungleboyjGood.  I feel like we are getting better at the remote hosting.16:26
smcginnisThanks everyone that attended remotely. I know sometimes that can be difficult.16:26
enriquetaso+116:26
jungleboyjThough next time it would be good to try Zoom or something.16:26
jungleboyjI was thankful we had that PolyCom phone.  I think that worked well.16:27
jungleboyjenriquetaso: You were able to follow too?16:27
e0ne_sound quality was good this time16:27
whoami-rajatjungleboyj: the sound was better than the last PTG.16:27
jungleboyjOk.  Cool.16:27
enriquetasojungleboyj, yup16:27
jungleboyjThat is great.16:28
jungleboyjRoom was better and we had a PolyCom that works as just a speaker/mic.16:28
jungleboyjAnyway, anything else that people want to discuss today?16:29
whoami-rajatif i'm not interrupting the open discussion, i would appreciate feedback on this patch https://review.openstack.org/#/c/627359/ .16:29
jungleboyjwhoami-rajat:  That is what OpenDiscussion is for.  :-)16:29
whoami-rajatjungleboyj: Thanks :)16:30
jungleboyjwhoami-rajat:  I think eharney needs to see your response there.16:30
eharneyyeah we were just chatting on #openstack-cinder16:30
*** yamamoto has joined #openstack-meeting16:30
whoami-rajatjungleboyj: we had a continuation on the channel.16:31
eharneyit seems this may be exposing a bug around how we handle shell parameters already16:31
jungleboyjOk.16:31
eharneyi'm not convinced it's reasonable to have the client throw away arguments like "--all-tenants 0" when they are explicitly requested by the user16:31
eharneywhich is what this patch hinges on, but also what we apparently already do16:31
smcginnis--all-tenants 0 means not all tenants, right?16:32
eharneyyes, but if you request --all-tenants 0 as non-admin, the server rejects the request16:32
smcginnisIsn't that the default? So wouldn't it be safe to ignore that?16:32
eharneythe server should be the one ignoring it -- if we code the client to make that decision, and then do something later in the server like add a policy flag to control this behavior... the client will no longer do the right thing16:33
whoami-rajateharney: also the rejection isn't handled properly (against admin non-admin)16:33
eharneyor, nobody can ignore it and we can just fail when the caller isn't admin, which is also reasonable16:34
eharneythe messy part comes in with the current patch where the client decides "this arg probably isn't allowed by the server so i'll just throw it away even though the user requested it"16:34
*** markvoelker has quit IRC16:34
whoami-rajatit's not only in regard of all-tenant but all boolean parameters that are passed as 0 are rejected. https://github.com/openstack/python-cinderclient/blob/master/cinderclient/base.py#L143-L14516:35
jungleboyjHmmm, that seems bad.16:36
smcginnisI would think as long as it passes when the argument is 1, then that should cover policy changes. But if 0 is the default and passing 0 sometimes would cause errors, then it's probably safer to drop it.16:36
eharneythe fix for the immediate bug here should just be to not pass all-tenants by default16:37
*** diablo_rojo has joined #openstack-meeting16:37
eharneyalso, why does this problem appear for non-admin on group-list and not other list calls?16:38
*** yamamoto has quit IRC16:38
whoami-rajateharney: because the reject_invalid_filters function is only added in groups group_snapshots and messages.16:39
eharneyhmm16:40
eharneyso volume list thinks all_tenants=0 is valid for non-admins and group-list doesn't16:40
whoami-rajathttps://github.com/openstack/cinder/blob/master/cinder/api/v3/groups.py#L160-L16116:41
whoami-rajateharney: looking at the code seems to have this behaviour.16:41
eharneyit kind of sounds like we should establish a consistent policy around this on the server before worrying about fixing client usability issues around it16:42
smcginnisYeah, looks like we can improve things on the server side.16:42
smcginnisWe can probably continue this outside the meeting.16:42
jungleboyjSounds good.16:43
jungleboyjAny other discussion required today?16:44
whoami-rajateharney:  IMO atleast we can have this fixed on the client side as other resources as bugs are being reported for the same.16:44
jungleboyjSo, doesn't appear that we have other topics for today.16:45
jungleboyjShould we wrap up the meeting and whoami-rajat and eharney can take this to the Cinder channel/16:46
*** sdake has quit IRC16:46
rosmaitajungleboyj: need you to look at https://review.openstack.org/#/c/636425/ to approve cinderclient release 3.1.116:46
whoami-rajatjungleboyj: sure16:46
*** sdake has joined #openstack-meeting16:46
jungleboyjrosmaita:  Thanks for updating that.  Looks good.16:47
rosmaitanp16:47
jungleboyjOk.  I think we are good for today then.16:47
jungleboyjThanks everyone for attending.16:47
*** e0ne has joined #openstack-meeting16:47
smcginnisThanks!16:47
jungleboyj#endmeeting16:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:47
openstackMeeting ended Wed Feb 13 16:47:56 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-02-13-16.00.html16:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-02-13-16.00.txt16:48
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-02-13-16.00.log.html16:48
*** rosmaita has left #openstack-meeting16:48
*** e0ne_ has quit IRC16:48
*** jamesmcarthur has quit IRC16:51
*** gyee has joined #openstack-meeting16:55
*** sdake has quit IRC16:58
*** aagate has joined #openstack-meeting16:59
*** jamesmcarthur has joined #openstack-meeting17:00
*** davidsha has quit IRC17:02
*** ekcs has joined #openstack-meeting17:04
*** rmascena__ has quit IRC17:04
*** rmascena__ has joined #openstack-meeting17:05
*** tssurya has quit IRC17:06
*** lseki has left #openstack-meeting17:09
*** ociuhandu_ has joined #openstack-meeting17:11
*** eumel8 has joined #openstack-meeting17:13
*** psachin has quit IRC17:18
*** ekcs has quit IRC17:19
*** mjturek has quit IRC17:20
*** jamesmcarthur has quit IRC17:22
*** e0ne has quit IRC17:25
*** kopecmartin is now known as kopecmartin|off17:26
*** markvoelker has joined #openstack-meeting17:32
*** jamesmcarthur has joined #openstack-meeting17:34
*** geguileo has joined #openstack-meeting17:34
*** ociuhand_ has joined #openstack-meeting17:39
*** ociuhandu has quit IRC17:42
*** mjturek has joined #openstack-meeting17:46
*** ociuhand_ has quit IRC17:48
*** markvoelker has quit IRC18:04
*** erlon has quit IRC18:05
*** hongbin has joined #openstack-meeting18:15
*** cloudrancher has joined #openstack-meeting18:16
*** erlon has joined #openstack-meeting18:18
*** sdake has joined #openstack-meeting18:19
*** e0ne has joined #openstack-meeting18:22
*** ijw has joined #openstack-meeting18:23
*** erlon_ has joined #openstack-meeting18:25
*** hongbin has quit IRC18:27
*** hongbin has joined #openstack-meeting18:27
*** erlon has quit IRC18:28
*** ociuhandu has joined #openstack-meeting18:29
*** yamamoto has joined #openstack-meeting18:31
*** verdurin has quit IRC18:31
*** mjturek has quit IRC18:32
*** ociuhandu has quit IRC18:33
*** aojea has quit IRC18:35
*** sdake has quit IRC18:37
*** sunnaichuan has quit IRC18:38
*** verdurin has joined #openstack-meeting18:39
*** ijw has quit IRC18:46
*** mkarray has joined #openstack-meeting18:48
*** tssurya has joined #openstack-meeting18:49
*** mriedem is now known as mriedem_away18:52
*** markvoelker has joined #openstack-meeting19:01
fungiper discussion in #storyboard we're skipping the regular meeting this week, but find us in there if you have anything you want to discuss!19:10
*** raildo has joined #openstack-meeting19:12
*** rmascena__ has quit IRC19:13
*** ociuhandu has joined #openstack-meeting19:16
*** ijw has joined #openstack-meeting19:26
*** ijw has quit IRC19:28
*** ociuhandu has quit IRC19:28
*** eharney has quit IRC19:31
*** erlon_ has quit IRC19:34
*** markvoelker has quit IRC19:34
*** irclogbot_1 has quit IRC19:47
*** e0ne has quit IRC19:47
*** jamesmcarthur has quit IRC19:55
*** ijw has joined #openstack-meeting19:57
*** irclogbot_1 has joined #openstack-meeting20:01
*** ijw has quit IRC20:01
*** bbowen_ has quit IRC20:06
*** bbowen_ has joined #openstack-meeting20:06
*** jamesmcarthur has joined #openstack-meeting20:07
*** jamesmcarthur has quit IRC20:12
*** jamesmcarthur has joined #openstack-meeting20:16
*** ralonsoh has quit IRC20:18
*** carlos_silva has quit IRC20:22
*** eharney has joined #openstack-meeting20:25
*** ociuhandu has joined #openstack-meeting20:31
*** markvoelker has joined #openstack-meeting20:31
*** jamesmcarthur has quit IRC20:35
*** hongbin has quit IRC20:40
*** hongbin has joined #openstack-meeting20:49
*** hongbin has quit IRC20:54
*** patchbot has joined #openstack-meeting20:59
*** timburke has joined #openstack-meeting20:59
*** zaitcev has joined #openstack-meeting21:00
notmyname#startmeeting swift21:00
openstackMeeting started Wed Feb 13 21:00:26 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
notmynamewho's here for the swift team meeting?21:00
claygo/21:00
timburkeo/21:00
tdasilvahi21:00
kota_o/21:00
mattoliverauo/21:00
rledisezo/21:00
patchboto/21:00
kota_lol21:01
notmynameall right, let's get started21:01
notmynameupdates from last week...21:01
notmynamelosf branch has been created. I saw some patches proposed to it21:01
mattoliveraunice21:02
notmynameI've proposed stable backport changelog updates. I would have landed them, but timburke reminded me to reno-ify them. so I reproprosed with that today. assuming the gate is happy with it, i'll land them in a few hours and put in the tag requests21:02
zaitcevAnd the Go is baaaack.21:02
notmynamelol21:02
notmynamealso, I want to collect all the backport changelog updates (from ever) and aggregate them and propose them to master. TBH I don't know yet what structure they'll take (eg at the top or inline), but it makes sense to me to have all the changelog updates on master21:03
notmynameany other updates from last week?21:03
notmynametimburke: you were just looking at some libec/pyeclib stuff21:04
notmynamecan you give an update?21:04
*** ociuhandu has quit IRC21:04
*** mriedem_away is now known as mriedem21:04
timburkeyup... i was trying to do some weird things, installing libec just for my user instead of the whole system, so i proposed https://review.openstack.org/#/c/636501/21:05
patchbotpatch 636501 - pyeclib - Try harder to find liberasurecode - 6 patch sets21:05
timburkewhich led me to realize that pyeclib gate was broken21:05
*** markvoelker has quit IRC21:05
timburkebut tdasilva already landed https://review.openstack.org/#/c/636668/ so we're good!21:05
patchbotpatch 636668 - pyeclib - Fix gate (MERGED) - 3 patch sets21:05
claygyay!21:06
*** hongbin has joined #openstack-meeting21:06
claygwtg timburke & tdasilva  - libec masters!21:06
timburkei was hoping that my LD_LIBRARY_PATH change would address https://bugs.launchpad.net/pyeclib/+bug/1780320 as a drive-by21:06
openstackLaunchpad bug 1780320 in PyECLib "If find_library('erasurecode') in setup.py does not return a library version, try to append it " [Undecided,New]21:06
*** raildo has quit IRC21:06
timburkebut it didn't. so now i kinda want to bump up our minimum-supported libec to 1.4.0 (released back in ocata, i think?) and do https://review.openstack.org/#/c/636748/21:07
patchbotpatch 636748 - pyeclib - Use liberasurecode_get_version() - 1 patch set21:07
notmynameI think it's totally reasonable to bump the min version supported21:07
notmynameanyone else have strong feelings on that?21:08
timburkeit would mean you can't use xenial system packages for libec though21:08
kota_that means we throw the binary supports in xenial?21:08
mattoliverau+1 and theres a bug we can use as a reason21:08
notmynametimburke: yeah, that's an issue. why does it break?21:09
* mattoliverau +1 was to raise the minimum. /me doesnt use ubuntu anymore :P21:09
timburkei think i might be able to make it work without it... the more i think about it, some combination of my patch and https://review.openstack.org/#/c/580754/ seems reasonable -- we don't have a libec2 yet, so...21:09
patchbotpatch 580754 - pyeclib - Adds support for systems that report library witho... - 1 patch set21:09
timburkenotmyname: xenial ships 1.1.021:09
timburkesee https://packages.ubuntu.com/xenial/liberasurecode121:09
notmynamethat's demonstrably terrible.21:09
timburkebionic's better: https://packages.ubuntu.com/bionic/liberasurecode121:10
notmynamemaybe we should figure out how to get xenial to update to a newer version21:10
* kota_ knows it's terrible tho21:10
notmynameI sortof doubt the version of swift in xenial supports <1.3.121:10
clayg well, hopefully if xenial uprevs their pyeclib they uprev their libec to a supported version21:10
timburkenotmyname: almost certainly a good idea -- 1.3.1 would be the bare minimum of what they should even think about shipping21:11
zaitcevIf you're going to tag 1.7, don't forget https://review.openstack.org/63655621:11
patchbotpatch 636556 - liberasurecode - Make our alt crc32 more portable - 1 patch set21:11
claygand if you install the latest pyeclib on your xenial maybe you can figure out how to build a new enough libec21:11
clayglike ... use packages or don't21:11
claygoh yeah that crc thing was a mess21:11
claygis?21:12
notmynameok, so to sum up it sounds like we want to raise the supported version, but we should probably check with whoever maintains that ubuntu package to see how to get it updated too21:12
timburkeoh yeah, and while we're talking libec, vr42 pushed up p 635603 p 635604 and p 635605 !21:12
patchbothttps://review.openstack.org/#/c/635603/ - liberasurecode - fix: data access when having non-zero metadata size - 1 patch set21:12
patchbothttps://review.openstack.org/#/c/635604/ - liberasurecode - fix: proper support of more than 32 fragments - 1 patch set21:12
patchbothttps://review.openstack.org/#/c/635605/ - liberasurecode - feature: quadiron backend and tests - 1 patch set21:12
notmynamenice21:12
notmynamethat's really good to hear21:12
*** browny has quit IRC21:13
kota_oh, that's new thing proposed at the last meeting21:13
notmynametimburke: between you and me, let's work on getting libec/pyeclib patches updated on the priority reviews page21:13
timburkezaitcev: i'mmm....gonna have to think about that....21:13
notmynamesounds like there's a bit of work to do that is bigger than a short conversation here plus 30 minutes in gerrit21:14
timburkei really really wanna just cordon off that busted alt-crc and never have to think about it again21:14
timburkeit was horribly broken and i worry that any attempt to make it not-horribly-broken is missing the point of why we kept it around21:15
claygi'm not sure id' seen that phrase before... "cordon off" - sounds like quarantine or sequester...21:15
zaitcevNo, you don't get it. On s390 it was NOT horribly broken. This patch DOES make it horribly broken, so that our tests pass.21:16
timburkeyeah, maybe "quarantine" would be better. w/e21:16
notmynametimburke: sound good to you? ie you and I track it on the wiki and that way we can track it a little better without it slipping through the cracks?21:16
timburkelol21:16
notmynameanything else to bring up from anyone? any updates from last week or other stuff going on?21:17
*** aagate has quit IRC21:17
notmynamerledisez: kota_: anythign to bring up about losf?21:19
kota_I started work on losf feature branch, just pushed alex's github version.21:20
rlediseznotmyname: not from my side. alecuyer is off this week and i'll be off next week, so not a lot of movements these days21:20
notmynameeveryone, please remember to register for the PTG in denver asap21:21
zaitcevI did21:21
kota_but it seems like, we need to fix some tests and it's the thing alex worried about, that would be affected by design.21:21
notmynameyou should have an email with a discount code in it21:21
zaitcevBTW, can you guys review py3 stuff21:21
zaitcevThere's like no time left21:21
notmynamezaitcev: thanks for bringing that up21:21
kota_so that I should take a review on design docs too to fix up.21:21
notmynamezaitcev: what is your timeframe. the only one I've heard is the openstack one of "end of T"21:21
claygdiscount code?21:21
zaitcevhttps://review.openstack.org/570320 this is most annoying21:22
patchbotpatch 570320 - swift - py3: port the container sharder - 14 patch sets21:22
kota_oh yeah, i should register ptg, just got internal approval yesteday.21:22
notmynamemattoliverau: were you going to look into that sharder py3 patch?21:22
notmynamezaitcev: what do you mean "there's no time left"?21:22
* mattoliverau still hasn't got a approval to go yet21:22
zaitcevIt started like "oh, I'm just gonna fix up some sharder CLI real quick", and it turned out that container everything depends on this, and in addition it touches py221:22
mattoliveraunotmyname: that was the plan21:22
claygoh indeed, i have a discount21:23
claygGTK21:23
mattoliverausorry I've been at sleep school with the baby (friday - Tuesday). I had my laptop but not really very productive (work wise). so now playing catch up21:23
zaitcevnotmyname: we have 39% of tests passing right now and we've been on it since November if not earlier. Even if we ship in late April, there's NO WAY to get there in time.21:23
mattoliveraubabies are aawesome :P21:23
zaitcevNovember, December, January - that's 3 months. February, March, April - seriously we're underperforming. And don't forget that once unit tests are done, we have to do some kind of function and migration tests.21:24
notmynamezaitcev: ok, but what's the april date? the only official date I've heard from anyone is "end of T" which will be towards the end of this calendar year21:24
zaitcevOh21:25
zaitcevRH OSP 14 is based on Stein21:25
*** jamesmcarthur has joined #openstack-meeting21:25
notmynameI'm sure distros have some date in mind, but I just don't think it's ever been shared outside their respective companies21:25
zaitcevThe Stein is the release that comes on top of RHEL 8 for us21:27
notmynameok21:28
zaitcevMy problem is, RHEL 8 does not have py2 in the core, therefore other core products like OpenStack cannot depend on it (else they pull in the extra distro with py2).21:28
claygRHEL 8 - best RHEL EVAR - IBMEL even21:28
zaitcevIf we bump Swift out, whole OpenStack comes crashing down because our Heat-based director uses it :-)21:28
kota_lol21:28
notmynamesounds like some explicit tracking of the py3 work would be warranted. I'll add that to priority reviews too. (but after I do, please update or clarify anything I miss or get wrong)21:29
claygwhy is everything so hard... sigh21:29
*** jamesmcarthur has quit IRC21:30
notmynamezaitcev: I think the work you've done for py3 in swift is both admirable and impressive21:30
*** ijw has joined #openstack-meeting21:30
notmynamemy gut reaction is one of frustration at distros in general though. everyone is wanting a thing, yet zaitcev is the *only* one who's been asked to work on it. but, you know, "open source" so I'm sure it will get done...21:31
zaitcevCyril was helping, but he has work in Glance21:31
zaitcevChristian has gone manager21:31
*** whoami-rajat has quit IRC21:32
* clayg pours one out21:32
notmynameyeah. I'm not blaming anyone or second-guessing work that's been done. just venting about it.21:32
notmynameanyway, we'll keep working, as a team. we'll bug our respective managers to prioritize py3 work (that's the real issue, TBH). and it'll be done when it's done. hopefully sooner than later21:33
claygzaitcev is great - I'm kinda almost a little bit sort of kinda starting to think maybe it would be less annoying if swift supported py321:33
notmynameclayg: whoa... hold on. such strong feelings there ;-)21:33
notmynamebuuut... we won't get anything done about it by complaining in here21:34
notmynameanything else that someone would like to bring up here in this meeting?21:34
clayghow long after we support py3 can we drop py2 support?21:34
clayglike... immediately?21:34
*** awaugama has quit IRC21:35
notmynameclayg: likely very very soon, seeing as the py community deadline is soon too21:35
timburkewell, we aren't going to be able to drop py2 *before* we support py3, so...21:35
claygas long as `swift-init restart` works right?21:35
claygtimburke: stick hasn't worked - so maybe the carrot?21:35
timburkeidk, i just keep seeing bigger and bigger sticks :-/21:36
claygROFL21:36
* clayg hugs timburke 21:36
notmynameI think we've covered everything this week21:37
notmynamethanks for coming, and thank you for your work on Swift21:37
notmyname#endmeeting21:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:37
openstackMeeting ended Wed Feb 13 21:37:32 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-02-13-21.00.html21:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-02-13-21.00.txt21:37
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2019/swift.2019-02-13-21.00.log.html21:37
*** patchbot has left #openstack-meeting21:37
*** zaitcev has left #openstack-meeting21:40
*** ganso has left #openstack-meeting21:40
*** enriquetaso has quit IRC21:49
*** ijw has quit IRC21:51
*** markvoelker has joined #openstack-meeting22:02
*** tssurya has quit IRC22:07
*** ijw has joined #openstack-meeting22:16
*** markvoelker has quit IRC22:34
*** gouthamr has quit IRC22:35
*** gouthamr has joined #openstack-meeting22:36
*** cburgess has quit IRC22:36
*** ijw has quit IRC22:37
*** ijw has joined #openstack-meeting22:38
*** cburgess has joined #openstack-meeting22:38
*** ijw has quit IRC22:42
*** jamesmcarthur has joined #openstack-meeting22:43
*** jamesmcarthur has quit IRC22:48
*** jamesmcarthur has joined #openstack-meeting22:51
*** mkarray has quit IRC22:52
*** david-lyle has quit IRC23:02
*** dklyle has joined #openstack-meeting23:02
*** jamesmcarthur has quit IRC23:07
*** slaweq has quit IRC23:11
*** mattw4 has joined #openstack-meeting23:27
*** slaweq has joined #openstack-meeting23:27
*** jamesmcarthur has joined #openstack-meeting23:27
*** mattw4 has quit IRC23:28
*** mattw4 has joined #openstack-meeting23:28
*** slaweq has quit IRC23:31
*** markvoelker has joined #openstack-meeting23:31
*** jamesmcarthur has quit IRC23:33
*** jamesmcarthur has joined #openstack-meeting23:49
*** lbragstad has quit IRC23:52
*** jamesmcarthur has quit IRC23:53
*** jamesmcarthur has joined #openstack-meeting23:56

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