17:01:47 <pballand> #startmeeting CongressTeamMeeting
17:01:48 <openstack> Meeting started Tue Sep 23 17:01:47 2014 UTC and is due to finish in 60 minutes.  The chair is pballand. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:49 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:01:51 <openstack> The meeting name has been set to 'congressteammeeting'
17:01:59 <pballand> howdy
17:02:04 <banix> hi
17:02:19 <jchen_> hello
17:02:25 <sarob> hallo
17:02:52 <dconde> hello
17:03:37 <pballand> want to start with a summary of the policy summit last week
17:04:08 <pballand> for those lurking or reading the logs, we had over 50 attendees last week in Palo Alto
17:04:43 <pballand> we had some great presentations from projects on their policy related features and roadmaps, and and excellent workshop day
17:04:58 <sarob> was awesome display of collaboration
17:05:08 <pballand> thanks again for all who participated!
17:05:19 <jchen_> thx for hosting the summit!
17:05:24 <dconde> also, thanks for the guest speaker(s) andl lightening talk
17:05:40 <pballand> notes from the summit can be found here: https://etherpad.openstack.org/p/juno-midcycle-policy-summit
17:05:49 <pballand> #link https://etherpad.openstack.org/p/juno-midcycle-policy-summit
17:06:15 <sarob> lots of new work and ideas to get ready for the kilo summit
17:06:42 <pballand> for those who had to leave early, we finished day two by creating a list of action items with owners - can be seen at the bottom of the etherpad linked above
17:07:24 <pballand> if there are items we missed, or you would like to participate in one of the items on the list, please add your name to the list, or participate in the spec creation
17:08:10 <s3wong> pballand: are the blueprints filed for those items?
17:08:50 <pballand> s3wong: the owner of each item is responsible for creating the bp
17:09:52 <pballand> #link https://wiki.openstack.org/wiki/Congress#How_To_Create_a_Blueprint
17:10:15 <pballand> instructions for creating a blueprint / spec can be found on the wiki link above
17:10:31 <pballand> I’m looking forward to seeing those come in
17:10:57 <pballand> lets go through a quick status update
17:11:01 <pballand> who would like to go first?
17:11:35 <pballand> not all at the same time :)
17:11:54 <alexsyip> I’m working on generalizing the data source drivers
17:11:56 <dconde> you’re asking the BP owners?
17:12:13 <alexsyip> And I will create a few bps for the table triggers
17:12:58 <pballand> alexsyip: great - can you give a guess on when you may be able to post a draft on the spec?
17:13:05 <sarob> im going through the specs i signed on to help straz with
17:13:14 <pballand> dconde: yes, bp owners, or any work in progress
17:13:30 <alexsyip> For the drivers, I already pushed a spec to gerrit.
17:13:40 <alexsyip> For the triggers, I will work on that today.
17:15:23 <pballand> alexsyip: I assume you mean https://blueprints.launchpad.net/congress/+spec/refactor-drivers
17:15:28 <pballand> is there a spec this can link to?
17:16:12 <alexsyip> https://review.openstack.org/#/c/123288/
17:17:08 <pballand> alexsyip: thanks - will review
17:17:47 <alexsyip> thanks.
17:17:55 <pballand> process question (maybe sarob knows?) how can blueprints be linked to specs that are still in review?
17:18:25 <rajdeep> alexsyip: i dont think we have a keystone driver yet ,
17:18:27 <sarob> The way i set it up was to have the new spec
17:18:34 <rajdeep> you mention rewriting it
17:18:34 <sarob> and blueprint linked together
17:18:41 <alexsyip> The keystone driver is in code review.
17:18:49 <rajdeep> ok
17:18:57 <sarob> but the blueprint doesnt get approved until after the spec gets merged
17:19:26 <banix> i think i  saw a driver for keystone
17:19:35 <banix> ahh yes in review
17:19:35 <pballand> does it make sense to set the url in the blueprint to the review until the spec is merged, then update it?
17:19:41 <sarob> the current patch is linked to the blueprint and vice verses
17:19:47 <sarob> yup
17:20:07 <sarob> that way if you find the spec or the bp, you will find the other
17:20:36 <alexsyip> For the driver blueprint, there is no link to the spec code review.  Am I supposed to add the link manually ?
17:20:59 <sarob> yup, manually
17:21:09 <alexsyip> oh ok.  I’ll add the link now.
17:21:22 <pballand> alexsyip: I just updated it
17:21:51 <pballand> alexsyip: it also looks like you own the keystone driver - can you update the status on that?
17:22:37 <arosen> sorry lost track of time X.x
17:23:14 <alexsyip> Hm. not sure how yet.
17:23:59 <pballand> alexsyip: was just asking if you were actively working on that patch
17:24:09 <pballand> https://review.openstack.org/#/c/122271/
17:24:21 <alexsyip> I am waiting for a second round of code review.
17:24:50 <sarob> alexsyip: the extra step you asked about, i just added to the how to create a blueprint instructions
17:24:53 <arosen> alexsyip:  Most of the times jenkins has to pass before people will look at the review fyi .
17:27:04 <pballand> anyone else with a status update?
17:27:39 <LouisF> browsing the congress code
17:27:54 <rajdeep> i started looking at the horizon code
17:28:00 <alexsyip> Ok, I see that now.
17:28:01 <rajdeep> for congress dashboard
17:28:27 <arosen> I've been still turning away at the CI stuff. Hopefully I should be able to get a test tempest tests working with congress sometime this weel.
17:28:33 <rajdeep> figuring out the code which janet shared
17:28:52 <pballand> rajdeep: can you please create a bp for congress-dashboard?
17:29:14 <rajdeep> sure.. was facing some issues with janet's code
17:29:33 <madhumohan> I am working on adapting ceilometer driver to new interfaces as per comments from Tim... and also on the test code.
17:31:47 <kudva> Hi kudva
17:32:12 <pballand> madhumohan: great - do you have everything you need / any blockers?
17:34:55 <madhumohan> going well so far... found one issue while testing with a simple ceilometer based policy --- "Unknown arity for table "ceilometer:meters"" ..  Not very sure of how to correct this...
17:36:04 <kudva> madhumohan: is this error coming from your python code accessing ceilometer api (sorry, I missed part of this discussion)
17:36:58 <kudva> ignore last comment. looks like this i part of tables discussion. Sorry
17:37:43 <pballand> madhumohan: I don’t know the issue offhand - probably best to ask in #congress
17:38:20 <pballand> #topic Open Discussion
17:39:04 <pballand> any questions / topics / concerns to discuss?
17:39:27 <kudva> I have pushed some code, will wait for review
17:39:29 <kudva> https://review.openstack.org/121418
17:40:34 <pballand> kudva: great - will take a look
17:40:42 <kudva> pballand: ok
17:40:46 <kudva> pballand: thanks
17:42:01 <pballand> is it clear to everyone how to propose blueprints and write specs?
17:42:07 <pballand> (and what the value of doing so is?)
17:42:30 <sarob> is to me ;)
17:42:58 <pballand> sarob: :-)
17:43:46 <sarob> i think our mentoring teams we broke up into on friday will help with explaining how the process works
17:43:51 <pballand> the goal is to add substantial visibility to the project, with minimal overhead to devs
17:44:42 <sarob> im planning on setting a public schedule for working with straz, so others can join in on how to write specs
17:44:50 <pballand> please reach out if you are frustrated/annoyed with the process - this should only take a couple minutes, and helps everyone understand what is being worked on
17:44:52 <sarob> maybe that can help
17:46:14 <pballand> okay, I think that’s it this week
17:46:36 <pballand> thanks for joining the conversation
17:46:47 <pballand> we’ll see you on the mailing list and in #congress
17:47:07 <pballand> #endmeeting