Thursday, 2017-11-02

Qimingdtruong, hi, we haven't given that a deep thought yet. we did received some requests on it.01:19
Qimingour current suggestion for those use cases is to have the users develop downstream event processors01:19
Qimingwhen cluster scale is changed (or something similar happens), senlin emits event notifications. users can subscribe to those events for further processing.01:20
Qimingdown this line is another topic we have just discussed during team meetup --01:21
Qimingwe may add a HTTP POST call as a driver for event generation01:21
Qimingwe believe that is somehow equivalent to the lifecycle hooks you mentioned01:22
*** openstackgerrit has joined #senlin03:13
*** ChanServ sets mode: +v openstackgerrit03:13
openstackgerritMerged openstack/senlin master: Clean useless decorator in test  https://review.openstack.org/51654003:13
openstackgerritMerged openstack/senlin master: Remove override get_schema  https://review.openstack.org/51623003:24
*** dtruong_ has joined #senlin03:43
dtruong_hi qiming.  thanks for the answer.  the problem with the downstream event processing is that it sends the notification after senlin already performed the scale in action and deleted the nodes.03:48
dtruong_the goal of the lifecycle hooks is to pause the scale in action and allow another service or application to perform clean up on the nodes that were identified to be deleted.03:49
dtruong_i'm working on an implementation that would another API to senlin for a scale in with lifecycle hook.03:50
Qimingem, that IS a problem.03:50
Qimingwe have to tell which API request is the original one and which is the "confirmed" one03:50
Qimingsounds like we still need an out-of-band flag for differentiation03:51
Qiminghowever, the team did discussed this use case during our meetup last week03:52
Qimingthe solution we came up is something like this:03:52
Qimingyou can attach a deletion policy to your cluster, telling Senlin that each node should be granted a graceful period before being actually removed03:53
Qimingthis is already supported03:53
Qimingwhat is missing is that Senlin should somehow send an alarm to your node (or some software) that a node is being destoryed03:54
Qimingthat logic is missing, and we felt a need to support a generic HTTP sink for event notification03:55
Qimingyou can do whatever logic during the time you get a notification and the time your node is deleted03:55
Qimingyou can adjust the grace period if you have a lot of things to do during that interval03:56
dtruong_i see.  the one disadvantage i see is that we cannot notify senlin that the clean up has completed.  in AWS there is a concept of lifecycle completion where the application can notify the scaling group that the clean up is done.04:01
dtruong_in this case we would have to wait until the grace period expires.04:01
Qimingyep04:01
dtruong_i guess my general question is how does the team feel about adding the equivalent of the AWS lifecycle hooks in senlin04:02
dtruong_i was thinking of a design where is a new API for 'scale in with lifecycle hook'.04:04
dtruong_that API would be similar to the existing 'scale in' API but also take a parameter for a zaqar queue.  then during execution of that API, it would identify nodes for deletion same as the 'scale-in' API04:06
dtruong_but instead of actually deleting the nodes it would send a notification to the zaqar queue of the nodes to be deleted.04:06
dtruong_that would be the lifecycle hook for the application to perform the custom clean-up04:07
*** AlexeyAbashkin has joined #senlin04:18
*** AlexeyAbashkin has quit IRC04:22
*** dtruong_ has quit IRC05:00
*** dtruong_ has joined #senlin05:06
*** maestropandy has joined #senlin05:31
*** maestropandy has quit IRC05:35
dtruong_qiming:  i will submit a spec file for review that explains my idea in more detail.05:37
Qiminggreat!05:38
*** dtruong_ has quit IRC05:39
*** maestropandy has joined #senlin06:03
*** maestropandy has left #senlin06:14
*** maestropandy has joined #senlin07:23
*** maestropandy1 has joined #senlin07:27
*** maestropandy has quit IRC07:29
*** maestropandy1 has left #senlin07:58
*** AlexeyAbashkin has joined #senlin07:58
*** liyi has joined #senlin08:02
*** liyi has quit IRC08:05
*** liyi has joined #senlin08:11
*** liyi has quit IRC08:22
*** liyi has joined #senlin08:30
*** maestropandy has joined #senlin09:38
*** maestropandy has quit IRC09:59
*** maestropandy has joined #senlin10:00
*** liyi has quit IRC10:07
*** liyi has joined #senlin10:07
*** liyi has quit IRC10:12
*** liyi has joined #senlin10:28
*** maestropandy has quit IRC10:29
*** liyi has quit IRC10:32
*** liyi has joined #senlin11:01
*** catintheroof has joined #senlin12:34
*** maestropandy has joined #senlin12:36
*** maestropandy has quit IRC12:38
*** liyi has quit IRC12:58
*** AlexeyAbashkin has quit IRC13:23
*** jmlowe_ has quit IRC13:36
*** AlexeyAbashkin has joined #senlin13:45
*** liyi has joined #senlin13:50
*** liyi has quit IRC13:54
*** jmlowe has joined #senlin14:04
*** jmlowe has quit IRC14:11
*** liyi has joined #senlin14:21
*** liyi has quit IRC14:25
*** jmlowe has joined #senlin14:27
*** AlexeyAbashkin has quit IRC15:53
*** liyi has joined #senlin16:18
*** liyi has quit IRC16:22
*** catintheroof has quit IRC16:26
*** catintheroof has joined #senlin16:30
*** dtruong has quit IRC16:45
*** dtruong has joined #senlin16:53
*** liyi has joined #senlin17:07
*** liyi has quit IRC17:12
*** AlexeyAbashkin has joined #senlin17:31
*** AlexeyAbashkin has quit IRC17:35
*** AlexeyAbashkin has joined #senlin18:09
*** AlexeyAbashkin has quit IRC18:14
*** liyi has joined #senlin19:16
*** liyi has quit IRC19:20
*** liyi has joined #senlin20:26
*** liyi has quit IRC20:30
*** jmlowe has quit IRC20:48
*** AlexeyAbashkin has joined #senlin21:08
*** AlexeyAbashkin has quit IRC21:13
*** jmlowe has joined #senlin21:41
*** catintheroof has quit IRC21:53
*** AlexeyAbashkin has joined #senlin22:08
*** AlexeyAbashkin has quit IRC22:13
*** liyi has joined #senlin22:45
*** liyi has quit IRC22:49

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