Tuesday, 2016-03-22

*** yangyapeng has quit IRC00:05
*** a_ta has joined #openstack-manila00:17
*** a_ta has quit IRC00:23
*** furlongm has quit IRC00:55
*** furlongm_ has joined #openstack-manila00:55
*** mtanino has quit IRC01:10
openstackgerritdaiki kato proposed openstack/python-manilaclient: Fix typos  https://review.openstack.org/29558501:20
*** baojg has joined #openstack-manila01:43
*** akshai has quit IRC01:44
*** jasonsb has joined #openstack-manila02:15
*** houming has joined #openstack-manila02:24
*** gouthamr has quit IRC02:44
*** a_ta has joined #openstack-manila02:46
*** akshai has joined #openstack-manila02:49
*** esker has quit IRC02:50
*** a_ta has quit IRC02:50
*** akshai has quit IRC02:53
*** akshai has joined #openstack-manila03:10
*** akshai has quit IRC04:06
*** chlong|wfh has quit IRC04:12
*** chlong has joined #openstack-manila04:25
*** furlongm_ is now known as furlongm04:36
*** a_ta has joined #openstack-manila04:51
*** furlongm has quit IRC04:54
*** a_ta has quit IRC04:56
*** furlongm has joined #openstack-manila05:11
*** houming has quit IRC05:12
*** houming has joined #openstack-manila05:27
*** houming has quit IRC05:36
*** houming has joined #openstack-manila05:42
*** baojg has quit IRC05:56
*** baojg has joined #openstack-manila05:57
*** rraja has joined #openstack-manila06:02
*** sgotliv has joined #openstack-manila06:08
openstackgerritDevin proposed openstack/manila: [Doc] Update quick start guide from Kilo release to Liberty release.  https://review.openstack.org/29563706:23
*** nkrinner has joined #openstack-manila06:29
openstackgerritRamana Raja proposed openstack/manila: Doc fixes for CephFS native driver  https://review.openstack.org/29544806:31
*** yangyapeng has joined #openstack-manila07:15
*** sgotliv has quit IRC07:20
mkoderer__vponomaryov: ping07:29
mkoderer__vponomaryov: I might don't understand this "admin export location" thing. How does it know that it must use NeutronSingleNetworkPlugin if NeutronNetworkPlugin is used?07:39
mkoderer__I don't find any pointer from NeutronNetworkPlugin to NeutronSingleNetworkPlugin or vice versa07:40
mkoderer__ahh it's by setting admin_network_config_group right?07:41
*** permalac has quit IRC08:33
*** openstackgerrit has quit IRC08:33
*** openstackgerrit has joined #openstack-manila08:34
*** pcaruana has joined #openstack-manila08:40
*** sgotliv has joined #openstack-manila08:49
*** a_ta has joined #openstack-manila08:53
*** a_ta has quit IRC08:58
*** lpetrut has joined #openstack-manila09:16
*** lpetrut has quit IRC09:21
openstackgerritMarc Koderer proposed openstack/manila: Add neutron driver for binding  https://review.openstack.org/28349409:23
*** yangyapeng has quit IRC10:04
*** tpsilva has joined #openstack-manila10:13
*** lpetrut has joined #openstack-manila10:16
*** lpetrut has quit IRC10:17
*** lpetrut has joined #openstack-manila10:17
openstackgerritMarc Koderer proposed openstack/manila: Add neutron driver for binding  https://review.openstack.org/28349410:30
vponomaryovmkoderer__: yes, by setting admin_network_config_group10:48
vponomaryovmkoderer__: and I strongly recommend you to enable it for your test lab10:49
vponomaryovmkoderer__: As I understand you have possibility to run NetApp driver, so, it already supports admin network10:50
vponomaryovmkoderer__: or you can test them one-by-one enabling for main network interface10:58
*** sgotliv has quit IRC11:37
*** baojg has quit IRC11:41
*** dencaval has joined #openstack-manila11:42
*** houming has quit IRC11:44
*** a_ta has joined #openstack-manila11:46
*** a_ta has quit IRC11:51
*** sgotliv has joined #openstack-manila11:51
*** yangyapeng has joined #openstack-manila11:59
mkoderervponomaryov: +112:07
*** alyson_ has joined #openstack-manila12:10
*** a_ta has joined #openstack-manila12:17
*** a_ta has quit IRC12:21
gansobswartz: ping12:27
*** mtanino has joined #openstack-manila12:30
*** sgotliv has quit IRC12:36
bswartzganso: pong12:47
gansobswartz: Good morning Ben12:47
bswartzmornin'12:47
gansobswartz: I would like to talk about your topic title "Data copy service RPC design"12:47
bswartzoh yes12:47
bswartzthat's for austin tho12:48
bswartzI want all of us to spend more time focused on migration12:48
bswartzand places where migration overlaps with over features12:48
gansobswartz: yes, I would to know more about, because I had some topic on Data service, that may or may not include what you are already proposing in that session12:48
bswartzoh I'm not proposing sessions12:48
*** swamireddy1 has joined #openstack-manila12:49
bswartzjust throw out ideas -- hoping others have actual proposals12:49
bswartzthrowing out ideas12:49
swamireddy1Hi12:49
swamireddy1Team12:49
gansobswartz: oh ok, but what is that idea about? what's related to the RPCs?12:49
swamireddy1can you please confirm - is the manila project has stable release or still incubation?12:50
bswartzI think the big issue in my mind is the lack of job state tracking12:50
bswartzwhen doing a data copy, we need to be tracking the state in the DB12:50
bswartzbecause it's a long running operation, and the admin may want to restart the m-dat service12:50
vponomaryovswamireddy1: you suggested not compatible things12:51
bswartzthe RPC will probably need to change a bit to allow this12:51
vponomaryovswamireddy1: manila has stable releases and OpenStack has no "incubation" idea12:51
bswartzvponomaryov: +112:51
gansobswartz: it has some sort of tracking right now, but there is a lot of improvement to be done12:51
bswartzswamireddy1: we were "incubated" a long time ago but now manila is a normal project12:51
vponomaryovswamireddy1: manila is under "big tent"12:52
bswartzganso: well I'd like Newton to be the release where we get all of that finished12:52
gansobswartz: since every job right now is related to a share, the share has the task_state field which represents its "job_state". If m-dat is restarted while the Data Service has jobs running, it will set all their task_state to error12:52
bswartzokay well I might be misinformed about what's already done12:53
swamireddy1thank you very much...12:53
bswartzin any case I want to bring the whole community onto the same page and get others to help with migration if you need it12:53
gansobswartz: yes, there is a lot of around of it to be proposed, like, we may not need Data Service RPCs anymore, just add job to DB, and Data Service may keep it up. Data Service may update the DB with job progress instead of admins having to query Data Service for progress, etc. Lots of improvements12:54
bswartzI'd like to make these feature non-experimental12:54
gansobswartz: oops let me fix the above sentence, it is very confusing12:55
gansobswartz: yes, there is a lot of improvements that can be proposed, like, we may not need Data Service RPCs anymore, just add job to DB, and Data Service may pick it up. Data Service may update the DB with job progress instead of admins having to query Data Service for progress, etc. Lots of improvements12:55
gansobswartz: and these improvements need to be designed12:56
gansobswartz: the patches that merged in Mitaka were mostly responsible for laying ground to these improvements12:56
gansobswartz: I would like to start working on Retype in Newton12:57
gansobswartz: having retype use case implemented may point out necessary changes to migration, and it is best to address those changes while in experimental12:58
bswartzyes I agree12:58
*** ociuhandu has quit IRC12:59
bswartzall I'm saying is that we should make migration a focus area for newton so it's not just you working on it -- if enough people pitch in we could get it done completely12:59
*** rraja_ has joined #openstack-manila13:00
*** rraja has quit IRC13:00
bswartzso let's come up with a list of everything we need and you can tell us where you want help13:00
bswartzI have a meeting bbl13:00
gansobswartz: I agree completely, that should be the main focus. If only I am working on it, my scope of improvements and changes is rather limited since I am the only one using it13:00
gansobswartz: ok13:00
*** cknight has joined #openstack-manila13:02
zigoGuys, manila-ui just reached Debian Experimental! :)13:04
zigo\o/13:04
zigo(I uploaded it yesterday)13:04
*** akerr has joined #openstack-manila13:06
*** bswartz has quit IRC13:08
*** timcl has joined #openstack-manila13:13
*** bswartz has joined #openstack-manila13:14
*** mtanino has quit IRC13:17
openstackgerritMerged openstack/manila: Add hacking check to ensure not to use xrange()  https://review.openstack.org/29412413:18
openstackgerritEmilien Macchi proposed openstack/puppet-manila: Switch to ubuntu-trusty DIBS  https://review.openstack.org/29580213:21
*** gouthamr has joined #openstack-manila13:23
*** rraja_ has quit IRC13:23
*** furlongm_ has joined #openstack-manila13:28
*** furlongm has quit IRC13:30
*** erlon has joined #openstack-manila13:34
*** porrua has joined #openstack-manila13:37
*** eharney has joined #openstack-manila13:41
*** Yogi1 has joined #openstack-manila13:43
openstackgerritRodrigo Barbieri proposed openstack/manila: Add Driver Data Service Helper  https://review.openstack.org/29583613:51
*** ociuhandu has joined #openstack-manila13:52
*** rhagarty has joined #openstack-manila13:54
*** dustins has joined #openstack-manila13:55
*** a_ta has joined #openstack-manila13:57
*** mtanino has joined #openstack-manila14:01
*** yangyapeng has quit IRC14:02
*** baojg has joined #openstack-manila14:05
*** yangyapeng has joined #openstack-manila14:06
bswartzvponomaryov: You didn't put your nick next to all of the items you added in etherpad14:12
*** martyturner has joined #openstack-manila14:12
bswartzganso: put your nick next to things you add so we know it was you14:14
bswartzhttps://etherpad.openstack.org/p/manila-newton-summit-topics14:14
gansobswartz: I will, in a sec xD14:14
bswartzmy softphone is crap14:14
bswartzanyone know a good softphone that runs on Fedora?14:14
*** swamireddy1 has quit IRC14:25
*** jasonsb has quit IRC14:30
*** jasonsb has joined #openstack-manila14:31
*** openstackgerrit has quit IRC14:33
*** baojg has quit IRC14:34
*** openstackgerrit has joined #openstack-manila14:34
*** baojg has joined #openstack-manila14:35
*** baojg has quit IRC14:36
akerrbswartz: OSx14:42
akerrbswartz: just remind yourself its a flavor of Unix and all will be right with the world :)14:43
*** vbellur has quit IRC14:45
*** absubram has joined #openstack-manila14:46
dustinsbswartz: https://fedoraproject.org/wiki/VoIP14:48
dustinsThere's a list of Softphone apps on that page, no idea if any of them are any good, but it's a starting point!14:49
*** martyturner has quit IRC14:52
*** baojg has joined #openstack-manila14:53
*** JoseMello has joined #openstack-manila15:01
*** aovchinnikov has quit IRC15:05
*** baojg has quit IRC15:05
*** vbellur has joined #openstack-manila15:10
*** vbellur has quit IRC15:10
*** vbellur has joined #openstack-manila15:10
*** nkrinner has quit IRC15:42
*** timcl has quit IRC15:47
*** timcl has joined #openstack-manila15:47
*** a_ta has quit IRC16:03
*** bswartz has quit IRC16:21
*** vbellur has quit IRC16:28
*** a_ta has joined #openstack-manila16:32
*** swamireddy1 has joined #openstack-manila16:33
*** breitz has quit IRC16:36
*** akshai has joined #openstack-manila16:45
*** jasonsb has quit IRC16:48
*** pcaruana has quit IRC16:52
*** akshai has quit IRC16:52
*** akshai has joined #openstack-manila16:52
*** akshai_ has joined #openstack-manila16:54
*** akshai has quit IRC16:58
*** sgotliv has joined #openstack-manila17:01
*** timcl1 has joined #openstack-manila17:03
*** timcl has quit IRC17:04
*** bswartz has joined #openstack-manila17:19
bswartzdustins: that was the first place I went17:20
bswartzso far every one I've tried is crap17:20
dustinsWhat were you using?17:20
bswartzSFLPhone and Linphone17:20
dustinsLooks like folks here tend to use Linphone17:21
dustinsWhich if that's not working for you...17:22
bswartzlinphone isn't terrible -- but it doesn't like my audio devices17:22
vponomaryovbswartz: have you tried skype?17:22
*** a_ta has quit IRC17:22
bswartzI can't use speakerphone because it tries to open the ALSA device at 8kHz which doesn't work'17:22
dustinsvponomaryov: I was thinking that too, but I'd heard they stopped supporting/updating Skype for linux17:23
bswartzand it won't work with my headset because it ends up looping over some control setting and blowing up17:23
*** a_ta has joined #openstack-manila17:23
bswartzvponomaryov: that's MSFT software -- not open source17:23
vponomaryovbswartz: I use skype all the time on Ubuntu for webex17:23
vponomaryovbswartz: when webex's audio is disabled by host17:24
*** akerr is now known as akerr_away17:24
bswartzit's something to consider17:24
vponomaryovbswartz: not open source does not mean we cannot use it17:24
bswartzif I can't get a decent softphone however I'll just replace my cisco hardphone17:24
bswartzI'm hoping it's just a bad power supply because I can replace that17:26
*** akerr_away is now known as akerr17:27
*** a_ta has quit IRC17:28
bswartzvponomaryov: I avoid supporting closed source stuff when there's a decent open source alternative -- in the case of softphones I'm starting to worry that the decent open source alternative doesn't exist17:29
tpsilvabswartz: ping17:32
*** vbellur has joined #openstack-manila17:34
*** krotscheck has quit IRC17:43
*** swamireddy1 has quit IRC17:44
*** pcaruana has joined #openstack-manila17:44
*** akerr has quit IRC17:46
*** lpetrut has quit IRC17:49
bswartztpsilva: pong17:49
tpsilvabswartz: hello Ben. I was thinking about leading one of the summit topics... probably the snapshots one17:52
bswartztpsilva: you coming to austin?17:52
tpsilvabswartz: no, unfortunately... will be participating remotely17:53
tpsilvabswartz: ganso and adriano (one of our cinder guys) will be there, though17:53
bswartzas I was telling vponomaryov -- I'm just throwing topics up on the etherpad -- I'm expecing most of them to be led by other people, because if I lead all of them it will get really boring17:53
bswartzokay cool17:53
tpsilvaright17:54
bswartzalso I simply don't have time to prepare much material for all those topics, we need people to lead them -- ideally the same people who will volunteer to do the work17:54
tpsilvabswartz: I'll prepare something for this then17:55
bswartzif you want to lead a topic please add your name to the etherpad and say you want to lead it17:55
* bswartz AFK for a bit17:55
tpsilvabswartz: I thought about having a wip by then, but it looks like it's not really well defined yet how this should be implemented17:55
*** akerr has joined #openstack-manila17:56
*** akerr has quit IRC18:05
*** akerr has joined #openstack-manila18:06
*** dencaval has quit IRC18:09
*** dencaval has joined #openstack-manila18:15
*** akerr has quit IRC18:15
*** akerr has joined #openstack-manila18:16
*** a_ta has joined #openstack-manila18:27
*** akerr has quit IRC18:31
*** akerr has joined #openstack-manila18:31
*** lpetrut has joined #openstack-manila18:46
*** mtanino has quit IRC19:04
*** ociuhandu has quit IRC19:16
*** a_ta has quit IRC19:17
*** a_ta has joined #openstack-manila19:18
*** a_ta has quit IRC19:22
*** akerr has quit IRC19:26
*** porrua has quit IRC19:33
*** ociuhandu has joined #openstack-manila19:35
bswartztpsilva: did you follow the discussion from tokyo?19:37
bswartzunfortunately no progress was made afterwards because a question was raised and never answered19:37
tpsilvabswartz: no... is there an etherpad or something like that?19:38
bswartzdustins: ping19:38
bswartztpsilva: probably, but I doubt it has the latest thinking19:38
bswartzthere was one for toyko, but it probably doesn't capture the aftermath19:38
tpsilvabswartz: I know that two possible implementations were being discussed: inheriting rules from the share, but in read only mode; or allowing specific rules for the snapshots (read only, of course)19:41
tpsilvabut I don't know which was preferred19:41
dustinsbswartz: pong19:42
bswartzdustins: regarding the people who use linphone -- do they use ALSA or pulseaudio?19:46
dustinsbswartz: Not sure, the docs just say that the audio device can be selected in preferences19:47
dustinsWhich is not exactly helpful19:47
bswartzindeed it can19:48
bswartzbut pulse doesn't work at all and alsa has a lot of problems19:48
dustinsI'd say you'd probably be better off with ALSA19:48
bswartzI was wondering where to invest my efforts19:48
dustinsBut now that I say that, haha19:48
dustinsYeah there's nothing in the docs here about whether to use PulseAudio over ALSA or vice versa19:49
bswartzdustins: I was mostly wonder if you or anyone you know who uses linphone could share their working configuration19:50
bswartzdebugging this is annoying, and inspires me to look for other options19:50
dustinsOh, that I don't know, haha I'll ask around the internal channels and get back to you19:50
*** a_ta has joined #openstack-manila19:50
*** timcl1 has quit IRC19:52
bswartzunbelievable19:54
bswartzapparently my normal phone is dead on account of the power supply19:54
bswartzat least this is fixable19:54
*** david-lyle_ has joined #openstack-manila19:56
*** akerr has joined #openstack-manila19:57
*** david-lyle has quit IRC19:57
*** ekarlso- has quit IRC19:58
*** Yogi1 has quit IRC19:58
*** akerr_ has joined #openstack-manila19:59
*** david-lyle_ is now known as david-lyle20:02
*** akerr has quit IRC20:03
*** ekarlso- has joined #openstack-manila20:11
* bswartz jumps for joy20:18
bswartzphone is working20:18
bswartzno thanks to broken cisco power supply that's out of support20:19
bswartztpsilva: still here?20:19
bswartztpsilva: we can cover the options now20:19
*** ganso has quit IRC20:19
tpsilvabswartz: yes, just a sec... on mobile now20:21
bswartzlmk20:21
*** a_ta has quit IRC20:21
*** a_ta has joined #openstack-manila20:22
tpsilvabswartz: ok, I'm here now20:22
*** akerr_ is now known as akerr_away20:22
*** a_ta has quit IRC20:23
*** a_ta has joined #openstack-manila20:24
tpsilvabswartz: https://etherpad.openstack.org/p/mitaka-manila-snapshot-semantics is this the etherpad from tokyo?20:25
*** lpetrut has quit IRC20:27
bswartztpsilva: okay so there are 3 proposals for making snapshots directly mountable by users in readonly mode20:33
bswartztpsilva: 1) make "readable" snapshots inherit the access rules of the parent share20:33
bswartztpsilva: 2) add new APIs for snapshot access allow/deny and store these rules in a new DB table20:34
bswartztpsilva: 3) create the new concept of a "read-only" share, and add a flag to create-snapshot-from-share to allow the resulting share to be readonly -- for backends which had the ability, they could create a dummy share if the readonly flag was specified and simply use that share to expose the snapshot20:36
bswartzall options have downsides20:36
tpsilvayes20:37
bswartz(1) creates problems because if the user wants to allow different systems to access the share and the snapshot, then they can't do that20:37
bswartz(2) is a lot of new APIs, database work, and driver interface changes20:37
tpsilvaI was preferring option 3, but when you said about this dummy share... it might become confusing for the drivers20:37
bswartz(3) creates a whole new type of share, and we'd need to be careful to specify how all existing operations behave on a share that is designated "readonly"20:38
bswartzno -- the driver interface would be no different20:38
bswartzif we go with (3) then the driver would receive the same call from the manager it does today, just with a readonly=True flag20:38
bswartzthe driver could choose to not actually create anything on the controller and to return the export locations of the snapshot itself, if the controller can directly export snapshots20:39
bswartzso any complexity would be down inside the driver20:40
tpsilvayou're right... it would depend on the driver20:40
bswartzthe issue is that now we have to define how every other operation works with readonly shares20:40
bswartzcan you expand a readonly share? can you shrink it? can you take snapshots of it? can you migrate it? etc....20:40
tpsilvaprobably the only operations that make sense are allowing/denying rules for this kind of shares20:41
bswartzyes probably, but we need to think through everything20:42
bswartzbecause at the API layer it will look like a new share20:42
bswartzso all the API code will need to start checking that readonly flag before doing its work20:42
bswartzwe need to think about quota impact too20:43
bswartzdoes a readonly share consume quota similar to a new writable share?20:43
tpsilvaright, it should probably not consume quotas20:43
bswartzwell that gets nasty20:43
tpsilvayep20:43
tpsilvabut it doesn't  mess that much with DB like option 2 and looks more flexible than option 120:44
bswartzI proposed option (1) in the room in tokyo and it seems like a nonstarter20:45
bswartz(2) was the backup plan, but (3) was actually proposed by sage during the session20:45
bswartzI have a hard time deciding between (2) and (3)20:46
tpsilvawell20:46
tpsilvaI was looking at the DB today because I thought option 2 was the only option20:46
tpsilvaadd the export location to the snapshot would not be that much of a problem20:47
bswartzconceivably (2) wouldn't end up being much work20:47
bswartzyes we'd need to whole new APIs20:47
tpsilvabut for the rules we would need another table20:47
bswartztwo*20:47
bswartzbut the code could be reusable20:48
tpsilvaor change the current rules table for this20:48
bswartzwe might be able to reuse the DB table -- I'd have to look20:48
tpsilvawell, but we have that update_access problem as well20:48
bswartzand we'd need new driver entry points, but again they might end up looking very similar to share access20:48
tpsilvait's not quite done, I'd guess20:48
bswartzwe'll get there20:48
bswartzthat's another topic for newton20:48
tpsilvaand I would suggest some changes20:49
tpsilvayes20:49
bswartzhow to we get the laggers to implement update_access()20:49
tpsilvaand how we fix the concurrency issues once and for all20:49
*** cknight has quit IRC20:49
bswartzuhhh20:49
bswartzthat's going to be incremental20:49
bswartzwe can fix individual issues once and for all, but we need a framework to do so20:49
bswartzwe'll never be done with concurrency issues IMO20:50
tpsilvaanyway, those were the two thinks I'd like to work with in newton... but I don't think I'll have much time to work with both20:50
tpsilvaso I'll probably stick with the snapshot one20:50
tpsilvaso you prefer option 2 over option 3?20:50
tpsilvafor me option 3 looks like the most obvious one... when ganso was explaining the problem for me, I immediately thought the solution was something like option 320:51
bswartzthat's what I thought after the session in tokyo20:52
bswartzwhen I thought about all the follow on impacts I started to wonder if (2) was really so bad20:53
tpsilvanot bad, but I worry about the rules20:54
tpsilvabut if we add a new table just for the snapshot rules, doesn't look that bad20:54
*** dustins has quit IRC21:03
tpsilvabswartz: ?21:05
bswartz?21:06
bswartzI'm still undecided21:06
tpsilvawell, I can elaborate both proposals for the summit then21:07
bswartzI guess I'm now leaning a bit towards (2) because it's less confusing -- but we need an honest assessment of how much code could be reused and how much new code would be needed21:07
tpsilvalooks like this is not quite ready for a wip21:07
tpsilvait is indeed less confusing, since we don't have a new different type of share21:09
*** gouthamr has quit IRC21:11
*** cknight has joined #openstack-manila21:25
*** cknight has quit IRC21:33
*** cknight has joined #openstack-manila21:37
*** cknight1 has joined #openstack-manila21:38
*** JoseMello has quit IRC21:39
*** cknight has quit IRC21:42
*** akerr_away has quit IRC21:42
*** gouthamr has joined #openstack-manila21:47
*** a_ta has quit IRC21:48
*** openstackgerrit has quit IRC21:48
*** a_ta has joined #openstack-manila21:48
*** openstackgerrit has joined #openstack-manila21:49
*** a_ta has quit IRC21:53
*** eharney has quit IRC22:06
*** darrenc is now known as darrenc_afk22:14
*** gouthamr_ has joined #openstack-manila22:34
*** cknight1 has quit IRC22:35
*** darrenc_afk is now known as darrenc22:35
*** gouthamr has quit IRC22:37
*** ociuhandu has quit IRC22:40
*** absubram has quit IRC22:47
*** sgotliv has quit IRC22:59
*** ociuhandu has joined #openstack-manila22:59

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