17:02:07 <pballand> #startmeeting CongressTeamMeeting
17:02:08 <openstack> Meeting started Tue Aug 26 17:02:07 2014 UTC and is due to finish in 60 minutes.  The chair is pballand. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:02:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:02:11 <openstack> The meeting name has been set to 'congressteammeeting'
17:02:15 <pballand> hello everyone
17:02:19 <harrisonkelly> hey
17:02:55 <pballand> harrisonkelly: good morning/afternoon
17:03:17 <pballand> I expect a small crowd this week due to confrerences
17:03:28 <pballand> anyone else around?
17:03:51 <sarob> sarob
17:03:54 <sarob> is
17:03:55 <sarob> here
17:03:56 <pballand> hey sarob
17:04:25 <pballand> lets just give a quick status update for those reading the logs, and get back up to speed next week
17:04:38 <pballand> harrisonkelly: you’ve been hard at work - how’s DSE going?
17:05:28 <pballand> harrisonkelly: seems to have fallen asleep
17:05:38 <harrisonkelly> good, I think i finished getting the DSE to use eventlets
17:06:10 <harrisonkelly> If there is anything left to do on the DSE, I can start working on something else
17:06:13 <pballand> cool - once thinrichs takes a look, we should be able to merge it
17:06:26 <pballand> harrisonkelly: there is plenty of stuff needed - it would be great if you have the cycles
17:06:48 <pballand> the first item that comes to mind is to add functionality to the cage to query the status of each datsource
17:06:59 <harrisonkelly> I have some time this week, but I’m going to have less starting next week because of school
17:07:23 <harrisonkelly> what do you mean by status? Like ‘running’ or ‘stopped’?
17:08:15 <pballand> basically, each datasource should have basic health like {running, error}, and other fields like ‘last_update_time’
17:08:30 <pballand> those are just (bad) examples
17:08:47 <harrisonkelly> So basically any information that I can collect from the services?
17:08:56 <pballand> ultimately, the requirement is for the policy engine to be able to understand when a datasource is having trouble
17:09:22 <pballand> for example, the neutron plugin may be up and running, but may have connection issues with the Neutron API endpoint
17:09:59 <pballand> the info will also be exposed on the /v1/data-sources/<ds-id>/status API path
17:10:23 <harrisonkelly> ok, I can take a look into that
17:11:11 <pballand> harrisonkelly: that would be great - unfortunately we don’t have a spec for the work yet, so that would be a good place to start so we can refine the design
17:11:26 <harrisonkelly> ok, I’ll start that today
17:11:51 <pballand> great!
17:12:00 <pballand> sarob: did you want to update us on specs
17:12:15 <sarob> righto
17:12:36 <sarob> the basics are merged
17:13:04 <sarob> i am going to backport a few blueprints to specs
17:13:11 <sarob> that are missing specs
17:13:39 <sarob> i will be proposing a way to track
17:13:47 <sarob> specs between releases
17:13:52 <sarob> thats it
17:14:10 <pballand> sarob: that’s great - can you please update the wiki with the new link to specs: https://wiki.openstack.org/wiki/Congress#How_To_Create_a_Blueprint
17:14:15 <sarob> will do
17:14:21 <pballand> perfect
17:14:30 <sarob> thanks for noticing
17:14:49 <pballand> looks like a couple other people joined - for those coming in, we’re on a skeleton crew due to concurrent conferences this week
17:15:04 <pballand> anyone else have updates they want to discuss this week?
17:16:18 <pballand> From a project status standpoint we tagged an alpha release last week, and are pushing for people to try out the code
17:16:57 <pballand> the POC use case is working from a demo perspective, and we will be shifting to filing out the rough edges
17:17:04 * sarob wiki updated with new spec repo location
17:17:11 <pballand> sarob: thanks
17:17:55 <pballand> the other item coming up is the policy summit - sarob has been leading that - can you give us an update?
17:18:08 <sarob> the policy summit etherpad #link https://etherpad.openstack.org/p/juno-midcycle-policy-summit
17:18:20 <sarob> needs some attention
17:18:41 <sarob> we have 38 people signed up for the event
17:19:03 <sarob> i have mikal on the hook for both finding us a nova policy standin
17:19:20 <sarob> and updating the nova policy session on the etherpad
17:19:43 <sarob> i have some notes from mikal that i will be
17:19:51 <sarob> putting into the etherpad agenda as well
17:19:56 <sarob> thats it
17:20:10 <pballand> cool, thanks sarob
17:20:20 <sarob> ;)
17:20:52 <pballand> if there are topics that are near and dear to you to discuss at the summit, be sure to add them to the etherpad
17:21:23 <pballand> that’s all I had for this week
17:21:30 <pballand> #topic Open Discussion
17:21:46 <kudva> Hi, I have a problem with install
17:22:20 <kudva> trying to check in some code which I need to test. standalone install fails. Any guesses on what it may be?
17:22:40 <pballand> hi kudva what are you running for install?
17:22:40 <kudva> https://bugs.launchpad.net/congress/+bug/1360629
17:23:09 <kudva> pballand: cloned from git and followed the "standalone" instructions (not devstack) in the README
17:23:28 <pballand> what OS / version ?
17:23:46 <kudva> Ubuntu Precise I think
17:23:52 <kudva> Recommend a different one?
17:23:57 <rajdeep> what is your tox version?
17:24:16 <kudva> rajdeep: let me check
17:24:38 <rajdeep> please make sure it is tox 1.5
17:24:56 <kudva> rajdeep: will do. Will reinstall and try again. Thanks!
17:24:58 <pballand> a lot of the OpenStack packages have specific package version dependencies that conflict with what Ubuntu has in APT
17:25:27 <pballand> in general, try to uninstall any python dependencies installed from apt, and install from pip instead
17:26:02 <rajdeep> even pip version can give heart burns
17:26:10 <kudva> pballand: ah, got it, will try that :)
17:26:11 <rajdeep> make sure you install latest pip
17:26:29 <kudva> rajdeep: I have pip. It's possible I have a mix of pip and apt installs. need to clean up
17:26:43 <rajdeep> python get-pip.py
17:26:55 <rajdeep> please don't use apt-get to install pip
17:27:17 <rajdeep> it installs older version..hence your issues
17:27:17 <kudva> rajdeep: okay, I'll clean up all the packages and start over
17:27:22 <kudva> rajdeep; thanks
17:27:34 <rajdeep> kudva : my pleasure
17:27:45 <rajdeep> python reminds me of dll
17:27:46 <rajdeep> :)
17:28:21 <pballand> kudva: thanks for the report - if there is anything we can do to make the instructions more clear, please let us know (or submit a patch) :)
17:28:47 <kudva> pballand: I'll redo everything and summarize for the benefit of others who may try standalone
17:29:19 <pballand> kudva: thanks so much!
17:29:29 <rajdeep> perhaps check pip / tox versions
17:29:37 <rajdeep> in a script
17:30:06 <kudva> rajdeep: okay
17:31:30 <pballand> kudva: have you been able to use run_tests.py instead of tox?
17:32:48 <kudva> pballand: didnt' try this time. Just followed instructions in README
17:34:08 <pballand> kudva: ah - I didn’t realize we suggested tox instead of run_tests
17:34:19 <pballand> not sure why that is
17:34:36 <kudva> pballand: okay, in that case, let me do a clean install and try both run_tests and tox
17:34:45 <pballand> that would be really helpful
17:36:37 <pballand> any other concerns or comments for this forum?
17:37:43 <pballand> ok, thanks for coming this week
17:38:05 <pballand> #endmeeting