[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852255#comment-13852255
 ] 

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

Commit 5fb80f90f0a75c7deb7219f16ae2f41ab24391b8 in branch refs/heads/master 
from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5fb80f9 ]

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)

Reply via email to