Monday, 2016-12-19

*** Qiming has joined #openstack-mistral01:54
Qimingmorning/evening01:54
Qimingany mistral cores online?01:55
kong_Qiming: afternoon :-)01:55
Qiminghi, kong_01:55
QimingI'm looking at mistral support from openstacksdk01:55
Qimingit is not there01:55
kong_yeah, as i expected :-)01:55
Qimingwe want in enabled from openstacksdk, so that people can interact with mistal without having to install its client01:56
Qimings/in/it01:56
Qimingwhen looking at the mistral code, it looks different from other services01:56
Qimingthe first thing is about version discovery01:57
Qimingaccording to the guideline from API-wg: http://git.openstack.org/cgit/openstack/api-wg/tree/guidelines/microversion_specification.rst#n14001:57
Qiminga service is supposed to return a {'versions': [...]} JSON01:57
Qimingand the 'link' key should be plural01:57
Qimingis it okay for me to try fix it?01:58
kong_Qiming: feel free to do that01:59
Qimingalright01:59
kong_you are always welcomed to fix anything01:59
Qimingjust want to ensure that I'm not working on something that team here already has a decision of NOT doing it, :)01:59
kong_the other thing i need to mention is mistral client doesn't support session, not sure it's another roadblock for you02:00
Qimingif we support mistral resources directly from openstacksdk, we won't depend on mistralclient02:00
kong_Qiming: that's great02:01
Qimingthe goal of the sdk is to "kill" all service client libraries02:01
Qimingso that the CLI can go to openstackclient, the library can go to openstacksdk02:01
Qiming:)02:01
kong_Qiming: just curious, what's the difference between oepnstacksdk and openstackclient?02:01
Qimingan ideal vision which may never come true02:01
kong_you already answered that02:01
kong_openstackclient will call openstacksdk, is that the roadmap of openstackclient team?02:02
kong_Qiming ^^02:02
Qimingyes, but openstackclient moved very fast02:03
Qimingfor most services, it is still calling their clients02:03
kong_ok02:03
kong_i see02:03
Qimingthere are some migration works recently, e.g. rebasing neutron resources onto sdk02:03
kong_the first step is to improve sdk, and if it's mature enough, you can convince openstackclient to use it02:04
Qimingyes02:04
kong_mature, i mean it contains most of openstack service resources02:04
Qimingright, that means a lot of resources to be modeled, :)02:04
kong_Qiming: sounds like a long way to go :-)02:05
Qimingyep02:05
Qimingand the right thing to do02:05
kong_Qiming: btw, what's the motivation of you doing that?02:06
kong_adding mistral support in openstacksdk?02:06
Qiminga user story of VM HA02:07
kong_Qiming: awesome02:07
Qimingyou know I'm working on senlin02:07
kong_haha,我知道02:07
Qimingso far we have failure detection and failure recovery implemented already02:07
Qiminga missing link is about recovery of user apps02:08
Qimingand we don't know whatelse we can do ...02:08
Qimingalong the recovery process, we want to insert a mistral workflow02:08
kong_yeah, mistral is good candidate for that job02:08
Qimingusers can define and manage their custom workflows and then tell us02:08
Qiming"when you are recovering my VMs in this cluster, please invoke this workflow when a VM is back to life"02:09
Qimingit is an extension to the builtin recovery process02:09
kong_which means, users should install mistral first, right?02:10
kong_sorry, the service provider02:10
Qimingyes, they have to install mistral to enable this feature02:10
kong_ok, in order to interact with mistral, you choose to use openstacksdk in senlin, rather than all kinds of clients of other opensatck services?02:11
Qimingyes, we interact with nova, keystone, neutron, ceilometer, heat via sdk02:12
kong_ok, fair enough02:12
Qimingand openstacksdk then becomes the single dependency for us02:12
Qimingthe management is drastically simplified02:12
Qimingwe don't need to chase the client version changes02:13
kong_sorry for the inconvenience brought by mistral, hah02:13
Qimingand..., in an ideal case, they ALL should be bead in near future02:13
Qimingtox -e p27 produced 13 errors ...02:15
kong_Qiming: sorry was distracted by internal stuff02:18
kong_Qiming: can you paste the error?02:18
kong_it shouldn't be that case since py27 jenkins job is green :-)02:19
QimingFAIL: mistral.tests.unit.api.test_cors_middleware.TestCORSMiddleware.test_invalid_cors_get_request02:21
QimingFile "mistral/tests/unit/engine/test_cron_trigger.py", line 112, in test_workflow_without_auth02:23
Qiming    self.assertEqual(1, len(next_triggers))02:23
Qimingtesttools.matchers._impl.MismatchError: 1 != 002:23
QimingTraceback (most recent call last):02:23
Qiming  File "mistral/tests/unit/services/test_trigger_service.py", line 202, in test_oneshot_trigger_create02:23
Qiming    trigger.next_execution_time02:23
Qimingtesttools.matchers._impl.MismatchError: !=:02:23
Qimingreference = datetime.datetime(4242, 12, 25, 13, 37)02:23
Qimingactual    = datetime.datetime(4242, 12, 25, 18, 37)02:23
kong_Qiming: http://paste.openstack.org/ is your friend02:25
Qimingit is too big, :)02:26
kong_hmm...you can run it again to try your luck02:27
Qimingtrying02:27
Qimingso ... I have to get mistral installed and configured to run unit tests?02:27
QimingI'm not familar with pecan02:27
kong_i don't thing so, it should work only if you git clone mistral repo02:28
*** catintheroof has quit IRC02:28
Qimingokay, will keep trying02:29
Qimingcurrent summary:02:29
QimingRan 838 (-3) tests in 242.164s (+0.685s)02:29
QimingFAILED (id=1, failures=13, skips=13)02:29
*** catintheroof has joined #openstack-mistral02:30
*** catintheroof has quit IRC02:34
openstackgerritQiming Teng proposed openstack/mistral: Fix configuration generator  https://review.openstack.org/41225602:47
*** FL1SK has quit IRC03:00
*** FL1SK has joined #openstack-mistral03:01
*** sharatss has quit IRC03:16
*** sharatss has joined #openstack-mistral03:16
*** sharatss has quit IRC03:21
*** sharatss has joined #openstack-mistral03:22
openstackgerritRenat Akhmerov proposed openstack/mistral: Exclude .tox folder from coverage report  https://review.openstack.org/41113703:33
kong_Qiming: sorry, was distracted by some internal stuff03:52
kong_Qiming: i ran the tox on my dev env, all passed03:52
kong_Qiming: http://paste.openstack.org/show/592751/03:53
kong_Qiming: I have to head home now, if you have any other questions, please leave message in this channel03:54
* kong_ is way03:54
Qimingthanks, kong_, will do04:38
*** hparekh has joined #openstack-mistral05:06
openstackgerritQiming Teng proposed openstack/mistral: Fix docs in README.rst  https://review.openstack.org/41228405:11
openstackgerritMerged openstack/mistral-extra: Add clone vm example  https://review.openstack.org/39684005:13
*** jaosorior has joined #openstack-mistral06:06
*** pkoniszewski has left #openstack-mistral06:56
*** ist has joined #openstack-mistral06:56
*** sharatss has quit IRC07:24
*** sharatss has joined #openstack-mistral07:25
openstackgerritMerged openstack/mistral: Updated from global requirements  https://review.openstack.org/41213707:36
*** jaosorior has quit IRC07:58
openstackgerritRenat Akhmerov proposed openstack/mistral: Fix 'with-items' task completion condition  https://review.openstack.org/41234107:59
*** shardy has joined #openstack-mistral08:02
openstackgerritMerged openstack/mistral: Add more tests to mistral rally  https://review.openstack.org/40870908:13
openstackgerritQiming Teng proposed openstack/mistral: Fix docs in README.rst  https://review.openstack.org/41228408:16
rakhmerovddeja, d0ugal, hparekh: guys, can you pleaaase review my 'with-items' patches?08:23
rakhmerovneed them badly08:23
hparekhok sure08:24
*** jaosorior has joined #openstack-mistral08:24
ddejarakhmerov: yup, sure thing08:28
rakhmerov:)08:28
rakhmerovthx08:28
rakhmerovddeja: btw, oslo team fixe the breakage (https://review.openstack.org/#/c/411555/1/global-requirements.txt)08:31
rakhmerovbut they didn't send a patch to make a release08:31
rakhmerovalthough I don't like the fix08:31
rakhmerovthey again simply specified 4.0.208:31
rakhmerovwhy can't they use a range? Do you know?08:32
rakhmerovkombu 4.0.3 will break us again08:32
*** sharatss has quit IRC08:33
*** sharatss has joined #openstack-mistral08:34
*** ^Gal^ has joined #openstack-mistral08:45
*** jaosorior has quit IRC08:45
*** jaosorior has joined #openstack-mistral08:46
*** tuan_ has joined #openstack-mistral08:47
tuan_Hi guys08:47
tuan_hopefully there is someone online since Christmas is coming08:47
tuan_:)08:47
*** jpich has joined #openstack-mistral08:50
tuan_d0ugal: Hi ddeja, sorry to disturb you again08:54
tuan_i would like to know that do we have any benchmark for performance of mistral when running actions08:54
tuan_how much rams, cpus, etc. (i mean resources) needed for running actions in mistral?08:54
ddejarakhmerov: I'm not sure... maybe they hope that next version would be OK08:56
ddejawe may try to add it to our requirements08:56
ddejabut I'm not sure if it's good idea08:56
ddejatuan_: Hi08:56
rakhmerov:))08:57
*** jtomasek has joined #openstack-mistral08:57
ddejatuan_: There is no such mechanism08:57
tuan_hi ddeja08:57
rakhmerovddeja: yeah08:57
ddejarakhmerov: or, on the other hand, we may add the package that is missing for kombu to our requirements08:57
tuan_in our environment, it seems that mistral running with quite pretty much resources08:58
tuan_but i do not think it is because of mistral itself08:58
rakhmerovtuan_: what version of Mistral?08:59
rakhmerovfrom master?08:59
tuan_liberty08:59
rakhmerovddeja: I guess there should be a patch soon added by a bot to update our requirements08:59
rakhmerovI wonder why we still don't have it08:59
rakhmerovtuan_: :)) can you switch to a newer version09:01
ddejarakhmerov: there must be next release of oslo to pip, so we can have it09:02
rakhmerovsince then we improved it by orders of magnitude09:02
tuan_let's me check again about the version, i am not sure09:02
tuan_:D09:02
rakhmerovok09:02
tuan_but why liberty has this problem?09:02
rakhmerovmany reasons09:02
rakhmerovwe did a huge number of optimizations since then09:02
tuan_OK, give me a sec09:03
rakhmerovddeja: yes, right09:03
rakhmeroveven if it's fixed in global requirements it needs to be fixed and released in oslo09:03
rakhmerovI wrote it to their channel09:04
ddejarakhmerov: BTW, I'm not sure if I'll be able to participate in todays meeting09:04
d0ugalliberty is really old for Mistral :)09:04
rakhmerovbut seems like there's still a weekend for most of them09:04
rakhmerovddeja: that's ok09:04
ddejaI have some kind of xmas party with my high school class mates :)09:04
rakhmerovxmas ?09:04
rakhmerovwhat's that?09:04
rakhmerovooh, I see09:05
rakhmerovChristmas09:05
ddejayup ;)09:05
rakhmerovsure, np09:05
rakhmerovI actually don't believe we'll gather a bunch of people during the next 2-3 weeks )09:05
ddejaI can try to jump using my phone at the begginign09:05
rakhmerovok, but don't worry about it09:06
rakhmerovenjoy your party man :)09:06
ddejaoh, and also you will have the Christmas on the beggining of January in Russia, am I right?09:06
ddejainstead of end of December09:07
rakhmerovyeah09:07
rakhmerovJan 7th09:07
rakhmerovbut usually Christmas is not so greatly celebrated as NY in Russia09:07
rakhmerovit's kind of quite religios holiday09:07
ddejarakhmerov: Oh, I see09:07
rakhmerovyes09:07
rakhmerovmany simply forget about it at all :)09:08
rakhmerovbut New Year is a big thing here09:08
ddejawell, In Poland we got both 25 and 26 of December free days09:08
rakhmeroveveryone is drunk :)09:08
rakhmerov:)09:08
ddejaand a lot of people get vacation till new year ;)09:08
rakhmerovooh, by the way09:09
ddejabut the main "focus" is on Cristmas itself09:09
ddejarakhmerov: hm?09:09
rakhmerovddeja, d0ugal, hparekh, kong_ and others: I'll be mostly unavailable from Dec 31 till Jan 9th09:09
d0ugalI'll be unavailable from 22nd until the 4th :)09:10
rakhmerovevery year we have long holidays in Russia in the beginning of January09:10
rakhmerov8-9 days09:10
d0ugalNice!09:10
rakhmerovit is!09:10
rakhmerov:)09:10
ddejaI'll be less available starting 24 of December up to, hmm, 2 of January09:10
rakhmerovddeja, d0ugal: ok, guys, having that said :)09:11
rakhmerovI wanna ask you to review patches :)09:11
ddejarakhmerov: sure, as always ;)09:11
rakhmerovbefore you go on holidays09:11
rakhmerov:)09:11
d0ugalwhat ddeja said :)09:11
ddejaI'll look on the with-items today, but probably it would be my afternoon (in 2-3 ours)09:11
rakhmerovnp09:12
tuan_sorry guys09:12
tuan_it is 3.0.0 rc209:12
rakhmerovthis one is specifically important: https://review.openstack.org/#/c/412341/09:12
rakhmerovdue to it the combination of 'retry' and 'with-items' simply didn't work09:12
d0ugaltuan_: so Liberty, I think?09:12
tuan_damm it, it took me time sicne we use it in virtualenv09:12
tuan_no no09:12
tuan_3.0.009:12
tuan_it was released on Oct, 201609:13
rakhmerovnewton09:13
tuan_yeah09:13
tuan_newton09:13
d0ugalright, sorry09:13
rakhmerovok, why do you think it uses too much resources?09:13
* d0ugal is still waking up. I'll remember how counting works soon.09:13
rakhmerovcan you pls provide more details?09:13
rakhmerovsome reports maybe etc.09:13
rakhmerovmonitoring info09:13
tuan_i do not think the resouces it takes is quite much09:14
tuan_since we had problem of resources leak09:14
tuan_and after checking, what i saw is that the most consumable process is mistral09:14
rakhmerovtuan_: so you are not sure atm that exactly Mistral is guilty? :)09:14
rakhmerovhow consumable?09:15
tuan_i just want to know some more info about mistral in consuming resources09:15
tuan_yeap09:15
tuan_it is around 20% RAM09:15
rakhmerovI mean what amount of memory may be?09:15
rakhmerovwhat is the approximate value? In megabytes?09:15
tuan_1GB around :D, haha09:15
rakhmerovok, and what do you run on Mistral?09:16
tuan_woa, so many actions including so many components09:16
tuan_that is why i think it may depend on the type of actions i run09:16
rakhmerovtuan_: it might not be a memory actively used all the time. It may be a peak value that Mistral used on peak loads09:16
tuan_but mistral architect itself09:17
tuan_ah ha09:17
tuan_interesting point09:17
rakhmerovpeak memory usually gets freed when memory is not enough for other processes09:17
rakhmerovor over time09:17
rakhmerovby GC09:17
rakhmerovyeah09:17
rakhmerovand yes, it certainly depends on specific actions you run09:18
tuan_yeap, and peak memory happens in mistral at the very beginning of loading actions09:19
tuan_?09:19
*** jtomasek has quit IRC09:19
rakhmerovyes, and when you run some heavy workflows09:20
tuan_but what about this case:09:21
tuan_when mistral loads workloads, the memory is not sufficient for peak memory then it needs the swap in this case09:21
tuan_then it frees memory but swap is not09:21
tuan_then i wander that do we have some mechanism or based on experiences about how much RAM we should provide for running mistral09:22
tuan_to advoid this case09:23
tuan_for instance, in porduction what i saw that the controller node is around 32GB09:23
tuan_of course based on experiments and experiences09:23
tuan_otherwise we do not have any benchmark to state that09:24
d0ugaltuan_: it sounds like you are using tripleo?09:24
tuan_nope09:25
d0ugaloh, nevermind then :)09:26
openstackgerritSharat Sharma proposed openstack/mistral-dashboard: Testing fix for dashboard docs-gate  https://review.openstack.org/41236209:26
tuan_may be later on we will test with tripleO09:26
tuan_but we deploy mistral in a VM running on top of openstack09:27
tuan_:(09:27
d0ugaltuan_: I just guessed beause you said 32gb and controller - that is what we recommend :)09:27
d0ugaltuan_: aha, I see09:27
d0ugaltuan_: anyway, ignore that bit.09:27
d0ugaltuan_: I think it is probably a hard question to answer, because it depends how heavily your Mistral is used.09:27
tuan_yeah, i think so and i do not believe on that it is because of mistral architect09:28
tuan_since we jsut have 4GB for RAM of vm where mistral is running09:28
tuan_that sounds stupid09:28
tuan_:(09:28
d0ugaltuan_: I can tell you how much my Mistral is using if you can wait about 30 mins09:29
tuan_4GB is just for OS of 14.04 of Ubuntu, how does it fit with other processes like mistral when it loads actions09:29
tuan_well, after 30mins, it still uses around 20GB09:29
d0ugalYou should only load actions when you first start?09:29
tuan_20% RAM09:29
tuan_sorry09:29
d0ugalhaha, 20gb would be bad :-D09:30
tuan_yeah :D09:30
tuan_well, you know i am not the person who did this experiment09:30
d0ugalright09:30
tuan_but i am now the man who have to dig into this case to find out what happens09:30
d0ugalactions only need to be loaded when you first install Mistral or when you add a new custom action.09:31
tuan_and the guy who did it this spawned a vm with 4GB of RAM09:31
*** Ravikiran_K has joined #openstack-mistral09:31
tuan_yeah, that is right09:31
tuan_you can imagine like that09:31
tuan_after spawning a vm with mistral installed09:31
tuan_i let it run in couple of hours09:32
hparekhrakhmerov: I will be unavailable from 22nd DEC to 1st of JAN09:32
tuan_then mistral daemon still running with 20% RAM09:32
rakhmerovhparekh: ok, thanks for letting us know09:32
tuan_free memory is about 1GB over 4GB09:32
tuan_but SWAP is full09:32
openstackgerritSharat Sharma proposed openstack/mistral-dashboard: Fix docs-gate for mistral-dashboard  https://review.openstack.org/41236209:33
d0ugaltuan_: interesting, that does sound bad :)09:33
tuan_it seems like: it may happen that mistral use peak memory for loading actions from very beginning of spawning vm09:33
tuan_that peak memory needs swap too09:33
tuan_and then it frees out the memory09:33
tuan_that is the only case what i can see09:33
tuan_:(09:33
tuan_so that 4GB of flavor is stupid09:34
d0ugallol09:34
sharatssrakhmerov: d0ugal finally above patch fixes the docs gate09:34
d0ugalsharatss: great.09:34
tuan_d0ugal: btw, thank you :D09:35
tuan_i will ask that guy to test it again09:35
tuan_merry christmas to you guys and happy new year09:35
d0ugaltuan_: no problem, I am just waiting for my openstack to install and then I'll take a look at this09:35
tuan_haha09:35
tuan_yeap09:35
tuan_:)09:35
rakhmerovsharatss: great!09:36
rakhmerovtuan_: I doubt that the problem is swap09:37
rakhmerovI really do09:37
rakhmerovtuan_: I started Mistral on my local machine now w/o running anything yet, it is taking 62 mb09:42
tuan_rakhmerov: Awesome, and i also did that in my devstack without any actions09:43
tuan_since we have many actions so that as you mentioned before the peak memory of loading workflows09:44
rakhmerovtuan_: so please collect more info: what workflows you run, what actions, when consumed RAM goes up etc.09:44
rakhmerovtuan_: what do you do with Mistral?09:44
rakhmerov:)09:44
rakhmerovso that I knew the context09:44
tuan_well, we have some our own workflows that mistral will take to talk to HEAT to deploy some vm on openstack09:45
tuan_and other workflows to run ansible to configure them09:45
tuan_it consumes RAM of course09:45
tuan_and now i think mistral works well as expected09:46
rakhmerovok, good to know09:48
rakhmerovinteresting09:48
openstackgerritLingxian Kong proposed openstack/mistral: Support openstack context for workflow and task  https://review.openstack.org/40724010:06
sharatssrakhmerov: thanks. whenever u r free pls review that patch. we can start working on dashboard if it gets merged10:06
openstackgerritQiming Teng proposed openstack/mistral: Fix version response from root controller  https://review.openstack.org/41238910:22
*** hparekh has quit IRC10:51
*** szaher has joined #openstack-mistral11:16
*** szaher has quit IRC11:23
*** szaher has joined #openstack-mistral11:27
*** szaher has quit IRC11:35
*** szaher has joined #openstack-mistral11:37
*** sharatss has quit IRC11:40
*** sharatss has joined #openstack-mistral11:41
d0ugalGetting a strange Mistral error here: http://logs.openstack.org/92/408992/3/check-tripleo/gate-tripleo-ci-centos-7-ovb-nonha/b55fdf1/console.html#_2016-12-19_06_27_31_50251311:47
d0ugalThe action is missing the uuid parameter for some reason.11:48
d0ugalhttps://github.com/openstack/python-ironic-inspector-client/blob/master/ironic_inspector_client/client.py#L3311:48
d0ugal^ that is what it should call.11:48
d0ugalactually, it calls this: https://github.com/openstack/python-ironic-inspector-client/blob/master/ironic_inspector_client/v1.py#L9011:49
d0ugalbut same issue.11:49
jaosoriord0ugal: last time it was the case that it couldn't instantiate the ironic-inspector client instance11:57
jaosoriord0ugal: which is why the keystone session was added here https://github.com/openstack/mistral/blob/master/mistral/actions/openstack/actions.py#L40511:58
jaosoriord0ugal: ironic inspector client also requires the server to be running already in order to retrieve it's own version11:59
jaosoriorso, effectively, that db-populate call requires keystone and ironic-inspector server to be running and ready before it can be called11:59
jaosoriorand in tripleo, it needs haproxy to be available as well11:59
jaosoriorit could also be some other issue with creating that client instance... so we really need those logs to see what happened12:01
d0ugaljaosorior: right12:03
d0ugaljaosorior: I find it intersting that it was half added, the action is there but the parameters are not12:04
d0ugalso it suggests that it is getting further than creating the client.12:04
* d0ugal reads more code12:04
jaosoriord0ugal: yeah, IIRC that was pretty much the behavior when I was seeing that error.12:05
d0ugalhttps://github.com/openstack/mistral/blob/master/mistral/actions/openstack/action_generator/base.py#L91-L9612:06
d0ugalThat seems dangerous to me - if we can't get the method, we shouldn't add the action. it should fail more loudly.12:06
d0ugaland like 87 needs to be LOG.exception12:06
d0ugaljaosorior: the command output might not tell us anything12:06
jaosoriord0ugal: at least if it's an issue creating the client it will go here https://github.com/openstack/mistral/blob/master/mistral/actions/openstack/action_generator/base.py#L8712:07
d0ugaljaosorior: true, so we will see that message but have no idea what the exception was :-D12:08
jaosoriord0ugal: do you have any idea why this is here https://github.com/openstack/mistral/blob/master/mistral/actions/openstack/action_generator/base.py#L94 ? why don't we just skip adding the action if we couldn't get the method12:08
jaosoriord0ugal: it does print the exception12:08
d0ugaljaosorior: no idea, I just linked to that above ^12:09
d0ugaljaosorior: true, it should be LOG.error tho'12:09
jaosoriorit's the third parameter12:09
d0ugalI am making a patch12:09
jaosoriorthat's what the 'e' is for here https://github.com/openstack/mistral/blob/master/mistral/actions/openstack/action_generator/base.py#L8812:09
jaosoriorbut yeah12:09
jaosoriorlog.error would be better12:09
d0ugalI see it :-P12:09
openstackgerritDougal Matthews proposed openstack/mistral: Use LOG.error when adding an OpenStack action fails  https://review.openstack.org/41243012:11
openstackgerritQiming Teng proposed openstack/mistral: Fix configuration generator  https://review.openstack.org/41225612:12
openstackgerritDougal Matthews proposed openstack/mistral: Use LOG.error when adding an OpenStack action fails  https://review.openstack.org/41243012:12
*** shardy is now known as shardy_lunch12:15
openstackgerritDougal Matthews proposed openstack/mistral: Don't create actions with empty arg_lists  https://review.openstack.org/41243312:15
*** sharatss has quit IRC12:18
*** catintheroof has joined #openstack-mistral12:18
*** sharatss has joined #openstack-mistral12:18
openstackgerritQiming Teng proposed openstack/mistral: Fix docs in README.rst  https://review.openstack.org/41228412:19
openstackgerritSharat Sharma proposed openstack/python-mistralclient: Wrap the contents of the input and description fields  https://review.openstack.org/40334112:21
*** dprince has joined #openstack-mistral12:22
openstackgerritSharat Sharma proposed openstack/python-mistralclient: Initial commit for python-mistralclient document  https://review.openstack.org/40473612:26
openstackgerritSharat Sharma proposed openstack/mistral: Added congress actions into Mistral  https://review.openstack.org/41020812:40
*** jtomasek has joined #openstack-mistral12:56
openstackgerritSharat Sharma proposed openstack/python-mistralclient: Wrap the contents of the input and description fields  https://review.openstack.org/40334112:59
*** tuan_ has quit IRC12:59
*** tuan_ has joined #openstack-mistral13:04
openstackgerritDougal Matthews proposed openstack/mistral: Don't create actions with empty arg_lists  https://review.openstack.org/41243313:21
openstackgerritDougal Matthews proposed openstack/mistral: Use LOG.exception when adding an OpenStack action fails  https://review.openstack.org/41243013:21
d0ugaljpich: ^ thanks.13:21
jpichd0ugal: Np!13:22
*** weshay_lata is now known as weshay13:31
*** zaneb has quit IRC13:36
*** tuan_ has quit IRC13:46
*** clenimar has joined #openstack-mistral13:46
openstackgerritSharat Sharma proposed openstack/mistral: Added congress actions into Mistral  https://review.openstack.org/41020813:58
*** bobh has joined #openstack-mistral14:09
*** chlong has joined #openstack-mistral14:14
*** shardy_lunch is now known as shardy14:16
*** bobh has quit IRC14:41
*** jtomasek has quit IRC14:50
*** jamielennox is now known as jamielennox|away14:56
*** jtomasek has joined #openstack-mistral14:59
*** bobh has joined #openstack-mistral15:06
*** bobh has quit IRC15:07
*** bobh has joined #openstack-mistral15:07
*** bobh has quit IRC15:12
*** jtomasek has quit IRC15:13
*** weshay is now known as weshay_afk15:41
*** weshay_afk is now known as weshay15:45
*** jtomasek has joined #openstack-mistral16:12
*** jtomasek has quit IRC16:16
openstackgerritGal Margalit proposed openstack/mistral-dashboard: Workflow list - added missing fields  https://review.openstack.org/41251716:20
*** weshay is now known as weshay_bbiab16:34
*** jaosorior has quit IRC16:48
*** jaosorior has joined #openstack-mistral16:49
openstackgerritPradeep Kilambi proposed openstack/mistral: Add aodh actions to mistral  https://review.openstack.org/40868416:51
*** ^Gal^ has quit IRC17:03
*** jpich has quit IRC17:04
*** weshay_bbiab is now known as weshay17:51
*** shardy has quit IRC18:08
*** openstack has joined #openstack-mistral19:15
*** chlong has quit IRC19:34
*** chlong has joined #openstack-mistral19:36
*** jaosorior has quit IRC19:52
*** Ravikiran_K has quit IRC19:54
*** thrash is now known as thrash|biab20:16
*** weshay is now known as weshay_relocatin20:42
*** jamielennox|away is now known as jamielennox21:04
*** thrash|biab is now known as thrash21:49
*** bobh has joined #openstack-mistral21:56
*** bobh has quit IRC21:58
*** dprince has quit IRC22:02
*** enykeev has quit IRC23:28
*** enykeev has joined #openstack-mistral23:28

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