15:00:06 <bswartz> #startmeeting manila
15:00:08 <openstack> Meeting started Thu Jan  7 15:00:06 2016 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:11 <openstack> The meeting name has been set to 'manila'
15:00:16 <cknight> Hi
15:00:17 <bswartz> hello all
15:00:22 <dustins> \o
15:00:24 <vponomaryov1> hi
15:00:27 <toabctl> hi
15:00:32 <mkoderer> hello
15:00:33 <markstur> hi
15:00:34 <xyang> hi
15:00:40 <bswartz> merry orthodox christmas
15:00:41 <gouthamr> hello!
15:00:52 <alyson_> hi!
15:01:01 <ganso> hello
15:01:17 <bswartz> #agenda https://wiki.openstack.org/wiki/Manila/Meetings
15:01:27 <bswartz> #topic announcements
15:01:44 <bswartz> I just want to remind everyone about deadlines coming up
15:01:52 <tbarron> hi
15:01:55 <bswartz> Mitaka-2 is in 2 week (Jan 21)
15:02:39 <bswartz> as we agreed at the beginning of the release, we won't be accepting any "major features" that don't have WIP patches submitted by that date
15:03:07 <bswartz> the goal of that deadline is to make sure that we have enough time to review the big stuff going into mitaka
15:03:35 <bswartz> and also the we should try to get as many features complete and merged by the milestone so it's interested from a testing pespective
15:04:01 <bswartz> #topic broken gate
15:04:32 <bswartz> so the gate has been broken most of this week, due to changes in nova, neutron, and devstack (did I miss anything?)
15:04:53 <bswartz> thankfully it seems vponomaryov's latest patch has fixed it
15:05:34 <bswartz> but this week's events just highlights how vulnerable we are to changes in other projects affecting our CI
15:05:41 <mkoderer> bswartz: tempest? ;)
15:06:13 <bswartz> mkoderer: tempest was implicated but I think it was actually devstack's change to tempest options that sunk us
15:06:26 <mkoderer> bswartz: yeah that's correct
15:06:59 <gouthamr> the more tests we add, the more chances of the job being killed due to timeout.. generic driver.
15:07:06 <bswartz> in any case I want to remind people that we're trying to get new first party drivers done so we can use those for testing instead of the current generic driver with all of its dependencies
15:07:29 <bswartz> gouthamr: I don't think number of test is an issue (or at least it shouldn't be)
15:08:09 <gouthamr> it shouldn't be bswartz.. but there are nova timeouts on the gate that kill the entire job.
15:08:10 <mkoderer> what can we do to prevent such issues..? running manila test within other project won't be accepted I guess
15:08:29 <bswartz> please prioritize reviews of the the LVM and LXC/LXD drivers so we can get those merged and then share to move our gate tests to those drivers
15:08:41 <cknight> bswartz:  I've been testing the LVM driver as part of reviewing it.  It seems to work, but there are a few failing tests and many review comments.  So with Julia out until next week, it seems it will be a couple weeks before it can merge.  And it is solely a DHSS=False driver.
15:09:16 <bswartz> cknight: jvarlamova will be back next week and if she's quick the driver could get merged by Tuesday
15:09:34 <cknight> bswartz: Let's hope so.
15:09:42 <bswartz> realistically it will take a bit longer but I want everyone to be aware of the benefits of getting the new drivers in
15:10:05 <bswartz> the point of the new drivers is that they don't depend as much on external things so there's less chance of churn in other projects breaking our gate
15:10:26 <cknight> bswartz: And they should be vastly faster, so the number of tests shouldn't be an issue.
15:10:33 <bswartz> yeah that too
15:10:56 <cknight> bswartz: I think we promised the infra team we would lower our timeouts once the new drivers were ready.
15:11:06 <bswartz> I was worried that we would need to discuss extraordinary measures in the meeting today to get CI unbroken so I'm glad we can avoid that least
15:11:19 <vponomaryov1> cknight: 65 minutes as it was
15:11:27 <bswartz> but the risk still exists that new bugs in break us in the coming weeks
15:12:06 <bswartz> vponomaryov1: 3rd party drivers are able to run the tests in under 10 minutes (plus devstack time)
15:12:21 <tbarron> sorry to be catching up, but are both LVM and LXC/LXD drivers DHSS=False ?
15:12:26 <vponomaryov1> only 3rd party?
15:12:31 <bswartz> we should aim to get the first party drivers that fast
15:12:34 <cknight> tbarron: No, LXC is DHSS=True
15:12:43 <tbarron> cknight: cool, ty
15:12:50 <vponomaryov1> LXC tend to be both
15:13:25 <bswartz> okay that's all I had about the gate issues
15:13:54 <bswartz> thanks again to vponomaryov1 for fixing it (even though he's on holiday!)
15:14:08 <cknight> +1  Thanks, Valeriy!
15:14:11 <bswartz> #topic Midcycle meetup
15:14:16 <vponomaryov1> ))
15:14:21 <bswartz> #link https://wiki.openstack.org/wiki/Sprints/ManilaMitakaSprint
15:14:31 <bswartz> #link https://etherpad.openstack.org/p/manila-mitaka-midcycle
15:14:43 <bswartz> so the etherpad was empty until this morning
15:14:48 <bswartz> and I'm filling it out today
15:15:25 <bswartz> the facilities stuff here at NetApp is all sorted out for people attending in person
15:15:58 <bswartz> if you are attending in person please make sure I know you are so we can put you on the visitor list
15:16:32 <bswartz> we've gotten netapp to waive the usual NDA paperwork the visitors have to sign
15:17:05 <xyang> bswartz: does the wifi work?  I mean can you access IRC, etc
15:17:08 <bswartz> I'll be adding a lot more topics to the agenda over the next week
15:17:18 <bswartz> xyang: lol
15:17:18 <cknight> xyang: yes
15:17:31 <bswartz> IBM will never live down the austin midcycle will they?
15:17:31 <tbarron> xyang: the guest network always worked in the past, don't jinx it!
15:17:49 <tbarron> :-)
15:18:18 <bswartz> netapp has open wifi for guests -- some ports are blocked but you can get onto the internet easily and IRC should not be an issue
15:18:56 <bswartz> VPNs should work around any port blockage
15:19:13 * mkoderer is trying to organzie the next mid-cycle in Germany btw
15:19:26 <bswartz> honestly I've never understood the logic of blocking outgoing ports in a firewall
15:19:56 <gouthamr> mkoderer: also try getting lufthansa to sponsor :P
15:20:00 <bswartz> yes mkoderer is already thinking ahead to the summer (newton?) midcycle meetup
15:20:22 <mkoderer> gouthamr: :)
15:20:37 <toabctl> gouthamr: lufthansa usually doesn't fly. they tend to strike when you want to use them ;)
15:20:47 <mkoderer> yep maybe we can have a quick chat about it during this mid-cycle
15:20:54 <gouthamr> :D
15:21:02 <bswartz> mkoderer: do you have an etherpad where people can register their interest in traveling there?
15:21:17 <mkoderer> bswartz: I can setup one... sure
15:21:31 <bswartz> I suggest an etherpad or some other way to collect feedback about how many people want to travel and can get funding to travel
15:22:05 <mkoderer> yep, I need to know whos intressted and who has issues with travel founding
15:22:18 <bswartz> the cinder team is also considering a european site for their summer midcycle meetup
15:22:27 <bswartz> dublin was proposed
15:22:41 <mkoderer> cool :)
15:22:45 <bswartz> mkoderer: where exactly are you proposing?
15:22:52 <bswartz> do you know which city?
15:23:19 <mkoderer> bswartz: SAP has many locations... Headquater would be Walldorf near Heidelberg
15:23:46 <bswartz> I would recommend some place near a large airport hub because that would cut travel costs for everyone
15:23:47 <mkoderer> this would be best for me to organize everything
15:24:10 <toabctl> mkoderer: walldorf isn't a real city. I guess there's just SAP ;)
15:24:24 <mkoderer> bswartz: yep Frankfurt would be best.. I will find out what is possible
15:24:34 <bswartz> okay thanks mkoderer
15:24:46 <mkoderer> toabctl: :P
15:24:46 <bswartz> anyways, regarding the meetup next week, please suggest topics if you have them
15:24:54 <bswartz> I'll be adding mine
15:25:00 <bswartz> and we can always add stuff as we go
15:25:36 <bswartz> for remote participants the plan is to setup webex again and to have good quality audio (don't know about video)
15:26:09 <bswartz> if I can get a windows box I may try to setup video
15:26:34 <bswartz> (unfortunately webex + fedora linux = fail)
15:27:24 <bswartz> also, in case it's not obvious, we will cancel the weekly IRC meeting next week, as it would occur during the meetup
15:27:48 <bswartz> so the next IRC meeting will be the day of the mitaka-2 milestone release
15:28:07 <bswartz> #topic open discussion
15:28:16 <bswartz> that's all I had for today
15:28:44 <bswartz> welcome back from the holidays and for those still on holidays please stop working and enjoy them!
15:29:01 <dustins> good to be back
15:29:01 <vponomaryov1> bswartz: when it is planned to have agenda for topics of meetup?
15:29:23 <bswartz> oh and speaking of gate being fixed, we've gotten quite a backlog of changes that need review/merge
15:30:17 <bswartz> core reviewers please try to clear out at much review backlog as we can while the gate is functioning (goal being to merge everything ready to merge before M-2)
15:30:44 <bswartz> vponomaryov1: you're referring to a schedule of what we will discuss at what times?
15:30:50 <xyang> bswartz: is there a deadline to merge manila client changes?
15:31:02 <vponomaryov1> bswartz: what at what time
15:31:32 <tpsilva> I have a question about share extend and shrink
15:31:33 <bswartz> xyang: yes, as we learned during liberty, the client and other library projects are subject to the same feature freeze timelinesas manila proper
15:31:47 <xyang> ok
15:32:05 <bswartz> so we won't be able to get away with sneaking in UI or client features during M-4
15:32:46 <bswartz> vponomaryov1: I'm afraid the exact schedule will be somewhat flexible because new topics always get proposed at the last minute
15:32:57 <bswartz> but I'll do my best to have to mostly laid out by Monday
15:33:17 <bswartz> so remote attendees can plan their attendance times
15:33:38 <vponomaryov1> bswartz: ok, thank you
15:34:06 <bswartz> tpsilva: go ahead with your question
15:35:38 <bswartz> ?
15:35:40 <tpsilva> bswartz: when you extend a share and it fails on the driver, the api doesn't give you any errors...
15:36:03 <bswartz> well the extend operation (like most) is asynchronous
15:36:27 <bswartz> so the extend request should succeed unless the request itself was malformed
15:36:40 <bswartz> if the extend operation fails, that should be communicated to the user with a status change
15:37:08 <bswartz> oh requests can also immediately fail for administrative reasons (quota exceeded, etc)
15:37:35 <tpsilva> I see
15:37:39 <ganso> I was wondering if the scheduler could verify if there is space available for extending
15:38:02 <ganso> the scheduler has this information
15:38:10 <vponomaryov1> ganso: scheduler is not a member of extend operation
15:38:59 <cknight> ganso: also, the scheduler may be running somewhere else, so that would still be asynchronous
15:39:43 <ganso> cknight, vponomaryov1: I understand, thanks! :)
15:39:55 <bswartz> tpsilva: is that clear?
15:40:16 <tpsilva> yes, thank you
15:40:23 <bswartz> okay I think we're done for today
15:40:28 <bswartz> thanks all
15:40:41 <bswartz> #endmeeting