Bug 1042023

Summary:	[RFE][horizon]: Instance Action Dashboard
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:	low	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	aberezin, ajeain, aortega, ddomingo, jpichon, markmc, mrunge, rhos-flags, slong, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature
Target Release:	6.0 (Juno)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/horizon/+spec/instance-actions-dashboard
Whiteboard:	upstream_milestone_juno-3 upstream_status_implemented upstream_definition_approved
Fixed In Version:	python-django-horizon-2014.2-4.el7ost	Doc Type:	Enhancement
Doc Text:	An additional 'Action Log' tab is now available for specific instances (Project > Compute > Instances > [instance]). The tab lists all actions which have been carried out on that specific instance. For example, a tenant user can now use the 'Action Log' tab to see who created or shut down an instance.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-09 14:54:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 20:37:09 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/instance-actions-dashboard.

Description:

Create a new dashboard in Horizon to show the actions taken on the tenant's instances in reverse date order (latest first). This provides the user with a view of what's been happening in their environment, and any errors that have occurred.

This should make use of the nova-instance-actions API: https://wiki.openstack.org/wiki/NovaInstanceActions

Use cases:
1) A tenant Admin logs into web interface and sees that one of the users has been hitting errors when deploying new instances. The errors are due to a lack of available space or a quota limit, so the tenant Admin increases the user's quota.
2) A tenant user logs into the web interface and finds that an instance has been shut down. The tenant is able to see who shut it down in order to follow up on the reasons why this was done.

Specification URL (additional information):

None

Comment 4 Ido Ovadia 2014-12-21 14:09:29 UTC

Verified
========
python-django-horizon-2014.2.1-3.el7ost.noarch

Comment 6 errata-xmlrpc 2015-02-09 14:54:12 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://rhn.redhat.com/errata/RHEA-2015-0154.html