vCenter compute driver enhancements to support HP Cinder 3Par driver
Title: vCenter compute driver enhancements to support HP Cinder 3Par driver
Blueprint/
Volumes created on FC arrays are supported only for KVM today. This blueprint proposal is to
1. Enhance the vCenter driver to support FC volume attach to instances created on ESX
2. Support HP Cinder 3Par driver
3. Provide HBA information of all ESX hosts in the vCenter cluster(s) so that cinder driver can present the LUN to the right ESX host(s)
4. Provide iSCSI initiator information for all hosts in the cluster
Intending to implement for vCenter compute driver only
Note: The blueprint for FC support for KVM(libvirt) has already been approved and code has been merged into Grizzly 3. https:/
Blueprint information
- Status:
- Started
- Approver:
- Russell Bryant
- Priority:
- Undefined
- Drafter:
- Kiran Kumar Vaddi
- Direction:
- Needs approval
- Assignee:
- Kiran Kumar Vaddi
- Definition:
- Review
- Series goal:
- None
- Implementation:
- Needs Code Review
- Milestone target:
- None
- Started by
- Kiran Kumar Vaddi
- Completed by
Whiteboard
Hi, during the discussions at the Havana summit, it was proposed to avoid interface changes between nova and cinder and move the request of presenting the LUN for each host in the cluster into nova.
So in the modified approach, the sequence for a volume-attach would be as follows
1. nova-api calls attach volume method of Nova manager
2. Nova manager calls get_volume_
The nova driver returns the connector information. It additionally returns the list of all hosts in the cluster in a new key called clustered_hosts
3. Nova manager calls initialize_
4. Nova manager now calls attach_volume of the vCenter nova driver with the connection_info. The driver now attaches the volume to the instance. The driver attaches the volume from the host on which the instance resides.
We can discuss further in the IRC.
-kirankv
Gerrit topic: https:/
Addressed by: https:/
Enhance the vCenter driver to support FC volume attach
Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)
Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy