Thursday, 2016-12-29

*** tommylikehu has joined #openstack-karbor01:18
*** chenying has quit IRC03:04
*** chenying has joined #openstack-karbor03:22
*** tommylikehu has quit IRC04:25
*** tommylikehu has joined #openstack-karbor04:26
openstackgerritchenying proposed openstack/karbor: Generic database Bank implementation  https://review.openstack.org/36582306:25
*** yamamoto has joined #openstack-karbor07:00
*** yamamoto has quit IRC07:02
*** gouthamr has joined #openstack-karbor07:05
*** yamamoto has joined #openstack-karbor07:33
*** yuval has joined #openstack-karbor07:34
yuvalping zhonghua07:35
zhonghuapong yuval07:36
zhonghuahey07:36
*** zengyingzhe__ has joined #openstack-karbor07:40
*** yamamoto has quit IRC07:42
chenyingping yuval07:43
yuvalhey chenying07:43
*** zengyingzhe_ has quit IRC07:44
*** yamamoto has joined #openstack-karbor07:44
chenyingI am doing the work about bugfix. Have you seen this bug?  https://bugs.launchpad.net/karbor/+bug/1574980   need a mechanism to check resource status in plan07:46
openstackLaunchpad bug 1574980 in Karbor "need a mechanism to check resource status in plan" [Medium,Triaged]07:46
*** gouthamr has quit IRC07:48
*** gouthamr has joined #openstack-karbor07:51
*** gouthamr has quit IRC07:58
yuvalchenying: maybe extend the protectable plugin interface?07:59
chenyingyuval: What I want to say, Do we need check the status of resources in the plan creation stage or in the protection execution stage?08:01
chenyingyuval: Checking the status of resources could be done in karbor protection service.  I think vendors will check the status of resource before protecting this resource in their plug-in implementations.08:05
chenyingyuval:  maybe extend the protectable plugin interface?  --- maybe not, this work could be done in the protect/delete/restore interface of plugins.08:07
yuvalchenying: both in the creation stage and in the protection execution08:18
yuvalchenying: there is also a problem with showing a plan when a resource was deleted08:21
yuvalchenying: if a user creates a plan with resource A, then deletes it, trying to '.show()' the plan gives an error08:22
yuvalchenying: this is why I'm for adding a resource status to protectable interface08:22
openstackgerritYuval Brik proposed openstack/karbor: Enable heat plugin in devstack sample and docs  https://review.openstack.org/41563808:27
chenyingyuval: this is why I'm for adding a resource status to protectable interface ---- you mean that adding a status filed for resources database table?08:29
*** tommylikehu_ has quit IRC08:30
yuvalchenying: no08:31
yuvalchenying: I mean, right now if you try so do 'show' on a protectable instance08:31
yuvalchenying: and it is deleted, you get an error08:31
yuvalchenying: there should be a way for the protectable api to handle that case08:32
chenyingyuval: The protectable plugins will return error if to show a deleted resource.08:32
yuvalchenying: I know. This is way trying to view a plan with a deleted resource fails08:33
yuvalchenying: and that is not desired. we want the plan to show, and let us know that the resource is deleted08:33
chenyingyuval: maybe the the back-end of protectable plugins also don't know that resource is invalid or is having been deleted.08:35
yuvalchenying: can you provide an example for such case?08:35
*** tommylikehu_ has joined #openstack-karbor08:42
chenyingyuval: volume protectable plugin call cinderclient to show a provided volume id. If it can not be got form cinder just return error. we don't know the volume is deleted or is a invalid id.08:42
yuvalchenying: it doesn't matter whether it is invalid or deleted. It can be displayed as 'Not Found'. The bottom line is, if the protectable plugin can't find the resource - Karbor can not operate on it08:44
chenyingyuval:  It can be displayed as 'Not Found'. You mean just show the 'Not Found' flag in karbor-dashboard? don't need save this 'Not Found' flag to the resources database table?08:46
yuvalchenying: yes08:48
yuvalchenying: btw, not just the dashboard, the whole rest api of protectables08:49
chenyingyuval: The response of plan API, also show the resources list, may need display the resources as 'Not Found' when it can not been got from protectables API.08:54
yuvalchenying: I don't understand08:55
*** yamamoto has quit IRC09:13
*** tommylikehu_ has quit IRC09:14
*** yamamoto has joined #openstack-karbor09:15
yuvalchenying: ?09:23
chenyingyuval: I mean that when we call plan get restapi to show the detail of a plan, do we need check the status of resources in this plan.09:26
yuvalchenying: yes09:27
chenyingyuval: I note that most of work about the volume plugin refactoring patch have been finished.09:28
chenyingCould we start the refactoring work about nova/glance plugins base on new interfaces?09:28
yuvalchenying: yes :)09:28
chenyingyuval:If you don't mind, I could start the patch about refactoring glance plugin first.09:28
yuvalchenying: the current nova protection plugin needs to be fixed, not just refactored09:28
*** tommylikehu_ has joined #openstack-karbor09:29
chenyingyuval: what is the problom in the nova protection plugin?09:31
yuvalchenying: current nova plugin creates a snapshot of the image09:32
yuvalchenying: this is not desireable. If the server boots from a volume - use the already restored volume. If the server boots from an image - use the already restored image.09:33
chenyingyuval: You mean that we need consider this situation, the server boots from a volume. not from a image?09:37
chenyingyuval:?09:47
yuvalchenying: yes09:47
yuvalchenying: but also, currently nova protection plugin takes a snapshot of the image09:47
yuvalchenying: that's not what we want09:47
*** tonyb has quit IRC10:30
*** lihi has quit IRC10:30
*** tonyb has joined #openstack-karbor10:36
*** lihi has joined #openstack-karbor10:36
*** yamamoto has quit IRC10:40
*** tommylikehu_ has quit IRC10:53
*** tommylikehu_ has joined #openstack-karbor11:04
*** tommylikehu_ has quit IRC11:31
*** yamamoto has joined #openstack-karbor11:40
*** tommylikehu_ has joined #openstack-karbor11:48
*** tommylikehu_ has quit IRC12:02
*** tommylikehu_ has joined #openstack-karbor12:12
*** tommylikehu_ has quit IRC13:20
*** tommylikehu_ has joined #openstack-karbor13:23
*** tommylik_ has joined #openstack-karbor13:41
*** tommylikehu_ has quit IRC13:43
*** yamamoto has quit IRC14:55
*** yamamoto has joined #openstack-karbor15:03
*** yuval has quit IRC15:09
*** tommylik_ has quit IRC15:27
*** yamamoto has quit IRC15:42
*** yamamoto has joined #openstack-karbor16:43
*** yamamoto has quit IRC16:52
*** gouthamr has joined #openstack-karbor18:31
*** Jeffrey4l has quit IRC21:34
*** tommylikehu_ has joined #openstack-karbor22:26
*** tommylikehu_ has quit IRC22:31
*** thx has joined #openstack-karbor22:38
*** thx has left #openstack-karbor22:40
*** tommylikehu_ has joined #openstack-karbor22:43
*** gouthamr has quit IRC22:47
*** tommylikehu_ has quit IRC22:47
*** tommylikehu_ has joined #openstack-karbor22:48
*** tommylikehu_ has quit IRC22:48
*** tommylikehu_ has joined #openstack-karbor22:49
*** tommylikehu_ has quit IRC22:55
*** zhangshuai has quit IRC23:08
*** zhangshuai has joined #openstack-karbor23:08
*** Jeffrey4l has joined #openstack-karbor23:31

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