Base Zone Driver is responsible to manage access control using FC zoning Vendor specific implementations should extend this class to provide concrete implementation for add_connection and delete_connection interfaces.
Related Flags
| zoning_policy: | Used by: class: ‘FCZoneDriver’. Defaults to ‘none’ |
|---|---|
| zone_driver: | Used by: class: ‘FCZoneDriver’. Defaults to ‘none’ |
Bases: cinder.zonemanager.fc_common.FCCommon
Interface to manage Connection control during attach/detach.
Add connection control.
Abstract method to add connection control. All implementing drivers should provide concrete implementation for this API. :param fabric: Fabric name from cinder.conf file :param initiator_target_map: Mapping of initiator to list of targets Example initiator_target_map:
- {
- ‘10008c7cff523b01’: [‘20240002ac000a50’, ‘20240002ac000a40’]
}
Note that WWPN can be in lower or upper case and can be ‘:’ separated strings
Delete connection control.
Abstract method to remove connection control. All implementing drivers should provide concrete implementation for this API. :param fabric: Fabric name from cinder.conf file :param initiator_target_map: Mapping of initiator to list of targets Example initiator_target_map:
- {
- ‘10008c7cff523b01’: [‘20240002ac000a50’, ‘20240002ac000a40’]
}
Note that WWPN can be in lower or upper case and can be ‘:’ separated strings
Get SAN context for end devices.
Abstract method to get SAN contexts for given list of end devices All implementing drivers should provide concrete implementation for this API. :param fabric: Fabric name from cinder.conf file :param initiator_target_map: Mapping of initiator to list of targets Example initiator_target_map: [‘20240002ac000a50’, ‘20240002ac000a40’] Note that WWPN can be in lower or upper case and can be ‘:’ separated strings