Monday, 2016-03-21

*** x00350071 has quit IRC00:54
*** x00350071 has joined #openstack-smaug00:59
*** x00350071_ has joined #openstack-smaug03:41
*** x00350071 has quit IRC03:44
*** openstackgerrit has quit IRC06:17
*** openstackgerrit_ is now known as openstackgerrit06:17
*** openstackgerrit_ has joined #openstack-smaug06:18
*** openstackgerrit_ is now known as openstackgerrit06:18
*** openstackgerrit_ has joined #openstack-smaug06:19
yinwei_computerping saggi07:18
*** yuval has joined #openstack-smaug07:27
yuvalping chenzeng07:29
saggiyinwei_computer, yinweiishere: pong07:41
yinwei_computerhello saggi07:45
saggiyinwei_computer: How are you?07:45
yinwei_computerlong time not talk to you07:45
yinwei_computergood07:45
yinwei_computerwhat about you?07:45
saggiI'm good, thank you07:46
yinwei_computerhope you will still work on smaug even if you get your job07:46
yinwei_computer:)07:46
yinwei_computerjust want to confirm with the checkpoint collection patch07:46
yinwei_computerwhat's your plan?07:47
saggiyinwei_computer: What job?07:47
yinwei_computerIt's said that you will graduate from school, and you are looking for nice offers07:48
yinwei_computerthe news is out of date?07:48
saggiyinwei_computer: I'm graduating in 6 months but I'm not looking for anything else at the moment. I'll just start working full time.07:50
yinwei_computeroh, that's terrific!07:50
yinwei_computerI'd like to check the checkpoint patch with you, are you free now?07:51
saggiyinwei_computer: Could you send the restore presentation to gample and I.07:51
yinwei_computerwhat restore presentation? the ppt I talked about last week?07:52
saggiyes07:52
yinwei_computernp07:52
yinwei_computerwhat's your mail box?07:52
saggisaggi.miztahi@toganetworks.com07:53
saggisaggi.mizrahi@toganetworks.com07:54
yinwei_computergot it07:55
yinwei_computerI will send it to the mailbox above and eran's huawei mail box07:57
saggiyinwei_computer: about checkpoints07:57
yinwei_computeryes07:58
saggiI sent a very basic patch. After that there are 2 main tasks. Using the leases and serializing the plan.07:58
yinwei_computerI see.07:59
saggiCan you take one? I think using the lease is perfect for you since you know the alogrithm very well.07:59
saggiSince, you helped design it08:00
yinwei_computersure, np08:00
*** gampel1 has joined #openstack-smaug08:00
yinwei_computerso you will first commit the basic one?08:00
saggiYes, so we can work on top of it together.08:00
yinwei_computerand we will work based on your patch?08:00
saggiyes08:00
yinwei_computerthat's good08:00
saggiI will do the plan serialization to the checkpoint since I already wrote the tree implementation so I know it well.08:00
yinwei_computeranother issue I want to confirm with you is08:01
yinwei_computerwhat interface do you think the protection plugin could use to save the information, like backup id, image url stored in bank, or anything else required in save_info_schema?08:02
yinwei_computerthose information should be saved into checkpoint08:02
yinwei_computerper resource08:03
yinwei_computerand should be read from checkpoint during restoration08:03
saggiThe checkpoint file will contain the plan and full resource tree. This means that we hall all the IDs.08:05
saggiEach plugin will get a BankSection at /plugindata/<checkpoint_id>/<resiource_id> where it will write whatever it wants.08:05
saggiWhen we get the saved info we will give that section to each plugin and let it read the data and return the dict.08:05
saggiThe checkpoint file is like and index to all the rest of the data which will be spread out. This will allow multiple plugins to modify data without needing to synchronize their writes since the use different "namespaces"08:06
yinwei_computerdo you mean in this way, each protection plugin will write directly to bank under the key /plugindata/<checkpoint_id>/<resiource_id> ? they don't need first update this info to checkpoint and then commit checkpoint?08:08
saggiIt's not a key, it's a prefix. This is what the BankSection is for.08:08
saggiIt could have any number of objects but will all have the same prefix.08:09
yinwei_computerok, got it. what about read? checkpoint won't load those info from bank to memory, but each protection plugin will read directly from bank by them selves?08:10
yinwei_computerand each plugin is free to organize keys under this prefix?08:10
saggiThey get a BankSection which means they always treat everything as root.08:11
yinwei_computerlast question is how to get this prefix or how to get this bank section?08:12
saggiwhen the pluing will write to key "/volumeid" it will actually write to /plugindata/<checkpoint_id>/<resource_id>/volumeid.08:12
saggiBefore passing the context to the plugin. The provider puts the appropriate BankSection in the context.08:12
saggicontext.bank_section = BankSection(self._bank, "/plugin_data/%s/%s" % (checkpoint_id, resource_id))08:13
saggiThe provider will also set it for RO\RW08:13
saggiThat way the plugin doesn't know about namespaces.08:14
saggiOnly the provider08:14
yinwei_computerhmm, I see08:14
saggiWhen the plugins does context.bank_section.list_objects() it will get all the objects in the namespace.08:14
saggiSince this is how the section works08:15
saggiIt prefixes everything08:15
saggiSo the plugin can do whatever it wants.08:15
yinwei_computerwhat about to have checkpoint object to return the bank section of each resource? like a static method of checkpoint?08:15
saggiSure, that's good too.08:16
saggiIt will be better since it already knows the checkpoint id.08:16
yinwei_computerok08:16
yinwei_computeryes08:16
yinwei_computeranother issue I want to confirm with you is the resource graph08:16
yinwei_computerdo you mean the plan will also persist the resource graph?08:17
yinwei_computerjust to make sure what we persisted is the actual dependency resource graph instead of a set of top resources08:17
saggiNo, the checkpoint will. And it will be the entire resource graph.08:18
yinwei_computerok, then I have no problem here.08:18
saggiyinwei_computer: :)08:19
yinwei_computerso your basic patch is ready, right?08:19
yinwei_computerthen I will give a +1, so you can merge. and then we can work upon it.08:19
yinwei_computerBTW, luobin has a patch about graph walker listener, are you free to review it?08:22
yinwei_computersaggi: https://review.openstack.org/#/c/287572/08:24
saggiyinwei_computer: it is ready08:25
saggiyinwei_computer: I will look at the patch08:25
yinwei_computersaggi, Liu an has also committed a patch, which made a common task flow mechanism for task builder: https://review.openstack.org/#/c/285149/08:26
yinwei_computerhope you can take a look at these two patches when you get time08:26
yinwei_computerthen we can start debugging protection ASAP08:26
*** gampel2 has joined #openstack-smaug08:54
*** gampel1 has quit IRC08:56
*** yinweiishere has quit IRC08:59
*** CrayZee has quit IRC09:28
*** CrayZee has joined #openstack-smaug09:29
*** x00350071_ has quit IRC10:22
*** x00350071 has joined #openstack-smaug10:24
*** gampel1 has joined #openstack-smaug11:58
*** gampel2 has quit IRC12:00
*** zengyingzhe has quit IRC12:06
openstackgerritYingzhe Zeng proposed openstack/smaug: Implement the ProtectableRegistry  https://review.openstack.org/28178312:16
*** gampel2 has joined #openstack-smaug12:30
*** gampel1 has quit IRC12:32
*** x00350071 is now known as xiangxinyong14:54
openstackgerritMerged openstack/smaug-dashboard: Add skeleton for the smaug-dashboard  https://review.openstack.org/28972415:52
openstackgerritMerged openstack/smaug: Implement the common logic for service client  https://review.openstack.org/29152816:00
*** yuval has quit IRC16:03
openstackgerritMerged openstack/smaug: Implement Glance service client  https://review.openstack.org/29211916:11
openstackgerritYuval Brik proposed openstack/smaug: Implement Nova service client  https://review.openstack.org/29153216:26
openstackgerritYuval Brik proposed openstack/smaug: Implement Cinder service client  https://review.openstack.org/29153516:29
*** gampel2 has quit IRC16:33
openstackgerritYuval Brik proposed openstack/smaug: Implement Cinder service client  https://review.openstack.org/29153516:41
*** gampel1 has joined #openstack-smaug18:50
*** gampel1 has quit IRC20:28
*** gampel1 has joined #openstack-smaug20:28
*** gampel1 has quit IRC22:28
*** openstackgerrit has quit IRC23:03
*** openstackgerrit_ is now known as openstackgerrit23:03
*** openstackgerrit has quit IRC23:03
*** openstackgerrit_ has joined #openstack-smaug23:03
*** openstackgerrit_ is now known as openstackgerrit23:04
*** openstackgerrit_ has joined #openstack-smaug23:08

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