3PAR iSCSI Driver using 'excessive' iscsi & fc ports
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Low
|
Ramy Asselin |
Bug Description
According to the note at the end of http://
"You can configure one or more iSCSI addresses by using the hp3par_iscsi_ips option. When you configure multiple addresses, the driver selects the iSCSI port with the fewest active volumes at attach time. The IP address might include an IP port by using a colon (:) to separate the address from port. If you do not define an IP port, the default port 3260 is used. Separate IP addresses with a comma (,). The iscsi_ip_
The 3PAR Driver should not consume ALL N:S:P iSCSI Paths (and FC!) from the 3PAR to the host, especially when it is configured with a single port iSCSI Configuration when attaching a volume to a host.
Instead, it should simply choose the least used (at the time of connection).
Steps to reproduce:
1. Configure a 3PAR to a blade with more than one path: e.g. 2 iscsi & 2 fc
2. Create an iscsi volume
3. Attach the iscsi volume to an instance
4. Observe that 4 VLUNs are created, one for each path between the 3par & the instance (2 iscsi & 2 fc, yes, fc too even if this is an iscsi volume)
Changed in cinder: | |
assignee: | nobody → Ramy Asselin (ramy-asselin) |
status: | New → In Progress |
Changed in cinder: | |
milestone: | none → icehouse-3 |
Changed in cinder: | |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | icehouse-3 → 2014.1 |
Changed in cinder: | |
importance: | Undecided → Low |
Fix proposed to branch: master /review. openstack. org/68456
Review: https:/