Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 26 May 2016 03:06:14 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12924704.1451403638000.299110.1464231974434@Atlassian.JIRA>
In-Reply-To: <JIRA.12924704.1451403638000@Atlassian.JIRA>
References: <JIRA.12924704.1451403638000@Atlassian.JIRA> <JIRA.12924704.1451403638901@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-9203) [API] extend
 updateVirtualMachine to support updating security groups
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 26 May 2016 03:06:29 -0000


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9203?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D15301410#comment-15301410 ]=20

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

Commit de205c5805b356d7dc261e10519901bebfa85e04 in cloudstack's branch refs=
/heads/master from [~williamstevens@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=3Dcloudstack.git;h=3Dde205c5 ]

Merge pull request #1297 from DaanHoogland/CLOUDSTACK-9203

CLOUDSTACK-9203 Implement security group move on updateVM API call  cherry-=
picked from a exoscale internal fix

Conflicts:
=09api/src/org/apache/cloudstack/api/command/user/vm/UpdateVMCmd.java
=09server/src/com/cloud/vm/UserVmManager.java
=09server/src/com/cloud/vm/UserVmManagerImpl.java

* pr/1297:
  CLOUDSTACK-9203 refactorred DeployVM code to be used by UpdateVM as well
  CLOUDSTACK-9203 security group update on running instance

Signed-off-by: Will Stevens <williamstevens@gmail.com>


> [API] extend updateVirtualMachine to support updating security groups
> ---------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9203
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-920=
3
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          Components: API
>            Reporter: Ren=C3=A9 Moser
>            Assignee: Daan Hoogland
>            Priority: Minor
>             Fix For: Future
>
>
> There is currently no way to change security groups on exisitng VMs.
> {{updateVirtualMachine}} should be extended in a similar way as {{deployV=
irtualMachine}} which should allow passing a list of IDs or names to update=
 the security groups as passed:
> {{securitygroupids}} parameter
> comma separated list of security groups id that going to be applied to th=
e virtual machine. Should be passed only when vm is created from a zone wit=
h Basic Network support. Mutually exclusive with securitygroupnames paramet=
er, default: false
> {{securitygroupnames}} parameter
> comma separated list of security groups names that going to be applied to=
 the virtual machine. Should be passed only when vm is created from a zone =
with Basic Network support. Mutually exclusive with securitygroupids parame=
ter. default: false
> Exoscale did already some work in their branch which we are [allowed|http=
s://twitter.com/resmo79/status/681428989018267648] to use, see [https://git=
hub.com/exoscale/cloudstack/pull/6/]


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