Wednesday, 2016-03-09

chenzenggampel:if you online, please let me know. Sorry, i missed yesterday's meeting.01:10
zengyingzheHe'll online afternoon.01:12
xiangxinyongchenying:ping01:26
yinweiishereI missed the meeting too01:56
yinweiishereyesterday was women's day so I went to the cinema ...01:56
*** mingyu has joined #openstack-smaug02:14
openstackgerritzengchen proposed openstack/smaug: Implement rpc interfaces of OperationEngine  https://review.openstack.org/27608102:16
*** chenying has joined #openstack-smaug02:17
openstackgerritWeAreFormalGroup proposed openstack/smaug: Implement cinder protection plugin  https://review.openstack.org/28645802:21
*** smile-luobin has joined #openstack-smaug02:31
*** luobin has quit IRC02:34
openstackgerritxiangxinyong proposed openstack/smaug-dashboard: Add skeleton for the smaug-dashboard  https://review.openstack.org/28972402:49
*** smile-luobin has quit IRC02:50
*** smile-luobin has joined #openstack-smaug02:51
openstackgerritzengchen proposed openstack/smaug: Implement RestAPIs of trigger.  https://review.openstack.org/28640602:55
*** mingyu has quit IRC03:27
*** mingyu has joined #openstack-smaug03:38
*** mingyu has quit IRC03:50
*** mingyu has joined #openstack-smaug04:28
*** mingyu has quit IRC05:28
*** mingyu has joined #openstack-smaug05:43
*** mingyu has quit IRC06:24
*** mingyu has joined #openstack-smaug06:34
*** mingyu has quit IRC06:36
*** mingyu has joined #openstack-smaug06:52
*** smile-luobin has quit IRC07:09
*** smile-luobin has joined #openstack-smaug07:14
*** gampel has joined #openstack-smaug07:21
zengyingzheping xiangxinyong07:23
xiangxinyonghi07:24
yinwei_computeryingzhe, sorry, I still have problem of your protectable layout07:25
yinwei_computerpls. check how to get child image resources of a server through your layout07:25
yinwei_computerping gampel07:26
zengyingzheyinwei_computer, OK, we can talk about it later. I got a issure to confirm with xiangxinyong07:26
zengyingzhesorry07:26
yinwei_computernp07:26
xiangxinyongzengyingzhe: what's wrong?07:27
*** mingyu has quit IRC07:27
zengyingzhexiangxinyong, the protection plugin paramters, UI is asking user to fill for each resource type or each resource instance?07:28
yinwei_computerping saggi07:28
*** mingyu has joined #openstack-smaug07:29
zengyingzheI change an expression. UI support that user can specify parameters for each resource instance?07:32
xiangxinyongzengyingzhe: right07:33
zengyingzheor the instances of one the same type have the same parameters?07:33
xiangxinyongzengyingzhe: so far, we agree this point(this instances of one the same type have the same parameters)07:34
xiangxinyongzengyingzhe: sorry i can not send a email of the fake ui to you07:35
xiangxinyongbut you can glance my lastest email about the smaug ui.07:36
zengyingzhexiangxinyong, that's OK. So the parameters are specified for resource type? not resource instance?07:37
*** smile-luobin has quit IRC07:44
*** smile-luobin has joined #openstack-smaug07:45
yinwei_computerping gampel, pls. check the following two patches: https://review.openstack.org/#/c/287572/, https://review.openstack.org/#/c/285149/07:46
yinwei_computerping saggi, pls. add a pari of interfaces in checkpoint class to write and read resource definitions, then we can call them in protection plugin07:47
yinwei_computera pair, sorry07:47
openstackgerritMerged openstack/smaug: The RESTAPI of resource checkpoints  https://review.openstack.org/28641208:05
openstackgerritzengchen proposed openstack/smaug: RPC client recreates exception object failed  https://review.openstack.org/28968508:12
openstackgerritzengchen proposed openstack/smaug: Implement RestAPIs of Scheduled Operation.  https://review.openstack.org/28703608:12
gampelhi smile-luobin08:13
gampelhi  yinwei_computer: :08:13
gampelsmile-luobin: Please rebase on [1] https://review.openstack.org/#/c/285816/ and we can merge08:14
openstackgerritzengchen proposed openstack/smaug: implement time trigger  https://review.openstack.org/27119608:16
xiangxinyongzengyinzhe: yeah. we can confirm with eran.08:16
smile-luobinOK08:16
xiangxinyongeran: hi08:17
yinwei_computerintegrate smaug to hybrid cloud DR08:21
yinwei_computerintegrate smaug to hybrid cloud DR08:21
yinwei_computerping gampel, pls. check the following two patches: https://review.openstack.org/#/c/287572/, https://review.openstack.org/#/c/285149/08:21
openstackgerritzengchen proposed openstack/smaug: Implement operation manager  https://review.openstack.org/27433908:22
openstackgerritzengchen proposed openstack/smaug: Implement executor of OperationEngine  https://review.openstack.org/28226308:22
openstackgerritzengchen proposed openstack/smaug: Implement RestAPIs of trigger.  https://review.openstack.org/28640608:22
openstackgerritzengchen proposed openstack/smaug: Implement rpc interfaces of OperationEngine  https://review.openstack.org/27608108:22
zengyingzhexiangxinyong, I've check the UI design you sent before. The parameters could be specified for each instance.08:22
zengyingzheSo no problem anymore.08:23
*** smile-luobin has quit IRC08:32
*** smile-luobin has joined #openstack-smaug08:32
zengyingzheyinwei_computer, for the scenario you gave, the parent resource would be a VM, then the image plugin could construct a nova client and use this client to query the VM details, then we could get the image which this VM uses.08:32
openstackgerritYingzhe Zeng proposed openstack/smaug: Implement the ProtectableRegistry  https://review.openstack.org/28178308:42
openstackgerritYingzhe Zeng proposed openstack/smaug: Implement the ProtectableRegistry  https://review.openstack.org/28178308:45
openstackgerritzengchen proposed openstack/smaug: Implement RestAPIs of trigger.  https://review.openstack.org/28640608:46
*** openstackgerrit has quit IRC08:47
*** openstackgerrit has joined #openstack-smaug08:48
openstackgerritzengchen proposed openstack/smaug: RPC client recreates exception object failed  https://review.openstack.org/28968508:48
*** yuval has quit IRC08:49
gampel xiangxinyon: hi08:49
gampelyes08:49
openstackgerritYingzhe Zeng proposed openstack/smaug: Implement cinder protectable plugin  https://review.openstack.org/28561108:52
openstackgerritYingzhe Zeng proposed openstack/smaug: Implement nova protectable plugin  https://review.openstack.org/28654208:54
*** smile-luobin has quit IRC08:58
*** smile-luobin has joined #openstack-smaug08:58
openstackgerritYingzhe Zeng proposed openstack/smaug: Implement the ProtectableRegistry  https://review.openstack.org/28178308:58
openstackgerritYingzhe Zeng proposed openstack/smaug: Implement cinder protectable plugin  https://review.openstack.org/28561109:00
openstackgerritzengchen proposed openstack/smaug: Implement RestAPIs of Scheduled Operation.  https://review.openstack.org/28703609:01
openstackgerritYingzhe Zeng proposed openstack/smaug: Implement nova protectable plugin  https://review.openstack.org/28654209:06
*** mingyu has quit IRC09:08
*** mingyu has joined #openstack-smaug09:12
openstackgerritYingzhe Zeng proposed openstack/smaug: Implement protectable RPC handlers  https://review.openstack.org/28592109:14
openstackgerritYingzhe Zeng proposed openstack/smaug: Implement protectable RPC handlers  https://review.openstack.org/28592109:32
zengyingzhegampel, could you please check https://review.openstack.org/#/c/281783/09:39
zengyingzheand https://review.openstack.org/#/c/285921/09:39
zengyingzhethese are two base patch, many other patches depend on them.09:40
zengyingzheit would be better if they could be merged sooner.09:40
zengyingzhesaggi, please review the patches I mentioned above. Thanks.09:41
yinwei_computeryingzhe, yes, that's the case I don't prefer09:48
yinwei_computerit means the 'image' protectable has to visit its parent resource 'server', and should understand the result of 'get_server'09:49
yinwei_computerit's not a good design for encapsulation09:49
yinwei_computerthe good design principle should be each layer/component should only understand its own data/logic, and there should be an isolation09:50
yinwei_computerIf you adjust the lay out and each protectable only returns its own children not its parent children, say, we have server protectable to return all of its children resources:volume, image, there's no such trouble.09:52
yinwei_computerwhich means, server should only visit nova and should only understand the metadata of server; while image should only visit glance and only understand the metadata of image;09:54
yinwei_computergampel, what do you think?09:54
yinwei_computerin this way, we coupled image protectable tightly with server protectable09:57
zengyingzheall of the plugins are isolated object, we just need to focus on the interfaces provided to outside, and the interfaces return what we want. Does it matter so much how it implements interally>10:02
zengyingzheAnd for project resource, based on your idea, the implementation of projest plugin also must be aware other services like nova and cinder, i think it's got the same problem.10:04
yinwei_computerif the server metadata changes, say, you have to change all of its children protectables which are not server, which sounds weird10:05
yinwei_computerand it's confusing for user to develop them10:05
yinwei_computerprotectables are plugins, which could be replaced and reimplemented by users10:06
yinwei_computerfor project, yes and no.10:06
yinwei_computerthis is because there's no project service in openstack and thus we need list all of its children resources10:07
zengyingzheI don't quite understand why "server metadata changes, say, you have to change all of its children protectables which are not server"10:09
yinwei_computerIf protectable is out internal logic, I don't care how to implement it because user won't change it. Since they are plugins, just have concern on the flexibility.10:10
yinwei_computersay, server metadata changes one field10:10
yinwei_computerit used to be server.image and now it turns to be server.image_id10:11
yinwei_computeryou need change image plugin10:11
zengyingzhehave you seen gampel's reply after your comment. in this way there's a advantage, that if we add a new resource type dependency later, we only need to add a new plugin, no need to modify the parent plugins that already exist.10:17
zengyingzhethis make the future maintenance much easier.10:17
zengyingzhebut what you said also make sense. maybe we'd better pull saggi&gampel in to discuss together.10:18
zengyingzhei'm about go home soon, let's talk about it tomorrow?10:20
*** mingyu has quit IRC10:41
*** smile-luobin has quit IRC10:52
*** gampel has quit IRC11:03
*** chenying has quit IRC11:11
*** chenying has joined #openstack-smaug11:12
*** yuval has joined #openstack-smaug11:42
*** gampel has joined #openstack-smaug12:30
xiangxinyonggampel: sorry for late to reply.12:48
xiangxinyonggampel:zengyingzhe and I have a question about the smaug ui.12:49
xiangxinyonggampel:when we create a protection plan, we need to choose resources.12:50
xiangxinyonggampel:and the parameters need be specified for each resource instance.12:51
xiangxinyonggampel:if the resource type is the same, are the resource instance parameters the same too?12:52
xiangxinyonggampel: e.g. Do two vm instances have the same resource parameters?12:53
*** gampel1 has joined #openstack-smaug13:02
*** gampel has quit IRC13:02
*** chenying_ has joined #openstack-smaug13:37
*** chenying has quit IRC13:40
*** gampel1 has quit IRC14:15
*** gampel has joined #openstack-smaug14:19
*** gampel has quit IRC15:43
yuvalzengyingzhe: hey15:51
yuvalzengyingzhe: in nova protectable plugin, nova's configuration is in server.py. Since that there is no glance->nova mapping - in  glance protectable we need to use nova's client as well, with that configuration.15:52
yuvalzengyingzhe: how about moving the nova and cinder client configuration to a central location?Maybe common.config15:53
yuvalzengyingzhe: plus the nova client version16:04
*** gampel has joined #openstack-smaug16:47
*** gampel has quit IRC19:13
*** gampel has joined #openstack-smaug19:17
*** gampel has left #openstack-smaug19:17
*** gampel has joined #openstack-smaug19:51
*** gampel has quit IRC20:51

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