15:00:53 <gouthamr> #startmeeting manila
15:00:54 <openstack> Meeting started Thu Oct  3 15:00:53 2019 UTC and is due to finish in 60 minutes.  The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:55 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:57 <openstack> The meeting name has been set to 'manila'
15:00:59 <lseki> \o.
15:01:06 <gouthamr> courtesy ping: gouthamr xyang toabctl bswartz ganso erlon tpsilva vkmc amito jgrosso dviroel lseki carloss tbarron
15:01:15 <dviroel> o/
15:01:17 <gouthamr> got to update that list, haven't i ^
15:01:17 <amito> .o/ hello
15:01:20 <carloss> hi :)
15:01:21 <xyang> hi
15:01:30 <gouthamr> Hello everyone! \o/
15:01:41 <ganso> o/
15:01:52 <tbarron> hi
15:02:02 <gouthamr> #link: https://wiki.openstack.org/wiki/Manila/Meetings - Meeting agenda
15:02:13 <bswartz> .o/
15:02:52 <gouthamr> Ignore the date on the page - it's third october 2019 everywhere in the world i think
15:03:09 <gouthamr> we've most people here, lets get started! :)
15:03:16 <gouthamr> #topic Announcements
15:03:32 <gouthamr> First off, the Ussuri cycle Schedule is live
15:03:45 <gouthamr> if you haven't had a chance, take a look:
15:03:46 <gouthamr> #link: https://releases.openstack.org/ussuri/schedule.html
15:04:07 <gouthamr> Yesterday, i started a review to propose manila specific deadlines:
15:04:13 <gouthamr> #link: https://review.opendev.org/#/c/686303/
15:04:44 <gouthamr> ^ thank you tbarron, dviroel for taking a look already..
15:04:48 <jgrosso> https://governance.openstack.org/tc/goals/ussuri/index.html  does not work
15:05:24 <jgrosso> for the community wide goals for Ussuri
15:05:27 <gouthamr> jgrosso: ack, that page will start to function if one of the goals merges i think
15:05:38 <jgrosso> gouthamr ack thanks !
15:05:59 <gouthamr> right now, they're still being deliberated
15:06:06 <jgrosso> makes sense
15:06:08 <gouthamr> #link: https://etherpad.openstack.org/p/PVG-u-series-goals - Goals etherpad
15:06:53 <jgrosso> Set up storyboard for tracking :)
15:07:12 <gouthamr> if you're lazy like me, please see the o/p for the schedule including manila deadlines here: https://f5099681efe8f43a08c5-01a74348816d1fa0c2c779804dc21128.ssl.cf2.rackcdn.com/686303/1/check/openstack-tox-docs/e5405bc/docs/ussuri/schedule.html
15:08:01 <tbarron> note that gouthamr's review is putting *manila* stuff on this schedule, stuff like the
15:08:04 <vkmc> o/
15:08:10 <tbarron> general ussuri goals is already there
15:08:31 <tbarron> so we need to think about the dates and definitions of the manila stuff
15:08:56 * gouthamr passes vkmc coffee+alfajores, welcome
15:09:07 <gouthamr> tbarron +1
15:09:09 <tbarron> on the definitions he corrected an unintended innovation in the last cycle where
15:09:26 <tbarron> we said doc needed to be ready at feature proposal freeze
15:09:29 * gouthamr docs are an unintended innovation indeed :)
15:09:35 <tbarron> it doesn't need to be ready then
15:09:51 <vkmc> :D
15:10:02 <tbarron> and he has an intended innovation this time which he should explain to us :)
15:10:10 <gouthamr> haha, yes
15:10:28 <gouthamr> didn't mean to confuse you all
15:10:38 <tbarron> the dates look OK to me but i celebrate typical 'murican holidays so others should check!
15:10:43 <gouthamr> i added new language under the "manila feature freeze" deadline
15:10:47 <gouthamr> #link: https://f5099681efe8f43a08c5-01a74348816d1fa0c2c779804dc21128.ssl.cf2.rackcdn.com/686303/1/check/openstack-tox-docs/e5405bc/docs/ussuri/schedule.html#u-manila-ffreeze
15:11:03 <gouthamr> currently says "All new Manila features must be merged by the end of the week. Any new API changes must be accounted for in the OpenStack Dashboard plugin (manila-ui) and the SDK/CLI components of python-manilaclient."
15:11:45 <tbarron> Note that no other projects to my knowledge define their own feature freeze deadline, manila is spearheading :)
15:12:03 <tbarron> Does everyone understand what "must be accounted for" means?
15:12:27 <gouthamr> what i meant was if you're making manila API changes that affect the clients (manila-ui, python-manilaclient), and you have client changes in flight - these *have* to merge at the feature freeze deadline, because the clients will be released then
15:12:34 * tbarron made a private todo item for himself to add his api change to the ui someday :)
15:12:53 <gouthamr> we maintain backwards/forwards compatible clients
15:13:09 <tbarron> don't we have enought ui tech debt that this might be a challenging (but desirable) requirement?
15:13:22 <gouthamr> so, if your API changes aren't reflected in the client, it's not the end of the world - but,
15:13:48 <gouthamr> since there may be other services and downstream consumers - clients do get released much earlier than the manila service project
15:14:39 <gouthamr> so, if you'd like to have your changes in the clients for the Ussuri release, we must try and get them to merge before/at Feature Freeze
15:15:10 <tbarron> ah, so it's *if* you have client or ui changes and want to get them in this relase, then ....
15:15:26 <tbarron> not *you must have corresponding client and ui changes*
15:15:32 <gouthamr> yes
15:15:38 <dviroel> =)
15:15:59 <tbarron> k, refinement of language can be done in the review ...
15:16:05 <tbarron> thanks for explaining
15:16:44 <gouthamr> afair, we've always tried to maintain full feature coverage atleast with python-manilaclient
15:17:20 <tbarron> yeah with client and not at all with ui
15:17:21 <gouthamr> we have the same desire for manila-ui, but, like tbarron said, we've accrued a lot of tech-debt now
15:18:13 <gouthamr> dviroel tbarron: i'll respond to your comments after this meeting, thank you for bringing this up :)
15:18:17 <tbarron> and hopefully soon osc client will be in the mix
15:18:27 <gouthamr> ^ +1
15:18:38 <dviroel> gouthamr: ok
15:18:54 <gouthamr> alright, next announcement
15:19:13 <gouthamr> I've a new Core team addition proposed on the openstack-discuss mailing list
15:19:16 <gouthamr> #link: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/009910.html
15:19:31 <gouthamr> thank you ganso xyang tbarron amito for responding
15:19:37 <lseki> 🎉
15:19:46 <dviroel> :)
15:20:14 * gouthamr ^ he's smiling now, but soon...
15:20:26 <amito> lol
15:20:29 <xyang> Congrats dviroel!
15:20:31 <carloss> haha
15:20:32 <dviroel> :|
15:20:38 <carloss> congrats dviroel
15:20:56 <dviroel> xyang carloss ty
15:20:57 <gouthamr> please respond to this proposal
15:20:58 <bswartz> :-D
15:21:08 <gouthamr> and we'll go ahead and formalize it if we have consensus
15:21:31 <bswartz> I'm not on the ML for some reason. I guess because they renamed it
15:21:41 * bswartz goes to fix ML subscription
15:21:48 <gouthamr> bswartz: ah, that was like a year ago man :D
15:22:00 <bswartz> That explains the less amount of email I get about openstack
15:22:07 <gouthamr> lol
15:22:11 <dviroel> lol
15:22:59 <gouthamr> okay folks anything else that you'd like to announce?
15:23:13 <jgrosso> Hockey Season has started!
15:23:14 <jgrosso> :)
15:23:32 <jgrosso> wrong channel
15:23:34 <jgrosso> sorry
15:23:37 <gouthamr> jgrosso: nice, it's a bye week for Clemson, so maybe i'll watch some
15:23:47 <jgrosso> gouthamr ack ;)
15:23:47 <vhari> jgrosso: :)
15:23:50 <gouthamr> #topic: How are our release candidates faring?
15:24:04 <gouthamr> again, typo - we only have one release candidate
15:24:25 <gouthamr> that's RC1 that we cut for manila over a week ago
15:25:13 <gouthamr> i hope you'll are testing, packaging this - if you find any release critical bugs, please file them and tag them with "train-rc-potential"
15:25:30 <tbarron> so far we're doing a pretty good job keeping the trajectory bswartz started of not having a lot of release time drama
15:25:41 <gouthamr> +1
15:26:29 <gouthamr> the official release is still nearly a couple of weeks away
15:26:37 <bswartz> Email subscription fixed, now to fix my filters
15:26:42 <gouthamr> so, please keep testing
15:26:58 <gouthamr> nice bswartz!
15:27:18 <gouthamr> +rule: from:gouthamr set: priority +100 kthxbye
15:27:28 <gouthamr> #topic Tempest test breakage (dviroel)
15:27:51 <gouthamr> ^ i added dviroel's name on this since he's driving this
15:27:59 <gouthamr> #link: https://bugs.launchpad.net/tempest/+bug/1846236
15:27:59 <openstack> Launchpad bug 1846236 in tempest "User credentials not being released when skipException is raised on resource_setup()" [Undecided,Fix released] - Assigned to Douglas Viroel (dviroel)
15:27:59 <gouthamr> #link: https://review.opendev.org/#/c/686008/
15:28:33 <gouthamr> last week, a new release of tempest shipped with this bug ^ and manila-tempest-plugin broke
15:28:51 <gouthamr> we've since fixed this bug, thanks dviroel for filing and fixing it!
15:29:29 <gouthamr> i was wondering if we needed to request a new release of tempest?
15:29:30 <dviroel> gouthamr: yw
15:30:36 <dviroel> gouthamr: i guess so
15:31:11 <gouthamr> dviroel: okay, you can either propose it and add gmann to the review for guidance
15:31:22 <gouthamr> dviroel: or ask directly on the review page
15:31:34 <dviroel> gouthamr: ack
15:32:05 <gouthamr> dviroel: Although there is this one
15:32:13 <gouthamr> #link https://review.opendev.org/#/c/685406/ - Tempest release for train cycle
15:32:46 <gouthamr> dviroel: we can use that review possibly
15:32:55 <gouthamr> let's coordinate with gmann
15:33:06 <dviroel> gouthamr: sure, will do
15:33:07 <gouthamr> that's all i had wrt the topic
15:33:30 <gouthamr> if you see any CI jobs misbehaving, get hold of our new tempest/CI expert, dviroel
15:33:41 <gouthamr> thank you dviroel
15:34:25 <gouthamr> #topic Python3 for third party CI
15:34:40 <tbarron> thanks for your expertise dviroel
15:34:55 <dviroel> gouthamr: tbarron thanks
15:34:59 <bswartz> If I drop connection, it's because thunderbird crashed my computer trying to clean up my openstack mail folders (45000 unread messages)
15:35:07 <gouthamr> i added this $topic back to check on the third party CI
15:35:09 <gouthamr> omg bswartz
15:35:23 <tbarron> everybody send bswartz mail, he feels lonely
15:35:27 <lseki> lol
15:35:46 <jgrosso> :)
15:35:57 <tbarron> bswartz thought openstack was dead and everyone has moved to k8s
15:36:37 <gouthamr> 45k "we miss you, come back" messages later
15:36:42 <tbarron> IAAS and hard multi-tenancy neeeds will never die
15:37:17 <gouthamr> amito: did you have an update regarding $topic
15:37:55 <gouthamr> dviroel: i recall you shared a spreadsheet recently regarding third party CI coverage for DHSS=True
15:37:56 <amito> Yep,
15:38:08 <amito> Our CI now runs on py3
15:38:20 <dviroel> gouthamr: yes, regarding subnets patches
15:38:34 <gouthamr> amito: oh nice, that's a good-kinda update
15:38:51 <dviroel> gouthamr: need to look for it, will be good to update it also
15:38:56 <gouthamr> dviroel: i wonder if we should make one for this mission
15:39:14 <amito> gouthamr:We've had some failures lately, but I don't think it's related to the py3 change
15:39:22 <amito> arrgh
15:39:23 <gouthamr> dviroel: we can audit the ones that report right now and alert those folks if they haven't been listening on the ML or to these meetings
15:39:46 <gouthamr> amito: oh - one of them could definitely be https://bugs.launchpad.net/tempest/+bug/1846236
15:39:46 <openstack> Launchpad bug 1846236 in tempest "User credentials not being released when skipException is raised on resource_setup()" [Undecided,Fix released] - Assigned to Douglas Viroel (dviroel)
15:40:07 <gouthamr> dviroel was using the infinidat CI logs to work through that bug
15:40:08 <dviroel> gouthamr: yes, wont be that hard to do the audit
15:40:27 <amito> gouthamr: yep, it was definitely credentials related
15:40:36 <gouthamr> awesome, dviroel - let's start a collaborative sheet and do that together
15:40:39 <dviroel> amito: was affecting NetApp CI and Infinibox CIs
15:40:47 <dviroel> gouthamr: ok
15:41:21 <gouthamr> amito: ack, should be fixed now
15:41:22 <gouthamr> thanks dviroel, lets connect after this meeting
15:41:31 <gouthamr> any other third party CI updates?
15:41:34 <amito> dviroel: thanks
15:41:40 <dviroel> amito: np
15:41:48 <gouthamr> #topic: Ussuri PTG Planning
15:42:28 <gouthamr> as you're all aware, the community is going to be meeting for the Open Infrastructure Summit + Forum + PTG event in Shanghai next month
15:42:43 <gouthamr> #link: https://www.openstack.org/summit/shanghai-2019/
15:43:02 <gouthamr> #link https://www.openstack.org/ptg/
15:43:18 <gouthamr> PTG = Project Technical Gathering
15:43:42 <gouthamr> this is typically the forum where we meet face-to-face and discuss project plans for the next cycle
15:44:06 <gouthamr> thanks tbarron for creating the planning etherpad
15:44:10 <gouthamr> #link: https://etherpad.openstack.org/p/manila-shanghai-ptg-planning PTG Planning Etherpad
15:45:11 <gouthamr> we're a month away from the event, lets gather all topics on that etherpad
15:46:14 <gouthamr> i'd ask you not to prioritize any topics - we've taken all sorts of things to discussions in the past, and the output has been amazing
15:46:47 <gouthamr> so don't hold back, if you thought that something was a minor discussion point
15:47:07 <gouthamr> i've done that in the past, and we've had healthy two hour discussions on such things
15:47:11 <gouthamr> ask jgrosso
15:47:16 <bswartz> PTG is in shanghai this cycle right?
15:47:17 <jgrosso> :)
15:47:29 <bswartz> That's going to cause serious timezone issues for remote attendees
15:47:38 <gouthamr> that's true
15:47:54 <gouthamr> sees a tbarronuo typing away
15:48:02 <tbarron> hmm
15:48:21 <bswartz> I worry that remote attendance might not even be possible
15:48:33 <tbarron> we may have a follow up remotee ptg as well
15:48:36 <gouthamr> bswartz: true
15:48:44 <bswartz> Are you going to have to deal with the so-called "great firewall" of china?
15:48:56 <tbarron> bswartz: that is an open question
15:49:07 <gouthamr> at present, i think we don't know what the connectivity is going to be like
15:49:09 <tbarron> asked and not settled yet
15:49:24 <tbarron> and our PTL will be remote this time
15:49:36 <bswartz> Which PTL?
15:49:40 <gouthamr> tbarron and vkmc are traveling, and it's possible they won't have their work machines with them
15:49:40 <tbarron> so PTG will be a bit of an experiment
15:49:55 <gouthamr> this one
15:50:10 <bswartz> gouthamr won't be there?
15:50:18 <tbarron> our first priority will be to use it as meet-greet with any APAC folks who haven't had the
15:50:26 <tbarron> opportunity to participate in Manila
15:50:28 <bswartz> Oy
15:50:32 <gouthamr> yeah, unfortunately won't be there in person
15:50:49 <lseki> 12:49:41 <gouthamr> it's possible they won't have their work machines with them
15:50:49 <lseki> hmm why not?
15:50:52 <bswartz> Your timezone will be less far off than mine if you do attend remotely
15:51:07 <tbarron> understand needs, show our PTG topics, solicit reactions, etc.
15:51:08 <gouthamr> tbarron will continue to lead this one, and i'll be hoping to join remotely if we can figure out how/what
15:51:18 <gouthamr> bswartz: +1
15:51:30 <tbarron> lseki: company issues, can discuss offline
15:52:22 <gouthamr> let's fill out the etherpad, and then arrange topics
15:52:23 <lseki> tbarron: ok
15:52:45 <dviroel> and we'll need a new coke can
15:52:46 <gouthamr> at present, i agree we will try and plan a day of remote PTG
15:52:52 <carloss> dviroel ++
15:52:55 <gouthamr> as we have decided to do in the past
15:53:21 <gouthamr> ooh we don't have yours anymore, dviroel?
15:53:37 <gouthamr> coke can - speaker we used to connect our room to Bluejeans in Denver for the last PTG
15:53:52 <dviroel> gouthamr: erlon was the owner of that one
15:53:58 <gouthamr> ah that guy
15:54:24 <carloss> gouthamr: we still have the camera
15:54:25 <gouthamr> okay, we'll figure out AV too
15:55:06 <tbarron> now that we've planted these folks at canonical maybe canonical will contribute to manila
15:55:13 <gouthamr> logistical issues aside, we will have a remote PTG to look forward to, in friendlier timezones to our audience
15:55:29 <gouthamr> current audience*
15:55:35 <carloss> tbarron ++
15:55:39 <dviroel> tbarron++
15:55:45 <lseki> tbarron++
15:55:57 <gouthamr> Shanghai is a great opportunity for us to touch base with and revive our APAC contributors
15:56:11 <gouthamr> and that will be the focus of the meetings there, like tbarron mentioned
15:57:31 <gouthamr> based off the topics we gather, we can make our plans for the Shanghai PTG and the remote one in a West friendly timezone
15:57:50 * gouthamr looks at clock - eek
15:57:57 <jgrosso> :9
15:58:02 <gouthamr> anything else on $topic
15:58:02 <jgrosso> :(
15:58:07 * bswartz lights a fire under gouthamr
15:58:22 * gouthamr books flight ticket to Boston
15:58:39 <gouthamr> sorry jgrosso, skipping you two weeks in a row now
15:59:02 <jgrosso> I leave manila team and they toss you out :(
15:59:09 <jgrosso> I see how it is ;)
15:59:17 <gouthamr> er, he lies ^
15:59:24 <jgrosso> gouthamr no worries :)
15:59:26 <tbarron> he will never get away
15:59:31 <jgrosso> haha
15:59:38 <gouthamr> #topic Open Discussion
15:59:50 <tbarron> he'll be testing manila in real context, system tests
15:59:56 <jgrosso> :)
16:00:02 <gouthamr> So, why on earth is Alabama #1 again, who did they even play
16:00:13 <gouthamr> oh, sorry, manila related, everyone
16:00:24 <gouthamr> end of our meeting
16:00:31 <tbarron> cya
16:00:32 <lseki> \o
16:00:35 <carloss> bye :)
16:00:37 <gouthamr> please hop on to #openstack-manila if you have anything to discuss right away
16:00:37 <dviroel> thanks
16:00:41 <gouthamr> thank you all
16:00:41 <jgrosso> bye
16:00:43 <gouthamr> #endmeeting