Wednesday, 2016-12-28

*** tonyb has quit IRC00:43
*** tonyb has joined #openstack-karbor00:44
*** smile-luobin has joined #openstack-karbor01:57
*** x00350071__ has joined #openstack-karbor02:19
*** zengyingzhe__ has joined #openstack-karbor02:20
*** x00350071_ has quit IRC02:22
*** zengyingzhe_ has quit IRC02:22
*** x00350071__ is now known as edisonxiang02:27
*** yamamoto_ has joined #openstack-karbor02:41
*** Jeffrey4l_ has quit IRC03:03
*** Jeffrey4l_ has joined #openstack-karbor03:03
*** Jeffrey4l_ has quit IRC03:03
*** Jeffrey4l_ has joined #openstack-karbor03:04
*** Jeffrey4l_ has quit IRC03:04
*** Jeffrey4l has joined #openstack-karbor03:04
*** Jeffrey4l has quit IRC03:07
*** Jeffrey4l has joined #openstack-karbor03:07
*** gouthamr has quit IRC04:09
*** yamamoto_ has quit IRC05:29
*** yamamoto_ has joined #openstack-karbor06:26
*** chenying has quit IRC06:41
*** smile-luobin has quit IRC06:47
*** chenying has joined #openstack-karbor06:57
*** yuval has joined #openstack-karbor07:50
*** gouthamr has joined #openstack-karbor08:09
chenyingping saggi08:43
chenyingsaggi hi08:43
openstackgerritchenying proposed openstack/karbor: Add a user_id field for resource plan  https://review.openstack.org/39159508:43
chenyingping yuval08:44
saggichenying: pong08:53
chenyinghi saggi https://review.openstack.org/#/c/391595/ https://review.openstack.org/#/c/388593/ These two patches have been rebased. Do you have any time to review them?08:59
chenyingsaggi:  What's your oppion about caching the extra-info of resources to database?  The scene is that, When I call the protectable api, the volume instances with extra-info about 'Availability Zone' are returned. And then save this extra-info of instances to database table resource when I create a plan.09:05
chenyingsaggi: The  extra-info of instances in plan are also saved to metadata of checkpoint when user execute the volume protection action. So the user can see the extra-info of instances  from the checkpoint API.09:07
openstackgerritOpenStack Proposal Bot proposed openstack/karbor-dashboard: Updated from global requirements  https://review.openstack.org/41540909:08
*** c00281451 has joined #openstack-karbor09:15
*** c00281451 is now known as zengchen09:18
*** gouthamr has quit IRC09:26
chenyingping yuval09:27
saggichenying: chenying, hmm. Does it matter for restore?09:35
chenyingsaggi: I think this scene is only considering to show the detail info about the resources. When user want to restore this checkpoint, he can get some more info about this resource. These info may be usefull for restore action. For example, if he know the 'Availability Zone' of this volume, and he can select a different/right AZ when he want to cross site resotre.09:42
saggiWe can get this information during the dependency graph building09:43
saggiSo it's not that much of an issue09:44
chenyingsaggi: Yes  when user query the checkpoint data,  user also can get this info from rebuilding the dependency graph by calling the protectable api. In karbor dashboard, we can get these.09:53
saggichenying: Did zhonghua tell you I'm coming to visit Chengdu next week?09:54
chenyingsaggi: But from karbor's restapi view, user can not get these info about resource form the response of checkpoint.09:54
chenyingsaggi: :) yes I know. yinwei has tell me that you are in shenzhen now.09:55
saggichenying: We can add it in the response next to the existing {name, id} . It's not complicated. But, again, the user can rely on this information existing09:56
chenyingsaggi: Maybe it is a good solution,09:57
saggiBut it has to be the persisted information not current10:00
saggisince everything in the checkpoint represents the state at the time of protectoin10:00
chenyingsaggi:We are very much looking forward to your visit chengdu next week. Chengdu is a exciting city. It is a famous city in china. :)10:01
chenyingsaggi: everything in the checkpoint represents the state at the time of protectoin. I agree this point.10:02
chenyingsaggi: See you next time, I get off work now.10:04
saggiWe are in meetings for a few more hours10:04
saggienjoy your evening10:04
yuvalping chenying10:17
*** yamamoto_ has quit IRC10:24
*** zengyingzhe_ has joined #openstack-karbor10:39
*** tommylikehu1 has joined #openstack-karbor10:39
*** c00281451 has joined #openstack-karbor10:40
*** tommylikehu has quit IRC10:42
*** tommylikehu1 is now known as tommylikehu10:42
*** zengyingzhe__ has quit IRC10:42
*** zengchen has quit IRC10:42
*** tommylikehu has quit IRC11:03
*** tommylikehu_ has joined #openstack-karbor11:06
*** yamamoto has joined #openstack-karbor11:27
*** zhonghua has quit IRC11:36
*** zhonghua has joined #openstack-karbor11:37
*** yamamoto has quit IRC11:42
*** yamamoto has joined #openstack-karbor12:01
*** tommylikehu_ has quit IRC12:10
*** tommylikehu_ has joined #openstack-karbor12:11
*** tommylikehu_ has quit IRC12:45
*** tommylikehu_ has joined #openstack-karbor12:45
*** zhurong has joined #openstack-karbor12:46
*** yuvalb has quit IRC13:06
*** yuvalb has joined #openstack-karbor13:06
*** yamamoto has quit IRC13:10
*** saggi has quit IRC13:46
*** saggi has joined #openstack-karbor13:47
*** yamamoto has joined #openstack-karbor14:09
*** yamamoto has quit IRC15:04
*** tommylikehu_ has quit IRC15:05
*** zhurong has quit IRC15:11
*** zhangshuai has quit IRC15:23
*** zhangshuai has joined #openstack-karbor15:24
*** yuval has quit IRC15:44
*** yamamoto has joined #openstack-karbor15:47
*** yamamoto has quit IRC15:58
*** yamamoto has joined #openstack-karbor16:04
*** yamamoto has quit IRC16:07
*** yamamoto has joined #openstack-karbor17:08
*** gouthamr has joined #openstack-karbor17:17
*** yamamoto has quit IRC17:18
*** gouthamr has quit IRC17:39
*** zhangshuai has quit IRC18:31
*** zhangshuai has joined #openstack-karbor18:31
*** Jeffrey4l has quit IRC21:34
*** Jeffrey4l has joined #openstack-karbor21:47
*** tommylikehu_ has joined #openstack-karbor23:00

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