cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Min Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-355) Fix "count" in a bunch of API commands
Date Fri, 18 Jan 2013 22:04:12 GMT

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

Min Chen commented on CLOUDSTACK-355:
-------------------------------------

listTrafficTypeImplementors is based on NetworkGuru adapters loaded into memory, so DB view
based search refactoring will not solve this issue. Since the count of the list is limited,
pagination will not be used that often, no urgent need to fix for this api.
                
> Fix "count" in a bunch of API commands
> --------------------------------------
>
>                 Key: CLOUDSTACK-355
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-355
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.1.0
>            Reporter: Alena Prokharchyk
>            Assignee: Min Chen
>             Fix For: 4.1.0
>
>
> Count should be fixed for following list commands (as a part of Search Engine refactoring)
> listResourceLimits
> listIsos
> listTemplates
> listLoadBalancerRuleInstances
> listCapacity
> listHosts
> listSecurityGroups
> listNetworks
> listVPCs
> listTemplatePermissions
> listIsoPermissions
> listServiceOfferings
> listDiskOfferings
> listNetworkDevice
> listVPCOfferings
> listTrafficTypeImplementors
> listSnapshotPolicies
> listLBStickinessPolicies
> listCapabilities
> listZones
> listEventTypes
> listSwifts
> listHypervisors
> listNetworkOfferings
> listSupportedNetworkServices
> listStorageNetworkIpRange
> listEvents 

--
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