16:00:09 <vkozhukalov> #startmeeting Fuel
16:00:10 <openstack> Meeting started Thu Jul 10 16:00:09 2014 UTC and is due to finish in 60 minutes.  The chair is vkozhukalov. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:13 <openstack> The meeting name has been set to 'fuel'
16:00:24 <vkozhukalov> hey everyone
16:00:27 <aglarendil> hey
16:00:29 <mihgen> hi
16:00:33 <ikalnitsky> o/
16:00:35 <AndreyDanin> hi
16:00:36 <xarses> hi doctor bob
16:00:39 <vkozhukalov> #topic Greetings, announcements
16:00:51 <evgeniyl> hi
16:00:52 <vkozhukalov> as usual agenda is here
16:00:57 <asledzinskiy> hi
16:01:01 <vkozhukalov> #link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
16:01:02 <brain461> hello
16:01:27 <alex_didenko> hi
16:01:30 <mihgen> Ok let me provide short status
16:01:33 <vkozhukalov> #topic feature freeze status
16:01:46 <vkozhukalov> #chair vkozhukalov
16:01:47 <openstack> Current chairs: vkozhukalov
16:01:51 <mihgen> Feature Freeze was moved by one week and it's planned for today
16:02:00 <mihgen> well it is still planned for today :)
16:02:12 <mihgen> as far as I can tell we are not in ideal state, but in pretty good one
16:02:34 <mihgen> first of all, I can say that Fuel CI now verifies patches correctly for ~10 hours already
16:02:59 <mihgen> for FF date, we will need to make a few exceptions
16:03:20 <mattymo> +1 for working CI. It's great.
16:03:27 <mihgen> Those which I'm aware of: ML2, Mellanox
16:03:39 <mihgen> will talk about it more later during the meeting
16:03:49 <vkozhukalov> mihgen: ok
16:03:53 <mihgen> let me know if we have anything else to request exceptions for
16:04:01 <mihgen> vkozhukalov: that's short update from me
16:04:02 <vkozhukalov> moving topic to 5.0.1?
16:04:04 <mihgen> yep
16:04:19 <vkozhukalov> #topic 5.0.1 release status
16:04:30 <angdraug> #link https://bugs.launchpad.net/fuel/+milestone/5.0.1
16:04:45 <angdraug> 5.0.1 is mostly ready for code freeze
16:04:59 <angdraug> we're still waiting for a few bugs:
16:05:05 <angdraug> https://bugs.launchpad.net/mos/+bug/856764
16:05:07 <uvirtbot> Launchpad bug 856764 in oslo.messaging "RabbitMQ connections lack heartbeat or TCP keepalives" [Critical,In progress]
16:05:15 <angdraug> https://bugs.launchpad.net/fuel/+bug/1319451
16:05:18 <uvirtbot> Launchpad bug 1319451 in fuel/5.1.x "AMQP Channel errors in orchestrator logs" [High,In progress]
16:05:20 <angdraug> https://bugs.launchpad.net/fuel/+bug/1339236
16:05:21 <uvirtbot> Launchpad bug 1339236 in fuel/5.1.x "DockerUpgrader: failed to upgrade: Failed to run services" [Medium,Confirmed]
16:05:34 <angdraug> mihgen: ^ is Medium priority, but you mentioned that it must be fixed, can you clarify?
16:05:58 <mihgen> 764 is painful thing, though it doesn't always break stuff
16:06:01 <angdraug> as you can see at the milestone link above, there's a couple High priority New bugs
16:06:18 <mihgen> evgeniyl: https://bugs.launchpad.net/fuel/+bug/1339236 doesn't look like Medium to me
16:06:21 <mihgen> it's rather critical
16:06:24 <angdraug> fix for 764 is in testing since a few hours ago, no?
16:06:39 <mihgen> as far as I understand it fails upgrade procedure pretty often
16:06:52 <angdraug> upped 236 to Critical
16:07:26 <evgeniyl> Yes, it has medium priority because it affects specific tarball
16:07:40 <mihgen> I'm making a call to wait fix for #link https://bugs.launchpad.net/mos/+bug/856764
16:07:41 <uvirtbot> Launchpad bug 856764 in oslo.messaging "RabbitMQ connections lack heartbeat or TCP keepalives" [Critical,In progress]
16:08:03 <mihgen> I'd like HA to be better. As far as I know fix is under testing now
16:08:17 <angdraug> anyone can update on https://bugs.launchpad.net/bugs/1338573 ?
16:08:18 <akasatkin> evgeniyl: reproduced on 112 tarball
16:08:18 <uvirtbot> Launchpad bug 1338573 in fuel/5.1.x "Incorrect status of progress bar on Ubuntu" [High,Confirmed]
16:08:34 <angdraug> and https://bugs.launchpad.net/bugs/1340237 ?
16:08:35 <uvirtbot> Launchpad bug 1340237 in fuel "Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install iptables-persistent=0.5.3ubuntu2' returned 100" [High,New]
16:08:41 <evgeniyl> akasatkin: could you please provide env?
16:08:41 <mihgen> aglarendil: also I'm wondering if #link https://bugs.launchpad.net/fuel/+bug/1323277 could be anyhow fixed in 5.0.1 ?
16:08:43 <uvirtbot> Launchpad bug 1323277 in fuel "vip__management recovered with error" [Critical,Confirmed]
16:08:51 <evgeniyl> akasatkin: I would like to check if it is the same issue
16:09:10 <mihgen> evgeniyl: akasatkin let's keep as critical then before we find out
16:09:10 <aglarendil> mihgen: 277 is related to rabbitmq ocf script
16:09:23 <aglarendil> there is no way to fix it in 5.0.1 completely
16:09:30 <mihgen> :(
16:09:31 <aglarendil> but oslo.messaging may help a lot
16:09:57 <mihgen> ok it must go to release notes then..
16:10:27 <akasatkin> evgeniyl: 172.18.194.24 : 5599
16:10:32 <mihgen> angdraug: I think #link https://bugs.launchpad.net/bugs/1338573 is not that important and we could ignore it for 5.0.1
16:10:34 <uvirtbot> Launchpad bug 1338573 in fuel/5.1.x "Incorrect status of progress bar on Ubuntu" [High,Confirmed]
16:10:44 <vkozhukalov> what is the expectation about date of 5.0.1?
16:11:05 <mihgen> vkozhukalov: July 15th
16:11:20 <angdraug> not sure abotu 573, a very in-your-face problem
16:11:27 <mihgen> it may change if we are stuck with 856764
16:11:35 <aglarendil> I faced 573 many times
16:11:41 <aglarendil> and facing it right now
16:11:58 <aglarendil> progress bar is hanging until the reload
16:12:05 <mihgen> vkramskikh: did you guys manage to reproduce the issue? ^^
16:12:42 <mihgen> let's move on folks, take this topic out of here unless angdraug has more info
16:12:54 <vkozhukalov> #topic Features
16:13:01 <mihgen> too many things to discuss still, sorry
16:13:06 <vkozhukalov> #topic Zabbix status
16:13:31 <vkramskikh> mihgen: we didn't unfortunately :(
16:13:38 <akislitsky> Zabbix is tested on custom ISO in HA and multi-node modes
16:13:49 <mihgen> vkramskikh: you may need real deployments
16:13:51 <akislitsky> now it is merged into master
16:13:57 <mihgen> akislitsky: all merged?
16:14:06 <akislitsky> mihgen, all
16:14:08 <vkozhukalov> great
16:14:09 <mihgen> excellent
16:14:16 <mihgen> any critical bugs you aware of ?
16:14:22 <vkozhukalov> #topic Install OpenStack from upstream
16:14:51 <vkozhukalov> brain461 around?
16:15:07 <brain461> yes, but there's still question to akislitsky
16:15:15 <akislitsky> i have seen problems with nova networks and may be zabbix specific errors will be found in QA cycle
16:15:41 <akislitsky> i guess nova will be fixed in library in short time
16:15:48 <mihgen> no worries if someone not replied, those can put "?" here to request for waiting
16:16:04 <mihgen> akislitsky: ok, thanks
16:16:16 <vkozhukalov> brain461: go ahead
16:16:20 <brain461> rpm building code is merged into master
16:16:37 <brain461> according to devops, public gerrit is setup, so this unblocks the whole migration process
16:16:47 <brain461> we prepared the repository with build dependencies for components from master
16:16:57 <brain461> we prepared specs that could be built against the current master for most of the openstack components, but some of them are still on review
16:17:26 <mihgen> brain461: very good. Do you have any architecture / specs / slides for the setup?
16:17:50 <mihgen> so we could get more info on how it's gonna be implemented and work all together
16:17:52 <brain461> tomorrow on demo I'll be demonstrating the build process
16:18:17 <brain461> specs are merged into fuel-specs, btw
16:18:58 <mihgen> #link http://docs-draft.openstack.org/68/101868/3/check/gate-fuel-specs-docs/74f9fd7/doc/build/html/specs/5.1/openstack-from-master.html ?
16:19:19 <mihgen> sorry I was on vacation and didn't have a chance to look into :) will do
16:19:25 <mihgen> ok brain461 thanks
16:19:31 <vkozhukalov> moving
16:19:33 <angdraug> spec looks very short (
16:19:35 <mihgen> no more questions from me
16:19:37 <vkozhukalov> thanks brain461
16:19:52 <vkozhukalov> #topic ML2
16:19:59 <mihgen> +1 to angdraug … expected to see some diagrams
16:20:06 <mihgen> will provide my feedback later
16:20:15 <mihgen> aglarendil: xarses you go folks
16:20:26 <aglarendil> so.
16:20:40 <aglarendil> we had a meeting today with xarses and mihgen
16:20:53 <mihgen> yep results are in openstack-dev mailing list
16:21:21 <aglarendil> and we decided to merge xenologs implementation right now
16:21:28 <aglarendil> to unblock other teams
16:21:41 <mihgen> is it merged or not yet?)
16:21:48 <angdraug> #link http://lists.openstack.org/pipermail/openstack-dev/2014-July/039851.html
16:21:49 <aglarendil> I am waiting for the final test result
16:21:54 <aglarendil> and we will do extensive tests for Andrew's request
16:22:03 <aglarendil> if it passes the test, we will rebase it and merge
16:22:16 <aglarendil> along with rebase of Mlnx and NSX features
16:22:28 <mihgen> I know that xenolog did some patches to xarses's request
16:22:32 <aglarendil> for this purpose we decided to extend FF a little bit for these particular features
16:22:34 <mihgen> while he was sleeping in PST
16:22:45 <aglarendil> yep, he posted some stuff into change requests
16:22:51 <aglarendil> but he is offline now
16:23:01 <aglarendil> so, the ball goes to xarses again
16:23:02 <mihgen> xarses: are you aware of that? what's the status?
16:23:32 <angdraug> he's already posted another patchset on top of xenolog's changes, so probably aware
16:23:43 <xarses> mihgen: yes, I've spoken with xenolog, the last changed failed due to missed coma, and its back up for testing
16:23:45 <mihgen> should be just minor fixes from xenolog, he did not have much time today..
16:23:53 <mihgen> ok
16:24:01 <xarses> I've almost finished rebuilding my test env with the 307 iso
16:24:11 <xarses> and will start retesting locally
16:24:19 <mihgen> so I hope it will be tested more or less by EOD on Monday MSK
16:24:41 <mihgen> and we will merge it after that, so extending FF for this ML2 implementation
16:24:53 <mihgen> any more stuff on this topic?
16:24:59 <xarses> I didn't see mail about test plan
16:25:07 <xarses> did I miss it?
16:25:12 <aglarendil> it's in ML2 blueprints thread
16:25:18 <xarses> ok
16:25:18 <aglarendil> on openstack-dev
16:25:29 <angdraug> I've posted link above
16:25:40 <mihgen> nurla: can we have test plan for ML2 ?
16:25:53 <mihgen> to test xarses implementation?
16:26:28 <nurla> mihgen: no, we actually should check regression
16:26:51 <mihgen> nurla: we need more than just regression I think. We need to play with params, should not use defaults
16:27:03 <mihgen> and then make sure all IP ranges, etc. propagated properly
16:27:12 <mihgen> regression may appear in random place
16:27:33 <mihgen> even for regression, we need a plan so we can all follow to test xarses ISO once it's ready
16:27:39 <mihgen> can you please prepare one for us?
16:28:38 <nurla> for xenolog patch i sure our checks that we already have more enough
16:29:13 <angdraug> moving on?
16:29:26 <vkozhukalov> moving
16:29:31 <mihgen> nurla: I'm not about xenolog patch, ok will follow up on what we need
16:29:32 <nurla> ok, for xarser iso we'll create testplan
16:29:36 <mihgen> vkozhukalov: let's move onn
16:29:37 <vkozhukalov> #topic VMware
16:29:42 <AndreyDanin> ?
16:30:01 <AndreyDanin> NSX+KVM
16:30:02 <AndreyDanin> blueprint #link https://blueprints.launchpad.net/fuel/+spec/neutron-nsx-plugin-integration
16:30:03 <AndreyDanin> fuel-web part #link https://review.openstack.org/#/c/105438/ has two +1 and ready to merge
16:30:03 <AndreyDanin> fuel-library part #link https://review.openstack.org/#/c/86329 has -1 related to ML2
16:30:24 <AndreyDanin> vCenter features
16:30:24 <AndreyDanin> blueprint #link https://blueprints.launchpad.net/fuel/+spec/vcenter-hv-full-scale-support
16:30:26 <AndreyDanin> VMDK support
16:30:27 <AndreyDanin> fuel-library part #link https://review.openstack.org/#/c/104942/ merged
16:30:29 <AndreyDanin> fuel-web part #link https://review.openstack.org/#/c/104944/ merged
16:30:30 <AndreyDanin> HA support #link https://review.openstack.org/#/c/104130/ merged
16:30:31 <AndreyDanin> multi cluster support
16:30:32 <AndreyDanin> fuel-library part #link https://review.openstack.org/#/c/104197/ has one +1 and -1 from CI
16:30:33 <AndreyDanin> fuel-web part #link https://review.openstack.org/#/c/104927/ merged
16:30:51 <angdraug> +100500 for preparing a paste in advance!
16:30:57 <mihgen> #link https://review.openstack.org/#/c/105438/ akasatkin, evgeniyl can we merge?
16:31:35 <mihgen> thanks AndreyDanin
16:31:40 <mihgen> how much is it all ready to go?
16:31:47 <mihgen> any tested by anyone?
16:32:09 <mihgen> As far as I know we merged a lot of VMWare stuff today once master was fixed
16:32:09 <AndreyDanin> we tested it  by hands
16:32:10 <akasatkin> mihgen: looks good. but didn't test it
16:32:46 <mihgen> AndreyDanin: -1 from CI in multi-cluster - should be on your side or we just need to retrigger
16:32:55 <mihgen> Fuel CI should show correct results today
16:33:05 <AndreyDanin> We have got 6 servers and going to setup a test lab.
16:33:30 <mihgen> so we need to decide what to do with FF for multi cluster support
16:33:43 <mihgen> how much time do we need to finish with merging this stuff?
16:33:49 <aglarendil> I would give it a chance
16:34:00 <aglarendil> until the end of week
16:34:10 <aglarendil> this should be some easy fix
16:34:24 <mihgen> aglarendil: ok.. what about https://review.openstack.org/#/c/86329 ?
16:34:40 <mihgen> how time will it need after ML2 is introduced?
16:35:01 <aglarendil> hmmmm... anyway as we are going to give xarses' ML2 a chance
16:35:06 <mihgen> aglarendil: how both things are isolated, i.e. how is it risky to merge for core features?
16:35:11 <aglarendil> let's give it to ML2 implementation
16:35:20 <aglarendil> also, NSX is isolated and should not affect master
16:35:23 <mihgen> aglarendil: but after xenolog's code, it should work, right?
16:35:32 <mihgen> so AndreyDanin can rely on xenolog's code for now?
16:35:32 <aglarendil> ML2+NSX will require a couple additional days
16:35:43 <mihgen> and then rebase? Or what's the plan?
16:35:55 <aglarendil> yep, changes for NSX +ML2 should be similar for xenolog's and xarses' code
16:35:58 <AndreyDanin> mihgen: I didn’t test it with xenolog code.
16:36:48 <xarses> aglarendil: if NSX+ML2 enters from /etc/astute.yaml quantum_settings L2 settings then there will not need to be any code change between the two
16:36:51 <mihgen> aglarendil: xarses If you guys see it's pretty well isolated, we could give an exception for these almost ready stuff up until next Th, but no later
16:37:21 <AndreyDanin> mihgen: I need day or two to rebase to check xenolog/xarses code, make fix and test it
16:37:32 <mihgen> I mean NSX + ML2 & multi cluster support
16:37:47 <aglarendil> anyway, we are waiting for MLNx guys until Thursday.
16:37:51 <aglarendil> so I would give it a try
16:38:30 <mihgen> it doesn't make a sense to make exception for all, then it would mean slipping the date. But a few isolated small things are fine
16:38:55 <aglarendil> I agree
16:38:59 <mihgen> xarses, angdraug: are you agree on NSX + ML2 & muleticluster ?
16:39:17 <angdraug> I agree
16:39:42 <xarses> yes
16:39:46 <aglarendil> we have the majority features to be merged in 24 hours, so, I would feel ok with simple isolated features to be slipeed a little bit
16:39:48 <mihgen> ok, cool. thanks. Let's move on
16:40:06 <vkozhukalov> seems like we are done on this topic
16:40:17 <vkozhukalov> #topic Mellanox
16:40:39 <vkozhukalov> AndreyDanin: do you have any info about this activity?
16:40:52 <vkozhukalov> if not let's pass this topic
16:40:54 <AndreyDanin> Are there any guys from Mellanox?
16:41:00 <vkozhukalov> and move on
16:41:19 <xarses> I was speaking with aviramb yesterday
16:41:24 <AndreyDanin> It seems I have nothing to share.
16:41:26 <aglarendil> I think Dmitry Ilyin can provide some update
16:41:28 <vkozhukalov> looks like there are no mellanox guys
16:41:32 <xarses> they will fix their entrypoint into ML2
16:41:42 <aglarendil> I'll call him
16:41:46 <mihgen> they are waiting also for qemu 2.0
16:41:51 <dilyin> yes, i'm here
16:42:03 <xarses> which will allow them to use either puppet module
16:42:05 <aglarendil> dilyin: you have just had a call with Mellanox guys
16:42:24 <aglarendil> dilyin: could you provide a short update on the status of Mellanox code ?
16:42:58 <mihgen> meanwhile angdraug what about documentation for upgrade 5.0 -> 5.0.1 ?
16:43:04 <mihgen> are you aware of the status on this?
16:43:19 <mihgen> dilyin: I assume you are typing meanwhile..
16:43:55 <mihgen> vkozhukalov: let's move on
16:44:01 <mihgen> we don't have much time
16:44:10 <vkozhukalov> #topic OpenStack patching
16:44:10 <angdraug> documentation for upgrade is in progress, there's a review out
16:44:11 <mihgen> folks be prepared in advance for staus
16:44:18 <mihgen> angdraug: ok thanks
16:44:21 <angdraug> #link https://review.openstack.org/105324
16:44:34 <angdraug> reviews are appreciated
16:44:42 <dilyin> the Puppet part of the code is mostly ready. at least I have refactored all bad styles and not it's passing our CI without mellanox part enabled. I have not tested deployment with mellanox enabled yet
16:45:10 <mihgen> dilyin: ok sound very good, thanks.
16:45:17 <mihgen> ikalnitsky: are you here for status on patching?
16:45:18 <vkozhukalov> ikalnitsky: around?
16:45:25 <ikalnitsky> yep, i'm here
16:45:32 <ikalnitsky> ok, it looks like openstack patching works fine. we have two known bugs and both are not critical, as for me.
16:45:38 <ikalnitsky> the first one is related to node status which doesn't marked as error when update fails
16:45:43 <ikalnitsky> #link https://bugs.launchpad.net/fuel/+bug/1332494
16:45:44 <uvirtbot> Launchpad bug 1332494 in fuel "[Updates] Nodes do not marked by error status when update fails" [Medium,Confirmed]
16:45:50 <ikalnitsky> the second is related to our openstack init scripts which in some cases may lead to the situation when update process hangs (i mentioned it in previous demo)
16:45:56 <ikalnitsky> #link https://bugs.launchpad.net/fuel/+bug/1333292
16:45:57 <uvirtbot> Launchpad bug 1333292 in fuel "nova-api hangs during openstack updating" [Critical,In progress]
16:46:00 <ikalnitsky> the fix is already done and has been tested by qa, but it still doesn't merged.
16:46:01 <mihgen> On Mellanox, there are a lot of things to do still, and in agreement FF is extended for them by next Th
16:46:17 <ikalnitsky> and that's it :)
16:46:29 <mihgen> ikalnitsky: very good
16:46:38 <mihgen> nurla: can you confirm QA side of it?
16:47:06 <mihgen> are there any publicly available test cases for this feature?
16:47:59 <ikalnitsky> mihgen: Tatiana Leontovich is responsible for testig this feature. Unfortunately, she is ooo today.
16:48:11 <vkozhukalov> #topic Sustaining features: galera, rabbitmq, pacemaker improvements, manifests merge
16:48:14 <nurla> nurla: i can confirm, we already have cases and check all important reviewa
16:48:26 <vkozhukalov> guys we have just several minutes
16:49:03 <vkozhukalov> aglarendil: you were going to give some details on that topic
16:49:13 <mihgen> nurla: so what about test cases?
16:49:20 <aglarendil> so, we finally merged ha related blueprints
16:49:26 <aglarendil> with rabbitmq and galera improvements
16:49:32 <aglarendil> they have some bugs
16:49:33 <mihgen> wait
16:49:37 <mihgen> is galera there?
16:49:46 <aglarendil> I meant galera ocf script
16:49:47 <mihgen> I thought we reverted it 
16:49:59 <mihgen> oh ok, so new package is not in master yet
16:50:06 <aglarendil> I am going to merge these modifications tomorrow
16:50:17 <aglarendil> with all the newer packages and xtrabackup and so on
16:50:33 <aglarendil> this will allow us to make deployment of controllers in parallel
16:50:34 <mihgen> aglarendil: what's the status on testing of it?
16:50:40 <aglarendil> which part?
16:50:44 <aglarendil> xtrabackup?
16:50:45 <mihgen> galera packages
16:50:50 <mihgen> and xtracackup
16:50:58 <aglarendil> we will see tomorrow, I tested it and it should work
16:51:07 <aglarendil> as soon as we modify configs correspondingly
16:51:15 <aglarendil> this is about galera
16:51:25 <mihgen> ok, thanks, it would be cool to see it master. Please note, if we don't merge it tomorrow - no way for 5.1 for it
16:51:32 <mihgen> no more exceptions on this
16:51:46 <mihgen> vkozhukalov: let's move on, a few things left still
16:51:47 <aglarendil> rabbitmq ocf script has some partitioning bugs, but after some poking it reassembles cluster just fine
16:52:00 <aglarendil> along with galera script we have a very resilient HA architecture
16:52:09 <aglarendil> I tested it just now and it works fine
16:52:17 <mihgen> aglarendil: it's great to hear that our HA finally gets right attention
16:52:24 <vkozhukalov> #topic access-control-master
16:52:24 <aglarendil> though, there are some bugs with memcache and some pacemaker improvements
16:52:25 <mihgen> and becomes better and better :)
16:52:50 <mihgen> sambork: you go
16:53:18 <sambork> We are on good way to finish all tasks according to blueprint stages I and II (http://docs-draft.openstack.org/29/96429/11/gate/gate-fuel-specs-docs/2807f30/doc/build/html/specs/5.1/access-control-master-node.html).  Still 7 patches waiting for merge but 4 of them have enought +1 . Only fake tests and update waiting for review https://review.openstack.org/#/q/status:open+branch:master+topic:bp/access-control-master-node,n,z .Tests are going
16:53:41 <mihgen> sambork: very good
16:53:55 <mihgen> out of those 4, all of them into fuel-library?
16:54:24 <mihgen> the plan from aglarendil was to merge ML2, and if it's all fine, then merge access control to fuel-library
16:54:25 <sambork> 3 of them are in fuel-lib one from fuel-main
16:54:50 <mihgen> mattymo: can you confirm we are in a good shape in fuel-library?
16:54:54 <mattymo> yes
16:54:55 <mattymo> We had a false report of a regression with setting a custom password, but I couldn't reproduce. The remainder all good ready to merge. The only holdbakc is we're not enabling auth by default. It's a matter of updating 2 lines in Fuel Library to turn it on.
16:55:10 <mattymo> It's all beautiful.
16:55:15 <mihgen> what about system tests?
16:55:22 <mihgen> unit? all ready for this feature?
16:55:25 <mattymo> Andrey Sledzinskiy said he was running thos etoday
16:55:33 <mattymo> we have no unit tests for puppet
16:55:33 <mihgen> I hope sys tests won't be broken after merge
16:55:41 <mattymo> I told him to run first before full merge
16:55:49 <mattymo> but nothing will be possibly broken until we enable real auth
16:56:01 <mihgen> nurla: are you aware of changes in sys test ?
16:56:06 <asledzinskiy> mihgen: I run only 'one_node_deploy' sys_test with enabled authorization and it passed
16:56:08 <vkozhukalov> 5 minutes
16:56:10 <mihgen> because of auths
16:56:19 <mihgen> asledzinskiy: oh that's cool
16:56:24 <asledzinskiy> now I'm checking ha deploys
16:56:24 <mihgen> perfect, thanks guys
16:56:27 <nurla> https://review.openstack.org/#/c/104131/
16:56:36 <vkozhukalov> #topic nailgun plugins
16:56:39 <mihgen> let's keep pushing to merge remaining patches
16:56:50 <meow-nofer> sup
16:57:08 <meow-nofer> plugins are under active reviewing process
16:57:28 <meow-nofer> the bad thing is we didn't merge new SQLAlchemy yet
16:57:37 <meow-nofer> and it is required for plugins to work
16:58:11 <mihgen> then sorry for 5.1..
16:58:25 <mihgen> will merge your part in master once it's reopened
16:58:30 <meow-nofer> but still, there are two requests, https://review.openstack.org/#/c/104608/ and https://review.openstack.org/#/c/97827/
16:58:33 <mihgen> too late for sqlalchemy update now
16:58:40 <meow-nofer> and they are both ready to merge
16:58:50 <vkozhukalov> #topic image based provisioning
16:58:54 <mihgen> but folks stuff meow-nofer is doing is extremely important
16:58:57 <vkozhukalov> it almost works
16:59:07 <vkozhukalov> we have 6 pull requests
16:59:15 <vkozhukalov> #link https://blueprints.launchpad.net/fuel/+spec/image-based-provisioning
16:59:24 <vkozhukalov> some of them +1
16:59:25 <mihgen> so let's put attention to that, and review thoroughly, especially in terms of design. It's gonna be example on how to do further plugins in nailgun
16:59:39 <vkozhukalov> and it does not break anything
16:59:50 <vkozhukalov> ending
16:59:53 <mihgen> vkozhukalov: then it looks like we can merge if it has enough reviews
16:59:58 <vkozhukalov> thanx everyone
16:59:59 <mihgen> thanks vkozhukalov
17:00:07 <vkozhukalov> #endmeeting