ASF GitHub Bot commented on CLOUDSTACK-9417:

Github user serg38 commented on the issue:

    @rhtyd  @jburwell @rafaelweingartner Can we use event_details table which 
is not used at the moment? if we consider sanity job to generate event_id=0 
then max_id can be easily represented there as ("id","0","max_id","value")
    Alternatively a new table would require new DAO isn't it? Seems to be huge 
scope creep for such a minor fix as permission issue. Can we just merge it as 
it is and open another PR for the extended scope?

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

Reply via email to