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