17:00:36 <pballand> #startmeeting CongressTeamMeeting
17:00:37 <openstack> Meeting started Tue Sep 30 17:00:36 2014 UTC and is due to finish in 60 minutes.  The chair is pballand. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:38 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:41 <openstack> The meeting name has been set to 'congressteammeeting'
17:00:56 <sarob> Morning
17:01:12 <thinrichs1> Hi all
17:01:16 <pettori> Morning :)
17:01:44 <pballand> #chair thinrichs
17:01:45 <openstack> Warning: Nick not in channel: thinrichs
17:01:46 <openstack> Current chairs: pballand thinrichs
17:02:04 <arosen-home2> hi
17:03:04 <pballand> I wanted to start by letting people know in the meeting that I am stepping down as PTL due to time conflicts
17:03:15 <pballand> in my place, I would like to recommend thinrichs
17:03:40 <sarob> +1
17:03:44 <arosen-home2> +1
17:03:50 <pballand> I still plan on being active as a core contributer, but have to to take a step bac in responsibilities
17:03:50 <alexsyip> +1
17:03:57 <pettori> +1
17:04:19 <pballand> so with that, I’d like to had over the meeting with thinrichs1
17:04:29 <thinrichs1> Thanks for the rec!  I'm happy to help out.
17:04:52 <thinrichs1> We're trying to keep to the standard election procedures.
17:05:05 <thinrichs1> So if anyone else wants to run for PTL, let us know.
17:05:53 <thinrichs1> Hopefully we've all recovered from the policy summit, which was awesome by the way./
17:05:56 <thinrichs1> Let's start with status updates.
17:06:31 <thinrichs1> alexsyip: how about you start?
17:06:50 <alexsyip> We pushed a keystone driver to master.
17:06:58 <alexsyip> It has a bug, but I have a fix in code review now.
17:07:12 <alexsyip> I also started working on datasource driver refactoring.
17:08:25 <alexsyip> The goal of the refactoring is to allow a datasource driver to describe declaritively how to translate from the API response to tables with columns and keys.
17:08:51 <alexsyip> The hope is that this will make it easier and less bug prone to write new drivers.
17:09:02 <alexsyip> It will probably take a few more days.
17:09:32 <thinrichs1> That sounds great!  It should help us ramp up building datasource drivers, at least the common ones.
17:10:03 <thinrichs1> arosen-home2: Want to go next?
17:10:08 <arosen-home2> thinrichs1: sure
17:10:42 <arosen-home2> so i've been working on the CI stuff. I've make good progress here. The one bug that alex mentioned was blocking it but once we merge these patches we should be able to start gating with some functional tests.
17:11:04 <arosen-home2> Here's the patch that adds a tempest test to congress
17:11:07 <arosen-home2> https://review.openstack.org/#/c/123839/
17:11:17 <arosen-home2> I think we should start trying to add tempest tests here for each data sources driver.
17:11:48 <arosen-home2> i'm sure there will be a few kinks we'll need to work out with the ci though fyi :)
17:12:05 <thinrichs1> So those patches are ready to go?
17:12:54 <arosen-home2> thinrichs1:  there is still one issue i'm hitting with the keystone driver i believe in the CI though I don't think it's related to alexsyip's patch
17:12:59 <arosen-home2> i think it might be config related.
17:13:13 <arosen-home2> Hopefully i'll be able to sort this out in the next hour and we can merge all these changes.
17:13:19 <arosen-home2> I'll keep everyone posted!
17:13:22 <thinrichs1> Sounds good!
17:13:23 <arosen-home2> that's it from me for now though.
17:13:33 <thinrichs1> I can't wait til all our use cases are up as tempest tests so they're never broken.
17:13:43 <thinrichs1> Good stuff!
17:13:44 <arosen-home2> oh also we want to do a 1.0.0a release of the python-congressclient sometime soon if possible.
17:14:42 <thinrichs1> I like the idea of snapshotting.  Are we doing something with that snapshot?
17:14:56 <arosen-home2> what do you mean by snapshotting?
17:15:02 <thinrichs1> Tagging with 1.0.0,.a
17:15:03 <arosen-home2> the git tags?
17:15:17 <arosen-home2> well in order to allow people to install the congress client we need to git tag the release version
17:15:31 <arosen-home2> this will allow people to do: pip install python-congressclient
17:15:51 <arosen-home2> but i agree having tags in the client will be helpful for known points that work
17:16:51 <thinrichs1> So our client will be available in pypi?
17:17:20 <arosen-home2> thinrichs1:  yup, in fact it's already available today :) , you just have to do: pip install python-congressclient -pre
17:17:29 <arosen-home2> after we add the git tag we can remove the -pre
17:17:37 <thinrichs1> Very cool!
17:17:42 <arosen-home2> BOOM! :)
17:18:21 <thinrichs1> Let's move on.
17:18:31 <thinrichs1> sarob: want to give your status report?
17:19:08 <sarob> Yup
17:19:42 <sarob> I'm going to put out
17:20:02 <sarob> The sum total of the specs from the summit on the ML
17:20:28 <sarob> We can all report back on status of mentoring and specs
17:20:44 <sarob> A bit on more on the summit
17:21:00 <sarob> We had 83 people sign up
17:21:17 <sarob> 32 companies represented
17:21:40 <sarob> I believe most participated
17:21:53 <sarob> Since the room was pretty full
17:22:37 <sarob> I believe all new specs from
17:22:49 <sarob> This point til the summit
17:23:06 <sarob> Should be pushed into the kilo slit
17:23:09 <sarob> Slot
17:24:17 <sarob> I'm thinking we approve specs for kilo review at the summit
17:24:26 <sarob> Now until the summit
17:24:59 <thinrichs1> That sounds good.
17:25:00 <sarob> Then debate which spec/bp get assigned to which milestone
17:25:52 <pballand> I think we should discuss what milestones we should have - it may not make sense to follow the ‘standard’ milestones since we are still early
17:25:52 <sarob> So we should have about 10-20 specs/bp for Paris debate
17:26:16 <sarob> Pballand: sure
17:27:04 <sarob> That's it for me
17:27:04 <thinrichs1> Maybe now is a good time to have each person who volunteered to mentor a group at the summit report.
17:27:20 <thinrichs1> Have we heard from our mentorees?  Has any progress been made toward specs?
17:27:24 <thinrichs1> I'll start.
17:27:43 <thinrichs1> My group has emailed around the start of a spec.
17:27:59 <thinrichs1> The spec is being co-authored by 4 different people, and there are slots in the spec for each.
17:28:25 <thinrichs1> So all seems to be going well.
17:28:46 <pballand> I need to follow up with yathi and debo on the compute hints specs
17:29:21 <sarob> I'm working with staz
17:29:35 <sarob> Straz I meant
17:30:00 <sarob> Spec up over the next days
17:30:59 <thinrichs1> And if anyone is here that volunteered, please pipe up and let us know how the spec process is working for you.
17:31:48 <alexsyip> LouisF had a follow up question for one of our specs, but I’ll need to follow up some more on the other ones.
17:32:33 <LouisF> alexsyip: sending you an email on that
17:32:43 <alexsyip> great!
17:34:33 <thinrichs1> Anyone else from the policy summit want to chime in here?
17:35:03 <thinrichs1> Is there anything we can do to help you get specs in place?  Is the procedure clear?
17:36:51 <thinrichs1> So let's wrap up the post-summit discussion and continue with status reports.
17:37:24 <thinrichs1> madhumohan: want to report on what you've been working on?
17:39:47 <thinrichs1> Maybe madhumohan stepped away.
17:40:18 <thinrichs1> He's pushed a ceilometer driver up for review and gone through 1 round of comments.
17:41:13 <thinrichs1> As far as I can tell, this is his first code contribution!  Congrats!
17:42:11 <thinrichs1> kudva, who has been working on builtins, pushed another patch recently.
17:42:37 <thinrichs1> I haven't tested this myself, but I believe we can now write policies with less-than, greater-than, addition, subtraction, and maybe some string manipulation.
17:43:14 <thinrichs1> There are still some rough edges, but he was slammed for the next few weeks and we wanted to get the functionality in there.
17:43:30 <thinrichs1> rajdeep: want to tell us what you've been doing?
17:44:02 <rajdeep> hi i have been working on the spec for horizon integration
17:44:23 <madhumohan> thinrichs: fixed those Jenkins errors. now looking at pep8
17:44:27 <rajdeep> submitted the spec for review
17:44:46 <rajdeep> https://review.openstack.org/#/c/124725/
17:45:27 <rajdeep> feedback welcome on the spec
17:45:50 <thinrichs1> We'll look at the spec and get you feedback.
17:46:08 <thinrichs1> I'll give my status.
17:46:19 <thinrichs1> I've been working on adding column-references to our datalog rules.
17:46:42 <thinrichs1> So instead of having to write a rule like p(x) :- neutron:networks(x,x1,x2,x3,…,x10)
17:46:59 <thinrichs1> you'll be able to write a rule like p(x) :- neutron:networks(id=x)
17:47:17 <thinrichs1> The benefit is that you don't need to know every column in the table when you write the rule.
17:47:25 <thinrichs1> And if the columns change, you don't need to change your rules.
17:48:09 <thinrichs1> For now you'll only be able to use column-references on datasource tables, just because those tables are the only ones that have schemas declared.
17:48:31 <thinrichs1> Eventually we'll allow schema declarations for all tables, and then you'll be able to use column-references in every rule.
17:48:53 <thinrichs1> Radu_: we're just wrapping up status updates.
17:49:00 <thinrichs1> Radu_: want to tell us what you've been doing?
17:49:36 <Radu_> Sure
17:49:59 <Radu_> I've been working on making sure my driver intregration works with the newest version of congress
17:50:27 <Radu_> A few changes to the API and I believe the change to the DSE had a bit of an effect that I finished fixing earlier
17:50:29 <madhumohan> thinrichs: i tried applying the logic at the input side by reading the policy as error(x) :- nova:servers(x, y) format... and padding with appropriate values before writing to the policies.
17:50:56 <Radu_> Everything seems to be working as it should be, I havent ran a full demo again since doing an update though
17:51:26 <Radu_> https://www.youtube.com/watch?v=2oLFxsw7QeI is a video of a demo using congress and my plexxi intregation driver
17:51:57 <thinrichs1> Radu_: I didn't realize we had changed the API recently.  Can you give us a quick summary of the changes?
17:52:04 <pballand> Radu_: what API changes are you mentioning?
17:52:15 <Radu_> just the /v1 really
17:52:33 <Radu_> I had some other issues that I may have created thinking other things changed
17:52:53 <Radu_> the api document is still out of date on the google docs
17:53:30 <Radu_> it still states that the api  address is "/api/v1/..." where its now "/v1/...." and used to be "/..."
17:53:55 <pballand> Radu_: ah - good point, will change the path
17:54:11 <pballand> arosen made that change as part of the pythonclient work
17:54:15 <thinrichs1> madhumohan: will get to you.  Hang on.
17:54:23 <Radu_> Sorry I cant be here for the full meeting, have a time conflict.
17:54:42 <thinrichs1> Radu_: no worries—glad you could make some of the meeting.
17:55:07 <thinrichs1> Let's hear from madhumohan before we run out of time.
17:55:18 <arosen-home1> https://github.com/stackforge/python-congressclient/blob/master/congressclient/v1/client.py#L18
17:55:21 <arosen-home1> (for api)
17:55:31 * arosen-home1 on the client side
17:56:16 <thinrichs1> madhumohan: are you saying you're having trouble inserting policy from the API?  Could you clarify?  Were you using curl, the python-client, etc.?
17:56:58 <Radu_> I might be able to help with that issue as well
17:57:20 <Radu_> Ive just been using python requests to insert policy rules
17:57:32 <madhumohan> I was working on using simple policies without having to list all fields in the table.
17:58:03 <arosen-home1> I added this example on how to use the python bindings which mind be helpful: https://review.openstack.org/#/c/124945/2/congressclient/v1/client.py
17:58:19 <thinrichs1> madhumohan: that's definitely a good problem to work on.  I'm working on the same thing.  Want to collaborate?
17:58:20 <madhumohan> Thats where I tried to pad the input with the required columns without the entire column list...
17:58:48 <madhumohan> Would surely like to collaborate...
17:59:22 <thinrichs1> I'll ping you offline, since we're about out of time.
17:59:53 <thinrichs1> And we're officially out of time.
17:59:55 <thinrichs1> Thanks all!
18:00:06 <thinrichs1> See you next week!
18:00:24 <pballand> bye!
18:00:27 <thinrichs1> #endmeeting
18:00:52 <arosen-home1> later
18:01:02 <pballand> #endmeeting