Thursday, 2017-06-22

*** jmlowe has quit IRC00:14
*** jmlowe has joined #openstack-manila00:15
openstackgerritBen Swartzlander proposed openstack/manila master: Add NFSLocalHelper  https://review.openstack.org/47623900:23
bswartzzhongjun: https://review.openstack.org/#/c/444479/00:43
*** tuanluong has joined #openstack-manila00:50
*** kaisers__ has joined #openstack-manila01:28
*** kaisers_ has quit IRC01:31
*** chlong has joined #openstack-manila01:44
*** gregsfortytwo has quit IRC01:47
openstackgerritzhongjun proposed openstack/manila master: Use parenthesis instead of backslashes in tempest folder  https://review.openstack.org/47602701:50
openstackgerritqtlu proposed openstack/manila master: Add support for Guru Meditation Reports for manila  https://review.openstack.org/44468802:00
*** sapcc-bot1 has joined #openstack-manila02:00
*** david_ has quit IRC02:00
*** sapcc-bot has quit IRC02:00
openstackgerritqtlu proposed openstack/manila master: Add support for Guru Meditation Reports for manila  https://review.openstack.org/44468802:03
*** chlong has quit IRC02:04
openstackgerritVu Cong Tuan proposed openstack/manila master: Replace the usage of 'manager' with 'os_primary'  https://review.openstack.org/47601502:27
*** chlong has joined #openstack-manila02:36
openstackgerritzhongjun proposed openstack/manila master: Use parenthesis instead of backslashes in tempest folder  https://review.openstack.org/47602702:49
zhongjunbswartz: Thanks a lot,  I added some comments in this patch, please take a look03:06
*** gouthamr has quit IRC03:39
zhongjungouthamr: Hi,  It looks like we are only doing versioning in the shell or in the client when we add a new input field in this patch(https://review.openstack.org/#/c/468277/9/manilaclient/v2/shell.py) .   Sometimes we're doing versioning in both the shell and in the client, because  we need to display different things, and it could not work in the client. such as :03:45
zhongjunhttps://github.com/openstack/python-manilaclient/blob/master/manilaclient/v2/shell.py#L116903:45
*** kaisers__ has quit IRC03:52
*** chlong has quit IRC04:02
*** chlong has joined #openstack-manila04:15
*** arnewiebalck_ has joined #openstack-manila04:16
*** kaisers_ has joined #openstack-manila04:52
*** kaisers_ has quit IRC05:24
*** jprovazn has joined #openstack-manila05:28
*** dsariel has quit IRC05:49
*** lpetrut has joined #openstack-manila06:03
*** kaisers_ has joined #openstack-manila06:20
*** dsariel has joined #openstack-manila06:36
*** kaisers_ has quit IRC06:36
*** pcaruana has joined #openstack-manila07:05
*** lpetrut_ has joined #openstack-manila07:11
*** lpetrut has quit IRC07:13
openstackgerritzhongjun proposed openstack/manila master: Add export-location filter in share and share instance list API  https://review.openstack.org/46171207:19
*** kaisers_ has joined #openstack-manila07:34
*** a-pugachev has joined #openstack-manila07:44
openstackgerritOpenStack Proposal Bot proposed openstack/manila-ui master: Imported Translations from Zanata  https://review.openstack.org/47639708:02
*** sapcc-bot1 has quit IRC08:03
*** sapcc-bot has joined #openstack-manila08:03
*** david_ has joined #openstack-manila08:03
*** mkoderer_ has joined #openstack-manila08:03
*** seife_ has joined #openstack-manila08:03
*** tpatzig_ has joined #openstack-manila08:03
*** carthaca_ has joined #openstack-manila08:03
*** dgonzalez_ has joined #openstack-manila08:03
*** dgonzalez_ has quit IRC08:05
*** carthaca_ has quit IRC08:05
*** seife_ has quit IRC08:05
*** tpatzig_ has quit IRC08:05
*** mkoderer_ has quit IRC08:05
*** david_ has quit IRC08:05
*** kaisers_ has quit IRC08:07
*** sapcc-bot has quit IRC08:15
*** sapcc-bot2 has joined #openstack-manila08:15
*** dgonzalez_ has joined #openstack-manila08:16
*** david_ has joined #openstack-manila08:16
*** carthaca_ has joined #openstack-manila08:16
*** tpatzig_ has joined #openstack-manila08:16
*** seife_ has joined #openstack-manila08:16
*** mkoderer_ has joined #openstack-manila08:16
*** carthaca_ has quit IRC08:17
*** seife_ has quit IRC08:17
*** tpatzig_ has quit IRC08:17
*** dgonzalez_ has quit IRC08:17
*** david_ has quit IRC08:17
*** mkoderer_ has quit IRC08:18
openstackgerritMerged openstack/manila master: Retry backend initialization  https://review.openstack.org/46420508:29
*** tpatzig_ has joined #openstack-manila08:30
*** dgonzalez_ has joined #openstack-manila08:30
*** carthaca_ has joined #openstack-manila08:30
*** mkoderer_ has joined #openstack-manila08:30
*** seife_ has joined #openstack-manila08:30
*** david_ has joined #openstack-manila08:30
*** tpatzig_ has quit IRC08:32
*** dgonzalez_ has quit IRC08:32
*** carthaca_ has quit IRC08:32
*** mkoderer_ has quit IRC08:32
*** seife_ has quit IRC08:32
*** david_ has quit IRC08:32
*** dmk0202 has joined #openstack-manila08:40
*** kaisers_ has joined #openstack-manila09:04
*** kaisers_ has quit IRC09:22
*** Administrator__ has joined #openstack-manila09:37
*** Administrator_ has quit IRC09:40
*** dmk0202 has quit IRC09:40
openstackgerritzhongjun proposed openstack/manila master: Add export-location filter in share and share instance list API  https://review.openstack.org/46171210:03
*** kaisers_ has joined #openstack-manila10:19
zhongjunvponomaryov: ping10:55
*** ganso has joined #openstack-manila11:02
openstackgerritzhongjun proposed openstack/manila master: Add export-location filter in share and share instance list API  https://review.openstack.org/46171211:20
openstackgerritHelen Walsh proposed openstack/manila master: VMAX VNX Manila - Refactor VMAX and VNX to use common code  https://review.openstack.org/46310611:22
*** kaisers_ has quit IRC11:22
openstackgerritzhongjun proposed openstack/manila master: Enable IPv6 in manila(network plugins and drivers)  https://review.openstack.org/40677611:24
openstackgerritHelen Walsh proposed openstack/manila master: VMAX VNX Manila - Refactor VMAX and VNX to use common code  https://review.openstack.org/46310611:25
*** arnewiebalck_ has quit IRC11:27
openstackgerritMerged openstack/manila master: Replace the usage of 'manager' with 'os_primary'  https://review.openstack.org/47601511:35
*** arnewiebalck_ has joined #openstack-manila11:39
vponomaryovbswartz, tbarron: hello, you may be interested in following feature -> https://blueprints.launchpad.net/manila/+spec/generic-driver-boot-vm-from-volume11:54
vponomaryovzhongjun: pong11:54
tbarronvponomaryov: that may be useful as part of service VM HA solution11:58
tbarronvponomaryov: besides your use case11:58
*** dsariel has quit IRC11:58
vponomaryovtbarron: use case I am aware about is to be able to migrate VM while node is going down for maintenance11:58
tbarronvponomaryov: if the hypervisor for a service VM dies then it would be good to "nova evactuate" the SVM to another hypervisor11:59
tbarronvponomaryov: that requires shared backing store for the vm, or persistent shared volume11:59
tbarronthat the vm boots from11:59
vponomaryovtbarron: so, you are interested in it, right?12:00
tbarronvponomaryov: persistent backing store for vm image via ceph in /var/lib/libvirt/images is good for some but cinder volume would be good for those that don't use ceph that way12:00
tbarronvponomaryov: yes12:00
vponomaryovtbarron: good to know, ty12:00
*** tuanluong has quit IRC12:06
zhongjunvponomaryov: Why we just remove some invalid filters for non-admin https://github.com/openstack/manila/blob/master/manila/api/common.py#L30912:06
*** rraja has joined #openstack-manila12:08
vponomaryovzhongjun: I don't have strict opinion here. We inherited it from Cinder12:08
zhongjunvponomaryov: oh,  I think we could do the same thing for admin and non-admin in our code12:11
zhongjunvponomaryov: https://review.openstack.org/#/c/461712/29/manila/api/v2/shares.py@434   Thanks for your review,   As we did it before, we just pop the parameter in old API version when we add a new parameter in API.  such as: we add  'is_public' in manage API.   Do we really need to raise BadRequest in old API?12:15
zhongjunvponomaryov: such as: https://github.com/openstack/manila/blob/master/manila/api/v2/shares.py#L39912:16
zhongjunvponomaryov: Do you have strict opinion here?12:17
*** kaisers_ has joined #openstack-manila12:18
zhongjunvponomaryov: such as: https://github.com/openstack/manila/blob/master/manila/api/v2/shares.py#L18712:20
vponomaryovzhongjun: about this, my opinion is at https://review.openstack.org/#/c/461712/29/manila/api/v2/shares.py@434 removing arg and returning some data you make user think that his parameter was applied, but it is not indeed12:20
*** gcb has joined #openstack-manila12:20
vponomaryovzhongjun: and I consider it a bug12:21
vponomaryovzhongjun: no matter how many times it was done the same way before12:21
zhongjunvponomaryov: If it is a bug, it looks like we need to fix it in many places12:22
openstackgerritMaurice Schreiber proposed openstack/manila master: Add ou to security service  https://review.openstack.org/47215412:24
*** chlong has quit IRC12:26
*** rpittau__ is now known as rpittau12:31
*** eharney has quit IRC12:33
*** kaisers_ has quit IRC12:39
openstackgerritzhongjun proposed openstack/manila master: Enable IPv6 in manila(network plugins and drivers)  https://review.openstack.org/40677612:39
*** cknight has joined #openstack-manila12:43
*** dsariel has joined #openstack-manila12:44
*** dustins has joined #openstack-manila13:15
*** jmlowe has quit IRC13:16
*** eharney has joined #openstack-manila13:18
bswartzvponomaryov: that does look like an interesting feature13:19
bswartzvponomaryov: do we really need a stateful root volume though? the alternative is to keep all state in the Manila DB like we do today13:19
*** catintheroof has joined #openstack-manila13:20
*** xyang1 has joined #openstack-manila13:26
*** gouthamr has joined #openstack-manila13:34
*** dsariel has quit IRC13:36
*** kaisers_ has joined #openstack-manila13:37
*** chlong has joined #openstack-manila13:39
openstackgerritHelen Walsh proposed openstack/manila master: VMAX VNX Manila - Refactor VMAX and VNX to use common code  https://review.openstack.org/46310613:40
tbarronbswartz: I was thinking a stateful root volume would be handy for migrating (or nova "evacuating") service VMs13:44
tbarronbswartz: stateful volume will at least in theory work for this even if the cloud deployer doesn't back /var/lib/libvirt/images with shared storage like nfs or rbd images13:45
*** gouthamr has quit IRC13:47
openstackgerritMerged openstack/manila-ui master: Imported Translations from Zanata  https://review.openstack.org/47639713:52
*** gouthamr has joined #openstack-manila13:52
bswartztbarron: doesn't nova migration take care of state in "ephemeral" root volumes for you?14:04
tbarronbswartz: I don't think so, I think you have to set up shared storage for the VM images or boot from cinder volume14:05
bswartztbarron: that's interesting14:07
bswartzhooray for boot-from-volume14:07
bswartztbarron: does nova actually understand the concept of shared "ephemeral" storage in some explicit way?14:08
* smcginnis laughs14:08
bswartzsmcginnis: ^ do you know the answer to this?14:09
smcginnis:)14:09
smcginnisbswartz: I believe the answer is no.14:09
tbarronbswartz: my impression is that it just migrates the VM (or "evacuates" it) and that if there is shared backing store14:09
bswartzif not, then how could nova take advantage of it during a migration?14:09
*** lpetrut_ has quit IRC14:09
tbarronwhen the VM comes up on the other side the kept state is available14:10
bswartzdoes it just rely on file name uniqueness, and look if the file is there, and if so, assumes that it's shared?14:10
tbarronin the case of an "evacuate" at least14:10
tbarronit has to start the VM up on the new hypervisor, right?14:11
bswartzAIUI, there's a period of time where the VM exists in both places14:11
tbarronbswartz: I'm thinking more of the "evacuate" case, where the source hypervisor has failed14:12
bswartzit's not like star trek teleportation -- it's more like when you "mv" a file across filesystems -- it's really a "cp" followed by a "rm"14:12
bswartzoh14:13
tbarronbswartz: "instance" HA case14:13
bswartzyou're talking about resurrection of dead VMs?14:13
tbarronbswartz: yes, resurrect would have been a better word than "evacuate"14:14
tbarronnova "evacuates" the victims after they've already been killed once14:14
bswartzor reincarnation may be the more apt analogy, since it will live in a new body14:14
tbarronin traditional christian and jewish theologies resurrected people had some kind of body14:14
tbarronpost-Descartes that idea tended to go away14:15
tbarronbut that's an aside14:15
bswartzevacuate is a term I would use _before_ the hypervisor has died -- when you plan to bring it down for maintenance and you're relocating the still-living VMs14:15
tbarronbswartz: I agree, but the command is called "nova evacuate" - go figure14:15
bswartzI'm only familiar with the Hindu/Buddhist notions of resurrection14:15
bswartzs/resurrection/reincarnation/14:16
tbarronwhere the goal is to quit getting resurrected because it's the same damn thing over and over again14:16
tbarrons/resurrected/reincarnated/14:16
tbarronkinda like OpenStack discusssions14:17
bswartzROFL14:17
bswartzokay so back to something relevant -- how does this notion of evacuation/VM reincarnation apply to manila?14:17
tbarronbswartz: I'm interested in eliminating SPOF in data path when using service VMs14:18
bswartzso are you concerned about the ability to move a living service VM or what to do about dead service VMs?14:18
tbarronso resurrecting a VM on another hypervisor when the original node fails is part of the solution14:18
tbarronbswartz: more the second14:18
tbarronthe problem is hard14:18
tbarronperhaps the simplest place to start is with a physical failure of a node hosting a service VM14:19
bswartzI disagree -- although I admin not having thought deeply about this topic14:19
bswartzadmit14:19
bswartzMy intuition is that all of the state to reincarnate the service VM must live in the manila DB14:19
bswartztherefore there's no value in preserving the root volume of the service image14:20
tbarronwe need to detect that automatically, fence the host (in case it's not really gone but isn't reachable); and "evacuate" to a new host14:20
tbarronand we need a way to set that up with installer tools14:20
tbarronor have manila driver set it up14:20
bswartzoh god you have to consider split brain problems here14:21
tbarronbswartz: you raise another interesting point though; do we have to rely on nova for the re-incarnation-with-state14:21
tbarronin some ways the last part (boot up on new hypervisor with state) may be the easiest part14:21
tbarronbswartz: but your point needs to be understood anyways, if with a manila SVM DB state is sufficient and one doesn't need14:22
*** dsariel has joined #openstack-manila14:22
bswartzI has assumed the HA scheme was going to look more like an active-active scheme where you had 2 running service images that were in contact with eachother, such that either one could die without loss of data or availability to the client14:22
tbarronshared state for the SVM itself outside the DB, that's worth understanding14:22
bswartzin the case I described, the more interesting question is what to do when your active node count drops from 2 to 114:23
tbarronbswartz: I am playing with that idea too, but that requires a VIP that migrates14:23
bswartzwhen your active node count drops from 1 to 0, then the obvious thing to do is to build a new one from scratch, using the Manila DB state to configure the new service image14:24
tbarronbswartz: in my case I want ganesha in the service VMs and ganesha won't run active-active yet14:25
bswartzif there's anything in that service image which isn't persisted in the manila DB, then I think we have a problem14:25
bswartzwhat do you mean by "yet"?14:25
bswartzis it a feature under active development? planned for the future? works today but with limitations?14:26
tbarronbswartz: but even if it did, you want to keep the export location from the dead service VM still working14:26
tbarronbswartz: I repeat a hand wave :)  don't think it's being actively developed14:26
bswartzthe point of multiple export locations combined with pNFS is that it doesn't matter if one of the export locations is down -- you can just use another14:27
tbarronbswartz: so using one SVM and evactuating/migrating/reincarnating it is attractive14:27
tbarronbswartz: which one did the user VM put in its fstab?14:28
bswartzwell I agree if neither nfs-kernel-server or ganesha-nfs has proper pNFS support, then you're stuck with some kind of active/passive scheme14:28
tbarronbswartz: it *could* just use another, but how would it know to do so?14:28
tbarronbswartz: dumb question, does pNFS fix that issue from the user VM/client side?14:29
bswartztbarron: it does after the mount succeeds14:29
bswartzyou're correct that the node that happens to be down is the IP in your fstab then you have a problem14:30
bswartzI suspect this is why netapp does IP takeover for NFS14:30
tbarronbswartz: ^^14:30
tbarronbswartz: yeah, that's what I figured re. NetApp too14:30
bswartzdoes nova have a facility for IP takeover?14:30
bswartzcould you grab the neutron port and reassign it to a different nova VM?14:31
tbarronbswartz: evacuate moves the VM to new hypervisor and it comes up with the same IPs14:31
bswartzoh I see where you're going14:31
tbarronbswartz: I don't *know* how well this interacts with neutron though, am researching14:31
tbarronI think it's supposed to work and there may be some bugs14:31
bswartzthis isn't even active/passive, this is just automatically restarting14:32
tbarronbswartz: right, I was mixing topics14:32
bswartzokay let me consider that scenario14:32
tbarronbswartz: I'm exploring several fronts.14:32
tbarronoriginal subject was migration/evacuation/reincarnation of a single service VM14:33
*** jmlowe has joined #openstack-manila14:33
tbarronto a new node/hypervisor14:33
bswartzso the theory is that even when the hypervisor is gone, nova remembers the old VM and its neutron ports etc14:33
tbarrondoesn't matter if it's ganesha or generic or whatever14:33
bswartzand it's easier to ask nova to just bring the same old instance up somewhere else than it is to create a new instance from scratch using the same image ID and neutron ports14:33
tbarronyeah, it's a theory/conjecture to explore14:34
bswartzand the main challenge in that case is what to do about the root volume, because it's most likely gone in the ephemeral case, but still available in the cinder volume case14:34
tbarronit's what people who are working on "instance HA" for "pet" VMs are looking at14:34
bswartzin the ephemeral case, you could in theory reconstruct the whole service VM after it booted up from the image with a clean state14:35
tbarronwell, that's a challenge (others are detection, fencing, etc. but we'll wave hands on those for the moment since they are there whichever approach for re-gaining state is taken)14:35
bswartzthe only state that would need restoring would be all of the shares and their access rules14:35
tbarronyeah, there's the manila state and the neutron/port state.14:37
bswartzthe ephemeral case seems cleaner to me because you have one source of truth14:37
tbarronso you are arguing atm for using ensure-shares to restore the shares, access-rules, and exports ...14:38
bswartztbarron: honestly I'm not sure what's required on the manila driver side14:41
bswartzbut it strikes me that we should be able to solve this problem without resorting to boot from volume for service images14:42
bswartzand it feel intuitively like the more robust soluition14:42
bswartzin the end it might be more work if we have to add more driver interfaces14:43
bswartzI'd need to think about what the manila side of the solution would look like -- who is watching for heartbeats and how are we pulling the trigger on a reincarnation process14:44
tbarronbswartz: I do think there are multiple approaches for the manila state and wasn't looking at boot-from-volume (or shared backing store for libvirt images) from thinking about that issue per se14:44
tbarronbswartz: it was more looking at SVM HA in the context of current approaches in OpenStack for "instance HA"14:45
tbarronbswartz: and wondering if that could/should be leveraged14:45
tbarronbswartz: which other projects than manila have SVMs that are currently SPOFs for data path (or other critical service path)?14:46
*** markstur has joined #openstack-manila14:52
bswartzwe should be clear that it's only certain drivers that suffer from this limitation14:59
bswartzmanila is designed to be out of the data path14:59
tbarronbswartz: right, but open source drivers that use SVMs have this issue15:00
bswartztbarron: the same could be true of any driver in any project that leveraged nova15:01
bswartzjust saying that drivers are a special case15:01
tbarronany project that uses OpenStack VMs, or OpenStack containers to build an open source "appliance" that delivers the core goods15:02
*** MVenesio has joined #openstack-manila15:08
*** sapcc-bot2 has quit IRC15:10
*** sapcc-bot has joined #openstack-manila15:10
*** eharney_ has joined #openstack-manila15:17
*** eharney has quit IRC15:18
*** kaisers_ has quit IRC15:19
*** gregsfortytwo has joined #openstack-manila15:22
*** cknight has quit IRC15:25
*** eharney_ has quit IRC15:30
*** rraja has quit IRC15:31
*** eharney has joined #openstack-manila15:34
*** jmlowe_ has joined #openstack-manila15:36
*** jmlowe has quit IRC15:38
*** jprovazn has quit IRC15:38
*** pcaruana has quit IRC15:42
openstackgerritMerged openstack/manila master: Use parenthesis instead of backslashes in tempest folder  https://review.openstack.org/47602715:48
tbarron^^ such projects use VMs (or other kinds of compute) as stateful "pets" and face a challenge of what to do if the host for the pet dies15:55
* tbarron ignores more subtle failures at the moment15:56
tbarronbswartz: I'm going to get lunch but just followed up with another remark, I had stopped so as not to interrupt the communnity meeting15:57
openstackgerritBen Swartzlander proposed openstack/manila master: Add NFSLocalHelper  https://review.openstack.org/47623916:01
bswartztbarron: I don't disagree -- just pointing out that manila is not unique in this regard16:02
bswartzI'm sensitive to suggestions that manila is in the data path16:02
bswartzdrivers may or may not cause other openstack components to be in the data path16:03
bswartzbut of course drivers can do practically *anything*16:03
tbarronbswartz: ack16:05
tbarronbswartz: ignoring the manila data service manila itself is not in the data path16:06
tbarronbswartz: but some of its drivers rely on SVMs and the like which are in the data path16:08
tbarronbswartz: and which may be a SPOF16:09
tbarronbswartz: as long as it is understood that those drivers are for reference/research purposes, cool16:10
vponomaryovtbarron: https://www.openstack.org/assets/survey/April2017SurveyReport.pdf page 5916:15
*** cknight has joined #openstack-manila16:15
*** kaisers_ has joined #openstack-manila16:16
vponomaryovtbarron: so, generic driver definitely not "for reference/research purposes only"16:18
tbarronvponomaryov: yeah, one fifth are using it and it introduces a SPOF in the data plane :(16:22
tbarronvponomaryov: so it is a problem worth solving16:22
*** cknight has left #openstack-manila16:22
tbarronvponomaryov: cephfs driver doesn't have this issue but ganesha in front of cephfs will if we put it in a SVM16:22
tbarronand zfs on linux has it in that circumstance16:23
tbarroni'd like a robust software only open source solution16:23
vponomaryovtbarron: also, if you look at page 51, you will see, that the majority is openvswitch - the only L2 element supported and tested with generic driver16:25
vponomaryovplus multitenancy that generic driver has16:25
vponomaryovall that in summary means that this driver covers really big field of use cases16:26
tbarronvponomaryov: agree16:26
tbarronvponomaryov: so lots of use cases but not robust enough for production as long as it introduces a SPoF in data plane16:28
tbarronvponomaryov: cloud deployer might not care but supporting a distro I have to care16:29
vponomaryovtbarron: it is question to cinder's backend16:29
vponomaryovtbarron: losing Vm is only downtime, but not losing data16:30
tbarronvponomaryov: even if cinder backend is completely robust you still have SPoF b/c SVM is a single unprotected nova instance16:30
tbarronvponomaryov: oh, I agree data loss is more serious than downtime16:31
tbarronvponomaryov: but downtime on data path is also a sufficiently big issue16:31
tbarronvponomaryov: and we have open source solutions for the data loss/integrity issue16:32
*** kaisers_ has quit IRC16:46
*** a-pugachev has quit IRC16:49
openstackgerritBen Swartzlander proposed openstack/manila master: Add NFSLocalHelper  https://review.openstack.org/47623917:25
bswartzafter I tackle LVM I plan to make the generic driver great again17:26
*** kaisers_ has joined #openstack-manila17:42
*** arnewiebalck_ has quit IRC17:47
openstackgerritVictoria Martinez de la Cruz proposed openstack/manila master: Add create/delete/extend/shrink share notifications  https://review.openstack.org/46658617:59
*** eharney has quit IRC18:25
*** kaisers_ has quit IRC18:25
*** sapcc-bot has quit IRC18:29
*** sapcc-bot has joined #openstack-manila18:29
*** jprovazn has joined #openstack-manila18:42
*** arnewiebalck_ has joined #openstack-manila18:55
*** kaisers_ has joined #openstack-manila18:56
*** eharney has joined #openstack-manila18:57
*** jprovazn has quit IRC19:38
*** bswartz has quit IRC19:38
*** MVenesio has quit IRC20:08
*** a-pugachev has joined #openstack-manila20:16
*** eharney has quit IRC20:18
*** kaisers_ has quit IRC20:39
*** kaisers_ has joined #openstack-manila20:39
*** jmlowe_ has quit IRC20:41
*** arnewiebalck_ has quit IRC20:58
*** arnewiebalck_ has joined #openstack-manila20:59
*** arnewiebalck_ has quit IRC21:00
*** dmellado has quit IRC21:00
*** dmellado has joined #openstack-manila21:03
*** dustins has quit IRC21:14
*** catintheroof has quit IRC21:18
*** a-pugachev has quit IRC21:19
*** kaisers_ has quit IRC21:36
*** kaisers_ has joined #openstack-manila21:41
*** kaisers_ has quit IRC21:47
*** gouthamr has quit IRC21:55
*** xyang1 has quit IRC21:56
*** chlong has quit IRC21:57
*** kaisers_ has joined #openstack-manila22:07
*** gouthamr has joined #openstack-manila22:16
*** ganso has quit IRC22:29
*** dmellado has quit IRC22:33
*** dmellado has joined #openstack-manila22:37
*** dmellado has quit IRC23:03
*** dmellado has joined #openstack-manila23:06
*** chlong has joined #openstack-manila23:10
*** dmellado has quit IRC23:15
*** dmellado has joined #openstack-manila23:18
*** bswartz has joined #openstack-manila23:25
*** dmellado has quit IRC23:31
*** winston-d_ has joined #openstack-manila23:44
*** dmellado has joined #openstack-manila23:51
*** dmellado has quit IRC23:55

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