Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1107924 - [RFE][horizon]: Expose cinder volume transfer functionality in horizon
[RFE][horizon]: Expose cinder volume transfer functionality in horizon
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
high 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
Depends On:
Blocks: 1226932
  Show dependency treegraph
 
Reported: 2014-06-11 00:10 EDT by RHOS Integration
Modified: 2015-08-05 09:12 EDT (History)
7 users (show)

See Also:
Fixed In Version: python-django-horizon-2015.1.0-7.el7ost
Doc Type: Enhancement
Doc Text:
The option to create Block Storage (cinder) volume transfers has been added to the 'Volumes' tab in the OpenStack dashboard. Volume transfers move ownership from one project to another. A donor creates a volume transfer, captures the resulting transfer ID and secret authentication key, and passes that information out of band to the recipient (such as by email or text message). The recipient accepts the transfer, supplying the transfer ID and authentication key. The ownership of the volume is then transferred from the donor to the recipient, and the volume is no longer visible to the donor. Note the following limitations of the Block Storage API for volume transfers and their impact on the UI design: 1. When creating a volume transfer, you cannot specify who the intended recipient will be, and anyone with the transfer ID and authentication key can claim the volume. Therefore, the dashboard UI does not prompt for a recipient. 2. Current volume transfers are only visible to the donor; users in other projects are unable to view these transfers. So, the UI does not include a project table to view and accept volume transfers, since the current transfers are not visible. Instead, the transfer information is added to the volume details, which are visible by the donor, and the volume state clearly reflects that a transfer has been created. The UI also cannot present to the recipient a pull-down list of transfers to accept. 3. The only time that the authorization key is visible to the donor is in the response from the creation of the transfer; after creation, it is impossible for even the donor to recover it. Since the donor must capture the transfer ID and authorization key in order to send it to the recipient, an extra form was created to present this information to the donor immediately after the transfer has been created.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-05 09:12:26 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-06-11 00:10:59 EDT
Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/cinder-volume-transfer.

Description:

cinder supports transferring the ownership of a volume from one project to another. This should be supported in horizon. The relevant cinder commands are:
- cinder transfer-create
- cinder transfer-accept
- cinder transfer-delete
- cinder transfer-list
- cinder transfer-show


Specification URL (additional information):

None
Comment 2 Matthias Runge 2015-04-15 05:26:37 EDT
upstream review: https://review.openstack.org/#/c/112741/
Comment 5 errata-xmlrpc 2015-08-05 09:12:26 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.