JB, Sorry for the delay in my response. I've configured all as discussed. What i'm seeing now is that if an child node is not logged in when an install is initiated, that event doesn't get pushed down once the child node reconnects back in to the cluster group. I'm not sure if that has to do with any of the black-listing or consumer / producer suppression that i've done. Any suggestions?
On Sat, Sep 27, 2014 at 12:12 PM, jbonofre [via Karaf] < [email protected]> wrote: > Actually, the manager should have consumer set to OFF, producer ON, and > the opposite on the "managed" site. > > Regards > JB > > On 09/27/2014 03:33 PM, bwest wrote: > > > JB, > > > > Unless i'm not doing something correctly, i'm pretty sure that the > activemq > > install is not be initiated on the site1 node. Also for informational > > purposes i'm running karaf 3.0.1 > > > > I can add the repo and have them push down: > > > > > > > > *On the Manager Node:* > > karaf@root()> cluster:feature-repo-add dev-sites > > mvn:org.apache.activemq/activemq-karaf/5.10.0/xml/features > > > > > > *On the SITE NODE* > > karaf@root()> cluster:feature-repo-list dev-sites > > URL > > ------------------------------------------------------------------ > > mvn:org.apache.karaf.features/standard/3.0.1/xml/features > > mvn:org.apache.karaf.features/enterprise/3.0.1/xml/features > > mvn:org.jclouds.karaf/jclouds-karaf/1.4.0/xml/features > > mvn:org.ops4j.pax.web/pax-web-features/3.1.0/xml/features > > mvn:org.ops4j.pax.cdi/pax-cdi-features/0.7.0/xml/features > > mvn:org.apache.karaf.cellar/apache-karaf-cellar/3.0.0/xml/features > > mvn:org.apache.karaf.features/spring/3.0.1/xml/features > > mvn:org.apache.activemq/activemq-karaf/5.10.0/xml/features > > karaf@root()> > > > > > > I can also see the cluster:feature list dev-sites and see the activemq > > features there as well. > > > > *FROM THE SITES NODE:* > > karaf@root()> cluster:feature-list dev-sites | grep -i activemq > > activemq-camel | 5.10.0 | > > activemq-broker-noweb | 5.10.0 | > > activemq-web-console | 5.10.0 | > > activemq-blueprint | 5.10.0 | > > activemq-broker | 5.10.0 | > > > > > > *So from the the manager Node, I issue the install on the dev-sites > group > > that site1 is part of:* > > karaf@root()> cluster:feature-repo-add dev-sites > > mvn:org.apache.activemq/activemq-karaf/5.10.0/xml/features > > karaf@root()> cluster:feature-list dev-sites | grep -i activemq > > activemq-camel | 5.10.0 | > > activemq-broker-noweb | 5.10.0 | > > activemq-web-console | 5.10.0 | > > activemq-blueprint | 5.10.0 | > > activemq-broker | 5.10.0 | > > karaf@root()> cluster:feature-install dev-sites activemq-broker > > karaf@root()> > > > > > > *And when I review on the Site 1 node, i see: * > > karaf@root()> cluster:feature-list dev-sites | grep -i activemq > > activemq-camel | 5.10.0 | > > activemq-broker-noweb | 5.10.0 | > > activemq-web-console | 5.10.0 | > > activemq-blueprint | 5.10.0 | > > activemq-broker | 5.10.0 | > > karaf@root()> > > > > > > I do have one note on the the site nodes, i have the producer status set > to > > off, I wouldn't think that should affect an incoming request. Would > that > > be having an effect? > > > > > > > > > > On Sat, Sep 27, 2014 at 2:22 AM, jbonofre [via Karaf] < > > [hidden email] <http://user/SendEmail.jtp?type=node&node=4035563&i=0>> > wrote: > > > >> It's normal for the local node (manager) (and it's debug message, just > >> for information), activemq-broker feature should be install on site1 > right > >> ? > >> > >> Regards > >> JB > >> > >> On 09/26/2014 10:56 PM, bwest wrote: > >> > >>> JB, > >>> > >>> I'm sorry i mispoke. Let me outline this a bit better: > >>> > >>> > >>> Here is my group list and associated nodes: > >>> > >>> karaf@root()> cluster:group-list > >>> | Group | Members > >>> -------------------------------------------- > >>> x| manager | BWEST.stuff.com:5701(x) > >>> | default | > >>> | dev-sites | site1.stuff.com:5701 > >>> > >>> > >>> > >>> Then I do this: > >>> > >>> karaf@root()> cluster:feature-install dev-sites activemq-broker > >>> > >>> Which results in the following log message: > >>> > >>> 2014-09-26 16:55:13,236 | DEBUG | ool-10-thread-31 | > >>> FeaturesSynchronizer | 86 - > >>> org.apache.karaf.cellar.features - 3.0.0 | CELLAR FEATURES: node is > >>> not part of the event cluster group dev-sites > >>> > >>> > >>> > >>> > >>> On Fri, Sep 26, 2014 at 4:50 PM, jbonofre [via Karaf] > >>> <[hidden email] <http://user/SendEmail.jtp?type=node&node=4035557&i=0>> > > >> wrote: > >>>> Hi, > >>>> > >>>> not with feature:install, yes with cluster:feature-install (actually, > >>>> it's the difference, cluster:feature-install accepts a cluster group > as > >>>> target). > >>>> > >>>> Regards > >>>> JB > >>>> > >>>> On 09/26/2014 10:48 PM, bwest wrote: > >>>> > >>>>> JB, > >>>>> > >>>>> Thanks so much for your reply. I've done all that you suggested. > >>>>> What i'm noticing now is that when I try to do an install on the > other > >>>>> group, i get a message in the log : > >>>>> > >>>>> 86 - org.apache.karaf.cellar.features - 3.0.0 | CELLAR FEATURES: > >> node > >>>>> is not part of the event cluster group dev-sites > >>>>> > >>>>> Is there a way to issue feature:install on a cluster group that the > >>>>> issuer is not part of? > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> On Thu, Sep 25, 2014 at 9:47 AM, jbonofre [via Karaf] > >>>>> <[hidden email]> wrote: > >>>>>> Hi, > >>>>>> > >>>>>> by default in Cellar, all nodes are manager for the others. > >>>>>> So all action that you do on one node is push/spread on the other > >> nodes > >>>>>> (in the cluster group). > >>>>>> > >>>>>> More over, Cellar sync the actions: not the bundles itself. The > nodes > >>>>>> have to access to a shared repository where they will download the > >>>>>> artifacts. > >>>>>> > >>>>>> What you can do: > >>>>>> > >>>>>> 1/ after installing Cellar on all nodes, you create a new cluster > >> group: > >>>>>> cluster:group-create manager > >>>>>> > >>>>>> 2/ you define the manager node in the manager cluster group: > >>>>>> cluster:group-set manager nodex:xxx > >>>>>> > >>>>>> 3/ on the manager group, you can do > >>>>>> cluster:[bundle-install|feature-install] with default cluster > group: > >>>>>> cluster:feature-install default xxxx > >>>>>> > >>>>>> 4/ you can play with whitelist/blacklist (in > >>>>>> etc/org.apache.karaf.cellar.groups.cfg) to completely isolate the > >>>>>> manager node > >>>>>> > >>>>>> Regards > >>>>>> JB > >>>>>> > >>>>>> On 09/25/2014 03:34 PM, bwest wrote: > >>>>>> > >>>>>>> Greetings, > >>>>>>> > >>>>>>> I'm very new with Karaf (3.0.1) and cellar. Basically I'm trying > to > >> use > >>>>>>> a > >>>>>>> specific Karaf container instance as a Central Management node. > >>>>>>> > >>>>>>> The question I have is how can I install a bundle on the central > >> node, > >>>>>>> have > >>>>>>> it push down to the child nodes, without it actually running on > the > >>>>>>> central > >>>>>>> node. Basically I don't want any features or bundles to be run on > >> the > >>>>>>> central node. For instance, i don't want the central node to > >> running an > >>>>>>> activemq instance or associated camel routes etc.... > >>>>>>> > >>>>>>> My vision would be to have the central node just push things down > to > >> the > >>>>>>> child nodes, where the bundles / features would be installed and > >> ran. > >>>>>>> > >>>>>>> > >>>>>>> Sorry if i'm using terminology incorrectly, i'm very new to this > >> product > >>>>>>> and > >>>>>>> these concepts. Any help or pointers would be very appreciated. > >>>>>>> > >>>>>>> Thank you! > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> -- > >>>>>>> View this message in context: > >>>>>>> > >>>>>>> > >> > http://karaf.922171.n3.nabble.com/using-karaf-node-instance-as-central-managment-tp4035520.html > >>>>>>> Sent from the Karaf - User mailing list archive at Nabble.com. > >>>>>>> > >>>>>> > >>>>>> -- > >>>>>> Jean-Baptiste Onofré > >>>>>> [hidden email] > >>>>>> http://blog.nanthrax.net > >>>>>> Talend - http://www.talend.com > >>>>>> > >>>>>> > >>>>>> ________________________________ > >>>>>> If you reply to this email, your message will be added to the > >> discussion > >>>>>> below: > >>>>>> > >>>>>> > >> > http://karaf.922171.n3.nabble.com/using-karaf-node-instance-as-central-managment-tp4035520p4035521.html > >>>>>> To unsubscribe from using karaf node instance as central managment, > >> click > >>>>>> here. > >>>>>> NAML > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> View this message in context: > >>>>> > >> > http://karaf.922171.n3.nabble.com/using-karaf-node-instance-as-central-managment-tp4035520p4035553.html > >>>>> Sent from the Karaf - User mailing list archive at Nabble.com. > >>>>> > >>>> > >>>> -- > >>>> Jean-Baptiste Onofré > >>>> [hidden email] > >>>> http://blog.nanthrax.net > >>>> Talend - http://www.talend.com > >>>> > >>>> > >>>> ________________________________ > >>>> If you reply to this email, your message will be added to the > >> discussion > >>>> below: > >>>> > >> > http://karaf.922171.n3.nabble.com/using-karaf-node-instance-as-central-managment-tp4035520p4035554.html > >>>> To unsubscribe from using karaf node instance as central managment, > >> click > >>>> here. > >>>> NAML > >>> > >>> > >>> > >>> > >>> -- > >>> View this message in context: > >> > http://karaf.922171.n3.nabble.com/using-karaf-node-instance-as-central-managment-tp4035520p4035555.html > >>> Sent from the Karaf - User mailing list archive at Nabble.com. > >>> > >> > >> -- > >> Jean-Baptiste Onofré > >> [hidden email] <http://user/SendEmail.jtp?type=node&node=4035557&i=1> > >> http://blog.nanthrax.net > >> Talend - http://www.talend.com > >> > >> > >> ------------------------------ > >> If you reply to this email, your message will be added to the > discussion > >> below: > >> > >> > http://karaf.922171.n3.nabble.com/using-karaf-node-instance-as-central-managment-tp4035520p4035557.html > >> To unsubscribe from using karaf node instance as central managment, > click > >> here > >> < > >> . > >> NAML > >> < > http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > > >> > > > > > > > > > > -- > > View this message in context: > http://karaf.922171.n3.nabble.com/using-karaf-node-instance-as-central-managment-tp4035520p4035559.html > > Sent from the Karaf - User mailing list archive at Nabble.com. > > > > -- > Jean-Baptiste Onofré > [hidden email] <http://user/SendEmail.jtp?type=node&node=4035563&i=1> > http://blog.nanthrax.net > Talend - http://www.talend.com > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://karaf.922171.n3.nabble.com/using-karaf-node-instance-as-central-managment-tp4035520p4035563.html > To unsubscribe from using karaf node instance as central managment, click > here > <http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4035520&code=Yndlc3RlcmZpZWxkQGdtYWlsLmNvbXw0MDM1NTIwfDEwNTI2NDM2MzE=> > . > NAML > <http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://karaf.922171.n3.nabble.com/using-karaf-node-instance-as-central-managment-tp4035520p4035616.html Sent from the Karaf - User mailing list archive at Nabble.com.
