Difference between revisions of "Cinder Backend Activity Attributes"
(Cinder Backend Activity Attributes) |
(→Cinder Backend Activity Attributes) |
||
| Line 4: | Line 4: | ||
For Cinder this would typically be an iSCSI target or an NFS server. | For Cinder this would typically be an iSCSI target or an NFS server. | ||
| − | Volume Drivers have a great deal of flexibility on how to perform specific functions, which typically involves replicating the content of a volume or snapshot to somewhere. The different possible activities, and how their implementations can very is discussed in [[ | + | Volume Drivers have a great deal of flexibility on how to perform specific functions, which typically involves replicating the content of a volume or snapshot to somewhere. The different possible activities, and how their implementations can very is discussed in [[Cinder_Backend_Activities]]. |
Revision as of 20:21, 25 September 2013
Cinder Backend Activity Attributes
A Cinder Backend Activity is some process, thread, job or state machine which is launched by a Cinder Volume Driver on another machine that is not directly under Compute's control. For Cinder this would typically be an iSCSI target or an NFS server.
Volume Drivers have a great deal of flexibility on how to perform specific functions, which typically involves replicating the content of a volume or snapshot to somewhere. The different possible activities, and how their implementations can very is discussed in Cinder_Backend_Activities.
