cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Feng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-583) Expose Service Offerings and Zone options (including UUID) to users in the CloudStack UI
Date Tue, 04 Dec 2012 20:08:58 GMT

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

Jie Feng commented on CLOUDSTACK-583:
-------------------------------------

Forgot to mention that service offering is more critical than zone. For zone, there is another
workaround, which is to look at a template in the UI and find the zone ID for the template.
But for service offering, it is no where to be found for a user. So I recommend to prioritize
service offering support above zone if they cannot both be fixed in the same release.Thanks.
                
> Expose Service Offerings and Zone options (including UUID) to users in the CloudStack
UI
> ----------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-583
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-583
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.0.0
>            Reporter: Jie Feng
>            Assignee: Brian Federle
>             Fix For: 4.1.0
>
>
> Use case: When a user uses a third party program to instantiate a VM through CloudStack
API, s/he needs to provide service offering ID and zone ID (in addition to template ID). However,
these are not exposed in the CloudStack UI. (i.e. user cannot see Service Offering and Zones
in CloudStack UI). A workaround is to make a signed API call to get this information, which
is not easy to do for a regular user.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message