Tuesday, 2016-10-18

*** david-lyle has quit IRC00:09
*** david-lyle has joined #openstack-zaqar00:22
*** david-lyle has quit IRC00:29
*** david-lyle has joined #openstack-zaqar00:31
*** david-lyle has quit IRC00:34
*** david-lyle has joined #openstack-zaqar00:36
*** david-lyle has quit IRC00:47
*** david-lyle has joined #openstack-zaqar00:48
*** david-lyle has quit IRC00:51
*** david-lyle has joined #openstack-zaqar00:52
*** david-lyle has quit IRC00:59
*** david-lyle has joined #openstack-zaqar01:01
*** david-lyle has quit IRC01:05
*** tqtran has quit IRC01:05
*** david-lyle has joined #openstack-zaqar01:06
*** david-lyle has quit IRC01:07
*** david-lyle has joined #openstack-zaqar01:13
*** david-lyle has quit IRC01:14
*** david-lyle has joined #openstack-zaqar01:15
*** shu-mutou-AWAY is now known as shu-mutou01:18
*** david-lyle has quit IRC01:19
*** david-lyle has joined #openstack-zaqar01:20
*** david-lyle has quit IRC01:21
*** david-lyle has joined #openstack-zaqar01:23
*** yanyanhu has joined #openstack-zaqar01:23
*** david-lyle has quit IRC01:24
*** david-lyle has joined #openstack-zaqar01:26
*** david-lyle has quit IRC01:32
*** david-lyle has joined #openstack-zaqar01:34
*** david-lyle has quit IRC01:37
*** david-lyle has joined #openstack-zaqar01:38
*** david-lyle has quit IRC01:38
*** david-lyle has joined #openstack-zaqar01:44
*** david-lyle has quit IRC01:44
*** david-lyle has joined #openstack-zaqar01:45
*** david-lyle has quit IRC01:46
*** david-lyle has joined #openstack-zaqar01:57
*** david-lyle has quit IRC01:57
*** david-lyle has joined #openstack-zaqar01:59
*** david-lyle has quit IRC02:00
*** david-lyle has joined #openstack-zaqar02:01
*** david-lyle has quit IRC02:02
*** david-lyle has joined #openstack-zaqar02:03
*** david-lyle has quit IRC02:03
*** david-lyle has joined #openstack-zaqar02:07
*** david-lyle has quit IRC02:08
*** david-lyle has joined #openstack-zaqar02:10
*** david-lyle has quit IRC02:11
*** david-lyle has joined #openstack-zaqar02:12
*** david-lyle has quit IRC02:14
*** david-lyle has joined #openstack-zaqar02:17
*** david-lyle has quit IRC02:18
*** david-lyle has joined #openstack-zaqar02:19
*** david-lyle has quit IRC02:19
*** david-lyle has joined #openstack-zaqar02:21
*** david-lyle has quit IRC02:21
*** david-lyle has joined #openstack-zaqar02:26
openstackgerritwanghao proposed openstack/zaqar: Reword description of grace  https://review.openstack.org/38536202:47
flwang1therve: need your help for the zaqar's trust notification driver03:12
*** david-lyle has quit IRC03:23
*** david-lyle has joined #openstack-zaqar03:24
*** david-lyle has quit IRC03:25
*** david-lyle has joined #openstack-zaqar03:26
*** david-lyle has quit IRC03:27
*** david-lyle has joined #openstack-zaqar03:28
*** david-lyle has quit IRC03:29
*** david-lyle has joined #openstack-zaqar03:30
*** david-lyle has quit IRC03:33
*** david-lyle has joined #openstack-zaqar03:34
*** rbrady is now known as rbrady-afk03:35
*** david-lyle has quit IRC03:36
*** david-lyle has joined #openstack-zaqar03:50
*** david-lyle has quit IRC03:51
*** david-lyle has joined #openstack-zaqar03:53
*** david-lyle has quit IRC03:54
*** tqtran has joined #openstack-zaqar03:57
*** david-lyle has joined #openstack-zaqar03:57
*** david-lyle has quit IRC03:57
*** david-lyle has joined #openstack-zaqar04:00
*** david-lyle has quit IRC04:01
*** david-lyle has joined #openstack-zaqar04:02
*** david-lyle has quit IRC04:04
*** david-lyle has joined #openstack-zaqar04:05
*** david-lyle has quit IRC04:05
*** david-lyle has joined #openstack-zaqar04:06
*** david-lyle has quit IRC04:08
*** david-lyle has joined #openstack-zaqar04:10
*** david-lyle has quit IRC04:11
*** david-lyle has joined #openstack-zaqar04:12
*** david-lyle has quit IRC04:13
*** david-lyle has joined #openstack-zaqar04:14
*** david-lyle has quit IRC04:15
*** david-lyle has joined #openstack-zaqar04:17
*** david-lyle has quit IRC04:18
*** david-lyle has joined #openstack-zaqar04:19
*** david-lyle has quit IRC04:20
*** flwang1 has quit IRC04:20
*** david-lyle has joined #openstack-zaqar04:21
*** GB21 has joined #openstack-zaqar04:34
*** flwang1 has joined #openstack-zaqar04:56
*** tqtran has quit IRC05:32
*** eliqiao has joined #openstack-zaqar05:43
*** rcernin has joined #openstack-zaqar06:01
*** pcaruana has joined #openstack-zaqar06:18
*** tesseract has joined #openstack-zaqar07:03
*** tesseract is now known as Guest8585507:03
*** odyssey4me has quit IRC07:16
*** odyssey4me has joined #openstack-zaqar07:18
therveflwang1, Around now07:21
flwang1therve: i'm not really sure if it's a mistral bug or the trust issue07:30
therveflwang1, What is? :)07:31
therveHello?07:35
flwang1therve: sorry, back07:37
flwang1when i test zaqar+ mistral + heat07:37
flwang1i found the token passed to mistral can't initialize keystone client07:37
flwang1therve: here is the bug i opened https://bugs.launchpad.net/mistral/+bug/163409007:38
openstackLaunchpad bug 1634090 in Mistral "Failed to create keystone client" [Undecided,New] - Assigned to Fei Long Wang (flwang)07:38
flwang1personally i think it's a bug of mistral07:38
flwang1but i just wanna get your opinion on this07:38
flwang1you're an expert of trust07:38
flwang1based on my understanding, the token trustee got based trust id should have the same permission like the trustor, right?07:39
therveYep07:40
therveSo you can create the trust, but then you can auth with it?07:41
therveI'd try to use the trust without mistral07:41
flwang1yep, the auth works i think, since i can see the request in mistral07:42
flwang1but mistral will use the token to built a keystone client to get service endpoint, e.g. heat's endpoint07:42
flwang1when building the client, mistral balmed07:42
therveAh ok07:43
flwang1mistral throws exception at here https://github.com/openstack/mistral/blob/master/mistral/utils/openstack/keystone.py#L3307:44
therveIt's possible that mistral needs to be aware of the fact that's it's a trust token07:49
therveflwang1, We should probably enter https://github.com/openstack/mistral/blob/master/mistral/utils/openstack/keystone.py#L125 but we don't07:52
flwang1therve: what's the real difference between a normal token and a trust token?07:59
flwang1technically, i assume they should be same08:00
flwang1at least, 'same' means they can do same things08:00
therveWell, yes, but there are some limitations08:00
flwang1any doc/link about the limitations?08:01
flwang1btw, how should i understand the 'is_trust_scoped'?08:01
flwang1this is the context of mistral when it handles the request from zaqar08:02
flwang1MistralContext {u'project_name': None, u'user_id': u'af6f84aaf58442cb85fc34e9ba6d58a4', u'roles': [u''], u'auth_uri': u'http://127.0.0.1:5000/v3', u'auth_cacert': None, u'auth_token': u'e86a0754f9e04fc79ca58b6d833a6f8a', u'expires_at': u'2016-10-18T08:11:25.000000Z', u'is_trust_scoped': False, u'project_id': None, u'user_name': u'admin', u'target_service_catalog': None}08:02
therveIt seems is_trust_scoped is only informed internally08:02
flwang1is_trust_scoped = Flase08:02
therveflwang1, You have only one empty role, that's strange08:02
flwang1since i'm using admin user under admin project08:03
flwang1it's a devstack env08:03
*** openstackgerrit has quit IRC08:04
*** openstackgerrit has joined #openstack-zaqar08:04
flwang1i think mistral is using the is_trust_scoped in a very limited way, see https://github.com/openstack/mistral/blob/master/mistral/services/security.py#L5108:06
flwang1it's the only place that is_trust_scoped can be set as 'True'08:07
flwang1which is for mistral webhook08:07
flwang1so for a token like what we're using, it's a trust token, but mistral 'hardcode'(believe) it as False08:08
*** mdnadeem has quit IRC08:09
therveI think it's an internal flag that they use, it shouldn't really matter08:21
*** GB21 has quit IRC09:03
*** openstackgerrit has quit IRC09:04
*** openstackgerrit has joined #openstack-zaqar09:04
*** GB21 has joined #openstack-zaqar09:14
flwang1therve: many thanks09:47
therveNo pb!09:47
flwang1all good now09:47
*** dynarro has joined #openstack-zaqar09:55
*** yanyanhu has quit IRC10:22
*** jtomasek is now known as jtomasek|biab10:40
*** dynarro has quit IRC10:42
*** dynarro has joined #openstack-zaqar11:25
*** rbrady-afk is now known as rbrady11:51
*** jtomasek|biab is now known as jtomasek11:54
*** GB21 has quit IRC12:41
*** nadya has joined #openstack-zaqar12:41
nadyahi folks! Could anyone please talk to me about kafka support in zaqar?12:42
thervenadya, Hi12:55
nadyahi therve! Could you please tell me what is the status of kafka support?12:55
thervenadya, Non existent12:56
nadyahehe :)12:56
nadyaok, so is that technically possible to introduce it?12:57
therveI think there may be a spike somewhere, so yeah I suppose12:57
nadyatherve: I mean, for example in oslo.messaging there is a pluggable structure. To support a new driver (e.g. kafka) we need to create a new implementation. Is that the same in zaqar?13:00
thervenadya, Yes. Zaqar already supports several drivers (mongo and redis)13:00
nadyatherve: ok. I think I should investigate code a little bit and will come back to you later. Thank you very much for your help!13:03
therveNo problem13:03
therveflaper87, Do we have traces somewhere of a kafka driver?13:04
flaper87therve: I do not :(13:04
*** nadya has quit IRC13:20
*** mpanetta has joined #openstack-zaqar13:31
*** jtomasek is now known as jtomasek|afk13:33
*** mpanetta has quit IRC13:35
*** mpanetta has joined #openstack-zaqar13:36
-openstackstatus- NOTICE: We are away of pycparser failures in the gate and working to address the issue.14:06
*** nadya has joined #openstack-zaqar14:17
*** nadya has quit IRC15:33
*** nadya has joined #openstack-zaqar15:39
-openstackstatus- NOTICE: pycparser 2.16 released to fix assertion error from today.16:12
*** jtomasek|afk is now known as jtomasek16:22
*** Guest85855 has quit IRC16:25
*** wxy__ has quit IRC16:26
*** wxy__ has joined #openstack-zaqar16:26
*** kgriffs is now known as kgriffs3216:35
*** kgriffs32 is now known as kgriffs___16:35
*** kgriffs___ is now known as kgriffs16:35
*** kgriffs is now known as abcdefghijkgriff16:35
*** abcdefghijkgriff is now known as kgriffs16:36
*** wxy__ has quit IRC16:42
*** wxy__ has joined #openstack-zaqar16:42
*** tqtran has joined #openstack-zaqar16:42
*** wxy__ has quit IRC16:45
*** wxy__ has joined #openstack-zaqar16:45
*** rcernin has quit IRC16:51
*** exploreshaifali has joined #openstack-zaqar17:00
*** dynarro has quit IRC17:05
*** wxy__ has quit IRC17:33
*** njohnston has quit IRC17:33
*** flaper87 has quit IRC17:33
*** Guest66666 has quit IRC17:33
*** EmilienM has quit IRC17:33
*** boris-42 has quit IRC17:33
*** tonyb has quit IRC17:33
*** Guest66666 has joined #openstack-zaqar17:33
*** tonyb has joined #openstack-zaqar17:33
*** wxy__ has joined #openstack-zaqar17:34
*** EmilienM has joined #openstack-zaqar17:34
*** EmilienM has quit IRC17:35
*** EmilienM has joined #openstack-zaqar17:35
*** njohnston has joined #openstack-zaqar17:36
*** boris-42 has joined #openstack-zaqar17:40
*** nadya has joined #openstack-zaqar17:59
*** nadya has quit IRC18:03
*** nadya has joined #openstack-zaqar18:39
*** dynarro has joined #openstack-zaqar18:43
*** nadya has quit IRC18:44
*** exploreshaifali has quit IRC18:45
*** flaper87 has joined #openstack-zaqar18:46
*** flaper87 has quit IRC18:46
*** flaper87 has joined #openstack-zaqar18:46
*** exploreshaifali has joined #openstack-zaqar19:00
*** nadya has joined #openstack-zaqar19:55
*** flwang1 has quit IRC19:59
*** nadya has quit IRC19:59
*** jasond has joined #openstack-zaqar20:34
*** flwang1 has joined #openstack-zaqar21:01
*** dynarro has quit IRC21:05
jasondhi, is there some documentation on subscription options somewhere?21:10
flwangjasond: hi, unfortunately, not too much, which driver you're looking for?21:26
jasondflwang: i was just working on the heat resource for zaqar subscriptions21:27
flwangjasond: cool, subscription's options is just a dict/json, technically, you can put anything in it21:27
jasondflwang: ok, thanks.  i will just pass the options data along to zaqar then21:28
flwangbut for email driver and trust driver, there are some specific reserved 'attributes'21:28
flwangfor email subscription, we support from and subject, see https://github.com/openstack/zaqar/blob/master/zaqar/notification/tasks/mailto.py#L4521:29
flwangfor webhook/trust, we support 'post_data' see https://github.com/openstack/zaqar/blob/master/zaqar/notification/tasks/webhook.py#L3721:31
flwangi will add this in developer documents, thanks for reminding me :)21:32
jasondflwang: i did see that post_data part in the code.  made me wonder.  thanks for the info21:32
flwangpost_data is a little bit confused i would say21:34
flwangjasond: let me give a good example for that, wait a sec21:34
flwang1jasond:  see http://paste.openstack.org/show/586283/21:35
flwang1it's a subscription for mistral and using trust21:35
flwang1to trigger an execution of a mistral workflow21:35
jasondflwang1: nice, that helps21:36
flwang1mistral need a specific post body format, for an execution, it needs 'workflow_id' and 'input'21:36
flwang1and, we also need to 'inject' the message body to that post body21:36
flwang1so i assume you got the idea now21:36
jasondflwang1: yes. thank you. i will add you to the gerrit review when i get it up21:37
flwang1it's not a perfect solution, but it works as charm21:37
flwang1jasond: no problem, i'm happy to review it21:37
*** flwang1 has quit IRC21:52
*** flwang1 has joined #openstack-zaqar21:52
*** jasond has quit IRC21:59
*** exploreshaifali has quit IRC23:51

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