Peer persistence support for HPE 3PAR volumes in Cinder
HPE 3PAR storage systems support a feature named "Peer Persistence". A high-level overview of this function is available here:
Practically, it results in two 3PAR systems that each have storage paths towards the storage client, with active paths for the primary system and "ghost" paths for the secondary. In the event of a problem on the primary node, path status changes and the secondary system seamlessly takes over from the primary, activating the ghost paths.
This mechanism is often used to account for disaster-recovery scenario's in order to minimize impact in case of an outage. Under linux, it is utilized using the multipath tools.
This blueprint aims to support the implementation of the peer persistence feature in cinder.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Ruben de Smet
- Direction:
- Needs approval
- Assignee:
- Ruben de Smet
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Adds peer persistence feature to HPE 3PAR driver
Addressed by: https:/
Adds peer persistence feature to HPE 3PAR driver
Addressed by: https:/
Adds peer persistence feature to HPE 3PAR driver
Gerrit topic: https:/
Addressed by: https:/
Adds peer persistence feature to HPE 3PAR driver
Addressed by: https:/
Adds peer persistence feature to HPE 3PAR driver
Addressed by: https:/
First attempt at a naive implementation for Peer Persistence volumes in the HPE 3PAR driver for Cinder.
Work Items
Work items:
Implement creation of peer persistence volumes: INPROGRESS
Review implementation code: TODO
Validate functionality of cinder driver for non-peer persistent volumes: TODO
Validate creation of peer persistence volumes: TODO
Validate configuration of peer persistence volumes: TODO
Validate high-availability of peer persistence volumes: TODO