16:01:34 <xarses> #startmeeting fuel
16:01:34 <xarses> #chair xarses
16:01:34 <xarses> Todays Agenda:
16:01:34 <xarses> #link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
16:01:34 <xarses> Who's here?
16:01:35 <openstack> Meeting started Thu Feb 25 16:01:34 2016 UTC and is due to finish in 60 minutes.  The chair is xarses. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:36 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:38 <openstack> The meeting name has been set to 'fuel'
16:01:40 <openstack> Current chairs: xarses
16:01:43 <maximov_> hi
16:01:44 <mwhahaha> hi
16:01:45 <IvanBerezovskiy> hi
16:01:46 <warpc> hi
16:01:48 <monester> hi
16:01:48 <akislitsky_> hi
16:01:50 <mihgen> hi
16:01:54 <kszukielojc> hi
16:01:56 <vsakharov> hi
16:01:57 <degorenko> hi
16:02:02 <dpyzhov> hi
16:02:03 <aspiers> hi
16:02:14 <ashtokolov> hi
16:02:16 <pigmej> hi
16:02:16 <angdraug> o/
16:02:19 <xarses> #topic action items from last week
16:02:28 <xarses> ashtokolov will look into increased deployment time in smoke tests
16:02:29 <aglarendil> \o/\o/
16:02:37 <yottatsa> o\
16:02:41 <salmon_> hi
16:03:05 <ikalnitsky> o/
16:03:21 <igorbelikov> o/
16:03:29 <aglarendil> ashtokolov: is typing
16:03:32 <fzhadaev> hi
16:03:33 <aglarendil> please be patient
16:03:33 <xarses> =)
16:03:39 <aglarendil> ....
16:03:41 <ashtokolov> we discovered one issue with apache task https://review.openstack.org/282455
16:03:53 <kozhukalov> hi
16:04:01 <agrebennikov> hi there
16:04:42 <ashtokolov> it was a floating issue, fix was merged
16:04:57 <xarses> so did deployment time decrease?
16:05:03 <xarses> or are we still facing issues there?
16:05:42 <aglarendil> ....
16:05:49 <aglarendil> ashotokolov is typinh
16:05:51 <aglarendil> ....
16:06:13 <mihgen> .. by letf foot :P
16:06:22 <ashtokolov> xarses, deployment time decreased by 5-10%
16:06:37 <aglarendil> as we expected with 4-core cpus of CI nodes
16:06:43 <ashtokolov> sorry folks, slow wi-fi in the office
16:06:58 <angdraug> slower than you typing? :P
16:07:06 <aglarendil> ....
16:07:12 <aglarendil> ashtokolov is typing
16:07:14 <aglarendil> ....
16:07:18 <xarses> ok, moving
16:07:24 <xarses> ikalnitsky holser to follow up with dnikishov on the spec for non-root https://review.openstack.org/#/c/243340/
16:07:49 <ikalnitsky> we have reviewed the spec
16:07:58 <ikalnitsky> i think the main approach is established
16:08:07 <ikalnitsky> so i start merging patches to fuel-web
16:08:29 <xarses> thanks
16:08:41 <xarses> fzhadaev yottatsa to sync on NFV status and provide combined update
16:08:49 <fzhadaev> Done. And vsakharov will provide our combined update
16:08:55 <fzhadaev> :)
16:09:24 <xarses> thanks
16:09:25 <fzhadaev> it's in agenda
16:09:28 <xarses> #topic code review backlog status: http://bit.ly/1Kp8BzM (mihgen)
16:09:59 <mihgen> folks we lag behind
16:10:14 <mihgen> I won't be giving actions items, but please check the link and help to move this forward
16:11:14 <xarses> Yes, we want to keep up on our code review throughput
16:11:30 <xarses> thanks mihgen
16:11:46 <xarses> #topic Using multiple OpenStack versions https://review.openstack.org/#/c/281557/ (xarses)
16:12:03 <xarses> oh, we've scoped it down a bit since I wrote that =)
16:12:07 <xarses> I've been working to socialize https://review.openstack.org/#/c/281557/ so we can start versioning openstack tasks seperate of others. This led to needing to open https://review.openstack.org/#/c/284294/ (remove some of the ::openstack manifests) this also relates to the prior because some of the calls are inderected in ::openstack before making it to the puppet-openstack modules.
16:13:15 <xarses> questions?
16:14:09 <xarses> #topic feasibility of converging with upstream https://launchpad.net/openstack-resource-agents (aspiers)
16:14:15 <aspiers> hi
16:14:24 <aspiers> thanks for tolerating an outsider crash your meeting :)
16:14:34 <aspiers> I am the maintainer of this upstream projecct
16:14:36 <xarses> welcome
16:14:46 <aspiers> and I recently noticed that fuel has forked some of the OCF RAs
16:14:59 <aglarendil> holy guacamole, Adam! welcome!
16:15:01 <aspiers> I talked to bogdando and he suggested I raise the idea of reconvergence here
16:15:04 <aspiers> :)
16:15:17 <bogdando> hi
16:15:22 <aspiers> I think it could be a win-win situation for all
16:15:28 <aspiers> by combining efforts
16:15:31 <xarses> I'm for it, we have a bunch of stuff in here
16:15:38 <xarses> that is diverged
16:15:50 <aspiers> I am guessing the fork happened whilst the project was unmaintained and living in github.com/madkiss
16:15:51 <bogdando> and bunch of improvements :)
16:16:07 <bogdando> yes, few years ago
16:16:11 <aspiers> but since then I brought it into the openstack ecosystem and we have various vendors contributing now
16:16:11 <xarses> forgive me now knowing, what do you have for CI coverage?
16:16:32 <xarses> we already have the OCF installed as a RPM, so we could swap them
16:16:37 <aspiers> xarses: nothing right now but we have just started preliminary work on fixing that
16:16:49 <aspiers> e.g. https://launchpad.net/bugs/1508559
16:16:49 <openstack> Launchpad bug 1508559 in openstack-resource-agents "Needs bashate CI" [Wishlist,Confirmed]
16:16:49 <yottatsa> aglarendil is typing
16:16:56 <xarses> evntually, we'd want to vote, at least in regards to what we consume
16:17:26 <angdraug> aspiers: have you seen https://ci.fuel-infra.org/view/puppet-openstack/ ?
16:17:26 <xarses> we have a bunch of CI around beating the cluster
16:17:32 <aglarendil> oh, common, is there anyone using non-bash shell?
16:17:35 <bogdando> note, I have a PoC Travis CI for docker containers running a pacemaker cluster
16:17:43 <aspiers> angdraug: no I haven't
16:17:43 <angdraug> aglarendil: only all of Debian users :)
16:17:46 <bogdando> this may be used as the base for OCF under tests
16:17:49 <aspiers> bogdando: cool!
16:17:51 <bogdando> or suchlike
16:17:55 <aspiers> I think we definitely want unit tests too
16:18:11 <aglarendil> angdraug: the first thing you do 'dpkg-reconfigure dash'
16:18:11 <aspiers> although that would require mocking dependencies, and it's a pain with shell code
16:18:29 <aspiers> but anyway I don't mean to hijack your meeting with our future plans
16:18:41 <bogdando> example OCF testing job https://travis-ci.org/bogdando/rabbitmq-server/builds/109353708
16:18:46 <aspiers> just wanted to raise it and see if convergence potentially appeals to you guys
16:18:47 <bogdando> JFYI
16:19:06 <xarses> aspiers: lets prepare a ML or such, and find out who can work on this, and then we should maybe setup a meeting time to talk just about this
16:19:08 <bogdando> my vote is +1. Although we need specs submitted, both sides
16:19:08 <aspiers> since I think these RAs definitely have potential to be shared across many vendors
16:19:10 <angdraug> looks like everyone is excited about the prospect of reconvergence
16:19:41 <aspiers> xarses: makes sense
16:19:46 <xarses> aspiers: can I put an action on you to follow up on this?
16:19:47 <angdraug> bogdando: would you be our project's liaison with openstack-resource-agents?
16:19:51 <aspiers> xarses: sure
16:19:52 <aglarendil> I am +1 for convergence
16:20:07 <bogdando> angdraug, ok
16:20:28 <xarses> #action aspiers will create ML to find out who is interested in RA convergance and probably set up dedicated meeting for such
16:20:33 <xarses> ok moving?
16:20:37 <angdraug> yup
16:20:46 <aspiers> thanks!
16:20:57 <xarses> thanks for raising this aspiers
16:21:01 <xarses> #topic topics for design summit in Austin https://etherpad.openstack.org/p/fuel-austin-agenda (angdraug)
16:21:12 <angdraug> #link https://etherpad.openstack.org/p/fuel-austin-agenda
16:21:12 <angdraug> me and mihgen has added session leads and required participants to the proposed topics for Austin
16:21:12 <angdraug> please review and if you find your name on the list confirm that you can lead discussion of the topic
16:21:12 <angdraug> if you add another topic, please leave your name in brackets so that we don't have to guess who added it
16:21:15 <angdraug> if you see topics that are better served by online discussion or spec review, feel free to flag them
16:21:18 <angdraug> we will finalize the high-level agenda next week, so don't wait until the week before the summit to review this
16:21:21 <angdraug> thanks
16:22:20 <angdraug> moving?
16:22:41 <aglarendil> angdraug: do we have right to propose some changes?
16:22:46 <angdraug> of course
16:22:52 <vkramskikh> how to > confirm that you can lead discussion of the topic ?
16:23:08 <angdraug> vkramskikh: I think silent consent is enough
16:23:21 <angdraug> object if you see your name against something you don't know enough about
16:23:37 <angdraug> or if you think someone else should be there
16:24:23 <angdraug> aglarendil: what kind of changes do you have in mind?
16:24:46 <aglarendil> angdraug: finalizing HA reference architecture with power management and proper event-based control
16:25:23 <xarses> aglarendil: add a ~victim~ owner
16:25:31 <aglarendil> me!
16:25:37 <aglarendil> mi-mi-mi
16:26:10 <xarses> ok moving
16:26:17 <xarses> #topic Plugins v5 status (ikutukov)
16:26:29 <ikutukov> Plugins v5 features:
16:26:40 <ikutukov> - deployment tasks v2.0.0 is used as only task version
16:26:44 <ikutukov> ikalnitsky asked us to implement:
16:26:47 <ikutukov> - per-release configuration including deployment graph
16:26:50 <ikutukov> And request from our services:
16:26:54 <ikutukov> - configuration folders and custom paths support
16:26:57 <ikutukov> Spec review:
16:27:00 <ikutukov> https://review.openstack.org/#/c/271417/
16:27:48 <xarses> This came up form a conversation that I had with some one working on a plugin. The wanted to know when the v5 version and tags would be ready so that they can finalize the metadata for their 9.0 plugins
16:28:12 <mihgen> will we be able to make it before FF.. ?
16:28:14 <ikalnitsky> xarses: tags? you meant repo tag?
16:28:38 <xarses> well as of yesterday, 5.0 wasn't merged
16:28:44 <ikalnitsky> mihgen: i think only nailgun part must be ready before ff. fuel-plugin-builder has untied release cycle
16:28:55 <xarses> in fuel-plugins or rpm for fuel-plugin-builder
16:29:00 <ikalnitsky> xarses: yeah. i want to release current master on pypi
16:29:18 <ikalnitsky> i'm waiting for merging my patch to openstack-infra
16:29:30 <ikalnitsky> that pushes new rlease to pypi once tag is pushed
16:29:40 <xarses> ikalnitsky: also, I noticed we don't have recent tags or branches for 7.0 or 8.0
16:30:02 <ikalnitsky> xarses: that's because we have untied from Fuel release cycle
16:30:31 <xarses> but there are no tags for 4.0 then
16:30:38 <ikalnitsky> yes
16:30:44 <ikutukov> #ikalnitskiy its hard, but there are some chances to make nailgun support before SCF, some part of the FPB is on review but it's not possible to finish work on FPB before SCF
16:30:50 <ikalnitsky> i will push it once this patch is merged
16:30:56 <ikalnitsky> #link https://review.openstack.org/#/c/283683/
16:31:48 <xarses> wait, 4.0 version on fuel-plugins == v5 plugin support?
16:31:58 <ikalnitsky> nope
16:32:06 <ikalnitsky> 4.0 = v4 plugins
16:32:13 <ikalnitsky> make a release on pypi
16:32:18 <ikalnitsky> merge v5 to master
16:33:07 <xarses> ok, this is all confusing
16:33:33 <xarses> I will follow up after the meeting
16:33:39 <ikalnitsky> ok
16:33:44 <xarses> #topic move ceph/public to Fuel Storage by default https://review.openstack.org/#/c/284467/ (agrebennikov)
16:33:56 <agrebennikov> It happened on the number of customers where we had to do dirty hack and replace ceph/public and ceph/replication net assignments to fuel networks
16:34:03 <agrebennikov> огые нуыеуквфн ыфьу куйгуые
16:34:07 <agrebennikov> ooops))
16:34:16 <agrebennikov> just yesterday - same request one more time
16:34:24 <agrebennikov> is possible to do it with templates, but there is no reason to ever mix item with openstack management
16:34:32 <agrebennikov> usually customers have slow interfaces for public/mgmt and fast interfaces for storage. so lets place entire ceph traffic to storage and let the user to split ceph traffic with net templates when necessary
16:34:52 <angdraug> objections anyone?
16:35:08 <xarses> +1 from me
16:35:18 <agrebennikov> basically ceph doesn't even Require cluster network
16:35:43 <mihgen> do we have a bug for it.. ?
16:35:45 <agrebennikov> but xarses said it is impossible to test cases "have cluster"/"no cluster net"
16:35:50 <agrebennikov> we do
16:35:52 <angdraug> mihgen: linked from the commit
16:36:02 <mihgen> I'd get ceph folks to review..
16:36:22 <agrebennikov> ok
16:36:26 <angdraug> mihgen: please invite the right people to +1
16:36:32 <mihgen> I'll follow up with them
16:36:56 <xarses> thanks for raising this agrebennikov
16:37:04 <agrebennikov> np
16:37:16 <agrebennikov> thanks guys, leaving
16:37:20 <xarses> #topic UI Team status (vkramskikh)
16:37:26 <vkramskikh> Hi! Here is our status for 9.0 features:
16:37:26 <vkramskikh> 1) https://blueprints.launchpad.net/fuel/+spec/remove-vendor-code - the removal request has been merged; request to restore them in the downstream is still in progress - expected to be merged soon after restructuring the code.
16:37:26 <vkramskikh> 2) https://blueprints.launchpad.net/fuel/+spec/allow-choosing-nodes-for-provisioning-and-deployment - the first part (separate provisioning) was merged, separate deployment and choosing nodes are going to land soon.
16:37:26 <vkramskikh> 3) https://blueprints.launchpad.net/fuel/+spec/separate-fuel-ui-repo - separate test runner was merged, but still doesn't work in case of separate repo; still unsure if we could make it before FF.
16:37:29 <vkramskikh> 4) NFV stuff - implementation for node attributes (for Nova and DPDK CPU pinning) is close to be implemented and merged; other changes (topology representation and interface screen changes) still require working API before we can merge UI changes.
16:37:35 <vkramskikh> Questions?
16:39:06 <xarses> seems no, thanks for the update
16:39:07 <kozhukalov> >>> but still doesn't work in case of separate repo
16:39:16 <kozhukalov> i 'll check it later today
16:39:36 <kozhukalov> i believe nothing serious
16:39:56 <angdraug> thanks kozhukalov
16:40:00 <angdraug> moving on?
16:40:13 <xarses> #topic Bugfix team status (dpyzhov)
16:40:19 <dpyzhov> hi guys
16:40:31 <dpyzhov> we all good with 8.0 release, as you know
16:40:58 <dpyzhov> for high priority bugs we have constant number of bugs in python
16:41:09 <mihgen> angdraug: releasing?..
16:41:43 <dpyzhov> and we solving library bugs as they appear
16:41:58 <dpyzhov> but we have lack of python guys right now
16:42:05 <dpyzhov> and we have 100 medium priority bugs in python
16:42:13 <dpyzhov> and 3 weeks before SCF
16:42:28 <mihgen> :(
16:42:51 <dpyzhov> library guys are helping with python
16:43:09 <dpyzhov> but they have limited expertise and also they have their tasks
16:43:22 <angdraug> mihgen: yes on releasing 8.0
16:43:27 <angdraug> bookwar: ^
16:43:43 <dpyzhov> it doesn't look like we'll be able to get good progress with medium priority bugs in 9.0 and most of them will be moved to 10.0
16:44:32 <angdraug> we don't have much time to introduce new medium bugs, either...
16:44:54 <xarses> dpyzhov: it sounds like we need to prioritize them over an iteration in 10, since we will have a longer cycle
16:44:55 <dpyzhov> 2/3 of medium priority bugs were moved from 8.0 release
16:45:43 <angdraug> dpyzhov: do you mean 1/3 of medium bugs were fixed in 8.0, or that 1/3 of currently open medium bugs were introduced in 9.0?
16:45:55 <mihgen> folks there many other topics in agenda, time..
16:46:06 <xarses> lets try to work out how we can knock them down in 10, we don't have time for 9.0 either
16:46:07 <dpyzhov> 1/3 of currently open medium bugs were submitted after 8.0 SCF
16:46:27 <dpyzhov> that's all that I wanted to highlight
16:46:55 <xarses> #topic Fuel + Solar integration (pigmej)
16:47:06 <pigmej> Hey
16:47:11 <pigmej> As you may now we should integrate solar with fuel in 9.0. Integration in 9.0 will be very experimental and it will not affect fuel except: https://review.openstack.org/283600.
16:47:11 <pigmej> We will introduce 2 new packages (and some dependencies) in Centos7, these dependencies are already packaged and available in mos-master.
16:47:11 <pigmej> Predicted UX:
16:47:11 <pigmej> - user will need to install 2 rpm packages: solar and fuel2solar
16:47:13 <pigmej> - user will configure everything in fuel-web and then switch to solar CLI before clicking "deploy" button
16:47:16 <pigmej> 
16:47:19 <pigmej> Current plan is to:
16:47:22 <pigmej> 1. create fuel-spec about introducing these 2 additional packages (and requirements), this spec will not requre any QA activities,
16:47:25 <pigmej> 2. then should we describe everything again in openstack-dev ML
16:47:28 <pigmej> 3. describe this everything in fuel docs
16:47:31 <pigmej> 
16:47:35 <pigmej> 
16:47:37 <pigmej> Or maybe instead fuel-spec in 1 could we just create blueprint with pretty much the same content ?
16:49:11 <ashtokolov> pigmej do we need to land any patches to nailgun before FF to make it work?
16:49:15 <xarses> do we even need to introduce the packages onto the ISO? can we just leave them in the fuel mirror?
16:49:28 <kozhukalov> another q is should we put these two packages on the iso (i think we should)
16:49:32 <pigmej> ashtokolov: https://review.openstack.org/283600 this is only one required
16:49:33 <mihgen> if it's just about adding a couple of packages to the mirror, then I don't think we need a spec for it
16:49:34 <dshulyak> ashtokolov: one patch, that extends nailgun api
16:49:49 <dshulyak> ashtokolov: i believe same thing you was describing 2 months ago
16:49:58 <pigmej> solar package is already in mos-master, requirements are there also
16:50:14 <kozhukalov> xarses: by default we use local mirror (unfortunately)
16:50:33 <kozhukalov> so we'd better place these packages on iso
16:50:44 <xarses> kozhukalov: we have fuel centos mirror on the fuel-master
16:50:51 <ashtokolov> dshulyak you mean serialised graph and deployment info?
16:51:12 <xarses> even with deb, we still have the fuel-mirror in the repo list
16:51:38 <pigmej> for now we have just rpms
16:51:38 <xarses> anyway, we need to move
16:51:53 <xarses> thank pigmej
16:51:57 <xarses> #topic Telco Team Status + NFV (vsakharov)
16:52:02 <vsakharov> Hi all.
16:52:03 <vsakharov> For now, Telco team has three main activities for 9.0:
16:52:03 <vsakharov> 1) Support NFV features:
16:52:03 <vsakharov> 1.1) Huge pages [1]
16:52:03 <vsakharov> 1.2) NUMA/CPU pinning [2]
16:52:03 <kozhukalov> xarses: you mean let's leave this to a user to download these packages using fuel-mirror?
16:52:03 <vsakharov> 1.3) SR-IOV [3]
16:52:05 <dshulyak> ashtokolov: yes, but deployent info is already available using existing handlers, that patch adds is only for serialized graph
16:52:05 <vsakharov> 1.4) DPDK [4]
16:52:07 <vsakharov> All specs were merged. 10 patches merged, 17 - on review
16:52:09 <vsakharov> 2) Daemon Resource Allocation Control [5]
16:52:09 <dshulyak> sorry
16:52:11 <vsakharov> Spec is merged. 4 patches are on review.
16:52:13 <vsakharov> 3) Removing Mirantis-specific code from fuel code
16:52:15 <vsakharov> 3 patches are merged.
16:52:17 <vsakharov> [1] https://blueprints.launchpad.net/fuel/+spec/support-hugepages
16:52:19 <vsakharov> [2] https://blueprints.launchpad.net/fuel/+spec/support-numa-cpu-pinning
16:52:21 <vsakharov> [3] https://blueprints.launchpad.net/fuel/+spec/support-sriov
16:52:23 <vsakharov> [4] https://blueprints.launchpad.net/fuel/+spec/support-dpdk
16:52:25 <vsakharov> [5] https://blueprints.launchpad.net/fuel/+spec/cgroups
16:52:27 <vsakharov> Any questions?
16:52:57 <xarses> kozhukalov: yes, we don't need to include it in the release that way, its just packages sitting on the internet
16:53:20 <mihgen> pigmej: I think you'd at least need to raise this in ML, and then see if spec/whatever is needed..
16:53:29 <xarses> vsakharov: whats at risk for feature freeze?
16:54:00 <dklenov> DPDK with high risk
16:54:00 <pigmej> mihgen: I will post the same on ML then, and we will see what will happen.
16:54:13 <dklenov> all other fuel related - with medium
16:54:28 <dklenov> merging is going a bit slow :(
16:54:36 <yottatsa> xarses we're expecting to merge library and agent #link http://bit.ly/1oCR2Jt before FF
16:54:45 <xarses> #action pigmej will post on the ML with regards to solar packages merge
16:54:56 <mihgen> any creative ideas to metigate it / speed up review/merge?
16:55:09 <xarses> vsakharov: dkalleg yottatsa thanks
16:55:57 <xarses> #topic Network team status (alex_didenko)
16:56:10 <alex_didenko1> Our team is working on the following features.
16:56:10 <alex_didenko1> https://blueprints.launchpad.net/fuel/+spec/allow-any-vip - requires some changes in spec and design, working on them, patches are on review. Spec change and email to ML are in TODO. This feature looks good so far.
16:56:10 <alex_didenko1> https://blueprints.launchpad.net/fuel/+spec/support-sriov - Only library patches are in good shape, no patches merged in other projects. So this feature is in red state (risk of not landing till FF is above average)
16:56:10 <alex_didenko1> https://blueprints.launchpad.net/fuel/+spec/support-dpdk - Even library patches are not yet ready to be merged (but they are on review though). This one is red also (risk of not landing till FF is very hight).
16:56:22 <alex_didenko1> some more details on NFV :)
16:57:03 <alex_didenko1> Done
16:57:15 <yottatsa> yep, we're stuck with nailgun
16:57:42 <ikalnitsky> yottatsa: what's that?
16:58:26 <mihgen> there are 5 topics left. Should those be followed up over email, since we won't be able to discuss all of them now.. ?
16:58:27 <xarses> #topic Nonroot feature status (dnikishov
16:58:34 <dnikishov> hi
16:58:43 <wayward710> _ hi
16:59:01 <dnikishov> as ikalnitsky mentioned, there are few merged patches for fuel-web
16:59:08 <xarses> mihgen: probably
16:59:30 <dnikishov> the plan is to get non-vital commits merged first and coordinate the rest with infra
16:59:57 <mihgen> are you getting help for library patches?
17:00:19 <xarses> we are out of time guys
17:00:19 <dnikishov> yes, I've got some reviews
17:00:36 <xarses> please follow up on the remaining items on the ML
17:00:39 <ikalnitsky> here's the list of patches to be merged in first order and in second
17:00:41 <ikalnitsky> #link https://etherpad.openstack.org/p/nonroot-safe-merging
17:00:43 <tmcpeak> o/
17:00:49 <LHinds> hi *
17:00:56 <xarses> #endmeeting