21:02:36 <ttx> #startmeeting project
21:02:37 <openstack> Meeting started Tue Jul 30 21:02:36 2013 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:02:38 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:02:40 <openstack> The meeting name has been set to 'project'
21:02:43 <ttx> #link http://wiki.openstack.org/Meetings/ProjectMeeting
21:02:55 <ttx> Back in business after last week pause, we'll have a look at havana-3 plans and how reasonable they are (or not)
21:03:04 <ttx> #info feature freeze is on *September 4*
21:03:15 <ttx> Note that some projects implement a feature proposal freeze a few weeks before
21:03:28 <ttx> #topic General stuff
21:03:41 <ttx> I don't have anything specific
21:03:54 <ttx> Oh. Yes I have
21:04:21 <apevec> ttx, I'd like to repeat that we have planned stable/grizzly freeze on Aug 1st
21:04:21 <ttx> If you have generic contraints you'd like applied to desig nsummit topics, like "no QA session at the same time as Infra sessions" please send them my way ASAp
21:04:33 <apevec> and release 2013.1.3 on Aug 8th
21:04:47 <shardy> apevec: heat has several outstanding reviews FYI
21:04:57 <ttx> apevec: how is it doing so far ?
21:05:09 <ttx> going*
21:05:32 <apevec> adam_g has sent status yesterday, there were two exceptions discussed on the stable-maint
21:05:55 <apevec> shardy, so you want to have heat 2013.1.3 ?
21:06:14 <ttx> sdague, annegentle, mordred: news from QA/Docs/Infra programs ?
21:06:15 <shardy> apevec: yes please, but we can discuss that offline :)
21:06:27 <sdague> so the neutron job is in really bad shape
21:06:37 <mordred> ttx: we're having fun issues with requirements - but we're working on making them more solid
21:06:38 <ttx> sdague: we'll talk about Neutron testing in the Neutron section
21:06:47 <shardy> or after the mtg rather
21:06:53 <mordred> ttx: this is going to lead to more aggressive alignment on the requirements repo
21:06:56 <anneisgentle> We're holding Docs Boot Camp in Mountain View Sept 9 and 10, thanks to Mirantis for playing host.
21:06:59 <anneisgentle> #link wiki.openstack.org/wiki/Docs_Bootcamp_2013
21:07:04 <sdague> ok, requirements chasing is getting interesting... not there yet
21:07:07 <mordred> ttx: because doing otherwise is killing us
21:07:19 <markmc> mordred, any more details? the issues, the changes?
21:07:19 <gabrielhurley> +1
21:07:25 <ttx> mordred: aggressivity++
21:07:41 <mordred> markmc: the issues have to do with the fact that pip installs wind up with state based on the arbitrary sequence
21:07:46 <mordred> rather than the graphe of needs
21:07:50 <markmc> ok
21:07:54 <mordred> so the first thing that sdague and I are working on
21:08:02 <markmc> yeah, think I saw something go by
21:08:02 <markmc> fun
21:08:03 <shardy> anneisgentle: any way to participate remotely?
21:08:07 <mordred> is getting devstack to run the update.py script in setup_develop
21:08:28 <mordred> so that we have the same current behavior as devstack, but aligned to what's in requirements
21:08:40 <mordred> along with that we'll start gating changes to requirements on devstack
21:08:45 <anneisgentle> shardy: sorry, not at this point
21:08:57 <mordred> then, we'll start auto-creating and proposing changes to projects on changes to requirements repo
21:08:58 <shardy> anneisgentle: OK, thanks
21:09:02 <anneisgentle> shardy: we're always here for you :) Monday office hours.
21:09:08 <mordred> because, well, we will have already tested that they work
21:09:21 <ttx> ok, time to get into the specifics
21:09:37 <ttx> #topic Oslo status
21:09:42 <ttx> markmc: hi!
21:09:46 <ttx> #link https://launchpad.net/oslo/+milestone/havana-3
21:09:46 <markmc> howdy
21:10:01 <markmc> it's all looking pretty fine
21:10:03 <ttx> You have 8 tracked blueprints targeted to h3, which is pretty reasonable
21:10:04 <markmc> apart from messaging
21:10:10 <ttx> oh, 5 now
21:10:24 <markmc> basically, oslo.messaging is in gerrit etc.
21:10:37 <markmc> and now has working kombu and qpid drivers
21:10:46 <markmc> not thoroughly tested, but the basics work
21:11:03 <markmc> the big question is whether we can complete their testing and get e.g. nova switched over to using it
21:11:03 <ttx> Most of your stuff is already under review, which is good news
21:11:20 <markmc> we've set ourselves a deadline of August 16th for a go/no-go
21:11:26 <ttx> sounds a bit risky to do it, and a bit risky not to do it
21:11:34 <markmc> i.e. unless nova is using oslo.messaging at that point, we punt to icehouse
21:11:41 <ttx> markmc: +1
21:11:44 <markmc> not doing it shouldn't have an impact on havana
21:11:55 <ttx> I think it's good to wrap up oslo changes a few weeks before H3 anyway, so that we have time to push oslo-incubator syncs at the end of the milestone
21:11:57 <markmc> any messaging features we want for havana will go in through oslo-incubator anyway
21:12:15 <markmc> the other big messaging one is the message security patches
21:12:19 <markmc> which look in great shape
21:12:29 <markmc> and the keystone KDS patches look pretty well advance too
21:12:37 <markmc> so I'm fairly confident that will make it for havana
21:12:53 <markmc> a fair bit of work to make nova etc. use it, though
21:13:13 <ttx> ok
21:13:24 <ttx> markmc: anything else you wanted to raise ?
21:13:32 <markmc> it begs the question whether we should have e.g. nova blueprints for "use oslo.messaging" and "use oslo message security"
21:13:43 <markmc> not just nova, all rpc-using projects
21:13:53 <ttx> markmc: does that sound fair to say that oslo should be finished with its features a few weeks before feature freeze ?
21:14:02 <markmc> ttx, yes
21:14:24 <ttx> markmc: sounds like you want blueprints that affect multiple projects!
21:14:39 <markmc> a blueprint with tasks for multiple projects
21:14:50 <markmc> i.e. like launchpad bugs
21:14:53 <ttx> markmc: your wishes may soon be granted.
21:14:57 <markmc> heh
21:15:01 <markmc> in the meantime?
21:15:14 <ttx> in the meantime, tracking as a separate blueprint makes sense to me
21:15:14 <markmc> would filing blueprints help track stuff?
21:15:16 <markmc> ok
21:15:22 <ttx> Questions about Oslo ?
21:15:37 <markmc> thanks ttx
21:15:43 <ttx> #topic Keystone status
21:15:49 <ttx> henrynash: around ?
21:16:43 <ttx> looks like henrynash is not around, jd__ you up ?
21:16:57 <jd__> hum?
21:16:59 <jd__> yep!
21:17:02 <ttx> #undo
21:17:03 <openstack> Removing item from minutes: <ircmeeting.items.Topic object at 0x20a3f50>
21:17:04 <ttx> #topic Ceilometer status
21:17:07 <ttx> jd__: hey
21:17:09 <ttx> #link https://launchpad.net/ceilometer/+milestone/havana-3
21:17:40 <ttx> You have 13 tracked blueprints, which is slightly optimistic compared to your usual velocity
21:17:44 <ttx> It's also highly dependent on Eoghan and yourself, representing 9 of those 13
21:17:54 <ttx> How are you both going to make it ?
21:18:16 <jd__> we believe!
21:18:26 <jd__> though one of my blueprint "Alarming" isn't a real one
21:18:36 <jd__> it's just one final to track a bunch of others
21:18:54 <jd__> I don't know if we can change it status so it's clearer for you to track
21:18:55 <ttx> ok, we'll track that closely
21:19:22 <ttx> use-new-rpc-messsage is marked Blocked. Could you explain what it is blocking on ?
21:19:43 <jd__> ttx: yes, check its dependency graph actually
21:19:54 <jd__> we're waiting for https://blueprints.launchpad.net/oslo/+spec/trusted-messaging
21:20:07 <ttx> ok
21:20:10 <ttx> stacktach-integration depends on logging-uses-notifications and remove-instance-fault-table, but those have been targeted to "next"
21:20:27 <jd__> these are Nova bp I think
21:20:56 <ttx> jd__: still sounds difficult to complete your ceilometer bp in h3 if nova's deferred on their side :)
21:21:01 <jd__> all I can do is remove stacktach-integration, not sure sandywalsh will be happy
21:21:05 <jd__> yep
21:21:08 <ttx> russellb: ^could you look into that with sandywalsh and jd__  ?
21:21:15 <jd__> maybe these aren't reall dep, I'll check with sandywalsh
21:21:18 <jd__> -l
21:21:25 <ttx> jd__: anything you wanted to mention ?
21:21:31 <jd__> all good
21:21:47 <ttx> Questions on Ceilometer ?
21:21:58 <ttx> (We'll skip Swift since notmyname is not around)
21:22:13 <ttx> #topic Glance status
21:22:15 <markwash> not fair
21:22:21 <ttx> markwash: busted
21:22:23 <markwash> was almost done :-)
21:22:35 <ttx> 7 tracked blueprints so far, that sounds pretty reasonable
21:22:49 <ttx> glance-tests-code-duplication still needs triaging :P
21:22:54 <markwash> indeed it does
21:22:59 <markwash> and there is one more that needs to be added to the list
21:22:59 <ttx> About api-v2-property-protection, we've been carrying it over for the last 12 months now...
21:23:09 <ttx> Is there any reason to think that it will hit in the next weeks ?
21:23:12 <markwash> ttx but now people are working on it! :-)
21:23:25 <markwash> there has been some activity on the list as well
21:23:26 <ttx> markwash: I heard that one before I think :)
21:23:34 <markwash> haha
21:23:42 <ttx> markwash: so this time it's for real ?
21:23:51 <markwash> this time, its personal
21:24:07 <ttx> ok, I'll track that one closely :)
21:24:10 <markwash> I'm not sure if it will make it, but there is active development and folks I trust
21:24:15 <ttx> markwash: we pushed an advisory (OSSA-2013-018) for Glance python client today
21:24:20 <ttx> markwash: how about we tag a new client release to get that out to the crowds ?
21:24:34 <markwash> sounds good, will do
21:24:38 <ttx> awesome
21:24:48 <ttx> markwash: anything you wanted to mention ?
21:24:59 <markwash> nothing from me, one question though
21:25:03 <markwash> what is "Beta Available" ?
21:25:23 <ttx> https://wiki.openstack.org/wiki/Blueprints#Implementation
21:25:32 <ttx> "Implementation is almost complete, code is available in a branch or a draft review now"
21:25:39 <markwash> okay
21:25:43 <markwash> ty
21:25:46 <ttx> Questions on Glance ?
21:26:05 <ttx> Do we have markmcclain in the house ?
21:26:22 <markmcclain> hi
21:26:25 <ttx> #topic Neutron status
21:26:30 <ttx> markmcclain: hi!
21:26:32 <ttx> #link https://launchpad.net/neutron/+milestone/havana-3
21:26:45 * ttx refreshes ttx.py output, takes time
21:27:00 <ttx> 42 targeted blueprints... about twice as many as the total implemented in havana-2
21:27:08 <ttx> This sounds a very unlikely goal, and could lead to issues prioritizing reviews and get the important stuff in
21:27:16 <ttx> That said, 22 of those 42 are implemented or under code review already...
21:27:29 <ttx> So I guess if you pulled an enormous code review effort early on, and pushed back a few of those 43 to "Low" priority... the picture could look a bit more doable
21:28:06 <ttx> There are a few without an assignee in there, which in my book could have been plain refused: auto-associate-floating-ip, ml2-multi-segment-api
21:28:15 <ttx> (you should require an assignee to be set before triaging a blueprint)
21:28:45 <ttx> markmcclain: openvswitch-kernel-vxlan is marked "Deferred"... should it be set to "next" milestone instead ?
21:29:14 <markmcclain> I need to doable check with the subteam working on vxlan
21:29:19 <markmcclain> might remove it all together
21:29:28 <ttx> You also have 12 "undefined" blueprints in there that need a priority. Ideally none of them would get higher than "Low" and add to the improbability above :)
21:29:46 <markmcclain> I'll fix up the 2 unassigned that I missed
21:29:56 <ttx> nachi, markmcclain, sdague: I wanted to talk about the Neutron gating tests
21:30:05 <ttx> We made the neutron gate non-voting due to bug 1194026
21:30:06 <uvirtbot> Launchpad bug 1194026 in neutron "check_public_network_connectivity fails with timeout" [Critical,In progress] https://launchpad.net/bugs/1194026
21:30:13 <ttx> I'd like to have those tests re-enabled ASAP so that they don't bitrot to the point where we can't use them anymore
21:30:18 <ttx> What's the status of that ? Are we now hitting bug 1206307 instead ?
21:30:19 <uvirtbot> Launchpad bug 1206307 in neutron "neutron-adv-test.sh:773 [Fail] Couldn't ping server in Gating" [Critical,Confirmed] https://launchpad.net/bugs/1206307
21:31:25 <ttx> sdague had to drop off -- markmcclain do you have news on that side ?
21:31:43 <markmcclain> yeah.. I was chatting with nati_ueno yesterday about it and still have problems reproducing outside of the gate
21:31:55 <markmcclain> I know that nati_ueno is actively working on the issue
21:32:01 <ttx> both bugs are still active ? Or the first one was solved ?
21:32:18 <markmcclain> the patch we pushed for the first one didn't fully solve the problem
21:32:25 <markmcclain> so the bug was reopened
21:32:31 <ttx> ok, so both bugs are active at this point
21:32:36 <markmcclain> in the investigation he found the 2nd one
21:34:02 <ttx> nachi: feel free to send me an update on your progress... and if you need any help
21:34:09 <ttx> markmcclain: anything you wanted to raise ?
21:34:19 <markmcclain> no
21:34:25 <ttx> Questions on Neutron ?
21:34:52 <ttx> #topic Cinder status
21:34:55 <ttx> jgriffith: hola!
21:35:12 <ttx> #link https://launchpad.net/cinder/+milestone/havana-3
21:35:42 <ttx> jgriffith: yt ?
21:36:33 <ttx> russellb: you there ?
21:36:35 <hub_cap> hes riding a horse
21:36:35 <russellb> yep
21:36:42 <ttx> #undo
21:36:43 <openstack> Removing item from minutes: <ircmeeting.items.Link object at 0x23b9110>
21:36:46 <ttx> #topic Nova status
21:36:49 <ttx> russellb: hey
21:36:51 <russellb> hi
21:36:51 <jgriffith> grrrr
21:36:53 <ttx> #link https://launchpad.net/nova/+milestone/havana-3
21:36:55 <russellb> #link http://lists.openstack.org/pipermail/openstack-dev/2013-July/012323.html
21:37:07 * jgriffith snoozes he looses his turn
21:37:15 <russellb> so .... yeah.
21:37:28 <russellb> i've deferred 10-15 blueprints or so
21:37:32 <ttx> russellb: so looking at tracked (>Low) blueprints, you are at 51
21:37:41 <ttx> compared to 25 delivered during h2
21:37:47 <ttx> I suspect you'll need to push more to "Low" (a.k.a. "may land, who knows") priority
21:37:59 <russellb> ttx: that's a good idea
21:38:03 <ttx> easier than deferring
21:38:10 <ttx> esp. when you don't know what might make it
21:38:14 <russellb> i'm also expecting a whole bunch to miss the proposal deadline
21:38:21 <ttx> When is your "proposed feature freeze" ?
21:38:25 <russellb> aug 21
21:39:02 <russellb> i will work on dropping priority of some
21:39:06 <russellb> hadn't thought of that
21:39:18 <ttx> it's an easy trick
21:39:29 <russellb> but otherwise i feel like the best i can do is try to encourage review priorities, and wait to see what code actually shows up
21:39:34 <ttx> basically helps prioritizing reviews on one side... and lower expectations on the other
21:39:45 <russellb> true
21:39:48 <ttx> image-multiple-location depends on effective-template-base-image-preparing which was not targeted to any milestone
21:40:15 <ttx> new-hypervisor-docker is marked Blocked... what is it blocking on ?
21:40:23 <russellb> oh, sorry for not updating whiteboard
21:40:27 <russellb> he's adding devstack support
21:40:43 <russellb> i wanted to have a clear path to being able to test it
21:40:53 <ttx> ok, that is sort of implied in the current explanation, but wanted to be sure
21:41:04 <ttx> wouldn't it be nice if we had tasks on blueprints ?
21:41:04 <russellb> ok, yes, that's all it is
21:41:15 <russellb> there's Work Items i guess ...
21:41:29 <ttx> but not for multiple projects.
21:41:34 <russellb> yeah.
21:41:39 <ttx> russellb: anything else you wanted to mention ?
21:41:46 <ttx> Oh, you may have missed the ping earlier
21:42:00 <russellb> not really, just thinking about what we can do better to avoid this kind of situation in the future
21:42:08 <russellb> i guess it's being more aggressive with using Low
21:42:09 <russellb> :-)
21:42:09 <ttx> <ttx> russellb: ^could you look into that with sandywalsh and jd__
21:42:18 <russellb> i did miss that, my connection dropped for a bit
21:42:26 <russellb> so i don't know what that's referring to
21:42:27 <ttx> <ttx> stacktach-integration depends on logging-uses-notifications and remove-instance-fault-table, but those have been targeted to "next"
21:42:38 <ttx> stacktach-integration is a ceilo bp
21:42:45 <ttx> the other two are nova's
21:42:50 <russellb> oh
21:42:55 <russellb> yeah, they hadn't started AFAIK
21:42:57 <russellb> so i pushed them off
21:42:59 <ttx> which made my inconsistency detector go bleep
21:43:15 <ttx> the answer might be to defer the ceilo one as well
21:43:24 <russellb> so either someone needs to yell at me to say "wait, i'm doing it!" or defer the ceilo one, yeah
21:43:29 <ttx> could you look into it with sandywalsh and jd__  ?
21:43:36 <russellb> my deferring triggered some yelling :-)
21:43:37 <russellb> yes.
21:43:41 <ttx> Any question on Nova ?
21:43:56 <ttx> #topic Cinder status
21:43:58 <jgriffith> :)
21:44:03 <ttx> jgriffith:hi!!
21:44:03 <jgriffith> hosre is back in teh barn
21:44:06 <jgriffith> hola
21:44:12 <ttx> #link https://launchpad.net/cinder/+milestone/havana-3
21:44:19 <ttx> 17 tracked blueprints, which is more than you delivered in h2
21:44:33 <ttx> You might want to push some of these "Medium" to "High" or "Low" to help prioritizing the review effort, same suggestion than for russellb
21:44:34 <jgriffith> Yeah, but this time we're going to hit them
21:44:48 <jgriffith> I'll comb through next week
21:44:54 <ttx> bare-metal-volumes and cinder-nfs-driver-qos need an assignee
21:44:56 <jgriffith> most are in progress pushes from H2
21:44:59 <ttx> (you should require an assignee to be set before giving a blueprint a priority)
21:45:08 <jgriffith> those will likely be dropped due to lack of interest
21:45:14 <ttx> cinder-volume-driver-optional-iscsi-support needs to be triaged too
21:45:23 <jgriffith> but I need to give folks a chance to speak up tomorrow
21:45:32 <ttx> sounds good
21:45:33 <ttx> finally, db-cleanup (Medium) depends on db-archiving (Low) ?
21:45:47 <jgriffith> quite frankly that whole thing is a bit of a mess
21:45:52 <ttx> maybe adjust prio or remove link if it doesn't make sense
21:46:06 <ttx> db-cleanup might be an "ongoing" task
21:46:11 <jgriffith> I'll adjust, but I'm also not convinced any longer on the whole thing
21:46:15 <ttx> unless it has clear objectives :)
21:46:23 <jgriffith> good point
21:46:37 <ttx> jgriffith: we have one Nova blueprint blocked on https://review.openstack.org/#/c/30974/ so please give that one some review priority
21:46:57 <jgriffith> I have reviewed
21:47:04 <ttx> jgriffith: anything on your mind ? apart from horses breaking out of the barn ?
21:47:14 <jgriffith> haha
21:47:25 <jgriffith> I'm concerened about encryption and db stuff
21:47:36 <jgriffith> also the quota stuff
21:47:46 <jgriffith> that merged into oslo before merging in Cinder or noava
21:47:48 <jgriffith> nova
21:47:53 <jgriffith> which seems backwards
21:47:56 <jgriffith> other than that
21:48:02 <jgriffith> nothing really
21:48:29 <ttx> once the code is separated, it doesn't sound backward to implement improvements in oslo and sync them back
21:48:41 <ttx> Questions on Cinder ?
21:48:49 <jgriffith> sure, if the code works
21:48:53 <jgriffith> anyway...
21:48:54 <ttx> jgriffith: indeed
21:48:57 <ttx> #topic Heat status
21:49:02 <ttx> shardy: o/
21:49:03 <shardy> o/
21:49:04 <ttx> #link https://launchpad.net/heat/+milestone/havana-3
21:49:19 <shardy> I know I need to start bumping (a lot) of stuff
21:49:22 * ttx refreshes
21:49:33 <ttx> 31 tracked blueprints, while you implemented 8 during h1 and 8 during h2
21:49:38 <ttx> That no longer qualifies as optimism, it's pure madness :)
21:49:42 <shardy> Not been ready to burst new-contributors bubbles just yet, but yeah
21:49:44 <hub_cap> heh
21:49:57 <ttx> You definitely need to more liberally use the "Low" priority to designate stuff that "may" make it
21:50:00 <shardy> to be fair, a lot of stuff has been carried over, specifically the HOT functionality
21:50:11 <ttx> That will help in communicating which features are the most likely to land to the rest of the world
21:50:13 <shardy> which is all starting to come together, combined with the watch-ceilometer stuff
21:50:18 <ttx> Because it's a quite unlikely those 30 will make it, and I prefer to be pleasantly surpised than doing bulk deferrals on feature freeze day
21:50:47 <shardy> ttx: agree, I'll start getting it into shape after discussions at our meeting tomorrow
21:50:50 <ttx> You also have a few waiting to have a priority set:
21:50:52 <ttx> software-configuration-provider, update-stack-new-resource-state, heat-multicloud, oslo-db-support
21:51:17 <shardy> ttx: that is deliberate - those appeared while I was on holiday and I need to discuss whether they just get bumped immediately
21:51:42 <ttx> If you push things to "Low" they will disappear from my radar and i'll stop complaining about crazy goals :)
21:51:50 <ttx> shardy: anything else you want to raise ?
21:51:53 * shardy sets everything to low
21:51:55 <shardy> ;)
21:52:05 <ttx> that would be cheating.
21:52:08 <shardy> no, not atm, will try to get things more realistic for next week :)
21:52:16 <ttx> great!
21:52:19 <ttx> Questions about Heat ?
21:52:25 <shardy> seem to have herded the cats into a corner atm ;)
21:52:39 <ttx> #topic Horizon status
21:52:44 <ttx> gabrielhurley: feeling better ?
21:53:05 <gabrielhurley> somewhat
21:53:09 <ttx> #link https://launchpad.net/horizon/+milestone/havana-3
21:53:13 <ttx> 16 tracked blueprints while you got 7 implemented in h2 (and 8 in h1)
21:53:21 <ttx> So that's pretty optimistic... though you have about half of them implemented or in review already
21:53:22 <gabrielhurley> yeah. I expect some will slip
21:53:29 <gabrielhurley> there's a lot with priority "low"
21:53:39 <ttx> So you might make it if you do a big review push early on
21:53:54 <gabrielhurley> certainly possible
21:54:02 <gabrielhurley> but probably optimistic
21:54:06 <gabrielhurley> I will refine as we go
21:54:08 <ttx> Has work started on https://blueprints.launchpad.net/horizon/+spec/rbac ?
21:54:26 <gabrielhurley> david-lyle has it in his head. he may have started code, but he's generally on it.
21:54:45 <ttx> ok
21:55:09 <ttx> gabrielhurley: some will slip, but ideally those who slip should be Low ones :)
21:55:19 <gabrielhurley> that's the goal
21:55:20 <gabrielhurley> :-)
21:55:26 <ttx> that's what the roadmap is about: setting expectations as good as we can
21:55:34 <ttx> gabrielhurley: anything you wanted to mention ?
21:55:45 <gabrielhurley> not off the top of my head
21:55:59 <ttx> Questions on Horizon ?
21:56:21 <ttx> Looks like we don't have henrynash, who was supposed to replace dolphm this week
21:56:35 <ttx> anyone else feeling like defending keystone ?
21:57:08 <ttx> ok, short update for the record
21:57:14 <ttx> #topic Keystone status
21:57:31 <ttx> 6 tracked blueprints in havana-3, which is reasonable
21:57:41 <ttx> endpoint-filtering needs an assignee (or be removed from havana-3)
21:58:03 <ttx> #topic Incubated projects
21:58:10 <ttx> hub_cap, devananda: news ?
21:58:14 * NobodyCam for devananda "we are still working on it. no real news yet"
21:58:20 <ttx> heh
21:58:32 <hub_cap> heyo
21:58:41 <ttx> hub_cap: how is it going ?
21:58:53 <hub_cap> no real news. ive got the rpm integration almost done as a POC
21:59:10 <hub_cap> a guy from mirantis and someone else both offered to finish it up
21:59:27 <hub_cap> so we shoudl be able to run on ubuntu or fedora images now
21:59:32 <hub_cap> well, once the reviews land ;)
21:59:37 <ttx> "Impl Cinder Volume extend for resize volume" is marked essential for your havana release, is it really essential ? As in "won't release without it" ?
21:59:38 <hub_cap> and heat integration is next
21:59:51 <hub_cap> well ttx, our cli tool and api already have it
22:00:01 <hub_cap> and we impl'd it internally at rax, FAIL
22:00:11 <ttx> ok. Assigning someone to that BP is probably a good idea then :)
22:00:20 <hub_cap> and haomaiwang said he wants to do it i believe
22:00:22 <ttx> ok, time is up, anything else you wanted to mention ?
22:00:24 <hub_cap> ill make sure its assigned this wk
22:00:33 * hub_cap hugs everyone
22:00:35 <hub_cap> that is all
22:00:37 <ttx> #endmeeting