17:01:24 <pballand> #startmeeting CongressTeamMeeting
17:01:24 <openstack> Meeting started Tue Aug 12 17:01:24 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:25 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:01:28 <openstack> The meeting name has been set to 'congressteammeeting'
17:01:35 <arosen> hi
17:01:39 <harrisonkelly> hey
17:01:40 <pballand> good morning
17:01:48 <alexsyip> Hi
17:01:59 <Basil_Saito> Howdy
17:02:30 <pballand> lets get started
17:03:03 <rajdeep> hi all
17:03:09 <pballand> we’ve been working to stabilize things after the large commits of code that have gone in recently
17:03:21 <sarob> morning
17:03:26 <kudva> Hi
17:03:30 <pballand> unfortunately it looks like some of the installs and tests have been broken, so that is a big focus area this week
17:04:12 <pballand> harrisonkelly: I think this is your first meeting - care to introduce yourself, and what brings you to congress?
17:04:24 <harrisonkelly> Of course
17:05:52 <harrisonkelly> I’m Harrison Kelly, I’ve been interning at Plexxi since May (I’m from umass lowell) and finished a big integration project with vCenter and Plexxi using the DSE (Derick’s version from before it went into Congress). Derick thought that it would be a good idea for me to get involved in the project and I thought it would also be good for me to get more experience working with and
17:05:53 <harrisonkelly> contributing to open source software
17:06:18 <cloudtoad> What's up, Harrison?
17:06:23 <harrisonkelly> hey Derick
17:06:47 <pballand> great, we’re happy to have your help :)
17:06:51 <harrisonkelly> thanks!
17:07:39 <pballand> lets go through status updates
17:08:00 <pballand> Basil_Saito: since you’re also new to the meeting, would you like to go?
17:08:13 <Basil_Saito> Hello!
17:08:45 <Basil_Saito> I am an intern at the Marist College IBM/Join Study datacenter
17:09:10 <Basil_Saito> I work alongside Radu_, he is a programmer, I am the SysAdmin
17:09:37 <Basil_Saito> It's a pleasure to be here and see what we can do with Congress!
17:10:03 <pballand> great, welcome!
17:10:21 <pballand> Basil_Saito: do you have any particular use case you are targetting?
17:10:57 <Basil_Saito> Radu_ can provide some input on that
17:11:36 <pballand> hi Radu_ you around?
17:11:43 <Radu_> yeah
17:12:11 <Radu_> We are creating a driver in order to integrate  Plexxicore with openstack
17:12:36 <thinrichs> Radu_: Great!
17:12:41 <thinrichs> (sorry I'm late)
17:12:56 <Radu_> I have some diagrams outlining a rough usecase that I was working on improving a bit, but the general idea is to use congress to help create affinites between VM's on a network using data from plexxi and other sources such as nova
17:13:15 <pballand> Radu_: that sounds awesome!
17:13:19 <Radu_> https://onedrive.live.com/view.aspx?resid=1F3E9DE6C22F170A!171&ithint=file%2cpptx&app=PowerPoint&authkey=!APYFH_qEqMXu2v8
17:13:30 <Radu_> Those are my diagrams, they are still a little rough around the edges
17:13:44 <Radu_> working on incorperating some feedback to paint a better picture
17:14:25 <pballand> one of the the things we’ve been trying move towards is gettings specs for all of the work that people are targetting
17:14:51 <pballand> unfortunately we’ve been stalled on a spec repo, but sarob was working on that - any updates sarob?
17:15:43 <sarob> pballand: infra spec patch merged
17:16:20 <sarob> the initial spec patch zuul isnt picking up
17:16:39 <sarob> im going to add another patch to verify the infra patch worked
17:17:16 <pballand> cool - fingers crossed that it goes through soon
17:17:32 <pballand> in the mean time, I think we should continue to post blueprints following the wiki
17:18:06 <sarob> working on the patch now
17:18:16 <pballand> kudva: any updates on the builtins patch?
17:19:42 <pballand> kudva appears to be away...
17:19:47 <kudva> pballand: I have checked in the builtin-runtime patch. Tim gave me a few bugs to test the query-optimization and syntax-checking errors. I plan to test them
17:20:04 <kudva> pballand: been a bit swamped the last week, should have an update next week.
17:20:37 <thinrichs> kudva: before we enable builtins I think we need to fix those bugs.
17:20:53 <thinrichs> Otherwise if people can write reasonable-looking rules, and the policy engine will break on them.
17:20:53 <pballand> kudva: is this the patch? https://review.openstack.org/#/c/109099/
17:21:04 <kudva> thinrichs: yes agreed. Plan to do it this week
17:21:08 <kudva> pballand: yes
17:21:22 <thinrichs> kudva: good to know.
17:21:50 <thinrichs> kudva: I'm excited to get those builtins in place.  I *know* people will be asking for them 10 min after they get the hang of writing policy.
17:22:28 <kudva> thinrichs: yes, I think we are very close. My goal is to get the tests done by Friday this week.
17:23:01 <pballand> rajdeep: anything new on your end?
17:23:19 <rajdeep> hi , i was trying to setup a new environment with congress
17:23:35 <rajdeep> looks like we have lot of undocumented dependencies
17:23:54 <rajdeep> i will update the docs
17:24:03 <rajdeep> got the tests working
17:24:31 <pballand> ok - I know arosen was working on cleaning up some of that...
17:24:51 <pballand> arosen: can you give an update on what you are working on, and coordinate with rajdeep ?
17:25:11 <rajdeep> e.g libxml2-dev, libxslt1-dev, lib32z1-dev
17:25:20 <thinrichs> BTW, there's a new set of instructions if you're installing with devstack.
17:25:24 <thinrichs> rajdeep: you might try those.
17:25:25 <thinrichs> https://github.com/stackforge/congress/blob/master/contrib/devstack/README.rst
17:25:49 <arosen> Sure, i'm about to push a quick patch that removes datasources/settings.py so the datasources can be configured via the config file.
17:26:20 <rajdeep> sure thinrichs will try that as well
17:26:27 <arosen> I'm also planning on improving the devstack integration so it's a little easier to undertsand
17:26:35 <arosen> that's pretty much it from me this week
17:27:15 <pballand> thanks - we’ve been trying to get the install instructions seamless
17:27:40 <pballand> we are targeting install directions using devstack, and standalone
17:28:13 <pballand> so far the devstack install seems to be working pretty well, with some minor tweaks that arosen is working on
17:28:28 <pballand> if everyone can beat on these and file bugs, that would be really helpful
17:29:56 <pballand> alexsyip: welcome to the project - would you mind introducing yourself and what you are working on?
17:30:30 <alexsyip> Hi, I’m coming to Congress from vmware NVP/NSX where I worked on the nlog programming language compiler and runtime.
17:31:04 <alexsyip> Currently, I am working on a demo policy for congress, in particular the “Public/private networks with group membership” example policy.
17:31:40 <alexsyip> I have the demo working, and I am working on documenting so that other people can try it out.
17:31:59 <pballand> very cool, thanks alexsyip
17:32:17 <pballand> gokul: are you around?
17:32:28 <gokul> hello!  yes -- sorry, joined late.
17:32:31 <pballand> (or anyone else with an update on the optimization+enforcement efforts)
17:32:43 <pballand> no worries - thanks for joining :)
17:33:26 <gokul> let me start with a question:  Tim mentioned that you would have a server etc. running...   was wondering about it.
17:33:57 <thinrichs> gokul: I assume you're talking about a prototype that runs end-to-end for monitoring policy.
17:34:24 <gokul> I think he referred to a congress policy server with one policy and the whole loop of enforcement (if I understood it right the last time)
17:34:38 <thinrichs> It's getting close.  If you check the logs of this meeting you'll see arosen/rajdeep talking about getting a devstack installation ready.
17:35:02 <thinrichs> gokul: we've pulled enforcement out as a feature of this release (we're targeting an alpha release soon).
17:35:15 <thinrichs> But the remnants of basic enforcement code is still in the repo.
17:35:24 <thinrichs> I'm happy to schedule a time to give you an overview of what we have.
17:35:32 <thinrichs> Probably on the phone is best.
17:35:39 <thinrichs> Anyone else is welcome to join, of course.
17:35:52 <gokul> thinrichs:  ok. thanks.    I think if I can get an overview, that would be awesome.  it will help me bootstrap and contribute faster ;)
17:36:17 <thinrichs> gokul: sounds good.  Drop me an email to set up a time.  Same goes for everyone else.  thinrichs@vmware.com
17:37:32 <thinrichs> gokul: Enforcement is super-important, so starting the design process is crucial.
17:37:40 <thinrichs> I'm looking forward to it!
17:37:43 <pballand> did I miss anyone?
17:37:51 <harrisonkelly> I made some progress
17:38:03 <gokul> thinrichs:  agreed.  thanks!  i'll contact you.
17:38:42 <pballand> harrisonkelly: great - can you give us some details?
17:40:09 <kudva> thinrichs: please include me on that phone call for overview
17:40:27 <thinrichs> kudva: ok.
17:40:30 <sarob> i can jump here
17:40:34 <pballand> not sure if harrisonkelly is still around
17:40:38 <pballand> sarob: that would be great
17:40:40 <harrisonkelly> I started changing the DSE to use eventlets instead of threads. I used the vCenter integration that I previously did as a test to see if it ran with the new changes.  It sort of ran, but now how I expected it to.  Only 3/8 of the modules did what they were suposed to.  The last ‘step’ that was done was to publish data to another module, so I began by looking into the subscribing/publishing
17:40:41 <harrisonkelly> functions in deepsix.py.  The DSE recognizes that there was a subscription to the module, but when the module published the data, it didn’t have any subscribers.  I think I messed something up in the dse internals and have to look at it more
17:41:24 <pballand> harrisonkelly: are you able to run the existing unit tests before and after your changes?
17:42:05 <harrisonkelly> I didn’t attempt to run those, are those the ones that are in the .sh file?
17:42:18 <pballand> run_tests.sh
17:42:33 <pballand> (see the read me)
17:42:49 <harrisonkelly> I couldn’t get that one to run when I tried to setup Congress last week
17:43:00 <pballand> let’s talk about that offline (#congress IRC or mail list) - we need to get to the policy summit
17:43:11 <harrisonkelly> alright no problem
17:43:15 <pballand> sarob: you’re up
17:43:26 <sarob> #link https://etherpad.openstack.org/p/juno-midcycle-policy-summit
17:43:44 <sarob> this is the working etherpad for the 18-19 sep policy summit
17:44:09 <sarob> we will need to get people commenting on the schedule
17:44:16 <sarob> slash agenda
17:44:36 <sarob> i wil be creating an eventbrite page soon
17:44:49 <sarob> with space for 30 people
17:45:03 <sarob> who online is planning on joining us?
17:45:13 <sarob> mestery, mikal?
17:45:45 <pballand> cloudtoad: ?
17:46:06 <sarob> thinking thing
17:46:08 <sarob> ing
17:46:20 <sarob> well no reason to hold up the meeting
17:46:36 <cloudtoad> I am planning on going, but it's not cleared yet for me...  I may have to go to Boston that week.
17:47:02 <sarob> ill reach out for some of the others offline
17:47:12 <pballand> ok, thanks sarob :)  We’re hoping to get a good crowd, so please spread the word
17:47:18 <sarob> spreadign
17:48:45 <pballand> we have been working hard to get a release (alpha) out - thinrichs has a short list of items left
17:49:03 <pballand> thinrichs: can you give us an update, and anyone else chime in with other critical items
17:49:34 <thinrichs> Sure.  It looks like there are a few pretty simple bugs along with a few features we need to expose to the API.
17:50:05 <thinrichs> It looks reasonable to do a code freeze on Friday and then spend next week testing/fixing bugs.
17:50:27 <thinrichs> I'm hoping to get the alpha officially tagged and released by next Friday.
17:50:42 <rajdeep> do we have the client library working?
17:51:01 <thinrichs> I'm doubtful we'll get that into the alpha, unfortunately.
17:51:11 <pballand> arosen was working on the client library - but I don’t think it will be ready this week
17:51:26 <thinrichs> Without it the main interface will be curl/wget
17:51:41 <arosen> I've made some good progess there. I think i basically have the whole api exposed at this point though I haven't added code coverage yet.
17:51:50 <arosen> I have a patch online for review if you want to try it out.
17:52:33 <thinrichs> Well maybe it's more likely to make it in than I thought.
17:53:28 <rajdeep> would love to try it
17:53:35 <Radu_> I've been using some simple python to play with the API a bit. I pasted one test script I was using on the openstack paste section a while back
17:54:07 <rajdeep> it has a usability aspect which is important
17:54:26 <pballand> thanks thinrichs - does anyone else have items they think are critical to get in before we publicly announce a “release”?
17:56:03 <pballand> ok, three minutes left - any other topics to discuss?
17:56:10 <sarob> nope
17:56:13 <sarob> for me
17:57:04 <pballand> ok, that’s it for this week
17:57:10 <pballand> thanks everyone for joining
17:57:15 <pballand> see you in #congress
17:57:24 <pballand> #endmeeting