Add support for image deactivate and reactivate

[Niall Bunting]

Add support for image deactivate and reactivate. So admins can use the osc rather than the api.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Niall Bunting (<email address hidden>) on branch: master
Review: https://review.openstack.org/251410
Reason: Abandoned in favour of: https://review.openstack.org/#/c/257403/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/257403
Committed: https://git.openstack.org/cgit/openstack/python-openstackclient/commit/?id=b3943d714275b276a973de9c52307e82c90be8bc
Submitter: Jenkins
Branch: master

commit b3943d714275b276a973de9c52307e82c90be8bc
Author: NiallBunting <email address hidden>
Date: Mon Dec 14 14:28:45 2015 +0000

    Add image re/deactivate commands

    This change allows admins to deactivate and reactivate their
    images. Currently this has to be done with the REST api or the
    glanceclient.

    This change introduces `--deactivate` and `--activate` for the `image
    set` command.

    This requires glanceclient 1.2.0. Which got bumped here:
    https://review.openstack.org/#/c/257512/

    Change-Id: I476c44a0343cdc92d58ddc93fb06470242de2345
    Depends-On: I2c370c6bf6ff664d94d756cc76aaa983fbdb8869
    Closes-Bug: 1516661

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/python-openstackclient 2.1.0 release.