16:00:53 #startmeeting Fuel 16:00:53 Meeting started Thu May 12 16:00:53 2016 UTC and is due to finish in 60 minutes. The chair is kozhukalov. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:58 The meeting name has been set to 'fuel' 16:01:04 hello everyone 16:01:11 agenda is here 16:01:11 hi 16:01:12 hi 16:01:16 hi! 16:01:16 Hi! 16:01:17 #link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda 16:01:43 #topic Mixed team status (asaprykin) 16:01:52 hi 16:01:52 https://www.irccloud.com/pastebin/scV2XxT1/ 16:02:16 hi! 16:02:23 Mixed team is working on bugfixing. 16:02:24 One critical bug https://bugs.launchpad.net/fuel/+bug/1576127. 16:02:25 Patch was merged to 10.0, backport to 9.0 is on review. 16:02:25 Questions? 16:02:25 Launchpad bug 1576127 in Fuel for OpenStack mitaka "Execution of openastck-config doesn't applied for primary-controller node" [Critical,In progress] - Assigned to Alexander Saprykin (cutwater) 16:03:05 short status indeed 16:03:50 is this bug a blocker for swarm? 16:04:04 yes, it is 16:04:33 how many test cases does it break? 16:05:15 ok anyway fix is on review, thanks asaprykin 16:05:17 It breaks test cases related to this particular feature 16:05:31 doesn't affect anything else 16:05:37 moving on then? 16:05:58 #topic UI Team status (vkramskikh) 16:06:03 Hi! We're still working on bugs - during Russian holidays we've got 5 new High and Critical bugs. We still have 6 High and 1 Critical bug to fix. 16:06:03 As for Newton acitvities, we're working on tech debt - updating our dependencies (Backbone & LoDash, attempting to use NPM 3.x dedupe functionality) and migrating to native promises from jQuery Deferreds. 16:06:03 Also, as a result of my discussions during summit, we're helping OpenStack to move towards migration to ES6 aka ES2015 by adding ES6-related rules for ESLint to eslint-config-openstack: https://review.openstack.org/#/q/project:openstack/eslint-config-openstack+topic:es6 16:06:04 Questions? 16:07:38 vkramskikh_: great that you are helping them to switch to ES6 16:08:01 unfortunately for Newton we still don't have clear scope 16:08:23 I hope it will be clear at the beginning of next week 16:08:49 thank you vkramskikh_ for the information 16:09:01 looks like no one has any q 16:09:04 moving on 16:09:04 you're welcome :) 16:09:21 #topic Telco Team Status (fzhadaev) 16:09:33 Our team continues fixing bugs: 16:09:33 Done from the last update - 12 16:09:33 In progress (in development and on review) - 15 16:09:33 Still have no certain plans for 10.0. 16:09:33 Do you have any questions? 16:11:27 yes, I heard about some issues with dpdk in nailgun-agent, do you have any info on this? 16:12:38 akasatkin: could also have some info on this 16:12:48 are there any links to bugs? 16:13:36 ok, looks like akasatkin isn't here 16:13:40 moving on then 16:13:55 #topic Toolbox Team status (ashtokolov) 16:13:57 hm. I can't answer right now. sorry :( I'll try to find this bug 16:14:07 Fuel toolbox Team is working on bugs 16:14:10 looking.. 16:14:16 Current status: 25 bugs 16:14:25 Last 2 weeks status: Income 13 bugs, Outcome: 17 bugs. 16:14:31 One critical bug https://bugs.launchpad.net/fuel/+bug/1578974 was fixed in master and on review in stable/mitaka 16:14:33 Launchpad bug 1578974 in Fuel for OpenStack mitaka "It is not possible to execute a separate task" [Critical,In progress] - Assigned to Igor Kalnitsky (ikalnitsky) 16:14:54 that's all 16:15:38 nice 17 bugs fixed for 2 weeks 16:15:46 great job folks 16:15:55 thanks for the info 16:16:10 does anyone have any q here? 16:16:49 Folks, regarding DPDK issue - it is https://bugs.launchpad.net/fuel/+bug/1580541. Integration between nailgun-agent and nailgun 16:16:50 Launchpad bug 1580541 in Fuel for OpenStack "Compute re-deployment with network bonding and DPDK fails: Puppet (err): Can't add bond 'bond0'" [High,In progress] - Assigned to Aleksey Kasatkin (alekseyk-ru) 16:17:32 dklenov: thanks 16:17:48 ah, https://bugs.launchpad.net/fuel/+bug/1580541 . it's more about bonds than dpdk .. we don't have a good solution for nailgun-agent so far so we patch nailgun 16:17:54 i see it is on review 16:18:36 to not accept info from nailgun-agent in some cases 16:18:57 btw, there is a patch for nailgun-agent about getting rid of ohai https://review.openstack.org/#/c/314642/ 16:19:35 i don't like because i hope we'd better get rid of nailgun-agent itself 16:19:49 in favor of ironic-inspector 16:19:59 but it is another story 16:20:02 moving on 16:20:30 #topic diagnostic snapshot & shotgun - using non-root (gomarivera) 16:20:39 With regards to https://specs.openstack.org/openstack/fuel-specs/specs/9.0/fuel-nonroot-openstack-nodes.html. 16:20:39 Which mentions: * Nailgun will pass to Shotgun ssh-user parameter along with ssh-key for remote SSH access. This username will be taken from the DB. * Shotgun will be extended to accept ssh-user parameter and use sudo, if needed. 16:20:39 We need discussion about the method of design for shotgun and diagnostic snapshot such that they do not require root level access to the openstack nodes. Furthermore, the diagnostic snapshot capabilities should enable a certain level of viewing privileges for the data. 16:20:39 what we want to discuss is 16:20:39 1. Is diagnostic snapshot still a feature that will be kept in the Fuel roadmap? 16:20:39 2. prior discussions mentioned the use of file transfer method or a potential sudo implementation of the fetch 16:20:40 the non-root feature - will it be definitely implemented in by Fuel 10 16:20:40 if not we need consensus on whether to sue sudo to fetch files or provide a strategy around addressing this in the current cycle 16:23:31 1. IMO diag snapshot should be independent (shotgun is already independent project), and there are plans to move it to plugins or get rid it totally in favor of timmy tool 16:23:42 give me a second to find a link 16:24:07 https://github.com/adobdin/timmy 16:24:40 i am not sure about this particular tool (mirantis support team uses it) 16:25:38 I'd like fuel to provide a good plugin interface for such a feature like diag snapshot button on UI 16:25:57 i am not familiar with it either - in concern to the topic - my question would be regarding the expected design around using non-root access - and any view privileges 16:25:59 or UX could be totally CLI 16:26:21 could we have a standalone task graph to fetch diagnostic data? 16:26:28 my vote for diagnostic snapshots on the local nodes would be to leverage https://github.com/sosreport/sos rather than write yet another one. then figure out a way to collect them 16:26:57 kozhukalov: yes, looks like timmy is specifically designed for gathering logs for openstack env, +1 to use it 16:27:22 gomarivera: anyway I understand your concerns about root access 16:28:29 it represent a blocker to dnikishov - he brought up that not having a clear path forward in addressing it could block the non-root implementation 16:29:47 maximov: I am not talking that timmy or any other tool should replace shotgun. my idea is rather that diag snapshot should not be default fuel functionality, it should be a separate tool, everyone should be able to use his favorite tool 16:30:40 if there's plan to decouple diagnostic snapshot to a different tool that's pluggable then that would make it better 16:31:27 is there a blueprint/spec for this? 16:31:51 we in the end need a plan b in case the new tool is not implemented during 10/N timeframe 16:33:19 gomarivera: i don't like the idea to use fabric sudo feature instead of root access, because it does not actually addresses all the security issues, but yes, in 9.0 we could accept this fix that dnikishov made, but keeping in mind that in the future we will make this feature independent 16:34:50 dnikishov: blueprints for Newton will be created next week (still don't have approved scope and resources) 16:35:05 thanks 16:36:27 gomarivera: plan B would be to use timmy or use shotgun independently (btw it is data driven) 16:37:09 as far as I understand dnikishov had some ideas to use kind of rootwrap for dealing with this 16:37:26 dnikishov: could you comment on this? ^ 16:38:30 kozhukalov: do I understand this correctly that for now it's ok to have fabric sudo in shotgun, but we'll have to design a new tool with possibility of non-root in mind? 16:38:50 gomarivera: about timmy could you please contact adobdin@mirantis.com directly or in openstack-dev ML? 16:39:06 yes i can 16:39:38 rootwrap could be used, but only if we know what we need to collect beforehand 16:40:38 dnikishov: yes, let's do it for 9.0, but please make resource property (i.e. configurable) 16:41:47 ok, are there any other q? 16:41:51 moving on? 16:42:07 #topic Open discussion 16:43:10 Please see mailing list about using upstream haproxy module 16:44:37 #link http://lists.openstack.org/pipermail/openstack-dev/2016-May/094823.html 16:45:19 thanks mwhahaha for this info 16:46:02 ok, if there are no other topic, then closing 16:46:11 thanks everyone for attending 16:46:22 #endmeeting