16:00:05 #startmeeting fuel 16:00:05 Meeting started Thu Sep 1 16:00:05 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:06 #chair xarses 16:00:06 Todays Agenda: 16:00:06 #link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda 16:00:06 Who's here? 16:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:10 The meeting name has been set to 'fuel' 16:00:11 Current chairs: xarses 16:00:14 hi 16:00:36 hi 16:00:41 \o 16:00:48 hi 16:00:52 hi 16:01:20 hi 16:01:53 #topic action items from last week 16:02:03 romcheg update ML with regards to the removal of fuel and the promotion of fuel2 16:02:12 That was done 16:02:18 should I post a link? 16:02:28 thats fine, thanks! 16:02:41 kk 16:02:49 romcheg: we did only for newton, we didn't back port it to mitaka? 16:03:10 No, at some point we got blocked by fuel-devops 16:03:31 ok, thanks 16:03:35 perhaps we will be able to resolve the issue by 9.2 16:04:12 I should mention that we only didn't manage to deprecate the old CLI in 9.1. The rest of the plan was done 16:05:03 ok 16:05:12 #topic 9.1 Bugs Scope http://bit.ly/fuel-9-1-sustaining-bugs http://bit.ly/fuel-9-1-networking-bugs (dpyzhov) 16:05:32 so, we have about 2 weeks before release of 9.1 update 16:05:59 and we have some untaken bugs. I think it is a good time to start moving some of them to 9.2 16:06:14 or maybe even don't backport to Mitaka at all 16:06:46 first of all, we have bugs with networking and we have very limited manpower in this area 16:06:53 shouldn't we just move all of the medium as defacto? 16:06:57 #link http://bit.ly/fuel-9-1-networking-bugs 16:07:20 xarses: agree, all medium priority bugs should go to 9.2 16:07:40 xarses: we should review carefully even medium bugs to ensure that priority set correcty before moving them 16:07:48 at networking we have 11 high priority bugs 16:08:05 maximov: all bugs will be moved manually 16:08:38 I think we should focus on field reports in networking and move all other bugs to 9.2 16:09:01 there are 3 bugs with customer-found tag 16:09:42 so you propose to move 7 net bugs which don't have customer-found tag ? 16:09:52 maximov: yes 16:11:32 are we on same page here? 16:12:06 I think so 16:12:07 https://bugs.launchpad.net/fuel/mitaka/+bug/1594287 this seems to important 16:12:07 Launchpad bug 1594287 in Fuel for OpenStack mitaka "Network verification failed after reboot of cluster with bonded interfaces" [High,Confirmed] - Assigned to l23network (l23network) 16:12:40 we shouldnt move bugs which fails our swarm tests 16:13:26 maximov: looks like the issue is not related to networking 16:13:30 We should focus on bugs that prevent deployment, and then in common cases beyond that we don't have time to fix everything 16:14:34 ok, I'll move https://bugs.launchpad.net/fuel/mitaka/+bug/1594287 to other teams for deeper investigation 16:14:34 Launchpad bug 1594287 in Fuel for OpenStack mitaka "Network verification failed after reboot of cluster with bonded interfaces" [High,Confirmed] - Assigned to l23network (l23network) 16:15:05 dpyzhov: ok 16:15:20 are we ok with other bugs? 16:16:12 https://bugs.launchpad.net/fuel/mitaka/+bug/1618891 16:16:12 Launchpad bug 1618891 in Fuel for OpenStack mitaka "haproxy issue: backends are in DOWN state after node restarts" [High,Confirmed] - Assigned to Fuel Sustaining (fuel-sustaining-team) 16:16:47 xarses: this is from fuel-sustaining list 16:17:01 it is next list 16:17:05 #link http://bit.ly/fuel-9-1-sustaining-bugs 16:17:05 ok 16:17:54 here we have 1 critical and 16 high priority bugs 16:18:02 and as I said we have 2 weeks 16:18:57 I propose to keep them all in the list until next week 16:19:40 https://bugs.launchpad.net/fuel/mitaka/+bug/1587310 - ok to move looks like hw issue 16:19:40 Launchpad bug 1587310 in Fuel for OpenStack mitaka "[X(L)710] MTU for private network on DPDK-enabled interface is configured incorrectly" [High,Confirmed] - Assigned to l23network (l23network) 16:19:42 I don't see any high priority bug that definitely should be removed from the release 16:20:12 https://bugs.launchpad.net/fuel/mitaka/+bug/1597775 also hw issue, ok to move 16:20:12 Launchpad bug 1597775 in Fuel for OpenStack newton "[nailgun-agent] VNICs ignored due to SR-IOV filtering" [High,Confirmed] - Assigned to l23network (l23network) 16:21:33 These seem more important, but I don't see any others to move https://bugs.launchpad.net/fuel/mitaka/+bug/1608700 https://bugs.launchpad.net/fuel/mitaka/+bug/1613367 https://bugs.launchpad.net/fuel/mitaka/+bug/1613724 https://bugs.launchpad.net/fuel/mitaka/+bug/1618891 16:21:33 Launchpad bug 1608700 in Fuel for OpenStack mitaka "Provision failed due to astute/cobbler timeouts." [High,Confirmed] - Assigned to Fuel Sustaining (fuel-sustaining-team) 16:21:34 Launchpad bug 1613367 in Fuel for OpenStack mitaka "'Success Deployment is done' and 'deployment was unsuccessful' at the same time " [High,Confirmed] - Assigned to Fuel Sustaining (fuel-sustaining-team) 16:21:36 Launchpad bug 1613724 in Fuel for OpenStack mitaka "Can't create instance in nova az after shutdown primary controller after scale environment." [High,Confirmed] - Assigned to Fuel Sustaining (fuel-sustaining-team) 16:21:37 Launchpad bug 1618891 in Fuel for OpenStack mitaka "haproxy issue: backends are in DOWN state after node restarts" [High,Confirmed] - Assigned to Fuel Sustaining (fuel-sustaining-team) 16:22:47 ok, moving? 16:22:53 yes 16:22:54 thanks for feedback 16:23:08 #topic Newton FF (kozhukalov) 16:23:19 Just an announcement 16:23:28 Today is FF for Newton 16:23:41 will write ML in openstack-dev 16:24:04 but i'd like to know if there are any FFe requests 16:24:23 I will probably ask for one for tags 16:25:00 https://review.openstack.org/#/c/341678/ 16:25:11 and ISOless bvt and deployment test jobs also is not finished yet 16:25:23 so, let's discuss this in ML 16:25:52 ok 16:26:07 #topic CCP update - status & nearest plans (mzawadzki) 16:26:41 Here's the update from CCP team: 16:26:45 New features merged: 16:26:58 * Enable mcp build tool to use git repositories or local folder for components code 16:27:03 * Heat support 16:27:06 * Dependencies between services 16:27:10 * Per-service deployment 16:27:12 * Logging and monitoring improved 16:27:19 Nearest plans: 16:27:24 * Stabilize, fix urgent bugs 16:27:29 * Start moving docs to upstream 16:27:34 * Basic support for updates 16:27:42 * DSL versioning 16:27:47 * Improve CI tests for Docker images built before they get published 16:27:55 That's it, guys, Questions? 16:29:13 When might you produce an install procedure // release bundle for fuel so that we can stand up an env? 16:30:05 The preliminary plan is to publish install docs in next 3 weeks. 16:30:37 but not release bundle for fuel or smth. like this, right? 16:30:55 i doubt it is duable in 3 weeks 16:31:43 No, I don't think so. Installation is based on tools from git repositories and on Docker images pulled from registry (some can be optionally built locally). 16:32:36 right, there is no plan to provide any integration with fuel before the end of ocata cycle 16:33:00 ci/cd like ux only 16:33:19 or script 16:34:27 anything else? 16:34:35 ok, thanks guys 16:34:39 #topic open discuss 16:34:50 if there is nothing else, I will close the meeting shortly 16:36:06 thanks everyone 16:36:10 #endmeeting