00:01:48 <thinrichs> #startmeeting CongressTeamMeeting
00:01:48 <openstack> Meeting started Thu Oct  8 00:01:48 2015 UTC and is due to finish in 60 minutes.  The chair is thinrichs. Information about MeetBot at http://wiki.debian.org/MeetBot.
00:01:49 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
00:01:52 <openstack> The meeting name has been set to 'congressteammeeting'
00:02:31 <ramineni> hi
00:02:36 <su_zhang> hello all
00:02:44 <masahito> hi
00:02:57 <su_zhang> it has been another week. time flies
00:02:59 <jwy> o/
00:03:14 <thinrichs> On my agenda today…
00:03:18 <thinrichs> 1. liberty
00:03:20 <thinrichs> 2. kilo
00:03:28 <thinrichs> 3. devstack for m1
00:03:37 <thinrichs> 4. stable maintenance team
00:03:59 <thinrichs> 5. status: distributed arch and python3
00:04:06 <thinrichs> Anything to add?
00:04:49 <thinrichs> If you think of anything, let me know.
00:04:50 <masahito> nothing from me.
00:04:54 <thinrichs> #topic Liberty
00:05:13 <thinrichs> I did another round of manual testing this week and found a few bugs.
00:05:24 <thinrichs> https://bugs.launchpad.net/congress/+bugs/?field.tag=liberty-rc2
00:06:10 <thinrichs> I decided the one with devstack we could reasonably just ignore and include a warning in the release notes.
00:06:30 <thinrichs> The other 3 we have volunteers for.
00:06:58 <thinrichs> Anusha, Eric: want to give status updates on those?
00:08:07 <ramineni> thinrichs: yesterday, was trying to reproduce the issue, but didnt get the same error on my env
00:08:07 <ekcs> yea. I commited my fix to the murano issue just now.
00:08:31 <ekcs> waiting jenkins to verify.
00:08:46 <thinrichs> ekcs: great!  I'll take a look in the morning.  If anyone else can look at it tonight, that'd be great.
00:08:47 <ramineni> thinrichs: but facing some other issue, will be working on it today
00:09:26 <thinrichs> Here's the link to ekcs's patch for master:
00:09:27 <thinrichs> #link https://review.openstack.org/#/c/232279/
00:10:00 <thinrichs> That reminds me,,,
00:10:10 <ramineni> thinrichs: will try to resolve by today
00:10:10 <thinrichs> if you're using devstack, make sure to checkout the stable/liberty congress and murano branches.
00:10:46 <thinrichs> Neither Congress nor Murano seem to check out the proper branches...
00:11:03 <thinrichs> unless you do it manually or include CONGRESS_BRANCH in your localrc
00:11:33 <thinrichs> ramineni: do you need anything from us?
00:12:07 <thinrichs> BTW I have a fix for one of the bugs too.  So if people could review, that'd be good.
00:12:09 <thinrichs> #link https://review.openstack.org/#/c/232022/
00:12:14 <ramineni> thinrichs: no as of now, will ping you guys for any help , thanks :)
00:12:25 <thinrichs> Turns out the problem doesn't exist on master, but does exist on stable/liberty.
00:13:11 <thinrichs> I tried to track down the commit we missed backporting to liberty, but it seemed to be spread across a couple of (larger) commits.
00:13:17 <thinrichs> ramineni: sounds good.
00:13:41 <ramineni> thinrichs: https://review.openstack.org/#/c/224985/2
00:14:48 <ramineni> thinrichs: looks like this one on master right
00:14:49 <thinrichs> ramineni: thanks!  I cherry-picked it to stable/liberty.
00:15:11 <thinrichs> Only downside is it doesn't include the unit test to catch the problem.
00:15:17 <thinrichs> We can decide offline what to do.
00:15:19 <ramineni> thinrichs: sure, np, but tests are part of larger commit
00:15:27 <ramineni> thinrichs: ya,ok
00:15:50 <thinrichs> Next week we officially release Liberty
00:15:52 <thinrichs> #link https://wiki.openstack.org/wiki/Liberty_Release_Schedule
00:16:36 <thinrichs> I'm hoping to get our final release candidate done this week and just do the release management stuff (bugs, blueprints, uploading code) next week.
00:16:42 <thinrichs> Questions on liberty?
00:16:47 <su_zhang> sorry I promised to do the tempest test. However, this week is crazy busy for me. If there is still remaining tasks, I will try my best to get it done soon.
00:17:08 <thinrichs> su_zhang: you were looking into the kilo release, which is older.
00:17:23 <ramineni> thinrichs: so, bugs shuld be fixed max by tomorrow?
00:17:34 <ramineni> thinrichs: taregted for rc2
00:17:59 <thinrichs> ramineni: end of week at the latest.  I don't plan to do another whole round of manual testing.
00:18:05 <thinrichs> Just some spot checking.
00:18:15 <ramineni> thinrichs: ok
00:18:39 <thinrichs> su_zhang: we don't have the time pressure for kilo like we do for liberty
00:18:51 <thinrichs> Speaking of which…new topic
00:18:54 <su_zhang> got u. thanks
00:19:00 <thinrichs> #topic stable maintenance team
00:19:21 <su_zhang> I added security group management policies into congress use case doc
00:19:22 <thinrichs> In many openstack projects there are a few people who are responsible for stable branches.
00:19:32 <thinrichs> I'm just learning about this myself, but here's the doc I found.
00:19:41 <su_zhang> if anyone could review it and give some comments, it will be great
00:19:42 <thinrichs> #link https://wiki.openstack.org/wiki/StableBranch
00:19:48 <su_zhang> thanks for sharing
00:20:32 <thinrichs> su_zhang: Thanks.  Let's all try to take a look and give feedback on the ML
00:20:44 <su_zhang> cool, thanks
00:21:18 <su_zhang> I will send its link through ML if needed
00:21:19 <ekcs> sorry what’s ML?
00:21:24 <su_zhang> mailing list
00:21:30 <ekcs> oh ok
00:22:04 <thinrichs> Now that we have a couple of stable branches, it'd be good if we had a person or two for the stable maintenance team.
00:22:19 <thinrichs> So take some time to look over that doc and the responsibilities and let me know if you're interested.
00:22:59 <thinrichs> Next up is the summit.
00:23:03 <thinrichs> #topic Tokyo summit
00:23:19 <thinrichs> alexsyip_: how's the HOL?  Get any feedback on your latest version?
00:23:27 <alexsyip_> it’s basically done.
00:23:38 <alexsyip_> ekcs ran through it and found two typos.
00:24:22 <masahito> I used alexsyip_'s VM with others and it works well.
00:24:36 <thinrichs> That's great news!
00:24:40 <su_zhang> cool
00:25:07 <thinrichs> Are we planning to use the same slides as last year for an introduction?
00:25:54 <thinrichs> Or perhaps that's up to me since I'm giving the intro.
00:26:13 <alexsyip_> You’re welcome to use the old slides.
00:26:22 <thinrichs> Besides the VM and the slides, the other important thing is to have volunteers.
00:26:44 <thinrichs> The volunteers show up for the lab and walk around the room helping people get it running and answering questions.
00:26:53 <thinrichs> Any volunteers?
00:27:11 <ekcs> I’ll be there.
00:27:12 <masahito> I'll do it.
00:27:53 <pballand> I’ll be there
00:28:33 <thinrichs> The more the merrier, so just show up the day-of if you feel like it.
00:29:00 <thinrichs> Anything else for the summit to discuss?
00:29:11 <thinrichs> Oh—I was thinking about having a Congress dinner some night.
00:29:20 <thinrichs> Is anyone interested?
00:29:57 <masahito> sounds interested.
00:30:09 <ramineni> sounds good
00:30:52 <thinrichs> I am thinking Wed night
00:31:50 <thinrichs> I'll ask again a bit closer to the summit, so we know when all the parties are.
00:32:11 <thinrichs> #topic devstack
00:32:37 <thinrichs> Just found out that we're going to need to build a devstack plugin before the first milestone of M
00:32:42 <thinrichs> #link http://lists.openstack.org/pipermail/openstack-dev/2015-October/076310.html
00:33:07 <thinrichs> If we don't, our tempest tests won't run in gate, and Congress won't work with devstack.
00:33:29 <thinrichs> Currently we do a copy-paste to integrate with devstack
00:33:40 <thinrichs> That will no longer work at M1
00:34:02 <thinrichs> Anyone want to build a devstack plugin?
00:34:06 <ramineni> thinrichs: i can take it up, if no one wrkng on it
00:34:16 <thinrichs> ramineni: Great!
00:34:40 <thinrichs> ramineni: maybe create a blueprint for it too
00:34:55 <ramineni> thinrichs: sure
00:35:07 <thinrichs> #topic Python3
00:35:35 <thinrichs> What's our status looking into antlr3 for Python3 compatibility?
00:36:10 <ramineni> thinrichs: https://github.com/antlr/antlr3/tree/master/runtime/Python3 ,
00:36:17 <ramineni> thinrichs: it says python3 compatible
00:36:27 <ramineni> thinrichs: dont we use this?
00:37:33 <thinrichs> ramineni: there were a couple of options we discussed…
00:38:09 <thinrichs> moving to antlr4
00:38:10 <thinrichs> pulling antlr out of the trunk (since we're checking in the generated code anyway)
00:38:23 <thinrichs> This seems like a 3rd option.
00:38:41 <thinrichs> It would be nice to pull antlr out of the trunk
00:39:14 <thinrichs> But someone was supposed to look into these options, I thought.
00:41:16 <thinrichs> Nevermind—no one volunteered to look into pulling antlr3 out.  We just talked about it.
00:41:46 <thinrichs> Maybe I'll take a look once we get out from under the liberty deadline.
00:41:50 <thinrichs> #topic Status updates
00:42:02 <thinrichs> We finally have some time to do status updates this week.
00:42:24 <thinrichs> Who's been making some progress they want to share?
00:42:36 <thinrichs> And to get feedback from the group?
00:43:41 <alexsyip_> I’ve been working on synchronizing rules and policies, but it’s not ready for review yet.
00:44:26 <alexsyip_> I have a change on gerrit for a startup script that is awaiting review.
00:44:46 <thinrichs> alexsyip_: So in the new distributed arch, that addresses the problem of synchronizing multiple instances of the policy engine running on different machines but sharing the database.  Right?
00:44:57 <alexsyip_> that’s right.
00:45:21 <su_zhang> One thing I want to mention is that update frequency should be configurable. Right now it is hardcoded in datasources.py as 1 second. This can be a DOS attack for certain environments
00:45:48 <su_zhang> I could not find it is configurable in congress.conf
00:45:51 <pballand> I’ve been refactoring the DseNode code to have a separate test suite, using the oslo.messaging fake driver - it’s not yet working, so nothing to share yet
00:45:52 <alexsyip_> The synchronizer runs on a configurable interval.
00:46:19 <alexsyip_> There is a “poll_time” configuration value in the config file.
00:46:24 <su_zhang> okay, I will look into it. Thanks
00:46:55 <ekcs> here are some documentation fixes that help users avoid some of the errors I ran into while following stand-alone congress install instructions. Be great if someone can review. Hoping to get it in liberty release.
00:46:56 <ekcs> #link https://review.openstack.org/#/q/status:open+project:openstack/congress+branch:stable/liberty+topic:amended-sample-conf-instruction-liberty,n,z
00:46:57 <ekcs> #link https://review.openstack.org/#/q/status:open+project:openstack/congress+branch:master+topic:amended-sample-conf-instruction,n,z
00:46:58 <ekcs> #link https://review.openstack.org/#/q/status:open+project:openstack/congress+branch:stable/liberty+topic:README.rst-install-instruction-fix-liberty,n,z
00:46:59 <ekcs> #link https://review.openstack.org/#/q/status:open+project:openstack/congress+branch:master+topic:README.rst-install-instruction-fix,n,z
00:47:28 <ramineni> thinrichs: working on rpcfying row model api blueprint, almost done with code, will put up for review by next week
00:47:37 <thinrichs> ekcs: I'll make a pass through review tomorrow morning
00:48:17 <thinrichs> Everyone should take another look at alexsyip_'s script.  Several people have commented already, and he's provided a new patchset in response.
00:48:48 <masahito> thinrichs: got it.
00:48:49 <thinrichs> pballand: It's great we're still making progress on the DSENode.  It's crucial to the new arch.  Let us know if you need anything.
00:49:47 <thinrichs> ramineni: great!  Having the API working seemingly over RPC puts us in a good spot to pull pballand's changes in.
00:52:05 <thinrichs> jwy: have you heard from Yali?
00:52:18 <thinrichs> That change for the new UI is still sitting in review.
00:52:58 <thinrichs> #topic open discussion
00:52:58 <jwy> thinrichs: not for a while. she said she'd update it soon, not sure what happened with that
00:53:16 <thinrichs> jwy: mind pinging her?  I think she wanted to touch base in Tokyo.
00:53:48 <jwy> sure. the last i spoke with her, she also said that she wouldn't be able to attend the summit
00:53:59 <thinrichs> maybe I'm confused then
00:54:08 <thinrichs> Anything else to discuss, anyone?
00:54:19 <ekcs> yea
00:55:17 <thinrichs> ekcs: what's up?
00:55:30 <ekcs> actually nvm.
00:55:47 <thinrichs> OK
00:55:48 <ramineni> thinrichs: one question on heat polling issue, once enabling heat driver, that issue sees during polling ,
00:56:07 <ramineni> thinrichs: or any other config to be done?
00:56:35 <thinrichs> I just created the Heat datasource and then created a deployment, I think.
00:56:52 <thinrichs> One minute.
00:57:23 <ramineni> thinrichs: ok, i didnt do deployment , will try that
00:58:20 <thinrichs> Here's the command I think I used.
00:58:20 <thinrichs> heat deployment-create -s 37990ba3-b816-441c-bdb6-86c2170b0bd1 doug
00:58:26 <thinrichs> The UUID is for a server.
00:58:42 <thinrichs> So you may need to create a server first.
00:58:50 <ramineni> thinrichs: stack right
00:59:03 <ramineni> i mean stack-create?
00:59:07 <thinrichs> To create a server, something like...
00:59:07 <thinrichs> nova boot beta --flavor=m1.tiny --image=cirros-0.3.4-x86_64-uec
00:59:16 <thinrichs> I think I did a 'deployment', not a 'stack'.
00:59:20 <thinrichs> We should probably do both
00:59:21 <ramineni> thinrichs: oh, ok
00:59:33 <thinrichs> I think our driver tries to pull both of them in.
00:59:54 <thinrichs> Out of time.
01:00:00 <thinrichs> Thanks all!
01:00:03 <ramineni> thinrichs: thanks, will try that
01:00:28 <thinrichs> #endmeeting