You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Kishan Kavala (JIRA)" <ji...@apache.org> on 2013/02/05 12:27:13 UTC
[jira] [Resolved] (CLOUDSTACK-798) Move usage related cmd classes
from cloud-server to cloud-api
[ https://issues.apache.org/jira/browse/CLOUDSTACK-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kishan Kavala resolved CLOUDSTACK-798.
--------------------------------------
Resolution: Fixed
commit 7970384f6e429b5c97f6d6e80f59cbab6ce90ede
Author: Kishan Kavala <ki...@cloud.com>
Date: Tue Feb 5 16:43:18 2013 +0530
CLOUDSTACK-786, CLOUDSTACK-1014: Moved usage APIs to cloud-api. Removed ManagementServerExt. Usage API related implementation is added to UsageServiceImpl
> Move usage related cmd classes from cloud-server to cloud-api
> -------------------------------------------------------------
>
> Key: CLOUDSTACK-798
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-798
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: API, Usage
> Reporter: Rohit Yadav
> Assignee: Kishan Kavala
> Fix For: 4.1.0
>
>
> Usage related apis exist in cloud-server, the cmd classes should be in cloud-api:
> server/src/com/cloud/api/commands/AddTrafficMonitorCmd.java
> server/src/com/cloud/api/commands/DeleteTrafficMonitorCmd.java
> server/src/com/cloud/api/commands/GenerateUsageRecordsCmd.java
> server/src/com/cloud/api/commands/GetUsageRecordsCmd.java
> server/src/com/cloud/api/commands/ListTrafficMonitorsCmd.java
> server/src/com/cloud/api/commands/ListUsageTypesCmd.java
> The issue is that they are tightly coupled with cloud-server and instead of using interface to handle object method evoking, they are used directly on implementing class objects. This makes move refactoring impossible. For example UsageVO implements no contract or interface which should be defined in cloud-api.
--
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