[
https://issues.apache.org/jira/browse/METRON-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277859#comment-16277859
]
Otto Fowler commented on METRON-989:
------------------------------------
METRON-1339 could help with this I think.
Because we can visit all stellar configuration items and fields, we should be
able to 'find' any stellar embedded in any configuration.
If we need more context, we can add that to the Annotations
> design and implement configuration interface for stand-alone Stellar
> --------------------------------------------------------------------
>
> Key: METRON-989
> URL: https://issues.apache.org/jira/browse/METRON-989
> Project: Metron
> Issue Type: Sub-task
> Reporter: Matt Foley
>
> In the first effort to separate Stellar from Metron, I left a truncated
> version of Metron's configuration model in Stellar. This isn't very
> satisfactory. The goals should be:
> # User must be able to configure Stellar itself, regardless of the platform
> it is plugged into.
> # Stellar's configuration model should not be grossly Metron-specific;
> ideally it should be storage-agnostic and possibly schema-driven.
> # We would like to still be able to use Stellar to manipulate the
> Metron-specific config when plugged into Metron. Reading and setting are
> required, since Stellar has become a major tool of convenience for managing
> Metron's config.
> # We would like to be able to use Stellar to manipulate the
> application-specific config of other platforms when Stellar is plugged into
> them, if the other platform allows. Reading is more important than setting.
> The last two items argue for a client interface layer where the platform can
> provision Stellar's config model as the platform prefers.
> Investigate whether Apache commons configuration would be appropriate,
> perhaps with add-ins for JSON sources and Curator event support.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
