Thursday, 2018-11-01

*** markvoelker has quit IRC00:01
*** cloudrancher has quit IRC00:09
*** cloudrancher has joined #openstack-meeting-alt00:10
*** markstur has quit IRC00:10
*** slaweq has quit IRC00:15
*** erlon has quit IRC00:30
*** betherly has joined #openstack-meeting-alt00:35
*** betherly has quit IRC00:39
*** erlon has joined #openstack-meeting-alt00:43
*** betherly has joined #openstack-meeting-alt00:56
*** betherly has quit IRC01:01
*** hongbin has joined #openstack-meeting-alt01:24
*** betherly has joined #openstack-meeting-alt01:48
*** betherly has quit IRC01:52
*** erlon has quit IRC01:58
*** markvoelker has joined #openstack-meeting-alt02:03
*** tetsuro has joined #openstack-meeting-alt02:08
*** tetsuro has quit IRC02:11
*** apetrich has quit IRC02:16
*** iyamahat_ has quit IRC02:23
*** yamahata has quit IRC02:24
*** markvoelker has quit IRC02:35
*** Leo_m has quit IRC02:45
*** Leo_m has joined #openstack-meeting-alt02:50
*** tetsuro has joined #openstack-meeting-alt02:54
*** tetsuro has quit IRC02:59
*** tetsuro has joined #openstack-meeting-alt03:00
*** bhavikdbavishi has joined #openstack-meeting-alt03:10
*** dustins has joined #openstack-meeting-alt03:15
*** betherly has joined #openstack-meeting-alt03:21
*** dustins has quit IRC03:25
*** betherly has quit IRC03:26
*** markvoelker has joined #openstack-meeting-alt03:32
*** betherly has joined #openstack-meeting-alt03:53
*** betherly has quit IRC03:57
*** markvoelker has quit IRC04:06
*** yamahata has joined #openstack-meeting-alt04:07
*** iyamahat has joined #openstack-meeting-alt04:07
*** betherly has joined #openstack-meeting-alt04:24
*** betherly has quit IRC04:29
*** hongbin has quit IRC04:37
*** tetsuro has quit IRC04:44
*** alex_xu has quit IRC04:53
*** markvoelker has joined #openstack-meeting-alt05:02
*** betherly has joined #openstack-meeting-alt05:16
*** betherly has quit IRC05:21
*** ircuser-1 has quit IRC05:24
*** markvoelker has quit IRC05:36
*** betherly has joined #openstack-meeting-alt05:37
*** betherly has quit IRC05:42
*** betherly has joined #openstack-meeting-alt05:57
*** betherly has quit IRC06:02
*** markvoelker has joined #openstack-meeting-alt06:33
*** masahito has joined #openstack-meeting-alt06:47
*** masahito has left #openstack-meeting-alt06:47
*** bhavikdbavishi has quit IRC07:02
*** apetrich has joined #openstack-meeting-alt07:03
*** tetsuro has joined #openstack-meeting-alt07:04
*** markvoelker has quit IRC07:05
*** lpetrut has joined #openstack-meeting-alt07:26
*** alexchadin has joined #openstack-meeting-alt07:38
*** slaweq has joined #openstack-meeting-alt07:58
*** bhavikdbavishi has joined #openstack-meeting-alt08:01
*** markvoelker has joined #openstack-meeting-alt08:03
*** bhavikdbavishi has quit IRC08:09
*** bhavikdbavishi has joined #openstack-meeting-alt08:09
*** lpetrut has quit IRC08:12
*** slaweq has quit IRC08:18
*** markvoelker has quit IRC08:36
*** tetsuro has quit IRC08:51
*** tetsuro has joined #openstack-meeting-alt08:53
*** rdopiera has joined #openstack-meeting-alt08:55
*** alexchadin has quit IRC09:00
*** alexchadin has joined #openstack-meeting-alt09:01
*** tetsuro has quit IRC09:09
*** alexchadin has quit IRC09:11
*** derekh has joined #openstack-meeting-alt09:16
*** markvoelker has joined #openstack-meeting-alt09:33
*** PagliaccisCloud has quit IRC09:34
*** PagliaccisCloud has joined #openstack-meeting-alt09:34
*** ttsiouts has joined #openstack-meeting-alt09:36
*** ttsiouts has quit IRC09:42
*** e0ne has joined #openstack-meeting-alt09:43
*** ttsiouts has joined #openstack-meeting-alt09:47
*** lpetrut has joined #openstack-meeting-alt09:49
*** panda|off is now known as panda09:56
*** markvoelker has quit IRC10:07
*** apetrich has quit IRC10:12
*** tssurya has joined #openstack-meeting-alt10:24
*** apetrich has joined #openstack-meeting-alt10:25
*** e0ne has quit IRC10:32
*** e0ne has joined #openstack-meeting-alt10:36
*** jtomasek has quit IRC10:43
*** jtomasek has joined #openstack-meeting-alt10:45
*** dave-mccowan has joined #openstack-meeting-alt10:46
*** markvoelker has joined #openstack-meeting-alt11:04
*** bhavikdbavishi has quit IRC11:16
*** ttsiouts has quit IRC11:30
*** markvoelker has quit IRC11:36
*** bhavikdbavishi has joined #openstack-meeting-alt11:54
*** erlon has joined #openstack-meeting-alt11:57
*** ttsiouts has joined #openstack-meeting-alt12:06
*** pbourke has quit IRC12:09
*** pbourke has joined #openstack-meeting-alt12:10
*** lpetrut has quit IRC12:13
*** raildo has joined #openstack-meeting-alt12:17
*** munimeha1 has joined #openstack-meeting-alt12:47
*** e0ne has quit IRC12:55
*** ttsiouts has quit IRC12:55
*** yamamoto has quit IRC12:56
*** jcoufal has joined #openstack-meeting-alt13:04
*** ttsiouts has joined #openstack-meeting-alt13:04
*** yamamoto has joined #openstack-meeting-alt13:14
*** liuyulong has joined #openstack-meeting-alt13:15
*** belmoreira has joined #openstack-meeting-alt13:17
*** dustins has joined #openstack-meeting-alt13:34
*** e0ne has joined #openstack-meeting-alt13:40
*** cloudrancher has quit IRC13:43
*** cloudrancher has joined #openstack-meeting-alt13:43
*** Leo_m has quit IRC13:44
*** liuyulong has quit IRC13:47
*** AlanClark has joined #openstack-meeting-alt13:48
*** cloudrancher has quit IRC13:54
*** tpsilva has joined #openstack-meeting-alt13:55
*** cloudrancher has joined #openstack-meeting-alt13:55
*** bhavikdbavishi has quit IRC13:58
*** liuyulong_ has joined #openstack-meeting-alt14:03
*** hongbin has joined #openstack-meeting-alt14:05
*** AlanClark has quit IRC14:06
*** AlanClark has joined #openstack-meeting-alt14:07
*** e0ne_ has joined #openstack-meeting-alt14:09
*** e0ne has quit IRC14:10
*** Leo_m has joined #openstack-meeting-alt14:31
*** Leo_m has quit IRC14:31
*** Leo_m has joined #openstack-meeting-alt14:32
*** Swami has joined #openstack-meeting-alt14:52
*** markstur has joined #openstack-meeting-alt14:55
*** zaneb has joined #openstack-meeting-alt14:56
*** ganso has joined #openstack-meeting-alt14:58
tbarron#startmeeting manila15:01
openstackMeeting started Thu Nov  1 15:01:08 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
amitohello15:01
marksturhi15:01
zanebo/15:01
tbarronlet's wait another minute15:02
tbarronping xyang15:02
dustins\o15:02
xyanghi15:02
tbarronping toabctl15:02
gouthamro/15:03
tbarronHi all!15:03
tbarron#topic announcements15:03
*** openstack changes topic to "announcements (Meeting topic: manila)"15:03
tbarronSpec deadline is a week from today.15:04
tbarronWe have specs on the agenda, so 'nuff said for now.15:04
tbarronSummit is the following week.15:04
tbarronI will make an etherpad for our forum session and send it to the dev list.15:05
*** liuyulong_ has quit IRC15:05
tbarronWho here will be at summit?15:05
* tbarron will, vkmc will15:05
amitomost likely won't be there... but I'll know soon.15:05
*** jgrosso has joined #openstack-meeting-alt15:05
tbarronok, ping me if you'll be attending this one please.15:06
amitonp15:06
vkmco/15:06
*** liuyulong has joined #openstack-meeting-alt15:06
tbarronI don't have any other announcements, anyone else?15:06
xyangI won't be there.  I'll be in KubeCon Shanghai in that same week15:06
tbarronxyang: cool, but remember platforms need infra :)15:06
gansoerlon, tpsilva and I will15:07
xyang:)15:07
tbarronganso: cool, the boys from brazil :)15:07
tbarron#topic technical vision15:07
*** openstack changes topic to "technical vision (Meeting topic: manila)"15:07
tbarronWe have zaneb as a special guest today.15:07
tbarronI've been following the proposed tech vision in review15:08
tbarron#link https://review.openstack.org/#/c/592205/15:08
tbarronI personally like the vision and15:08
tbarronthink manila fits unprobematically with it.15:08
tbarronBut we should all take a look.15:08
tbarronzaneb: you're up :)15:09
zanebhi everyone :)15:09
amitohi zaneb15:09
zanebI'm here to listen more than to talk :)15:09
zanebI'd like to hear what y'all think15:09
zanebbecause I'm not an expert on Manila by any means15:10
tbarronme too, have folks had a chance to read over the review?15:10
zanebso do you think this direction is right? is there anything important that we've missed. is there anything there that shouldn't be?15:11
tbarronIMO manila provides part of basic data center mgmt via self-service shares15:11
tbarronIt virtualizes the resources underneath15:11
tbarronIt isolates tenants from one another15:12
tbarronIt provides an API so that programs can use it, not just humans15:12
tbarronIt is not particularly nova-centered since it offers15:12
dustinsI haven't had the chance to look at it (and honestly didn't know there was an ongoing effort to define a vision)15:12
tbarronup storage over a network rather than via a hypervisor15:13
zanebone question I had actually, is does Manila also make it easier to scale granularly (like e.g. Swift does) or do you hit limits in terms of having to pre-allocate the size of the file system (like e.g. Cinder)?15:13
tbarrondustins: /me recommends following the dev list15:13
zanebI think it's still the latter, but I was unsure of how it works in practice15:14
* gouthamr isn't aware of cinder's issue needing pre-allocating size of the file-system15:14
erlonhey15:14
tbarronzaneb: yeah, not sure about the cinder limitation either but15:15
gouthamrzaneb: inherently shared-file-systems are "elastic" - so manila supports expanding and shrinking15:15
tbarronwe are elastic15:15
zanebgouthamr: I mean, the size of a volume in Cinder is fixed. In Swift if you need to store another object, you just do it. In Cinder if the FS is full, you have much more work to do. Not that that's bad, but they're different things15:15
tbarroncloud admins need to track usage and increasee backing store15:15
gouthamror users15:15
tbarronzaneb: a "share" has a fixed size (with some back ends that's just a back end quota, nothing more)15:16
tbarronzaneb: but it can be "extended"15:16
gansozaneb: there is no way to create a share with "undefined", "unlimited" or "indetermined" size, the user has to choose a size and then can increase or decrease it later15:16
zanebok, so it's sorta in-between15:16
tbarronwe've considered "infinite" or "auto-sizing" shares but they've not been implemented yete15:17
tbarronyet15:17
zanebyou have to define a size, unlike Swift, but it's easy to change, unlike Cinder15:17
gouthamryep, cinder doesn't let you shrink a volume15:17
bswartzOn some backends it's easy to change...15:17
gouthamrs/cinder/block devices15:17
amitoalso, increasing or decreasing its size depends on backend capabilities15:18
*** AlanClark has quit IRC15:18
* zaneb is learning a lot today :)15:18
bswartz#TIL15:18
*** apetrich has quit IRC15:18
tbarronthere's nothing stopping a program from selecting a flexible back end (via a share type) for shares, tracking usage, and extendiing as appropriate15:19
*** AlanClark has joined #openstack-meeting-alt15:19
zanebso it may be the case that Manila is also contributing to several of the other design goals as well, not just the basic data center infrastructure15:19
tbarronbut the abstraction sits over some back ends that may not allow this15:20
gouthamr+1 - the point about "arbitrary grouping" makes sense on multiple levels for us15:20
tbarronzaneb: +215:20
gouthamrfor instance ^ :)15:20
tbarronI meant +1 :)15:20
* tbarron wasn't exercising any special powers15:20
gouthamr'ts a good read, will review today and provide feedback15:22
tbarronzaneb: fwiw I agree with rosmaita that quotas are useful even with "central-planning" cloud economics where individual consumers aren't evaluating opportunity costs :)15:22
tbarronbut that's a nit15:22
tbarronAnyone have any deep concerns about the proposed tech vision or manila's fit ?15:23
tbarronzaneb: I'm not hearing any worries so I'll add my +1 as PTL as you requested.15:24
zanebtbarron: thanks! new patch set with responses to comments coming today probably15:24
tbarronIf anyone comes up with issues take them to the review or catch zaneb on #openstack-tc15:25
zaneb++15:25
tbarronzaneb: thanks for joining us today15:25
zanebthanks for your time everyone, looking forward to your comments :)15:25
tbarron#topic spec reviews15:25
*** openstack changes topic to "spec reviews (Meeting topic: manila)"15:25
tbarron#link https://wiki.openstack.org/wiki/Manila/SteinCycle#Other_Work15:26
tbarron^^ That will take you to the right spot even though the topic isn't just right15:26
tbarronAs mentioned earlier, spec deadline is a week from today.15:27
tbarronWe have three outstanding spec reviews at the moment.15:27
tbarronAnd *no* review comments :(15:27
tbarronI'm going to block off some time for these today and tomorrow but15:28
tbarroncan we get more reviewers to sign up for these and give initial feedback before the weekend?15:28
tbarronganso: You may want to do some lobbying/arm-twisting since as15:29
tbarronthings stand now I'd say these are at risk for not making this cycle simply because we15:29
tbarronare limited on review bandwidth.15:29
gansosorry I don't understand the expression "lobbying/arm-twisting"15:29
tbarronganso: if you have to triage, life-boat style, what is your priority?15:30
bswartzganso: he's saying you need to go ask people for reviews15:30
tbarronganso: sorry for the colloquialism, I mean ^^15:30
bswartzThere is no magical review fairy15:30
tbarronganso: in an ideal world there would be sufficient reviewer bandwidth and interest in these features that you wouldn't need to do that, but ...15:31
gansomy priority would be 1) manage/unmanage DHSS=True, 2) Replication DHSS=True and 3) Create share from snapshot in other backends15:31
tbarronganso: so find other people with DHSS=True back ends who care about these features and get them to review and agree on the approach15:31
amitoI can try and review specs this weekend.15:32
tbarronamito: thanks!15:32
tbarronAnything else on this topic today?15:33
*** gyee has joined #openstack-meeting-alt15:33
*** e0ne_ has quit IRC15:34
tbarron#topic planning our work15:34
*** openstack changes topic to "planning our work (Meeting topic: manila)"15:34
tbarron#link https://wiki.openstack.org/wiki/Manila/SteinCycle15:34
*** e0ne has joined #openstack-meeting-alt15:34
tbarrongouthamr: how is it going with running the lvm job in bionic instead of centos?15:35
gouthamrtbarron: pretty good so far, late-breakthrough with the quagga issue i was seeing15:35
tbarronAs a reminder, this is a step in the python3 goal since centos currently doesn't support python315:35
gouthamrtbarron: i want to test those changes on centos and invoke the netapp-ci which is testing this on xenial15:35
gouthamrafter which we should be good15:36
*** apetrich has joined #openstack-meeting-alt15:36
tbarrongouthamr: sounds like good progress15:36
gouthamrI have work to do on the base patch wrt the Grenade job - that's on my plate today - it'd be nice to get these in, and be the first project to stop testing Stein on Xenial :D15:36
tbarronvkmc: gouthamr: what will be the next step on python3 goal after converting the lvm job?15:37
vkmctbarron, porting tempest tests15:37
tbarronvkmc: will we port to zuulv3 as part of that?15:38
*** jgrosso has quit IRC15:38
gouthamrwe also need to replicate these job changes on manila-tempest-plugin (and at some point look at rebuilding the service images)15:39
tbarrongouthamr: ack15:39
gouthamrimho zuulv3 can be a slower transition, unless infra wants us to do it right away15:39
tbarrongouthamr: fine by me15:40
gouthamri haven't heard that they do, we have so much other work to get to :)15:40
tbarronvkmc: gouthamr: you've been keeping15:40
vkmctbarron, yes, but migrating to zuulv3 requires some planning since this will affect third party ci's15:41
tbarron#link https://wiki.openstack.org/wiki/Manila/SteinCycle#Python315:41
vkmcwe need to make it slowly15:41
tbarronpretty up to date, so please keep doing so :)15:41
vkmcwe discussed about this briefly during the dublin ptg, we didn't talk about this during the denver ptg15:41
tbarronand ack on de-coupling this from zuulv315:41
vkmcbut certainly is the next step15:41
vkmcyeah, we need to decouple py3 migration to zuulv3 migration15:42
tbarronI know everybody has been busy with downstream work and concerns lately but I'll mention15:42
tbarronon the Manila CSI subject that we hope to have some15:43
tbarrongood discussions with CERN and OpenStack k8s sig on this subject15:43
tbarronat the Summit15:43
bswartz\o/15:44
tbarronMeanwhile people are using the dynamic external storage provider for manila successfully but15:44
tbarronsome of them have raised an issue when using CephFS back end where15:44
tbarronk8s needs the shares to be mode 775 instead of 75515:45
tbarronbecause the workload running in the conatiner, which sees the share via biind mout from the k8s host15:45
tbarronruns with a high number (non-root) uid but is in root group15:45
bswartzOh yes I remember this discussion15:46
tbarronI have an open PR in the ceph_volume_client (in ceph) for this and a dependent review in manila15:46
bswartzWe need a way for manila to set the mode/owner of the root of the share15:46
tbarronI mention this in case any other back ends have similar issues.15:46
tbarronbswartz: the manila patch right now is short-term and back end specific but15:47
bswartzIt's currently undefined which means it's completely up to the driver15:47
bswartzAnd that's terrible15:47
tbarronwe can look at generalizations too15:47
bswartzSome drivers just set it to 777 to avoid any problems15:47
tbarronI think we have to get a sense of back end capabilities and defaults in this area before we can do a general solution scoped over all back ends15:48
tbarronSo I may send an email on the dev list to inquire.15:48
tbarronok, moving along15:49
bswartzWell I think it's a solvable problem15:49
bswartzThere's no reason a backend couldn't set the mode/owner -- it's just not in the manila API15:49
tbarronAnyone have updates on any of the other planned work?15:49
bswartzThe hard part would be amending the Manila API15:49
tbarronbswartz: agree, that's why we're doing back end specific for cephfs and cephfs/nfs as the first step15:50
tbarronother back ends may want to do something similar15:50
tbarron#topic Bugs15:50
*** openstack changes topic to "Bugs (Meeting topic: manila)"15:50
tbarron#link https://wiki.openstack.org/wiki/Manila/SteinCycle#Bug_Triage15:51
tbarrondustins: got anyting for us today?15:51
dustinstbarron: I do not, unfortunately/fortunately15:51
tbarrondustins: yeah I know you've been pretty busy with downstream concerns ...15:52
dustinsTo put it lightly :P15:52
gansothere is a new bug though, and I have some comments from another bug15:52
dustinsganso: Do tell!15:52
tbarronganso: link?15:52
gansolooking for it just a sec15:52
ganso#link https://bugs.launchpad.net/manila/+bug/179974215:53
openstackLaunchpad bug 1799742 in Manila "Wrong segmentation ID sent to drivers when using multi-segments" [Medium,New]15:53
tbarronsome Rodrigo guy raised this one :)15:53
gansoI found this while testing the network plugins with multiple neutron segments15:53
gansoneutron would allow each subnet to have different VLANs15:54
gansobut the manila plugin code just iterates over the list of segments from the network (not the subnet), the picks the last one, for any subnet15:54
gansos/the picks/then picks15:54
gansoI checked if it an easy fix15:55
tbarronganso: so is the fix straightforward? i.e. do we have the info to know where in the loop to stop instead of just picking the last?15:55
gansoaccording to my approach, it is not15:55
gansobecause the neutron segments API is not supported by our abstraction of neutron client, nor neutron client v2.0 itself15:55
gansoit requires openstacksdk15:56
gansoI glanced at it, and it seems the authentication system is slightly different (uses that yaml file which we wouldn't want to use)15:56
gouthamrganso: https://github.com/openstack/manila/blob/2b40e5618f2c1039bbbbd1a3e31b72e104b5436b/manila/network/neutron/neutron_network_plugin.py#L25815:56
gansogouthamr: L269 is the bug15:57
gouthamrthe note suggests "the lowest segment" - it's unclear what that is, but mkoderer may have known what was going on15:57
tbarronwell using the SDK rather than clients is arguably the right direction anyways ...15:57
gansogouthamr: yea, I don't know what it is supposed to mean15:57
gouthamri know what you're referring to, i'm suggesting that you could have a misconfiguration?15:57
gansogouthamr: I am not sure, it is a good idea to be triaged by someone who understands a lot more about neutron multi-segments than I do15:58
gansotbarron: may I proceed to the next bug?15:58
gouthamryes, reading through the code it looks like only one of the segments can have their "'provider:physical_network'" attr set to the physical network15:58
tbarronganso: maybe "reach out" to mkoderer?15:58
tbarronganso: sure, ++15:59
tbarronbug++15:59
gansotbarron: yea we can try that15:59
gansobug #2 #link https://bugs.launchpad.net/manila/+bug/178605915:59
openstackLaunchpad bug 1786059 in Manila "Cannot Connect to Share Server when Creating Share with Generic Driver (DHSS=True)" [Undecided,Invalid]15:59
tbarronyou have 45 secs15:59
gansofor some reason, a lot of people are hitting that bug15:59
gansoI have discussed it already15:59
gansowe cannot reproduce it in the gate15:59
tbarronright15:59
gansobut we don't know why so many people are hitting that15:59
gansoI'm receiving emails asking for help15:59
bswartzThere is an environmental issue16:00
gouthamri kinda have an inkling why16:00
gansoand I don't know how to help16:00
gouthamr:)16:00
bswartzBut I was never able to track down the root case16:00
tbarronlet's go to #openstack-manila, I think a lot of us are getting these emailis16:00
bswartzcause even16:00
gansoI spent alot of time this and last week helping people debug, and I am out of ideas16:00
tbarronThanks everyone!16:00
tbarron#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Thu Nov  1 16:00:40 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-11-01-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2018/manila.2018-11-01-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2018/manila.2018-11-01-15.01.log.html16:00
*** ganso has left #openstack-meeting-alt16:10
*** belmoreira has quit IRC16:11
*** chhagarw has joined #openstack-meeting-alt16:12
*** ttsiouts has quit IRC16:16
*** ircuser-1 has joined #openstack-meeting-alt16:20
*** dustins has quit IRC16:25
*** e0ne has quit IRC16:26
*** ttsiouts has joined #openstack-meeting-alt16:27
*** slaweq has joined #openstack-meeting-alt16:29
*** Swami has quit IRC16:55
*** belmoreira has joined #openstack-meeting-alt17:02
*** belmoreira has quit IRC17:19
*** belmoreira has joined #openstack-meeting-alt17:20
*** diablo_rojo has joined #openstack-meeting-alt17:22
*** Swami has joined #openstack-meeting-alt17:26
*** slaweq has quit IRC17:27
*** e0ne has joined #openstack-meeting-alt17:31
*** ttsiouts has quit IRC17:38
*** ttsiouts has joined #openstack-meeting-alt17:38
*** liuyulong has quit IRC17:39
*** ttsiouts has quit IRC17:43
*** e0ne has quit IRC17:47
*** yamamoto has quit IRC17:49
*** e0ne has joined #openstack-meeting-alt17:59
*** derekh has quit IRC18:00
*** e0ne has quit IRC18:02
*** iyamahat has quit IRC18:05
*** e0ne has joined #openstack-meeting-alt18:05
*** yamahata has quit IRC18:05
*** e0ne has quit IRC18:07
*** yamamoto has joined #openstack-meeting-alt18:17
*** yamamoto has quit IRC18:17
*** iyamahat has joined #openstack-meeting-alt18:19
*** AlanClark has quit IRC18:27
*** jcoufal has quit IRC18:28
*** jcoufal has joined #openstack-meeting-alt18:28
*** tssurya has quit IRC18:30
*** jcoufal has quit IRC18:32
*** jcoufal has joined #openstack-meeting-alt18:33
*** jcoufal has quit IRC18:36
*** jcoufal has joined #openstack-meeting-alt18:36
*** yamahata has joined #openstack-meeting-alt18:38
*** diablo_rojo has quit IRC18:47
*** diablo_rojo has joined #openstack-meeting-alt18:48
*** belmoreira has quit IRC18:48
*** chhagarw has quit IRC18:51
*** yamamoto has joined #openstack-meeting-alt18:53
*** apetrich has quit IRC18:56
*** diablo_rojo has quit IRC18:57
*** diablo_rojo has joined #openstack-meeting-alt18:59
*** yamamoto has quit IRC19:00
*** apetrich has joined #openstack-meeting-alt19:08
*** panda is now known as panda|off19:20
*** diablo_rojo has quit IRC19:31
*** belmoreira has joined #openstack-meeting-alt19:32
*** diablo_rojo has joined #openstack-meeting-alt19:33
*** dustins has joined #openstack-meeting-alt20:05
*** dustins has quit IRC20:06
*** dustins has joined #openstack-meeting-alt20:06
*** dustins has quit IRC20:07
*** dustins has joined #openstack-meeting-alt20:08
*** e0ne has joined #openstack-meeting-alt20:11
*** belmoreira has quit IRC20:12
*** e0ne has quit IRC20:28
*** dave-mccowan has quit IRC20:32
*** slaweq has joined #openstack-meeting-alt20:50
*** rdopiera has quit IRC20:50
*** erlon has quit IRC21:05
*** raildo has quit IRC21:25
*** hongbin has quit IRC21:30
*** dustins has quit IRC21:31
*** iyamahat has quit IRC21:33
*** slaweq has quit IRC21:36
*** iyamahat has joined #openstack-meeting-alt21:39
*** jcoufal has quit IRC22:02
*** Leo_m has quit IRC22:36
*** yamamoto has joined #openstack-meeting-alt22:57
*** yamamoto has quit IRC23:02
*** tpsilva has quit IRC23:04
*** Swami has quit IRC23:53
*** gyee has quit IRC23:58

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