Add deactivate step to extend_lv

[OpenStack Infra]

https://review.openstack.org/206935
commit 4d2794527ead282514f7019ce8a9b58d2817eda3
Author: Curt Bruns <email address hidden>
Date: Mon Jul 6 15:09:41 2015 +0000

    Add deactivate step to extend_lv

    Extending a linear LVM volume that has a snapshot requires
    that the LV be deactivated explicitly prior to extending.

    This adds a deactivate_lv method and calls it prior to
    issuing the extend call. If auto_activation_volume_list
    is not defined lvm.conf, then volumes will be reactivated
    automatically after the extend. If auto_activation_volume_list
    is defined, then volumes that should be automatically
    reactivated should be added to the auto_activation_volume_list
    or they won't be activated automatically.
    NOTE: This doesn't apply to thin provisioned LVs as they don't
    require the deactivation step.

    DocImpact: When a user extends LVM Volumes with a snapshot, the
    volumes will be deactivated. Their re-activation is automatic,
    unless auto_activation_volume_list is defined in lvm.conf.
    See lvm.conf for more info. Thin provisioned LVM Volumes
    will not be deactivated as they don't require it.

    Conflicts:
            cinder/tests/brick/test_brick_lvm.py

    Co-Authored-By: John Griffith <email address hidden>
    Change-Id: If746625cfe658c3528525dc7f4bf869f1c9704dc
    Closes-Bug: #1470558
    (cherry picked from commit 314611f79afa6fe79f3d5022c814772048669bb0)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/356739
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=d9271e75186ea02f8e47106f6be001770000db20
Submitter: Jenkins
Branch: master

commit d9271e75186ea02f8e47106f6be001770000db20
Author: Scott Machtmes <email address hidden>
Date: Wed Aug 17 21:17:48 2016 +0000

    Added resize note describing auto-reactivation of volumes

    Change-Id: I6caaf5bd6ea15628b39402ec3712ce8a01e63ff6
    Closes-Bug: 1486624

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-manuals 15.0.0 release.