| *** huntxu has joined #openstack-qinling | 01:13 | |
| *** caoyuan has joined #openstack-qinling | 01:27 | |
| *** caoyuan_ has joined #openstack-qinling | 01:33 | |
| *** caoyuan has quit IRC | 02:49 | |
| *** caoyuan has joined #openstack-qinling | 03:58 | |
| *** caoyuan_ has quit IRC | 04:06 | |
| *** caoyuan_ has joined #openstack-qinling | 04:08 | |
| *** ukinau has joined #openstack-qinling | 04:33 | |
| ukinau | anyone here? | 04:33 |
|---|---|---|
| lxkong | ukinau: yeah | 04:33 |
| lxkong | ukinau: can i help you? | 04:33 |
| ukinau | Hi, I just happened to see the presentation about Qinling and I thought it's similar to what we are thinking to do | 04:34 |
| ukinau | but I wanted to know if you guys have any plan to integration openstack resource event as trigger for function for Qinling | 04:35 |
| lxkong | ukinau: what do you mean by 'openstack resource event' | 04:35 |
| lxkong | ceilometer or something? | 04:35 |
| lxkong | ukinau: qinling can integrate with Aodh with any code change | 04:36 |
| ukinau | what we are thinking is to allow the end-user to specify the code and event based on openstack-notification appearing on message bus | 04:36 |
| lxkong | ukinau: something like this: https://docs.openstack.org/qinling/latest/user/aodh.html | 04:36 |
| lxkong | ukinau: may i know your company name if you don't mind? | 04:37 |
| ukinau | oh this "event data" include notification emitted by each component. I thought that event indicate something new entity. | 04:39 |
| ukinau | i don't mind, I'm from LINE. | 04:40 |
| lxkong | ukinau: as long as you have the event data, you can trigger qinling function. It's up to you for how to trigger that, either by some alarm defined by your user, or manually by yourself | 04:41 |
| ukinau | We were thinking to implement such a system by ourselves, and if we do support multi tenancy we do need to store event data for each project, do you know aodh consider the multitenancy ? | 04:45 |
| lxkong | ukinau: yes, aodh is what you want | 04:46 |
| lxkong | and qinling can be integrated with aodh very well | 04:47 |
| lxkong | aodh allows the end user to define their own alarm based on the notification of their own resources | 04:47 |
| ukinau | that's great :) I will take a look. and also Qinling support the external data store for code? | 04:48 |
| lxkong | ukinau: what do you mean by 'external data store'? | 04:48 |
| lxkong | ukinau: for now, qinling only supports either you upload you code file/package, or you stored your code in Swift, or even your docker image | 04:49 |
| ukinau | github or s3, we don't want to have user defined source code in our side and I'm thinking we can drop version stuff instead | 04:49 |
| lxkong | ukinau: no support for github or s3, but github is a good use case, we could consider supporting that | 04:50 |
| lxkong | ukinau: your contribution is also welcomed | 04:50 |
| lxkong | ukinau: i have to head off now, leave message to me and keep stay in this channel, i will reply you when i'm available later on | 04:51 |
| ukinau | thanks for your help! | 04:51 |
| lxkong | ukinau: you're welcome | 04:51 |
| *** ukinau has quit IRC | 06:09 | |
| *** caoyuan_ has quit IRC | 09:18 | |
| *** lxkong_ has joined #openstack-qinling | 09:53 | |
| *** wangyuxin has joined #openstack-qinling | 09:59 | |
| *** lxkong has quit IRC | 10:01 | |
| *** yuxin_ has quit IRC | 10:01 | |
| *** lxkong_ is now known as lxkong | 10:01 | |
| *** caoyuan has quit IRC | 10:15 | |
| *** huntxu has quit IRC | 11:09 | |
| *** caoyuan has joined #openstack-qinling | 11:44 | |
| *** caoyuan_ has joined #openstack-qinling | 15:24 | |
| *** caoyuan_ has quit IRC | 15:33 | |
| *** caoyuan has quit IRC | 15:37 | |
| *** caoyuan has joined #openstack-qinling | 16:41 | |
| *** caoyuan has quit IRC | 16:46 | |
| *** caoyuan has joined #openstack-qinling | 22:56 | |
| *** caoyuan has quit IRC | 23:05 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!