Clustered SCSI target using RBD Status » History » Version 1
Jessica Mack, 07/06/2015 10:03 PM
1 | 1 | Jessica Mack | h1. Clustered SCSI target using RBD Status |
---|---|---|---|
2 | |||
3 | h3. Summary |
||
4 | |||
5 | The goal of this project is to modify the Linux target layer, LIO, to be able to support active/active access to a device across multiple nodes running LIO. The changes to LIO are being done in a generic way to allow other cluster aware devices to be used, but our focus is on using RBD. |
||
6 | |||
7 | More info can be found in the Hammer blue print here: |
||
8 | https://wiki.ceph.com/Planning/Blueprints/Hammer/Clustered_SCSI_target_using_RBD |
||
9 | |||
10 | This will be a update on what has been completed and open issues. |
||
11 | |||
12 | h3. Owners |
||
13 | |||
14 | * Name (Affiliation) |
||
15 | * Name (Affiliation) |
||
16 | * Name |
||
17 | |||
18 | h3. Interested Parties |
||
19 | |||
20 | * Name (Affiliation) |
||
21 | * Name (Affiliation) |
||
22 | * Name |
||
23 | |||
24 | h3. Current Status |
||
25 | |||
26 | h3. Detailed Description |
||
27 | |||
28 | Open issues from the Hammer blue print include: |
||
29 | |||
30 | 1. - SCSI task management (TMF) / Unit Attention (UA) / PREEMPT AND ABORT Handling. |
||
31 | |||
32 | This has not yet been worked on since the Hammer discussion. |
||
33 | |||
34 | 2. Configuration and Device State. |
||
35 | |||
36 | - The current plan is to use pacemaker/corosync for the setup and syncing device state across nodes. |
||
37 | |||
38 | - For management, I am looking into implementing a libStorageMgmt (http://sourceforge.net/projects/libstoragemgmt/) plugin, so tools like lsmcli can manage the target. |
||
39 | |||
40 | Both of these need more research and discussion. |
||
41 | |||
42 | h3. Work items |
||
43 | |||
44 | h4. Coding tasks |
||
45 | |||
46 | # Task 1 |
||
47 | # Task 2 |
||
48 | # Task 3 |
||
49 | |||
50 | h4. Build / release tasks |
||
51 | |||
52 | # Task 1 |
||
53 | # Task 2 |
||
54 | # Task 3 |
||
55 | |||
56 | h4. Documentation tasks |
||
57 | |||
58 | # Task 1 |
||
59 | # Task 2 |
||
60 | # Task 3 |
||
61 | |||
62 | h4. Deprecation tasks |
||
63 | |||
64 | # Task 1 |
||
65 | # Task 2 |
||
66 | # Task 3 |