17:00:49 <pballand> #startmeeting CongressTeamMeeting
17:00:50 <openstack> Meeting started Tue Nov 18 17:00:49 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:51 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:54 <openstack> The meeting name has been set to 'congressteammeeting'
17:01:15 <pballand> thinrichs is out this week, so I will be running the meeting
17:01:17 <pballand> anyone around?
17:01:26 <sarob> Morn
17:02:01 <pballand> hi sarob
17:02:03 <pballand> welcome back
17:02:18 <sarob> Thx
17:02:49 <banix> hi
17:03:08 <pballand> banix: hi
17:03:17 <jasonsb> hallo
17:03:28 <kudva> hi
17:03:36 <pballand> welcome everyone
17:03:52 <pballand> I’ll go ahead and kick things off with an update from the administrative side
17:04:25 <pballand> at the summit, we discussed several blueprints and requested they be submitted by last friday
17:04:50 <pballand> there has been quite a bit of activity here
17:04:57 <pballand> #link https://blueprints.launchpad.net/congress
17:05:25 <sarob> 24 by last night
17:05:37 <pballand> thinrichs couldn’t make it today, but he submitted numerous blueprints, and there are a lot of specs for review
17:05:57 <pballand> #link https://review.openstack.org/#/q/status:open+congress-spec,n,z
17:06:32 <pballand> if you comitted to add a blueprint and haven’t yet done so, please push it asap
17:06:56 <pballand> lets get a quick status update from around the room
17:07:09 <pballand> who wants to go first?
17:08:10 <pballand> sarob: mind giving an update?
17:08:46 <sarob> Sure
17:09:15 <sarob> We met with a lot of people over the summit
17:09:32 <sarob> The two follow up deep dives
17:09:58 <sarob> I am now following up with what commitments
17:10:18 <sarob> People and companies can make to the kilo release
17:10:23 <sarob> Of congress
17:10:53 <sarob> If you haven't heard from me by mid week
17:11:00 <sarob> Please reach out
17:11:20 <sarob> So we have a gauge of how much work we can get
17:11:30 <sarob> Done this release cycle
17:12:19 <sarob> That's it for me
17:12:34 <pballand> ok, thanks
17:12:51 <banix> I did a few code reviews. was looking at the specs and I think the priority of blueprints need to be set so one can get a better idea about them
17:13:30 <pballand> banix: agreed - the push last week was to get the bluprints published, and now it will be on reviewing and prioritizing them
17:13:53 <pballand> ideally, we would have the blueprints before the summit, but we are a week or two behind
17:14:12 <sarob> Seems like the summit design etherpad
17:14:20 <pballand> I don’t that that is a bad thing at this level or project maturity, however
17:14:24 <sarob> Is a good place to hash out
17:14:33 <sarob> Priorities
17:15:00 <sarob> Some of the bp are there but needs an update
17:15:32 <pballand> banix: id the challenge that there are too many to look at/understand, or just you don’t know where your time would be best spent?
17:16:09 <banix> the latter; i think it wont be bad to have ptl ;) go through them and assign a priority to start with
17:16:52 <banix> of course the priorities can change but having an initial priority will give an structure to what is there and identify major (and less major) areas to work on
17:17:21 <pballand> banix: agreed - I think its reasonable to have that by next week
17:17:40 <pballand> (since thinrichs isn’t here to defend himself, I’ll go ahead and assign that to him ;) )
17:17:44 <jasonsb> banix: i think this is also a function of how many people are working on them per sarob's point
17:18:02 <sarob> Banix what's yours
17:18:04 <pballand> #action PTL to prioritize blueprints by 11/25 meeting, pballand to assist
17:18:30 <kudva> banix: prioritizing will also depend on who will be working on coding those, and with expertise on them no?
17:18:39 <banix> pballand: thanks. I am a bit out of the loop as I had to take several weeks off work for personal reasons and had to cancel my trip to the summit so others may have a better handle of what is what
17:18:46 <pballand> banix: do you have any blueprints to add, or any other updates?
17:19:16 <banix> no that’s it for me for now
17:20:16 <pballand> banix seems to have left
17:20:36 <banix> pballand: no just responded
17:20:51 <pballand> ok, thanks banix
17:21:36 <pballand> in case you missed it, all of the notes from the summit are in the etherpad: https://etherpad.openstack.org/p/par-kilo-congress-design-session
17:21:46 <pballand> jasonsb: mind giving an update next?
17:22:00 <jasonsb> sure
17:22:23 <jasonsb> i don't have too much.  working on getting something set up with security people to discuss congress
17:22:43 <jasonsb> try to have something this week
17:23:13 <jasonsb> also want to thank arosen for generous time last week to go through some QoS things
17:23:54 <jasonsb> besides that i had a question for the end: murano integration and the recent keystone policy post to the ML
17:24:09 <jasonsb> are they solving different problems or same
17:25:15 <rayv> Hello my name is Ray Valdez and I am interested in contributing to congress  with respect to security.
17:25:15 <jasonsb> thats it for me
17:25:26 <pballand> jasonsb, lets give kudva a chance for a status update, and then we can get in to that
17:25:41 <arosen> whoops sorry i'm late. Was thinking it was still at 10am still x.x
17:25:58 <pballand> rayv: hello and welcomed
17:26:24 <pballand> kudva: mind giving an update?
17:26:45 <pballand> rayv: would you mind giving a quick intro after kudva?
17:27:04 <kudva> I started some work on ceilometer integration but a few weeks had to drop it.
17:27:15 <kudva> Will pick it up again and submit something by next week.
17:28:03 <kudva> also, workign with a colleague in security to develop a blueprint
17:28:42 <rayv> I am from IBM Research and work in the area of secure systems
17:28:59 <pballand> kudva: great - there has been some work ongoing with the ceilometer plugin, and we met with the team in Paris
17:29:16 <pballand> what specific features are you working on?
17:29:21 <kudva> pballand: would llike to get an update on that
17:30:27 <kudva> pballand: I was looking to see how alarms may be used to communicate between congress and ceilometer
17:30:28 <pballand> I don’t know the specifics on the driver work - but there are three patches in code review
17:30:40 <kudva> pballand: will look, thanks
17:31:07 <pballand> from the team, the way we are polling aggregated stats is inefficient with the current implemenation, and alarms won’t help
17:31:22 <pballand> ceilometer is looking at improving the efficiency of aggregation in this release
17:31:48 <pballand> other than that, I would recommend reaching out wo Pierre ettori and Madhu Mohan for details on their patches
17:32:07 <kudva> pballand: okay, will do that.
17:33:41 <pballand> arosen: do you have any updates to share?
17:33:47 <arosen> pballand:  sure
17:34:12 <arosen> On my end the CI has been failing over the last day. Unfortunately, a change merged into devstack that broke anyone using precise as a slave. The devstack fix (https://review.openstack.org/#/c/135163/) is now in the process of merging so hopefully we should be up and running shortly.
17:34:41 <arosen> I'm also working on refactoring the base datasource framework which should hopefully improve a number of things. Here's a WIP patch for that work: https://review.openstack.org/#/c/135099/
17:35:13 <arosen> Here's the blueprint i have for the specs refactoring work: https://review.openstack.org/#/c/134420/
17:35:36 <arosen> that's all from me unless anyone wants to talk about this.
17:35:50 <pballand> thanks arosen
17:36:25 <pballand> rayv: what brings you to the congress project?
17:36:50 <rayv> I am interest in security policy enforcement
17:37:50 <pballand> fantastic - do you have something in particular you are looking to contribute?
17:39:08 <rayv> I have a simple blueprint that I would like to implement as starting point, isolating physical systems for tenants.
17:40:05 <pballand> rayv: I don’t recall seeing that - have you submitted it to launchpad and/or gerrit?
17:40:53 <rayv> I haven't yet,  I will work with kudva to submit.
17:41:12 <pballand> ok, fantastic
17:42:01 <pballand> having example use cases that others can follow is great for the project - I’m excited to see how it goes
17:43:21 <pballand> did I miss anyone with status updates?
17:43:37 <alexsyip> I have been working on a parent-key relation for datasource drivers.
17:43:38 <pballand> (we still have jasonb’s question)
17:43:50 <alexsyip> I have a change on gerrit that more or less works, but I need to work on it some more.
17:44:08 <alexsyip> Aaron is using it for the glance driver work.
17:44:20 <alexsyip> I’m also working on a blueprint/spec for a heat driver.
17:44:28 <alexsyip> I should have something today for that.
17:45:22 <alexsyip> That’s all.
17:45:44 <pballand> alexsyip: thanks
17:46:22 <jwy> i'll give updates on the horizon items before i drop out of the room again (internet is being flaky)
17:46:38 <pballand> ok, I’m going to open the floor to jasonsb, and any other topics that people want to bring up
17:47:29 <jwy> finishing up the spec/bp for creating policies in horizon
17:48:16 <jwy> and rajdeep is still working on adding view of data source tables
17:49:09 <jwy> jasonb: you had suggested bip.io in the kilo etherpad for creating policies - wondering if you had specific thoughts on that?
17:50:06 <jasonsb> jwy: no specific thoughts.  i was going to attempt to put something together for a POC
17:50:19 <jasonsb> jwy: alas, i got lazy last week
17:50:35 <jwy> haha ok
17:50:44 <jasonsb> jwy: i will try to put together something for a demo
17:51:52 <jwy> cool
17:52:17 <pballand> jasonsb: were you referring to this keyston emai: http://osdir.com/ml/openstack-dev/2014-11/msg01191.html ?
17:54:07 <jasonsb> yes
17:54:29 <jasonsb> thats the one
17:54:50 <pballand> I know thinrichs was working on doing something similar in Congress - injest all the RBAC config files, and answer questions similar to those in the eimail
17:54:53 <pballand> *email
17:55:13 <pballand> to me, this seems like an appropriate problem for Congress - what do others think?
17:56:26 <jasonsb> looked kind of like an invitation, but i didn't sit in on any of the keystone discussions
17:56:36 <jasonsb> so i was just curious if anybody had more context
17:57:29 <pballand> thinrichs and I were too swamped to attend any keystone sessions , unfortunately
17:57:54 <pballand> it definitely seems like something we should engage with over the mailing list
17:59:11 <pballand> only 2 more minutes - any last minute comments to squeeze in?
18:00:01 <alexsyip> I agree.  Tim has already started working on something for this.  The last time the openstack list had a discussion about it, Tim was involved.
18:00:16 <alexsyip> I’ll let him know there’s more activitiy on the keystone list.
18:01:04 <pballand> thanks alexsyip
18:01:08 <pballand> thanks everyone for joining
18:01:11 <pballand> have a great week!
18:01:16 <jasonsb> bye
18:01:19 <banix> bye
18:01:19 <pballand> #endmeeting