15:00:10 #startmeeting manila 15:00:11 Meeting started Thu Sep 18 15:00:10 2014 UTC and is due to finish in 60 minutes. The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:14 The meeting name has been set to 'manila' 15:00:19 Hi 15:00:23 hi 15:00:26 hi 15:00:27 hello all 15:00:29 hi 15:00:38 Hi) 15:00:56 #agenda https://wiki.openstack.org/wiki/Manila/Meetings 15:00:58 hi 15:01:15 so we've still have bugs :-( 15:01:23 I'm going to start with those 15:01:28 #topic bugs 15:01:36 #link https://launchpad.net/manila/+milestone/juno-rc1 15:01:44 I see 5 still open 15:02:08 lgreg: ping 15:02:36 vvechkanov1's 2 bugs have open reviews 15:02:55 bswartz: lgreg is not on the channel 15:03:03 I see 15:03:16 deepak isn't here either 15:03:35 anyways this is a reminder that we've got just 1 week until RC1 15:03:47 top priority is closing out these 5 bugs 15:04:01 does anyone have any bugs that aren't on this list that should be? 15:04:18 bswartz: there are new bugs,but scheduled for kilo 15:04:32 we can still target bugs to rc1 if they need to be 15:05:00 at this point it has to be critical or super low risk though 15:05:29 I'll ping deepak and greg as soon as I see them 15:05:40 #topic dev status 15:05:48 Dev status for last week: 15:05:55 1) Fixed ubuntu image for Manila according to bug: #link https://bugs.launchpad.net/manila/+bug/1370216 15:05:58 Launchpad bug 1370216 in manila "Samba not configured to use registry configuration" [Undecided,Fix released] 15:06:12 2) Several bugfixes to Generic and NetApp cmode drivers were commited 15:06:19 3) Other attempts were directed to testing and bugfixing, available for review: 15:06:19 3.1) #link https://review.openstack.org/119621 15:06:19 3.2) #link https://review.openstack.org/122399 15:06:47 that's the main 15:06:48 k I need to review those 15:06:57 thanks 15:07:03 (3.2) will be updated with unittests 15:07:23 okay on to the fun stuff 15:07:31 #topic paris design summit 15:08:05 so those of you who read the ML may have noticed that we won't be using summit.openstack.org to plan the design summit 15:08:41 the new format is to have the various teams organize their design summit topic on etherpads 15:09:00 https://wiki.openstack.org/wiki/Summit/Planning 15:09:52 There is an etherpad specifically for manila 15:10:02 #link https://etherpad.openstack.org/p/kilo-manila-summit-topics 15:10:14 And I got things started by dumping all of my ideas onto the etherpad 15:10:46 bswartz: do you know how much time we will get for the design summit? number of sessions? 15:10:53 I don't want to monopolize the time with my topics, but I wanted to present a format and get things started 15:11:02 xyang1: still no idea 15:11:38 but there will be "pods" for each project team and we'll get one of our own so we can have practically unlimited time to talk among ourselves 15:11:39 bswartz: hereā€¦. 15:11:53 lgreg_1: hey we missed you on the bugs topic 15:12:20 bswartz: apologies, on other call 15:12:20 lgreg_1: I'll sync up with you on the status of the 2 netapp driver bugs 15:12:53 I think it's still to early to worry about how to cram the topics into a fixed amount of time 15:13:17 right now I'd rather be brainstorming cool stuff to work on so we can pick the best ones for the public forum 15:13:22 bswartz: ok, will catch up 15:13:51 I'd rather have the problem of too many cool ideas and not enough time rather than too much time and not enough cool ideas 15:14:43 ofc we'll need to spend some time of boring stuff 15:15:52 hey vponomaryov, vvechkanov1, will you guys be able to come to the summit? 15:16:17 bswartz: unfortunately, I guess no 15:16:34 :-( 15:17:01 I hope you can get Mirantis to reconsider -- it would be great to have you there 15:17:22 xyang1: is it safe to assume you're coming? 15:17:31 bswartz: yes 15:17:53 * bswartz would love to have the whole core team in 1 place 15:18:05 anyways, any questions on the summit or the etherpad? 15:18:26 bswartz: what do we plan to be integrated with HEAT project? 15:18:56 vponomaryov: a plugin to heat so that heat templates can invoke manla 15:18:58 manila* 15:19:41 #topic incubation update 15:19:44 any plan on integrating with Sahara? 15:20:02 nileshb: I don't have any -- please suggest it if you do 15:20:11 ok sure 15:20:35 so the current word from infra is that the stackforge/manila->openstack/manila rename is happening tomorrow at 20:30 UTC 15:20:56 I'm going to be online at that time to help out if things go badly 15:21:23 there are SO MANY places where stackforge/manila appears in the code 15:21:35 I worry that it will take a while to get them all 15:21:41 and get things stabilized 15:21:48 so we can make RC1 next week 15:22:00 bswartz: we are just changing the location, but not the program name itself, correct? 15:22:15 yeah it's just to reflect that we're now incubated 15:22:34 nothing else changes 15:23:00 but sadly I do expect things to break so any help would be appreciated when it comes to fixing them 15:23:44 bswartz: I'll assist if needed. 15:23:49 #topic open discussion 15:23:55 okay anyone have anything else 15:24:15 xyang1: I wanted to ask you about CI since I've been looking at Manila CI 15:24:25 xyang1: are you responsible for the emc cinder ci? 15:24:27 bswartz: sure 15:24:33 bswartz: yes 15:24:42 and have you given any thought to how you'd do it for manila? 15:25:08 bswartz: I saw you asked for an CI account for NetApp manila driver. we are planning for it too 15:25:08 I want to setup something similar in kilo, and I've been hacking to see what's possible 15:25:11 bswartz: any dates? 15:25:24 a date will help us planning 15:25:44 hmm 15:26:09 my goal is to have something running before juno releases 15:26:11 the naming is tricky too 15:26:15 but I don't expect other to do the same 15:26:17 Juno? 15:26:21 10/16? 15:26:36 that's my goal -- maybe I'm crazy 15:26:47 that will be too soon for us:) 15:27:00 we have emc-vnx-ci for cinder 15:27:05 yeah I think the goal for the team should be to have things working by end of kilo 15:27:06 so I don't know how to name it for manila 15:27:24 xyang1: there's no reason you couldn't use the same CI account for 2 projects 15:27:28 when I asked for CI account, they didn't want to include cinder in name 15:27:44 in my case I'm trying not to distract the guys working on the cinder CI so I asked for a second account 15:27:49 xyang1: project names can be changed 15:27:51 bswartz: they are triggered by cinder commits now 15:27:51 long term though we want to merge it back to 1 account 15:28:02 I don't know what it means to run both 15:28:20 CI in cinder runs tests for Cinder, CI in manila runs tests in manila 15:28:23 xyang1: "Jenkins" is one account that runs on all projects -- it just knows to invoke different tests 15:28:46 emc-vnx-ci can do what jenkins does and run on more than 1 project 15:29:04 maybe it is ok 15:29:15 it's not a high priority 15:29:19 but it is already overwhelming to handle the number of commits in Cinder 15:29:33 we can only handle about 20 commits a day 15:29:47 given the infra we have today 15:29:51 manila should be lower volume than cinder 15:30:00 also we have less tests 15:30:02 yes 15:30:06 that's something I want to change, but that's a separate topic 15:30:18 it sounds like nobody has anything else 15:30:52 thanks all 15:30:57 thanks 15:30:57 thanks 15:30:59 thanks 15:31:02 #endmeeting