cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-7908) Addition of userid field to vm_instance table to identify user that created the VM
Date Mon, 16 Feb 2015 10:44:13 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-7908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322636#comment-14322636
] 

ASF subversion and git services commented on CLOUDSTACK-7908:
-------------------------------------------------------------

Commit 2580edbcfbf7ff784209de2930df8926178801e2 in cloudstack's branch refs/heads/master from
[~rohit.yadav@shapeblue.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2580edb ]

CLOUDSTACK-7908: UserVmResponse returns userid/username information of the creator

Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>


> Addition of userid field to vm_instance table to identify user that created the VM
> ----------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7908
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7908
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.3.0
>         Environment: 4.3.0
>            Reporter: David Williams
>            Assignee: Rohit Yadav
>            Priority: Minor
>             Fix For: 4.6.0
>
>
> It would be handy/helpful if the userid of the user that created a VM was recorded in
the database in the vm_instance table. Currently, the only way I know of to find the user
that deployed a VM is by checking the logs. There's an owner field in the vm_instance table
but this seems to be the account ID of the account the user belongs to.
> By being able to find the user that deployed a VM, it makes VM cleanups much easier since
you know who to contact for each VM to check if it can be deleted. A similar thing in the
other tables for the other resources would be useful too when trying to cleanup networks and
volumes, etc. Also, if this change went ahead, then the API and GUI could be changed also
to show the user details for the VM when listing the VM's details. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message