[jira] [Commented] (KARAF-1408) These changes of the PID(org.apache.karaf.cellar.groups) which in both blacklist inbound and blacklist outbound can be synchronized to other karaf instance

["Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>]

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

Jean-Baptiste Onofré commented on KARAF-1408:
---------------------------------------------

Not sure to understand this Jira.

You are talking about default.features.blacklist.outbound which concerns feature cluster event, and you talk about config:edit which concerns config cluster event.

If you're talking about config:edit sync, it's the "expected" behavior right now as the LocalConfigurationListener doesn't send the cluster event.
                
> These changes of the PID(org.apache.karaf.cellar.groups)  which in both blacklist inbound and blacklist outbound can be synchronized to other karaf instance
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KARAF-1408
>                 URL: https://issues.apache.org/jira/browse/KARAF-1408
>             Project: Karaf
>          Issue Type: Bug
>          Components: cellar-config
>    Affects Versions: cellar-2.2.3
>            Reporter: Meifang Shen
>            Assignee: Jean-Baptiste Onofré
>             Fix For: cellar-3.0.0, cellar-2.2.4
>
>
> About the configuration of the PID(org.apache.karaf.cellar.groups) as follows:
> {noformat} 
> default.config.whitelist.inbound=*
> default.config.whitelist.outbound=*
> default.config.blacklist.inbound=org.apache.karaf.cellar.groups,org.apache.karaf.cellar.instance,org.apache.karaf.cellar.node,org.apache.karaf.management
> default.config.blacklist.outbound=org.apache.karaf.cellar.groups,org.apache.karaf.cellar.instance,org.apache.karaf.cellar.node,org.apache.karaf.management
> default.config.sync=true
> default.features.whitelist.inbound=*
> default.features.whitelist.outbound=*
> default.features.blacklist.inbound=cellar,jetty,http
> default.features.blacklist.outbound =cellar,jetty,http
> default.features.sync=true
> default.features.repositories.sync=true
> default.bundle.whitelist.inbound=none
> default.bundle.whitelist.outbound=none
> default.bundle.sync=false
> default.obr.urls.sync=true
> default.obr.bundles.sync=true
> {noformat} 
> Please note: the pid "org.apache.karaf.cellar.groups" is in blacklist.
> Locally there are three karaf instances(node1, node2, node3), all are installed the feature cellar.
> (1)would like to test this property "default.features.blacklist.inbound".
> Expect that blacklist inbound works as below:
> => one node1 has feature("eventadmin") in blacklist inbound, node2 and node3 have not..., node2 installs feature, node3 gets synchronized, node1 not...
> When execute the below command on node1 manually:
> {noformat}
> config:edit org.apache.karaf.cellar.groups; config:propappend default.features.blacklist.inbound ,eventadmin; config:update
> {noformat}
> Then sometimes changed this pid configuration on node1, but often changed this pid configuration on node2 or node3.
> It seems that the configuration of this pid org.apache.karaf.cellar.groups can be synchronized.
> (2)would like to test this property "default.features.blacklist.outbound".
> Expect that blacklist outbound works as below:
> => one node1 has feature in blacklist outbound, all others have not... if node1 installs blacklisted feature, it shall not be synchronized.
> Execute the below command on node1 manually:
> {noformat}
> config:edit org.apache.karaf.cellar.groups; config:propappend default.features.blacklist.outbound ,eventadmin; config:update
> {noformat}
> Then same as the above case. should only the configuration on node1 can be changed, however often node1 not changed but node2 or node3 would be changed.
> (3) If firstly changed the above configuration(blacklist.outbound or blacklist.inbound) manually not use the above command, then start three karaf instances, then it worked as expected.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira