16:00:58 <vkozhukalov> #startmeeting Fuel
16:00:59 <openstack> Meeting started Thu Jul  3 16:00:58 2014 UTC and is due to finish in 60 minutes.  The chair is vkozhukalov. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:00 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:03 <openstack> The meeting name has been set to 'fuel'
16:01:07 <vkozhukalov> #chair vkozhukalov
16:01:08 <openstack> Current chairs: vkozhukalov
16:01:18 <evgeniyl> Hi
16:01:22 <vkramskikh> hi
16:01:26 <vkozhukalov> #topic Greetings, announcements
16:01:40 <vkozhukalov> who is here?
16:01:59 <salmon_> o/
16:02:19 <brain461> hi there
16:02:56 <vkozhukalov> #topic bug squashing day results
16:03:17 <vkozhukalov> as usual agenda is here
16:03:22 <vkozhukalov> #link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
16:03:42 <vkozhukalov> angdraug around?
16:04:16 <angdraug> vkozhukalov: here
16:04:32 <angdraug> we didn't have bug squashing day this week
16:04:35 <vkozhukalov> can you share any details about squashing day?
16:04:49 <angdraug> results of normal day to day bug squashing are at the same place:
16:05:15 <angdraug> #link https://docs.google.com/a/mirantis.com/spreadsheets/d/10mUeRwOplnmoe_RFkrUSeVEw-__ZMU2nq23BOY-gzYs/edit#gid=66519680
16:05:22 <vkozhukalov> ok
16:05:30 <vkozhukalov> #topic 5.0.1 release status
16:06:49 <dpyzhov> We have several critical bugs with upgrades in 5.0.1. Most of them will be addressed today
16:07:34 <dpyzhov> this bug will not be fixed today. #link https://bugs.launchpad.net/fuel/+bug/1336350
16:07:36 <uvirtbot> Launchpad bug 1336350 in fuel/5.1.x "[Update] status bar do not show progress after update/rollback" [High,Confirmed]
16:08:14 <vkozhukalov> #link https://bugs.launchpad.net/fuel/+bug/1336350
16:08:34 <vkozhukalov> hash tag must be in the beginning of the line
16:09:01 <dpyzhov> also we have several other bugfixes on review, they will be merged tomorrow
16:09:17 <angdraug> the plan is to announce code freeze for 5.0.1 as soon as upgrades are ready
16:09:27 <dpyzhov> and we have ostf issues. plan is to merge fixes tomorrow
16:09:33 <dpyzhov> not tomorrow, today
16:09:50 <angdraug> dpyzhov: is #1336350 the only blocker that won't be fixed today?
16:10:31 <dpyzhov> angdraug: the only blocker in upgrades
16:10:45 <angdraug> #link https://launchpad.net/fuel/+milestone/5.0.1
16:11:07 <angdraug> the only other critical bug that I see there is #1308684
16:11:23 <angdraug> it has fixes on review already
16:11:52 <dpyzhov> we have broken master right now
16:12:04 <dpyzhov> so we can not test and backport fix
16:12:20 <dpyzhov> it will be backported tomorrow in the first half of the day
16:12:29 <dpyzhov> and we will create rc1 tomorrow
16:12:41 <angdraug> ok
16:12:56 <vkozhukalov> ok, moving?
16:13:03 <angdraug> yes
16:13:10 <vkozhukalov> #topic Feature freeze on 5.1
16:13:32 <vkozhukalov> again i believe dpyzhov has some info
16:13:50 <dpyzhov> We have one more week before feature freeze
16:14:04 <dpyzhov> In order to finish several features
16:14:29 <dpyzhov> But this mean that features should be merged no later then Monday
16:14:34 <vkozhukalov> great, everyone is glad
16:14:46 <dpyzhov> We don’t want to be in hurry next Thursday
16:15:01 <dpyzhov> Some of features will not be ready by Monday
16:15:10 <vkozhukalov> you mean not merged but on review, right?
16:15:31 <dpyzhov> vkozhukalov: just do not postpone till Thursday
16:15:44 <dpyzhov> As soon as possible
16:15:49 <vkozhukalov> dpyzhov: that is clear
16:16:03 <vkozhukalov> dpyzhov: one more week is enough
16:16:04 <dpyzhov> Yes, code on review on Monday is mandatory
16:16:42 <vkozhukalov> afaik you have detailed status for every feature
16:17:08 <vkozhukalov> which of them are risky?
16:17:26 <angdraug> ml2 is still at risk
16:17:43 <angdraug> it's on agenda for later
16:18:15 <dpyzhov> also lsi in on high risk
16:18:16 <vkozhukalov> ok, let's move on and ask details about ml2 a bit later
16:18:29 <vkozhukalov> #topic Feature statuses
16:18:30 <dpyzhov> and qemu update needs investigations
16:18:43 <vkozhukalov> #topic Install OpenStack from upstream
16:18:54 <brain461> hello everyone
16:18:58 <vkozhukalov> #link https://blueprints.launchpad.net/fuel/+spec/openstack-from-master
16:19:03 <brain461> code is merged into master already. as soon as public gerrit is setup and repos are created, feature will be available to all customers
16:19:04 <vkozhukalov> brain461: hello
16:19:48 <vkozhukalov> does it work? )
16:19:57 <brain461> yes
16:19:58 <vkozhukalov> great, that it is ready
16:20:15 <vkozhukalov> any other details? concerns?
16:20:17 <brain461> haven't tested deployments though
16:20:37 <brain461> none
16:20:57 <vkozhukalov> but you are going to, right?
16:21:13 <brain461> QA part is still not implemented
16:21:32 <brain461> I expect help from our qa team in that regard
16:21:37 <angdraug> QA/CI is in scope, right?
16:21:59 <brain461> yes, there will be tests for every component
16:22:06 <vkozhukalov> great
16:22:13 <vkozhukalov> moving
16:22:18 <angdraug> running Fuel CI on top of that is essential
16:22:33 <vkozhukalov> #topic ML2: blueprints status and implementation
16:22:56 <angdraug> xarses: please share your status
16:23:15 <xarses> ML2 from Upstream - Still work in progress, Ubuntu Single mode passes cluster building, Ubuntu HA is about to pass cluster building. Sill need to finish with new create networks (written/not tested) and plug in last few settings from nailgun to configure agents
16:23:15 <xarses> Packages where missing for CentOS
16:23:15 <xarses> We need to discuss better version of OVS if possible
16:23:15 <xarses> #link https://lists.launchpad.net/fuel-dev/msg01272.html
16:23:50 <aglarendil> I rearranged blueprints
16:24:13 <aglarendil> now
16:24:16 <aglarendil> #link https://blueprints.launchpad.net/fuel/+spec/neutron-ml2-plugin-in-fuel-51
16:24:20 <aglarendil> is targeted for 5-1
16:24:29 <aglarendil> and being implemented for 5.1
16:24:35 <angdraug> not a very good name for a blueprint
16:24:46 <aglarendil> #link https://blueprints.launchpad.net/fuel/+spec/ml2-neutron
16:24:52 <aglarendil> is now targeted to 6.0
16:25:00 <aglarendil> we achieved this agreement
16:25:10 <angdraug> what agreement?
16:25:11 <aglarendil> and this blueprint shows how it is gonna be in 5.1
16:25:13 <angdraug> link?
16:25:18 <xarses> what agreement?
16:25:27 <aglarendil> that if xarses approach does not work
16:25:36 <aglarendil> I mean the one with neutron upstream full merge
16:25:49 <aglarendil> then we start parallel implementation
16:25:54 <aglarendil> xenolog started it
16:26:01 <aglarendil> and this implementation differs a bit
16:26:05 <xarses> yes, but it still doesn't pass CI
16:26:36 <aglarendil> it is almost ready
16:26:50 <aglarendil> it will be merged tomorrow I hope
16:26:53 <angdraug> that's what xarses is saying above :)
16:27:32 <aglarendil> yep, but is much more complete than xarses approach
16:28:16 <angdraug> I don't know, it doesn't even have a spec in the BP
16:28:43 <aglarendil> that's why I created a BP
16:28:44 <xarses> If the approach was not complete then it should have been raised in the spec review, which still isn't approved
16:29:29 <angdraug> lets move on
16:29:33 <vkozhukalov> but, there is no spec on review, right?
16:29:37 <aglarendil> it is
16:29:48 <angdraug> there is for ml2-neutron
16:29:52 <aglarendil> i just posted a link
16:29:54 <angdraug> #link https://review.openstack.org/99807
16:29:58 <aglarendil> https://blueprints.launchpad.net/fuel/+spec/neutron-ml2-plugin-in-fuel-51
16:30:10 <angdraug> aglarendil: that's a link to BP, link to spec in the BP is not set
16:30:31 <aglarendil> it will be ready tomorrow
16:30:38 <aglarendil> I know guys, it is a bit messy
16:30:52 <aglarendil> sorry for that
16:31:05 <aglarendil> but this was our risk mitigation plan supported by mihgen
16:31:20 <aglarendil> in case we do not succeed with xarses approach
16:31:34 <angdraug> lets move on take it to the ML, IRC meeting is a wrong place for discussions like that
16:32:30 <vkozhukalov> ok, but we dont have any other items for this meeting
16:32:34 <aglarendil> i wrote about it. you did not respond
16:32:45 <vkozhukalov> #topic open discussion
16:33:29 <vkozhukalov> looks like nobody has questions or topics to discuss
16:33:32 <vkozhukalov> right?
16:33:51 <vkozhukalov> if so, let's close meeting and continue to work
16:34:00 <vkozhukalov> thanks everyone
16:34:13 <vkozhukalov> #endmeeting