17:00:08 <sergmelikyan> #startmeeting murano
17:00:09 <openstack> Meeting started Tue Feb 10 17:00:08 2015 UTC and is due to finish in 60 minutes.  The chair is sergmelikyan. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:10 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:13 <openstack> The meeting name has been set to 'murano'
17:00:51 <sergmelikyan> Hi :)
17:00:58 <ruhe> o/
17:01:24 <katyafervent> o/
17:02:06 <gokrokve> o/
17:03:40 <RadekPospisil> o/
17:03:49 <sergmelikyan> #topic Action Items Review
17:03:55 <StanLagun> o/
17:04:28 <sergmelikyan> #1 katyafervent, research more about log/exception localization
17:04:50 <katyafervent> I sent an email with my research
17:05:02 <katyafervent> And created a blueprint https://blueprints.launchpad.net/murano/+spec/organize-translation
17:05:21 <katyafervent> So if no objections, we should implement it in kilo
17:05:45 <katyafervent> The conclusion is: debug log and exceptions are not translatable
17:06:10 <katyafervent> But other log levels need to be translated
17:07:15 <sergmelikyan> Ok, thank you
17:07:30 <sergmelikyan> #topic Open Discussion
17:07:56 <sergmelikyan> Today we had once again issues with DSVM job, it's failed due to changes in devstack :(
17:08:19 <ruhe> honestly, i've never understood the purpose of translated logs. but, i guess some people need them. so +1 for katyafervent's proposal
17:08:33 <henar> hi all
17:09:21 <sergmelikyan> ruhe, same with me... I am not sure that we will provide translations right away, but at least it is better to support
17:09:24 <pashkin> Hi
17:09:26 <sergmelikyan> Hi, henar!
17:09:58 <sergmelikyan> Returning to the issues with DSVM...
17:10:00 <sergmelikyan> They removed tempest requirements installation: https://github.com/openstack-dev/devstack/commit/220e6e73d8c998ed575fb99fe454a27c665a3a6a
17:10:05 <StanLagun> I don't understand it either. Why not postpone it until someone actually understand it or at least someone ask for it?
17:10:34 <sergmelikyan> StanLagun, we anyway need to migrate to i18n
17:11:15 <sergmelikyan> https://review.openstack.org/154490 <- fix for DSVM
17:11:57 <StanLagun> sergmelikyan: there are a lot of things that need to be done and 99% of them is more urgent than something nobody sees a need for
17:12:30 <StanLagun> so just leave it until a better day
17:14:28 <sergmelikyan> StanLagun, I don't agree, I don't thing that we need to drop everything and start implementing it, but code should be maintained constantly, and this is part of maintenance
17:17:14 <katyafervent> I have a couple of blueprint, that need to be discussed
17:17:28 <katyafervent> We need to define, should we track them or not
17:17:58 <katyafervent> https://blueprints.launchpad.net/murano/+spec/stop-deploy-during-the-deployment
17:19:10 <StanLagun> that is a bug that was solved long time ago
17:19:25 <sergmelikyan> StanLagun, we can stop deployment?
17:19:46 <katyafervent> but we don't have special button for that?
17:19:54 <StanLagun> With introduction of timeouts the only way for a deployment to last forever is to enter endless loop or deadlock
17:20:15 <StanLagun> so it is possible in theory but never happened in practice
17:20:30 <katyafervent> but there is no opportunity to stop the deployment at any moment
17:20:43 <katyafervent> the question is will we support it or this feature is not needed?
17:20:53 <StanLagun> and no? we cannot stop hanged deployment from outside, but workfloaw itself can stop it by throwing exception
17:21:06 <sergmelikyan> Yeah, right. Sorry, I meant that we probably need to update BP to define way how to stop deployment manually at any given point of time
17:21:35 <StanLagun> sergmelikyan: Does somebody know how to do it?
17:21:54 <katyafervent> this question should be asked later
17:22:19 <sergmelikyan> Checking DB for some specific flag, and throw exception to stop deployment?
17:22:26 <sergmelikyan> But Kate actually correct
17:22:30 <katyafervent> so let's track that, if we pick it for a milestone, we'll think how implement that
17:22:42 <StanLagun> this BP will be relevant if it will be accompanied with spec saying how to do this
17:22:48 <StanLagun> checking DB will not solve
17:22:49 <sergmelikyan> We can think about later, I don't think that we should assign this BP for nearest milestone
17:23:16 <katyafervent> The next is https://blueprints.launchpad.net/murano/+spec/simulated-execution-mode-murano-engine
17:23:20 <StanLagun> imagine endless loop in MuranoPL that hangs the only engine's thread and never switches
17:24:14 <sergmelikyan> This is really more like corner case
17:26:52 <katyafervent> Stan what do you think? should we track that blueprint?
17:28:03 <StanLagun> katyafervent: I was the one who asked for this BP in the first place
17:28:05 <StanLagun> so yes
17:29:29 <StanLagun> it is extremely useful but it is not completely clear how to achieve it. It requires some bright ideas
17:30:05 <katyafervent> Ok, so keep it, may be we find someone who will implement this :)
17:31:40 <katyafervent> https://blueprints.launchpad.net/murano/+spec/admin-rights-restriction
17:32:05 <katyafervent> On the one hand, admins can have rights to delete the whole tenant
17:33:03 <katyafervent> should admins be able to delete private packages from different tenants?
17:33:11 <StanLagun> only admins in "admin" tenant
17:34:05 <katyafervent> and is it more like a bug, or may be used as blueprint?
17:34:21 <StanLagun> there must be someone that able to do that. But it cannot be someone other that whole OpenStack installation admin (cloud operator)
17:35:18 <StanLagun> katyafervent: can you explain what do you mean there by "admin users"?
17:35:52 <StanLagun> I just don't know if tenant admins exist at all
17:35:55 <katyafervent> but we do not determine cloud operator in the code
17:36:03 <katyafervent> we only looking for admin in the context
17:36:13 <katyafervent> that's may be our problem
17:36:31 <StanLagun> what is a criteria for user beeing an admin?
17:36:34 <katyafervent> we can think more about it and describe it blueprint
17:39:01 <katyafervent> role assigned in keystone
17:47:13 <sergmelikyan> Looks like no other questions left?
17:50:03 <sergmelikyan> #endmeeting murano