You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Jessica Wang (JIRA)" <ji...@apache.org> on 2013/12/03 01:18:35 UTC

[jira] [Updated] (CLOUDSTACK-4738) dynamic compute offering

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jessica Wang updated CLOUDSTACK-4738:
-------------------------------------

    Attachment: InstanceDetail_changeServiceOffering_when_selected_computeOffering_is_NOT_custom.jpg
                InstanceDetail_changeServiceOffering_when_selected_computeOffering_is_custom.jpg

> 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#6144)