Thursday, 2016-03-31

*** xuhaiwei has joined #senlin00:12
*** Qiming has quit IRC00:34
*** zzxwill has joined #senlin00:42
openstackgerritMerged openstack/senlin: Developer doc for API microversioning  https://review.openstack.org/29862600:49
*** zzxwill has quit IRC01:10
*** zzxwill has joined #senlin01:13
*** zzxwill_ has joined #senlin01:36
*** zzxwill has quit IRC01:39
*** Qiming has joined #senlin01:47
*** yanyanhu has joined #senlin01:47
*** yanyanhu has quit IRC01:57
*** yanyanhu has joined #senlin01:58
*** EldonZhao has quit IRC02:01
*** EldonZhao has joined #senlin02:01
*** elynn has joined #senlin02:03
*** elynn_ has joined #senlin02:09
*** elynn has quit IRC02:11
openstackgerritEldonZhao proposed openstack/senlin: Add NoneType protection for ex.response in sdk.py  https://review.openstack.org/29910202:12
*** elynn_ has quit IRC02:35
*** EldonZhao has quit IRC02:43
*** EldonZhao has joined #senlin02:46
*** yanyanhu has quit IRC03:05
*** yanyanhu has joined #senlin03:06
*** yuanying has quit IRC03:21
*** elynn_ has joined #senlin03:34
*** elynn__ has joined #senlin03:53
*** elynn_ has quit IRC03:56
*** zzxwill_ has quit IRC03:57
*** yuanying has joined #senlin04:07
*** elynn__ has quit IRC04:13
*** EldonZhao has quit IRC04:38
*** zzxwill has joined #senlin05:07
*** elynn__ has joined #senlin05:29
*** elynn__ has quit IRC05:34
*** elynn__ has joined #senlin05:34
*** elynn_ has joined #senlin05:43
*** elynn__ has quit IRC05:46
*** elynn__ has joined #senlin05:50
*** elynn_ has quit IRC05:52
elynn__Hi Qiming06:13
elynn__About patch https://review.openstack.org/#/c/298187/ I don't get the point of Anne Gentle's comments.06:16
Qimingwell06:22
QimingI think there were two comments06:22
Qimingthe inline comment was about actionLocationParameter and resourceLocationParameter06:22
Qimingshe wasn't sure that there is an actionLocationParameter entity in common.ent06:23
Qimingthen when posting her comment, she further suggested you to remove resourceLocationParameter if it is not used anymore06:23
elynn__First, she saw that there's a actionLocationParameter cause she paste it in comment06:24
elynn__Is she confused or I'm confused...06:24
elynn__And for resourceLocationParameter, we still used for other resources, we can't remove it.06:25
QimingI think she was confused06:26
Qimingthat is fine06:26
Qimingexplain it then06:26
elynn__Is there anything I can do according to her comment?06:26
elynn__about the codes.06:26
Qimingwe are using actionLocationParameter in some cases and we are still using resourceLocationParameter somewhere else06:26
elynn__Yes, thanks, I will post a comment later :) I really need to improve my English skills...06:28
elynn__And another question06:28
elynn__https://review.openstack.org/#/c/298187/2/api-ref/src/wadls/clustering-api/src/v1/wadl/clustering-api.wadl L217-21906:28
elynn__Do we need to change that too?06:28
Qimingwhy?06:29
elynn__No very familiar with wadl, is it related to actionLocationParameter?06:30
Qimingit is not about the WADL06:30
Qimingit is about where are we returnning from a cluster create request06:30
elynn__Oh, I see...06:30
elynn__It's another return value of this request.06:31
Qimingno, line 213-222 is the return value06:31
Qimingthe so called resourceLocationParameter is just a header06:31
Qimingsee this: http://git.openstack.org/cgit/openstack/api-site/tree/api-ref/src/wadls/clustering-api/src/v1/common.ent#n3006:33
elynn__Okay, then I should leave it there.06:34
Qimingit says the style is a header06:34
Qimingright, I guess so06:34
elynn__Thanks for clarification :)06:35
QimingI think for cluster create, we are returning pointer to the cluster instead of the action06:36
Qimingthat means we should use resourceLocationParameter, not actionLocationParameter06:36
elynn__https://github.com/openstack/senlin/blob/master/senlin/api/openstack/v1/clusters.py#L18006:37
elynn__We return location pointed to actions now, according to your suggestion.06:38
elynn__I remember you said 202 should always comes with a location to action?06:39
Qimingno06:39
Qimingthat wasn't what I said06:39
QimingI pointed you to the spec06:39
Qiminghttp://git.openstack.org/cgit/openstack/api-wg/tree/guidelines/http.rst#n10506:40
elynn__the URI of a status resource that the client can use to query the06:40
elynn__        progress of the asynchronous operation.06:40
QimingI said I was okay with both ways06:41
elynn__I think this means the action ID06:41
Qimingyes06:41
Qimingpreviously, we are using "the URI of the resource to be created, if known."06:41
Qimingcannot recall why we saw that a problem06:41
elynn__yes06:42
elynn__It's a comment you leave in my tempest patch.06:42
elynn__https://review.openstack.org/#/c/295647/3/senlin_tempest_tests/services/clustering/json/clustering_client.py L 10306:43
Qimingok, looking06:44
Qimingright, I was making mistakes06:44
QimingI was believing that all 202 responses have the location header pointing to an action id06:45
elynn__I think pointing to an action ID is ok06:45
elynn__We can track the action status to see if a cluster is ready.06:45
Qimingyes, function wise, either way is okay06:46
Qimingmy concern is mostly about ease of use, from a developer's perspective06:46
elynn__I would prefer to return a location pointed to action ID, since pointed to a cluster id is useless, we can get cluster from cluster['id']06:47
Qimingin the tempest code, we are not checking the 'location' header anyway, no matter it is pointing to the cluster or the action06:48
elynn__That's exactly what we do in senlin codes now.06:48
Qimingwhat do you mean?06:48
elynn__I mean we return a location pointed to action in senlin API now.06:48
Qimingline 103 and 162 in the file: https://review.openstack.org/#/c/295647/3/senlin_tempest_tests/services/clustering/json/clustering_client.py06:49
elynn__And new patchset of tempest is checking the action status.06:49
Qimingwe are returning them or checking them06:49
elynn__https://review.openstack.org/#/c/295647/5/senlin/tests/tempest_tests/services/clustering/clustering_client.py L98-9906:50
Qimingthat will make negative tests very difficult06:50
elynn__Why do you say so?06:50
Qimingpatch set 5 looks much better06:51
Qimingsuppose we want to emulate some node creation failures (e.g. host running out of memory)06:51
Qimingwe need to understand what happened some time after create_node has been invoked06:52
Qimingif we are returning the action_id, we have a better venue to do that now06:53
elynn__We could just failed the action?06:54
Qimingeither way, we'd better make the openstack_test drivers smarter06:54
elynn__Haven't touch the drivers, but will think of it.06:55
Qimingwhen the faked nova driver is about to create an instance, it may choose to return something good, or something bad06:56
Qimingthat is gonna be a really challenge for senlin engine/action06:56
Qimingsee if we can handle all failures properly06:56
Qiming(I believe we cannot today)06:56
Qiminghttp://git.openstack.org/cgit/openstack/senlin/tree/senlin/tests/functional/drivers/openstack/nova_v2.py06:58
elynn__Or we can create a new backend driver to tests failures?06:58
Qimingsounds like a bad idea to me06:58
elynn__We can pass some extra parameters to cause failure.06:58
Qimingeach time you switch driver, you will need to restart the senlin-engine06:59
Qimingwe don't have dynamical driver switching mechanism06:59
Qimingand I don't think we will need such a complex infra setup06:59
elynn__Okay, I need to think about it.07:00
elynn__BTW, I run into some db problems https://bugs.launchpad.net/senlin/+bug/156392007:00
openstackLaunchpad bug 1563920 in senlin "Got db error when running tempest tests" [Undecided,New]07:00
Qiminghttp://git.openstack.org/cgit/openstack/senlin/tree/senlin/tests/functional/drivers/openstack/nova_v2.py#n12607:01
Qimingthat is a place we can inject some customization07:01
Qimingit could be a global 'success_rate' variable07:01
elynn__Or maybe some specific name or id can cause failure?07:01
Qimingwe don't have a name/id generation protocol for hacking, right?07:04
elynn__seems so...07:04
elynn__maybe 'success_rate' is a good idea07:05
QimingI did saw 1563920 report, but I'm not sure I can reproduce it right now and dig into it07:05
*** gongysh has quit IRC07:06
QimingI'm doubting if we should reconsider the usage of 'oslo_context.get_current()'07:06
Qimingnot sure if it is relevant to this07:07
elynn__I remember yanyanhu encountered db error before when he writes functional tests.07:07
Qimingyep, several decades ago, we were trapped by db concurrency problems07:08
yanyanhuelynn__, that error was caused by db concurrency issue. I think it has been addressed by Qiming's patches on action and DB rework07:09
yanyanhuit didn't happen recently07:09
elynn__So I'm facing another problem?07:09
yanyanhuhmm, not sure about it07:10
yanyanhuI saw that bug report but didn't get clue07:10
elynn__It happens very high frequency in my env, about 50%, not sure what's causing it. Only have 3 tests for now.07:12
yanyanhujust cluster create/delete and update, right?07:12
elynn__yes07:13
Qimingokay, that high frequency warrants some debug07:13
yanyanhuis there any difference between the behavior of tempest test and our existing functional test?07:14
yanyanhue.g. all tests are running in parallel?07:14
elynn__yanyanhu, no, I copy it and just use the client from tempest.07:14
elynn__I think they are parallel.07:14
yanyanhuhmm, this is different from existing functional test which runs all cases in sequence07:15
elynn__Haven't figure out how to run them in sequence.07:15
yanyanhuany error log in engine?07:15
yanyanhusenlin-engine07:15
yanyanhuelynn__, in parallel means three test cases are started concurrently?07:16
elynn__Pasted in bug description, delete_clusters will failed because of db problem.07:16
elynn__I'm not sure all of them or just some of them are parallel.07:17
yanyanhuthe old DB issues always produced forever-waiting actions and you can observed related log07:17
yanyanhuyou mean this bug report? https://bugs.launchpad.net/senlin/+bug/156392007:17
openstackLaunchpad bug 1563920 in senlin "Got db error when running tempest tests" [Undecided,New]07:17
yanyanhuthe log msg07:17
elynn__Seems it failed at start_action07:18
elynn__"/opt/stack/senlin/senlin/engine/dispatcher.py", line 112, in start_action07:18
yanyanhudoesn't look like a DB error ?07:18
elynn__InvalidRequestError A transaction is already begun. Use subtransactions=True to allow subtransactions.07:18
yanyanhulooks like an error about rpc07:19
elynn__Hmm, maybe it's not a db error07:19
yanyanhuabout the rpc communication between engine dispatcher and worker07:19
yanyanhuI guess it's not an error about DB transaction : )07:20
elynn__Let me check the full log.07:20
yanyanhualthough this line looks like ... Remote error: InvalidRequestError A transaction is already begun. Use subtransactions=True to allow subtransactions.07:20
yanyanhuyes, I think there should be some hints in the full engine log07:20
yanyanhuabout why RemoteError happened07:20
openstackgerritEldonZhao proposed openstack/senlin: Add NoneType protection for ex.response in sdk.py  https://review.openstack.org/29910207:22
*** gongysh has joined #senlin07:23
elynn__Got this error at my home env, may need to reproduce this in my work env to collect logs...07:23
yanyanhu...07:24
openstackgerritEldonZhao proposed openstack/senlin: Add NoneType protection for ex.response in sdk.py  https://review.openstack.org/29910207:27
openstackgerritEldonZhao proposed openstack/senlin: Add NoneType protection for ex.response in sdk.py  https://review.openstack.org/29910207:59
*** elynn__ has quit IRC08:11
*** zzxwill has quit IRC08:18
*** zzxwill has joined #senlin08:59
*** lixinhui_ has joined #senlin09:09
*** elynn__ has joined #senlin09:10
*** elynn__ has quit IRC09:14
*** elynn__ has joined #senlin09:14
*** lixinhui_ has quit IRC09:15
*** elynn__ has quit IRC09:22
*** zzxwill has quit IRC09:46
*** Qiming has quit IRC09:52
*** yanyanhu has quit IRC09:54
*** yanyanhu has joined #senlin09:55
*** yanyanhu has quit IRC09:55
*** elynn__ has joined #senlin09:58
*** zzxwill has joined #senlin09:59
*** elynn__ has quit IRC10:03
*** elynn__ has joined #senlin10:03
openstackgerritMerged openstack/senlin: Add NoneType protection for ex.response in sdk.py  https://review.openstack.org/29910210:06
*** elynn__ has quit IRC10:06
*** zzxwill_ has joined #senlin10:11
*** zzxwill has quit IRC10:12
*** zzxwill_ has quit IRC10:37
*** zzxwill has joined #senlin10:39
*** Qiming has joined #senlin10:49
*** zzxwill has quit IRC10:51
*** dhellmann has quit IRC11:22
*** dhellmann_ has joined #senlin11:22
*** lixinhui_ has joined #senlin11:26
*** dhellmann_ is now known as dhellmann11:26
*** lixinhui_ has quit IRC12:05
*** zzxwill has joined #senlin12:16
openstackgerritEldonZhao proposed openstack/senlin: Add action-id to Resp of node-delete  https://review.openstack.org/29989812:35
openstackgerritEldonZhao proposed openstack/senlin: Add action-id to Resp of node-delete  https://review.openstack.org/29989812:38
*** lixinhui_ has joined #senlin13:43
*** zzxwill has quit IRC13:46
*** zzxwill has joined #senlin13:57
*** lixinhui_ has quit IRC14:12
*** gongysh has quit IRC14:25
*** gongysh has joined #senlin14:42
*** zzxwill has quit IRC14:46
*** zzxwill has joined #senlin14:52
*** gongysh has quit IRC14:56
*** Qiming has quit IRC15:24
*** zzxwill has quit IRC16:40
openstackgerritEthan Lynn proposed openstack/senlin: [WIP]Use the new enginefacade from oslo.db  https://review.openstack.org/30008916:44
openstackgerritEthan Lynn proposed openstack/senlin: [WIP]Use the new enginefacade from oslo.db  https://review.openstack.org/30008916:53
-openstackstatus- NOTICE: Job failures for missing traceroute packages are in the process of being fixed now, ETA 30 minutes to effectiveness for new jobs17:49
*** openstackgerrit has quit IRC19:03
*** openstackgerrit has joined #senlin19:05
-openstackstatus- NOTICE: Any jobs which erroneously failed on missing traceroute packages should be safe to recheck now19:55
*** Qiming has joined #senlin23:58

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