Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 9 Jan 2014 21:15:51 +0000 (UTC)
From: "Animesh Chaturvedi (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12686467.1388092292136.71474.1389302151163@arcas>
In-Reply-To: <JIRA.12686467.1388092292136@arcas>
References: <JIRA.12686467.1388092292136@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-5651) deployVm: customparameters
 param name has to be changed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Animesh Chaturvedi commented on CLOUDSTACK-5651:
------------------------------------------------

Bharat

If you put a bug for InReview do include reviewboard link. Please add it no=
w

> deployVm: customparameters param name has to be changed
> -------------------------------------------------------
>
>                 Key: CLOUDSTACK-5651
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-565=
1
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>    Affects Versions: 4.3.0
>            Reporter: Alena Prokharchyk
>            Assignee: Bharat Kumar
>            Priority: Critical
>             Fix For: 4.3.0
>
>
> deployVm API got a new param in 4.3 -=E2=80=9Ccustomparameters=E2=80=9D. =
The description of the parameter is very vague and generic =E2=80=9Cused to=
 specify the custom parameters=E2=80=9D.
> Is it just the metadata in form of value/key pairs? If so, please change =
the name to =E2=80=9Cdetails=E2=80=9D - the generic name used when specify =
key/value metadata in other API commands.=20
> Also you need to save this information in the =E2=80=9Cuser_vm_details=E2=
=80=9D table, and return it in the UserVmResponse, =E2=80=9Cdetails=E2=80=
=9D map parameter. I don=E2=80=99t see =E2=80=9Ccustom parameters=E2=80=9D =
key map being returned anywhere in the UserVmResponse. Its very confusing, =
because whatever is passed to the Create/Update call, should be returned in=
 the response as well.
> It all has to be fixed in 4.3 branch.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)