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