[
https://issues.apache.org/jira/browse/CLOUDSTACK-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chip Childers updated CLOUDSTACK-583:
-------------------------------------
Description:
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.
Release Planning:
Dev list discussion: unknown
Functional Spec: unknown
was: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.
> 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.
> Release Planning:
> Dev list discussion: unknown
> Functional Spec: unknown
--
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
