[
https://issues.apache.org/jira/browse/CLOUDSTACK-9417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339809#comment-15339809
]
ASF GitHub Bot commented on CLOUDSTACK-9417:
--------------------------------------------
Github user nvazquez commented on the issue:
https://github.com/apache/cloudstack/pull/1593
Thanks @jburwell for your review!
About your first question, as @serg38 said file will be created on sanity
check run if it didn't exist, and then it would just update it.
About your second question, it would be nice that it can be included on 4.9
but I think it will be deferred to 4.10. I just targeted it to 4.9 as it was
current version without realizing about 4.9 freeze. Actually I tried updating
JIRA ticket to 4.10 but it doesn't exist. Should I leave version fields blank?
> 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.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)
