[
https://issues.apache.org/jira/browse/CLOUDSTACK-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852253#comment-13852253
]
ASF subversion and git services commented on CLOUDSTACK-4738:
-------------------------------------------------------------
Commit b7a81f8428e580f0e67d9656d57e853fed252c76 in branch refs/heads/4.3 from
[~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b7a81f8 ]
CLOUDSTACK-4738: UI > VM Wizard > select compute offering step > make Number of
CPU Cores/CPU/Memory field required when selected compute offering is
customized.
> 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
>
> Attachments:
> InstanceDetail_changeServiceOffering_when_selected_computeOffering_is_NOT_custom.jpg,
>
> InstanceDetail_changeServiceOffering_when_selected_computeOffering_is_custom.jpg
>
>
> 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.4#6159)
