[
https://issues.apache.org/jira/browse/CLOUDSTACK-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801091#comment-13801091
]
Jessica Wang edited comment on CLOUDSTACK-4738 at 10/22/13 6:55 PM:
--------------------------------------------------------------------
Expected API change:
(1) Service Offering:
1-1. CreateServiceOffering API will take in a new parameter:
@Parameter(name=ApiConstants.CUSTOMIZED, type=CommandType.BOOLEAN,
description="whether compute offering is custom or not")
private Boolean customized;
When CUSTOMIZED parameter is true, CPU_NUMBER/CPU_SPEED/MEMORY parameters
are NOT required.
When CUSTOMIZED parameter is false, CPU_NUMBER/CPU_SPEED/MEMORY parameters
are required.
1-2: class ServiceOfferingResponse will include new parameter:
@SerializedName("iscustomized") @Param(description="true if service offering
uses custom CPU/memory, false otherwise")
private Boolean customized;
(2) DeployVM API will take in 4 new parameters:
@Parameter(name=ApiConstants.CPU_NUMBER, type=CommandType.LONG, required=false,
description="the arbitrary CPU number of the VM")
private Long cpuNumber;
@Parameter(name=ApiConstants.CPU_SPEED, type=CommandType.LONG, required=false,
description="the arbitrary CPU speed of the VM in MHz")
private Long cpuSpeed;
@Parameter(name=ApiConstants.MEMORY, type=CommandType.LONG, required=false,
description="the arbitrary memory of the VM in MB")
private Long memory;
@Parameter(name=ApiConstants.ROOTDISKSIZE, type=CommandType.LONG,
required=false, description="the arbitrary size for the ROOTDISK")
private Long rootsize;
was (Author: jessicawang):
Expected API change:
(1) Service Offering:
1-1. CreateServiceOffering API will take in a new parameter:
@Parameter(name=ApiConstants.CUSTOMIZED, type=CommandType.BOOLEAN,
description="whether compute offering is custom or not")
private Boolean customized;
When CUSTOMIZED parameter is true, CPU_NUMBER/CPU_SPEED/MEMORY parameters
are NOT required.
When CUSTOMIZED parameter is false, CPU_NUMBER/CPU_SPEED/MEMORY parameters
are required.
1-2: class ServiceOfferingResponse will include new parameter:
@SerializedName("iscustomized") @Param(description="true if service offering
uses custom CPU/memory, false otherwise")
private Boolean customized;
(2) DeployVM API will take in 4 new parameters:
@Parameter(name=ApiConstants.CPU_NUMBER, type=CommandType.LONG, required=false,
description="the arbitrary CPU number of the VM")
private Long cpuNumber;
@Parameter(name=ApiConstants.CPU_SPEED, type=CommandType.LONG, required=false,
description="the arbitrary CPU speed of the VM in MHz")
private Long cpuSpeed;
@Parameter(name=ApiConstants.MEMORY, type=CommandType.LONG, required=false,
description="the arbitrary memory of the VM in MB")
private Long memory;
@Parameter(name=ApiConstants.ROOTSIZE, type=CommandType.LONG, required=false,
description="the arbitrary size for the ROOTDISK")
private Long rootsize;
> dynamic compute offering
> -------------------------
>
> Key: CLOUDSTACK-4738
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4738
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Bharat Kumar
> Assignee: Bharat Kumar
> Fix For: 4.3.0
>
>
> Currently in cloudstack users have to pick a preconfigured service offering
> for creating VMs. we want to change this by providing a way to specify the
> custom values for cpu and ram without the need to tie them to some service
> offering, some thing like the custom disk offering.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
