00:00:55 <thinrichs> #startmeeting CongressTeamMeeting
00:00:56 <openstack> Meeting started Thu Aug 27 00:00:55 2015 UTC and is due to finish in 60 minutes.  The chair is thinrichs. Information about MeetBot at http://wiki.debian.org/MeetBot.
00:00:57 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
00:00:59 <openstack> The meeting name has been set to 'congressteammeeting'
00:01:12 <pballand> hi
00:01:15 <masahito> hi
00:01:29 <thinrichs> pballand, masahito: hi
00:01:47 <RuiChen> hi
00:01:48 <thinrichs> Main agenda items from me:
00:01:51 <Yingxin1> hi
00:01:55 <thinrichs> 1. Summit details
00:02:07 <thinrichs> 2. Tempest tests in gate
00:02:16 <thinrichs> 3. Status reports
00:02:19 <thinrichs> Anything else?
00:02:25 <thinrichs> RuiChen, Yingxin1: hi
00:03:35 <thinrichs> Ok; let us know if something else should go on the agenda.
00:03:40 <thinrichs> #topic summit
00:03:55 <thinrichs> The schedule for the Tokyo summit is out.
00:04:07 <thinrichs> #link 	•	https://www.openstack.org/summit/tokyo-2015/schedule/
00:04:26 <thinrichs> We had 1 talk accepted (that I know of): the Hands On Lab
00:05:15 <masahito> sounds good!
00:06:12 <veena> Hi
00:06:24 <thinrichs> If you search for congress on the schedule, you can see a new policy platform called Sentinel.
00:06:42 <thinrichs> I *just* saw this and don't know anything about it.
00:08:01 <thinrichs> veena: hi.  We're going over details about the upcoming summit.
00:08:13 <thinrichs> Sentinel looks to be a Congress-like thing that eBay built.
00:08:29 <veena> thinrichs: okay
00:08:49 <thinrichs> Reminder to book your hotel rooms.
00:08:50 <pballand> hmm, they seem to be at the same time too :(
00:09:41 <thinrichs> pballand: :( What are the chances?
00:10:08 <thinrichs> We should reach out to those folks and talk before the summit, I'd think.
00:10:08 <pballand> thinrichs: seems we may want to talk to the organizer about that… those interested in policy are going to have trouble
00:10:28 <thinrichs> pballand: good thought.  I'll look into it.
00:10:29 <pballand> I expect there still should be time to fix the schedule
00:10:52 <thinrichs> #action thinrichs will ask summit organizers about moving Sentinel and Congress to different time slots
00:12:25 <thinrichs> I'll also reach out to the Sentinel team to see if I can get some info before the summit.
00:12:34 <thinrichs> #action thinrichs will reach out to Sentinel team
00:13:57 <thinrichs> Has anyone received emails about being Active contributors because of your work in Congress
00:14:10 <thinrichs> ?
00:14:28 <veena> thinrichs: yes, I recieved and got the free entry pass for summit
00:14:30 <pballand> I got an ATC badge, which I assume is related to Congress
00:14:34 <masahito> I've received.
00:15:25 <thinrichs> I got a free pass for being on the HOL talk, but no ATC email.
00:16:06 <thinrichs> If anyone that's pushed code to Congress hasn't gotten a free registration, let me know.
00:17:28 <RuiChen> I get it, but some conflict with my other work, so I can't join tokyo summit :(
00:17:53 <thinrichs> pballand: ayip put the HOL talk proposal together.  Is VMware planning to provide machines like the last HOL?
00:18:00 <masahito> thinrichs: I think your registered email address is different between gerrit and openstack foundation.
00:18:31 <thinrichs> masahito: I tried to fix all that, but you may be right.
00:18:48 <pballand> thinrichs: ayip hasn’t told me anything about it...
00:18:51 <thinrichs> RuiChen: sorry you won't make it.  :(  Maybe next time!
00:19:20 <pballand> I can ping him about it
00:19:35 <pballand> #action pballand Check with ayip on infrastructure for HOL
00:19:48 <thinrichs> pballand: that'd be great.  If VMware doesn't have the machines we'll need to figure out how to run the lab.
00:20:29 <thinrichs> We also need to decide on room requests for the design summit.
00:20:38 <thinrichs> In Vancouver we had 2 small rooms and 1 large room.
00:20:51 <thinrichs> They say there's less space in Tokyo and there are more teams requesting rooms.
00:21:02 <thinrichs> It's easier to get small rooms than large rooms.
00:21:12 <thinrichs> Any opinions on what we should request?
00:22:10 <pballand> I’d rather have more meetings in small rooms than fewere in large rooms
00:22:32 <masahito> It seems to be better to use small room to discuss features.
00:23:10 <thinrichs> We could try to ask for 4 small rooms and 0 large rooms.
00:23:24 <thinrichs> (I agree the large room wasn't so useful last time.)
00:23:39 <masahito> because we were able to discuss face to face in Vancouver at small rooms.
00:24:09 <thinrichs> I also felt the time went really fast in the small rooms, which is why I proposed 4.
00:24:27 <thinrichs> If we asked for a large room, any thoughts on what we would discuss?
00:24:47 <thinrichs> Something that we'd want feedback from a larger audience on.
00:25:51 <veena> thinrichs: I had applied for travel fund, but didn't get it :( not sure if I can make it.
00:26:14 <masahito> It could get feedback or attention for Congress itself in large rooms?
00:26:41 <thinrichs> veena: sorry that didn't work out.  Maybe try again for Austin (the next summit)?
00:26:53 <veena> thinrichs: Sure
00:27:07 <thinrichs> masahito: what would the topic be that might draw people in?
00:28:30 <masahito> thinrichs: it might be use-cases of in production deployment if there exists.
00:29:04 <thinrichs> masahito: none in production that I know of.
00:29:43 <masahito> thinrichs: hmm.. sorry, I couldn't help you ;(
00:30:12 <thinrichs> It sounds like we don't have a good use in mind for a large room.
00:30:19 <thinrichs> So we'll go with several smaller rooms.
00:30:32 <thinrichs> 4 seems good, and they can give us less if they need to.
00:30:40 <thinrichs> Is anyone going to be around Friday?
00:30:54 <thinrichs> I'm planning to fly out at 5p or so.
00:31:06 <thinrichs> We can request space on Friday too.
00:31:51 <masahito> thinrichs: which airport do you plan to use?
00:32:09 <thinrichs> Not sure yet—there are more flights into the farther one.
00:32:11 <pballand> I’ll likely be heading out friday afternoon
00:32:24 <pballand> but don’t have flights yet
00:32:51 <masahito> thinrichs: ok. it's reminder. If you use Narita, you need to leave summit place at noon to get flight at 5pm.
00:33:31 <thinrichs> masahito: thanks!  That's helpful.
00:34:14 <thinrichs> I'm happy to meet up Friday morning, but I won't request a room unless someone else thinks it's a good idea.
00:34:28 <thinrichs> And is planning on meeting up Friday morning.
00:35:53 <thinrichs> Ok.  I'll skip requesting a room on Friday.
00:36:02 <thinrichs> We can meet up somewhere if we want to.
00:36:09 <pballand> +1 for avoiding Friday if possible
00:36:32 <thinrichs> Moving on to the next topic.
00:36:42 <thinrichs> #topic Tempest tests in gate
00:37:04 <thinrichs> I ended up disabling all of the datasource driver tempest tests.
00:37:14 <thinrichs> Now it seems to be consistently green.
00:37:28 <thinrichs> And I've started running tempest tests before merging code.
00:37:40 <thinrichs> (To do that, enter "check experimental" into a comment.)
00:37:59 <thinrichs> There's a patch under review for moving those tests to the gate
00:38:09 <thinrichs> so that every time code gets merged those tests need to pass
00:38:35 <pballand> yay!
00:38:46 <masahito> great!
00:39:03 <RuiChen> cool
00:39:59 <masahito> Should I +1 for the patch moving tempest tests to the gate?
00:40:28 <thinrichs> The infra team needs to +2 the patch.  I'll ping them tomorrow if it hasn't happened.
00:41:01 <masahito> got it.
00:41:04 <thinrichs> The test coverage is pretty poor at this point, but at least we'll know we're not breaking basic devstack integration.
00:41:36 <thinrichs> Let's move on to status updates, with our remaining 20 minutes
00:41:38 <thinrichs> #topic status
00:41:47 <thinrichs> pballand: want to start?
00:42:27 <pballand> sure
00:42:41 <pballand> unfortunately not as much to report as I wanted
00:42:58 <pballand> I have a distributed DSE base class that I am working on
00:43:05 <pballand> to test out ideas in the spec
00:43:21 <pballand> I expect to be pushing a revised version of the spec in the next day or two
00:43:54 <pballand> the code will be a bit further out as I get some of the kinks worked out
00:43:59 <pballand> that’s it for me
00:44:11 <thinrichs> pballand: thanks
00:44:24 <thinrichs> pballand: any idea when you'll have a first cut at the base class pushed to review?
00:44:43 <thinrichs> There's still enough for other people to do without seeing it,
00:45:25 <thinrichs> but at some point soon it'll be helpful to see the basic methods provided by the base class
00:45:32 <thinrichs> Even if they're not fully baked.
00:45:41 <pballand> my hope is to have some eyes on it before next week’s meeting
00:47:08 <thinrichs> pballand: nice!
00:47:16 <thinrichs> We're looking forward to it.
00:47:31 <thinrichs> RuiChen: want to go next?
00:47:39 <RuiChen> ok
00:48:06 <RuiChen> I'm still working on bug 1473924
00:48:07 <openstack> bug 1473924 in congress "datasource-row-list API raise 400 exception when thread switching occur in update_from_datasource()" [Undecided,In progress] https://launchpad.net/bugs/1473924 - Assigned to Rui Chen (kiwik-chenrui)
00:48:28 <RuiChen> start to do refactor for other datasource drivers
00:48:48 <RuiChen> I will push the patch to gerrit in next one or two days
00:49:09 <thinrichs> RuiChen: great!  do you need anything from us?
00:49:22 <RuiChen> no, thank you
00:49:28 <thinrichs> masahito: want to go next?
00:49:35 <masahito> ok
00:50:09 <masahito> I'm working on dist-api-* of schema, table, row model now
00:50:56 <masahito> I pushed a first commit for schema model.
00:51:30 <masahito> I'll push rest 2 models in 2 or 3 days.
00:51:41 <thinrichs> masahito: I haven't had a chance to look at that change yet.  Hopefully tomorrow morning.
00:52:03 <thinrichs> Running short on time…
00:52:06 <masahito> thinrichs: ok
00:52:11 <masahito> it's my updates.
00:52:14 <thinrichs> veena: want to do a status update?
00:53:20 <veena> thinrichs: I see that there are syntax errors
00:53:35 <veena> thinrichs: which do not comply with py3
00:54:11 <veena> thinrichs: but most are in third party. Should I take up that work and fix it?
00:54:31 <thinrichs> veena: leave thirdparty alone I'd say.  Get everything else working.
00:54:45 <thinrichs> We need to decide what to do with the thirdparty stuff—we might move it out of our repo.
00:55:00 <veena> thinrichs: okay
00:55:02 <thinrichs> Yingxin1: status update?
00:55:07 <Yingxin1> yes
00:55:35 <Yingxin1> I'm working on schema conflict check on bug 1484015
00:55:36 <openstack> bug 1484015 in congress "policy rule head can have conflict definations" [Undecided,In progress] https://launchpad.net/bugs/1484015 - Assigned to Yingxin (cyx1231st)
00:56:07 <Yingxin1> the schema can raises exception when attempt to delete non-exist rules
00:56:17 <Yingxin1> And it can be roll-backed
00:56:42 <Yingxin1> I think it's ready for review
00:57:07 <Yingxin1> https://review.openstack.org/#/c/213283/
00:57:07 <thinrichs> Sounds good.  I'll try to take another look tomorrow.
00:57:14 <Yingxin1> Thank you
00:57:23 <thinrichs> Does anyone have anything else in the last 3 minutes?
00:59:05 <thinrichs> Okay then.  We all get 2 minutes of our day back.  :)
00:59:11 <thinrichs> See you next week!
00:59:22 <masahito> see you!
01:00:09 <veena> Bye. :)
01:00:12 <RuiChen> bye, everybody :)
01:00:16 <Yingxin1> bye
01:00:58 <thinrichs> #endmeeting