Hyper-V Fibre Channel support
At the moment, the Hyper-V driver supports attaching volumes only via iSCSI or SMB. In many cases, using FC based topologies might be desired.
This blueprint proposes adding Fibre Channel support for the Hyper-V driver.
Blueprint information
- Status:
- Complete
- Approver:
- John Garbutt
- Priority:
- Low
- Drafter:
- Lucian Petrut
- Direction:
- Approved
- Assignee:
- Lucian Petrut
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Deferred
- Milestone target:
- None
- Started by
- Completed by
- Matt Riedemann
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Hyper-V: Add Fibre Channel support
Please note this blueprint will delayed until the M release if it is not in the NeedsCodeReview state (with all the code up for review) before July 16th, and merged by July 30th. We expect to re-open master for the M release in September. For more information, please see: https:/
--johnthetubaguy 15th July 2015
Unapproved for liberty due to the Non-Priority Feature Proposal Freeze. --johnthetubaguy 16th July 2015
Gerrit topic: https:/
Addressed by: https:/
Moves Hyper-V Fibre Channel support spec to Mitaka
Gerrit topic: https:/
Re-approved for mitaka --johnthetubaguy 7th October 2015
Sorry, we have now hit the Non-Priority Feature Freeze for Mitaka. For more details please see: http://
--johnthetubaguy 2016.01.30
Gerrit topic: https:/
Addressed by: https:/
Moves Hyper-V Fibre Channel support spec to Newton
Previously Merged Patches
=======
Addressed by: https:/
HyperV: Set disk serial number for attached volumes
Addressed by: https:/
HyperV: Fix vm disk path issue
Pending Patches
=============
Addressed by: https:/
Hyper-V: Add FC attached volumes support
Addressed by: https:/
HyperV: Refactor livemigr, avoiding getting disk paths remotely
Addressed by: https:/
[WIP]HyperV: use os-brick for volume related operations
This is now tracked under https:/
