16:01:00 <kozhukalov> #startmeeting Fuel
16:01:01 <openstack> Meeting started Thu Oct 30 16:01:00 2014 UTC and is due to finish in 60 minutes.  The chair is kozhukalov. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:02 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:04 <mihgen> hi
16:01:04 <openstack> The meeting name has been set to 'fuel'
16:01:11 <kozhukalov> #chair kozhukalov
16:01:12 <openstack> Current chairs: kozhukalov
16:01:15 <kozhukalov> who is here?
16:01:20 <kozhukalov> hi mihgen
16:01:22 <rvyalov> hi
16:01:29 <xarses> o/
16:01:34 <kozhukalov> agenda as usual
16:01:42 <kozhukalov> #link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
16:01:53 <kozhukalov> let's start
16:02:08 <kozhukalov> #topic Announcements (mihgen)
16:02:30 <mihgen> hi all, a few things to share
16:02:41 <sanek11> hi
16:02:50 <mihgen> first of all, we seem to be in a pretty good shape (better than last releases) shape for feature freeze
16:02:58 <stamak> hi
16:03:07 <mihgen> majority of features are in, and in green state
16:03:28 <mihgen> though we had to call to stop merging some of them due to technical preview
16:03:43 <mihgen> which we were able to prepare today.
16:04:03 <mihgen> community ISO has to be built today I believe, I'd love anyone from devops to confirm it here
16:04:28 <mihgen> due to we stopped merging the stuff, it sounded reasonable to extend FF deadline
16:04:59 <mihgen> I don't like it so much but there is no other way.. I hope it won't impact very much release schedule
16:05:00 <kozhukalov> bookwar: around?
16:05:04 <bookwar> yep
16:05:19 <kozhukalov> bookwar: will you confirm about community iso?
16:05:19 <mihgen> so it's Monday now, 3 Nov is the Feature Freeze (FF) date
16:05:29 <mihgen> bookwar: pls trigger new build
16:05:32 <bookwar> community builds work as usuall, 3 a.m. MSK
16:05:35 <bookwar> mihgen: ok
16:05:55 <mihgen> we actually need nede to come up with building community releases and giving them as links to download on our public wiki
16:06:05 <mihgen> as now it's only tags in branches
16:06:23 <mihgen> so we force folks to build ISOs themselves, which can be complcated sometimes
16:06:42 <mihgen> Ok, next thing
16:07:01 <mihgen> next week is gonna be OpenStack summit and many folks are gone for it
16:07:12 <mihgen> So I think we have to cancel the meeting next week
16:07:14 <mihgen> any objections?
16:07:20 <xarses> no
16:07:29 <kozhukalov> mihgen: no objections
16:07:48 <kozhukalov> are we planning to share kind of summit diary?
16:07:56 <mihgen> ok good
16:08:27 <kozhukalov> about what interesting is going on there and there
16:08:59 <kozhukalov> ok, mihgen, are you done wich announcements?
16:08:59 <mihgen> kozhukalov: I think we should go through sessions intersecting with Fuel in any way
16:09:14 <mihgen> and put it to the one place
16:09:44 <mihgen> I think I'm done, yeah, thanks
16:09:48 <kozhukalov> mihgen: sounds reasonable
16:09:53 <kozhukalov> mihgen: thanx
16:09:59 <kozhukalov> any questions?
16:10:09 <kozhukalov> moving on then
16:10:22 <kozhukalov> #topic Fuel-stats status report (akislitsky)
16:10:29 <akislitsky> Hi, all! We have statistics collecting included into the ISO. Sending, migration, analytics reports of statistics are tested. We have collector on https://collector.mirantis.com and analytics on https://product-stats.mirantis.com/. Access to collector is closed from our network after the tests. Access to the analytics web UI is allowed only from our network. Now we have issue with periodical migration data from collecto
16:10:29 <akislitsky> r to the analytics, but it should be fixed by devops team in short time. In other cases our stats collecting feature is launched for the commercial ISO (with feature_group: -mirantis).
16:11:39 <mihgen> akislitsky: thx
16:11:42 <mihgen> that's for mirantis
16:11:49 <mihgen> what's the status for community?
16:12:47 <akislitsky> code for sending community ISO statistics is in the ISO, but we need community VMs to be configured like VMs for commercial version
16:13:08 <mihgen> so it's question to devops now, right?
16:13:13 <akislitsky> yes
16:13:33 <mihgen> I talked to monester, and I believe we gonna have it in about a week or two
16:13:46 <mihgen> it's gonna be great to see who uses what configurations
16:14:11 <kozhukalov> akislitsky: thanx
16:14:13 <akislitsky> sounds good
16:14:29 <kozhukalov> akislitsky: are you done?
16:14:40 <akislitsky> yes
16:14:43 <kozhukalov> moving on
16:14:54 <kozhukalov> #topic authx (prmtl)
16:15:00 <prmtl> hi all
16:15:00 <prmtl> authx improvements had been successfully merged, everything went smooth, now they will be backported to 5.1
16:15:05 <kozhukalov> prmtl: hi
16:15:12 <prmtl> that's all
16:15:34 <kozhukalov> sounds great
16:15:55 <kozhukalov> any q?
16:16:22 <kozhukalov> #topic Image based provisioning (agordeev)
16:16:34 <kozhukalov> agordeev: around?
16:16:54 <kozhukalov> agordeev: can you share the status?
16:16:55 <agordeev> hi
16:17:09 <agordeev> Good news: I haven't heard negative feedback about centos from QA folks. Safely assumed that it works pretty good.
16:17:23 <agordeev> Ubuntu is now in "works for me" state. So It requires additional testing with the help of QA
16:17:36 <agordeev> that's all from me
16:17:42 <kozhukalov> great
16:18:02 <angdraug> was it tested with ceph?
16:18:03 <kozhukalov> we still have a couple patches to be merged
16:18:25 <kozhukalov> and the q is are we planning to include this feature by default?
16:18:26 <agordeev> angdraug: i'll will ask QA
16:18:43 <angdraug> ceph is the trickiest part of our provisioning
16:18:45 <kozhukalov> mihgen: can you answer?
16:18:48 <angdraug> so I think it should be covered
16:19:08 <asledzinskiy> angdraug: hi, we have case with ceph
16:19:25 <kozhukalov> asledzinskiy: does it work?
16:19:35 <asledzinskiy> and it worked on CentOS
16:19:42 <angdraug> excellent, thanks!
16:20:10 <angdraug> moving on?
16:20:20 <kozhukalov> right now we have something like "if experimental then enable image based provisioning"
16:20:27 <kozhukalov> is it correct?
16:20:39 <kozhukalov> or maybe we need to remove those if conditions
16:20:59 <kozhukalov> mihgen: around?
16:21:12 <kozhukalov> ok, let's discuss this a little bit later
16:21:15 <kozhukalov> moving on
16:21:28 <kozhukalov> #topic Diff upgrade (kozhukalov, skulanov)
16:21:43 <kozhukalov> here there are 3 patches on review
16:21:57 <kozhukalov> #link https://review.openstack.org/#/c/124734
16:22:12 <kozhukalov> #link https://review.openstack.org/#/c/131071
16:22:25 <kozhukalov> #link https://review.openstack.org/#/c/131153
16:22:52 <kozhukalov> please if anyone can help with review feel free to leave your +1
16:22:57 <kozhukalov> or maybe -1
16:23:30 <kozhukalov> we still need to create build jobs for these feature
16:23:47 <kozhukalov> I believe devops team is working on that
16:24:19 <kozhukalov> and we need QA cooperations
16:24:38 <kozhukalov> ok, that is it
16:24:45 <kozhukalov> any q?
16:24:58 <kozhukalov> moving on
16:25:09 <kozhukalov> #topic Ceph upgrade (angdraug)
16:25:16 <angdraug> #link https://bugs.launchpad.net/mos/+bug/1360352
16:25:16 <angdraug> we still have Ceph v0.80.4 in 5.1.1 and 6.0 repos
16:25:16 <angdraug> this version is buggy and absolutely has to be upgraded
16:25:16 <angdraug> v0.80.7 is already built by mos-linux, we must pull it to our repos now
16:25:16 <angdraug> we also need v0.67.11 for 5.0.x
16:25:16 <angdraug> also we are affected by bugs in v0.80.7 that were fixed in upstream git
16:25:17 <uvirtbot> Launchpad bug 1360352 in mos/5.1.x "Upgrade Ceph to latest Firefly version" [High,Triaged]
16:25:18 <angdraug> we have to be ready to pull yet another Ceph update from mos-linux as soon as its ready
16:25:20 <angdraug> so that we have enough time to test it before HCF
16:25:22 <angdraug> waiting a whole week like we are doing with v0.80.7 is unacceptable
16:25:45 <angdraug> rvyalov: ^
16:26:39 <kozhukalov> rvyalov: around?
16:27:00 <kozhukalov> rvyalov: could you please get a comment on that?
16:27:43 <angdraug> mihgen: please help us get ^^^ sorted offline
16:28:39 <kozhukalov> ok, looks like rvyalov and mihgen are unavailable now
16:28:49 <angdraug> yeah, I hope they read the logs
16:29:19 <angdraug> open discussion?
16:29:31 <kozhukalov> we have nothing more to discuss in our agenda
16:29:35 <kozhukalov> yep
16:29:49 <kozhukalov> #topic Open discussion
16:30:37 <angdraug> looks like everyone's too busy preparing for paris :)
16:30:59 <Tatyanka_Leontov> :)
16:31:01 <xarses> python 2.7 migration? Kilo is dropping py26 support. We need think about how we want to deal with moving from our old py26
16:31:27 <kozhukalov> xarses: great note
16:31:57 <bookwar> shouldn't it be the part of Ubuntu 14.04/CentOS 7/..etc migration?
16:32:03 <kozhukalov> that is one of the questions we need to redirect to mos team
16:32:04 <rvyalov> kozhukalov: I dont know, should ask the mos-linux team
16:32:06 <xarses> upgrading to 2.7 in centos 6.5 looks very painful. Moving to a newer master-node os will help
16:32:10 <angdraug> it should, depends on when we can have that
16:33:01 <angdraug> if we upgrade to centos7, might as well move master node to ubuntu
16:33:02 <xarses> bookwar: its part of it
16:33:34 <xarses> but we need to not leave the masternode behind since its running ironic and keystone now
16:33:53 <bookwar> we can run certain py27 tests on CI
16:33:58 <xarses> and pumphouse is already not supporting py26 so we have to do other things for it
16:34:12 <kozhukalov> xarses: master node does not run ironic
16:34:19 <kozhukalov> xarses: only keystone
16:34:36 <xarses> kozhukalov: ahh, I thought we had ironic for image provisioning
16:34:42 <angdraug> still, we will have to have py27 on master in 7.0
16:34:50 <angdraug> preferrably sooner
16:35:12 <xarses> angdraug: yes, sooner would be good
16:35:28 <kozhukalov> xarses: we just re-invented a wheel )
16:35:40 <angdraug> having both major openstack upgrade and major linux upgrade in the same release is going to be a nightmare
16:35:41 <xarses> yes but now it has legs
16:36:14 <kozhukalov> ok, this topic about migrating to py27 is pretty for ML not for a meeting
16:36:31 <xarses> I just wanted to start you thinking about it
16:36:59 <kozhukalov> xarses: could you please start a thread in ML
16:37:03 <xarses> ok
16:37:03 <kozhukalov> ?
16:37:16 <kozhukalov> xarses:  thanx
16:37:30 <kozhukalov> any other q, suggestions?
16:38:13 <kozhukalov> looks like we are done
16:38:23 <kozhukalov> let's close
16:38:31 <kozhukalov> thanx everyone
16:38:46 <kozhukalov> #endmeeting