17:02:48 <thinrichs> #startmeeting CongressTeamMeeting
17:02:48 <openstack> Meeting started Tue Apr  8 17:02:48 2014 UTC and is due to finish in 60 minutes.  The chair is thinrichs. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:02:49 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:02:51 <openstack> The meeting name has been set to 'congressteammeeting'
17:03:42 <thinrichs> Let's start by reviewing action items from last week.
17:03:58 <thinrichs> #topic action items review
17:04:12 <thinrichs> I was supposed to modify the policy engine to provide 3 toplevel policies.
17:04:32 <thinrichs> AccessControl, ProhibitedStates, and Execution/Enforcement
17:04:44 <thinrichs> I added the AccessControl policy.  The other 2 were already there.
17:05:05 <thinrichs> I decided for the time being to leave the other high-level functionality in place.
17:05:12 <thinrichs> We'll just not discuss it in the docs.
17:05:27 <thinrichs> I think we'll want that functionality later (e.g. enumerating a list of potential remediations for a given policy violation).
17:05:38 <thinrichs> I did not get around to updating the docs.
17:05:57 <thinrichs> rajdeep: can you report on your data source driver docs?
17:06:17 <rajdeep> yes -- i have completed the first draft of the docs
17:06:48 <thinrichs> Great!  I looked them over quickly and thought it looked about right.  I left I think 1 comment in gerritt.
17:06:49 <rajdeep> change request submitted for review https://review.openstack.org/#/c/84358/
17:07:00 <rajdeep> ok, will take a look
17:07:13 <pballand> Looked reasonable to me too - just a couple nits
17:07:13 <rajdeep> i focus on how to write a generic driver
17:07:28 <rajdeep> converting lists / dictionaries into tuples
17:07:35 <pballand> I think the examples will probably be the most useful going forward
17:08:14 <thinrichs> pballand: can you report on the API?
17:08:18 <rajdeep> that is where i spent most of the time
17:08:28 <pballand> unfortunately, I got pulled 20 different ways over the last 2 weeks, and did not make any progress :(
17:09:04 <thinrichs> pballand: understood.  We really need at least some progress on that front so that others can pick up slack.
17:09:17 <pballand> understood - it is on the top of my stack
17:09:38 <pballand> I hope to have better news to report soon
17:09:56 <thinrichs> Sounds good.
17:10:26 <thinrichs> kudva: can you report on your builtin proposal?
17:10:46 <kudva> Yes, I sent a policy document very early version to the mailing list (pdf)
17:10:48 <kudva> Need feedback
17:10:58 <kudva> Then, I can put together a small code prototype
17:11:01 <kudva> implementation
17:11:14 <kudva> But first, I wanted the team to agree, give me feedback
17:11:49 <thinrichs> So let's all make an effort over the next couple of days to look at the proposal and give feedback.
17:11:58 <kudva> That would be terrific
17:12:16 <rajdeep> it will be easier if it is a google doc
17:12:23 <thinrichs> #action Everyone will look at the builtin proposal and provide feedback.
17:12:24 <rajdeep> easier to collaborate
17:12:26 <kudva> I can do that.
17:12:27 <kudva> sure
17:12:37 <kudva> Will make it a google doc and send a link
17:12:43 <rajdeep> great
17:13:00 <thinrichs> Sounds good.
17:13:20 <thinrichs> I think that was the last action item.
17:13:55 <thinrichs> Let's do a quick review of the outstanding tasks for an alpha release and divvy up work for those who have cycles.
17:14:02 <thinrichs> #topic Status update on alpha release.
17:14:49 <thinrichs> One of the chunks we're missing is the Plexxi codebase that enables the data sources to communicate with the policy engine.
17:15:06 <thinrichs> This morning I sent them a note to push that along.
17:15:26 <thinrichs> I'll take responsibility for getting that done, hopefully sooner than later.
17:15:34 <rajdeep> is there a time frame in which it will be done
17:16:07 <thinrichs> I'm aiming for end of the week.  I'm hoping to getting the alpha release out by the OpenStack summit.
17:16:23 <pballand> I am still committed to rewriting the API framework and runtime loop - aiming for last week :-/
17:16:23 <thinrichs> And it will take some time to get that part, in particular, integrated.
17:16:45 <pballand> serious estimate is middle of next week
17:16:56 <thinrichs> #action thinrichs will help Plexxi integrate their code
17:17:14 <thinrichs> #action pballand will get the API framework in place
17:17:47 <thinrichs> There's also the issue of adding a Nova datasource driver.
17:18:08 <rajdeep> i was planning to do that later this week / next week
17:18:19 <thinrichs> Great!
17:18:23 <rajdeep> atleast get few API mappings done
17:18:36 <thinrichs> #action rajdeep will work on a Nova datasource driver
17:19:49 <thinrichs> Forgot that once we get Plexxi merged we'll need to start the integration of that.
17:20:35 <thinrichs> Not sure that we'll have time to start the integration before the next meeting, so I'll take that as a possible action item.
17:20:51 <thinrichs> #action thinrichs will begin integration with Plexxi codebase, if possible
17:21:19 <thinrichs> The final must-have on my list is some performance analysis/improvements.
17:21:44 <thinrichs> Until we have more integration in place, this one will likely need to wait.
17:22:30 <thinrichs> There are some other things that would be nice to get in place (actually executing actions, persisting policy/logging), but we all have full plates for now.
17:22:59 <thinrichs> Am I missing anything important for the alpha release?
17:23:02 <rajdeep> how will executing actions talk to data sources?
17:24:01 <thinrichs> rajdeep: TBD--I expect the policy engine will publish the request for an action execution on the Plexxi bus.
17:24:11 <thinrichs> And whoever is listening on that bus will execute it.
17:24:22 <rajdeep> ok, i guess we can wait for this discussion
17:24:51 <thinrichs> Yes--a good idea to wait until we know more about the Plexxi code and how it works.
17:25:45 <thinrichs> Okay, so it sounds like we have good coverage for the alpha, as far as we can tell.
17:25:58 <thinrichs> Let's move to open discussion.
17:26:02 <thinrichs> #topic Open discussion
17:26:24 <pballand> I submitted a proposal for Congress in the Open Source track in Atlanta (http://www.openstack.org/blog/2014/03/call-for-proposals-open-source-openstack-summit/) - still waiting to hear on whether it was accepted
17:26:38 <pballand> just and FYI
17:26:43 <pballand> s/and/an/
17:27:00 <thinrichs> Sounds good.  Is it an hour-long or what?
17:27:40 <rajdeep> Do we have any projects around Congress? List of wish list we are currently not working on
17:27:54 <pballand> don’t know yet - but I expect plenty of conversations whether we have a room or not, so it would be great to have the space :)
17:28:16 <pballand> what do you mean by “projects”?
17:28:49 <rajdeep> i meant student / intern projects
17:29:28 <thinrichs> Not that I know of.  We're talking with several academics though.
17:29:33 <thinrichs> There should be interest there eventually.
17:31:25 <thinrichs> Does anyone know of other people we should be reaching out to that might be interested in contributing to Congress?
17:31:46 <rajdeep> there is a policy project starting at UCSB
17:31:57 <rajdeep> focussed on policy for platform as a service
17:32:09 <rajdeep> i met this team at a conference
17:32:50 <thinrichs> I was just down at SB this weekend.  Should have stopped by :)
17:33:24 <rajdeep> i can introduce you to them
17:33:30 <rajdeep> this team built appscale
17:33:40 <rajdeep> http://www.appscale.com/
17:33:59 <thinrichs> Sounds good.  Introduce us via email if you would.
17:34:08 <rajdeep> sure.
17:35:15 <thinrichs> kudva: mind telling us how you heard about the project and got involved?  Anything else we should be doing?
17:35:46 <kudva> We are working on policies here
17:35:54 <kudva> and also extensively with Openstack
17:36:05 <kudva> So, I looked up the project for policy automation in Openstack
17:36:20 <kudva> For us the most important are a common infrastructure for all kinds of policies
17:36:40 <kudva> compliance, resilience, ....
17:37:46 <pballand> We’ve had substantial interest from lots of users and vendors, but are still trying to push for more developer involvement...
17:37:48 <kudva> So, my interest is to have a common policy support part which is separate from the application part
17:38:06 <pballand> kudva: that sounds like a perfect fit :)
17:38:29 <kudva> Yes, a core engine that does all the datalog/logic programming part, and then many offshoots in different areas
17:38:54 <thinrichs> So it sounds like we need people to realize that having policy separate from application/networking/compute/etc. would help us.
17:38:56 <kudva> yes, looking forward to contributing more
17:38:59 <thinrichs> That's helpful!
17:40:09 <thinrichs> Getting an alpha out may help us quite a bit.  Then we can give people something to play with, and hopefully let them get a feel for what we're aiming at.
17:40:47 <pballand> thinrichs: agreed - (easily) usable examples are key
17:41:06 <thinrichs> Anything else today?
17:41:39 <thinrichs> Good discussion and progress today.  Let's keep it up and follow up on the ML as need be.
17:41:47 <thinrichs> Thanks all!
17:41:51 <kudva> thanks!!
17:42:04 <rajdeep> thanks all
17:42:17 <thinrichs> #endmeeting