Improve manageability of Cinder volumes for vSphere admin
vSphere admin will find it difficult to manage the datacenter using vSphere client if there are large number of Cinder volumes and Nova instances. This blueprint proposes the following changes in the VMDK driver to improve management of Cinder volumes using VMware products such vSphere client and vRealize:
* Restrict volume placement to specific vCenter clusters
Currently the volumes are placed in an arbitrary vCenter cluster. Admin can create clusters dedicated for OpenStack VMs and this change will enable placement of volumes in such clusters.
* Change vCenter inventory folder hierarchy for Cinder volumes
Currently Cinder volumes belonging to various OpenStack projects are stored under a vCenter inventory folder with name given by config option vmware_
Openstack/Project (<project-
* Set meta-data to identify Cinder volumes
Set a key “cinder.volume.id” in volume's vCenter configuration file so that solutions like vRealize can identify Cinder volumes.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Vipin Balachandran
- Direction:
- Needs approval
- Assignee:
- Vipin Balachandran
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Vipin Balachandran
- Completed by
- Vipin Balachandran
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
VMware: Create volume backing in specific clusters
Addressed by: https:/
VMware: Change inventory folder hierarchy
Addressed by: https:/
VMware: Add volume ID in vCenter's volume config
