16:00:23 <xarses> #startmeeting fuel
16:00:23 <openstack> Meeting started Thu Jan 14 16:00:23 2016 UTC and is due to finish in 60 minutes.  The chair is xarses. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:23 <maximov> hi
16:00:23 <xarses> #chair xarses
16:00:23 <xarses> Todays Agenda:
16:00:23 <xarses> #link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
16:00:23 <xarses> Who's here?
16:00:24 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:25 <monester> hi
16:00:26 <openstack> The meeting name has been set to 'fuel'
16:00:27 <openstack> Current chairs: xarses
16:00:29 <angdraug> hi all
16:00:30 <rmoe_> hi
16:00:37 <ashtokolov> Hi
16:00:41 <igorbelikov> hi
16:00:44 <akislitsky_> hi
16:00:47 <xarses> welcome back, I hope every one had a good break
16:00:50 <romcheg> \o
16:01:01 <asvechnikov_> hi
16:01:04 <mattymo> xarses, we did. Thanks.
16:01:11 <rvyalov_> hi
16:01:11 <xarses> #topic Action Items from last meeting
16:01:23 <xarses> monester and bookwar will work on getting the add reviewers by MAINTAINERS data script
16:01:36 <monester> done, https://ci.fuel-infra.org/job/auto-add-reviewers/
16:01:43 <xarses> awesome!
16:01:49 <xarses> pyzhov will announce changes in swarm-blocker tag
16:02:57 <xarses> moving on
16:03:51 <xarses> #topic ConfigDB description and status (ogelbukh, ytaraday)
16:04:51 <xarses> moving on
16:04:56 <xarses> #topic Fuel 9.0 release schedule (angdraug) https://wiki.openstack.org/wiki/Fuel/9.0_Release_Schedule
16:05:51 <angdraug> before Christmas, I've posted the release schedule for 9.0:
16:05:51 <angdraug> #link http://lists.openstack.org/pipermail/openstack-dev/2015-December/082655.html
16:05:51 <angdraug> #link https://wiki.openstack.org/wiki/Fuel/9.0_Release_Schedule
16:05:51 <angdraug> this is a transitional release that we use to realign our schedule with OpenStack releases
16:06:11 <angdraug> it's a tight one, basically we barely have time to implement Mitaka support
16:06:32 <angdraug> starting with 10.0/n*, we'll have proper 6-month release cycle like the rest of OpenStack
16:06:50 <angdraug> as I mentioned in my announcement, the biggest risk is external dependencies
16:07:00 <angdraug> namely packages and puppet-openstack
16:07:14 <angdraug> questions?
16:07:28 <xarses> puppet-openstack should be ready ~ start of next week
16:07:48 <xarses> so what if we need to push this?
16:08:18 <angdraug> xarses: what do you mean "push"?
16:08:50 <xarses> we find it's too aggressive and want to move it out?
16:09:18 <angdraug> we can shift the dates if we have to, but it will take time away from 10.0 development
16:09:25 <xarses> ok
16:09:36 <holser_> o/
16:09:59 <xarses> moving?
16:10:04 <ashtokolov> angdraug do we have any estimations about 10.0 release dates?
16:10:08 <angdraug> one big heads up related to that is that we should point Puppetfile at puppet-openstack master HEAD
16:10:35 <angdraug> ashtokolov: with 10.0, we follow the OpenStack n* schedule
16:10:46 <angdraug> you can use https://wiki.openstack.org/wiki/Liberty_Release_Schedule as an early indicator
16:11:13 <angdraug> same as with 9.0, we'll have HCF and a point release a month or two after n* release
16:11:17 <ashtokolov> angdraug Oct-Nov 2016?
16:11:31 <angdraug> so probably some time around Dec 2016 we'll have something that we can recommend for production use
16:11:38 <ashtokolov> I mean there is no 6 months between 9.0.1 and n* release
16:11:43 <holser_> community? or downstream?
16:11:47 <angdraug> as a reminder, HCF is a quality-based milestone, so it all depends on how stable it's going to be
16:12:05 <angdraug> holser_: 9.0.1 is a community release
16:12:21 <angdraug> downstream, it's going to be used in MOS 9.0 GA
16:13:03 <angdraug> ashtokolov: yes, 6 months includes an overlap between stable/mitaka and master/n* development
16:13:24 <angdraug> same as now except most of dev cycle is not going to overlap like it is with 9.0
16:14:22 <angdraug> did I answer your questions?
16:14:51 <ashtokolov> angdraug, yes, I got it
16:14:57 <angdraug> thanks, lets move on then
16:15:08 <ogelbukh> o/
16:15:10 <xarses> #topic Telco Team Status (asvechnikov)
16:15:16 <asvechnikov_> Fuel Telco Team Status:
16:15:19 <asvechnikov_> 1. Primary activity is fixing of 8.0 bugs
16:15:23 <asvechnikov_> In progress: 6
16:15:26 <asvechnikov_> Done: 11
16:15:34 <asvechnikov_> That's all
16:16:08 <angdraug> asvechnikov_: any work planned for 9.0?
16:16:31 <asvechnikov_> angdraug: We are waiting managers desicion
16:16:47 <angdraug> I see
16:18:00 <angdraug> xarses: ogelbukh is back with us, back to his item maybe?
16:18:29 <xarses> #topic ConfigDB description and status (ogelbukh, ytaraday)
16:19:33 <angdraug> ogelbukh: still with us?
16:20:10 <angdraug> hm, I thought on IRC "o/" means "hi", not "bye" :)
16:20:30 <ogelbukh> yep
16:20:44 <ogelbukh> configdb is being developed as a PoC
16:20:53 <ogelbukh> the ETA is next week
16:21:05 <angdraug> do you have a design spec?
16:21:20 <ogelbukh> we are in contact with solar team to define integration level and points
16:21:30 <ogelbukh> only in google docs yet
16:21:52 <angdraug> google doc is fine for a start if its publicly accessible
16:21:56 <ogelbukh> will move to LP/specs
16:22:02 <ogelbukh> once PoC is ready
16:23:11 <ogelbukh> let me check access and share the link
16:23:15 <angdraug> thanks
16:24:03 <xarses> #topic Bugs team status (mmosesohn) https://etherpad.openstack.org/p/fuel-bugs-status
16:24:10 <mattymo> hi!
16:24:22 <mattymo> So, dpyzhov is unavailable, so I'm filling in for bugfix team status
16:24:37 <ogelbukh> https://docs.google.com/document/d/1I7nMOnSrmFhtMPhSWb8BJ48qtImmfUFemzNaNUmDvrY/edit?usp=sharing
16:24:55 <mattymo> (paste warning) I'm going to show some hard numbers on what's coming in and out for bugfixing in ui/python/library teams
16:24:55 <ogelbukh> btw Yuriy sent it to openstack-dev on Dec 22
16:25:06 <mattymo> Real bugs (defects): Critical/high: 54(1/30/23) +25(3/7/15) -41(2/21/18). Medium/low: 54(4/49/1) +11(1/5/5) -10(1/2/7)
16:25:06 <mattymo> Features tracked as bug reports: Critical/high: 35(0/33/2) +0(0/0/0) -2(0/1/1) Medium/low: 82(1/81/0) +1(0/0/1) -3(0/0/3)
16:25:06 <mattymo> Technical debt bugs: Critical/high: 3(0/3/0) +1(0/1/0) -3(0/1/2). Medium/low: 21(0/21/0) +6(0/0/6) -8(0/2/6)
16:25:12 <mattymo> High priority defects on delivery teams: no-team: 5(5) +10(10) -9(9). team-bugfix: 30(30) +6(6) -24(24). team-enhancements: 8(8) +1(1) -1(1). team-network: 8(8) +2(2) -3(3). team-telco: 2(2) +2(2) -1(1). team-upgrades: 0(0) +1(1) -1(1)
16:25:18 <mattymo> Bugs in other teams. Format: Total open(High) +Total income(High) -Total outcome(High)
16:25:18 <mattymo> QA: 57(39) +18(16) -21(19). Docs: 171(40) +1(1) -0(0). Devops: 46(5) +16(4) -7(3)
16:25:18 <mattymo> Build: 2(2) +7(7) -8(8). CI: 75(38) +8(5) -8(6). Infra Apps: 5(0) +1(0) -0(0)
16:25:18 <mattymo> MOS: 98(44) +21(17) -49(40). Partners: 7(6) +2(1) -2(2). Plugins: 4(1) +1(0) -0(0)
16:25:24 <mattymo> Extra filters:
16:25:24 <mattymo> Swarm blockers: 2(0/0/2) +2(0/0/2) -4(0/2/2) Customer found: 0(0/0/0) +0(0/0/0) -1(0/0/1)
16:25:26 <mattymo> Security bugs: 1(0/1/0) +2(0/2/0) -1(0/0/1) Long haul testing: 0(0/0/0) +0(0/0/0) -0(0/0/0)
16:25:28 <mattymo> Affects 7.0: 7(0/3/4) +0(0/0/0) -4(0/1/3) Regressions: 47(1/27/19) +25(3/7/15) -37(2/20/15)
16:25:32 <mattymo> QA/Docs/Infra: 351(124) +50(33) -44(36)
16:26:17 <mattymo> in general, at least in Fuel Library side, all bugs are getting confirmed and reproduced and investigated the same day. We've got a bit of a backlog on reviews mostly due to technical discussion
16:26:51 <angdraug> ogelbukh: it links to https://docs.google.com/document/d/1bUS90ZQVVMw5okHzLFks0svLYjMGKxdGUbz87-0_MFA/edit -- please open that as well
16:27:00 <angdraug> mattymo: we're still fixing Medium bugs?
16:28:04 <mattymo> on library side we're low on high bugs, so we've had a few cycles for tech debt cleanup.. there were 10 resolved medium/low bugs this week
16:28:16 <angdraug> I see that there's not that much of them, but as a reminder 8.0 is in SCF, please make sure that only High and Critical bugfixes are targeted to stable/8.0
16:28:26 <mattymo> they're going to master only, not stable/8.0
16:28:55 <angdraug> mattymo: makes sense, thanks for clarifying!
16:29:26 <mattymo> Any questions?
16:29:37 <angdraug> are you on track with clearing up swarm blockers, need help from other teams?
16:29:56 <mattymo> We've had some help from mpolenchuk and aschultz (ninja bugfixers), but in general, we're in great shape.
16:30:23 <angdraug> good to know, thanks, no more questions from me
16:30:55 <xarses> #topic UI Team status (vkramskikh)
16:31:00 <vkramskikh> Hi! This week we worked on UI tech debt (moving to ES2015 syntax, upgrading testing framework and React, etc.), also solved the remaining 8.0 High bugs (2 of them are merged and 1 is in progress (https://bugs.launchpad.net/fuel/+bug/1533179, planned to be fixed tomorrow)) and worked on moving UI part of Fuel WEB code to a separate repo.
16:31:01 <openstack> Launchpad bug 1533179 in Fuel for OpenStack "Invalid checkboxes logic in Storage Backends" [Critical,In progress] - Assigned to Julia Aranovich (jkirnosova)
16:31:01 <vkramskikh> Since Monday (January 18) we plan to switch to 9.0 features development.
16:31:01 <vkramskikh> Questions?
16:32:13 <angdraug> vkramskikh: same question as for telco team, what are your plans for 9.0?
16:32:18 <xarses> seems, no on the questions
16:32:24 <xarses> nm
16:32:44 <vkramskikh> we have vendor code separation as our biggest feature and a lots of minor impovements
16:33:02 <vkramskikh> which we'll try to deliver after we deal with the code separation
16:33:16 <vkramskikh> which is the main priority
16:33:29 <angdraug> it is indeed :)
16:33:33 <angdraug> thanks
16:34:29 <xarses> #topic open discussion
16:34:40 <xarses> thats the end of the agenda
16:34:46 <xarses> is there anything else to bring up?
16:34:56 <angdraug> didn't have that much time for open discussion in a while :)
16:35:03 <xarses> otherwise we can wrap early
16:35:25 <angdraug> anyone's got stuck reviews, ideas, questions?
16:37:10 <xarses> sounds like its a wrap
16:37:12 <vkramskikh> a have a question about nova-network removal
16:37:15 <vkramskikh> https://review.openstack.org/#/c/261229/
16:37:19 <xarses> ok
16:37:25 <vkramskikh> do we still want to remove it in 8.0?
16:37:32 <vkramskikh> it could be a little late I think
16:38:08 <angdraug> I think we should deprecate it properly first, and plan to remove in 9.0
16:38:12 <xarses> ui, maybe no
16:38:25 <xarses> erm
16:38:30 <xarses> sorry, UI yes
16:38:37 <xarses> networkmanager, and data it needs no
16:39:09 <angdraug> or that
16:39:31 <angdraug> we can drop it from UI, leave CLI possibility there, document in the relnotes that it's deprecated
16:40:06 <angdraug> http://governance.openstack.org/reference/tags/assert_follows-standard-deprecation.html
16:40:06 <xarses> +1
16:40:23 <angdraug> we don't follow this yet but I think we should at least try to stick to it
16:41:25 <angdraug> vkramskikh: how much of an impact on UI would it be to drop it?
16:42:05 <vkramskikh> very little. though AFAIU we need to drop only ability to create a new cluster with nova-network
16:42:17 <vkramskikh> and keep all the other code to manage already deployed clusters
16:42:31 <angdraug> sounds like more than a one-liner
16:42:38 <vkramskikh> yep
16:42:42 <angdraug> maybe just add a deprecation notice to the strings?
16:42:59 <vkramskikh> they are here already
16:43:04 <vkramskikh> since 7.0 AFAIR
16:43:41 <vkramskikh> http://demo.fuel-infra.org:8000/#clusters
16:43:46 <vkramskikh> yes, since 7.0
16:43:46 <angdraug> well, if it's more than a one-liner it would need an FFE, and we're very much too late for that (
16:44:39 <angdraug> lets remove it in master for 9.0
16:44:53 <xarses> to remove it from the UI, it should just be some changes to the openstack.yaml for the wizard
16:45:09 <xarses> and we may need to update the jscript template for that wizard page
16:45:15 <xarses> very minor IMO
16:45:24 <vkramskikh> yep https://review.openstack.org/#/c/261229/11/nailgun/nailgun/fixtures/openstack.yaml
16:45:42 <vkramskikh> but if you look at the change it seems it affects quite a lot of code: https://review.openstack.org/#/c/261229/11
16:45:55 <vkramskikh> though it's mostly code removal
16:46:21 <angdraug> +19 -265
16:46:42 <angdraug> ...and failed CI
16:47:02 <vkramskikh> yep, it's still not ready
16:47:08 <vkramskikh> that's why I raised this topic
16:47:10 <angdraug> holser_: ikalnitsky: thoughts?
16:47:28 <angdraug> looks to me that this is large enough to need an FFE
16:47:29 <vkramskikh> partner team takes care of this change, too bad they're not on this meeting
16:48:08 <angdraug> they should be :(
16:48:39 <xarses> lets send out a message on the ML about this
16:48:41 <angdraug> ok, lets post an FFE for this and see what kind of objections and risks people come up with
16:48:52 <xarses> vkramskikh, can you send it?
16:49:06 <vkramskikh> xarses: ok
16:50:06 <xarses> ok anything else
16:50:26 <xarses> #action vkramskikh will raise topic in ML about https://review.openstack.org/#/c/261229/
16:50:49 <xarses> ok, lets wrap then
16:51:09 <xarses> #endmeeting