17:03:38 <pballand> #startmeeting CongressTeamMeeting 17:03:39 <openstack> Meeting started Tue Aug 5 17:03:38 2014 UTC and is due to finish in 60 minutes. The chair is pballand. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:03:40 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:03:42 <openstack> The meeting name has been set to 'congressteammeeting' 17:03:52 <david-lyle> I think the bot died in the middle of the last meeting and rejoined 17:04:05 <pballand> poor bot 17:04:19 <pballand> :) 17:04:25 <arosen> Hi 17:04:31 <sarob> hi 17:04:44 <pballand> good morning/afternoon/evening everyone 17:04:54 <skn_> Hey Guys 17:05:23 <pballand> a fair amount of code went in last week 17:05:26 <rajdeep> hi 17:05:30 <pballand> lets start off with some status updates 17:05:51 <pballand> arosen: I think you pushed the most code, would you mind going first? 17:06:32 <arosen> pballand: sure! 17:07:11 <arosen> So we have patches merged into the tree now that add support for keystone and openstack's policy.json (which is used to control which api calls can be called by specific openstack users). 17:08:03 <arosen> I've added CI support for most of the API's congress exposes right now so that should handle the keystone integration part so one doesn't have to pass in the auth token themselves. 17:08:10 <arosen> Though this is still WIP'ish 17:08:34 <arosen> We also have devstack support in tree which should help setting up congress+keystone and the rest of the openstack bits. 17:08:43 <pballand> CI = CLI? 17:08:54 <arosen> *CLI 17:09:10 <arosen> Lastly, i've made good progress getting CI up and running for congress. Hopefully have something voting by the end of the week. 17:09:16 <arosen> that's all from me. 17:09:44 <pballand> awesome, thanks! 17:10:01 <pballand> on the CLI - is there code ready for review? 17:10:27 <arosen> pballand: Here's the patch https://review.openstack.org/#/c/104375/ but i have yet to add tests 17:10:40 <arosen> So i'd probably wait to avoid it for now unless someone wants to start reviewing it. 17:11:25 <pballand> makes sense 17:11:50 <pballand> it would be helpful to update the wiki to point to the python client repo 17:12:01 <arosen> pballand: k will do 17:12:04 <pballand> thanks 17:12:10 <pballand> who would like to go next? 17:12:35 <pballand> skn_: any updates on the IDS integration? 17:12:46 <skn__> Sure! I can go next 17:13:17 <skn__> I have got the Bro up and running with OpenStack 17:13:34 <skn__> I am trying out some configurations now 17:14:03 <skn__> In the meantime, I am writing up the IDS data source driver spec for Congress 17:14:39 <skn__> I'll try to check the spec in by tomorrow so that we can get some reviews/feedbacks 17:15:12 <pballand> sounds good - looking forward to taking a peek 17:16:03 <skn__> Yeah, now I have the Bro working on a single node devstack, and I am trying to have it in a multi-node set up 17:17:18 <pballand> thanks skn__ anything else? 17:17:41 <skn__> No, that's all 17:17:50 <skn__> unless you guys have any questions 17:18:09 <skn__> After we have the spec, I'll work on the driver code 17:18:11 <pballand> I think we’ll have more to discuss once people have a chance to review the spec 17:18:23 <skn__> Yes 17:18:30 <pballand> sarob: are you around? 17:19:21 <pballand> sarob seems to be away; rajdeep, do you have any updates? 17:20:49 <pballand> thinrichs1: you there? 17:21:13 <thinrichs1> yep. 17:21:35 <thinrichs1> I made an editing pass over the rst docs. Trying to get them in shape for the alpha release. 17:21:47 <thinrichs1> https://review.openstack.org/#/c/111416/ 17:21:52 <skn__> I see sarob in the list 17:22:13 <thinrichs1> I'm told it's a bit hard to read in gerrit b/c lines are > 80 chars. I'll try to fix that. 17:22:46 <thinrichs1> I also sent around a proposal for renovating the data sources, to solve the problems with wide tables that I mentioned last week. 17:22:57 <thinrichs1> http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg31030.html 17:23:53 <thinrichs1> I'm swayed by the argument that we won't always be able to eliminate wide tables, so we'll need to make it easy to write policy over them.support wide tables 17:24:25 <pballand> that makes sense to me 17:24:25 <thinrichs1> We've had a couple of people weigh in, but if anyone else wants to pipe up, that'd be good. 17:25:05 <thinrichs1> I've also been trying to clean house so we can formally release the alpha. 17:25:07 <rajdeep> hi i was reviewing the docs CL sent by tim 17:25:15 <thinrichs1> That's it for me. 17:25:24 <pballand> thanks thinrichs1 17:25:34 <pballand> did I miss anyone? 17:25:50 <rajdeep> some of the commands like starting the server and running unit test cases seem to be failing 17:26:24 <pballand> rajdeep: can you be more specific? 17:27:12 <rajdeep> pballand see the comments https://review.openstack.org/#/c/111416/1/README.rst 17:27:20 <rajdeep> tox -e py27 fails 17:27:41 <skn__> I agree with this too, to somehow make it easy to write policies over wide tables 17:27:57 <rajdeep> so does sudo python setup.py develop 17:28:11 <rajdeep> am i missing something? 17:28:37 <pballand> rajdeep: it seems like some requirements are missing 17:29:12 <pballand> a patch went in to sync the requirements with upstream projects, it’s possible an error was in there 17:29:33 <rajdeep> ok. 17:29:43 <thinrichs1> It's hard to ensure we are listing all the packages, since each distro has a different set installed. 17:30:00 <thinrichs1> This is really useful info. We don't want users running into these problems. 17:30:37 <thinrichs1> rajdeep: What OS/distro were you using? 17:30:58 <thinrichs1> The setup instructions worked for me on a Mac. I figured they'd work on any Linux too. But I guess I was wrong. 17:31:35 <rajdeep> ubuntu 12.04 17:31:40 <rajdeep> with python 2.7 17:31:42 <pballand> the code has been working on my ubuntu box, but I may have some packages sitting around 17:31:48 <pballand> I’ll try from a fresh install 17:31:48 <sarob> im back, sorry about that 17:32:08 <thinrichs1> rajdeep: with devstack installed or Not? 17:32:08 <rajdeep> shall i try by cleaning .tox directory 17:32:17 <rajdeep> no devstack 17:32:27 <pballand> rm -rf .tox is always good place to start 17:32:27 <rajdeep> pure congress setup 17:32:42 <rajdeep> ok wil try that and revert 17:32:54 <rajdeep> it will be good to have a getting started guide 17:33:10 <rajdeep> and a trouble shooting readme as well 17:33:28 <thinrichs1> The README was intended to be a getting-started guide. 17:33:47 <thinrichs1> The point of the setup script was to install all the packages, so it should just work. 17:34:07 <thinrichs1> I think the goal is not more docs, but to make our setup script work. 17:34:55 <rajdeep> ok, i understand but people will invariable have problems 17:35:05 <pballand> thinrichs1: that’s right - the setup should handle the basic requirements, so if that doesn’t work, we need to fix it 17:35:18 <rajdeep> specially with all permutations of OS + Python version 17:35:20 <pballand> let’s follow up on this in #congress or email 17:35:35 <pballand> sarob: do you have any updates on the summit or other? 17:36:24 <sarob> pballand: im working on locking down a 30 person room in vmware PA 17:37:05 <sarob> pballand: we will be part of the operators summit as we discussed before 17:37:40 <pballand> sarob: any details on the schedule? 17:37:43 <sarob> pballand: i am reviewing the congress-spec infra config 17:37:55 <sarob> pballand: which one? 17:38:13 <pballand> the operator summit - let’s just sync offline 17:38:26 <skn__> sarob, peter: Let me know you need any help in the slides for the operator's summit 17:38:27 <sarob> pballand: sure, 17:38:47 <pballand> skn__: thanks, are you planning on attending? 17:39:23 <skn__> Nope 17:39:36 <skn__> But I'll be in the policy summit 17:39:45 <skn__> Unless you guys need me to present anything 17:40:29 <sarob> pballand: demo and slides for the operators summit would be goodness to link off the congress wiki 17:40:55 <pballand> sarob, skn__ : I have a deck that I am working on for the operator’s summit 17:41:18 <sarob> pballand, skn__: lets discuss on congress channel 17:41:18 <pballand> it’s in pretty good shape 17:41:23 <pballand> perfect 17:41:30 <sarob> pballand: ;) 17:41:33 <skn__> pballand, sarob: Oh, that's great. Yes 17:42:11 <pballand> anyone else have updates, or blockers to discuss? 17:43:28 <pballand> #topic open discussion 17:44:29 <pballand> if you haven’t voted on talks for the Paris summit, now is the time to do so 17:44:46 <skn__> sarob: Do we have a slightly more detailed agenda for the policy summit 17:45:04 <pballand> if you haven’t already, please vote for the congress session: https://www.openstack.org/vote-paris/Presentation/congress-policy-as-a-service 17:45:26 <sarob> skn__: not more than pballand suggested yet 17:45:42 <pballand> martin also mentions congress in his abstract: https://www.openstack.org/vote-paris/Presentation/policy-and-security-in-the-goldilocks-zone 17:46:23 <sarob> skn__: once I have the room locked down, I plan on pushing the discussion on content through ml, blog, and tweets 17:46:44 <skn__> Great! 17:46:53 <pballand> sarob: I can help lock down the room - let’s move on this today 17:47:26 <sarob> pballand: excellent 17:47:57 <pballand> I’m really looking foreword to all of the events we have coming up, and hope everyone can make at least one of them 17:48:18 <pballand> thanks for making time for the meeting this week, we’ll continue as usual in #congress 17:48:26 <pballand> #endmeeting