You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Dosta <dr...@gmail.com> on 2012/05/15 11:13:49 UTC

Cellar Bundle Sync help

Hello, 

I'm using Karaf 2.2.7 and Cellar 2.2.3 on two nodes (node 2 is remote).
Group configuration is set to allow feature, config and bundle sync.

Feature and configuration sync works great but bundle sync is not
operational. Documentation is quite short on this part so could anyone
direct me if I'm doing something wrong.

For the feature sync I used the "features:addurl URL" and "features:install
X" commands and nodes got synced.
For the configuration sync I used the "config:XXX" commands and nodes got
synced.

For the bundle sync I'm using the "bundle:install X", "bundle:start X",
"bundle:stop X" (same as the "osgi:install" or "install") and nodes don't
get synchronized. What am I doing wrong?


I'm not quite familiar with the "group components" either (group feature,
bundles, configuration). What do the actions performed on them actually DO?
Listing these components gets me a list of mutual components that node 1 and
node 2 have but installing/starting/stopping these components doesn't
trigger any changes to the nodes. Where is this group instance actually
located, because I cant access bundle behaviour even though the group bundle
is stated as started?


I tried using Karaf 3.0.0 and Cellar 3.0.0 but I didn't even get this far.
Any recommendations on what snapshot versions to use?
 

Thanks 

-D 

--
View this message in context: http://karaf.922171.n3.nabble.com/Cellar-Bundle-Sync-help-tp3987690.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Cellar Bundle Sync help

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,

My comments inline:

> Just to summarize:
> - For feature sync, use "features:OPERATION" (local node operation is
> propagated to the group and all the nodes).
Both work, feature:* or cluster:feature*

> - For configuration sync, use "config:OPERATION" (local node operation is
> propagated to the group and all the nodes).
Both work, config:* or cluster:config*

> - For bundle sync, use "cluster:bundle-OPERATION" and only that (GROUP
> operation is propagated to all the nodes). "Local node" bundle commands like
> bundle:install don't trigger the sync.
If sync is enable for the group ([group].bundle.sync=true), local 
commands (bundle:install, bundle:start, etc) should be sync on the 
cluster group (for the nodes in the same group as the local node).

>
> This means that if you perform operations using the webconsole (2.2.7 has
> only cellar group list and no special group-bundle management section), only
> the features and configuration operations will be synced with other nodes.
> This is because the local node bundle management in webconsole (start, stop,
> install...) uses the "bundle:OPERATION" commands and not the
> "cluster:bundle-OPERATION" commands.

No it should work also ;)

Regards
JB

>
>
> Is this correct?
>
> Thank you for your help,
> DD
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Cellar-Bundle-Sync-help-tp3987690p3988022.html
> Sent from the Karaf - User mailing list archive at Nabble.com.

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Cellar Bundle Sync help

Posted by Dosta <dr...@gmail.com>.
Thank you for the hint.

I was listing group bundles on node 1 all morning, but not on node 2. When I
tried to list them on node 2 I was greeted with a "command not found".

It seams that the cellar.bundle had crashed:
[ 55] [Active] [Faliure] [80] Apache Karaf :: Cellar :: Bundle (2.2.3)

After the node 2 restart, everything was working fine. Bundles are being
synced also (but only using the cluster:bundle-install" command).

Just to summarize:
- For feature sync, use "features:OPERATION" (local node operation is
propagated to the group and all the nodes).
- For configuration sync, use "config:OPERATION" (local node operation is
propagated to the group and all the nodes).
- For bundle sync, use "cluster:bundle-OPERATION" and only that (GROUP
operation is propagated to all the nodes). "Local node" bundle commands like
bundle:install don't trigger the sync.

This means that if you perform operations using the webconsole (2.2.7 has
only cellar group list and no special group-bundle management section), only
the features and configuration operations will be synced with other nodes.
This is because the local node bundle management in webconsole (start, stop,
install...) uses the "bundle:OPERATION" commands and not the
"cluster:bundle-OPERATION" commands.


Is this correct?

Thank you for your help,
DD

--
View this message in context: http://karaf.922171.n3.nabble.com/Cellar-Bundle-Sync-help-tp3987690p3988022.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Cellar Bundle Sync help

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Do you have something in the distributed map:

cluster:bundle-list default ?

FYI, Cellar 2.2.4 should be release very soon (in a couple of days) and 
provide a lot of bug fixes/enhancements, including around bundles.

Regards
JB

On 05/15/2012 12:29 PM, Dosta wrote:
> Hi JB,
>
> Yes, I have set it to true during configuration, and the config:list shows
> it to be set to true so it has updated the configuration.
>
> Full groups configuration file:
> ==============================
> 	default.config.whitelist.inbound=*
> 	default.config.whitelist.outbound=*
>
> default.config.blacklist.inbound=org.apache.karaf.cellar.instance,org.apache.karaf.cellar.node,org.apache.karaf.management
>
> default.config.blacklist.outbound=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
> 	default.features.blacklist.outbound=cellar
> 	default.features.sync=true
> 	default.features.repositories.sync=true
>
> 	default.bundle.whitelist.inbound=*
> 	default.bundle.whitelist.outbound=*
> 	default.bundle.sync=true
>
> 	default.obr.urls.sync=true
> 	default.obr.bundles.sync=true
> ==============================
>
> Thank you for your quick reply,
> D
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Cellar-Bundle-Sync-help-tp3987690p3987758.html
> Sent from the Karaf - User mailing list archive at Nabble.com.

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Cellar Bundle Sync help

Posted by Dosta <dr...@gmail.com>.
Hi JB,

Yes, I have set it to true during configuration, and the config:list shows
it to be set to true so it has updated the configuration.

Full groups configuration file:
==============================
	default.config.whitelist.inbound=*
	default.config.whitelist.outbound=*

default.config.blacklist.inbound=org.apache.karaf.cellar.instance,org.apache.karaf.cellar.node,org.apache.karaf.management

default.config.blacklist.outbound=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
	default.features.blacklist.outbound=cellar
	default.features.sync=true
	default.features.repositories.sync=true

	default.bundle.whitelist.inbound=*
	default.bundle.whitelist.outbound=*
	default.bundle.sync=true

	default.obr.urls.sync=true
	default.obr.bundles.sync=true
==============================

Thank you for your quick reply,
D

--
View this message in context: http://karaf.922171.n3.nabble.com/Cellar-Bundle-Sync-help-tp3987690p3987758.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Cellar Bundle Sync help

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,

could you check that default.bundle.sync is true (it's false by default) ?

Regards
JB

On 05/15/2012 11:13 AM, Dosta wrote:
> Hello,
>
> I'm using Karaf 2.2.7 and Cellar 2.2.3 on two nodes (node 2 is remote).
> Group configuration is set to allow feature, config and bundle sync.
>
> Feature and configuration sync works great but bundle sync is not
> operational. Documentation is quite short on this part so could anyone
> direct me if I'm doing something wrong.
>
> For the feature sync I used the "features:addurl URL" and "features:install
> X" commands and nodes got synced.
> For the configuration sync I used the "config:XXX" commands and nodes got
> synced.
>
> For the bundle sync I'm using the "bundle:install X", "bundle:start X",
> "bundle:stop X" (same as the "osgi:install" or "install") and nodes don't
> get synchronized. What am I doing wrong?
>
>
> I'm not quite familiar with the "group components" either (group feature,
> bundles, configuration). What do the actions performed on them actually DO?
> Listing these components gets me a list of mutual components that node 1 and
> node 2 have but installing/starting/stopping these components doesn't
> trigger any changes to the nodes. Where is this group instance actually
> located, because I cant access bundle behaviour even though the group bundle
> is stated as started?
>
>
> I tried using Karaf 3.0.0 and Cellar 3.0.0 but I didn't even get this far.
> Any recommendations on what snapshot versions to use?
>
>
> Thanks
>
> -D
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Cellar-Bundle-Sync-help-tp3987690.html
> Sent from the Karaf - User mailing list archive at Nabble.com.

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com