Bug 1101375

Summary:	[RFE][horizon]: Add support for resizing the trove instance
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	python-django-horizon	Assignee:	Matthias Runge <mrunge>
Status:	CLOSED ERRATA	QA Contact:	Ido Ovadia <iovadia>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	aortega, athomas, jkulina, lbopf, markmc, mrunge, yeylon
Target Milestone:	Upstream M2	Keywords:	FutureFeature, OtherQA, Triaged
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/horizon/+spec/trove-resize-instance-dialog
Whiteboard:	upstream_milestone_kilo-2 upstream_definition_approved upstream_status_implemented
Fixed In Version:	python-django-horizon-2015.1.0-7.el7ost	Doc Type:	Enhancement
Doc Text:	OpenStack Trove instances can now be resized in the OpenStack dashboard user interface by selecting a new flavor for the instance.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:12:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-05-27 04:07:39 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/trove-resize-instance-dialog.

Description:

Trove supports resizing the current instance i.e selecting a new flavor for the instance (similar to the nova feature).

We should add support to the Trove Database Instances panel to add a 'Resize instance' option on the selected database (in the dropdown 'More...' list).

This option will display a subset of the Trove Launch Instance dialog allowing the user to select a new instance flavor

Specification URL (additional information):

None

Comment 5 errata-xmlrpc 2015-08-05 13:12:11 UTC

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