Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1150839 - [RFE][horizon]: Add Manage/Unmanage Volume feature
[RFE][horizon]: Add Manage/Unmanage Volume feature
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon (Show other bugs)
unspecified
Unspecified Unspecified
medium Severity low
: Upstream M2
: 7.0 (Kilo)
Assigned To: Matthias Runge
Ido Ovadia
https://blueprints.launchpad.net/hori...
upstream_milestone_kilo-2 upstream_de...
: FutureFeature, OtherQA
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-09 00:07 EDT by RHOS Integration
Modified: 2015-08-05 09:14 EDT (History)
7 users (show)

See Also:
Fixed In Version: python-django-horizon-2015.1.0-9.el7ost
Doc Type: Enhancement
Doc Text:
The 'Manage/Unmanage' option has been added to the 'Volumes' tab of the OpenStack dashboard. 'Manage' takes an existing volume created outside of OpenStack and makes it available. 'Unmanage' removes the visibility of a volume within OpenStack, but does not delete the actual volume.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-05 09:14:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:1548 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2015-08-05 13:07:06 EDT

  None (edit)
Description RHOS Integration 2014-10-09 00:07:02 EDT
Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/add-manage-unmanage-volume.

Description:

Summary:
Add manage/unmanage options to "Admin -> Volumes" panel so that an admin can access existing volumes not currently managed by OpenStack.

Motivation:
This functionality exists via the Cinder CLI, so we should expose it in Horizon.

$ cinder help manage
usage: cinder manage [--id-type <id-type>] [--name <name>]
                     [--description <description>]
                     [--volume-type <volume-type>]
                     [--availability-zone <availability-zone>]
                     [--metadata [<key=value> [<key=value> ...]]] [--bootable]
                     <host> <identifier>

Manage an existing volume.

Positional arguments:
  <host>                Cinder host on which the existing volume resides;
                        takes the form: host@backend-name#pool
  <identifier>          Name or other Identifier for existing volume

Optional arguments:
  --id-type <id-type>   Type of backend device identifier provided, typically
                        source-name or source-id (Default=source-name)
  --name <name>         Volume name (Default=None)
  --description <description>
                        Volume description (Default=None)
  --volume-type <volume-type>
                        Volume type (Default=None)
  --availability-zone <availability-zone>
                        Availability zone for volume (Default=None)
  --metadata [<key=value> [<key=value> ...]]
                        Metadata key=value pairs (Default=None)
  --bootable            Specifies that the newly created volume should be
                        marked as bootable


$ cinder help unmanage
usage: cinder unmanage <volume>

Stop managing a volume.

Positional arguments:
  <volume>  Name or ID of the volume to unmanage.


UX:
Need to add a new "Manage Volume" action button to the "Admin -> Volumes" table. This will bring up a modal dialog allowing the user to enter volume and cinder host information.

Need to add a new "Unmanage Volume" action button to each row of the "Admin -> Volumes" table. This will simply send the volume and host name to the cinder client.

Outside Dependencies:
N/A

Requirements Update Required:
N/A

Doc Impact:
N/A

Specification URL (additional information):

None
Comment 6 errata-xmlrpc 2015-08-05 09:14:27 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548

Note You need to log in before you can comment on or make changes to this bug.