You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Wei Zhou (JIRA)" <ji...@apache.org> on 2017/01/13 13:50:26 UTC
[jira] [Commented] (CLOUDSTACK-9737) Ability to move VM to other
project
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821793#comment-15821793 ]
Wei Zhou commented on CLOUDSTACK-9737:
--------------------------------------
I created a PR long time ago, which includes the fix to this.
https://github.com/apache/cloudstack/pull/844
[4.10] CLOUDSTACK-7985: assignVM in Advanced zone with Security Groups #844
> Ability to move VM to other project
> -----------------------------------
>
> Key: CLOUDSTACK-9737
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9737
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Projects
> Reporter: Steven Segers
>
> A VM can be created inside a project or outside of a project. It is possible to move a VM to another domain but not to add/remove it to/from a project or move it from one project to another. It would be very practical if it was possible to do this. This issue potentially relates to CLOUDSTACK-3613
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)