| *** yuanying_ has joined #senlin | 00:03 | |
| *** yuanying has quit IRC | 00:06 | |
| *** yuanying_ has quit IRC | 00:07 | |
| *** elynn has joined #senlin | 00:09 | |
| *** elynn has quit IRC | 00:21 | |
| *** catintheroof has quit IRC | 00:23 | |
| *** catintheroof has joined #senlin | 00:24 | |
| *** catintheroof has quit IRC | 00:28 | |
| *** elynn has joined #senlin | 00:31 | |
| *** devlaps has quit IRC | 00:37 | |
| *** devlaps has joined #senlin | 00:38 | |
| *** yuanying has joined #senlin | 01:04 | |
| *** dinghh has quit IRC | 01:07 | |
| *** dinghh has joined #senlin | 01:12 | |
| *** zhurong has joined #senlin | 01:14 | |
| *** dinghh has quit IRC | 01:16 | |
| *** guoshan has joined #senlin | 01:24 | |
| *** dinghh has joined #senlin | 01:24 | |
| *** zhurong has quit IRC | 01:25 | |
| *** zhurong has joined #senlin | 01:26 | |
| *** dinghh has quit IRC | 01:30 | |
| *** zhurong has quit IRC | 01:34 | |
| *** zhurong has joined #senlin | 01:35 | |
| *** chohoor has joined #senlin | 01:37 | |
| *** fabian4 has quit IRC | 01:40 | |
| *** dinghh has joined #senlin | 01:43 | |
| *** fabian4 has joined #senlin | 01:43 | |
| *** yanyanhu has joined #senlin | 01:48 | |
| openstackgerrit | Merged openstack/senlin-dashboard: Following patch for angular cluster table https://review.openstack.org/407323 | 01:51 |
|---|---|---|
| *** shu-mutou-AWAY is now known as shu-mutou | 02:01 | |
| openstackgerrit | Aaron Ding proposed openstack/senlin: Correct the installation doc, fix path of openrc https://review.openstack.org/407485 | 02:03 |
| *** lxinhui has joined #senlin | 02:04 | |
| openstackgerrit | RUIJIE YUAN proposed openstack/senlin: fields object support webhook trigger https://review.openstack.org/407806 | 02:19 |
| *** guoshan has quit IRC | 02:31 | |
| *** guoshan has joined #senlin | 02:32 | |
| *** elynn has quit IRC | 02:46 | |
| *** elynn has joined #senlin | 02:48 | |
| *** yuanying has quit IRC | 02:58 | |
| *** guoshan has quit IRC | 03:06 | |
| *** guoshan has joined #senlin | 03:07 | |
| openstackgerrit | RUIJIE YUAN proposed openstack/senlin: engine service support webhook-trigger2 https://review.openstack.org/407832 | 03:33 |
| ruijie | http://logs.openstack.org/15/407515/1/check/gate-senlin-dsvm-tempest-integration-nv/f9037fb/console.html#_2016-12-06_14_21_47_885324 | 03:34 |
| ruijie | the gate was broken? | 03:34 |
| *** Drago1 has quit IRC | 03:37 | |
| openstackgerrit | Merged openstack/senlin: Get both event drivers into action https://review.openstack.org/406595 | 03:42 |
| *** yuanying has joined #senlin | 03:43 | |
| Qiming | ruijie, could be this https://review.openstack.org/#/c/407274/1 | 03:46 |
| *** yuanying has quit IRC | 03:48 | |
| *** yuanying has joined #senlin | 03:49 | |
| *** yuanying has quit IRC | 03:53 | |
| *** chohoor has quit IRC | 03:53 | |
| *** chohoor has joined #senlin | 03:54 | |
| *** xuhaiwei has joined #senlin | 03:54 | |
| *** devlaps has quit IRC | 03:58 | |
| *** guoshan has quit IRC | 04:03 | |
| *** zhurong has quit IRC | 04:27 | |
| *** yuanying has joined #senlin | 04:40 | |
| *** elynn has quit IRC | 05:03 | |
| *** guoshan has joined #senlin | 05:04 | |
| *** guoshan has quit IRC | 05:08 | |
| *** yuanying has quit IRC | 05:13 | |
| *** yuanying has joined #senlin | 05:13 | |
| *** zhenguo_ has joined #senlin | 05:14 | |
| *** zhenguo has quit IRC | 05:15 | |
| *** zhenguo_ is now known as zhenguo | 05:15 | |
| *** zhurong has joined #senlin | 05:27 | |
| *** zhurong has quit IRC | 05:30 | |
| *** zhurong has joined #senlin | 05:31 | |
| yanyanhu | hi, lxinhui, around? | 05:43 |
| lxinhui | hi, yanyanhu | 05:47 |
| lxinhui | I am here | 05:47 |
| lxinhui | my laptop crashed in the weekend for new VMware VPN, jus recover everything | 05:49 |
| yanyanhu | lxinhui, sigh... | 05:57 |
| yanyanhu | sorry just talked with a colleague | 05:58 |
| yanyanhu | about this patch, https://review.openstack.org/#/c/402296/ | 05:58 |
| yanyanhu | I think it looks good. Just I have the same question as Michael about the location that event is generated, I guess we should emit event in "update_health" method? | 06:00 |
| lxinhui | According to the spec | 06:02 |
| lxinhui | of lbaasv2 | 06:02 |
| lxinhui | all the details of different member of lbaas pool will be reported by stats | 06:03 |
| yanyanhu | lxinhui, you mean health status is just a subset of stats? | 06:04 |
| *** guoshan has joined #senlin | 06:04 | |
| lxinhui | health is different API | 06:05 |
| lxinhui | what we want is the details of different member ndoe | 06:05 |
| lxinhui | such as alive, dead, or reconfiged | 06:05 |
| lxinhui | by reading the code, you will find nowdays the method of udate_db will do the rpc call | 06:06 |
| lxinhui | of neutron_lbaas to update the db with the latest details collected from lbaas listener | 06:06 |
| lxinhui | what we want is to get such information directly instead of read DB | 06:07 |
| yanyanhu | yes, that makes sense | 06:07 |
| yanyanhu | just I noticed both UpdateStatsDb and UpdateHealthDb define a method "emit" | 06:08 |
| yanyanhu | so I was wondering if we only care about health status, maybe we should event_notifier.emit in UpdateHealthDB.emit rather than UpdateStatsDB.emit | 06:08 |
| *** guoshan has quit IRC | 06:09 | |
| yanyanhu | actually I'm not very clear about the difference between this health status and stats :) | 06:09 |
| lxinhui | Yes | 06:09 |
| yanyanhu | based on the comment embedded in the code | 06:10 |
| yanyanhu | I guess health status is included in stats | 06:10 |
| lxinhui | that depends on who will call udpdatehalthDB | 06:10 |
| yanyanhu | and stats contains more information like "ereq", "conns", etc. | 06:10 |
| yanyanhu | but health is only about status, e.g. UP, ONLINE, etc. of pool, member, and listener | 06:11 |
| yanyanhu | lxinhui, you mean? | 06:12 |
| lxinhui | Sorry I have a meeting | 06:12 |
| lxinhui | will ping you after that | 06:12 |
| yanyanhu | sure | 06:12 |
| yanyanhu | thanks a lot :) | 06:12 |
| *** guoshan has joined #senlin | 06:24 | |
| *** lxinhui_ has joined #senlin | 06:30 | |
| *** lxinhui has quit IRC | 06:34 | |
| *** zhurong has quit IRC | 07:01 | |
| *** zhurong has joined #senlin | 07:02 | |
| *** yuanying has quit IRC | 07:05 | |
| *** yuanying has joined #senlin | 07:17 | |
| *** edisonxiang has joined #senlin | 07:39 | |
| edisonxiang | Qiming: hello | 07:39 |
| Qiming | hi | 07:39 |
| edisonxiang | Qiming: sorry to trouble you. Could you tell me how to publish the Senlin's API-ref? | 07:43 |
| Qiming | it is already published | 07:44 |
| edisonxiang | yeah. | 07:44 |
| Qiming | http://developer.openstack.org/api-ref/clustering/ | 07:44 |
| edisonxiang | could you tell me how to do that? | 07:44 |
| edisonxiang | thanks | 07:44 |
| Qiming | it is a gate job | 07:46 |
| edisonxiang | OK. thanks | 07:48 |
| Qiming | lemme find the patch | 07:49 |
| edisonxiang | :) | 07:49 |
| edisonxiang | you are so nice | 07:49 |
| Qiming | a long history ... | 07:53 |
| Qiming | https://review.openstack.org/#/c/314832/ | 07:53 |
| Qiming | finally found it | 07:53 |
| edisonxiang | great | 07:57 |
| edisonxiang | thanks Qiming | 07:57 |
| *** zhurong has quit IRC | 08:00 | |
| *** zhurong has joined #senlin | 08:01 | |
| Qiming | np | 08:02 |
| *** yuanying has quit IRC | 08:08 | |
| edisonxiang | :) | 08:17 |
| lxinhui_ | yanyanhu | 08:19 |
| lxinhui_ | still there？ | 08:19 |
| Qiming | saw him alive, :D | 08:25 |
| Qiming | vivid | 08:25 |
| ruijie | :) | 08:32 |
| openstackgerrit | Kenji Ishii proposed openstack/senlin-dashboard: Add create cluster action https://review.openstack.org/403472 | 08:35 |
| openstackgerrit | Qiming Teng proposed openstack/senlin: Remove 'InvalidParameter' exception type https://review.openstack.org/407932 | 08:36 |
| yanyanhu | hi, lxinhui_ sorry just noticed your message | 08:48 |
| yanyanhu | hi, xuhaiwei, around? | 08:52 |
| xuhaiwei | yes | 08:53 |
| yanyanhu | hi, about the proposal to Tacker | 08:54 |
| openstackgerrit | Merged openstack/senlin-dashboard: Add create cluster action https://review.openstack.org/403472 | 08:54 |
| xuhaiwei | yes? | 08:54 |
| yanyanhu | maybe we can have a quick sync before talking to Tacker team? | 08:54 |
| yanyanhu | I assume we will join their next weekly meeting in Dec.14 :) | 08:54 |
| xuhaiwei | I have summarized it in this spec https://review.openstack.org/#/c/352943/ | 08:55 |
| yanyanhu | yes, I believe all the team are interested on it :0 | 08:55 |
| xuhaiwei | briefly speaking, We will make Senlin as a driver for vnf scaling | 08:56 |
| yanyanhu | but some ones may still not quite understand the detail | 08:56 |
| yanyanhu | yes, that's the goal | 08:56 |
| xuhaiwei | yanyanhu, shall we introduce senlin again to the team? | 08:56 |
| openstackgerrit | Qiming Teng proposed openstack/senlin: Remove 'ProfileTypeNotMatch' exception type https://review.openstack.org/407938 | 08:57 |
| yanyanhu | xuhaiwei, umm, maybe not, unless some ones from Tacker team want to listen it | 08:57 |
| yanyanhu | xuhaiwei, maybe we can make a quick call on Thursday or Friday? if it's convenient for you | 08:57 |
| Qiming | oh, haiwei, we have done that back in Barcelona | 08:58 |
| xuhaiwei | yes, I just want to share the idea of how to integrating senlin to tacker | 08:58 |
| Qiming | we tried very hard to educate Tacker team on the scope, capability and status of Senlin | 08:58 |
| Qiming | agree that a discussion to get everyone onto the same page is important | 08:59 |
| *** yuanying has joined #senlin | 08:59 | |
| xuhaiwei | yes, Qiming, so I think we dont need to introduce what is senlin again | 08:59 |
| Qiming | I don't think there is a need | 08:59 |
| yanyanhu | yes, so maybe we can sync up what we want to express in that meeting | 08:59 |
| xuhaiwei | just talk about how to integrate | 08:59 |
| yanyanhu | to better convince them | 08:59 |
| yanyanhu | and also make Senlin team better understand Tacker :) | 09:00 |
| Qiming | right, it is a IRC meeting, no time to walk everyone through senlin | 09:00 |
| Qiming | yes, good point | 09:00 |
| Qiming | we need to listen and understand what their concerns | 09:00 |
| yanyanhu | yes | 09:00 |
| xuhaiwei | yanyanhu, if you read the spec, you can understand what is going to be done | 09:00 |
| Qiming | haiwei, personally, I'm not that worried what could be done, I'm more interested in what should be done | 09:01 |
| xuhaiwei | generally speaking, the goal should be the scalability and HA of vnf | 09:01 |
| Qiming | I mean, what are their requirements, explicitly or implicitly expressed ... | 09:02 |
| yanyanhu | xuhaiwei, yes, I have read it. Just still not quite clear about the translation part :) I guess I need to learn some basic conception about VDU | 09:02 |
| yanyanhu | and also the translation of TOSCA | 09:02 |
| xuhaiwei | the scalability and HA can be controlled by senlin scaling-policy and ha-policy | 09:03 |
| xuhaiwei | I think that's why senlin meets Tacker's need | 09:03 |
| Qiming | there are basically two tech solutions: 1. have translator translates everything into Heat template, then tacker invokes Senlin indirectly as a resource type, that is already doable, according to Sahdev, PTL of tosca parser | 09:03 |
| Qiming | 2. have tosca parser translate high-level specifications (HA, scaling, etc) into Senlin policy specs directly, then Tacker interacts with Senlin directly | 09:04 |
| Qiming | I'm more opt in for the 2nd approach because Tacker will really benefit from the rich APIs Senlin exposes | 09:05 |
| xuhaiwei | yanyanhu, the translation part needs some jobs then, currently heat-translator has supported translation of senlin scaling policy, but tacker team doesnt allow new resources in their template, I have to translate the template in Tacker again instead of using heat-translator directly | 09:05 |
| Qiming | but I understand Tacker team's concern about the feasiblity of solution 2, they don't know that translation is doable or not, or anyone will help get that done | 09:06 |
| Qiming | another implicit concern could be that Tacker wants to manage their dependencies to other services to a minimum | 09:06 |
| yanyanhu | xuhaiwei, I see. So they prefer to manage all resources (including senlin cluster) using Heat in current stage | 09:07 |
| yanyanhu | including senlin cluster/policy | 09:07 |
| xuhaiwei | Qiming, exactly as you said, just one thing need to mention, that is Tacker already has their scaling policy, so senlin's policy translation by heat-translator can not be used directly | 09:07 |
| Qiming | "doesn't allow new resources in their template", you mean the high-level TOSCA specification? | 09:07 |
| Qiming | at which level Tacker's scaling policy sits? is it above Heat template, or below that? | 09:08 |
| xuhaiwei | Qiming, yes, Tacker defined their own scaling policy in TOSCA template already | 09:08 |
| xuhaiwei | above it | 09:08 |
| Qiming | yanyanhu, I think the team there is still struggling | 09:08 |
| Qiming | xuhaiwei, if it is above it, it is irrelevant | 09:08 |
| Qiming | it will be translated to heat policy resource type or senlin policy spec anyway | 09:09 |
| xuhaiwei | Qiming, they are not struggling I think | 09:09 |
| Qiming | okay, then they will be regretting | 09:09 |
| xuhaiwei | Qiming, that is not a big problem, senlin scaling policy can be under tacker scaling policy type, it just a policy name imo | 09:10 |
| Qiming | the key point is ... Heat is not designed to be a tool for operators | 09:10 |
| yanyanhu | so, that's why we need to translate Tocsa template to Heat template first, then use it to define Senlin profile. | 09:10 |
| yanyanhu | sorry, s/we/they :) | 09:10 |
| Qiming | exactly, xuhaiwei, so we don't have to express the 'senlin' name in their high-level policy spec | 09:10 |
| xuhaiwei | yes, we dont need to | 09:10 |
| Qiming | just when tacker turns those definitions into something real, it can be translated to heat ones or senlin ones | 09:11 |
| Qiming | we won't be able to convince them away from heat | 09:11 |
| xuhaiwei | Qiming, you are right | 09:11 |
| xuhaiwei | in Tacker all the things are done by heat, including senlin | 09:11 |
| Qiming | yanyanhu, maybe I'm too eager to see them succeed | 09:12 |
| yanyanhu | :) | 09:12 |
| xuhaiwei | senlin is just managing their vnfs after vnf are created | 09:12 |
| Qiming | okay, they will realize, soon, they they will change their deployment | 09:12 |
| yanyanhu | we both, for that means we succeed as well if they use senlin to manage their cluster :) | 09:12 |
| Qiming | and the only way to do that, for them, is 'heat stack-update' | 09:12 |
| Qiming | senlin is just a tool | 09:13 |
| Qiming | it is not designed for a specific business use case | 09:13 |
| Qiming | so ... we'd better prepared for that, :) | 09:13 |
| *** dinghh1 has joined #senlin | 09:14 | |
| *** dinghh has quit IRC | 09:14 | |
| Qiming | that is why I am so eager to see tacker succeed, magnum succeed, zun succeed, megh...war succeed | 09:14 |
| yanyanhu | haha | 09:15 |
| xuhaiwei | Qiming, yanyanhu, though senlin scaling policy can not be added in Tosca template directly, other senlin policies can be added directly, that means we should support these policy translation in heat-translator | 09:15 |
| Qiming | they succeeded because they are using senlin for resource pool management, ... that's my dream | 09:15 |
| Qiming | TOSCA templates already hardcoded heat policy? | 09:15 |
| yanyanhu | xuhaiwei, that is a work in heat-translator? | 09:15 |
| Qiming | I believe all other policies, including scaling policy, specification was derived from senlin | 09:16 |
| Qiming | we helped shape that standard | 09:16 |
| xuhaiwei | Qiming, yes, Tacker already difined their scaling policy | 09:16 |
| Qiming | in TOSCA? | 09:16 |
| xuhaiwei | yes | 09:16 |
| Qiming | then why we want to change that for senlin's purpose? | 09:17 |
| xuhaiwei | Tacker's scaling policy is derived from TOSCA scaling policy | 09:17 |
| Qiming | it is not generic enough? | 09:17 |
| Qiming | okay, that is fine | 09:17 |
| Qiming | that means it can be translated to either heat or senlin scaling policy | 09:17 |
| Qiming | just that in senlin's design, we don't include the "alarm" part | 09:18 |
| xuhaiwei | senlin scaling policy is also derived from TOSCA scaling policy, so senlin's policy is conflicting with Tacker's one | 09:18 |
| Qiming | we felt that inclusion a stupid constraint | 09:18 |
| Qiming | xuhaiwei, that is where I was confused | 09:18 |
| Qiming | "Tacker's scaling policy is derived from TOSCA scaling policy" | 09:19 |
| Qiming | "senlin scaling policy is also derived from TOSCA scaling policy, so senlin's policy is conflicting with Tacker's one" | 09:19 |
| Qiming | why? | 09:19 |
| xuhaiwei | maybe TOSCA allows many types of scaling policies | 09:19 |
| Qiming | they should do that IMO | 09:19 |
| Qiming | do you mean there is a workflow like this? | 09:19 |
| Qiming | TOSCAL scaling policy -> Tacker scaling policy -> Heat Scaling policy? | 09:20 |
| yanyanhu | I guess not? | 09:20 |
| xuhaiwei | Tacker scaling policy = Heat scaling policy imo | 09:20 |
| Qiming | that was my guess | 09:20 |
| xuhaiwei | just the type is changed | 09:21 |
| yanyanhu | IMO, it should be TOSCA scaling policy -> Heat Scaling policy or TOSCA scaling policy -> Senlin scaling policy | 09:21 |
| Qiming | so we are not talking about tacker's scaling policy | 09:21 |
| xuhaiwei | yes | 09:21 |
| xuhaiwei | you both are right | 09:21 |
| Qiming | it is about two translations: TOSCAL->Heat, TOSCAL-Senlin | 09:21 |
| Qiming | yes | 09:21 |
| Qiming | then there is no conflict | 09:21 |
| Qiming | the 2nd translation is not there yet, but we can get help from the translator team easily | 09:22 |
| Qiming | it is trivial | 09:22 |
| xuhaiwei | but in Tacker every resources are Tacker types | 09:22 |
| Qiming | that is fine | 09:23 |
| Qiming | under their roof, follow their design | 09:23 |
| Qiming | problem is? | 09:23 |
| xuhaiwei | no problem | 09:23 |
| xuhaiwei | just follow tacker's scaling policy type, make senlin as a driver, that will be ok | 09:24 |
| Qiming | exactly ... | 09:24 |
| xuhaiwei | senlin scaling policy and heat scaling policy are two drivers of tacker scaling policy | 09:24 |
| yanyanhu | I see | 09:24 |
| yanyanhu | it's more clear for me now :) | 09:24 |
| Qiming | fahongbao | 09:25 |
| xuhaiwei | hope tacker team will feel happy about that :) | 09:25 |
| yanyanhu | -_-! | 09:25 |
| yanyanhu | yes, hope so | 09:25 |
| yanyanhu | so lets push it to move on step by step | 09:25 |
| xuhaiwei | the source code is not difficult i think, I have started this job by refactoring the existing code in Tacker | 09:26 |
| yanyanhu | I believe once they get better understanding of Senlin, they will try to use it to support more functionality | 09:27 |
| yanyanhu | great | 09:27 |
| yanyanhu | we will also join that meeting in Dec.14, and help you answer their question :) | 09:27 |
| yanyanhu | and also listen :P | 09:27 |
| xuhaiwei | thanks yanyanhu | 09:27 |
| yanyanhu | my pleasure | 09:28 |
| openstackgerrit | RUIJIE YUAN proposed openstack/senlin: fields object support webhook trigger https://review.openstack.org/407806 | 09:41 |
| openstackgerrit | RUIJIE YUAN proposed openstack/senlin: engine service support webhook-trigger2 https://review.openstack.org/407832 | 09:41 |
| openstackgerrit | RUIJIE YUAN proposed openstack/senlin: api support webhook-trigger2 https://review.openstack.org/407971 | 09:41 |
| openstackgerrit | RUIJIE YUAN proposed openstack/senlin: kill dead code in engine service https://review.openstack.org/407973 | 09:44 |
| openstackgerrit | RUIJIE YUAN proposed openstack/senlin: kill dead code in engine service and rpc https://review.openstack.org/407973 | 09:46 |
| *** zhurong has quit IRC | 10:03 | |
| *** guoshan has quit IRC | 10:42 | |
| *** yanyanhu has quit IRC | 10:46 | |
| *** openstackgerrit has quit IRC | 11:32 | |
| *** openstackgerrit has joined #senlin | 11:42 | |
| *** ChanServ sets mode: +v openstackgerrit | 11:42 | |
| openstackgerrit | Shu Muto proposed openstack/senlin-dashboard: Add node create/update actions https://review.openstack.org/396975 | 11:42 |
| *** guoshan has joined #senlin | 11:43 | |
| *** shu-mutou is now known as shu-mutou-AWAY | 11:47 | |
| *** guoshan has quit IRC | 11:47 | |
| *** catintheroof has joined #senlin | 11:55 | |
| *** chohoor has quit IRC | 11:58 | |
| *** catintheroof has quit IRC | 12:32 | |
| *** catintheroof has joined #senlin | 12:32 | |
| *** catintheroof has quit IRC | 12:37 | |
| *** guoshan has joined #senlin | 12:44 | |
| *** guoshan has quit IRC | 12:48 | |
| *** catintheroof has joined #senlin | 12:54 | |
| *** guoshan has joined #senlin | 13:04 | |
| *** catinthe_ has joined #senlin | 13:14 | |
| *** guoshan has quit IRC | 13:15 | |
| *** catintheroof has quit IRC | 13:16 | |
| *** lxinhui_ has quit IRC | 13:28 | |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/senlin: Updated from global requirements https://review.openstack.org/408114 | 13:40 |
| *** catintheroof has joined #senlin | 14:02 | |
| *** catinthe_ has quit IRC | 14:04 | |
| openstackgerrit | Merged openstack/senlin: Fix profile create - call subclass methods https://review.openstack.org/407401 | 14:28 |
| *** guoshan has joined #senlin | 15:17 | |
| *** guoshan has quit IRC | 15:21 | |
| *** Drago1 has joined #senlin | 15:23 | |
| *** catintheroof has quit IRC | 15:26 | |
| *** catintheroof has joined #senlin | 15:26 | |
| *** catintheroof has quit IRC | 15:31 | |
| *** catintheroof has joined #senlin | 15:57 | |
| *** guoshan has joined #senlin | 16:18 | |
| *** guoshan has quit IRC | 16:22 | |
| *** devlaps has joined #senlin | 16:43 | |
| *** guoshan has joined #senlin | 17:18 | |
| *** guoshan has quit IRC | 17:23 | |
| *** dinghh has joined #senlin | 17:41 | |
| *** dinghh1 has quit IRC | 17:42 | |
| *** guoshan has joined #senlin | 18:19 | |
| *** guoshan has quit IRC | 18:24 | |
| *** guoshan has joined #senlin | 20:21 | |
| *** guoshan has quit IRC | 20:25 | |
| *** guoshan has joined #senlin | 21:21 | |
| *** guoshan has quit IRC | 21:26 | |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/senlin: Updated from global requirements https://review.openstack.org/408114 | 21:31 |
| *** catintheroof has quit IRC | 21:37 | |
| *** catintheroof has joined #senlin | 21:38 | |
| *** catintheroof has quit IRC | 21:42 | |
| *** guoshan has joined #senlin | 22:22 | |
| *** guoshan has quit IRC | 22:27 | |
| *** guoshan has joined #senlin | 23:23 | |
| *** guoshan has quit IRC | 23:27 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!