00:00:16 <ekcs> #startmeeting congressteammeeting
00:00:17 <openstack> Meeting started Thu Feb 16 00:00:16 2017 UTC and is due to finish in 60 minutes.  The chair is ekcs. Information about MeetBot at http://wiki.debian.org/MeetBot.
00:00:18 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
00:00:20 <openstack> The meeting name has been set to 'congressteammeeting'
00:00:30 <ramineni_> Hi
00:00:39 <ekcs> Hi all! Hope everyone's having a great week.
00:01:11 <ekcs> topics today:
00:01:11 <ekcs> - Ocata release
00:01:13 <ekcs> - PTG discussions
00:01:13 <ekcs> - PTG activities
00:01:20 <ekcs> anything else to add?
00:01:51 <aimeeu> hi all - agenda lgtm
00:02:43 <ekcs> hi aimeeu
00:03:17 <ekcs> ok then. let’s dive right in.
00:03:22 <ekcs> #topic Ocata release
00:03:52 <ekcs> This week is the final week to issue new RC for Ocata.
00:04:13 <ekcs> are there any bugs or patches to talk about?
00:04:21 <ekcs> https://review.openstack.org/#/q/status:open+project:openstack/congress+branch:stable/ocata
00:04:26 <ekcs> https://bugs.launchpad.net/congress
00:06:03 <bryan_att> Hi all
00:06:18 <ekcs> hi bryan_att !
00:07:23 <ekcs> ramineni_: do you think this patch ready to merge? https://review.openstack.org/#/c/432173/
00:07:32 <thinrichs> I think the one change in stable/ocata is ready, except it doesn't have the test that the one in master does.
00:08:07 <ramineni_> I cherry-picked the test one to ocata also
00:08:46 <thinrichs> Oops—I see now.
00:09:43 <thinrichs> Shall we push it in then?
00:10:15 <ekcs> thinrichs: sounds good to me.=
00:10:15 <thinrichs> Maybe we should merge into master as well
00:10:23 <thinrichs> ramineni_: ?
00:10:31 <ramineni_> Yes
00:10:56 <thinrichs> Done
00:11:04 <ekcs> thanks!
00:11:07 <ekcs> unfortunately my progress has been slow on this bug. https://bugs.launchpad.net/congress/+bug/1662809
00:11:07 <openstack> Launchpad bug 1662809 in congress "500 error on nova datasource delete" [Critical,New]
00:11:07 <ekcs> I'd consider an important bug to fix, but not necessarily a release blocker. I'd still like to get a fix in this week, but if I don't succeed (50/50 at best at this point), I suggest we just document a workaround.
00:11:36 <ekcs> what do others think?
00:12:19 <thinrichs> final RC is due tomorrow?
00:13:06 <ekcs> thinrichs: yes 2/17
00:13:34 <ekcs> so we have about two days.
00:14:03 <thinrichs> If we don't have a fix in time, we document it and the workaround.  Then we release an update once we patch the problem.
00:14:29 <ekcs> +1
00:14:51 <thinrichs> For a time we had an option where you couldn't delete a datasource if there were rules that mentioned it in the body.
00:15:38 <masahito> hi. sorry late.
00:15:45 <ekcs> hi masahito
00:15:54 <thinrichs> masahito: hi
00:16:37 <ekcs> thinrichs: I see.
00:16:56 <ekcs> masahito: we’re talking about this bug.
00:17:08 <ekcs> https://bugs.launchpad.net/congress/+bug/1662809
00:17:08 <openstack> Launchpad bug 1662809 in congress "500 error on nova datasource delete" [Critical,New]
00:17:41 <ekcs> unfortunately we don’t have a fix yet. so if we can’t get a fix in, thinrichs and I were talking about documenting in the release and releasing an update later.
00:17:46 <thinrichs> I wonder if the datasource deletion is partially working, but then getting the error that says the datasource shouldn't be deleted by the PE, and not handling it properly.
00:18:38 <ekcs> thinrichs: possible. like maybe there is leftover code in the PE that tries to block the deletion?
00:20:37 <ekcs> well I’ll look into it some more. I think it’s an easy fix once the problem is pinpointed.
00:20:57 <ekcs> let’s move on then if there is no other ocata item to discuss?
00:22:36 <ekcs> ok.
00:22:38 <ekcs> #topic PTG discussions
00:23:36 <ekcs> big thanks to all who contributed or discussed topics to the etherpad. I think we’ll have plenty to talk about. #link https://etherpad.openstack.org/p/congress-ptg-pike
00:23:44 <ekcs> definitely feel free to continue.
00:25:33 <ekcs> To help us use the time at PTG efficiently, I suggested we volunteer to initiate the topics we want to start. What do you all think about that?
00:25:34 <ekcs> http://lists.openstack.org/pipermail/openstack-dev/2017-February/112204.html
00:27:15 <thinrichs> That's a good idea
00:27:22 <ekcs> oh concurrently, here is a rough proposed schedule for our two days. Any thoughts/comments/suggestions? http://lists.openstack.org/pipermail/openstack-dev/2017-February/112205.html
00:27:57 <ekcs> oh sorry thinrichs for jumping around.
00:29:03 <masahito> make sense.
00:30:20 <thinrichs> Just noticed the Dattalog enhancements section in the etherpad.  We added the CIDR math builtins in Ocata, so is that still a topic to cover?
00:32:21 <ekcs> thinrichs: I’m not sure there’s anything more to do there.
00:33:16 <ekcs> possible we can get some feedback on whether more is needed.
00:33:35 <thinrichs> The schedule seems fine.  We might want to keep a running list of priorities (or maybe relative priorities) as we discuss topics and then review/revisit/finalize those priorities in the last hour on Thu
00:34:07 <ekcs> thinrichs: yes absolutely. otherwise we’d forget all the important things from wednesday.
00:34:51 <thinrichs> As long as we treat it the schedule as fluid.  Have we ordered the topics in roughly priority order so that if we don't get to everything we only miss out on the least important items?
00:35:31 <thinrichs> The UI is going to be important for early users, so we might not want to leave that til the end.
00:35:46 <ekcs> thinrichs: we haven’t ordered the topics. I’d also suggested that we (+1 nick) the items we find important. so that can be a rough guide when we need to cut things out.
00:36:32 <thinrichs> ekcs: sounds good
00:37:17 <ekcs> thinrichs: I see. maybe we can start that discussion before lunch on thursday?
00:38:10 <ekcs> bryan_att: if you’re still around, which parts of which days do you expect to join us?
00:38:24 <ekcs> so we can consider that in setting the schedule.
00:38:31 <thinrichs> ekcs: I like your suggestion of people voting so we can see what's most important and then putting the least important things last
00:38:45 <bryan_att> I should be pretty flexible
00:38:58 <bryan_att> wed-thu, right?
00:39:04 <ekcs> bryan_att: yup.
00:39:34 <bryan_att> ok, so slot me in where you can, and I'll prepare some more details on the things we added to the etherpad
00:39:49 <ekcs> bryan_att: ok thanks
00:40:20 <ekcs> thinrichs: that makes sense. we may want more granularity then. +1 for important and +2 for very important?
00:40:40 <thinrichs> +1
00:40:56 <masahito> +1
00:41:03 <ekcs> haha. ok then.
00:41:32 <ekcs> anything on the topics we want to talk about now?
00:42:29 <ekcs> on the WSGI community-wide goal, we’re listed as potentially not conforming. https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html#current-state-anticipated-impact
00:43:15 <ekcs> I’m not sure yet exactly what we need to do to conform or maybe we already do it’s just not obvious because we don’t use one of the standard implementations.
00:45:13 <ekcs> ok let’s move on then if we don’t have anything we need to discuss right now.
00:45:22 <ramineni_> I'll try to look into it
00:45:45 <ekcs> thanks ramineni_ !
00:46:44 <ekcs> ok.
00:46:51 <ekcs> let’s go straight to open discussion.
00:46:59 <ekcs> #topic open discussion
00:47:24 <ekcs> we can talk about PTG activities or anything else.
00:48:42 <ekcs> We’re all set for Thursday dinner at 7PM at R. Thomas Deluxe Grill?
00:49:20 <ramineni_> How are we planning to communicate over there .. IRC
00:49:26 <ramineni_> ?
00:50:10 <thinrichs> ekcs: yep—reservation is under my name for 7p on Thu.
00:50:40 <thinrichs> ramineni_: does text messaging work for everyone?
00:50:51 <thinrichs> If not, anyone have an IRC phone app to recommend?
00:51:15 <aimeeu> irccloud
00:51:17 <ekcs> ramineni_: IRC kind of worked in barcelona. aimeeu recommended IRCcloud
00:51:51 <ramineni_> Ya .. Already have that on phone
00:52:31 <ramineni_> Sounds good to me
00:52:33 <ekcs> I think there is a small fee for being perpetually signed in (otherwise in free version you’re dropped after two hours of inactivity and won’t get new messages), but there is a free trial period.
00:53:58 <aimeeu> slack is another option, or groupme
00:54:17 <masahito> or google hangout
00:54:19 <aimeeu> the women of openstack use groupme - no issues at past summits
00:55:22 <ekcs> hahaha.
00:55:52 <ramineni_> +1 for Slack , hangout  , haven't used groupme though
00:57:03 <masahito> me too. I haven't used groupme. +1 for Slack, hangout or IRC.
00:57:32 <ekcs> I’d say if people don’t mind paying the $5 to sign up for IRCcloud for a month, we can use that because it’s most accessible to new people we don’t know.
00:57:51 <ekcs> but if that’s a problem, then slack sounds good.
00:59:46 <ekcs> ok well time’s up =)
01:00:06 <ekcs> see you all at PTG next week.
01:00:07 <masahito> ekcs: that's no problem for me :)
01:00:19 <ekcs> oh i guess that mean we should cancel meeting. I’ll announce on ML.
01:00:52 <thinrichs> See you all next week!
01:00:58 <ekcs> ok thanks all and have a great week/weekend!
01:01:04 <ekcs> #endmeeting