nova libvirt driver requires iscsi initiator name regardless of using it in volume drivers
Bug #1007084 reported by
Joseph Heck
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Unassigned | ||
Grizzly |
Fix Released
|
Medium
|
Ruby Loo |
Bug Description
The nova libvirt driver requires the file /etc/iscsi/
This seems like it would be better organized if the volume driver looked up the information it needed rather than routing through methods on the compute manager.
tags: | added: libvirt |
tags: | added: grizzly-backport-potential |
Changed in nova: | |
milestone: | none → havana-2 |
status: | Fix Committed → Fix Released |
tags: | removed: grizzly-backport-potential in-stable-grizzly |
Changed in nova: | |
milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
the problem is that the manager (and probably in the future the api) is the one that calls initialize_ connection. It has to pass in info about where the connection will be coming from, but perhaps we could make initiator optional, as in if it can't find the initiator name, it won't pass it in initialize_ connection. If the receiving volume driver needs iscsi and it isn't set it can return an error.
Would that work?