cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Parth Jagirdar (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-1904) API : UI : Admin can not delete Events/Archive from other accounts.
Date Wed, 03 Apr 2013 05:25:15 GMT
Parth Jagirdar created CLOUDSTACK-1904:
------------------------------------------

             Summary: API : UI : Admin can not delete Events/Archive from other accounts.
                 Key: CLOUDSTACK-1904
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1904
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: API, UI
    Affects Versions: 4.2.0
         Environment: Master # 171
            Reporter: Parth Jagirdar


Currently Admin can not delete events from other Users. Which voids the purpose of having
Admins managing accounts.

Although not mentioned explicitly in FS; An assumption is made that Admins should have full
control over Alerts and Events from all Accounts.

To do this, API should facilitate a way to differentiate between accounts. And perform Delete/Archive
on them.


As per FS:

Purpose
In CloudStack, we have features like Alerts and Events that helps administrator in managing
the cloud. Admin can get a list of Alerts and Events but there is no way to control them i.e
delete or archive them.

This feature will provide the functionality to delete or archive the Alerts/Events. In this
way admin can get more controls over the Alerts and Events and manage them to get required
and useful information. CloudStack admin can manage them by using the APIs or through CloudStack
UI. This is a functional specification of feature "Ability to delete/archive Events and Alerts"
which has Jira ID CLOUDSTACK-874


However to differentiate between Accounts; additional param may be required.

I.E delete all LOGIN events from account 1 but leave account 2.

Similar functionality is expected for Archive.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message