You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ace.apache.org by "Marcel Offermans (JIRA)" <ji...@apache.org> on 2011/08/24 14:07:29 UTC

[jira] [Created] (ACE-170) Refactor the audit log implementation to accept not only a "name" but also a "ma" property.

Refactor the audit log implementation to accept not only a "name" but also a "ma" property.
-------------------------------------------------------------------------------------------

                 Key: ACE-170
                 URL: https://issues.apache.org/jira/browse/ACE-170
             Project: Ace
          Issue Type: Sub-task
            Reporter: Marcel Offermans


Since we want to be able to run multiple audit logs, one per management agent, each audit log should also have a "ma" property with the identity of that management agent instance. The audit log is already implemented as a managed service factory.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (ACE-170) Refactor the audit log implementation to accept not only a "name" but also a "ma" property.

Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ACE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Offermans reassigned ACE-170:
------------------------------------

    Assignee: Marcel Offermans

> Refactor the audit log implementation to accept not only a "name" but also a "ma" property.
> -------------------------------------------------------------------------------------------
>
>                 Key: ACE-170
>                 URL: https://issues.apache.org/jira/browse/ACE-170
>             Project: Ace
>          Issue Type: Sub-task
>            Reporter: Marcel Offermans
>            Assignee: Marcel Offermans
>
> Since we want to be able to run multiple audit logs, one per management agent, each audit log should also have a "ma" property with the identity of that management agent instance. The audit log is already implemented as a managed service factory.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (ACE-170) Refactor the audit log implementation to accept not only a "name" but also a "ma" property.

Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ACE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097934#comment-13097934 ] 

Marcel Offermans commented on ACE-170:
--------------------------------------

Decided not to create multiple audit logs, because fundamentally there can be only one log that keeps track of all life cycle changes so it does not make much sense to create multiple logs. We will still have multiple log sync tasks, each one responsible for sync'ing with its server.

> Refactor the audit log implementation to accept not only a "name" but also a "ma" property.
> -------------------------------------------------------------------------------------------
>
>                 Key: ACE-170
>                 URL: https://issues.apache.org/jira/browse/ACE-170
>             Project: Ace
>          Issue Type: Sub-task
>            Reporter: Marcel Offermans
>            Assignee: Marcel Offermans
>
> Since we want to be able to run multiple audit logs, one per management agent, each audit log should also have a "ma" property with the identity of that management agent instance. The audit log is already implemented as a managed service factory.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira