16:30:10 <sdake> #startmeeting kolla
16:30:11 <openstack> Meeting started Wed Sep 16 16:30:10 2015 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:30:12 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:30:15 <openstack> The meeting name has been set to 'kolla'
16:30:19 <sdake> #topic rollcall
16:30:21 <akwasnie> hi:)
16:30:31 <rhallisey> hey
16:30:55 <sdake> o/ folks :)
16:31:03 <jmccarthy> o/
16:31:21 <jpeeler> hi
16:32:47 <sdake> #topic LIberty rc1 planning
16:33:00 <sdake> #link https://launchpad.net/kolla/+milestone/liberty-rc1
16:33:27 <sdake> if folks pull that up, you will see we have a whole slew of blueprints and bugs for rc1
16:33:47 <coolsvap> hello
16:33:59 <sdake> first lets go through status reports of the blueprints not in the good progress or higher state
16:34:30 <sdake> #link https://blueprints.launchpad.net/kolla/+spec/logging-container
16:34:57 <sdake> inc0 any update here?
16:35:20 <inc0> few things to do on this one - optional bindmounting and Sam asked to provide keystone before merging initial patch
16:35:30 <inc0> I should be done with these 2 this week
16:35:41 <inc0> (was off for a week, hence time slip)
16:35:56 <sdake> do you ahve to modify all the containers to add logging to them?
16:36:14 <inc0> no, just ansible configs for services
16:36:47 <inc0> ansible-generated configs
16:36:48 <sdake> ok i woudl like folks to keep in mind any blueprint not in good progress by the 18th (as defined by will finish by the 25th, our rc1 deadline) will be pushed to mitaka
16:37:20 <sdake> #link https://blueprints.launchpad.net/kolla/+spec/ansible-mongodb
16:37:33 <sdake> coolsvap is that + ceilometer going to land for liberty?
16:37:59 <sdake> #link https://blueprints.launchpad.net/kolla/+spec/ansible-ceilometer
16:38:23 <coolsvap> sdake, yes
16:38:31 <coolsvap> on it
16:38:38 <sdake> can you push a work in progress review so people can start commenting ?
16:39:00 <coolsvap> yes will do that tonight or early morning tomorrow
16:39:05 <sdake> cool
16:39:17 <sdake> #link https://blueprints.launchpad.net/kolla/+spec/kolla-live-migration
16:39:26 <sdake> rhallisey any update on this?
16:39:38 <sdake> it says started, is it started?
16:39:45 <rhallisey> just focusing on refactor
16:39:50 <rhallisey> ya I started it a while back
16:39:57 <sdake> should I push this off then to mitaka?
16:40:00 <rhallisey> ya push it
16:40:13 <sdake> SamYaple has about 6 blueprints but he isn't here
16:40:27 <sdake> SamYaple if you happen to read later, can you focus on getting ceph in working order :)
16:40:28 <sdake> TIA
16:40:44 <inc0> I'll ask him to review it tomorrow
16:40:53 <inc0> but knowing him he'll read through logs
16:41:17 <sdake> bug triage
16:41:27 <sdake> the bug tirage has been going well, however the bug fixing hasn't been going as well
16:41:50 <sdake> If folks could assign themselves 1 or 2 bugs from the confirmed bugs, with the idea of fixing in the next 2-3 weeks that would be fantastici :)
16:42:15 <sdake> we have 87 bugs targeted for this milestone
16:42:37 <sdake> the way i target bugs, is i ipull all bugs in and we work on the ones we can, and push what remains to the next release
16:42:48 <sdake> we can't follow that pattern for rc2/rc3
16:43:04 <sdake> we need to actively fix all the critical/high bugs for rc2/rc3
16:43:15 <sdake> any questions ?
16:43:20 <rhallisey> sounds good
16:43:39 <sdake> #topic properly scoping work
16:44:02 <sdake> for l1/l2/l3/rc1 we have had many more blueprints then peoples time available
16:44:13 <sdake> we were successful in delivering all of our blueprints for l1/l2/l3
16:44:14 <pbourke_> sorry Im late
16:44:34 <sdake> pbourke_ welcome :)
16:44:42 <sdake> we also fixed a mountain of bugs
16:44:44 <pbourke_> stuck in hell that is keystone logging
16:44:51 <pbourke_> and forgot
16:45:00 <sdake> but rc1 is likely going to see alot less blueprints implemented then were scheduled
16:45:11 <sdake> sprints are about 1 month in duration
16:45:31 <sdake> what I'd like to see during the Mitaka cycle is that people that commit to delivering a blueprint or two only commit to their capacity
16:45:52 <sdake> for an example of this, I have two blueprints:
16:46:06 <sdake> #link https://blueprints.launchpad.net/kolla/+spec/upgrade-strategy
16:46:17 <sdake> #link https://blueprints.launchpad.net/kolla/+spec/rhel-based-image-support
16:46:27 <sdake> only one will finish for rc1
16:46:47 <sdake> it is hard for me to be inside everyone's head around their own capacity
16:46:57 <sdake> which means its hard to plan the project :)
16:47:44 <sdake> don't be afraid to say a blueprint isn't going to make it early in the sprint
16:48:02 <coolsvap> agreed
16:48:04 <sdake> I'd like to not operate over capacity for our team as it triggers burnout
16:48:19 <sdake> it works for short periods but not long term
16:48:41 <sdake> Kolla is in fantastic shape heading into Mitaka and we have alot of interest in our project
16:48:58 <sdake> but if we become disinterested because of overcommitment, that isn't helpful
16:49:06 <sdake> marathon, not a race ;)
16:49:12 <sdake> any questions ? :)
16:49:23 <rhallisey> sounds good
16:49:32 <coolsvap> agreed
16:49:44 <sdake> #topic announcements
16:49:57 <sdake> i should have done this first but forgot
16:50:06 <sdake> 1. rdo repos are down for scheduled maintenance as indicated by jpeeler
16:50:31 <jpeeler> they sent a follow up about mirroring it while down, but apparently are having problems currently
16:50:55 <sdake> 2. all cores should vote on the proposal to permit or not permit integration with cinder, neutron, and paid distros
16:51:00 <sdake> if you dont vote, it is essentially like voting -1
16:51:08 <sdake> since we require a majority
16:51:27 <sdake> if you want to vote -1 do that, but dont not vote :)
16:51:41 <sdake> if folks dont vote, I don't know where the project cores stand
16:51:52 <sdake> said proposal is on the mailing list
16:52:34 <sdake> i need a conclusion to the vote this week because otherwise rhos wont make rc1
16:52:36 <coolsvap> #link http://lists.openstack.org/pipermail/openstack-dev/2015-September/074310.html
16:53:07 <sdake> some folks had talked about some various points they want enabled to accept stuff in
16:53:24 <sdake> lets focus on the big picture (do we want to do it or not) first
16:53:26 <sdake> and details second
16:53:49 <sdake> my position is that I want to  do what is in the best interest of the project, not be high-horsey about open source :)
16:54:10 <sdake> please read the thread
16:54:16 <sdake> any annnouncements from the commnity?
16:54:29 <pbourke_> nope
16:54:58 <sdake> #topic open discussion
16:55:03 <sdake> so pretty light agenda for this meeting
16:55:43 <coolsvap> I think we should also use the review for highlighting the core vote on the rhos
16:56:02 <sdake> coolsvap lets just get it on the mailing list
16:56:04 <coolsvap> for this particular review we should have all cores vote on the first review
16:56:05 <sdake> that is super public
16:56:18 <coolsvap> in addition to the mailing list
16:56:42 <sdake> SamYaple wanted it somewhere more public then the gerrit review
16:56:57 <sdake> he asked, I delivered :)
16:57:06 <coolsvap> alright
16:57:09 <inc0> don't we have session on "What do we support policy"?
16:57:13 <inc0> in tokyo?
16:57:22 <sdake> its a policy decision not a technical matter
16:57:36 <sdake> inc0 i dont think so, we dont support anything
16:57:57 <inc0> also, we did talk about this topic in midcycle a bit
16:57:59 <sdake> inc0 we implement, other people support
16:58:05 <inc0> contrib stuff
16:58:07 <jpeeler> support is quite an overloaded term
16:58:58 <sdake> sup·port
16:59:07 <sdake> give assistance to, especially financially; enable to function or act.
16:59:39 <inc0> someone want's to give us financial assistance?
16:59:43 <sdake> a support organization takes our implementaiton and enables their customers to act
16:59:47 <inc0> wants*
17:00:27 <sdake> we have not built a support community
17:00:39 <sdake> not even neutron with over 100 person development team "supports" neutron
17:01:01 <sdake> I hope everyone understands this point :)
17:01:21 <sdake> postgresql got killed because they became popular and tried to support their software in the community
17:01:39 <sdake> its an anti-pattern for dev teams and support teams to be one in the same IMNSHO
17:02:01 <sdake> I know it seems a bit quiet during this period of the dev cycle (between releases)
17:02:02 <inc0> let's not be popular then - no problem with support;)
17:02:04 <sdake> its always like that
17:02:22 <sdake> so for folks new to the quietness, don't stress - always happens with openstack projects
17:03:08 <sdake> we have over 50 blueprints in our backlog that need prioritization
17:03:17 <sdake> so we have plenty of work to do going forward :)
17:03:24 <sdake> any other open discussion then?
17:03:42 <sdake> cool thanks for coming :)
17:03:44 <sdake> #endmeeting