No way to secure volumes based on initiator name
Bug #924461 reported by
Vish Ishaya
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Vish Ishaya |
Bug Description
Some hardware volume drivers secure volumes based on the name of the initiator. When the connection is prepared, an ip address is sent in, but the volume driver has no way of knowing what initiator the iscsi connection will come from. There needs to be some way for the driver to get the right initiator for the instance.
This could be done with a callback, but it is easiest to add the parameter to initialize_
Changed in nova: | |
importance: | Undecided → Medium |
assignee: | nobody → Vish Ishaya (vishvananda) |
status: | New → In Progress |
Changed in nova: | |
milestone: | none → essex-4 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-4 → 2012.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/3586
Review: https:/