os-brick: NVMeoF connection agent
The agent is responsible for initiator-side monitoring and self healing of NVMeoF connections and replicated mdraid volumes.
It will initially support block storage exposed by KumoScale volume driver used by NVMeoF connector. It should be implemented such that support can be added for any other block storage that makes use of mdraid on the initiator.
* Probing of storage orchestrator
* Monitor NVMeoF connections and replicated volumes' mdraid states
* Report initiator-side connection and volume events to storage orchestrator
* Connection and replication state re-conciliation
Overview in the following presentation, with an architecture diagram in slide 2:
https:/
Blueprint information
- Status:
- Started
- Approver:
- Gorka Eguileor
- Priority:
- Low
- Drafter:
- Zohar Mamedov
- Direction:
- Approved
- Assignee:
- Zohar Mamedov
- Definition:
- Approved
- Series goal:
- Accepted for zed
- Implementation:
-
Needs Code Review
- Milestone target:
-
zed-1
- Started by
- Brian Rosmaita
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
This is useful because the connection_info stored in Cinder is not updated, but all the volumes it references may have been replaced over time, which would make an attach on instance reboot fail.
