Thursday, 2018-10-04

*** tpsilva has quit IRC00:00
*** jcoufal has quit IRC00:03
*** jcoufal has joined #openstack-meeting-alt00:14
*** dtrainor has joined #openstack-meeting-alt00:22
*** jcoufal has quit IRC00:24
*** diablo_rojo has quit IRC00:26
*** dave-mccowan has quit IRC00:52
*** gyee has quit IRC00:54
*** jtomasek has joined #openstack-meeting-alt01:03
*** tetsuro has joined #openstack-meeting-alt01:05
*** jtomasek has quit IRC01:07
*** dtrainor has quit IRC01:18
*** iyamahat__ has joined #openstack-meeting-alt01:32
*** yamahata has quit IRC01:35
*** iyamahat_ has quit IRC01:35
*** ijw has quit IRC01:37
*** iyamahat__ has quit IRC01:38
*** iyamahat has joined #openstack-meeting-alt01:39
*** tetsuro has quit IRC01:41
*** tetsuro has joined #openstack-meeting-alt01:41
*** iyamahat has quit IRC01:44
*** tetsuro has quit IRC01:51
*** tetsuro has joined #openstack-meeting-alt01:55
*** hongbin has joined #openstack-meeting-alt01:55
*** iyamahat has joined #openstack-meeting-alt02:00
*** tetsuro has quit IRC02:01
*** jtomasek has joined #openstack-meeting-alt02:02
*** tetsuro has joined #openstack-meeting-alt02:03
*** jtomasek has quit IRC02:07
*** yamamoto has quit IRC02:47
*** yamamoto has joined #openstack-meeting-alt02:47
*** bhavikdbavishi has joined #openstack-meeting-alt03:00
*** bhavikdbavishi1 has joined #openstack-meeting-alt03:00
*** ircuser-1 has quit IRC03:01
*** bhavikdbavishi has quit IRC03:04
*** bhavikdbavishi1 is now known as bhavikdbavishi03:04
*** ircuser-1 has joined #openstack-meeting-alt03:06
*** hongbin has quit IRC03:27
*** adam_g has joined #openstack-meeting-alt04:06
*** tetsuro has quit IRC04:06
*** ianychoi_ has joined #openstack-meeting-alt04:15
*** ianychoi has quit IRC04:17
*** slaweq has joined #openstack-meeting-alt05:11
*** tetsuro has joined #openstack-meeting-alt05:14
*** slaweq has quit IRC05:16
*** sridharg has joined #openstack-meeting-alt05:18
*** ijw has joined #openstack-meeting-alt05:25
*** ijw is now known as ijw_05:25
*** ijw_ is now known as ijw05:26
*** jtomasek has joined #openstack-meeting-alt06:05
*** iyamahat has quit IRC06:35
*** rcernin has quit IRC06:38
*** rcernin has joined #openstack-meeting-alt06:38
*** dpawlik has joined #openstack-meeting-alt06:46
*** slaweq has joined #openstack-meeting-alt06:57
*** ttsiouts has joined #openstack-meeting-alt06:59
*** rcernin has quit IRC07:10
*** ttsiouts has quit IRC07:16
*** bhavikdbavishi has quit IRC07:46
*** iyamahat has joined #openstack-meeting-alt07:53
*** rdopiera has joined #openstack-meeting-alt08:00
*** ttsiouts has joined #openstack-meeting-alt08:00
*** tssurya has joined #openstack-meeting-alt08:03
*** derekh has joined #openstack-meeting-alt08:13
*** bhavikdbavishi has joined #openstack-meeting-alt08:25
*** e0ne has joined #openstack-meeting-alt08:42
*** bhavikdbavishi has quit IRC08:44
*** panda|off is now known as panda08:44
*** ttsiouts has quit IRC08:49
*** ttsiouts has joined #openstack-meeting-alt08:59
*** iyamahat has quit IRC09:02
*** ttsiouts has quit IRC09:04
*** ttsiouts has joined #openstack-meeting-alt09:08
*** yamamoto has quit IRC09:22
*** yamamoto has joined #openstack-meeting-alt09:22
*** jesusaur has joined #openstack-meeting-alt09:30
*** priteau has joined #openstack-meeting-alt09:49
*** alexchadin has joined #openstack-meeting-alt09:53
*** alexchadin has quit IRC10:02
*** alexchadin has joined #openstack-meeting-alt10:05
*** alexchadin has quit IRC10:19
*** ttsiouts has quit IRC10:21
*** ttsiouts has joined #openstack-meeting-alt10:31
*** slaweq_ has joined #openstack-meeting-alt10:38
*** kopecmartin|ruck is now known as kopecmartin|scho10:38
*** alexchadin has joined #openstack-meeting-alt10:39
*** slaweq has quit IRC10:40
*** erlon has joined #openstack-meeting-alt10:49
*** yamamoto has quit IRC10:49
*** yamamoto has joined #openstack-meeting-alt10:49
*** yamamoto has quit IRC10:54
*** ganso has joined #openstack-meeting-alt10:54
*** slaweq__ has joined #openstack-meeting-alt10:56
*** slaweq_ has quit IRC10:57
*** dave-mccowan has joined #openstack-meeting-alt11:01
*** janki has joined #openstack-meeting-alt11:06
*** alexchadin has quit IRC11:24
*** ttsiouts has quit IRC11:32
*** yamamoto has joined #openstack-meeting-alt11:38
*** raildo has joined #openstack-meeting-alt11:41
*** tpsilva has joined #openstack-meeting-alt11:44
*** slagle has quit IRC11:51
*** tetsuro has quit IRC12:04
*** jcoufal has joined #openstack-meeting-alt12:04
*** ttsiouts has joined #openstack-meeting-alt12:07
*** dustins has joined #openstack-meeting-alt12:09
*** erlon has quit IRC12:10
*** erlon has joined #openstack-meeting-alt12:29
*** kopecmartin|scho is now known as kopecmartin|ruck12:46
*** slagle has joined #openstack-meeting-alt12:47
*** slagle has quit IRC13:22
*** erlon_ has joined #openstack-meeting-alt13:25
*** tetsuro has joined #openstack-meeting-alt13:25
*** erlon has quit IRC13:29
*** slaweq__ is now known as slaweq13:36
*** slagle has joined #openstack-meeting-alt13:41
*** dpawlik has quit IRC13:47
*** alexchadin has joined #openstack-meeting-alt13:56
*** alexchadin has quit IRC13:56
*** munimeha1 has joined #openstack-meeting-alt13:58
*** alexchadin has joined #openstack-meeting-alt13:58
*** priteau has quit IRC13:58
*** priteau has joined #openstack-meeting-alt13:59
*** iyamahat has joined #openstack-meeting-alt14:02
*** munimeha1 has quit IRC14:05
*** hongbin has joined #openstack-meeting-alt14:17
*** munimeha1_ has joined #openstack-meeting-alt14:21
*** takashin has joined #openstack-meeting-alt14:30
*** takashin has left #openstack-meeting-alt14:30
*** liuyulong has joined #openstack-meeting-alt14:34
*** kopecmartin|ruck is now known as kopecmartin|scho14:47
*** jchhatbar has joined #openstack-meeting-alt14:50
*** janki has quit IRC14:53
*** jgrosso has joined #openstack-meeting-alt14:57
*** e0ne has quit IRC14:58
*** _erlon_ has joined #openstack-meeting-alt15:00
*** Swami has joined #openstack-meeting-alt15:00
tbarron#startmeeting manila15:01
openstackMeeting started Thu Oct  4 15:01:21 2018 UTC and is due to finish in 60 minutes.  The chair is tbarron. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: manila)"15:01
openstackThe meeting name has been set to 'manila'15:01
bswartz.o/15:01
gansohello15:01
gouthamro/15:01
* gouthamr comes in with trout shield15:01
dustins\o15:02
tbarronping xyang erlon15:02
tbarronping tpsilva vkmc15:02
amitohey!15:02
* dustins sees if attack roll beats gouthamr's AC on the trout shield15:02
_erlon_Hey15:03
tbarronamito: through with your drive already?15:03
jgrossohi15:03
vkmco/15:03
tbarronHi Jason!15:03
amitotbarron my girlfriend is driving ;)15:03
jgrossoHey Tom!15:03
tbarronEveryone meet jgrosso - Jason - a new addition on our team.15:03
tbarronHi all!15:03
tbarron#topic agenda15:04
*** openstack changes topic to "agenda (Meeting topic: manila)"15:04
gansowelcome to manila jgrosso! =)15:04
_erlon_Nice, hey Jason15:04
jgrossoThanks!!15:04
tbarron#link https://wiki.openstack.org/wiki/Manila/Meetings15:04
jgrossoHey15:04
amitoWelcome jgrosso15:04
jgrosso:)15:04
tbarron#topic Announcements15:04
*** openstack changes topic to "Announcements (Meeting topic: manila)"15:04
tbarronI nominated amito for manila core.  Thanks to those who have already voted.15:05
_erlon_Congrats amito15:05
amitoThanks for all the upvotes and trust :)15:05
tbarronWe'll give it till next Wednesday (a week after the nomination) and if there are no reservations we'll add him.15:05
gouthamramito: who said anything about trust :D15:06
tbarronI don't have any more announcements today.  Anyone else?15:06
tbarronTrust but verify.15:06
* amito puts on a sinister smile15:06
bswartz jgrosso from RedHat?15:06
tbarronbswartz: now he is, was Evil Machine Company15:07
jgrossoEMC15:07
jgrosso:)15:07
bswartz!!!15:07
openstackbswartz: Error: "!!" is not a valid command.15:07
gansotbarron: lol15:07
bswartzI didn't know anyone remembered that acryonym15:07
* bswartz slaps openstack around a bit with a large trout15:07
tbarronhe's going to be developing tests, breaking  manila.15:08
tbarroneasy work.15:08
jgrossoEndless Meeting Company was my fav15:08
bswartzwelcome jgrosso!15:08
vkmcEMC lol15:08
jgrossoThanks bswartz!15:08
*** iyamahat has quit IRC15:08
tbarron#topic Formalizing and changeing review guidelines.15:08
*** openstack changes topic to "Formalizing and changeing review guidelines. (Meeting topic: manila)"15:08
* dustins should really keep a d20 on his desk for all the trout slapping15:08
tbarron#link https://etherpad.openstack.org/p/manila-review-guidelines15:09
* gouthamr did i misspell that too? :(15:09
tbarrongouthamr you are up15:09
gouthamrty tbarron15:09
gouthamralright, this is a follow up on a short-discussion at the PTG15:09
tbarrongouthamr: I did a cut and paste but I think somehow introduced that extra 'e' myself15:09
gouthamrtbarron: no worries, you were imitating me15:09
xyanghi15:10
gouthamrthere's some content over in the etherpad15:10
* tbarron knows he meant *irritating*15:10
gouthamrhi xyang!15:10
tbarronall that orange is really annoying15:10
tbarronxyang: greetings15:10
* gouthamr slaps ganso with a trout15:11
gouthamroops, meant tbarron15:11
gansogouthamr: hey!15:11
tbarronouch15:11
*** ttsiouts has quit IRC15:11
gouthamrhehe, okay.. i can tl;dr a bit15:11
gouthamrplease look at the proposal, we're all aware of the lack of reviewer attention in manila for a while now15:11
vkmcwe need reviewers for the reviewers guide15:12
gouthamri'm proposing some new changes, and would like buy-in before formalizing them into a devref (there's your answer ganso, missed that point on the proposal, added now)15:12
* tbarron sees what vkmc did15:12
bswartzI'm confused15:13
*** e0ne has joined #openstack-meeting-alt15:13
_erlon_Good stuff, I was just wondering if allowing 1 +2 approvals for drivers bug fixes woundnt be a good case15:13
bswartzI thought the +2s from different organizations was meant to satisfy the organizational diversity goal from the TC15:13
gouthamrvkmc: i do this, a couple of releases ago I proposed this: https://review.openstack.org/#/c/321334/15:14
gouthamr:D15:14
tbarronbswartz: that was one of the goals but I think that isn't really being tracked in the same way any more?15:15
gouthamrtbarron: do we mind discussing each point right here?15:15
vkmcbswartz, apart from that, I think it's a good practice15:15
bswartzWell either it's something we care about or something we don't care about15:15
tbarrongouthamr: I don't mind spending some time if we can drive general agreement15:15
gouthamrtbarron bswartz: the short take on that is on lines 37 and beyond15:15
bswartzIf we don't care about it (it seems the proposal says we shouldn't) then let's be explicit about that15:16
gouthamrTC changed the definition of what it meant to be organizationally diverse15:16
bswartzI don't think the TC would be upset15:16
bswartzgouthamr: they did? do you have a link?15:16
vkmcencouraging reviews from people with different affiliations aims to reduce bias15:16
gouthamrand we no longer have a tag on each project15:16
vkmcit's fair15:16
gouthamr#LINK https://review.openstack.org/#/c/579870/15:16
* gouthamr finds link to ML thread15:16
vkmcgouthamr, you like meta-planning stuff lol15:17
bswartzThe commit message here is fine15:17
bswartzttx lays out a good case for why the tag is harmful15:17
tbarronvkmc: I still want to encourage diversity, the question is whether we need a rule that requires this on every review15:17
tbarroneven when e.g. we're just fixing stuff and there's no particular organizational interest at stake15:18
vkmctbarron, imho this should be mandatory for new features, not mandatory for bug fixes15:18
gouthamr#LINK http://lists.openstack.org/pipermail/openstack-dev/2018-June/131029.html15:18
bswartztbarron: if you think reviews add value beyond just a rubber stamp, then keep them15:18
vkmcthere is no bias in trying to fix something that is broken15:18
gouthamrbswartz: +115:18
gouthamrtbarron: +115:18
gouthamri'm only seeking dropping the need for rubber-stamp reviews15:19
tbarrondo we leave it to the workflow+1 person's judgment whether an additional review would be rubber-stamp or real review?15:20
bswartzI don't think it's possible to know if a review will be a rubber stamp or not15:20
bswartzIf you want a review, ask for it. If you want a rubber stamp, then don't ask for it and ninja merge instead15:20
gouthamrbswartz: nooo15:21
bswartzI don't see what the problem with ninja merges is15:21
* gouthamr , points to line on Ninja Merges: #5215:21
gouthamrbswartz: i am uncomfortable doing it, and i've added a couple of links with specific cases when ninja-merges may be useful15:22
bswartzWhat's the case against ninja merges?15:22
gouthamrbswartz: it's anti-community?15:22
bswartzIt's something the tools let us do -- the prohibition on them is something we enforce socially15:22
bswartzI would only be upset if someone exercised poor judgement with a ninja merge15:23
gouthamr+1, so i think we should retain our current policy on it - don't do it if you can help it15:23
gansoI think reviews are important everywhere except trivial changes, gate fixes and version upgrades15:23
gouthamrinstead of relying on our judgements15:23
gouthamrganso: absolutely +115:24
bswartzganso: are you in favor of dropping the review requirements in some cases then?15:24
gansoyea, people's judgements vary, in a way that it may seem like another reviewer feedback is not needed but actually is15:24
gansobswartz: just some cases15:25
vkmcganso++15:25
*** slagle has quit IRC15:25
*** macza has joined #openstack-meeting-alt15:25
vkmcninja merging should be the last resource15:25
amitoganso: i agree, moreover, this is the way to improve code quality15:25
bswartzI think we need to trust eachother on this kind of thing. If you don't feel like you could trust someone to exercise judgement, then don't nominate them to be a core reviewer15:25
vkmcbecause we need to fix something urgently (due to time constrains) and it's safe to do it15:26
vkmcbswartz++15:26
dustinsIf you abuse your powers, we'll know :)15:27
bswartzYes we have audit trails of what people do15:27
bswartzI don't think we've had big problems with people abusing trust15:27
bswartzSo I don't see a need to change anything15:28
gouthamrbswartz: can you clarify, anything, as in any of the problems in the proposal, or a specific one?15:28
gansobswartz: in the end of the day we are humans and we do some mistakes, we overlook some problems in the code, having 2 reviewers is good for code quality and because we have diverse opinion on how to implement something or fix a bug. Our history has shown us many times that we had code almost merging and somebody shows up with a -1 and a valid point on something to fix or improve15:28
tbarronbswartz: are you saying that we don't need a doc that writes down expecations?  I think that would be helpful as guidelines even15:29
bswartzgouthamr: I don't understand your dislike for ninja merging -- it's an important tool, and using it would solve some of the problems you seem to be complaining about15:29
tbarronthough I don't think a set of formal rules may make sense.15:29
gouthamrbswartz: hey, let me remind you of your ninja merge history :)15:29
gouthamrbswartz15:29
gouthamrbswartz: it's really short :P15:30
bswartzAnd I'm still not clear on what specific problem we're trying to solve15:30
gouthamrbswartz: i.e, we don't really have a dire-need for writing teh code and merging it ourselves15:30
gouthamrbefore anyone else has a say in it15:30
tbarronnote two difft kinds of ninja merges !15:30
bswartzgouthamr: are you arguing that's a good thing or a bad thing?15:30
tbarronone reviewer different coder15:30
gouthamrbswartz: a good thing15:31
tbarronone reviewer coded change themselves15:31
tbarronthe latter should be exceptional for sure15:31
bswartzYeah I was able to avoid ninja merges for the most part15:31
gouthamrtbarron: there's only ONE kind of ninja merge - I am the author of the change, and i merge it myself (usually before anyone else has to weigh in)15:31
bswartzBut that's not because I was afraid to do it, I was just able to find people quickly enough when I needed them15:32
gansoninja merge = I code the fix, I merge it myself. This is not what we want. What we want: one person codes an urgent gate fix, another person from the same company solely merges it15:32
tbarrongouthamr: ok if that's the definition but we were also talking about more general issues15:32
bswartzganso: we can achieve that by dropping our explicit diversity goal15:32
gouthamrbswartz: +1, i managed to dig through the team's history and see why we did it when we did it15:32
gouthamrand put out a couple of fine examples15:32
tbarronganso: I have no problem with a ninja merge fixing gate if no one else is around15:32
gansotbarron: yes, we do it excepcionally, we don't want to make it the norm15:33
gouthamr+115:33
tpsilvaI think Valeriy used to that a lot, and it was always helpful15:33
tbarronor if we already agreed in the community meeting to do the change and it's trivial to execute15:33
tpsilvafor gate fixes15:33
gansotbarron: if there are 2 people are there is no need to ninja merge15:33
gouthamr+115:33
tbarronganso: ditr15:33
gansos/are there/around, there15:33
tbarrons/ditr/sure/15:34
tbarronSo do we have a problem with people ninja merging now or is this a matter of writing down our expectations?15:34
bswartzWriting down the current expectations makes sense15:35
bswartzI don't see a need to change any longstanding policy15:35
bswartzAlthough I'd be open to changing policies for good reasons15:35
bswartzI just feel like I'm missing something15:36
* bswartz goes to read etherpad one more time15:36
gouthamrthat's good clarification, ty - can i ask about specific proposals? or do you want to discuss this on a review?15:36
gansogouthamr: we could consolidate it on a doc page through gerrit review15:36
gouthamri see some good points on the etherpad, ty ganso, tbarron, tpsilva (?)15:36
tbarronWe've taken a bit of time today but it's been a healthy discussion.15:37
tbarrongouthamr: why don't you post this in review.  Then let's have another meeting topic after everyone15:37
gouthamrtbarron: ack, will do15:37
tbarronhas had a chance to digest it again, have sidebar conversations, etc.15:38
gouthamrabsolutely, thanks everyone!15:38
tbarronI think it was good to have the etherpad and open discussion rather than just a bare review.15:38
tbarron#topic Planning Our work15:39
*** openstack changes topic to "Planning Our work (Meeting topic: manila)"15:39
tbarron#link https://wiki.openstack.org/wiki/Manila/SteinCycle15:39
tbarronWe introduced this wiki page last week and it's still WIP but15:39
tbarronI want to spend a few minutes discussing how to maintain and use it.15:40
tbarronLet's look at the python3 topic as an example.15:40
tbarronvkmc is the lead on this story.15:40
tbarronDoesn't mean that she does all the work.15:41
tbarronBut she is responsible for defining the tasks and for ensuring that15:41
tbarronthe status is up to date.15:41
tbarronShe can do that by editing the wiki or by emailing me since I'm going to do at least a weekly sweep.15:42
tbarronother people doing work on this project -- like gouthamr -- can do the same.15:42
tbarronNo strict hierarchy.15:42
tbarronMake sense?15:42
dustins+115:42
gouthamr+115:42
vkmc+115:43
* tbarron notes that he filled this one out and vkmc and gouthamr should slap him with trout and ensure that it's corrected after the meeting15:43
bswartzMakes sense15:43
amito+115:43
tbarronok, moving down the list15:43
tbarronJun isn't here today so we'll skip Priority for Access rules.15:43
tbarrongouthamr: check that what I said on the json schema validation is correct15:44
gouthamrtbarron: it is15:44
gouthamrwe sent an email to the spec owners asking if they want to continue working on JSON schema validation for Stein, no response yet15:44
tbarronganso: on manage/unmaage dhss=true please update or send me mail and I will15:45
gansotbarron: thanks for reminding me, I'll update15:45
tbarronganso: same for replicatin/dhss=True and share from snapshot in different pool/back end15:45
tbarronvkmc: please check manila ui plugin (also dustins )15:46
dustinstbarron: wilco15:46
*** jchhatbar has quit IRC15:46
tbarronon manila CSI gouthamr is scheduling a meeting with the CERN folks who are proposing same15:46
*** e0ne has quit IRC15:47
gouthamr+1, forgot to add it to this meeting, we just have confirmation of availability from the CERN folks15:47
tbarronand we're working with hodgepodge on standing sig-k8s meetings on manila and cinder CSI15:47
tbarronall early stuff15:47
gouthamrif we have anyone here that would like to know what's going on right now with Manila/CSI/dynamic-provisioner/*, please let me know i'll forward you an invite15:48
tbarronvkmc: you own the uwsgi project15:48
vkmcyes15:48
tbarrongouthamr: you are driving osc integration15:48
gouthamrtbarron: ack, status coming soon-ish15:48
tbarronnote that this should be a project to which we can have lots of contributors once it's underway15:49
gouthamr+115:49
tbarronamito: you are going to lead the sdk integration I think?15:49
amitotbarron: yep15:49
tbarronanother one that once framed we should be able to have people sign up for chunks  of work15:50
gouthamrtbarron amito: storyboard: https://storyboard.openstack.org/#!/story/200375215:50
gouthamrfor the OS-SDK work15:50
amitotbarron: some of it has already been implemented in the PTG, I don't think it should be a lot of work15:50
tbarronvkmc: are you planning a spec for the next telemetry work ?15:50
*** liuyulong has quit IRC15:51
vkmctbarron, I don't think is needed since it was mostly finish work we had planned in the previous spec and documentation15:51
vkmctbarron, but if we need it, I'll submit it by the end of the week15:51
tbarronvkmc: k, makes sense, that's kinda what I was thinking.15:51
vkmc:)15:51
tbarronAny more on this topic today?  Going forwards I'm hoping most of keeping this up to date will be *outside* this meeting.15:52
tbarron#topic Bugs15:52
*** openstack changes topic to "Bugs (Meeting topic: manila)"15:52
tbarrondustins: got any for us today?15:52
dustinsJust one today, since the other was already squashed by gouthamr15:53
tbarron#link https://wiki.openstack.org/wiki/Manila/SteinCycle#Bug_Triage15:53
dustins#link https://etherpad.openstack.org/p/manila-bug-triage-pad15:53
tbarronjinx15:53
dustins#link: https://bugs.launchpad.net/manila/+bug/179546315:53
openstackLaunchpad bug 1795463 in Manila "pagination limit not enforced on db" [Undecided,New]15:53
bswartzIs this just a missing optimization?15:53
gouthamrtech debt :(15:54
bswartzDoing pagination right is hard work15:54
bswartzI think the bug description should read "pagination doesn't speed up list queries"15:55
gouthamrtrue15:55
bswartzBecause speeding up the operation is the whole point15:55
tbarronso this one is confirmed, right?15:56
gouthamrcurrently, we're using some python methods to do the limit and the offset, but as maurice notes, this should be done in the DB to get some speedup15:56
tbarronhow serious?15:56
gouthamrwe've some examples in the newer APIs15:56
tbarrondo we want maurice if he wants to fix it?15:56
bswartzIt's a performance bug, so that lowers the priority somewhat15:57
tbarrongouthamr: examples of doing it right?15:57
gouthamrtbarron: we want maurice :D15:57
tbarronbswartz: +115:57
gouthamrtbarron: yes, i think, i can point it out on the bug, he points to an old manila commit that dropped it in the /shares APO15:58
gouthamrAPI*15:58
tbarron#action gouthamr will update the bug with pointers and ask maurice if he wants to work on it15:59
tbarronI did the other updates15:59
gouthamrack16:00
tbarron#action dustins put this on in your keep-track-of list on the etherpad please16:00
tbarronout of  time16:00
* bswartz glances at the clock16:00
*** gyee has joined #openstack-meeting-alt16:00
tbarronThanks everyone!!!16:00
bswartzthx!16:00
tbarron#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
dustinstbarron: Done!16:00
openstackMeeting ended Thu Oct  4 16:00:42 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2018/manila.2018-10-04-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2018/manila.2018-10-04-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2018/manila.2018-10-04-15.01.log.html16:00
*** jgrosso has quit IRC16:01
*** iyamahat has joined #openstack-meeting-alt16:14
*** slagle has joined #openstack-meeting-alt16:20
*** alexchadin has quit IRC16:34
*** dosaboy has quit IRC16:39
*** dosaboy has joined #openstack-meeting-alt16:45
*** iyamahat has quit IRC16:51
*** dosaboy has quit IRC16:55
*** diablo_rojo has joined #openstack-meeting-alt16:55
*** dosaboy has joined #openstack-meeting-alt17:01
*** derekh has quit IRC17:04
*** iyamahat has joined #openstack-meeting-alt17:04
*** yamahata has joined #openstack-meeting-alt17:04
*** sridharg has quit IRC17:22
*** Swami has quit IRC17:36
*** tssurya has quit IRC17:48
*** yamamoto has quit IRC17:51
*** yamamoto has joined #openstack-meeting-alt17:52
*** yamamoto has quit IRC17:57
*** munimeha1_ has quit IRC18:01
*** iyamahat_ has joined #openstack-meeting-alt18:02
*** Swami has joined #openstack-meeting-alt18:04
*** iyamahat has quit IRC18:05
*** macza has quit IRC18:25
*** macza has joined #openstack-meeting-alt18:26
*** yamamoto has joined #openstack-meeting-alt18:30
*** e0ne has joined #openstack-meeting-alt18:31
*** e0ne has quit IRC18:33
*** dustins has quit IRC18:43
*** jcoufal has quit IRC18:57
*** _erlon_ has quit IRC19:19
*** munimeha1 has joined #openstack-meeting-alt19:30
*** dustins has joined #openstack-meeting-alt19:41
*** munimeha1_ has joined #openstack-meeting-alt19:42
*** slagle has quit IRC19:43
*** munimeha1 has quit IRC19:43
*** jcoufal has joined #openstack-meeting-alt19:48
*** jcoufal_ has joined #openstack-meeting-alt20:03
*** jcoufal has quit IRC20:05
*** e0ne has joined #openstack-meeting-alt20:08
*** e0ne has quit IRC20:14
*** priteau has quit IRC20:15
*** slagle has joined #openstack-meeting-alt20:19
*** diablo_rojo has quit IRC20:24
*** diablo_rojo has joined #openstack-meeting-alt20:25
*** e0ne has joined #openstack-meeting-alt20:30
*** priteau has joined #openstack-meeting-alt20:36
*** devananda has quit IRC20:38
*** slagle has quit IRC20:39
*** jtomasek has quit IRC20:39
*** macza has quit IRC20:40
*** macza has joined #openstack-meeting-alt20:41
*** ijw has quit IRC20:43
*** rdopiera has quit IRC20:43
*** priteau has quit IRC20:48
*** e0ne has quit IRC21:00
*** erlon_ has quit IRC21:05
*** devananda has joined #openstack-meeting-alt21:25
*** panda is now known as panda|off21:36
*** dustins has quit IRC21:40
*** munimeha1_ has quit IRC21:45
*** ijw has joined #openstack-meeting-alt21:48
*** jcoufal_ has quit IRC22:07
*** ganso has quit IRC22:27
*** rcernin has joined #openstack-meeting-alt22:28
*** tpsilva has quit IRC22:40
*** hongbin has quit IRC22:57
*** macza has quit IRC22:58
*** pbourke has quit IRC23:03
*** pbourke has joined #openstack-meeting-alt23:04
*** ijw has quit IRC23:14
*** ijw_ has joined #openstack-meeting-alt23:14
*** slagle has joined #openstack-meeting-alt23:35
*** edleafe has quit IRC23:39
*** ijw_ has quit IRC23:53
*** tetsuro_ has joined #openstack-meeting-alt23:57

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