*** zhurong has quit IRC | 00:01 | |
*** mingyu has joined #openstack-smaug | 00:45 | |
*** mingyu has quit IRC | 00:49 | |
*** xiangxinyong_ has quit IRC | 00:54 | |
*** xiangxinyong has joined #openstack-smaug | 00:59 | |
*** zengyingzhe_ has quit IRC | 01:03 | |
*** zengyingzhe has joined #openstack-smaug | 01:10 | |
*** zhurong has joined #openstack-smaug | 01:12 | |
openstackgerrit | Merged openstack/smaug: Add description to Scheduled Operation https://review.openstack.org/351065 | 01:42 |
---|---|---|
*** mingyu has joined #openstack-smaug | 02:00 | |
*** mingyu has quit IRC | 02:05 | |
*** yinwei_computer has joined #openstack-smaug | 02:28 | |
*** mingyu has joined #openstack-smaug | 03:21 | |
openstackgerrit | zengchen proposed openstack/smaug: Add suspend/restart operation interface in Operation Engine https://review.openstack.org/349890 | 03:24 |
*** mingyu has quit IRC | 03:25 | |
*** chenying__ has quit IRC | 03:36 | |
openstackgerrit | zengchen proposed openstack/smaug: Add update interface for scheduled operation https://review.openstack.org/349869 | 03:58 |
*** mingyu has joined #openstack-smaug | 03:58 | |
*** zhurong has quit IRC | 04:04 | |
*** mingyu has quit IRC | 04:04 | |
*** zhurong has joined #openstack-smaug | 04:05 | |
*** yinwei_computer has quit IRC | 04:35 | |
openstackgerrit | OpenStack Proposal Bot proposed openstack/smaug: Updated from global requirements https://review.openstack.org/350928 | 04:41 |
*** mingyu has joined #openstack-smaug | 05:20 | |
*** mingyu has quit IRC | 05:25 | |
*** mingyu has joined #openstack-smaug | 05:38 | |
*** mingyu has quit IRC | 05:45 | |
*** yinwei_computer has joined #openstack-smaug | 06:19 | |
*** mingyu has joined #openstack-smaug | 06:27 | |
*** chenying has joined #openstack-smaug | 06:30 | |
openstackgerrit | Merged openstack/smaug: Update the 'get' function of ScheduledOperationState https://review.openstack.org/349440 | 06:40 |
*** mingyu has quit IRC | 06:42 | |
*** yuval has joined #openstack-smaug | 07:06 | |
*** yamamoto has quit IRC | 07:14 | |
openstackgerrit | zengchen proposed openstack/smaug: Add suspend/resume operation interface in Operation Engine https://review.openstack.org/349890 | 07:23 |
yuval | hey | 07:25 |
chenying | hi :0 | 07:34 |
yinwei_computer | hi yuval | 07:35 |
*** mingyu has joined #openstack-smaug | 07:36 | |
*** saggi1 has joined #openstack-smaug | 08:18 | |
*** saggi1 is now known as saggi | 08:21 | |
*** mingyu has quit IRC | 08:57 | |
*** mingyu has joined #openstack-smaug | 08:59 | |
*** chenying has quit IRC | 09:11 | |
*** chenying has joined #openstack-smaug | 09:12 | |
*** yamamoto has joined #openstack-smaug | 09:12 | |
*** yamamot__ has joined #openstack-smaug | 09:14 | |
*** c00281451 has joined #openstack-smaug | 09:15 | |
*** c00281451 is now known as zengchen | 09:15 | |
openstackgerrit | OpenStack Proposal Bot proposed openstack/smaug: Updated from global requirements https://review.openstack.org/350928 | 09:16 |
*** yamamoto has quit IRC | 09:17 | |
yinwei_computer | ping yuval | 09:18 |
yuval | hey yinwei_computer | 09:18 |
yinwei_computer | ping chenying | 09:22 |
yinwei_computer | yuval, ying talked to me about the reconstruct patch of work flow. | 09:22 |
yinwei_computer | Basically, I have reviewed the patch before and I think the patch itself is good. | 09:22 |
yinwei_computer | But ying has concern about the cooperation with providers. | 09:23 |
yuval | yinwei_computer: what do you mean? | 09:23 |
yinwei_computer | As he already has got 1 or 2 companies as potential providers, they are satisfied with simple protection plugin implementation. | 09:24 |
yinwei_computer | they don't want to know details of how workflow organized | 09:25 |
yinwei_computer | so the new plugin is a bit complicated for them. | 09:25 |
chenying | yinwei: hi | 09:26 |
yinwei_computer | What I suggested to ying is, shall we have an additional adapter class, say, BaseParallelPlugin? | 09:26 |
yinwei_computer | things like that | 09:26 |
yinwei_computer | where the tasks are organized on parallel by default, and they only provides interfaces to get status, but the BaseParallelPlugin will do other work for them? | 09:27 |
yinwei_computer | hi, chenying | 09:27 |
yinwei_computer | pls. make sure I talked the right thing | 09:28 |
yinwei_computer | the concrete plugin for providers remain the same interfaces as current plugin class offers | 09:29 |
yuval | yinwei_computer: I'm not sure I understand. In the current design, all tasks run in parallel | 09:29 |
yinwei_computer | in a work, they only want to implement simple functions | 09:29 |
yuval | yinwei_computer: if that is ok for vendors, they can implement one method | 09:30 |
chenying | yinwei yuval: I have communicated with several verdors about the interfaces of plugins. So I think we can implement the parallel task in base plugins class, don't need modify the interface of integration plugins. | 09:30 |
yuval | Ofcourse we have. Currently: | 09:31 |
yuval | 1. All tasks start at the same time. Both VM, image, and volume | 09:31 |
yuval | 2. Current interface requires that protect/restore return a 'status_getter' | 09:31 |
yuval | 3. You want to wrap the new implementation with another class, that mimics the current implementation? | 09:33 |
chenying | The prefix and postfix the methods may make the verdors confuse. like activity_protect_parallel. I think we can swap the method with prefix and postfix in base plugins class. | 09:34 |
*** yamamot__ has quit IRC | 09:35 | |
yinwei_computer | I think the point is to shield the work flow flexibility as an 'idiot' mode | 09:35 |
*** yamamoto has joined #openstack-smaug | 09:35 | |
yuval | chenying: what do you mean by prefix, postfix? | 09:35 |
yinwei_computer | yuval, we all think the flexibility is good for some higher level users and complicated scenarios | 09:35 |
yinwei_computer | but as the camera, not everyone prefers to set aperture shutter, etc | 09:36 |
yuval | yinwei_computer: I totally understand what you are saying. I'm trying to understand what is your implementation suggestion | 09:37 |
yinwei_computer | shall we provide an 'idiot mode' so in this mode all tasks are parallel and thus users only implement functions | 09:37 |
yinwei_computer | ok, good | 09:38 |
yinwei_computer | I think a BaseParallelPlugin will do. What do you think? | 09:38 |
yuval | What is it? What is its interface? | 09:39 |
yuval | chenying: what do you mean by "swap the method with prefix and postfix in base plugins class"? | 09:39 |
chenying | For example, last time I communicated with backup software verdors. I tell them only need to know how to implement the plugins with interface create_backup/delete_backup. It very clear. Now I may need to explain why we change the method name in the plugins. | 09:40 |
yinwei_computer | It's an adapter class, which adapt your new implementation to current interfaces | 09:40 |
yuval | chenying: if the name is the issue, we can take care of that | 09:40 |
yuval | chenying: but I don't understand what did you mean by "swap the method with prefix and postfix in base plugins class" | 09:40 |
*** yamamoto has quit IRC | 09:41 | |
yuval | yinwei_computer: I'm trying to understand why we need an adapter class. If it because vendors have already written protection plugins - that is one thing. In the current implementation you can only implement 'parallel' hook and you are doing almost the same as the current implementation | 09:43 |
yuval | yinwei_computer: do you think an adapter is required to match vendor implementation or to simplify the new interface? | 09:44 |
chenying | yuval: I means that the interfaces in plug-ins like create_backup/delete_backup is south-api of smaug. If we change the interface name or some parameters about them. We may think more about it. We may also need notification and explain it by email. | 09:45 |
yuval | chenying: I'm pretty sure we already discussed this specific change to the API. We agreed to go with the current implementation and change it after the fullstack tests are merged. | 09:46 |
yuval | chenying: regarding email to mailing list - I agree that it is vital, but only after the patch is properly reviewed and agreed upon | 09:47 |
chenying | yuval: Your design and patches is Ok technically. like yinwei said So I think we may need an adapter class to adapter framework change. To make verdor have a easy/idiot way implement it. The framework change don't affect them. | 09:56 |
*** zhurong has quit IRC | 10:03 | |
*** yamamoto has joined #openstack-smaug | 10:05 | |
*** yamamoto has quit IRC | 10:05 | |
*** yamamoto has joined #openstack-smaug | 10:06 | |
chenying | yuval: hi yuval. Did you get it? I have the same suggestion about it with yinwei, maybe describe it in a different way. | 10:06 |
*** yinwei_computer has quit IRC | 10:12 | |
*** yamamoto has quit IRC | 10:33 | |
yuval | chenying: ok. What is the purpose of the adapter class? what will it look like? (I mean, technically. Because I want to understand what do you consider as 'easy/idiot') | 10:34 |
yuval | chenying: I understand what you are saying and why you are saying it. I just want to understand what is the gap towards 'easy/idiot'. Maybe we can adjust the current implementation to match it | 10:35 |
*** yamamoto has joined #openstack-smaug | 10:39 | |
*** yamamoto has quit IRC | 10:51 | |
*** mingyu has quit IRC | 10:51 | |
*** yamamoto has joined #openstack-smaug | 10:55 | |
*** yamamoto has joined #openstack-smaug | 10:56 | |
*** yamamoto has quit IRC | 11:01 | |
*** yamamoto has joined #openstack-smaug | 11:03 | |
*** yamamoto has joined #openstack-smaug | 11:05 | |
*** yamamoto has quit IRC | 11:10 | |
*** yamamoto has joined #openstack-smaug | 11:10 | |
*** yamamoto has quit IRC | 11:26 | |
*** yamamoto has joined #openstack-smaug | 11:26 | |
*** yamamoto has quit IRC | 11:31 | |
*** yamamoto has joined #openstack-smaug | 11:34 | |
*** yamamoto has quit IRC | 11:34 | |
*** yamamoto has joined #openstack-smaug | 11:46 | |
*** mingyu has joined #openstack-smaug | 11:52 | |
*** mingyu has quit IRC | 11:57 | |
*** mingyu has joined #openstack-smaug | 12:07 | |
*** yamamoto has joined #openstack-smaug | 12:12 | |
*** yamamoto has joined #openstack-smaug | 12:13 | |
*** yamamoto has quit IRC | 12:14 | |
*** yamamoto has joined #openstack-smaug | 12:14 | |
*** yamamoto has joined #openstack-smaug | 12:20 | |
*** yamamoto has quit IRC | 12:25 | |
*** zhongjun_ has quit IRC | 12:32 | |
*** zhongjun_ has joined #openstack-smaug | 12:32 | |
*** yamamoto has joined #openstack-smaug | 13:24 | |
*** zhurong has joined #openstack-smaug | 13:27 | |
*** yamamoto has quit IRC | 13:29 | |
*** zhurong has quit IRC | 13:31 | |
*** zhurong has joined #openstack-smaug | 13:32 | |
*** mingyu has quit IRC | 14:38 | |
*** yuval has quit IRC | 15:04 | |
*** zhurong has quit IRC | 15:18 | |
*** xiangxinyong has quit IRC | 16:28 | |
*** xiangxinyong has joined #openstack-smaug | 16:29 | |
*** zhongjun_ has quit IRC | 17:11 | |
*** zhongjun_ has joined #openstack-smaug | 17:12 | |
*** yamamoto has joined #openstack-smaug | 17:21 | |
*** yamamoto has quit IRC | 17:27 | |
*** mingyu has joined #openstack-smaug | 17:39 | |
*** mingyu has quit IRC | 17:43 | |
*** mingyu has joined #openstack-smaug | 17:56 | |
*** mingyu has quit IRC | 18:39 | |
*** mingyu has joined #openstack-smaug | 20:25 | |
*** mingyu has quit IRC | 20:29 | |
*** yamamoto has joined #openstack-smaug | 21:09 | |
*** yamamoto has quit IRC | 21:10 | |
*** yamamoto has joined #openstack-smaug | 21:10 | |
*** yamamoto has quit IRC | 21:15 | |
*** mingyu has joined #openstack-smaug | 21:40 | |
*** mingyu has quit IRC | 21:44 | |
*** yamamoto has joined #openstack-smaug | 22:26 | |
*** mingyu has joined #openstack-smaug | 23:10 | |
*** mingyu has quit IRC | 23:15 | |
*** wanghao_ has joined #openstack-smaug | 23:37 | |
*** zhurong has joined #openstack-smaug | 23:46 | |
*** zhurong has quit IRC | 23:55 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!