iscsi_use_multipath confusing

Bug #1593860 reported by Walt Boring on 2016-06-17
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Undecided
Walt Boring

Bug Description

The [libvirt] config option 'iscsi_use_multipath' is confusing because it's also used for Fibre Channel.

Since you can have iSCSI and FC attaches on the same compute host, it makes sense to have a single config option that enables checking for multipath attaches globally (for all transports).

Fix proposed to branch: master
Review: https://review.openstack.org/331357

Changed in nova:
assignee: nobody → Walt Boring (walter-boring)
status: New → In Progress

Reviewed: https://review.openstack.org/331357
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=720e5af1e08cc829e98db10da4b93795771a927e
Submitter: Jenkins
Branch: master

commit 720e5af1e08cc829e98db10da4b93795771a927e
Author: Walter A. Boring IV <email address hidden>
Date: Fri Jun 17 14:35:18 2016 -0700

    config option: rename libvirt iscsi_use_multipath

    This patch renames the libvirt conf section entry of
    iscsi_use_multipath to volume_use_multipath. Both iSCSI and
    FibreChannel libvirt volume drivers use this value to determine
    if multipath volume attachments are to be used. It's an n-cpu system
    wide value that's not specific to iSCSI.

    Change-Id: Iebbac91a74df468d5be9b2e70560d5b4394ce595
    Closes-Bug: #1593860

Changed in nova:
status: In Progress → Fix Released

This issue was fixed in the openstack/nova 14.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers