16:00:15 <xarses> #startmeeting fuel
16:00:15 <xarses> #chair xarses
16:00:15 <xarses> Todays Agenda:
16:00:15 <xarses> #link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
16:00:15 <xarses> Who's here?
16:00:16 <openstack> Meeting started Thu Apr 14 16:00:15 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:17 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:20 <openstack> The meeting name has been set to 'fuel'
16:00:21 <openstack> Current chairs: xarses
16:00:24 <mwhahaha> hi2u
16:00:25 <fzhadaev> Hi!
16:00:28 <mihgen> hi
16:00:31 <pzhurba> Hi!
16:00:39 <akasatkin> hi
16:00:40 <kozhukalov> hi
16:00:45 <vsakharov> hi
16:00:46 <angdraug> \o
16:00:50 <romcheg> \o
16:01:17 <EZPZ> HI
16:01:32 <xarses> #topic action items from last meeting
16:01:36 <xarses> mwhahaha alex_didenko zynzel will document remaining gaps in idempotency coverage
16:02:02 <mwhahaha> nope, will do it this week. i'd also like to know where qa is around the tests for it
16:02:14 <alex_didenko> I have no news but https://launchpad.net/bugs/1541309
16:02:15 <openstack> Launchpad bug 1541309 in Fuel for OpenStack "Make network configuration idempotent" [High,In progress] - Assigned to Aleksandr Didenko (adidenko)
16:02:40 <xarses> thanks, I will ask again next week then?
16:03:04 <xarses> bookwar will update dev focus to newton
16:03:19 <dpyzhov> done
16:03:25 <xarses> thanks
16:03:30 <xarses> bookwar and dpyzhov will collaborate on next steps for moving bugs
16:03:41 <dpyzhov> done
16:03:52 <dpyzhov> Will share the status in my report
16:04:08 <xarses> ok
16:04:12 <xarses> #topic Telco Team Status (fzhadaev)
16:04:20 <fzhadaev> My update will be short. Our team continues fixing bugs:
16:04:20 <fzhadaev> Done 10
16:04:20 <fzhadaev> In progress (in development and on review) 11
16:04:20 <fzhadaev> Do you have any questions?
16:05:06 <xarses> any planning for newton?
16:05:17 <fzhadaev> not yet
16:05:46 <xarses> k
16:05:48 <xarses> #topic Mixed team status (pzhurba)
16:05:53 <pzhurba> Hi
16:05:57 <pzhurba> Mixed team was working on customer support, common bugfixing, and reviews.
16:06:18 <pzhurba> For now there are 2  open bugs in work connected our feature - multipath
16:06:45 <pzhurba> https://bugs.launchpad.net/fuel/+bug/1567450
16:06:46 <openstack> Launchpad bug 1567450 in Fuel for OpenStack "Provisioned node with multipath device can't boot if Base System isn't on dm-0" [High,Confirmed] - Assigned to Krzysztof Szukiełojć (kszukielojc)
16:06:46 <pzhurba> And
16:06:46 <pzhurba> https://bugs.launchpad.net/fuel/+bug/1562836
16:06:47 <openstack> Launchpad bug 1562836 in Fuel for OpenStack "[fuel-qa][venv]Provision of node with multipath device fails on boot" [High,Confirmed] - Assigned to Fuel QA Team (fuel-qa)
16:06:58 <pzhurba> that is all
16:07:13 <pzhurba> questions?
16:07:17 <xarses> any planning for newton?
16:07:32 <pzhurba> ?
16:07:53 <pzhurba> I din'd heard any thing
16:07:53 <xarses> have you thought about what your team will work on in newton?
16:08:04 <xarses> ok
16:08:06 <pzhurba> Not yest
16:08:09 <pzhurba> Not yet
16:08:13 <xarses> #topic UI Team status (vkramskikh)
16:08:18 <vkramskikh> Hi! Since the last week we had 3 outgoing and 3 incoming High bugs. Currently we have 3 High bugs. One of them is a bug related to unlock-settings-tab feature, 2 other bugs are late-discovery bugs. We plan to fix them before the release of Apr 20th.
16:08:18 <vkramskikh> After finishing our work on bugs we want to resolve some tech debt. We already updated lots of our dependencies to the latest versions, including React v15 which was released on Apr 8th.
16:08:18 <vkramskikh> Questions?
16:09:27 <xarses> any plans for newton? looks like you are getting your deps updated
16:09:46 <vkramskikh> we're going to resolve some tech debt, no plans for features yet
16:09:54 <xarses> ok
16:10:06 <xarses> #topic Bugfix status (dpyzhov)
16:10:20 <dpyzhov> We've moved medium/low/wishlist priority bugs to Newton release
16:10:47 <dpyzhov> Now we are targetting high/critical priority bugs both to Newton and Mitaka
16:11:18 <dpyzhov> We have some bugs with keep-in-9.0 tag
16:11:23 <xarses> by moved, we mean marked wont fix in Mitaka and adding Newton series?
16:11:28 <dpyzhov> I guess we'll fix them in Newton
16:11:33 <dpyzhov> xarses: exactly
16:11:53 <dpyzhov> maybe we'll replace keep-in-9.0 tag with something more appropriate
16:12:01 <xarses> do you know what the carry over stats where?
16:12:16 <xarses> i.e. how many did we move over
16:12:36 <dpyzhov> Now we have 88 high priority bugs in library and python. As I know we have a release in nearest future. Are we ok to release with this number of bugs?
16:12:48 <dpyzhov> xarses: I shared stats last week
16:12:53 <dpyzhov> it was about 100 of bugs
16:12:56 <xarses> ok
16:13:19 <dpyzhov> 122 bugs
16:13:33 <dpyzhov> it is current value
16:13:43 <kozhukalov> dpyzhov: we are not ok with having 88 high bugs, we are going to announce 9.0 release as unstable and then achive higher quality in June
16:14:24 <dpyzhov> Are we going to have public iso in June with fixes?
16:14:25 <kozhukalov> it will 9.0.1 release
16:14:32 <kozhukalov> yes
16:14:33 <dpyzhov> great
16:14:55 <xarses> have we looked over the high's to make sure they are high?
16:15:04 <xarses> that seems like alot
16:15:15 <dpyzhov> there are many bugs in new features
16:15:47 <kozhukalov> we are going to analyze these 88 bugs on Monday
16:16:00 <xarses> OK
16:16:03 <dpyzhov> however we didn't perform special review if they all are high priority
16:16:11 <kozhukalov> in order to understand which of them are Higher than other high bugs
16:16:36 <dpyzhov> there should be no low priority bugs among them because almost all bugs are in progress
16:17:04 <dpyzhov> thats all from my side
16:17:07 <kozhukalov> moving on?
16:17:14 <xarses> #topic Austin design summit sessions planning (deadline for filling in is 04/15/2016) (kozhukalov)
16:17:42 <kozhukalov> we have couple of sessions where we the agenda is not filled in yet
16:17:51 <kozhukalov> deadline is tomorrow
16:18:21 <kozhukalov> we'd better put all our sessions to the official schedule one week before summit
16:18:29 <xarses> #link https://etherpad.openstack.org/p/fuel-newton-summit-planning
16:18:41 <kozhukalov> yes, thanks for the link
16:19:05 <kozhukalov> xarses: one of those empty agendas is in your session about plugins
16:19:12 <xarses> yes, I see
16:19:26 <kozhukalov> and another is about scalability
16:19:50 <kozhukalov> also I have added puppet master integration topic to LCM session
16:20:12 <xarses> ok
16:20:17 <kozhukalov> in order to make sure community is informed about this solution
16:21:00 <xarses> anything else?
16:21:07 <kozhukalov> nothing
16:21:10 <xarses> #topic open discuss
16:21:11 <kozhukalov> thanks
16:21:27 <xarses> if any one has anything to raise, otherwise I will close the meeting shortly
16:21:56 <kozhukalov> we have few bugs which are related to /boot partition
16:22:09 <kozhukalov> #link https://bugs.launchpad.net/fuel/+bug/1569956
16:22:10 <openstack> Launchpad bug 1569956 in Fuel for OpenStack mitaka "fuel does not provision software raid as shown in documentation" [High,Confirmed] - Assigned to Fuel Python Team (fuel-python)
16:22:25 <kozhukalov> #link https://bugs.launchpad.net/fuel/+bug/1566399
16:22:25 <openstack> Launchpad bug 1566399 in Fuel for OpenStack 8.0.x "Fuel creates boot partitions on unalocated drives" [High,Confirmed] - Assigned to MOS Maintenance (mos-maintenance)
16:22:39 <kozhukalov> #link https://bugs.launchpad.net/fuel/+bug/1567450
16:22:39 <openstack> Launchpad bug 1567450 in Fuel for OpenStack "Provisioned node with multipath device can't boot if Base System isn't on dm-0" [High,Confirmed] - Assigned to Krzysztof Szukiełojć (kszukielojc)
16:23:06 <kozhukalov> we have kind of tricky logic in fuel-agent about where to put this /boot partition
16:23:39 <kozhukalov> this logic does not cover all possible cases
16:23:56 <kozhukalov> my suggestion is to introduce bootable disk flag on UI
16:24:43 <kozhukalov> we had it 3 years ago, and now it seems that it was not so bad idea
16:24:53 <xarses> ya, we will probably need to re-work it again
16:24:56 <kozhukalov> what do you guys think?
16:25:45 <kozhukalov> the thing is in most cases we could put /boot partition on the same disk where first physical volume of os volume group is located
16:25:59 <kozhukalov> but it does not work for nvme devices
16:26:12 <kozhukalov> and probably for some other cases
16:26:29 <kozhukalov> so we need this to be exposed to a user
16:26:50 <kozhukalov> so she can configure it if default assumption is wrong
16:27:15 <kozhukalov> vkramskikh: said that it is not so hard to implement this even in 9.0
16:27:22 <xarses> we'll likely have to draft out how this will need to be restructured and weigh in on it. I'd like to ensure we have uefi support too
16:28:08 <kozhukalov> if we adopt Ironic then we will get uefi out of the box
16:28:34 <kozhukalov> it would be great to have uefi support in fuel
16:28:56 <kozhukalov> ok, looks like we can move this discussion to ML
16:29:08 <kozhukalov> that is it from my side
16:29:11 <xarses> ok, sounds good
16:29:44 <xarses> I will close shortly if there is nothing else.
16:31:00 <xarses> ok, thanks everyone
16:31:06 <xarses> #endmeeting