Monday, 2016-08-08

*** zhurong has quit IRC00:01
*** mingyu has joined #openstack-smaug00:45
*** mingyu has quit IRC00:49
*** xiangxinyong_ has quit IRC00:54
*** xiangxinyong has joined #openstack-smaug00:59
*** zengyingzhe_ has quit IRC01:03
*** zengyingzhe has joined #openstack-smaug01:10
*** zhurong has joined #openstack-smaug01:12
openstackgerritMerged openstack/smaug: Add description to Scheduled Operation  https://review.openstack.org/35106501:42
*** mingyu has joined #openstack-smaug02:00
*** mingyu has quit IRC02:05
*** yinwei_computer has joined #openstack-smaug02:28
*** mingyu has joined #openstack-smaug03:21
openstackgerritzengchen proposed openstack/smaug: Add suspend/restart operation interface in Operation Engine  https://review.openstack.org/34989003:24
*** mingyu has quit IRC03:25
*** chenying__ has quit IRC03:36
openstackgerritzengchen proposed openstack/smaug: Add update interface for scheduled operation  https://review.openstack.org/34986903:58
*** mingyu has joined #openstack-smaug03:58
*** zhurong has quit IRC04:04
*** mingyu has quit IRC04:04
*** zhurong has joined #openstack-smaug04:05
*** yinwei_computer has quit IRC04:35
openstackgerritOpenStack Proposal Bot proposed openstack/smaug: Updated from global requirements  https://review.openstack.org/35092804:41
*** mingyu has joined #openstack-smaug05:20
*** mingyu has quit IRC05:25
*** mingyu has joined #openstack-smaug05:38
*** mingyu has quit IRC05:45
*** yinwei_computer has joined #openstack-smaug06:19
*** mingyu has joined #openstack-smaug06:27
*** chenying has joined #openstack-smaug06:30
openstackgerritMerged openstack/smaug: Update the 'get' function of ScheduledOperationState  https://review.openstack.org/34944006:40
*** mingyu has quit IRC06:42
*** yuval has joined #openstack-smaug07:06
*** yamamoto has quit IRC07:14
openstackgerritzengchen proposed openstack/smaug: Add suspend/resume operation interface in Operation Engine  https://review.openstack.org/34989007:23
yuvalhey07:25
chenyinghi :007:34
yinwei_computerhi yuval07:35
*** mingyu has joined #openstack-smaug07:36
*** saggi1 has joined #openstack-smaug08:18
*** saggi1 is now known as saggi08:21
*** mingyu has quit IRC08:57
*** mingyu has joined #openstack-smaug08:59
*** chenying has quit IRC09:11
*** chenying has joined #openstack-smaug09:12
*** yamamoto has joined #openstack-smaug09:12
*** yamamot__ has joined #openstack-smaug09:14
*** c00281451 has joined #openstack-smaug09:15
*** c00281451 is now known as zengchen09:15
openstackgerritOpenStack Proposal Bot proposed openstack/smaug: Updated from global requirements  https://review.openstack.org/35092809:16
*** yamamoto has quit IRC09:17
yinwei_computerping yuval09:18
yuvalhey yinwei_computer09:18
yinwei_computerping chenying09:22
yinwei_computeryuval, ying talked to me about the reconstruct patch of work flow.09:22
yinwei_computerBasically, I have reviewed the patch before and I think the patch itself is good.09:22
yinwei_computerBut ying has concern about the cooperation with providers.09:23
yuvalyinwei_computer: what do you mean?09:23
yinwei_computerAs he already has got 1 or 2 companies as potential providers, they are satisfied with simple protection plugin implementation.09:24
yinwei_computerthey don't want to know details of how workflow organized09:25
yinwei_computerso the new plugin is a bit complicated for them.09:25
chenyingyinwei: hi09:26
yinwei_computerWhat I suggested to ying is, shall we have an additional adapter class, say, BaseParallelPlugin?09:26
yinwei_computerthings like that09:26
yinwei_computerwhere 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_computerhi, chenying09:27
yinwei_computerpls. make sure I talked the right thing09:28
yinwei_computerthe concrete plugin for providers remain the same interfaces as current plugin class offers09:29
yuvalyinwei_computer: I'm not sure I understand. In the current design, all tasks run in parallel09:29
yinwei_computerin a work, they only want to implement simple functions09:29
yuvalyinwei_computer: if that is ok for vendors, they can implement one method09:30
chenyingyinwei 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
yuvalOfcourse we have. Currently:09:31
yuval1. All tasks start at the same time. Both VM, image, and volume09:31
yuval2. Current interface requires that protect/restore return a 'status_getter'09:31
yuval3. You want to wrap the new implementation with another class, that mimics the current implementation?09:33
chenyingThe 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 IRC09:35
yinwei_computerI think the point is to shield the work flow flexibility as an 'idiot' mode09:35
*** yamamoto has joined #openstack-smaug09:35
yuvalchenying: what do you mean by prefix, postfix?09:35
yinwei_computeryuval, we all think the flexibility is good for some higher level users and complicated scenarios09:35
yinwei_computerbut as the camera, not everyone prefers to set aperture shutter, etc09:36
yuvalyinwei_computer: I totally understand what you are saying. I'm trying to understand what is your implementation suggestion09:37
yinwei_computershall we provide an 'idiot mode' so in this mode all tasks are parallel and thus users only implement functions09:37
yinwei_computerok, good09:38
yinwei_computerI think a BaseParallelPlugin will do.  What do you think?09:38
yuvalWhat is it? What is its interface?09:39
yuvalchenying: what do you mean by "swap the method with prefix and postfix in base plugins class"?09:39
chenyingFor 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_computerIt's an adapter class, which adapt your new implementation to current interfaces09:40
yuvalchenying: if the name is the issue, we can take care of that09:40
yuvalchenying: 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 IRC09:41
yuvalyinwei_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 implementation09:43
yuvalyinwei_computer: do you think an adapter is required to match vendor implementation or to simplify the new interface?09:44
chenyingyuval: 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
yuvalchenying: 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
yuvalchenying: regarding email to mailing list - I agree that it is vital, but only after the patch is properly reviewed and agreed upon09:47
chenyingyuval: 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 IRC10:03
*** yamamoto has joined #openstack-smaug10:05
*** yamamoto has quit IRC10:05
*** yamamoto has joined #openstack-smaug10:06
chenyingyuval: 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 IRC10:12
*** yamamoto has quit IRC10:33
yuvalchenying: 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
yuvalchenying: 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 it10:35
*** yamamoto has joined #openstack-smaug10:39
*** yamamoto has quit IRC10:51
*** mingyu has quit IRC10:51
*** yamamoto has joined #openstack-smaug10:55
*** yamamoto has joined #openstack-smaug10:56
*** yamamoto has quit IRC11:01
*** yamamoto has joined #openstack-smaug11:03
*** yamamoto has joined #openstack-smaug11:05
*** yamamoto has quit IRC11:10
*** yamamoto has joined #openstack-smaug11:10
*** yamamoto has quit IRC11:26
*** yamamoto has joined #openstack-smaug11:26
*** yamamoto has quit IRC11:31
*** yamamoto has joined #openstack-smaug11:34
*** yamamoto has quit IRC11:34
*** yamamoto has joined #openstack-smaug11:46
*** mingyu has joined #openstack-smaug11:52
*** mingyu has quit IRC11:57
*** mingyu has joined #openstack-smaug12:07
*** yamamoto has joined #openstack-smaug12:12
*** yamamoto has joined #openstack-smaug12:13
*** yamamoto has quit IRC12:14
*** yamamoto has joined #openstack-smaug12:14
*** yamamoto has joined #openstack-smaug12:20
*** yamamoto has quit IRC12:25
*** zhongjun_ has quit IRC12:32
*** zhongjun_ has joined #openstack-smaug12:32
*** yamamoto has joined #openstack-smaug13:24
*** zhurong has joined #openstack-smaug13:27
*** yamamoto has quit IRC13:29
*** zhurong has quit IRC13:31
*** zhurong has joined #openstack-smaug13:32
*** mingyu has quit IRC14:38
*** yuval has quit IRC15:04
*** zhurong has quit IRC15:18
*** xiangxinyong has quit IRC16:28
*** xiangxinyong has joined #openstack-smaug16:29
*** zhongjun_ has quit IRC17:11
*** zhongjun_ has joined #openstack-smaug17:12
*** yamamoto has joined #openstack-smaug17:21
*** yamamoto has quit IRC17:27
*** mingyu has joined #openstack-smaug17:39
*** mingyu has quit IRC17:43
*** mingyu has joined #openstack-smaug17:56
*** mingyu has quit IRC18:39
*** mingyu has joined #openstack-smaug20:25
*** mingyu has quit IRC20:29
*** yamamoto has joined #openstack-smaug21:09
*** yamamoto has quit IRC21:10
*** yamamoto has joined #openstack-smaug21:10
*** yamamoto has quit IRC21:15
*** mingyu has joined #openstack-smaug21:40
*** mingyu has quit IRC21:44
*** yamamoto has joined #openstack-smaug22:26
*** mingyu has joined #openstack-smaug23:10
*** mingyu has quit IRC23:15
*** wanghao_ has joined #openstack-smaug23:37
*** zhurong has joined #openstack-smaug23:46
*** zhurong has quit IRC23:55

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!