Reference counter for protected snapshots » History » Version 1
Jessica Mack, 06/23/2015 08:46 PM
1 | 1 | Jessica Mack | h1. Reference counter for protected snapshots |
---|---|---|---|
2 | |||
3 | h3. Summary |
||
4 | |||
5 | For application dynamically/frequently creating/updating later cloned virtual machine |
||
6 | template it may be useful to run periodic protected snapshots garbage collection of no |
||
7 | longer used templates i.e. protected snapshots whit no attached clones. |
||
8 | This currently implies scanning the cluster for potential clones like "list children" |
||
9 | does which is a potentially expensive operation. In this case, a clone reference counter |
||
10 | would be perfectly fine to decide whether the snap may be unprotected. |
||
11 | |||
12 | Previously protected snapshots could fallback to the "list children" behavior. Any call |
||
13 | to "list children" could possibly init the reference counter on these snapshots. |
||
14 | |||
15 | h3. Owners |
||
16 | |||
17 | * Jean-Tiare Le Bigot (jean-tiare.le-bigot@ovh.net) |
||
18 | * Name (Affiliation) |
||
19 | * Name |
||
20 | |||
21 | h3. Interested Parties |
||
22 | |||
23 | * Loic Dachary <loic@dachary.org> |
||
24 | * Name (Affiliation) |
||
25 | * Name |
||
26 | |||
27 | h3. Current Status |
||
28 | |||
29 | Removing protected RBD snapshots is potentially extremely expensive as we need to scan the whole cluster for linked clones |
||
30 | |||
31 | h3. Detailed Description |
||
32 | |||
33 | h3. Work items |
||
34 | |||
35 | h4. Coding tasks |
||
36 | |||
37 | # add ref counter in image header |
||
38 | # add compatibility layer / lazy creation for snapshots created earlier |
||
39 | # Task 3 |
||
40 | |||
41 | h4. Build / release tasks |
||
42 | |||
43 | # Task 1 |
||
44 | # Task 2 |
||
45 | # Task 3 |
||
46 | |||
47 | h4. Documentation tasks |
||
48 | |||
49 | # Task 1 |
||
50 | # Task 2 |
||
51 | # Task 3 |
||
52 | |||
53 | h4. Deprecation tasks |
||
54 | |||
55 | # Task 1 |
||
56 | # Task 2 |
||
57 | # Task 3 |