15:00:06 #startmeeting manila 15:00:07 Meeting started Thu Mar 12 15:00:06 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:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:10 The meeting name has been set to 'manila' 15:00:19 hello all 15:00:24 hi 15:00:25 hi 15:00:26 hello 15:00:40 #agenda https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:01:00 small group today! 15:01:12 maybe some people forgot about the time change... 15:01:13 Hi 15:01:14 hi 15:01:20 hi 15:01:41 hi 15:01:51 #topic K-3 status / FF status 15:02:01 #link https://launchpad.net/manila/+milestone/kilo-3 15:02:28 so the good news is that we merged a good new of BPs in the last week 15:02:43 good number* of BPs 15:03:11 I only see 6 left to get done before feature freeze 15:03:28 thanks everyone for prioritizing reviews of these BPs 15:03:51 I want to get the remaining 6 merged by Tuesday of next week 15:04:03 if one slips to Wednesday that's not a big deal 15:04:18 we still still have multiple open on Wednesday I'm going to be nervous 15:04:37 The final feature freeze date is Thursday next week 15:04:46 anyone have questions about this? 15:05:14 what hour? :) 15:05:21 lol 15:05:42 let's say before we have this meeting next week 15:06:15 ok 15:06:20 I need to give ttx the commit hash for K-3 after the IRC meeting, but I want to do it on Wednesday ideally 15:06:37 or even Tuesday if we can manage it 15:06:51 csaba I know you have a non-targetted BP you're hoping to get in 15:07:07 yep :S 15:07:21 is it ready to merge? 15:07:58 so reviewers can +2 you 15:08:06 no, cknight has done a review but unit tests are WIP 15:08:13 I'll take a look too after I get to all the others 15:08:19 ok 15:08:43 thx 15:08:45 non-targetted BPs are *lowest* priority though for reviewers 15:09:05 please review the targeted ones first, then take a look at the rest 15:09:26 I'll -2 anything that looks too risky 15:09:33 I haven't gone through the whole list yet 15:09:45 but I have time today for reviews 15:10:03 anything else on this before we move on? 15:10:18 #topic postgres support 15:10:49 so mark-os has been trying to get manila running on top of postgres and having some problems 15:11:19 we don't actively test on postgres, but it's something we want to support 15:11:41 actively? we don't at all =) 15:11:43 I have a feeling we might not get around to fulfilling that promise until liberty, but I wanted to check if anyone had a different view 15:12:16 vponomaryov: by "we" I mean the whole community, not just the core team 15:12:41 bswartz: and I mean CI 15:12:41 I want to add a check/gate job that installs manila on postgres and runs tests 15:12:56 but before we can do that, we have to find/fix the bugs 15:13:26 actually we can do it in parallel, just making it non-voting 15:13:42 does anyone think there's a chance we could fix 1 or 2 bugs and have postgres 100% supported? or are we farther away than that? 15:13:43 vponomaryov +1 15:14:05 vponomaryov: +1 15:14:08 vponomaryov: that's true, but it's not a high priority if we know that postgres is horribly broken 15:14:34 the priority is to make it mostly work first before we start burning CI resources to test it 15:14:37 bswartz: tempest job with postgres will tell us 15:15:02 bswartz: we can make not static job 15:15:05 bswartz:but experimental 15:15:13 bswartz: that runs only by poking action 15:15:20 Hi, sry, <- late 15:15:29 anyways I'm not hearing that anyone has tried this yet -- so it's still a big open question 15:15:40 vponomaryov: good idea 15:16:04 anyways let's keep helping mark-os and anyone else who wants to spend time on that 15:16:16 during liberty we definitely need to get postgres officially supported 15:16:46 #topic unit tests on python 3.4 15:17:08 so I noticed that we're not currently testing on python 3 15:17:57 what holds us back from python 3 support? 15:18:14 bswartz: some deps 15:18:18 many other openstack projects test on both 15:18:26 and we've done a good amount of work to support both 15:18:58 vponomaryov: a lot of deps? how much work? 15:19:15 bswartz: need to investigate 15:19:38 I don't want to fall behind he rest of the community in this area 15:19:39 bswartz: some can be replaced by "six" like "pipes" 15:20:10 it's not urgent, but if we can get a python 3.4 check job running in liberty I think that would be good 15:20:40 bswartz: non-voting - anytime =) 15:20:45 lol 15:21:10 well I don't want to have a job that's always failing -- esp if we're not going to fix the problems until liberty 15:21:24 it's probably a bad idea to make a bunch of six changes during K-4 15:21:28 so we don't do that 15:21:34 won't* 15:22:15 okay enough on that 15:22:26 #topic Horizon plugin for Manila 15:22:34 markstur: here? 15:22:38 The Horizon team has been talking about Manila: http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-03-11-20.00.log.html 15:22:48 Quote: "20:55:23 murano will be here soon and manila and those should be plugins". 15:22:48 I work with Mark... 15:23:04 The model Horizon is proposing would put the plugin code in its own project. Perhaps manila-ui like the tuskar-ui. 15:23:07 oh this is news to me 15:23:15 just yesterday 15:23:25 At HP we are interested in getting that project started ASAP by taking from our current fork to create a plugin. 15:23:40 Obviously the goal is to get it in the openstack eco-system with gerrit for team collaboration. 15:23:56 Hey look I accidentally pinged David 15:24:00 the plugin model is what horizon is going for on new projects 15:24:05 * david-lyle came running 15:24:17 (and even old ones) 15:24:18 #link https://github.com/NetApp/horizon/tree/manila_kilo 15:24:31 ^ so this is what we have so far 15:24:39 gary-smith__ can get that project started. So we wanted to bring it up here. 15:24:57 nice, this will make horizon integration much easier 15:25:01 new service additions should target the horizon plugin mechanism, and we'll get that plugin into the openstack namespace 15:25:25 yes I absolutely support a manila gui proehct that plugs into horizon 15:25:28 this will also make sure your development work can progress at the rate you want 15:25:39 do we call it manila-ui? manila-dashboard? 15:25:46 and not suffer on our review queue 15:26:08 I wanted thrilla-in-manila, but that didn't really make sense. So you guys pick the name. 15:26:14 lol 15:26:19 the pattern so far would suggest manila-ui 15:26:26 david-lyle: is Horizon plugins remotely available or need to copy-paste files to Horizon dir directly? 15:26:27 although I like thrilla :-) 15:26:39 vponomaryov: remotely available 15:26:52 just need to be installed on the horizon server 15:26:54 david-lyle: good to know, thanks 15:27:05 is this something that will be achievable before Kilo or a plan for Liberty? 15:27:17 Liberty, definitely 15:27:23 one file needs to be linked or copied into the horizon enabled directory so Horizon knows to pick it up 15:27:36 okay 15:27:51 so we'll do what we've done before for our Kilo release 15:28:07 and when liberty starts up we'll get manila-ui started 15:28:19 I was thinking we'd start sooner. 15:28:29 But not sure when it would realistically be ready. 15:28:32 thanks david-lyle and gary-smith__ 15:28:33 I hope we can get the ball rolling before liberty 15:28:35 Easy for me to say 15:28:37 yeah, exactly 15:28:59 markstur: there's no harm in starting ASAP, but we need an actual working solution for uses of Kilo, and that's more important 15:29:27 s/uses/users/ 15:29:56 that's why we're going to keep doing what we've done before in in the next 2 months 15:30:08 RIght. 15:30:27 which is to maintain our fork of horizon with manila grafted on 15:30:51 Yes we need that until we have something else really ready to use. 15:31:03 Which is I think why Gary said Liberty. 15:31:03 markstur: +1 15:31:05 liberty sounds like the perfect timeframe for this 15:31:56 markstur: are you volunteering to own creating the project and getting things started? 15:32:15 Yeah. I'm volunteerying gary-smith__ 15:32:19 I will volunteer to do that 15:32:28 okay great 15:32:35 thanks! 15:32:48 anything else to discuss about horizon? For kilo or liberty? 15:33:15 Thanks for tuning in David. It was good to hear your support. 15:33:23 #topic open discussion 15:33:24 gary-smith__: one question 15:33:32 any other topics of any kind? 15:33:39 gary-smith__: do plugins support its own dependencies? 15:33:56 vponomaryov: I believe so 15:34:10 vponomaryov: you're thinking about python-manilaclient? 15:34:10 but david-lyle is the expert on that 15:34:24 do we have other dependencies? 15:34:25 bswartz: yes 15:34:43 no, for the moment 15:34:47 k 15:35:22 well it sounds like we're done early today 15:35:33 take back 25 minutes and do some code reviews 15:35:45 your plugin should have that dependency 15:35:55 I'll be reviewing all afternoon today 15:36:05 david-lyle: thanks 15:36:06 Are we able to use Availability Zones on shares? 15:36:27 david-lyle: that what I was interested in - possibility to setup deps for plugin 15:36:43 david-lyle: separately from deps of Horizon 15:37:14 vponomaryov: well it should be an installable python package, using setup.py or requirements.txt to pull in dependencies 15:37:14 bswartz: I removed target kilo from my BP 15:37:20 markstur: ther is no such API, so ... 15:37:34 ganso_: thanks 15:37:49 vponomaryov, But there probably should be like cinder... eventually... does that sound right? 15:37:52 david-lyle: requirements.txt is ok 15:38:20 markstur: eventually, yes 15:38:32 it hasn't been a priority yet 15:38:40 bswartz, OK. I was wondering if there was some other trick. 15:38:46 markstur: manila does not have it right now 15:38:47 vponomaryov: so your ui-plugin will own that file and can specify what is needed 15:39:03 david-lyle: great, thank you 15:39:35 alright, thanks everyone 15:39:48 #endmeeting