Thursday, 2018-10-18

*** Swami has quit IRC00:02
*** cloudrancher has joined #openstack-meeting-alt00:31
*** diablo_rojo has quit IRC00:39
*** bswartz has joined #openstack-meeting-alt00:44
*** tetsuro has joined #openstack-meeting-alt01:03
*** markvoelker has joined #openstack-meeting-alt01:05
*** markvoelker has quit IRC01:09
*** yamahata has quit IRC01:14
*** cloudrancher has quit IRC01:22
*** erlon__ has quit IRC01:29
*** tpsilva has quit IRC01:40
*** lei-zh has joined #openstack-meeting-alt01:48
*** tetsuro has quit IRC01:49
*** tetsuro has joined #openstack-meeting-alt01:52
*** hongbin has joined #openstack-meeting-alt02:29
*** tetsuro has quit IRC02:42
*** dave-mccowan has quit IRC02:56
*** lei-zh has quit IRC02:57
*** lei-zh has joined #openstack-meeting-alt02:58
*** rcernin has quit IRC03:02
*** bnemec has joined #openstack-meeting-alt03:05
*** bnemec has quit IRC03:10
*** rcernin has joined #openstack-meeting-alt03:28
*** tetsuro has joined #openstack-meeting-alt03:35
*** bhavikdbavishi has joined #openstack-meeting-alt03:36
*** isq_ has joined #openstack-meeting-alt03:37
*** yamahata__ has quit IRC03:39
*** bhavikdbavishi1 has joined #openstack-meeting-alt03:50
*** bhavikdbavishi has quit IRC03:52
*** bhavikdbavishi1 is now known as bhavikdbavishi03:52
*** hongbin has quit IRC03:57
*** yamamoto has quit IRC04:34
*** yamamoto has joined #openstack-meeting-alt04:34
*** chhagarw has joined #openstack-meeting-alt05:00
*** ccamacho has quit IRC05:03
*** lei-zh has quit IRC05:15
*** bhavikdbavishi has quit IRC05:23
*** liuyulong has quit IRC05:24
*** bhavikdbavishi has joined #openstack-meeting-alt05:25
*** lbragstad_503 has quit IRC05:27
*** lbragstad_503 has joined #openstack-meeting-alt05:27
*** lei-zh has joined #openstack-meeting-alt05:38
*** jtomasek has joined #openstack-meeting-alt06:18
*** e0ne has joined #openstack-meeting-alt06:38
*** janki has joined #openstack-meeting-alt06:51
*** rcernin has quit IRC07:07
*** lpetrut has joined #openstack-meeting-alt07:09
*** alexchadin has joined #openstack-meeting-alt07:14
*** alexchadin has quit IRC07:19
*** janki has quit IRC07:19
*** persia has quit IRC07:19
*** persia has joined #openstack-meeting-alt07:21
*** apetrich has quit IRC07:39
*** rdopiera has joined #openstack-meeting-alt07:52
*** chhagarw has quit IRC07:53
*** dpawlik has quit IRC07:55
*** apetrich has joined #openstack-meeting-alt08:00
*** e0ne has quit IRC08:02
*** kopecmartin|off is now known as kopecmartin08:02
*** slaweq has joined #openstack-meeting-alt08:02
*** ttsiouts has joined #openstack-meeting-alt08:03
*** ttsiouts has quit IRC08:09
*** e0ne has joined #openstack-meeting-alt08:13
*** dpawlik has joined #openstack-meeting-alt08:13
*** ttsiouts has joined #openstack-meeting-alt08:15
*** tssurya has joined #openstack-meeting-alt08:16
*** cloudrancher has joined #openstack-meeting-alt08:21
*** ttsiouts has quit IRC08:24
*** tetsuro has quit IRC08:25
*** ttsiouts has joined #openstack-meeting-alt08:31
*** jesusaur has quit IRC08:38
*** derekh has joined #openstack-meeting-alt08:39
*** cloudrancher has quit IRC08:39
*** alexchadin has joined #openstack-meeting-alt08:40
*** ttsiouts has quit IRC08:43
*** dpawlik has quit IRC09:02
*** dpawlik has joined #openstack-meeting-alt09:04
*** jesusaur has joined #openstack-meeting-alt09:31
*** cloudrancher has joined #openstack-meeting-alt09:39
*** ttsiouts has joined #openstack-meeting-alt09:40
*** ttsiouts has quit IRC09:43
*** betherly has joined #openstack-meeting-alt09:43
*** alexchadin has quit IRC09:50
*** ttsiouts has joined #openstack-meeting-alt09:51
*** priteau has joined #openstack-meeting-alt09:52
*** cloudrancher has quit IRC09:54
*** bhavikdbavishi has quit IRC09:56
*** jbadiapa has quit IRC09:58
*** ttsiouts has quit IRC10:06
*** ttsiouts has joined #openstack-meeting-alt10:07
*** yamamoto has quit IRC10:11
*** ttsiouts has quit IRC10:11
*** yamamoto has joined #openstack-meeting-alt10:12
*** cloudrancher has joined #openstack-meeting-alt10:13
*** yamamoto has quit IRC10:16
*** yamamoto has joined #openstack-meeting-alt10:16
*** dave-mccowan has joined #openstack-meeting-alt10:20
*** cloudrancher has quit IRC10:21
*** cloudrancher has joined #openstack-meeting-alt10:35
*** ttsiouts has joined #openstack-meeting-alt10:40
*** ttsiouts has quit IRC10:48
*** ttsiouts has joined #openstack-meeting-alt10:49
*** cloudrancher has quit IRC10:52
*** bhavikdbavishi has joined #openstack-meeting-alt10:54
*** chhagarw has joined #openstack-meeting-alt10:57
*** lei-zh has quit IRC11:05
*** erlon__ has joined #openstack-meeting-alt11:11
*** jbadiapa has joined #openstack-meeting-alt11:14
*** yamamoto has quit IRC11:20
*** yamamoto has joined #openstack-meeting-alt11:21
*** yamamoto has quit IRC11:25
*** panda is now known as panda|lunch11:39
*** chhagarw has quit IRC11:39
*** e0ne has quit IRC11:50
*** yamamoto has joined #openstack-meeting-alt12:03
*** ttsiouts has quit IRC12:11
*** raildo has joined #openstack-meeting-alt12:13
*** panda|lunch is now known as panda12:13
*** yamamoto has quit IRC12:20
*** yamamoto has joined #openstack-meeting-alt12:20
*** apetrich has quit IRC12:21
*** ttsiouts has joined #openstack-meeting-alt12:23
*** liuyulong has joined #openstack-meeting-alt12:28
*** dims has quit IRC12:30
*** dims has joined #openstack-meeting-alt12:33
*** apetrich has joined #openstack-meeting-alt12:33
*** jesusaur has quit IRC12:33
*** lpetrut has quit IRC12:33
*** ttsiouts has quit IRC12:35
*** ttsiouts has joined #openstack-meeting-alt12:49
*** e0ne has joined #openstack-meeting-alt13:07
*** weshay is now known as weshay_meeting13:12
*** munimeha1 has joined #openstack-meeting-alt13:29
*** lbragstad_503 is now known as lbragstad13:32
*** bnemec has joined #openstack-meeting-alt13:43
*** jgrosso has joined #openstack-meeting-alt13:44
*** hongbin has joined #openstack-meeting-alt14:05
*** efried_pto is now known as efried14:06
*** slaweq has quit IRC14:06
*** slaweq has joined #openstack-meeting-alt14:08
*** ttsiouts has quit IRC14:10
*** apetrich has quit IRC14:11
*** cloudrancher has joined #openstack-meeting-alt14:18
*** apetrich has joined #openstack-meeting-alt14:20
*** ttsiouts has joined #openstack-meeting-alt14:21
*** ccamacho has joined #openstack-meeting-alt14:30
*** sambetts|afk is now known as sambetts14:31
*** cloudrancher has quit IRC14:45
*** Swami has joined #openstack-meeting-alt14:56
*** cloudrancher has joined #openstack-meeting-alt14:58
*** ganso has joined #openstack-meeting-alt15:00
*** alysonr_ has joined #openstack-meeting-alt15:00
*** ttsiouts has quit IRC15:00
tbarron#startmeeting manila15:00
openstackMeeting started Thu Oct 18 15:00:52 2018 UTC and is due to finish in 60 minutes.  The chair is tbarron. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: manila)"15:00
openstackThe meeting name has been set to 'manila'15:00
gouthamro/15:01
bswartz.o/15:01
gansohello15:01
erlon__hey15:01
tbarronping vkmc15:01
amitohello .o/15:01
tbarronping dustins15:01
tbarronping erlon15:01
dustins\o15:01
tbarronping xyang15:01
xyanghi15:01
tbarronping tpsilva15:02
tbarronI think those are all the folks from the ping list who are not away15:02
tbarronHi all!15:02
tbarronAgenda:15:03
tbarron#link https://wiki.openstack.org/wiki/Manila/Meetings15:03
*** ttsiouts has joined #openstack-meeting-alt15:03
tbarron#topic announcements15:03
*** openstack changes topic to "announcements (Meeting topic: manila)"15:03
tbarronFive of us will not be here next week - we're at an offsite meeting - so:15:04
tbarronI'm one of the five.15:04
tbarronSo:15:04
tbarron1) does someone else want to chair the meeting next week?15:04
*** jgrosso_ has joined #openstack-meeting-alt15:04
tbarronor15:04
tbarron2) should we skip a week?15:05
tbarroncrickets15:05
bswartzSkipping is fine15:05
bswartzI sounds like we would lack quorum anyways15:05
tbarronanyone to the contrary?15:06
*** dklyle has joined #openstack-meeting-alt15:06
gansobswartz: +115:06
*** luizbag has joined #openstack-meeting-alt15:06
tbarron#action tbarron will send email that we're skipping next week's meeting15:06
*** markstur has joined #openstack-meeting-alt15:06
*** jgrosso has left #openstack-meeting-alt15:06
dustinsSounds good to me15:06
bswartzIs the offsite thing a RedHat meeting?15:06
tbarronbswartz: yeah, in Raleigh, which is offsite for all of us but dustin15:07
bswartzBecause NetApp has a big thing next week too15:07
tbarrondustins is having and onsite offsite15:07
tbarronbswartz: curious15:07
tbarronbswartz: and All Things Open is overlapping I think15:07
dustinsFar enough away for it to be offsite, close enough to not get a hotel :P15:08
* gouthamr a party in Las Vegas15:08
* bswartz thought that dustins lived so far from town that everything is offsite15:08
dustinsbswartz: So did I :D15:08
tbarronMoving on, summit/Forum topics are up:15:08
* dustins dreads two hours of commuting everyday next week15:08
tbarron#link https://www.openstack.org/summit/berlin-2018/summit-schedule/global-search?t=manila15:08
dustinsFor a good reason, at least :)15:08
tbarron^^^^ looks like lots of manila content15:09
dustinsOh wow, that's awesome!15:09
tbarronNext, I want to call attention to a change to cycle-with-milestones projects like manila proper15:11
tbarron#link http://lists.openstack.org/pipermail/openstack-dev/2018-September/135088.html15:11
tbarronWe no longer do milestone releases15:11
tbarronBut still pay attention to milestones for tracking purposes.15:12
tbarronAny questions/comments on this change?15:12
bswartzInteresting15:12
bswartzA sign of stability I guess15:12
*** e0ne has quit IRC15:12
*** betherly has quit IRC15:13
tbarronAny other announcements?15:13
tbarron#topic Code Review Guideline up for review15:13
*** openstack changes topic to "Code Review Guideline up for review (Meeting topic: manila)"15:13
tbarrongouthamr: you're up15:13
tbarron#link https://review.openstack.org/#/c/609598/15:13
gouthamrhi, ty tbarron15:13
gouthamri put that up last week, and have been having some good discussions on it, just a pointer for the rest of us to take a look as well :)15:14
gouthamrthat's all i had about that15:15
tbarronEveryone should pay attention to the sections on15:16
tbarronAffiliation, Ninja merging, and Vendor code and review.15:16
tbarronAny other remarks on this topic now?15:17
* dustins makes a point to look it over15:17
bswartzI'm not sure we want to document the process of ninja merging15:17
bswartzIt's kind of like talking about fight club15:18
tbarronlol15:18
gouthamr:P15:18
*** e0ne has joined #openstack-meeting-alt15:18
gansobswartz: you just broke #1 rule15:18
bswartzWhat is the first rule of fight club?15:18
luizbagyou never talk about fight club15:18
bswartzI feel the same way about ninja merges15:19
tbarronhttps://www.youtube.com/watch?v=dC1yHLp9bWA15:19
tbarronlet's discuss this subject some more15:19
tbarronin the review :)15:19
*** jesusaur has joined #openstack-meeting-alt15:19
bswartzOkay15:20
gouthamr+1 ty everyone15:20
tbarron#topic access rule prioritization15:20
*** openstack changes topic to "access rule prioritization (Meeting topic: manila)"15:20
tbarronganso, that's you!15:20
gansotbarron: thanks15:20
gansoWhile testing the patch, our team found something that we believe to be an issue15:20
gansothe spec proposes that, 1) when there are conflicting rules under the same priority, the behavior will be undefined15:21
*** yamamoto has quit IRC15:21
gansohttps://review.openstack.org/#/c/552935/19/specs/rocky/priority-for-access-rules.rst@8215:21
bswartzThis is intentional I think15:22
bswartzFor backwards compatibility15:22
*** yamamoto has joined #openstack-meeting-alt15:22
ganso2) after this change merges, drivers that reorder rules should stop doing so15:22
bswartzThe prior behavior is undefined, so we preserve whatever that undefined behavior is when there's a tie15:22
gansohttps://review.openstack.org/#/c/552935/19/specs/rocky/priority-for-access-rules.rst@30215:22
gansothe issue is: some backends do not have "undefined" behavior. Their behavior is defined and deterministic15:22
bswartzSo they match the spec then by definition15:23
gansoI will give an example15:23
bswartzUndefined just means you can do whatever you want and it will be considered correct by the spec15:23
gansoif a driver reorders the rule today to achieve a certain behavior, after the priorization patch merges, and the reordering is removed from the drivers15:24
gansothe behavior will not be the same when there are conflicting rules under the same priority15:24
bswartzIn practice we should encourage backends to break ties in exactly the way they used to handle conflicts before priorities existed15:24
tbarronbswartz: I think the issue is that the backend won't know that there is a tie.15:24
bswartzBut the spec doesn't require this15:25
tbarronthere will be a sort before the back end sees the rule set15:25
bswartzI see15:25
* bswartz headdesk15:25
tbarronso the back end can't preserve *exactly* the same behavior15:25
gansoour team disagrees with removing the reordering of rules once the patch lands because we would like to retain the behavior for the scenario I described. That is, we want to continue reordering rules when there are conflicting rules with the same priority15:25
gansotbarron: yes15:26
*** yamamoto has quit IRC15:26
tbarronganso: but you might violate the prioritization for non-ties!15:26
bswartzIs there a way we can add a capability so the drivers can declare support for rule priority and do the sorting themselves?15:26
gansotbarron: we want to change to code to take the other priorities into consideration15:26
gansobswartz: if we do that, the user experience will be inconsistent15:27
bswartztbarron: drivers can do that anyways15:27
gansotbarron: s/change to code/change the code15:27
tbarronbswartz: ?  they shouldn't, right?15:27
bswartztbarron: only tests cases can enforce that they don't15:27
bswartzAnd tests cases can enforce correct behavior however we implement it internally15:28
bswartzSo I propose a driver capability that the manager can query before it performs the sort15:28
bswartzObviously the capability will default to false15:28
tbarronDo any back ends besides NetApp sort the rules now?15:29
bswartzWe might not have the right people in the room to answer that15:29
tbarronWe may be able to just tie-break in the manager in a way that is consistent with current practice and then15:29
tbarronnot have to add extra complexity.15:29
bswartztbarron: if the desire is the implement tie breaking in the manager in a consistent way, then we should write that way into the spec so it's clear15:30
tbarronAll back ends would stop sorting themselves and we'd have the correct behavior.15:30
*** devananda has joined #openstack-meeting-alt15:30
tbarronbswartz: I agree that we should write how the manager will tie break in the spec.15:30
gansotbarron, bswartz: I agree with that, but apparently this was discussed in the spec and people agreed to not do that15:30
bswartzIf we want to preserve legacy behavior (or flexibility to do interesting things) then leaving it undefined makes more sense, and we should give drivers freedom to sort the list how they choose15:31
bswartzBut in any case, write tests that ensure drivers conform to the spec at least15:31
gansobswartz: indeed, as the spec puts it, the undefined behavior couldn't be tested consistently15:32
bswartzYou don't test undefined behavior, you test the defined behavior15:32
gansotbarron: it seems we don't have the spec owner here to discuss, how would we approach this?15:33
tbarronThe spec does not say drivers can just do whatever they want, only that when there are conflicts that it is undefined.15:33
gansobswartz: yes, it creates a test gap15:33
gansotbarron: I'm fine with that statement, I am against not being able to reorder the rules in the driver anymore, as stated in the spec15:34
bswartztbarron: agree15:34
tbarronganso: how will you know which rules you can re-order?15:34
*** ttsiouts has quit IRC15:35
tbarronganso: how will you know you don't violate the expressed priority?15:35
gansotbarron: we can read the 'priority' field within the driver15:35
tbarronganso: it's not in the rules given to you15:35
gansotbarron: we will sort only the group of rules within the same priority15:35
gansotbarron: according to my team tests, it is15:35
tbarronganso: how will you know that group15:36
gansotbarron: the model is being passed to the driver15:36
tbarronganso: oh I thought just the rules were passed, in an order, with no priority15:36
*** ccamacho has quit IRC15:36
tbarronganso: if you have the priority info, without having to do a database lookup from the driver, then sure15:37
gansotbarron: and even if this is a bug and the priority shouldn't be passed, then I disagree with it not being passed, and without it we wouldn't be able to accomplish what I am proposing15:37
gouthamryeah, we discussed passing the priority down to the drivers on the review/spec and agreed to do it iirc15:38
tbarrongouthamr: ok, i missed that15:38
*** ccamacho has joined #openstack-meeting-alt15:38
gansoprobably the model shouldn't be passed, but a dictionary containing the regular access fields and the priority should15:39
*** ttsiouts has joined #openstack-meeting-alt15:39
tbarronthen there's no issue with back ends maintaining current tie-breaking behavior, right?15:39
gansotbarron: yes, assuming they just reorder what falls in the "undefined" behavior15:40
tbarronI think we  can take any remaining discussioon to the review then.15:41
gansook15:41
tbarronganso: you still need to change your back end not to do a general sort15:41
gansoglad to reach agreement =)15:41
gansotbarron: yes, we will15:41
tbarronganso: just scope it to the ties15:41
gansotbarron: yup15:41
tbarron#topic planning our work15:41
*** openstack changes topic to "planning our work (Meeting topic: manila)"15:41
tbarron#link https://wiki.openstack.org/wiki/Manila/SteinCycle#Priority_for_Access_Rules15:42
tbarronSpec approval deadline is 8 November15:42
tbarronThe main thing on this topic that I want to cover today is15:42
tbarronwhich specs will be proposed.15:43
tbarronganso you have three, two of which are in the work plan.15:43
gansotbarron: actually 3, if you refresh the page right now15:43
*** gyee has joined #openstack-meeting-alt15:43
tbarronganso++15:43
tbarronWho else is planning on doing a spec?15:44
* tbarron thinks not all work requires specs but15:44
gouthamri am, for a few things that i raised BPs for15:44
gouthamrheh, read my mind15:44
*** tssurya has quit IRC15:44
tbarronif you are going to do a spec please post a review for it,15:45
gouthamrsure15:45
tbarroneven if you mark it WIP and it doesn't have anything yet15:45
tbarronand put the link in the work plan.15:45
gouthamryessir15:45
tbarronI think a plan of work may be useful as a "spec" for things like OSC and SDK15:46
*** liuyulong has quit IRC15:46
tbarronwhere we hope to divide and conquer on the actual tasks.15:46
*** liuyulong has joined #openstack-meeting-alt15:47
tbarronThat's all I have on this topic for this week.15:47
tbarron#topic Bugs!15:47
*** openstack changes topic to "Bugs! (Meeting topic: manila)"15:47
*** ccamacho has quit IRC15:47
tbarrondustins: you are the man15:47
gouthamrthe SDK has a workplan on storyboard, i will add a link to the wiki (if it hasn't been already)15:47
tbarrongouthamr: and that's fine, no spec needed15:47
* dustins gathers items15:47
dustins#link: https://etherpad.openstack.org/p/manila-bug-triage-pad15:48
tbarronlet's get the workplans in place by M1 or spec review time15:48
dustins#link: https://bugs.launchpad.net/manila/+bug/179698615:48
openstackLaunchpad bug 1796986 in python-manilaclient "[doc] No documentation on user messages" [High,Triaged]15:48
dustinsSo this one has already been triaged, we just need some volunteers to work on it15:49
dustinsAnd we should really make sure that no new features go into Manila without the corresponding documentation for how to interact with it15:49
tbarronunfortunately the folks who implemented user messages - ameade and jprovazn - aren't with us15:50
* gouthamr it's so straightforward it doesn't need docs :P15:50
dustinstbarron: Indeed :(15:50
tbarronwell the doc could be quite brief15:50
dustinsSo I need a volunteer for someone to take up the mantle to have a look at this15:50
tbarronshow the workflow for a characteristic error15:50
dustinsAnd tbarron is right, there's not anything particularly difficult about this15:51
tbarrondustins: you can give the bug to me but I disagree with High priority15:51
dustinsjgrosso_: Would be a good opportunity to get a commit into Manila and go through that workflow :)15:51
gouthamrif anyone is inspired, i wrote this for an internal doc team: https://paste.fedoraproject.org/paste/gzbnc5Ztnm82rbR3zQV91A15:52
tbarrondustins: if I take it it will be a bit15:52
dustinstbarron: I can lower priority if you'd like15:52
gouthamromy15:52
jgrosso_ok15:52
tbarronjgrosso_ just got voluntold :)15:52
dustinsI just wanted to call attention to the fact that we have features in our code that have no documentation for how to use them, maybe more of a "medium" thing15:53
gouthamrreplace link: http://paste.openstack.org/show/732438/15:53
dustinsNo one's data is getting destroyed after all :)15:53
jgrosso_:)15:53
dustinstbarron: The wonders of delegation15:53
dustins#action: dustins to work with jgrosso_ to get the documentation in15:54
dustins#link: https://bugs.launchpad.net/manila-ui/+bug/162442515:54
openstackLaunchpad bug 1624425 in manila-ui ""Set as Active" button shown for replicas in transitional states" [Low,New]15:54
dustinsI've got a few UI bugs to air out, so let's start with this one15:54
dustinsAnd yes, most of these are quite old15:55
bswartzWho is working on manila-ui now?15:55
*** ttsiouts has quit IRC15:55
dustinsbswartz: I was hoping you could tell me :)15:55
bswartzIt requires some special skills that we don't all have15:55
dustinsI know vkmc has done some work with it in the past15:55
dustinsBut I wouldn't say she owns it15:56
*** ttsiouts has joined #openstack-meeting-alt15:56
bswartzThat one seems like an easy bug, but it needs someone familiar with the UI15:56
*** macza has joined #openstack-meeting-alt15:56
bswartzOr maybe a pairing of someone with UI experience and someone with replication experience15:56
dustinsAgreed, and it need not require a NetApp backend, as it seems like it effects all replication workflows15:57
dustinsAny volunteers?15:57
tbarrondustins: seems like we need to start by confirming that it's still an issue?15:57
*** cloudrancher has quit IRC15:57
dustinstbarron: Yes, and I called that out in a comment on the bug15:57
tbarrondustins: you need a back end that slow enough replicating to show the issue15:57
tbarron:)15:57
* tbarron is just messing around15:58
gouthamri think this is a low-hanging-fruit, please mark it so in case we have any wayward contributors15:58
dustinsA lot has changed in the last two years, so it's possible that this has just gone away, but I don't think that's the case15:58
dustinsgouthamr: Wilco15:58
* dustins adds "low-hanging-fruit" tag15:58
dustins#link: https://bugs.launchpad.net/manila-ui/+bug/157677615:59
openstackLaunchpad bug 1576776 in manila-ui "Test coverage is too small" [Low,Triaged]15:59
*** cloudrancher has joined #openstack-meeting-alt15:59
dustinstl;dr We want to improve test coverage in Manila UI15:59
dustinsAnd need volunteers for such15:59
gansotime check15:59
* tbarron doesn't like bugs with general topics like that15:59
tbarronlet's follow up in #openstack-manila16:00
tbarronThanks everyone!16:00
dustinsSounds good16:00
tbarron#endmeeting16:00
*** openstack changes topic to "Documentation (Meeting topic: trove)"16:00
openstackMeeting ended Thu Oct 18 16:00:29 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-18-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2018/manila.2018-10-18-15.00.txt16:00
*** e0ne has quit IRC16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2018/manila.2018-10-18-15.00.log.html16:00
*** ttsiouts has quit IRC16:00
*** ganso has left #openstack-meeting-alt16:01
*** jgrosso_ has quit IRC16:02
*** cloudrancher has quit IRC16:05
*** yamamoto has joined #openstack-meeting-alt16:11
*** liuyulong is now known as liuyulong_zzz16:13
*** dklyle has quit IRC16:16
*** dklyle has joined #openstack-meeting-alt16:16
*** Swami has quit IRC16:21
*** macza has quit IRC16:33
*** luizbag has left #openstack-meeting-alt16:36
*** dklyle has quit IRC16:37
*** alysonr_ has quit IRC16:40
*** derekh has quit IRC16:54
*** yamamoto has quit IRC16:56
*** yamamoto has joined #openstack-meeting-alt16:56
*** yamahata has joined #openstack-meeting-alt17:04
*** sambetts is now known as sambetts|afk17:07
*** munimeha1 has quit IRC17:10
*** ircuser-1 has quit IRC17:15
*** rdopiera has quit IRC17:15
*** panda is now known as panda|off17:30
*** dklyle has joined #openstack-meeting-alt17:30
*** yamamoto has quit IRC17:33
*** dklyle has quit IRC17:42
*** diablo_rojo has joined #openstack-meeting-alt17:44
*** betherly has joined #openstack-meeting-alt17:45
*** betherly has quit IRC17:49
*** dklyle has joined #openstack-meeting-alt17:50
*** cezary_zukowski has quit IRC17:50
*** priteau has quit IRC17:52
*** dklyle has quit IRC18:02
*** betherly has joined #openstack-meeting-alt18:05
*** betherly has quit IRC18:09
*** apetrich has quit IRC18:10
*** diablo_rojo has quit IRC18:12
*** diablo_rojo has joined #openstack-meeting-alt18:13
*** yamamoto has joined #openstack-meeting-alt18:14
*** lbragstad has quit IRC18:17
*** dklyle has joined #openstack-meeting-alt18:20
*** apetrich has joined #openstack-meeting-alt18:24
*** betherly has joined #openstack-meeting-alt18:24
*** markstur has quit IRC18:25
*** diablo_rojo has quit IRC18:26
*** dklyle has quit IRC18:29
*** betherly has quit IRC18:29
*** weshay_meeting is now known as weshay18:33
*** caboucha has joined #openstack-meeting-alt18:43
*** diablo_rojo has joined #openstack-meeting-alt18:44
*** betherly has joined #openstack-meeting-alt18:44
*** lbragstad has joined #openstack-meeting-alt18:48
*** betherly has quit IRC18:49
*** panda|off has quit IRC18:59
*** panda has joined #openstack-meeting-alt19:00
*** dklyle has joined #openstack-meeting-alt19:07
*** dklyle has quit IRC19:14
*** lbragstad has quit IRC19:21
*** bhavikdbavishi has quit IRC19:22
*** lbragstad has joined #openstack-meeting-alt19:24
*** tpsilva has joined #openstack-meeting-alt19:33
*** diablo_rojo has quit IRC19:35
*** betherly has joined #openstack-meeting-alt19:44
*** apetrich has quit IRC19:44
*** devananda has quit IRC19:47
*** betherly has quit IRC19:48
*** e0ne has joined #openstack-meeting-alt19:52
*** markstur has joined #openstack-meeting-alt20:03
*** markstur has quit IRC20:04
*** markstur has joined #openstack-meeting-alt20:04
*** e0ne has quit IRC20:05
*** cloudrancher has joined #openstack-meeting-alt20:46
*** betherly has joined #openstack-meeting-alt20:49
*** weshay is now known as weshay_pto20:52
*** betherly has quit IRC20:54
*** dustins has quit IRC20:57
*** erlon__ has quit IRC21:01
*** panda has quit IRC21:08
*** raildo has quit IRC21:09
*** panda has joined #openstack-meeting-alt21:12
*** diablo_rojo has joined #openstack-meeting-alt21:12
*** bnemec is now known as bnemec-bbl21:20
*** dklyle has joined #openstack-meeting-alt21:36
*** diablo_rojo has quit IRC21:42
*** diablo_rojo has joined #openstack-meeting-alt21:44
*** dklyle has quit IRC21:45
*** rcernin has joined #openstack-meeting-alt22:33
*** pbourke has quit IRC22:35
*** pbourke has joined #openstack-meeting-alt22:36
*** betherly has joined #openstack-meeting-alt22:51
*** diablo_rojo has quit IRC22:52
*** ircuser-1 has joined #openstack-meeting-alt22:52
*** betherly has quit IRC22:56
*** tpsilva has quit IRC23:03
*** diablo_rojo has joined #openstack-meeting-alt23:03
*** hongbin has quit IRC23:08
*** betherly has joined #openstack-meeting-alt23:12
*** betherly has quit IRC23:16
*** erlon__ has joined #openstack-meeting-alt23:18
*** betherly has joined #openstack-meeting-alt23:32
*** betherly has quit IRC23:37
*** diablo_rojo has quit IRC23:37
*** bnemec has joined #openstack-meeting-alt23:50
*** bnemec-bbl has quit IRC23:52
*** gyee has quit IRC23:59

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