23:01:11 <pballand> #startmeeting CongressTeamMeeting
23:01:12 <openstack> Meeting started Tue Jul 28 23:01:11 2015 UTC and is due to finish in 60 minutes.  The chair is pballand. Information about MeetBot at http://wiki.debian.org/MeetBot.
23:01:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
23:01:16 <openstack> The meeting name has been set to 'congressteammeeting'
23:01:38 <pballand> thinrichs had a conflict this week, so will be running the meeting
23:02:31 <masahito> hi
23:02:33 <Yingxin1> :)
23:02:53 <zhenzanz> Good morning and good afternoon:-)
23:03:01 <pballand> there are a couple things on the agenda, but before I get to that, does anyone have somethign they want to add?
23:03:49 <masahito> nothing from me.
23:04:00 <pballand> ok, I’ll go with my items, and people can chime in after :)
23:04:26 <pballand> first item is meeting time - it looks like 5pm pacific works best for everyone, but Tuesday doens’t work
23:04:48 <pballand> so the plan is to stick with 5pm, but pick a new day
23:05:01 <pballand> here is a poll to voice your preference:
23:05:11 <pballand> #link http://doodle.com/5brc9vhggvtiipk3
23:05:18 <masahito> #topic Meetingtime
23:05:34 <pballand> masahito: thanks :)
23:06:01 <pballand> it would be really helpful if everyone could spend a few seconds to check days that work for them
23:06:12 <pballand> any questions or comments on meeting time?
23:06:33 <masahito> pballand:  ;)
23:07:00 <pballand> ok, moving on…
23:07:08 <pballand> #topic Tokyo summit talks
23:07:45 <pballand> Voting for talks closes this friday
23:08:10 <pballand> if you haven’t already, please take the time to express your preferences
23:08:41 <pballand> here are a couple talks that are related to congress:
23:09:03 <pballand> “Unifying Congress and Keystone Policies”
23:09:08 <pballand> #link https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/4388
23:09:22 <pballand> “Congress Hands On Lab”
23:09:27 <pballand> #link https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/4396
23:09:39 <pballand> “Telco usecase for Congress”
23:09:42 <pballand> #link https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/4617
23:10:13 <pballand> does anyone have other talks they want to point out?
23:11:06 <pballand> moving right along…
23:11:13 <pballand> #topic Midcycle sprint
23:11:36 <pballand> We are having a midcycle meetup / code sprint next week on Aug 6/7
23:11:54 <pballand> please RSVP if you are attending in person so we can get a headcount for food
23:12:06 <pballand> #link https://www.eventbrite.com/e/congress-liberty-midcycle-sprint-tickets-17654731778
23:12:47 <pballand> I know some people have expressed interest in attending remotely, which is great as well
23:13:04 <RuiChen> we can access it online?
23:13:48 <pballand> RuiChen: we will definitely communicate on IRC, and can set up a teleconference
23:14:01 <pballand> in the past, voice/video has been spotty, however
23:14:11 <RuiChen> cool
23:15:11 <pballand> our main focus is to crank on improving the message bus, so communication and code contributions will be helpful both in person and remote
23:15:21 <pballand> any other questions about the sprint?
23:16:08 <pballand> #topic Project milestones
23:16:31 <pballand> the Liberty-2 milestone is this week
23:16:45 <pballand> Liberty-3 and feature fress is Sept 1-3
23:17:23 <pballand> We have several changes that are targeted at Liberty-2.  Please update launchpad to reflect the current state of tasks you are working on.
23:17:49 <pballand> If the code is not already merged, retarget to Liberty-3
23:18:01 <RuiChen> get it
23:18:22 <zhenzanz> sorry, bp/action-listing may miss Liberty-2. The main reason is that we can't find an effective way to parse execution methods Congress would call
23:18:23 <pballand> thinrichs told me he would be working on retargetting blueprints
23:18:54 <zhenzanz> I did some work last week, novaclient has very good document for API
23:19:03 <zhenzanz> but neutronclient is terrible
23:19:56 <pballand> zhenzanz: good to know - sounds like you are making good progress despite the missed target
23:20:10 <zhenzanz> and it decorates all APIs with APIParamsCall so we cannot inspect the original function doc and args
23:21:30 <pballand> zhenzanz: are you blocked, or is there just more work to do than anticipated?
23:21:39 <zhenzanz> so we may merge the main logic at first
23:22:41 <zhenzanz> I think it's blocked if we want to go the parsing way.
23:24:07 <zhenzanz> or is it acceptable that we just list the API names if we cannot parse doc and args?
23:24:09 <masahito> zhenzanz: If we need some changes for neutron, I can ask neutron folks of it.
23:25:11 <zhenzanz> Thank you masahito. Maybe two things:
23:25:25 <pballand> masahito: it would be great to check with the Neutron team for a way to optimize this
23:25:31 <zhenzanz> 1. save original function info in the decorate
23:25:48 <pballand> #topic Status updates
23:25:57 <zhenzanz> 2. provides enough document for APIs and their arguments
23:26:52 <RuiChen> is there same issue for other clients, like: heatclient, cinderclient?
23:26:52 <masahito> ok. please tell me little details about the two things.
23:27:11 <masahito> 1. is it for neutronclient, right?
23:27:36 <zhenzanz> yes
23:28:00 <masahito> 2. The document means python document written in the codes, doesn't it?
23:28:08 <zhenzanz> I didn't try other client yet
23:28:24 <zhenzanz> yes, the inline doc in code
23:28:45 <zhenzanz> currently there is no doc for parameters
23:29:32 <masahito> got it. I'll tell him these.
23:29:47 <zhenzanz> thanks
23:30:19 <pballand> masahito, zhenzanz : thanks for working that out
23:30:54 <pballand> any other status updates?
23:31:35 <Yingxin1> yes, I have finished my first spec for rpc-for-dse, it's now in review state
23:31:56 <veena> pballand: bp python3 support is work in progress
23:32:19 <Yingxin1> masahito: thanks for reviewing, I've replied
23:33:28 <pballand> Yingxin1: thanks - will take a look
23:33:47 <Yingxin1> thank you
23:33:52 <pballand> veena: fantastic - how’s it going? any blockers or questions?
23:34:31 <masahito> Yingxin1: you're welcom. I'll check your replay.
23:35:19 <Yingxin1> masahito: :-D
23:35:25 <RuiChen> I working on bug/1473924, I can push a demo about refactor neutronv2 driver today, welcome to reveiwing
23:35:38 <veena> pballand: yeah, the build has failed with changing basetring to six.string_types. many test cases failed. I'll take a look.
23:36:07 <veena> pballand: couldn't check it yesterday
23:36:37 <pballand> veena: ok, glad you’re pushing forward
23:36:55 <pballand> RuiChen: great
23:37:06 <veena> pballand: Thanks
23:37:44 <pballand> speaking of test failures - how’s tempest stuff going?  Is everying passing after Zhenzan’s patch (https://review.openstack.org/#/c/203504/)
23:38:24 <pballand> it would be nice to enable gating on tempest again
23:38:25 <zhenzanz> I can pass all tempest cases in my environment
23:38:43 <zhenzanz> but my two tempest patches are still under review
23:39:44 <zhenzanz> https://review.openstack.org/#/c/202870/
23:39:51 <zhenzanz> https://review.openstack.org/#/c/203019/
23:41:58 <pballand> zhenzanz: thanks for the update - do  we need to ping some tempest cores to review?
23:42:53 <zhenzanz> I add Jordan Pittier, but progress is slow
23:45:16 <pballand> ok - if anyone has time to review and add some +1’s, maybe that will get their attention
23:45:39 <zhenzanz> thanks
23:45:55 <pballand> any other updates?
23:46:05 <masahito> I have
23:46:29 <masahito> I've been writing a new spec named 'policy-violation-history'
23:47:34 <pballand> masahito: cool - do you have a link?
23:47:56 <masahito> but there are some choices in its implementation, so it's hard to define changes in the spec.
23:48:26 <masahito> pballand: sorry, I've not submitted yes.
23:48:42 <masahito> not yes, but yet.
23:49:05 <pballand> masahito: there are placeholders for alternatives in the spec format - I would suggest picking whatever choice you are leaning toward, but be sure to fully document alternatives so others can voice their suggestions during review
23:49:36 <pballand> or, we can dicusss here or in #congress :-)
23:50:06 <pballand> (hard to discuss before seeing the spec though)
23:50:17 <masahito> I think so.
23:51:49 <masahito> I'll fully document in the spec and write a best change I think as definition. please wait few days.
23:52:01 <pballand> masahito: sounds great, thanks
23:52:13 <pballand> we have just a few minutes left - is there anything anyone else wants to cover?
23:52:21 <pballand> #topic Open Discussion
23:53:56 <pballand> ok, thanks everyone for participating
23:54:00 <zhenzanz> what's the working time for the sprint
23:54:08 <RuiChen> please help to review this patch https://review.openstack.org/#/c/205920/ , if it's merged, I finish the BP version-list-API, thanks
23:54:47 <pballand> zhenzanz: since the sprint is in Palo Alto, I expect most discussions will be between 9am - 5pm PDT
23:55:16 <pballand> code and reviews can be any time, of course
23:55:22 <zhenzanz> Got it, thanks. I'll try join remotely
23:55:25 <RuiChen> it's congressclient part code of this BP, congress part had been merged.
23:56:22 <pballand> RuiChen: will do
23:56:49 <RuiChen> pballand: thank you
23:56:56 <pballand> I expect thinrichs will want to update the meeting time and day again ASAP, so keep an eye on the mailing list and web page for next week’s time
23:58:58 <pballand> That’s it for this week, thanks for joining and have a great week!
23:59:03 <pballand> #endmeeting