Karaf
  1. Karaf
  2. 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

    Details

      Description

      About the configuration of the PID(org.apache.karaf.cellar.groups) as follows:

       
      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
      

      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:

      config:edit org.apache.karaf.cellar.groups; config:propappend default.features.blacklist.inbound ,eventadmin; config:update
      

      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:

      config:edit org.apache.karaf.cellar.groups; config:propappend default.features.blacklist.outbound ,eventadmin; config:update
      

      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.

        Activity

        Hide
        Jean-Baptiste Onofré added a comment -

        Just a reminder, for now config:edit action doesn't broadcast a cluster event, so the configuration won't be sync to other nodes if you use config:edit.

        Show
        Jean-Baptiste Onofré added a comment - Just a reminder, for now config:edit action doesn't broadcast a cluster event, so the configuration won't be sync to other nodes if you use config:edit.
        Hide
        Jean-Baptiste Onofré added a comment -

        It should be fixed with the latest enhancement on the producers check.

        Show
        Jean-Baptiste Onofré added a comment - It should be fixed with the latest enhancement on the producers check.
        Hide
        Meifang Shen added a comment -

        Hi Jean-Baptiste, yeah, I'm talking about config:edit sync, but the pid "org.apache.karaf.cellar.groups" is in default.config.blacklist.inbound and default.config.blacklist.outbound, If I change this pid "org.apache.karaf.cellar.groups" on node1, then it should not be synchronized on node2 or on node3, right?

        The situation is that the changes on node1 can be synchronized to node2 or node3.

        For default.features.blacklist.outbound I'm talking about, it is an automatic testcase I want to test.

        Show
        Meifang Shen added a comment - Hi Jean-Baptiste, yeah, I'm talking about config:edit sync, but the pid "org.apache.karaf.cellar.groups" is in default.config.blacklist.inbound and default.config.blacklist.outbound, If I change this pid "org.apache.karaf.cellar.groups" on node1, then it should not be synchronized on node2 or on node3, right? The situation is that the changes on node1 can be synchronized to node2 or node3. For default.features.blacklist.outbound I'm talking about, it is an automatic testcase I want to test.
        Hide
        Jean-Baptiste Onofré added a comment -

        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.

        Show
        Jean-Baptiste Onofré added a comment - 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.
        Hide
        Meifang Shen added a comment -

        Please note: for whitelist inbound or outbound, also has this issue.
        On node1 execute command mentioned in description, then not change node1 configuration, but node2 or node3.

        Show
        Meifang Shen added a comment - Please note: for whitelist inbound or outbound, also has this issue. On node1 execute command mentioned in description, then not change node1 configuration, but node2 or node3.

          People

          • Assignee:
            Jean-Baptiste Onofré
            Reporter:
            Meifang Shen
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development