00:01:32 #startmeeting congressteammeeting 00:01:32 Meeting started Thu Jan 19 00:01:32 2017 UTC and is due to finish in 60 minutes. The chair is ekcs. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:01:33 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 00:01:36 The meeting name has been set to 'congressteammeeting' 00:01:44 hi thinrichs ramineni_ ! 00:02:05 greeting all 00:02:23 welcome back everyone! 00:03:00 only items I have in mind are talking about ocata-3. 00:03:07 Ocata-3 outstanding patches 00:03:08 Ocata-3 outstanding/new bugs 00:03:13 anything else on our minds? 00:03:35 etherpad for PTG planning? 00:04:31 hi all. 00:04:58 hi masahito 00:05:09 aimeeu: ok. 00:05:28 hi all, bryan_att lurking 00:05:44 hi bryan_att ! 00:05:57 hi! 00:06:08 ok let’s dive in then. 00:06:22 #topic etherpad for PTG planning 00:06:47 So aimeeu I’m guessing what you mean is putting an etherpad in place so people can start putting down ideas and thoughts in PTG planning? 00:06:55 yes exactly 00:08:35 and then adding the link here: #link https://wiki.openstack.org/wiki/PTG/Pike/Etherpads 00:08:51 ok great I can do that after the meeting 00:09:03 #action ekcs add PTG planning etherpad 00:09:12 ekcs: thanks loads! 00:09:16 thanks for the minder! 00:09:23 moving on then. 00:09:30 #topic Ocata-3 outstanding patches 00:10:04 just for background, Ocata-3 is due next week. Testing is underway. 00:10:37 we did a good job of getting patches in for review last week, but we still have a few outstanding patches unmerged. 00:10:54 #link https://review.openstack.org/416777 00:10:54 #link https://review.openstack.org/417606 00:10:56 #link https://review.openstack.org/420653 00:10:56 #link https://review.openstack.org/410705 00:11:02 (anything else?) 00:11:38 I figure we can talk about whether we can/want to merge them quickly. 00:12:52 606 and 653 look about ready to me. Just a bug fix in 606, and then it and the dependent 653 can go in. 00:12:56 Should be a quick fix. 00:14:14 705 looks to be waiting on @masahito to answer the question: is this patch good enough for now? 00:14:44 thinrichs: makes sense. 00:15:14 thinrichs: I'll check it today. 00:15:55 777 I haven't looked at in depth. Only @masahito has. And it's somewhat thorny. If @masahito thinks its ready, fine with me. 00:17:47 ramineni_: does your client patch need to go in? Or is it too late for that? 00:18:08 https://review.openstack.org/#/c/412386/ 00:19:03 thinrichs: And the comment for 606 is that the json module can load rule string from json data if it's surrounded by double-quota. 00:19:41 masahito: It's that the policy language ONLY supports double-quotes. 00:19:52 So you can write p("abc") but not p('abc') 00:20:19 thinrichs: is client release done?? It's a simple patch , but not very imp ...As we have alternate way to do it too .. so either way should be fine 00:20:46 ramineni_: client release not yet done. plan to do next week concurrently with ocata-3. 00:20:52 thinrichs: when I use congress client, it works with single client. 00:21:23 masahito: You can insert p('abc') ? 00:21:41 ekcs: ok 00:21:51 thinrichs: yes 00:22:13 That's surprising. Maybe we added Python-like string handling. 00:22:16 the client changed single quote to double quote in it. 00:23:11 interesting it seems to convert to double quotes. 00:23:14 $ openstack congress policy rule create action "p('abc')" 00:23:14 then it calls API with p("abc"). 00:23:15 +---------+--------------------------------------+ 00:23:16 | Field | Value | 00:23:18 +---------+--------------------------------------+ 00:23:19 | comment | | 00:23:21 | id | d1a4c333-a71d-4f49-8fa8-c42abadea41c | 00:23:22 | name | None | 00:23:23 | rule | p("abc") | 00:23:24 +---------+--------------------------------------+ 00:23:50 Looking at the grammar, any Python string should work. Forgot about that. 00:24:11 When we are printing out the rule we always use double-quotes. 00:24:48 I think there're two option. 00:25:15 masahito: then the comment in the 606 should be: have you tested the code with p("abc") AND p('abc')? 00:26:00 thinrichs: p("abc") in json file doesn't work 00:26:56 because json module thinks "rule": "p("abc")" is "rule": "p(" and abc")" 00:27:33 What if someone escaped the quotes, such as "rule": "p(\"abc\")"? That would be valid JSON (I think). 00:27:53 thinrichs: this works. 00:28:11 Okay, then it's fine as is I'd say. 00:28:11 my another idea is using yaml file instead of json 00:28:55 We could always change it over to yaml later, but leaving it as JSON lets us get the functionality into ocata3 00:29:08 I'd say we can merge those 2 right away. 00:29:48 +1 00:29:57 +1 00:30:53 ok then! 00:32:14 ramineni_: what do you think about https://review.openstack.org/#/c/412386/ ? 00:32:38 it looks fine to me. a little strange that we’re going to have failing osc test from now on. 00:32:54 it’s required to support horizon getting subscribers? 00:33:46 Sorry—one sec. Just saw Aimee's comments on 653. 00:34:16 thinrichs: I answered my own question 00:34:37 ekcs: no ..It's not required for subscribers patch 00:34:41 aimeeu: ok. So that's ready to go in? 00:34:51 yes absolutely 00:35:11 ekcs ..but osc plugin failure is not related to the patch right 00:36:30 ramineni_: I was just guessing that osc failure has to do with what Tim said about adding command to osc dir. Maybe not. 00:37:07 ekcs: no , but will check again 00:37:49 ok. 00:38:53 so on https://review.openstack.org/#/c/416777/ , if someone has time to take a look I’d love to get that merged in order to maximize the testing on it. 00:39:10 but since it’s not a new feature, it technically could wait till after O3 release. 00:41:00 ramineni_: ok sorry I’m a little slow on this. 00:42:00 nvm let’s move on I’ll catch up on it (the client patch) after. 00:42:15 any other thoughts about the patches before we move on? 00:43:57 #topic Ocata-3 outstanding/new bugs 00:45:00 ok does anyone have new/outstanding bugs we should look at ? 00:45:49 either to be fixed by ocata-3 or shortly after. probably good to triage the bugs before ocata-3 to understand if they are fixable once restrictions kick in post O3. 00:47:24 Nothing from me 00:48:21 #link here’s the current bugs list with “new” on top. haha kind of annoying that tasks are mixed in with actual bugs. 00:48:26 #link https://bugs.launchpad.net/congress/+bugs?orderby=status&start=0 00:50:20 I’ve encountered a couple new bugs, but nothing that seems to be deep, hard-to-fix things. mostly on the periphery like DSD interfaces. 00:50:46 so i’m adding them as I see them. 00:51:18 ramineni_: I noticed the same bug you registered back in september. #link https://bugs.launchpad.net/congress/+bug/1626821 00:51:18 Launchpad bug 1626821 in congress "swift driver fails with authorization issue while polling" [Undecided,Invalid] 00:51:59 any idea why it shows up only on infra dsvm test but not locally? 00:52:12 Trying to figure out if we need to dig into it or it doesn’t matter. 00:53:00 ekcs: ya ..I remember debugging it before ..But it works all fine in local environment .. 00:53:15 And on gate too it's temporary 00:53:35 anyway we have 8 minutes left. let’s go to open discussion. where we can still continue discussing bugs. 00:53:41 #topic open discussion 00:53:45 Did u see the error in local environment too? 00:53:53 but feel free to throw out anything else. 00:54:29 ramineni_: no I didn’t see it locally either. I haven’t tested locally on xenial tho. thinking I should probably do that. cuz it could be a trusty vs xenial thing. 00:54:42 ramineni_: do you test on trusty or xenial? 00:54:53 Trusty 00:55:17 I think gate also on trusty at that time 00:55:51 ramineni_: hmm ok. well I guess we should test on xenial anyway so we’ll see what happens. 00:56:04 Ok 00:59:13 ok well thanks all! have a good week and let’s have a great Ocata-3 release! 00:59:28 Thanks all! 00:59:52 Thanks all 00:59:57 see you all later! 01:00:14 #endmeeting