| *** yizhihui has joined #openstack-smaug | 00:18 | |
| *** zhurong has joined #openstack-smaug | 01:10 | |
| *** iceyao has joined #openstack-smaug | 01:18 | |
| *** zhurong has quit IRC | 02:39 | |
| *** zhurong has joined #openstack-smaug | 02:40 | |
| *** iceyao_ has joined #openstack-smaug | 03:12 | |
| *** iceyao has quit IRC | 03:16 | |
| *** yamamoto_ has joined #openstack-smaug | 03:33 | |
| *** zhurong has quit IRC | 04:07 | |
| *** zhurong has joined #openstack-smaug | 04:12 | |
| *** zhonghua-lee has quit IRC | 05:17 | |
| *** zhonghua-lee has joined #openstack-smaug | 05:17 | |
| *** iceyao_ has quit IRC | 06:13 | |
| *** iceyao has joined #openstack-smaug | 06:13 | |
| *** yuval has joined #openstack-smaug | 06:37 | |
| yuval | hey all | 06:37 |
|---|---|---|
| chenying | hi | 06:48 |
| zhonghua-lee | hi | 06:52 |
| zhonghua-lee | https://etherpad.openstack.org/p/smaugmascot | 06:55 |
| zhonghua-lee | please edit it if you have any optional mascot for this project | 06:56 |
| xiangxinyong | hi | 07:12 |
| *** zhangshuai has joined #openstack-smaug | 07:12 | |
| *** zengyingzhe has quit IRC | 07:22 | |
| zhonghua-lee | saggi:ping | 07:22 |
| *** zengyingzhe has joined #openstack-smaug | 07:22 | |
| xiangxinyong | yuval: good morning | 07:58 |
| *** zhangshuai has quit IRC | 08:00 | |
| *** zhangshuai has joined #openstack-smaug | 08:00 | |
| *** zhangshuai_ has joined #openstack-smaug | 08:02 | |
| *** zhangshuai has quit IRC | 08:02 | |
| yuval | xiangxinyong: good after noon | 08:11 |
| xiangxinyong | yuval:) how are you? | 08:12 |
| yuval | xiangxinyong: very well, you? | 08:12 |
| xiangxinyong | better. you know I got the hit from the football game. | 08:13 |
| yuval | xiangxinyong: did you win? | 08:14 |
| xiangxinyong | :( | 08:14 |
| xiangxinyong | I guess we will win in the next game. | 08:17 |
| openstackgerrit | zengchen proposed openstack/smaug: Add a new executor for Operation Engine service https://review.openstack.org/350446 | 08:29 |
| xiangxinyong | yuval: about this feature: https://etherpad.openstack.org/p/scheduledoperation | 08:31 |
| xiangxinyong | yuval: if we don't filter checkpoints by plan, I guess we can only stor the checkpoint id into scheduledoperation | 08:33 |
| xiangxinyong | yuval: how do you think about that? | 08:33 |
| yuval | xiangxinyong: how? where to store it? | 08:36 |
| chenying | ping saggi | 08:37 |
| xiangxinyong | yuval: I am not sure where to store it. When the operation engine service execute a operation, it will call the interface "create chekckpoint" | 08:37 |
| xiangxinyong | and the response of "create checkpoint" includes some informations about the checkpoint | 08:38 |
| yuval | usually we get the checkpoint id, and then we can query the checkpoint by it | 08:40 |
| yuval | and get additioal info | 08:40 |
| xiangxinyong | yeah. | 08:41 |
| xiangxinyong | in the present db tables. I guess only "scheduled_operation"->"operation_definition" and "scheduled_operation_logs"->"extend_info" can store the checkpoint id. | 08:41 |
| xiangxinyong | But i think these two fileds are not the best place to store the checkpoint id. | 08:41 |
| chenying | xiangxinyong: +1 | 08:41 |
| yuval | yep, not very good places | 08:42 |
| yuval | what if we have two operation engine services? | 08:43 |
| chenying | yuval: You konw we have talked about the new API operation log | 08:43 |
| chenying | yuval: There will be database table operations_log to save every recourd of create checkpoint calling. | 08:44 |
| saggi | chenying: pong | 08:46 |
| saggi | zhonghua-lee: pong | 08:46 |
| yuval | chenying: wait, are you speaking about logs of the protection service? | 08:47 |
| chenying | saggi: Maybe we need pick up the design of operation log API. What's your opinion about it? | 08:47 |
| chenying | yuval: I talk about the operation log API. Do we need save every action operation( protect/delete/) log? | 08:50 |
| chenying | log=record. | 08:50 |
| yuval | chenying: I know you speak about operation log, but you said to save every record of create checkpoint, which is from protection service. Just want to understand what you mean | 08:50 |
| saggi | https://review.openstack.org/#/c/350121/ | 08:51 |
| saggi | For those who missed it | 08:51 |
| chenying | saggi: I see this spec. I think it is ok. I can implement it. | 08:54 |
| saggi | then +1 it :) | 08:56 |
| openstackgerrit | zengchen proposed openstack/smaug: Encapsulate smaug client in Operation Engine https://review.openstack.org/310394 | 08:57 |
| xiangxinyong | saggi: we are discuss where to store the checkpoint information when the operation engine trigger a create checkpoint request. | 08:59 |
| chenying | saggi: as your design If I also want to save scheduled-operation-id to userdata That mean define the user-data field like this: | 09:00 |
| chenying | { | 09:00 |
| chenying | ... | 09:00 |
| chenying | "user-data": { | 09:00 |
| chenying | "smaug-created-by": "operation-engine", | 09:00 |
| chenying | "smaug-scheduled-operation-id":"cf56bd3e-97a7-4078-b6d5-f36246333fd9", | 09:00 |
| chenying | } | 09:00 |
| chenying | } | 09:00 |
| xiangxinyong | saggi: I discuss this with yuval and chenying. we all think these two place are not the best place to store checkpoint info. "scheduled_operation"->"operation_definition" and "scheduled_operation_logs"->"extend_info" | 09:01 |
| * saggi is thinking... | 09:01 | |
| xiangxinyong | saggi: do you have some suggestions? | 09:01 |
| xiangxinyong | since we don't filter checkpoints by plan at the Newton | 09:02 |
| saggi | The main issue is that we have an operation that want's to save information it can query later. | 09:03 |
| xiangxinyong | yep | 09:03 |
| saggi | How do other project handle plugins needing their own tables? | 09:04 |
| xiangxinyong | ? | 09:05 |
| xiangxinyong | do you mean to add a new table to record this checkpoint information per scheduledoperation? | 09:05 |
| xiangxinyong | I write a new table structure here. https://etherpad.openstack.org/p/scheduledoperation | 09:08 |
| xiangxinyong | or we filter checkpoints by plan in the Restful API? | 09:10 |
| chenying | yuval: The original requirement about operation log is from smaug horizon. xinyong think we need a global page or api to show every operation(protect/delete/restore) record and its status(error/available). | 09:11 |
| chenying | yuval: you know we can query the protect operation record from checkpoint api. query the restore operation record from resotre api. But we cann't query the delete operation record at present. | 09:15 |
| *** smile-luobin_ has quit IRC | 09:33 | |
| *** smile-luobin has joined #openstack-smaug | 09:34 | |
| *** zhangshuai_ has quit IRC | 09:40 | |
| *** yamamoto_ has quit IRC | 09:41 | |
| *** zhurong has quit IRC | 10:13 | |
| *** yamamoto has joined #openstack-smaug | 10:17 | |
| *** yamamoto has quit IRC | 10:22 | |
| *** yamamoto has joined #openstack-smaug | 10:23 | |
| *** yamamoto has quit IRC | 10:28 | |
| *** garryfan has joined #openstack-smaug | 10:33 | |
| *** garryfan has quit IRC | 10:34 | |
| *** garryfan has joined #openstack-smaug | 10:44 | |
| *** iceyao has quit IRC | 10:45 | |
| *** saggi has quit IRC | 10:50 | |
| *** yamamoto has joined #openstack-smaug | 10:55 | |
| *** yizhihui has quit IRC | 11:03 | |
| *** garryfan has quit IRC | 11:05 | |
| *** yamamoto has quit IRC | 11:11 | |
| *** yamamoto has joined #openstack-smaug | 11:54 | |
| *** yamamoto has quit IRC | 11:59 | |
| *** yamamoto has joined #openstack-smaug | 12:00 | |
| *** yamamoto has quit IRC | 12:05 | |
| *** yamamoto has joined #openstack-smaug | 12:11 | |
| *** zhurong has joined #openstack-smaug | 12:33 | |
| *** iceyao has joined #openstack-smaug | 12:41 | |
| *** yamamoto has quit IRC | 12:49 | |
| *** yamamoto has joined #openstack-smaug | 13:13 | |
| *** zhurong has quit IRC | 13:15 | |
| *** zhurong has joined #openstack-smaug | 13:16 | |
| *** zengyingzhe_ has joined #openstack-smaug | 13:22 | |
| *** zengyingzhe has quit IRC | 13:25 | |
| *** zhurong has quit IRC | 13:25 | |
| *** yamamoto has quit IRC | 13:26 | |
| *** zhurong has joined #openstack-smaug | 13:27 | |
| *** saggi has joined #openstack-smaug | 13:33 | |
| *** zhurong has quit IRC | 13:48 | |
| *** zhurong has joined #openstack-smaug | 13:50 | |
| *** zhurong has quit IRC | 13:57 | |
| *** zhurong has joined #openstack-smaug | 13:58 | |
| *** yamamoto has joined #openstack-smaug | 14:26 | |
| *** yamamoto has quit IRC | 14:33 | |
| *** iceyao has quit IRC | 14:39 | |
| *** yuval has quit IRC | 15:01 | |
| *** zhurong has quit IRC | 15:33 | |
| *** saggi has quit IRC | 16:07 | |
| *** xiangxinyong has quit IRC | 16:25 | |
| *** xiangxinyong has joined #openstack-smaug | 16:25 | |
| *** zhongjun_ has quit IRC | 16:53 | |
| *** zhongjun_ has joined #openstack-smaug | 16:55 | |
| *** xiangxinyong has quit IRC | 16:56 | |
| *** smile-luobin has quit IRC | 16:56 | |
| *** xiangxinyong has joined #openstack-smaug | 16:57 | |
| *** zengyingzhe_ has quit IRC | 16:58 | |
| *** zengyingzhe has joined #openstack-smaug | 17:00 | |
| *** openstackgerrit_ has joined #openstack-smaug | 17:06 | |
| *** openstackgerrit_ has quit IRC | 17:08 | |
| *** xiangxinyong_ has joined #openstack-smaug | 17:36 | |
| *** xiangxinyong has quit IRC | 17:39 | |
| *** zengchen has quit IRC | 18:13 | |
| *** gampel has joined #openstack-smaug | 18:16 | |
| *** zhonghua-lee has quit IRC | 19:14 | |
| *** zhonghua-lee has joined #openstack-smaug | 19:15 | |
| *** gampel has quit IRC | 19:57 | |
| *** gampel has joined #openstack-smaug | 20:24 | |
| *** gampel has quit IRC | 20:44 | |
| *** yamamoto has joined #openstack-smaug | 21:09 | |
| *** yamamoto has quit IRC | 21:18 | |
| *** yamamoto has joined #openstack-smaug | 22:29 | |
| *** yamamoto_ has joined #openstack-smaug | 22:31 | |
| *** yamamoto has quit IRC | 22:31 | |
| *** zhurong has joined #openstack-smaug | 23:45 | |
| *** zhongjun_ has quit IRC | 23:47 | |
| *** zhongjun_ has joined #openstack-smaug | 23:48 | |
| *** zhurong has quit IRC | 23:54 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!