17:00:50 <thinrichs> #startmeeting CongressTeamMeeting
17:00:51 <openstack> Meeting started Tue Mar 24 17:00:50 2015 UTC and is due to finish in 60 minutes.  The chair is thinrichs. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:52 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:55 <openstack> The meeting name has been set to 'congressteammeeting'
17:01:46 <thinrichs> rajdeepd: are you joining us today?
17:02:00 <thinrichs> Seems like most people are running a few minutes late.
17:02:52 <rajdeepd> hi
17:02:56 <rajdeepd> yes
17:03:03 <rajdeepd> after few weeks
17:03:09 <arosen> Hi
17:03:46 <thinrichs> rajdeepd: glad to have you with us!
17:03:49 <thinrichs> arosen: hi
17:04:50 <thinrichs> rajdeepd: what have you been up to lately?
17:05:31 <rajdeepd> i was working on the UI for datasources status table
17:05:40 <rajdeepd> janet wanted some changes
17:05:51 <rajdeepd> in the placement location of the table
17:06:01 <rajdeepd> hence trying to rework that
17:06:11 <rajdeepd> and devstack has been giving me trouble
17:06:57 <thinrichs> Sounds good.  Let us know about devstack issues.
17:07:06 <rajdeepd> sure ..
17:07:10 <thinrichs> We use devstack on every commit, but I think it's the same commit.
17:07:19 <rajdeepd> will send email offline
17:07:21 <thinrichs> Sorry—the same devstack (as part of an image).
17:07:32 <thinrichs> Or you could file a bug.
17:07:42 <thinrichs> And then send us email pointing to the bug.
17:07:47 <rajdeepd> yeah, it was fine till a few weeks back
17:08:03 <thinrichs> Good to know.
17:08:14 <thinrichs> arosen: want to give a status update?
17:08:36 <arosen> sure
17:09:06 <arosen> So I've been mostly pulled away on some neutron stuff. But I'm starting to work on a trigger system for congress so that one can make an api call to congress to have it to repolll a datasource.
17:09:16 <arosen> I'm also working on setting up the CI on another openstack cloud
17:09:24 <arosen> so hopefully we'll have that back up and running again soon.
17:09:49 <arosen> that's it from me.
17:10:35 <thinrichs> Sounds good—the trigger system (not to be confused with the policy-engine-trigger blueprint) will be useful, both for debugging and for datasources that can tell us when they have data that needs to be pulled.
17:11:01 <thinrichs> There are a few things happening on my end, so I'll do a status update.
17:11:14 <thinrichs> We're making progress on the reactive enforcement blueprints.
17:11:37 <thinrichs> We have modals in place so we can write policy statements like "execute[disconnectNetwork(x,y)] :- blah"
17:11:50 <thinrichs> We have a first cut of policy-engine-triggers in place.
17:12:27 <thinrichs> I hear we have good progress on actually being able to execute a given action, e.g. disconnectNetwork('vm123', 'net456')
17:12:46 <arosen> nice that sounds excited.
17:12:52 <iben> iben here… hello everyone!
17:12:57 <thinrichs> The policy-engine-triggers should let us set it up so that every time the disonnectNetwork table contents changes, we execute that command.
17:13:09 <thinrichs> iben: hi!  We're doing status updates.
17:13:28 <thinrichs> There's also someone working on publishing the contents of tables defined via policy onto the DSE.
17:13:57 <thinrichs> This way, if another entity subscribes to a table defined by policy, it will actually be published on the bus.
17:14:10 <thinrichs> So I think that's it on the reactive enforcement side.
17:14:22 <thinrichs> The other thing that's happening is on delegation.
17:14:46 <thinrichs> There was a meeting last week, where we split up the work to do a PoC.
17:15:17 <thinrichs> The idea is that Congress policy engine will give policy to a VM placement engine, and it will migrate VMs around that are violating policy.
17:15:33 <thinrichs> One sec and I'll get the link for the proposal.
17:15:45 <thinrichs> #link https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edit#heading=h.5uqcr270fdgk
17:16:09 <thinrichs> At the top of that file, there's a link to the work items and who volunteered for each.
17:16:20 <thinrichs> If anyone wants to pitch in, add your name to the spreadsheet.
17:16:45 <thinrichs> Those are the big things on my side.
17:16:58 <thinrichs> alexsyip: want to give a status update?
17:17:15 <alexsyip> I finished writing the datasource configuration synchronizer.
17:17:41 <alexsyip> The synchronizer reads datasource config from the DB periodically and makes the running datasources match the DB configuration.
17:18:06 <alexsyip> I started testing it, and found some bugs.
17:18:11 <alexsyip> I’m still working on that.
17:18:32 <alexsyip> This work was for the HA solution.
17:18:55 <thinrichs> Great!  It'll be nice to have some HA in place.
17:19:26 <thinrichs> stevenldt: want to go next?  How's the action execution progressing?
17:19:35 <stevenldt> sure.
17:20:23 <stevenldt> so far we have the end-to-end flow working using the existing API (same one we use for simulate)
17:20:54 <stevenldt> I submitted a WIP review to get some feedback
17:21:12 <thinrichs> stevenldt: great!
17:21:33 <thinrichs> I've been buried, and haven't made my usual passes over the list of all outstanding reviews recently.
17:21:54 <thinrichs> If you add me as a reviewer, it'll be eaiser for me to remember.
17:22:07 <thinrichs> But in any case I'll try to get you some feedback later today.
17:22:26 <stevenldt> next thing to do is to separate the action execution handler from the datasource so it can be more easily identified
17:23:39 <thinrichs> Sounds good.  Hopefully we can iterate quickly through the reviews to get something functional in place.
17:23:43 <thinrichs> Then we can optimize from there.
17:24:05 <thinrichs> jwy: want to give a status update?
17:24:28 <jwy> almost done with front end for the next revision of the policy creation ui
17:24:53 <stevenldt> yes, I think so far it looks good.
17:24:54 <jwy> after the inputs are settled, need to write the backend translation into datalog
17:25:24 <jwy> i wanted to ask about the upcoming design summit. i'll wait until status updates are done
17:25:56 <thinrichs> jwy: sounds good.  Let me know if you want help with the datalog.
17:26:06 <jwy> thinrichs: ok thanks
17:26:33 <thinrichs> sarob: any updates this week?
17:27:10 <sarob> #link https://review.openstack.org/#/c/165204/
17:27:46 <sarob> Congress project patch
17:28:06 <sarob> I will be reviewing with the TC in their meeting today
17:28:31 <sarob> Monty and Doug like
17:28:37 <thinrichs> Great!
17:28:38 <sarob> It's a good start
17:28:53 <thinrichs> Let us know if there's anything we should be doing to help.
17:28:58 <sarob> That's all I have
17:30:14 <thinrichs> Did I miss any of the regulars who have status updates?  (Before we hear from Iben?)
17:30:26 <iben> i don’t have anything much
17:31:21 <thinrichs> iben: want to describe what you're interested in, for those who don't know?
17:31:29 <iben> if there is time I do have a question about how congress is handling their documenation… is it just a readme.md using git markup?  will you worry about generating PDF docs?
17:31:56 <iben> we are looking to work with project in the OPNFV COPPER project
17:32:11 <iben> #link https://wiki.opnfv.org/copper
17:32:27 <thinrichs> iben: we're doing the usual openstack thing.  Docs are written in rtf, which are compiled to HTML in the makefile.  I *think* they're also being published to a documentation hub somewhere.
17:32:37 <thinrichs> No plans for PDF support.
17:32:46 <iben> gotcha - thanks!
17:33:11 <iben> when you say “the usual openstack thing” it is not well understood for us newbies.
17:33:21 <thinrichs> :)
17:33:52 <thinrichs> Seems like we're done with status updates.
17:34:01 <thinrichs> Let's open it up for discussion.
17:34:05 <thinrichs> #topic open discussion'
17:34:15 <thinrichs> jwy: you wanted to talk about the upcoming summit.
17:34:29 <jwy> yep, have we started planning for the design summit? any sessions?
17:34:50 <jwy> i'm going to meet up with Yali to go over the UI, if she can make it to the summit
17:35:03 <jwy> would be cool to carve out some time for that if other folk want to join
17:35:13 <jwy> maybe try to pull in some horizon people :)
17:35:37 <david-lyle> horizon people?
17:35:44 <jwy> to help with the ui
17:36:13 <thinrichs> david-lyle: Congress people right now.
17:36:20 <david-lyle> ah, ok
17:36:42 <david-lyle> I'm happy to help out as needed
17:36:52 <jwy> david-lyle: i meant, try to get some more congress contributors that do ui work (e.g., horizon)
17:36:58 <thinrichs> david-lyle: sorry—I didn't realize you were responding to Janet's comment.
17:37:07 <thinrichs> david-lyle: thought you were looking for the Horizon meeting.
17:37:29 <david-lyle> I just get pinged on 'horizon'
17:37:45 <david-lyle> sorry to derail
17:38:16 <thinrichs> david-lyle: funny exchange, actually.  :)
17:38:29 <thinrichs> sarob: how do we get set up with a design session?
17:38:36 <thinrichs> sarob: do we apply?
17:38:47 <thinrichs> BTW, we did get 2 talks accepted.
17:38:54 <thinrichs> Helping Telcos go Green and save OpEx via Policy
17:39:06 <thinrichs> #link https://www.openstack.org/vote-paris/presentation/helping-telcos-go-green-and-save-opex-via-policy
17:39:12 <thinrichs> Congress Hands on Lab
17:39:15 <sarob> I made a request to foundation
17:39:24 <thinrichs> #link https://www.openstack.org/vote-paris/presentation/congress-hands-on-lab
17:39:42 <sarob> And I can check
17:40:14 <sarob> And if the rooms are set up
17:41:01 <thinrichs> That'd be great!
17:41:19 <thinrichs> Don't hesitate to put me on emails if I can help out.
17:42:17 <thinrichs> Is there anything else we should discuss about the summit?
17:42:53 <thinrichs> Anything else to discuss, or should we end a bit early today?
17:43:44 <thinrichs> I'll call it then.
17:43:53 <thinrichs> Thanks all!  Talk to you next week.
17:44:25 <thinrichs> madhumohan: you here for Congress?
17:44:55 <thinrichs> madhumohan: we were just about to finish
17:45:00 <pettori> was iben gonna provide an update on what they are planning ?
17:45:39 <thinrichs> pettori: I think everybody is gone.
17:45:48 <thinrichs> Just before ending the meeting I saw madhumohan log on.
17:45:53 <iben> we’re not sure (I’m not up to speed) but we need intent and policy for nfv placement on openstack
17:46:09 <iben> things like affinity and anti-affinity
17:46:13 <madhumohan> thinrichs: yes. Just wanted to update I will be resuming to work with congress this week..
17:46:27 <thinrichs> madhumohan: Awesome!
17:46:38 <iben> and we are looking to use deployment tools like saltstack and anisble to deploy congress
17:47:13 <jwy> iben: are you working with bryan_att (sorry, i don't know his actual name)? i know he was also working on saltstack + congress
17:47:20 <iben> yes
17:47:36 <jwy> ok cool, was just curious
17:47:50 <thinrichs> madhumohan: I have a task that we need to get done before reactive enforcement will work, if you're interested.
17:47:55 <iben> bryan sullivan
17:48:20 <iben> for now intent definition and audit is enough
17:48:25 <iben> enforcement can come later
17:48:49 <iben> the actual use cases are here #link https://wiki.opnfv.org/copper/use_cases
17:49:10 <iben> this one I’m not so sure we can do at all - Geo-Diverse Service Instance Deployment
17:49:19 <iben> any thoughts on that?
17:49:31 <iben> As a service provider, I need my software application deployed in a geo-diverse environment with resources configured to meet specific quality of service, so I can ensure an acceptable user experience.
17:53:11 <thinrichs> It's been quiet for a while.  I'm going to end the meeting (for real this time).
17:53:14 <thinrichs> Thanks all!
17:53:17 <thinrichs> #endmeeting