0 Replies Latest reply on Aug 1, 2013 12:21 PM by N David Brown

    6.1 EA - Ensemble profile issues

    N David Brown Newbie

      After creating and configuring our initial fabric, we grow the Zookeeper ensemble to 3 nodes using the following commands:

       

        container-create-ssh --host itfus021 --user itfus021 root2

        container-create-ssh --host itfus022 --user itfus022 root3

        ensemble-add root2 root3

       

      Following this, container-list shows the following:

       

        [id]                           [version] [alive] [profiles]                                         [provision status]

        root*                          1.0       true    fabric, fabric-ensemble-0000-1, jboss-fuse-full, fabric-ensemble-0001-1 success

        root2                          1.0       true    default, fabric-ensemble-0001-2                    success

        root3                          1.0       true    default, fabric-ensemble-0001-3                    success

       

      Questions:

       

      1. When a node is added to the ensemble, why doesn't it automatically have the 'fabric' profile applied?

       

      As far as I'm aware, without the 'fabric' profile (or a similar custom profile) applied to the new ensemble nodes, you won't have access to fabric commands on the karaf shell. Specifically, the following features would be missing:

       

        fabric-commands

        fabric-agent

        fabric-partition

        fabric-maven-proxy

       

      This would surely be a nuisance (or worse?) if anything went wrong with the initial ensemble node, since you'd have to either manually install the features on (at least) one of the surviving ensemble nodes or else apply the 'fabric' profile before being able to manipulate your fabric on the shell to recover from the issues.

       

      In fact, since fabric-maven-proxy is absent from the other ensemble nodes, is it not true that manual resolution of the feature would fail at this point of the initial ensemble node going and you attempting a manual fix from the other ensemble nodes?

       

      2. Why does the 'root' container list two fabric ensemble profiles now? There's needless duplication of configuration; surely this is a bug:

       

      JBossFuse:admin@root> profile-display -o fabric-ensemble-0000-1

      Profile id: fabric-ensemble-0000-1

      Version   : 1.0

      Attributes:

              parents: fabric-ensemble-0000

              hidden: true

      Containers: root

       

       

      Container settings

      ----------------------------

       

       

      Configuration details

      ----------------------------

      PID: org.fusesource.fabric.zookeeper.server-0000

        initLimit 10

        clientPort 2181

        tickTime 2000

        syncLimit 5

        dataDir data/zookeeper/0000

        clientPortAddress 0.0.0.0

       

       

       

       

      JBossFuse:admin@root> profile-display -o fabric-ensemble-0001-1

      Profile id: fabric-ensemble-0001-1

      Version   : 1.0

      Attributes:

              parents: fabric-ensemble-0001

              hidden: true

      Containers: root

       

       

      Container settings

      ----------------------------

       

       

      Configuration details

      ----------------------------

      PID: org.fusesource.fabric.zookeeper.server-0001

        initLimit 10

        clientPort 2182

        server.3 ${zk:root3/ip}:2888:3888

        tickTime 2000

        syncLimit 5

        server.2 ${zk:root2/ip}:2888:3888

        dataDir data/zookeeper/0001

        clientPortAddress 0.0.0.0

        server.1 ${zk:root/ip}:2888:3888

        server.id 1