kerberos should be configured for each lif within cmode driver

Bug #1370965 reported by Valeriy Ponomaryov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
Low
Clinton Knight

Bug Description

To configure kerberos on vServer we should specify LIF (logical interface). Now, vServers of NetApp Cluster Mode backend use only one logical net interface, so no real bug exist, but when it will be more than 1 we will get bug in following code:

https://github.com/stackforge/manila/blob/1a9d060600693499eb735259ee5862d18191cf34/manila/share/drivers/netapp/cluster_mode.py#L533

problem is that request sends only for last value.

description: updated
Changed in manila:
importance: Undecided → Low
milestone: none → kilo-1
Changed in manila:
milestone: kilo-1 → kilo-2
tags: added: netapp
Changed in manila:
milestone: kilo-2 → kilo-3
Revision history for this message
Clinton Knight (clintonk) wrote :
Revision history for this message
Clinton Knight (clintonk) wrote :

Ignore my previous comment. This behavior is due to an indentation bug on a later line:

https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/cluster_mode.py#L569

This bug was fixed by inspection during the cDOT driver refactoring work.

Changed in manila:
assignee: nobody → Clinton Knight (clintonk)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Reviewed: https://review.openstack.org/153622
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=12eeedb6392462c8aa2a0afa5763e0a4612cc475
Submitter: Jenkins
Branch: master

commit 12eeedb6392462c8aa2a0afa5763e0a4612cc475
Author: Clinton Knight <email address hidden>
Date: Thu Jan 8 18:01:08 2015 -0500

    Manila NetApp cDOT driver refactoring

    The Manila cDOT driver is a single file exceeding 1200 lines. It contains
    multiple things (driver code, protocol helpers, ZAPI invocation code,
    options) that should be split apart to allow for easier maintenance and
    readability and add the potential for code sharing when we reintroduce
    a 7-mode driver, add a single-SVM cDOT driver, etc.

    We recently refactored NetApp's DOT Cinder drivers into a 4-layer
    structure (interface, library, client, API) that separates concerns and
    achieves the goals set forth above. This commit satisfies a plan to
    do the same thing in Manila. The implementation steps are:

    1. Update directory structure to match that of the Cinder NetApp drivers
    2. Create driver interface shim
    3. Move driver code to library (with base & C-mode classes, to allow for
       7-mode code sharing later)
    4. Move protocol helpers to separate files (already organized by base &
       C-mode classes)
    5. Split out ZAPI code to client layer (with base & C-mode classes, to
       allow for 7-mode code sharing later)
    6. Implement NetApp driver factory as in Cinder
    7. Implement common NetApp options file as in Cinder
    8. Implement cDOT API call optimizations
    9. Update all unit tests as needed

    Note that this patch appears to treble the total number of code lines.
    This is due to the addition of many more unit tests plus a large amount
    of fake controller API data to feed the API client tests.

    Implements: blueprint netapp-manila-cdot-driver-refactoring
    Closes-Bug: #1410317
    Partial-Bug: #1396953
    Closes-Bug: #1370965
    Closes-Bug: #1418690
    Closes-Bug: #1418696

    Change-Id: I3fc0d09adf84a3708f110a89a7c8c760f4ce3588

Changed in manila:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in manila:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in manila:
milestone: kilo-3 → 2015.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.