| *** gampel1 has quit IRC | 01:18 | |
| *** gampel has joined #openstack-smaug | 05:43 | |
| *** WANG_Feng has quit IRC | 06:36 | |
| *** WANG_Feng has joined #openstack-smaug | 06:36 | |
| *** gampel has quit IRC | 06:39 | |
| openstackgerrit | yinwei proposed openstack/smaug: Basic design doc for Protection Service https://review.openstack.org/261455 | 06:54 |
|---|---|---|
| openstackgerrit | yinwei proposed openstack/smaug: Basic design doc for Protection Service https://review.openstack.org/261455 | 07:06 |
| *** gampel has joined #openstack-smaug | 07:15 | |
| zengyingzhe | saggi, are you there? | 07:55 |
| chenzeng | hi,gampel. does the OperationEngine have another functions except triggering the protection operation, such as tracking the status of protection operation? thanks. | 08:26 |
| saggi | zengyingzhe: now i am | 08:29 |
| zengyingzhe | Can you add the Task definition to your pluggable_protection_provider.svg design? | 08:39 |
| zengyingzhe | I see yinwei has designed the Task class in her patch, are those the agreement you guys reached? | 08:41 |
| zengyingzhe | https://review.openstack.org/#/c/261455/4/doc/images/protection-service/class-diagram.png,unified | 08:41 |
| chenzeng | saggi: does the OperationEngine have another functions except triggering the protection operation, such as tracking the status of protection operation? thanks | 08:53 |
| chenzeng | saggi:do we need to add the ability of extending the OperationEngine nodes in the version 1. I think we can add it in the next version. | 08:57 |
| saggi | chenzeng: It needs to track and manage high level transactions. | 09:00 |
| saggi | chenzeng: For example, multiple deletions | 09:00 |
| saggi | chenzeng: A checkpoint is an atomic entity, but if a task requires operations on multiple checkpoints it will require multiple operations in the workflow engine that will have to be tracked. | 09:01 |
| zengyingzhe | saggi, I don't see why a task need to operate on multiple checkpoints. | 09:11 |
| zengyingzhe | Can you give us a instance? | 09:12 |
| saggi | zengyingzhe: Delete all checkpoints older than 10 days. | 09:12 |
| *** wangliuan has joined #openstack-smaug | 09:12 | |
| zengyingzhe | For the instance of deleting checkpoints, what status we need to track, which checkpoints are deleted already? or in deleting progress? | 09:19 |
| zengyingzhe | Something like this? | 09:19 |
| chenzeng | saggi:sorry. can you describe the functions of OperationEngine more clearly. I can't understand the scenario you said. | 09:23 |
| saggi | Lets say you have a policy to only keep checkpoints for one year. So when the deletion triggers it might need to delete more than one checkpoint. We will need to track all the deletions in Smaug. | 09:25 |
| zengyingzhe | Track what info exactly? What checkpoints already deleted and what in deleting progress? | 09:27 |
| saggi | Yes | 09:28 |
| saggi | Smaug will supply the information about progress for the specific task | 09:28 |
| zengyingzhe | So that user can query this info? | 09:28 |
| saggi | yes | 09:28 |
| saggi | The ProtectionService will track the single operation's status through the provider. | 09:29 |
| saggi | So for policies that requires a single checkpoint will only need to handle errors and cases where the trigger was missed. | 09:31 |
| saggi | But for policies that require more than one checkpoint operation it will need to track that. | 09:31 |
| zengyingzhe | You said this tracked by ProtectionService? | 09:34 |
| saggi | Also the OperationEngine will need to track the log of tirggered operations and their results. | 09:34 |
| saggi | ProtectionService tracks a single checkpoint operation. | 09:34 |
| saggi | When you create a checkpoint. You will get the progress information from the checkpoint objects. | 09:35 |
| saggi | But if you want to create a checkpoint and then delete the oldest one (so you only have N checkpoints) you will need higher order logic. | 09:35 |
| saggi | This will need to be defined in the OperationEngine | 09:35 |
| saggi | Since this is where higher order logic is defined. | 09:36 |
| saggi | zengyingzhe: ok? | 09:37 |
| zengyingzhe | You mean OperationEngine tracks progress info for operation, and ProtectionService tracks progress info for checkpoint, their fineness different? | 09:37 |
| chenzeng | saggi:what the meaning of " higher order logic"? | 09:39 |
| saggi | chenzeng: Policies that are composed of atomic operations. | 09:43 |
| saggi | Think of a calculator that has the Add(a,b). | 09:43 |
| saggi | You can define Pow(a, b) or Mult(a, b) using Add(a, b). | 09:43 |
| saggi | Add() is the atomic operation, Pow() and Mult() are higher order logic since they use low level Add() | 09:43 |
| chenzeng | saggi:you mean OperationEngin need track the result of each atomic operation? | 09:46 |
| saggi | Yes and also compose them. For example if you want to have 10 checkpoints at once you need to create a new checkpoint and only after the creation was successful delete the 11th checkpoint. | 09:47 |
| saggi | This logic is in the operation subclass. So we don't need to define all the policies now. But we do need to design the infra to allow operations to store status and transaction so that adding new policies is easy. | 09:48 |
| saggi | chenzeng: ? | 10:03 |
| chenzeng | saggi: sorry. I am discussing with zengyinzhe now. | 10:08 |
| saggi | chenzeng: no problem, just wanted to make sure you didn't miss this just because I didn't quote your nick. | 10:12 |
| chenzeng | saggi:ok. thanks. | 10:13 |
| *** wangliuan has quit IRC | 10:16 | |
| *** WANG_Feng has quit IRC | 12:44 | |
| *** WANG_Feng has joined #openstack-smaug | 12:45 | |
| gampel | Hi yinwei: | 12:58 |
| *** gampel1 has joined #openstack-smaug | 14:17 | |
| *** gampel has quit IRC | 14:19 | |
| *** gampel has joined #openstack-smaug | 14:20 | |
| *** gampel1 has quit IRC | 14:22 | |
| *** gampel1 has joined #openstack-smaug | 14:23 | |
| *** gampel has quit IRC | 14:26 | |
| *** WANG_Feng has quit IRC | 15:05 | |
| *** WANG_Feng has joined #openstack-smaug | 15:06 | |
| *** saggi has quit IRC | 15:28 | |
| *** saggi has joined #openstack-smaug | 16:04 | |
| *** gampel1 has quit IRC | 16:07 | |
| *** gampel has joined #openstack-smaug | 18:27 | |
| *** gampel1 has joined #openstack-smaug | 20:27 | |
| *** gampel has quit IRC | 20:31 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!
