15:00:18 <bswartz> #startmeeting manila 15:00:19 <openstack> Meeting started Thu Jan 29 15:00:18 2015 UTC and is due to finish in 60 minutes. The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:22 <openstack> The meeting name has been set to 'manila' 15:00:29 <bswartz> hey guys 15:00:33 <toabctl> hi 15:00:34 <vponomaryov> hello 15:00:35 <u_glide> hi 15:00:42 <rushil> hi 15:00:46 <markstur_> hi 15:00:48 <bswartz> so I don't have an agenda prepared for today 15:01:01 <bswartz> because I'm in austin at the cinder meetup 15:01:13 <bswartz> but there's a few things I'd like to talk about 15:01:16 <cknight> Hi 15:01:21 <bswartz> so I'm going to make up the agenda as I go 15:01:22 <ganso_> hi 15:01:34 <vponomaryov> breaking news: "generic driver is broken due to bug in Nova" 15:01:47 <ganso_> O_O 15:01:49 <bswartz> #topic midcycle meetup 15:02:03 <bswartz> vponomaryov: okay let's fix that 15:02:31 <bswartz> we can talk about that one after this one 15:02:59 <bswartz> so last week there was some interest from various folks to attend a manila meetup in RTP in person 15:03:14 <bswartz> however everyone I've talked to has said they can't make it 15:03:31 <bswartz> is there anyone who is still interested in attending in person? 15:04:06 <bswartz> I proposed times on both the ML and the etherpad 15:04:26 <bswartz> nobody has objected to those times so I'd like to lock those in 15:04:42 <bswartz> we can proceed under the assumption that everyone will be joining remotely 15:04:56 <bswartz> I saw some suggestions for agenda items on the etherpad already which is great 15:05:05 <bswartz> I'll be putting my own suggestions there soon 15:05:19 <vponomaryov> please, provide a link 15:05:25 <bswartz> #link https://etherpad.openstack.org/p/manila-kilo-midcycle-meetup 15:05:28 <vponomaryov> thanks 15:06:20 <bswartz> if anyone does plan to attend in person, PLEASE CONTACT ME by email 15:07:39 <bswartz> the planned dates are feb 11 and 12 which are just 2 weeks away 15:07:55 <bswartz> by next week I hope to have the agenda filled up 15:08:18 <bswartz> just a reminder: the morning and afternoon sessions will probably have overlapping content to accommodate for people joining from different timezones 15:08:29 <bswartz> any quesitons about that? 15:08:56 <vponomaryov> time dedication to topics? 15:09:33 <vponomaryov> like one topic - 15 minutes or similar 15:09:34 <bswartz> vponomaryov: we'll see how much we have to discuss 15:09:42 <bswartz> then split up the time 15:10:10 <bswartz> The purpose of the meetup is to benefit you guys 15:10:57 <bswartz> and if there's no enough to talk about then I'll take advantage of the time to pull you all into code reviews and bugfixing for K-3 15:11:01 <bswartz> hehe 15:11:16 <bswartz> okay 15:11:30 <bswartz> #topic nova bug affecting generic driver 15:11:37 <vponomaryov> bug in manila: #link https://bugs.launchpad.net/manila/+bug/1415770 15:11:40 <bswartz> vponomaryov: what is there to say about this topic? 15:11:41 <vponomaryov> bug in nova: #link https://bugs.launchpad.net/nova/+bug/1415835 15:11:47 <vponomaryov> Temporary fix into Manila: 15:11:48 <vponomaryov> gerrit: #link https://review.openstack.org/151217 15:12:02 <vponomaryov> Nova shoots in its own leg trying boot Vm with Neutron port 15:12:17 <vponomaryov> since today 15:12:44 <bswartz> did you talk to any nova guys about this? 15:13:06 <vponomaryov> #link https://review.openstack.org/#/c/151184/ 15:13:07 <bswartz> what's the likelihood it will be fixed there soon? 15:13:21 <vponomaryov> bswartz: it depends 15:13:31 <vponomaryov> but not only Manila is broken 15:13:35 <vponomaryov> rally project is broken too 15:13:38 <vponomaryov> we are not alone 15:14:40 <vponomaryov> I guess soon, because it is really critical 15:14:57 <bswartz> well is the fix you proposed something we shouldn't merge if they fix their bug soon? 15:15:29 <vponomaryov> bswartz: we do not have tempets covered until NOva bug is fixed 15:15:39 <vponomaryov> s/covered/coverage/ 15:15:55 <bswartz> oh I just reviewed the fix 15:16:06 <bswartz> okay this is a fine temporary workaround 15:16:21 <bswartz> thanks vponomaryov 15:16:25 <bswartz> #topic dev status 15:16:46 <vponomaryov> Dev status: 15:16:50 <vponomaryov> 1) New Neutron network plugin that uses only one preconfigured net/subnet 15:16:56 <vponomaryov> BP: #link https://blueprints.launchpad.net/manila/+spec/neutron-single-network-plugin 15:17:00 <vponomaryov> gerrit: #link https://review.openstack.org/150460 15:17:05 <vponomaryov> status: merged 15:17:14 <vponomaryov> 2) New standalone network plugin 15:17:18 <vponomaryov> BP: #link https://blueprints.launchpad.net/manila/+spec/standalone-network-plugin 15:17:21 <vponomaryov> status: work in progress 15:17:31 <vponomaryov> 3) Manage/unmanage shares 15:17:35 <vponomaryov> BP: #link https://blueprints.launchpad.net/manila/+spec/manage-shares 15:17:39 <vponomaryov> gerrit: #link https://review.openstack.org/147495 15:17:42 <vponomaryov> status: finished, ready for review 15:17:51 <vponomaryov> 4) Single_svm mode for Generic driver 15:17:55 <vponomaryov> BP: #link https://blueprints.launchpad.net/manila/+spec/single-svm-mode-for-generic-driver 15:17:59 <vponomaryov> gerrit: #link https://review.openstack.org/142403 15:17:59 <vponomaryov> status: finished, ready for review 15:18:05 <vponomaryov> 5) Share access levels 'ro' and 'rw' 15:18:08 <vponomaryov> BP: #link https://blueprints.launchpad.net/manila/+spec/level-of-access-for-shares 15:18:13 <vponomaryov> gerrit: 15:18:13 <vponomaryov> - client #link https://review.openstack.org/144298 15:18:13 <vponomaryov> - server #link https://review.openstack.org/144617 15:18:13 <vponomaryov> status: finished, ready for review 15:18:23 <vponomaryov> 6) level of visibility for shares 15:18:26 <vponomaryov> BP: #link https://blueprints.launchpad.net/manila/+spec/level-of-visibility-for-shares 15:18:30 <vponomaryov> gerrit: #link https://review.openstack.org/148853 15:18:38 <vponomaryov> status: work in progress 15:18:44 <vponomaryov> that's the main 15:19:27 <bswartz> rushil: where are we with share-types? 15:20:52 <bswartz> hmm 15:20:52 <bswartz> okay 15:21:00 <bswartz> #topic k-2 milestone 15:21:14 <bswartz> #link https://launchpad.net/manila/+milestone/kilo-2 15:21:32 <bswartz> okay I'm going to kick out anything that I can't get a response for 15:22:06 <bswartz> csaba: what is the status of gateway-mediated-with-ganesha 15:22:24 <bswartz> it's old and has -1 from jenkins 15:22:55 <bswartz> dynamic-storage-pools I know is ready 15:23:09 <bswartz> single-svm-mode-for-generic-driver is ready 15:23:21 <csaba> bswartz: we will submit patch soon 15:23:21 <bswartz> generic-driver-single-svm-ci-job -- is this ready? 15:23:34 <vponomaryov> bswartz: yes 15:23:36 <csaba> rraja can tell the details 15:23:40 <bswartz> csaba: can it be done for k2? 15:23:51 <bswartz> we only have a week 2 review and merge it 15:23:57 <bswartz> s/2/to/ 15:24:18 <csaba> bswartz: yes 15:24:28 <bswartz> csaba: I'd rather push it to k3 unless it's going to be a quick an easy review 15:25:06 <bswartz> level-of-access-for-shares is ready 15:25:31 <rraja> bswartz: yes it is quick and easy review. the patch https://review.openstack.org/#/c/124637/ should be up in a couple of days. 15:25:31 <csaba> bswartz: when do you need to decide? 15:25:38 <bswartz> netapp-driver-factory and netapp-driver-tracing are ready 15:25:55 <rraja> bswartz: i ran into couple of bugs in SSHPool and ganesha config options registry 15:25:59 <bswartz> rraja: it needed to be submitted 5 days ago for k2, technically 15:26:09 <bswartz> a few more days is too late 15:26:11 <rraja> bswartz: i've fixed those bugs. 15:27:03 <rraja> bswartz: OK. 15:27:12 <bswartz> it's high priority so I'll give it 24 hours to show up 15:27:18 <bswartz> tomorrow morning I'll boot it out 15:28:12 <jasonsb> bswartz: i have a question on updating requirements.txt 15:28:17 <bswartz> enhance-share-manager -- this doesn't look ready 15:28:21 <rraja> bswartz: ganesha bugs also affects GPFS Share driver. so hopefully at least that fix can go in, https://review.openstack.org/#/c/151112/ 15:28:27 <bswartz> jasonsb: let me get through the bp list forst 15:28:39 <bswartz> rraja: we can cover bugs too 15:28:51 <nileshb> right 15:28:59 <bswartz> vponomaryov: what's with enhance-share-manager 15:29:12 <vponomaryov> bswartz: no one works on it 15:29:19 <bswartz> okay I'll retarget 15:29:45 <bswartz> hp3par-manila-driver 15:29:52 <bswartz> this has a bunch of -1 15:30:00 <markstur_> fixes are ready except 15:30:07 <markstur_> adding share-from-snap 15:30:21 <markstur_> was planning that for later, but review asked for it 15:30:25 <bswartz> markstur_: okay just know that k-2 is a few days away 15:30:30 <markstur_> yeah 15:30:39 <bswartz> please be responsive to review comments to increase chance of getting merged 15:31:02 <bswartz> hitachi-sop-manila-driver 15:31:05 <markstur_> I can push fixes up today, but may have to do snapshare separate 15:31:30 <vponomaryov> jasonsb: is your driver going to support snapshots? 15:31:39 <jasonsb> 1 easy fix and test coverage to go 15:31:50 <jasonsb> vponomaryov: no. no snapshots for this 15:31:53 <bswartz> jasonsb: jenkins doesn't lke your patch 15:32:06 <jasonsb> how to best update requirements.txt? 15:32:15 <vponomaryov> jasonsb: just do it =) 15:32:17 <jasonsb> would like to pull from global-requirements into requirements 15:32:46 <jasonsb> it should be done separately from driver? 15:32:46 <bswartz> does global requirements overwrite our requirements, or can we add non-global requirements? 15:32:51 <bswartz> that's something I haen't tried 15:33:00 <ganso_> what is the guideline when driver does not support snapshots? prevent error or throw error in method? shouldn't there be an option in [manila] in tempest for this? 15:33:09 <jasonsb> global requirements has the thing i need so i think this is easy 15:33:09 <vponomaryov> bswartz: "global" is word from requirements projects 15:33:31 <bswartz> ganso_: drivers are supposed to support snapshots, even if the implementation is not efficient or pretty 15:33:35 <vponomaryov> jasonsb: itis ok to add it in commit with driver and before 15:33:46 <vponomaryov> if driver is first who starts using it 15:33:56 <jasonsb> vponomaryov: ok will do 15:33:58 <ganso_> bswartz: so a driver without snapshot cannot be accepted? 15:34:10 <bswartz> ganso_: talk to me about it offline 15:34:17 <bswartz> I want to know why it can't be supported 15:34:19 <vponomaryov> bswartz: we already have such drivers 15:34:32 <vponomaryov> csaba, rraja: right? 15:34:34 <bswartz> vponomaryov: we do make exceptions 15:34:48 <bswartz> but only for good reasons 15:35:01 <jasonsb> underlying platform doesn't support snapshots at present 15:35:06 <csaba> vponomaryov: yeah 15:35:22 <bswartz> it's bad to have backends that can't meet minimum functionality 15:35:45 <bswartz> we'll need to document which drivers have limitations and try to figure out how to fix them 15:36:04 <ganso_> bswartz: ok I will talk to you later about this 15:36:20 <bswartz> My intent is to start implement CI systems similar to what cinder has done 15:36:32 <bswartz> and drivers without snapshots won't pass those tests 15:36:44 <bswartz> that's a discussion for L though 15:37:03 <jasonsb> bswartz: am i ok for present? 15:37:22 <bswartz> let's talk offline 15:37:29 <jasonsb> ok 15:37:36 <bswartz> keep working on getting the driver to pass jenkins though 15:37:48 <vponomaryov> and pass reviewers too =) 15:37:51 <bswartz> and we'll do code reviews to try to get it mergable in parallel 15:38:03 <jasonsb> i'll post an update with requirements.txt to get a jenkins run 15:38:35 <jasonsb> vponomaryov: :) 15:38:38 <bswartz> it's not the end of the world if a driver slips to k-3, but if we have too many that limits our ability to focus on features and bugfixes 15:39:02 <bswartz> netapp-cdot-driver-extension 15:39:10 <bswartz> this one has been sitting around for a while 15:39:34 <bswartz> oh but it's getting worked on still 15:39:38 <bswartz> I'll give it another pass 15:39:47 <bswartz> okay BUGS 15:39:54 <bswartz> we have a bunch with no assignee 15:40:58 <bswartz> I see several netapp ones 15:41:07 <bswartz> can someone from netapp pick these up? 15:41:20 <cknight> bswartz: I can triage 15:41:24 <bswartz> ty 15:42:04 <bswartz> anyone working on a bug that's not targetted at k2? 15:42:25 <bswartz> I'm going to focus my reviews on k2-targetteed stuff only 15:42:39 <bswartz> going from high priority to low 15:43:12 <cknight> bswartz: yes, working on https://bugs.launchpad.net/manila/+bug/1415602 15:43:48 <bswartz> okay 15:44:08 <bswartz> so again I'll plead with all of you to focus on reviews this coming week 15:44:20 <bswartz> and if you have stuff being reviews, respond quickly 15:44:32 <bswartz> reviewed 15:44:42 * bswartz is typing on a crummy laptop keyboard 15:45:00 <bswartz> I have a good feeling about k2 15:45:11 <bswartz> but there a lot left to finish and not a lot of time 15:45:29 <bswartz> #topic open discussion 15:45:34 <bswartz> that's all I have 15:45:41 <bswartz> anyone have another topic to discuss today? 15:46:28 <bswartz> okay I think we're done 15:46:44 <ganso_> can we discuss snapshot now? 15:46:48 <bswartz> ganso_ and jasonsb: grab me today or tomorrow and we can talk about snapshots 15:46:49 <timcl> any updates on mid-cycle plans? 15:47:14 <bswartz> timcl: its looking like it will be all virtual 15:47:26 <bswartz> but the dates are good, so we can lock them in 15:47:34 <timcl> ok just wanted to make sure if there were people planning to travel 15:47:44 <bswartz> so far nobody is planning travel 15:47:52 <bswartz> to be fair we didn't give much advance notice 15:47:59 <bswartz> next time we can fix that 15:48:31 <bswartz> timcl: I'll let you know if that changes 15:48:54 <bswartz> thanks all! 15:49:09 <bswartz> #endmeeting