17:07:43 <thinrichs> #startmeeting CongressTeamMeeting
17:07:44 <openstack> Meeting started Tue Jan 27 17:07:43 2015 UTC and is due to finish in 60 minutes.  The chair is thinrichs. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:07:45 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:07:48 <openstack> The meeting name has been set to 'congressteammeeting'
17:08:03 <thinrichs> Let's start with status
17:08:06 <thinrichs> #topic status
17:08:13 <thinrichs> Who wants to start?
17:08:53 <arosen-train> I can start if no one wants to go.
17:09:05 <arosen-train> I've been working with pivotal on integration pivotal.io with congress.
17:09:05 <thinrichs> arosen-train: go for it.
17:09:24 <arosen-train> There are two parts of active development here.
17:09:35 <arosen-train> The first one is to create python-bindings to interface with their api.
17:09:46 <arosen-train> Currently they only have go bindings
17:10:30 <arosen-train> The python bindings are going to be on stackforge in python-cloudfoundryclient once this merger https://review.openstack.org/#/c/149173/
17:11:13 <arosen-train> the second part is the congress datasource driver which i'm working on with another guy at pivotal so hopefully that will be pushed to review later this week.
17:11:22 <arosen-train> That's all unless anyone wants to discuess.
17:11:30 <thinrichs> Cool stuff!
17:11:43 <thinrichs> Integrating with Cloudfoundry will give us the ability to write policy at the app-layer.
17:11:53 <thinrichs> Which everyone seems to want.
17:12:50 <arosen-train> yup, excited to see this happening.
17:13:03 <zhipeng> thinrichs one quick word, I'm still on track on the trigger BP, I'm trying to catch the K-2 target
17:13:16 <arosen-train> zhipeng:great!
17:13:23 <thinrichs> zhipeng: super!
17:13:26 <thinrichs> How's it going?
17:13:31 <zhipeng> there are just a hell of stuff going around me, but I'm on track
17:13:32 <thinrichs> Need anything from us?
17:13:39 <zhipeng> one silly question
17:13:51 <zhipeng> do u know how to test my patch locally using devstack?
17:14:01 <zhipeng> I asked sean days ago
17:14:05 <arosen-train> zhipeng: what do you mean by test?
17:14:09 <arosen-train> as in run the tempest tests?
17:14:32 <zhipeng> I guess so, just want to be sure before I submit
17:14:37 <thinrichs> zhipeng: could you be more specific about what tests you'd like to run?
17:14:45 <thinrichs> Are you running tox -epy27
17:14:46 <arosen-train> zhipeng: there are two kinds of tests that congress has. Unittests/pep8 tests and tempest.
17:15:02 <arosen-train> also tox -epep8  to run the style checker.
17:15:41 <zhipeng> I just have a vague idea, I played with odl+openstack sometimes ago, when we tried to modify stuff we could check out if the patch is working
17:15:44 <zhipeng> locally
17:15:48 <arosen-train> To run the tempest tests  you need to have devstack setup tempest. Just add tempest to ENABLED_SERVICES and then follow: https://github.com/stackforge/congress/tree/master/contrib/tempest
17:15:49 <zhipeng> with devstack
17:16:02 <zhipeng> ah great
17:16:34 <arosen-train> zhipeng: right a while ago devstack had some simple tests to do some sanify stuff but i don't think devstack was running tempest for you?
17:17:08 <zhipeng> not tempest
17:17:42 <arosen-train> zhipeng: ah okay, i believe those exercise scripts have been removed from devstack in favor of tempest.
17:18:14 <zhipeng> yes that's right
17:18:29 <zhipeng> and I think the link you provide is what im looking for
17:18:41 <zhipeng> thx for the info :)
17:18:41 <arosen-train> zhipeng: i lied they aren't removed but not being run by jenkins. https://github.com/openstack-dev/devstack/tree/master/exercises
17:19:10 <arosen-train> I think we should just do all of this testing in tempest as well rather than having a bash script with some tests.
17:19:31 <zhipeng> yep
17:19:51 <zhipeng> great I will try it out
17:20:04 <zhipeng> gotta go fellas it's really late in China
17:20:17 <zhipeng> I will send you guys emails if something troubles me
17:20:23 <zhipeng> thanks for the help :)
17:20:23 <arosen-train> sounds good. NIght
17:20:47 <thinrichs> Sounds good.  And don't be bashful about pushing code to review.  You can always mark it Work-in-progress.
17:20:56 <thinrichs> zhipeng: thanks for staying up late for us!
17:21:20 <thinrichs> jwy: want to go next?
17:21:37 <jwy> ok
17:21:57 <jwy> not much progress on the horizon policy creation blueprint
17:22:05 <jwy> did some code reviews
17:22:24 <jwy> i think that's it
17:23:51 <thinrichs> Any idea as to an ETA for the horizon policy creation?
17:24:09 <thinrichs> kilo2 is Feb 5.
17:25:27 <thinrichs> Looking through the other high priority blueprints to see if those folks are here…
17:26:37 <jwy> sorry, i got disconnected and missed if anyone said anything to me
17:26:53 <thinrichs> jwy: I asked if you had a guess when you'd have the horizon policy creation done.
17:28:05 <jwy> thinrichs: i probably need through next week
17:28:38 <thinrichs> jwy: in the next couple of weeks is great!
17:28:51 <thinrichs> alexsyip: want to take a turn?
17:28:55 <jwy> kilo-2 deadline is 2/12?
17:29:13 <alexsyip> yeah, I worked on speeding up the import from dse to the congress runtime.
17:29:48 <alexsyip> Now, importing 700MB in 7M rows takes 80 seconds and uses 4GB of memory.
17:30:01 <alexsyip> This is down from last week at 10min and 12GB.
17:30:13 <jwy> woot
17:30:18 <alexsyip> which was down from infinite time and memory.
17:30:54 <alexsyip> So big change that went into this was to store facts as native tuples instead of using a bunch of python objects like Literal, Rule, Param.
17:31:57 <thinrichs> alexsyip: Fantastic!
17:31:58 <alexsyip> And I streamlined the initialize_tables code to use generators.
17:32:04 <alexsyip> So we avoid creating a bunch of lists.
17:32:47 <alexsyip> So I think importing is fast enough now.
17:33:12 <thinrichs> That's really exciting progress.  And will be crucial for working with real systems.
17:33:17 <alexsyip> I have not tested how DSE handles this much data.
17:34:14 <alexsyip> anyway, that’ all.
17:34:25 <thinrichs> Thanks!
17:34:29 <thinrichs> sarob: want to go next?
17:36:07 <arosen-train> sarob:might be tied up with the nova midcycle that's going on now.
17:36:16 <thinrichs> Okay.
17:36:28 <thinrichs> There's one idea we've been kicking around.
17:36:46 <thinrichs> What would people think about having a sprint in the near future?
17:37:06 <thinrichs> We'd get people together for a day or two to churn out some code.
17:37:14 <thinrichs> People could participate remotely as well.
17:37:37 <thinrichs> Who thinks that sounds good?
17:37:55 <jwy> i think that could be useful
17:37:56 <arosen-train> That sounds like a fun idea. I would be down to attend.
17:39:24 <thinrichs> Seems like we're missing a few folks.  Maybe we'll also reach out via email/ML to gauge interest.
17:39:46 <arosen-train> I think it would be good if we could come up with some small projects in congress as well. I feel like the blueprints we currently have out there might be to large for someone to bite off in a hackathon
17:39:47 <thinrichs> Trying to think what other updates sarob might have...
17:40:26 <thinrichs> Good suggestion.
17:40:47 <arosen-train> I know we could definitely get people started writing some tempest scenario tests.
17:40:50 <thinrichs> Shall we each try to put together (at least) 2 bite-sized blueprints by next week?
17:40:55 <jwy> are there bugs that would be hackathon worthy?
17:40:58 <thinrichs> Even if we don't have the sprint, that could be useful.
17:41:01 <arosen-train> Would could be interesting since we could come up with some real use case policies and implement them.
17:41:30 <jwy> i think we tagged some bugs as low-hanging at some point. time to go through the newer ones and do it again?
17:41:44 <thinrichs> jwy: that's another good suggestion.
17:41:46 <arosen-train> jwy:probably :)
17:42:04 <thinrichs> Let's all make an effort this week to create blueprints and bug reports.
17:43:16 <arosen-train> sounds good
17:43:44 <thinrichs> Radu_: you still around?  Have anything to report?
17:44:03 <Radu_> Yeah, didnt have any time conflict for a change this week
17:44:32 <Radu_> Nothing much to report though, made a patch for the plexxi driver to sort out some issues it had with the horizon integration
17:44:32 <thinrichs> Glad you could make it this week!
17:44:53 <Radu_> Sort of inbetween projects at the moment
17:45:53 <thinrichs> Radu_: would you like suggestions as to your next project?  :)
17:47:11 <Radu_> maybe out of the meeting I could take a few, I would have to pass them upward to get approval to work on them though.
17:47:38 <sarob> im back
17:48:08 <Radu_> But yeah, thats about all I have, a patch and I submitted a bug report for horizon integration last week
17:48:13 <thinrichs> Radu_: of course.  If you want suggestions, let us know.
17:48:22 <thinrichs> We always love bug reports.
17:48:28 <thinrichs> We also always love code reviews.
17:48:43 <thinrichs> jwy: I've noticed you've been doing quite a few more reviews: nice!
17:49:13 <thinrichs> sarob: anything to report?  We discussed the sprint already.
17:49:37 <sarob> nope, the sprint was it
17:49:53 <thinrichs> Anyone else with a status report?
17:50:35 <jwy> thinrichs: thanks, trying to familiarize myself more with other parts of the code
17:51:24 <thinrichs> Let's open it up for discussion for a few minutes.
17:51:29 <thinrichs> #topic open-discussion
17:52:31 <madhumohan> thinrichs: modal operators is in reviews. have some errors after rebase..these errors do not seem to be related to the changes done... need to fix them up...
17:52:59 <thinrichs> madhumohan: great!  I'll take a look hopefully today.
17:53:27 <thinrichs> Sorry—there have been some pretty massive changes to the policy engine (textually).  Let us know if you want help with the rebase.
17:56:13 <thinrichs> Anyone else?  Last call.
17:57:04 <thinrichs> Thanks all!  Keep in touch over IRC and the ML.
17:57:07 <thinrichs> See you next week!
17:57:30 <thinrichs> #endmeeting