cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9417) Usage module refactoring
Date Tue, 13 Sep 2016 14:25:22 GMT

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

ASF GitHub Bot commented on CLOUDSTACK-9417:
--------------------------------------------

Github user jburwell commented on the issue:

    https://github.com/apache/cloudstack/pull/1593
  
    @serg38 I completely agree that it should be in the database, but it's not a configuration
setting.  Furthermore, it requires a different transactional behavior to operate properly.
 Therefore, it should be placed in a separate tracking table -- either a new table or as a
column on an existing table.


> Usage module refactoring
> ------------------------
>
>                 Key: CLOUDSTACK-9417
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9417
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Usage
>    Affects Versions: 4.9.0
>            Reporter: Nicolas Vazquez
>            Assignee: Nicolas Vazquez
>             Fix For: 4.9.1.0
>
>
> h3. Introduction
> Usage sanity check file was not been updated on sanity check.
> It is proposed:
> * New usage folder {{/var/cache/cloudstack/usage}}, creation on cloudstack-usage package
built.
> * New sanity check file location in new folder {{/var/cache/cloudstack/usage}}
> * Timestamp included in {{usage.log}} file
> * Include {{updateMaxId()}} on sanity check as it wasn't being updated



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message