Friday, 2016-10-14

*** guoshan has joined #senlin00:01
*** guoshan has quit IRC00:06
*** zzxwill has joined #senlin00:18
*** zzxwill has quit IRC00:20
*** zzxwill has joined #senlin01:00
*** yuanying has quit IRC01:03
*** yuanying has joined #senlin01:07
*** guoshan has joined #senlin01:14
*** ruijie has joined #senlin01:20
*** zhurong has joined #senlin01:22
*** yuanying_ has joined #senlin01:23
*** yuanying has quit IRC01:26
*** yanyanhu has joined #senlin01:31
*** zhurong has quit IRC01:40
*** zhurong has joined #senlin01:41
*** elynn has joined #senlin01:47
*** elynn_ has joined #senlin01:52
Qiminghi, all01:52
Qiminghi, guys,
Qimingcore team, please respond, thanks01:52
*** elynn has quit IRC01:55
yanyanhu+1 from, has replied to the mail02:07
yanyanhufrom me02:07
yanyanhuhi, R_lixh, around?02:09
yanyanhuhi, R_lixh, I have written down the design of message type of receiver in the following etherpad. You can refer to it to understand the workflow.02:22
Qimingyanyanhu, why don't we incorporate those texts into the developer docs here?
QimingI'm really concerned that we are scattering such docs randomly02:47
yanyanhuQiming, yes, I'm still working on it. Just xinhui asked me a quick introduction for message receiver, I rewrote that etherpad.02:48
QimingI know you are working on user docs for message type receivers02:48
Qimingthis etherpad is more about the design02:49
yanyanhuyes, need to work on developer doc as well02:49
Qimingwhich I think should be documented02:49
Qimingit would be super helpful for anyone who wants to understand this part of design02:50
yanyanhuwill work on developer doc soon to help other developer understand it02:50
*** yuanying_ has quit IRC02:51
*** yuanying has joined #senlin02:52
*** guoshan has quit IRC02:57
*** ruijie has quit IRC03:00
*** guoshan has joined #senlin03:03
*** yuanying has quit IRC03:15
*** yuanying has joined #senlin03:15
*** yuanying_ has joined #senlin03:17
*** yuanying has quit IRC03:18
*** yuanying_ has quit IRC03:22
*** ruijie has joined #senlin03:25
openstackgerritlvdongbing proposed openstack/senlin: Integrate osprofiler into Senlin
*** shu-mutou-AWAY has quit IRC03:41
*** shu-mutou has joined #senlin03:50
*** yuanying has joined #senlin03:52
*** zzxwill has quit IRC04:03
*** guoshan has quit IRC04:05
*** guoshan has joined #senlin04:05
openstackgerritwu.yucheng proposed openstack/senlin-dashboard: Cleanup allowed() for cluster/node action
*** guoshan has quit IRC04:10
*** elynn_ has quit IRC04:10
openstackgerritMerged openstack/senlin-dashboard: Cleanup allowed() for cluster/node action
*** xuhaiwei has joined #senlin04:42
openstackgerritKATO Tomoyuki proposed openstack/python-senlinclient: Add plug-in summary for osc doc
*** guoshan has joined #senlin05:20
*** guoshan has quit IRC05:25
*** R_lixh has quit IRC05:25
*** elynn_ has joined #senlin05:30
*** elynn__ has joined #senlin05:35
*** elynn_ has quit IRC05:35
*** zzxwill has joined #senlin05:36
ruijieHi, Qiming05:41
openstackgerritMerged openstack/python-senlinclient: Add plug-in summary for osc doc
*** zhurong has quit IRC05:51
*** R_lixh has joined #senlin05:59
*** zzxwill has quit IRC06:08
*** guoshan has joined #senlin06:11
openstackgerritlvdongbing proposed openstack/python-senlinclient: Change osprofiler option "--profile" to "--os-profile"
*** lixinhui_ has joined #senlin06:20
*** guoshan_ has joined #senlin06:22
*** guoshan has quit IRC06:25
*** guoshan has joined #senlin06:26
*** guoshan_ has quit IRC06:26
lixinhui_yanyanhu, Thanks06:31
yanyanhulixinhui_, my pleasure. I'm now writing the developer doc of message receiver. Hopefully, the first patch will be proposed this afternoon.06:32
yanyanhuyou can read it for more detail information. And plz leave comments if you have any question of confusion about it06:32
Qimingcore team, please check
Qimingand leave you vote06:35
xuhaiweiHi Qiming, have some questions about health policy06:47
xuhaiweiI can't find the document about it06:47
Qimingoh, want to write one in Japanese?06:47
xuhaiwei:(, am I going to the wrong place?06:48
Qimingno, the doc for health policy is still to be authored ...06:48
Qimingno doc for developer, no doc for user06:49
xuhaiweiok, I will explain it to the tacker team, so I need to understand it well06:49
Qimingem ...06:49
Qimingyou may want to check with xinhui and ethan06:50
Qimingthey are working on a talk on Barcelona ... building auto-healing clusters using senlin06:50
xuhaiweifrom the source, I have understood it to some extent06:50
Qimingbasically, there will be two questions you will need to answer06:51
Qiming1) what is HA and why it is needed?06:51
Qiming2) how could HA be achieved and how to do it with Senlin06:51
Qimingyes, we have a working version of health policy06:52
Qimingbut you will have to realize that the road is pretty long because the problem space is too large06:52
Qimingyou can communicate that to tacker team06:52
Qimingwe are working on a better support to HA even today, to make sure we can cover most typical use cases in real life06:54
xuhaiweiyes, from the source, I see currently if a vm is not in ACTIVE status, senlin will rebuild it or recreate it06:54
Qimingyes you can reference the source code, and let tacker team know where we are today06:54
xuhaiweiI am not understanding well about fencing06:55
Qimingyou may also want to let them know that our current design was an open framework06:55
Qimingwe considered a lot more use cases before we wrote these code06:55
Qimingfor example, auto-healing may not be always valid, we have cluster/node_check, cluster/node_recover APIs added to enable other usage scenarios06:56
Qimingour receivers design allows users to hook any external failure detection mechanism that can trigger a cluster recovery, so on and so forth ...06:57
Qimingfencing is an on-going work06:57
Qimingit is a (necessary) step before doing node recovery06:57
Qimingthe reason we need fencing is that failure detection itself cannot be made 100% reliable06:58
Qimingtake a VM down event for example06:58
Qimingif the senlin-engine (on management network) cannot reach a VM, it may conclude that VM is dead06:59
xuhaiweican senlin cooperate with other monitoring tools to check if the vm is healthy or not?06:59
Qiminghowever, that may and may not be true06:59
Qimingthe VM may be still alive on its tenant network06:59
Qimingbefore going any further on recovering that VM, we will need to **make sure the VM is dead**07:00
Qimingthat step is called fencing ... it is about killing a VM by shoot it in the head07:00
Qiminghealth checking can be completely offloaded to another software/service07:00
Qimingwe don't know how users will be doing that07:01
Qimingbut we believe they are smart people, and they have tools to monitor their baby VMs07:01
Qimingwhen they detect such VM failures, they can trigger a senlin receiver to do the recovery07:01
Qimingfor those who don't want to bother setting up their own monitoring infra, senlin has a builtin, basic closed-loop07:02
Qimingsenlin will detect the VM failure and handle them automatically07:02
xuhaiweiok, make sense to me, senlin receiver not only manage scale_in/out, but also manage cluster recovery07:02
Qimingyes, it is a socket07:03
Qimingyou can use it for whatever legal reasons07:03
ruijieHi, Qiming. Have a question about the review
ruijieWill the action be a new API?07:07
ruijieI mean all the cluster action will be divided to many new APIs07:07
Qimingany user visible API changes should be treated seriously07:09
Qimingthis include the introduction of a new URI, new verb, new field into a request, new field into a body, ...07:09
Qimingto avoid bumping the API micro-version frequently, we can group several changes into a single version bump07:10
Qimingfor example, last time we bumped api to 1.2 when we introduced three changes to the API07:11
Qimingcluster action changes is a little bit tricky because we are using the same POST URI /clusters/<cid>/actions for action triggering07:11
Qimingthat is why I was suggesting you move the new logic out of the current function and annotate it with a new version number07:12
openstackgerritMerged openstack/python-senlinclient: Change osprofiler option "--profile" to "--os-profile"
QimingI'm curious if that will help ensure/improve api versioning07:12
*** Qiming is now known as Qiming_afk07:13
ruijieeh.. that makes sense, I thought we are going to create a new API. Misunderstood the feedback.07:13
ruijieThanks, Qiming.07:15
openstackgerritYanyan Hu proposed openstack/senlin: [WIP]Add developer doc for message receiver
openstackgerritYanyan Hu proposed openstack/senlin: [WIP]Add user doc for message receiver
*** Qiming_afk is now known as Qiming07:23
openstackgerritYanyan Hu proposed openstack/senlin: [WIP]Add developer doc for message receiver
openstackgerritShu Muto proposed openstack/senlin-dashboard: Fix typo
xuhaiweihi, I am thinking a case that should we add a 'count' option when creating a SCALE_OUT receiver, since sometimes scale out one node is not enough at all07:48
xuhaiweiany ideas about this?07:48
Qimingyes, xuhaiwei, you can do that07:50
Qiming senlin receiver-create07:51
Qimingusage: senlin receiver-create [-t <TYPE>] [-c <CLUSTER>] [-a <ACTION>]07:51
Qiming                              [-P <KEY1=VALUE1;KEY2=VALUE2...>]07:51
Qiming                              <NAME>07:51
Qimingyou can pass '-P count=3' when creating such a receiver07:51
xuhaiweioh, I see07:52
openstackgerritRUIJIE YUAN proposed openstack/senlin: API support node replace
openstackgerritMerged openstack/senlin-dashboard: Fix typo
openstackgerritQiming Teng proposed openstack/senlin: Add config option 'rpc_use_object'
*** zhurong has joined #senlin08:16
*** shu-mutou is now known as shu-mutou-AWAY08:21
yanyanhuhi, Qiming, around?08:24
yanyanhuI checked the irc meeting time slot and found utc0600 is available except Tuesday08:26
yanyanhuthat will 2pm Beijing time and 3pm tokyo time08:26
yanyanhuwill be08:26
yanyanhuhi, xuhaiwei, is that time ok for you?08:26
xuhaiweiyes, it's 11:00 am?08:27
yanyanhuit's 3PM tokyo time08:28
yanyanhu8AM UTC time08:28
yanyanhusorry, 6AM UTC time08:28
xuhaiweii got it08:28
xuhaiweiit's ok08:28
yanyanhuif this time is ok for all people, I will propose to change the weekly irc meeting time08:29
xuhaiweion what day?08:29
yanyanhuTuesday is unavalable08:29
yanyanhuall other four days are ok08:29
yanyanhumaybe on Wednesday?08:29
xuhaiweii am ok08:29
yanyanhuTuesday UTC0600 is now used by doc-install team08:30
yanyanhuI see, will ask other team members08:30
yanyanhuhi, all, is UTC0600 Wednesday a proper time for you guys to join the irc meeting? I have the plan to change our weekly IRC meeting time. If that time slot is ok for all you guys, I will propose the change.08:31
openstackgerritRUIJIE YUAN proposed openstack/senlin: API support node replace
QimingI'm not sure if holding IRC meetings during work time may cause frequent conflict with company meetings08:35
yanyanhuyes, need to confirm with all guys before making the change08:36
Qimingand UTC0600 would be 14:00 pm in China, 02:00 am in US08:37
Qimingwe are totally excluding any guys from other countries to join us, to watch our progress08:37
yanyanhumaybe pick a timeslot in early night of us?08:38
Qimingyou can try this:
ruijiehaha, the next pic is fun08:40
yanyanhuQiming, another possible option is utc0200 which will be 10:am beijing time08:42
yanyanhufor us, it will be 10 pm or 11 pm08:43
yanyanhustill a little late08:43
yanyanhumaybe lets have a further discussion on this topic in next irc meeting08:44
yanyanhuand decide which time most people prefer for the meeting, worktime or night08:44
yanyanhuthen we decide to change the irc meeting time or not08:45
Qimingyup, that would be nice08:45
openstackgerritlvdongbing proposed openstack/senlin: Integrate osprofiler into Senlin
yanyanhuI see. Will add it to meeting agenda08:45
openstackgerritShu Muto proposed openstack/senlin-dashboard: Cleanup .gitignore and tox.ini
openstackgerritQiming Teng proposed openstack/senlin: Add RPC call for passing object as parameters
*** guoshan has quit IRC09:00
*** guoshan has joined #senlin09:01
*** yanyanhu has quit IRC09:08
*** elynn__ has quit IRC09:36
*** elynn__ has joined #senlin09:37
*** elynn__ has quit IRC09:42
*** elynn__ has joined #senlin09:42
*** lixinhui_ has quit IRC09:43
*** openstackstatus has quit IRC09:44
*** openstack has joined #senlin09:49
*** ruijie has quit IRC09:56
*** zhurong has quit IRC10:02
*** openstackstatus has quit IRC10:13
*** openstack has joined #senlin10:17
*** guoshan_ has joined #senlin10:19
*** guoshan has quit IRC10:22
*** guoshan_ has quit IRC10:24
*** gongysh has quit IRC10:56
*** elynn__ has quit IRC11:41
*** R_lixh has quit IRC11:47
*** openstackstatus has quit IRC12:43
*** openstack has joined #senlin12:47
*** Drago has joined #senlin14:35
*** Drago has joined #senlin14:36
*** Drago has quit IRC15:58
*** Drago has joined #senlin16:44
*** Drago has quit IRC17:33
*** heyongli has quit IRC17:40
*** heyongli has joined #senlin17:43
*** Drago has joined #senlin18:45
*** Drago has quit IRC18:45
*** Drago has joined #senlin18:46
*** Drago has quit IRC19:51
*** Drago has joined #senlin19:57
*** Drago has quit IRC21:34

Generated by 2.14.0 by Marius Gedminas - find it at!