16:01:17 #startmeeting fuel 16:01:17 #chair xarses 16:01:17 Todays Agenda: 16:01:17 #link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda 16:01:17 Who's here? 16:01:18 Meeting started Thu Dec 3 16:01:17 2015 UTC and is due to finish in 60 minutes. The chair is xarses. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:22 The meeting name has been set to 'fuel' 16:01:24 Current chairs: xarses 16:01:28 \o/ 16:01:31 hi 16:01:33 Hi! 16:01:35 hi 16:01:37 o/ 16:01:39 hi 16:01:40 hi 16:01:48 hi 16:01:57 hi 16:02:11 #topic Action items from last meeting 16:02:26 holser to report concerns with ubuntu bootstrap design on openstack-dev ML 16:03:08 vkramskikh to include mihgen in conversation about testing external plugin dashboard links 16:03:26 xarses: done 16:03:28 included, vkramskikh did it go further? 16:03:31 hi 16:03:38 mihgen: yep, we're fine 16:04:02 cool. xarses can you go back for holser_'s action? 16:04:04 hi 16:04:05 (action from last week) holser_ to report concerns with ubuntu bootstrap design on openstack-dev ML 16:04:40 I have investigated the status 16:04:58 the problem is pluggability 16:05:23 though we all agreed to create a blueprint and run in 9.0 16:05:46 ok, letms make sure we don't miss that 16:05:52 in 8.0 there will be instruction how to inject drivers to bootstrap 16:05:54 holser_: I still disagree with that problem 16:05:57 is it already created? 16:06:07 not yet ... 16:06:10 is there a bug for the docs? 16:06:11 holser_: openstack-dev email pls 16:06:22 k 16:06:40 #action holser to follow up creating bp for plugging ubuntu bootstrap 16:06:59 #action holser to follow up creating bug for injecting drivers into boostrap for 8.0 16:07:07 ok, moving 16:07:08 kozhukalov review stuck fuel-main patches, delegate to skulanov as needed 16:08:02 hi all 16:08:30 ok, moving; bgaifullin go over reviews in fuel-mirror, close obsolete ones and make sure all related bugs are addressed in new implementation 16:08:40 Fuel-mirror was merged and I’ve reviewed all bugs, so Done (both points) 16:09:14 thanks ashtokolov 16:09:19 warpc help with getting https://review.openstack.org/#/c/231433/ merged 16:10:32 its still open, so if we can get more eyes on that. that would be great 16:10:36 ikalnitsky review refactor-cinder-vmware-role spec https://review.openstack.org/230350 16:10:40 JOIN #openstack-meeting-4 16:10:46 JOIN #fuel 16:10:54 done, since it's merged 16:10:58 =) 16:11:08 ikalnitsky review stuck fuel-web CRs, delegate to maintainers where necessary 16:11:29 i poked guys to review 16:11:41 xares: looks good. What about mihgen question? 16:11:55 honestly, i can't say it really stucks. we did have a more worst situations in recent releases 16:12:08 i also sent an email to openstack-dev with python gerrit dashboard 16:12:16 #link http://lists.openstack.org/pipermail/openstack-dev/2015-November/080774.html 16:12:28 i think it should help to take care 16:12:57 ok, lets keep on it. If you can come up with ways to improve the situation, that would be great 16:13:16 we need more cores.. and more reviewers. 16:13:30 warpc: I missed mihgen's question 16:13:31 i'm going to work on it 16:13:43 ikalnitsky: do we have more ready to join core? 16:14:29 ok, moving 16:14:31 #link https://review.openstack.org/#/c/231433/1/specs/fuel-nailgun-agent.spec 16:14:37 question here perhaps about pkg naming 16:15:11 let's just provide feedback in the review request 16:15:43 mihgen: yes why does it have that anyway 16:15:49 its always the right version 16:16:00 +1 on removing suffix. 16:16:07 it doesn't need ~fuel anyway 16:16:30 in the changeset folks 16:17:12 ok, moving 16:17:12 xarses: moving .. / 16:17:14 holser ikalnitsky review stuck specs, ping angdraug for merge when done 16:18:02 ok xarses 16:18:04 i think there's no specs got 8.0 16:18:22 all unmerged spec should go to 9.0 16:18:36 holser_: +1 16:18:47 we need to ping authors 16:19:04 holser_: if they already landed though, we need to close them out 16:19:27 yep :( 16:19:46 keep in mind, angdraug will be out for a 1-2 weeks so we need to reach agreement with out him 16:20:14 last one 16:20:15 nurla follow up on http://lists.openstack.org/pipermail/openstack-dev/2015-November/080477.html 16:20:59 okay, do you have any comments for me? 16:22:07 I don't, just keep up on it. I'm curious to see how this ends up 16:22:23 ok, for the main attraction... 16:22:27 #topic 8.0 Feature Freeze http://lists.openstack.org/pipermail/openstack-dev/2015-December/081149.html (angdraug) 16:22:51 angdraug is out, so I'll pipe up here 16:23:20 we are now in FF, if you don't yet have a FF you are blocked until we branch 16:23:46 we are planning on branching on SCF (~Dec 23) at which time, master will be open for features again 16:23:53 don't have a FF exception* 16:24:25 mihgen: yes, correct. If you don't already have a FF exception, you are blocked until we branch 16:25:04 any questions? 16:25:09 also we freeze all repos for today 16:25:20 according to our centos7 integration plan 16:25:27 maximov_: for centos7? ya 16:25:31 today only or tomorrow too? 16:25:41 maximov_: for today only? i thought it until it's merged 16:25:51 today evening we will assess the progress 16:25:59 and will extend to tomorrow 16:26:31 #link http://lists.openstack.org/pipermail/openstack-dev/2015-December/081230.html 16:26:50 let's use this thread as a source of truth and watch for updates 16:27:43 time folks, let's go quicker 16:27:46 #topic Moving Fuel services out of Docker containers (kozhukalov) 16:29:26 moving on then 16:29:29 #topic Mixed team status (sslypushenko) 16:29:39 Development on BP https://blueprints.launchpad.net/fuel/+spec/openstack-config-change finished and all patchsets merged. 16:29:57 Manual testing in progress. Some bugs found and fixing is in progress 16:30:10 this is great, could you update status of this bp then.. ? 16:30:25 ok, will do 16:30:40 it's in my list to ask for status update anyway. We want clear pic on what is in and what is out for 8.0 16:30:46 thx 16:31:08 also automation tests is in progress to 16:31:23 I think that is all from my side 16:31:31 if qa is not blocked, then we are good. 16:31:48 We are working on it) 16:31:49 sslypushenko_: thanks, this will become very useful 16:32:07 #topic Telco Team Status (fzhadaev) 16:32:17 Fuel Telco team is finnishing work on Ubuntu bootstrap feature. Current status: 16:32:17 1) All functional commites are merged. 16:32:17 2) Writing automatic tests is in progress. 16:32:17 3) We'll switch to Ubuntu bootstrap by default after tests will be done. 16:32:50 fzhadaev: fantastic, thanks 16:32:54 during meeting yesterday, two commits were mentioned 16:33:02 as those need exception for enabling it 16:33:10 mihgen: they are merged 16:33:19 both merged, appears to be those are not for enabling ubuntu by default? 16:33:42 in my email: Ubuntu boostrap. Two patches requested for FFE: https://review.openstack.org/#/c/250504/, https://review.openstack.org/#/c/251873/. Both are merged. So I consider that this is actually done. 16:34:06 so then it is not a correct statement. Why didn't you folllow up in the email thread.. ? 16:34:25 yep. feature is done. switching the default os isn't part of feature. 16:34:34 it's just UX improvement 16:34:35 It IS part of the feature 16:34:45 if it's not tested now automatically 16:34:55 and by all who download and manually test ISO 16:35:11 that means we losing cycles of finding potential issues there 16:35:30 more over, it means that code is not complete if you can't just easily switch now 16:35:54 ok, let me comment 16:35:59 what is left to be done to switch it to be default one? 16:36:23 in the initial plan automatic tests are scheduled to be completed in the upcoming iteration 16:36:51 and we do not want to switch it by default unless it is run agaist these tests 16:37:07 switch is a small commit in a fuelmenu 16:37:17 so, then the feature is out for 8.0, it needs to be moved to experimental 16:37:37 and I see more risk to switch to it without tests 16:37:53 I don't really get why it won't be tested if we switch to it by default? 16:37:56 BTW, Ubuntu is available in Fuel menu now. User can chose it as bootstrap os. It's just not default OS. 16:37:57 generally if needed we can switch to it even now 16:37:58 in all swarm & bvt 16:38:09 do we have documentation that explains how to build dynamic, ubuntu bootstrap if custom drivers are needed? 16:38:29 ntrueblood: doc will be completed in January 16:39:04 mihgen: we can generally switch even now by default to ubuntu 16:39:12 dklenov: unless it runs by default starting from now, I feel there is a large risk of releasing it as a production solution later 16:39:26 we need community, and other to start actually using it 16:39:44 ok, I would involve QA folks as well 16:39:46 and file bugs. Delaying a moment of running it by default means way less testing 16:40:06 dklenov: please follow up in my email about FF exceptions with detailed data and plan 16:40:32 #topic Enhancements Team Status (ashtokolov) 16:40:51 Yesterday we finished feature development (except one FFE 16:40:58 Enhancements Team status: Fix committed+Fix released = 51 16:41:25 #action dklenov will follow up with with details on enabling ubuntu bootstrap on FFE thready 16:42:24 ashtokolov one multi rack feature went out of scope of 8.0 16:42:38 ashtokolov it was moved to 9.0 16:43:25 sorry, I had troubles with irc client 16:43:34 holser_: which one? 16:43:48 adidenko knows better 16:44:07 it is manual VIP address seting 16:44:15 ok 16:44:16 setting* 16:44:16 it's about ATT task with VIP allocation 16:44:33 we faced with DB changes 16:44:37 The following BPs have been moved out of multirack scope and assigned to 9.0 16:44:37 https://blueprints.launchpad.net/fuel/+spec/allow-any-vip 16:44:37 https://blueprints.launchpad.net/fuel/+spec/dhcp-vips 16:44:37 https://blueprints.launchpad.net/fuel/+spec/selective-default-gateway-net 16:44:48 ok 16:44:52 we also have not quite finished creating a document that describes how to set up controllers in HA across multiple racks. 16:45:02 multiple l3 segmented racks, that is. 16:45:03 and there was no way to fix it without DB changes 16:45:40 ntrueblood: do we have the docs defect captured somewhere? 16:45:43 alex_didenko: is it in your todo list for HA across multiple racks docs.. ? 16:46:00 #link https://bugs.launchpad.net/fuel/+bug/1476140 ? 16:46:00 Launchpad bug 1476140 in Fuel for OpenStack "Nodegroup instructions improvement" [Medium,Confirmed] - Assigned to Fuel Documentation Team (fuel-docs) 16:46:43 We have a JIRA backlog item for it, but we probably also need an lp bp. Not sure of status 16:46:56 mihgen: yes 16:46:58 lets keep going, we have 14 min 16:47:04 #topic UI Team status (vkramskikh). 16:47:09 Hi, we've merged all the features we planned to deliver without FFEs and switching to bugfixing and helping partners team to deliver Component registry. We have 7 High bugs and plan do fix them before SCF. Any questions? 16:47:16 mihgen: I'll update maybe on the next meeting about it 16:47:27 alex_didenko: cool, thx 16:47:51 vkramskikh: sounds good. thanks for keeping an eye on component registry FFE 16:48:13 vkramskikh: great =) 16:48:23 #topic Bugs team status (dpyzhov) https://etherpad.openstack.org/p/fuel-bugs-status 16:48:30 hi guys 16:48:37 I've update bugs statistics 16:49:00 Right now my team is focused on several high priority tricky bugs 16:49:15 We don't have many of them 16:49:21 and almost all of them are assigned 16:49:26 anything that we should discuss? 16:49:27 dpyzhov: do you see an increasing # of incoming? 16:49:38 mihgen: not yet 16:49:44 Actually I have a question 16:50:02 Are we going to have more developers moved to bugfixing now? 16:50:08 qa is not at full speed then. Let's sync and help if needed, they might be blocked 16:50:26 We have a bunch of medium priority bugs 16:50:29 One bug that is really impacting our ability to fix bugs is tracebacks in syslog in oslo.logging 16:50:43 It was rejected as invalid by mos oslo team (dims) as a feature, not a bug 16:50:44 I expect all teams which were working on features to do bugfixes in their features implmeneted 16:51:01 we have to reproduce the original problem in order to get the local trace that gets sent directly to file 16:51:09 And if we'll have more people than we'll need to think how to organize them all effectively 16:51:19 mattymo: if not already, lets start a ML about that 16:51:40 mattymo: this would be great feedback to oslo team from operators, i.e. you, let's share in ML 16:51:51 mihgen: and what will happen when they fix their bugs? 16:51:59 work on other features 16:52:06 xarses, sure. I've found another fun bug where some cinder errors don't log traceback to either) 16:52:09 master opens on SCF 16:52:11 mihgen, I'll start a thread on it 16:52:17 cool 16:52:26 So noone is going to join the bugs backlog cleanup party 16:52:30 that's ok 16:52:31 thanks 16:52:48 I have no more questions 16:52:50 #topic Let's clarify 8.0 blueprints statuses (mihgen) 16:53:24 folks let's go over some of bps, but I really need your help to go over them and just set rigth status or move out of 8.0 16:53:29 #link https://etherpad.openstack.org/p/8.0-features-status 16:53:30 #action mattymo will create ML to discuss issues with oslo.logging not sending some tracebacks on syslog 16:53:30 I need reviewers for Tenant IPv6 Docs and Tests spec https://blueprints.launchpad.net/fuel/+spec/provider-tenant-ipv6-networking 16:53:32 this is the list 16:53:36 #link https://blueprints.launchpad.net/fuel/+spec/provider-tenant-ipv6-networking 16:54:07 nurla: can you find someone to help with tests spec for ^^ ..? 16:54:19 mattymo_ : needs to be fixed upstream first https://bugs.launchpad.net/oslo.log/+bug/1514828 16:54:19 Launchpad bug 1514828 in oslo.log "tracebacks are not logged to syslog" [Low,Triaged] 16:54:42 yep, we agreed with Alekesey that we are staring work after FF 16:54:51 dims_: I doubt if it's Low if it makes life of ops very painful 16:54:58 mihgen nurla: ashtokolov said we're staring doing QA on next week, QA engineer is alerady allocated 16:55:00 yottatsa: ping me offline for docs 16:55:08 other bps: #link https://blueprints.launchpad.net/fuel/+spec/support-ip-ranges-for-storage-management-networks-on-ui 16:55:08 mihgen : welcome to bump up that importance :) 16:55:10 vkramskikh: ^^ 16:55:25 yottatsa: after FF :) 16:55:44 nurla yes, on I-4 16:55:59 #link https://blueprints.launchpad.net/fuel/+spec/network-interfaces-naming-schema 16:56:06 holser_: do you status of this one ^^ 16:56:47 alex_didenko: can we move https://blueprints.launchpad.net/fuel/+spec/l3-multiple-racks to implemented? what deployment status means? 16:57:15 mihgen: we have some QA BPs linked to this BP 16:57:22 and they are still in development 16:57:22 bgaifullin: https://blueprints.launchpad.net/fuel/+spec/refactor-local-mirror-scripts can this one be closed as Implemented.. ? 16:58:00 3 min 16:58:07 well 2 16:58:28 alex_didenko: we need to think about how to do it in this case then. when I open https://launchpad.net/fuel/+milestone/8.0, I'd like to understand what is in and what is out.. 16:58:40 actually, I've closed mine as implemented, we'll track system tests separately 16:58:42 may be deployment status is ok and we push all other out 16:58:45 mihgen, I think yes 16:58:58 vkramskikh: holser_ reply on those two first bps... ? 16:59:07 bgaifullin: cool,pls update 16:59:17 #link https://blueprints.launchpad.net/fuel/+spec/plugin-after-deployment 16:59:20 ikalnitsky: ^^ 16:59:27 ashtokolov: ^^ 16:59:43 Dine 16:59:47 Done 16:59:48 it's done 16:59:48 all patches are merged 17:00:09 pls update bp then 17:00:11 time folks, lets wrap on #fuel-dev 17:00:20 #endmeeting