Thursday, 2016-11-03

kongrakhmerov, ddeja, could you please review https://review.openstack.org/#/c/388590/? my colleague was hitting this on his trial for mistral (master branch)02:09
*** pawnesh has joined #openstack-mistral03:52
openstackgerritpawnesh kumar proposed openstack/python-mistralclient: Removed openstack/common/importutils.py  https://review.openstack.org/39307604:03
rakhmerovkong: done04:13
kongrakhmerov: thanks04:14
kongrakhmerov: how was the summit?04:14
pawneshCan we remove mistralclient/openstack/common/apiclient/client.py , As mistralclient has its own HTTP client (mistralclient/api/httpclient.py) ??04:22
kongpawnesh: hi, if that file is no longer used, yes, we can remove that04:23
pawneshkong: thanks04:24
rakhmerovpawnesh: yes, delete it04:29
rakhmerovkong: it was ok in general and pretty good for Mistral04:29
rakhmerov:)04:29
kongrakhmerov: any etherpad i can see for our priorities of next dev cycle04:30
kong04:30
rakhmerovkong: for you there won't be probably anything really new, but yes04:31
rakhmerovgive me a sec04:31
rakhmerovhttps://etherpad.openstack.org/p/mistral-barcelona-summit-topics-201604:31
kongrakhmerov: thanks, will take a look04:31
rakhmerovthe most important things are captured there04:31
rakhmerovoverall, it was a good productive discussion04:32
rakhmerovwe'll be fixing our OpenStack integration part (actions, keystone)04:32
rakhmerovit's important for the project face04:32
rakhmerovStackStorm actions will be possible to use with Mistral directly in the future04:33
rakhmerovwe'll make them compatible04:33
rakhmerovI think it's not even captured in the etherpad04:33
kongrakhmerov: how many people were involved in the design session?04:33
rakhmerovI think 13-1504:34
kongwow, awesome04:34
rakhmerovit was less than on the previous summit (in Austin we didn't have enough chairs, 7-8 were standing) but it's good anyway04:34
rakhmerovd0ugal was there too04:35
openstackgerritpawnesh kumar proposed openstack/python-mistralclient: Remove unused openstack/common/apiclient/client  https://review.openstack.org/39308404:35
kongcool04:36
rakhmerovkong: can you please look at these small patches: https://review.openstack.org/#/c/390938/ and https://review.openstack.org/#/c/391025/04:44
rakhmerovand this big one (important for me): https://review.openstack.org/#/c/390208/04:45
kongrakhmerov: sure, will do tonight or tomorrow morning04:51
rakhmerovok04:51
openstackgerritMerged openstack/mistral-lib: Updated from global requirements  https://review.openstack.org/39274204:54
*** hparekh has joined #openstack-mistral04:54
openstackgerritMerged openstack/mistral-dashboard: Updated from global requirements  https://review.openstack.org/39274104:55
openstackgerritMerged openstack/mistral-lib: Update .coveragerc after the removal of openstack directory  https://review.openstack.org/39007404:59
openstackgerritMerged openstack/python-mistralclient: Updated from global requirements  https://review.openstack.org/39282305:16
openstackgerritMerged openstack/python-mistralclient: Fix python35 job failures  https://review.openstack.org/39102505:21
openstackgerritMerged openstack/python-mistralclient: Removed openstack/common/importutils.py  https://review.openstack.org/39307605:44
openstackgerritMerged openstack/python-mistralclient: Adding files to .gitignore  https://review.openstack.org/39093805:44
*** openstackgerrit has quit IRC05:48
rakhmerovpawnesh: please rebase https://review.openstack.org/#/c/393084/05:48
*** openstackgerrit has joined #openstack-mistral05:48
openstackgerritMerged openstack/mistral: Get correct inbound tasks context for retry policy  https://review.openstack.org/38859005:55
pawneshrakhmerov: i am not able to rebase https://review.openstack.org/#/c/393084/ ; due to merge conflict06:02
rakhmerovyou can't do it in gerrit just by pressing a button but you can resolve the conflict and resend the patch06:03
rakhmerovI also call it "rebase"06:04
openstackgerritMerged openstack/mistral: Updated from global requirements  https://review.openstack.org/39274006:28
*** sharatss has joined #openstack-mistral06:57
openstackgerritHardik Parekh proposed openstack/python-mistralclient: Remove unused openstack/common/apiclient/client  https://review.openstack.org/39308407:19
d0ugalMorning07:25
*** jaosorior has joined #openstack-mistral07:28
hparekhd0ugal: Good Morning07:32
*** jtomasek_ has joined #openstack-mistral07:41
*** openstackgerrit has quit IRC07:48
*** openstackgerrit has joined #openstack-mistral07:48
d0ugalhuh, that __actions feature in environments is some black magic :)07:50
*** shardy has joined #openstack-mistral08:36
*** jpich has joined #openstack-mistral08:54
*** jtomasek_ is now known as jtomasek09:02
openstackgerritRenat Akhmerov proposed openstack/mistral: Fix DB API transaction()  https://review.openstack.org/39318709:32
*** tuan has joined #openstack-mistral09:33
tuanHi guys09:34
tuani am now looking for some references about implementing TOSCA with Mistral09:35
tuando we have any short summary/instruction about it09:35
tuan?09:35
tuanthanks in advanced09:35
*** jaosorior is now known as jaosorior_lunch09:41
kongtuan, for supporting tosca, you need to implement a plugin mechanism for workflow parsing in mistral09:42
kongbut i'm not sure, not farmilar with tosca09:43
rakhmerovtuan, kong: yeah, we just discussed it privately09:43
rakhmerovTOSCA is not related to Mistral directly09:44
rakhmerovit's just what we do at Nokia09:44
rakhmerovd0ugal: it is a black magic, yes ;)09:44
tuanyeap, since TOSCA is relevant for cloud app09:44
kongrakhmerov: yeah, i know, another orchestration template specification09:44
d0ugalrakhmerov: :) I only just learned about it when looking at the docs patch.09:44
tuanthat is why we decide to go forward with it09:44
rakhmerovit was supposed to be a very cool feature but I believe it's not even documented well09:44
*** jpich has quit IRC09:45
kongtuan: have you already used mistral?09:45
rakhmerovd0ugal: quick question about your comment on decorators09:45
d0ugalrakhmerov: sure09:45
kongor you just want to use mistral unless tosca is supported?09:45
rakhmerovd0ugal: I am not sure what redundant level I have :)09:46
rakhmerovI'm not too good at decorators probably09:46
rakhmerovsorry09:46
tuankong: yeap, we are directly working with it everyday09:46
d0ugalrakhmerov: np, let me write a quick example...09:47
rakhmerovso, I have too functions there, one takes 'func' which is the decorator09:47
tuani just wanna know that there is any case study out there about tosca and mistral09:47
rakhmerovand I return it09:47
rakhmerovok, sure09:47
*** jpich has joined #openstack-mistral09:49
d0ugalrakhmerov: http://paste.openstack.org/show/587731/09:54
d0ugalrakhmerov: so the first decorator must be called with @process1() - note the "()"09:54
d0ugalrakhmerov: The first approach is only needed if you want to pass args to the decorator itself09:54
d0ugalrakhmerov: so, really, the first one is a function that returns a decorator, the second one is just a decorator.09:55
d0ugal... I hope that makes sense :)09:55
tuanthat really makes sense dOugal:)09:56
d0ugal\o/09:56
tuanreally pythonic way:)09:57
kongd0ugal: if you want to pass arguments to decorator itself, shouldn't it be this way http://paste.openstack.org/show/587732/?09:58
d0ugalkong: Yup, that looks good09:59
kongyeah, it's the same way ...09:59
kong:-)09:59
d0ugalkong: You use @wraps which is better, that was my other comment on the review :-D09:59
d0ugalI skipped that in the example tho'09:59
konghah, don't know your context, just chime in09:59
d0ugal:)10:00
tuan:D, are you guys going to open a python class here.10:05
kongi still remember pepole were talking about 'if x is None' and 'if not x' in mailing list in 201310:06
rakhmerovd0ugal: reading..10:07
d0ugalkong: haha, I would have enjoyed that one :)10:07
rakhmerovd0ugal: yes, it makes sense10:12
rakhmerovok10:12
rakhmerovnow I need to understand about functools.wraps() :)10:13
rakhmerovd0ugal: ok, I have to admit that I don't understand why to use functools.wraps10:23
rakhmerovcan you explain pls?10:23
rakhmerovI removed the extra level like you said and it's look really concise now10:24
rakhmerovnot sure what this wraps() will give us10:24
kongrakhmerov: without wraps(), you function metadata will be changed10:24
konge.g. function name10:24
kongfunction name will be the decorator's name10:25
rakhmerovyes10:25
rakhmerovtrue10:25
rakhmerovis it the only reason to use it?10:26
rakhmerovor there's something else10:26
kongrakhmerov: i'm not sure, that's the only reason i know for using that10:26
rakhmerovok, I see now10:27
rakhmerovthat's why we pass the original function as a parameter10:27
rakhmerovit must be copying its metadata or something..10:27
kongrakhmerov: yes, according to python documentation, besides the function name, will also affect function docstring if not using it10:28
tuanit is nothing else just the wrapper of a function10:28
rakhmerovok, no problem10:28
rakhmerovI'll use it10:28
rakhmerovthanks for explanations10:29
tuanyou can check it on itnernet about its usage10:29
tuanbut one simple example like this10:29
tuanimagine if you need to call a function many times10:29
* kong will stop teaching and get some sleep10:29
tuan:D, good sleep Kong10:29
openstackgerritRenat Akhmerov proposed openstack/mistral: Run actions without Scheduer  https://review.openstack.org/39020810:29
kongtuan: cheers10:29
tuanthen you should check the result of that function10:30
tuanthat is why we should put that function into decorator10:30
tuaneach time you want to call it, jsut call decorator10:30
tuanthe decorator will take the function, runs it, returns the result of that function10:30
tuanthen you can get the result of that function to be parameter of other functions10:31
tuanit is the use case10:31
tuan:), hope it helps you more imaginable10:31
tuanactually, you can take a look into openstack source code, decorator is used every where10:32
rakhmerovtuan: thanks10:33
rakhmerovI have actually seen it many many times, I just didn't know why it was used10:33
tuanit will make your code shorter, cleaner10:33
tuanyou can see in the source code of OpenStack10:34
tuanyou will see a decorator will be used multiple times10:34
tuanwhen you use a decorator for a function10:34
tuanthe affect of it is what i explain above10:34
tuanimagine, if you want to call that function 100 times10:35
tuanto get it result to be another parameter of others10:35
tuanit will be messy10:35
tuanput that function under decorator10:35
tuando not worry, try to run some simple decorator10:36
tuanthen you will understand it10:36
rakhmerovtuan: appreciate it, thanks10:36
tuanit is not the hard thing, believe me, :)10:36
rakhmerovI got it10:36
rakhmerovthanks10:36
tuanmy pleasure :D10:36
d0ugalrakhmerov: functools.wraps just stops decorators obscuring the real function in tracebacks etc.10:38
d0ugalrakhmerov: that is my understanding at least10:38
d0ugalrakhmerov: but I see kong already said this :)10:39
rakhmerovok10:39
rakhmerovI sent another patchset10:39
rakhmerovhopefully it looks better :)10:39
openstackgerritRenat Akhmerov proposed openstack/mistral: Fix DB API transaction()  https://review.openstack.org/39318710:41
d0ugalrakhmerov: LGTM10:41
rakhmerovok, tests also passed10:41
openstackgerritpawnesh kumar proposed openstack/mistral: Add oslo.i18n module in mistral project  https://review.openstack.org/39323010:42
rakhmerov(dunno about tripleO gate though)10:42
d0ugalrakhmerov: we are having some CI issues at the moment, I'll take a look.10:43
*** dprince has joined #openstack-mistral11:16
*** AlexeyAbashkin has quit IRC11:30
*** AlexeyAbashkin has joined #openstack-mistral11:35
*** tuan has quit IRC11:39
*** jaosorior_lunch is now known as jaosorior11:44
rakhmerovddeja: can you look again at https://review.openstack.org/#/c/390208/ ?11:44
openstackgerritHardik Parekh proposed openstack/mistral: Added unit tests for workflow executions and task executions filtering  https://review.openstack.org/37241711:46
*** AlexeyAbashkin has quit IRC11:49
*** AlexeyAbashkin has joined #openstack-mistral11:50
*** hparekh has quit IRC11:52
ddejarakhmerov: looking12:16
ddejarakhmerov: +2 +W12:18
*** shardy is now known as shardy_lunch13:05
*** Kiall_ is now known as Kiall13:19
*** Alexey_Abashkin has joined #openstack-mistral13:27
*** AlexeyAbashkin has quit IRC13:30
*** bobh has joined #openstack-mistral14:10
*** shardy_lunch is now known as shardy14:13
*** jaosorior has quit IRC14:17
openstackgerritMerged openstack/mistral: Run actions without Scheduer  https://review.openstack.org/39020814:26
*** rrecio has joined #openstack-mistral14:42
*** bobh has quit IRC14:44
*** rrecio has quit IRC14:44
*** rrecio has joined #openstack-mistral14:45
*** d0ugal has quit IRC14:57
rakhmerovddeja: thanks!15:01
openstackgerritIstvan Imre proposed openstack/mistral: Handle region_name in openstack actions  https://review.openstack.org/38918315:12
*** d0ugal has joined #openstack-mistral15:13
*** jaosorior has joined #openstack-mistral15:17
*** bobh has joined #openstack-mistral15:23
*** d0ugal has quit IRC15:39
*** bobh_ has joined #openstack-mistral15:40
*** bobh has quit IRC15:43
*** jtomasek has quit IRC15:44
*** jaosorior has quit IRC15:54
*** rrecio_ has joined #openstack-mistral16:04
*** rrecio has quit IRC16:07
*** tuan has joined #openstack-mistral16:46
*** jtomasek has joined #openstack-mistral16:52
*** Alexey_Abashkin_ has joined #openstack-mistral16:56
*** Alexey_Abashkin has quit IRC16:59
*** tuan has quit IRC17:10
*** harlowja has quit IRC17:43
*** harlowja has joined #openstack-mistral17:46
*** dprince has quit IRC18:15
*** jpich has quit IRC18:37
*** dprince has joined #openstack-mistral18:41
*** shardy has quit IRC19:11
*** dprince has quit IRC20:26
*** gyee has joined #openstack-mistral20:32
*** harlowja has quit IRC21:56
*** bobh_ has quit IRC22:03
*** rrecio_ has quit IRC22:06
*** rrecio has joined #openstack-mistral22:06
*** bobh has joined #openstack-mistral22:07
*** rrecio has quit IRC22:09
*** bobh has quit IRC22:11
*** bobh has joined #openstack-mistral23:23
*** bobh has quit IRC23:25
*** bobh has joined #openstack-mistral23:28
*** bobh has quit IRC23:30
*** gyee has quit IRC23:49

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!