Return-Path: X-Original-To: apmail-karaf-commits-archive@minotaur.apache.org Delivered-To: apmail-karaf-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 92B8A175A4 for ; Mon, 19 Jan 2015 15:16:42 +0000 (UTC) Received: (qmail 5277 invoked by uid 500); 19 Jan 2015 15:16:44 -0000 Delivered-To: apmail-karaf-commits-archive@karaf.apache.org Received: (qmail 5246 invoked by uid 500); 19 Jan 2015 15:16:44 -0000 Mailing-List: contact commits-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list commits@karaf.apache.org Received: (qmail 5237 invoked by uid 99); 19 Jan 2015 15:16:44 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Jan 2015 15:16:44 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 590C9E0383; Mon, 19 Jan 2015 15:16:44 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: jbonofre@apache.org To: commits@karaf.apache.org Message-Id: X-Mailer: ASF-Git Admin Mailer Subject: karaf-cellar git commit: Fix minor issue in cluster groups documentation Date: Mon, 19 Jan 2015 15:16:44 +0000 (UTC) Repository: karaf-cellar Updated Branches: refs/heads/master bd141b81a -> 37942b9d4 Fix minor issue in cluster groups documentation Project: http://git-wip-us.apache.org/repos/asf/karaf-cellar/repo Commit: http://git-wip-us.apache.org/repos/asf/karaf-cellar/commit/37942b9d Tree: http://git-wip-us.apache.org/repos/asf/karaf-cellar/tree/37942b9d Diff: http://git-wip-us.apache.org/repos/asf/karaf-cellar/diff/37942b9d Branch: refs/heads/master Commit: 37942b9d48a9da8fac751f2abaeb464f73b6fed0 Parents: bd141b8 Author: Jean-Baptiste Onofré Authored: Mon Jan 19 16:16:24 2015 +0100 Committer: Jean-Baptiste Onofré Committed: Mon Jan 19 16:16:24 2015 +0100 ---------------------------------------------------------------------- manual/src/main/webapp/user-guide/groups.conf | 82 ---------------------- 1 file changed, 82 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/karaf-cellar/blob/37942b9d/manual/src/main/webapp/user-guide/groups.conf ---------------------------------------------------------------------- diff --git a/manual/src/main/webapp/user-guide/groups.conf b/manual/src/main/webapp/user-guide/groups.conf index ce89fd8..c48ce42 100644 --- a/manual/src/main/webapp/user-guide/groups.conf +++ b/manual/src/main/webapp/user-guide/groups.conf @@ -33,88 +33,6 @@ x | default | node2:5702 node1:5701(x) | test | {code} -h2. Group configuration - -You can see the configuration PID associated with a given group, for instance the default group: - -{code} -karaf@root()> cluster:config-list default |more ----------------------------------------------------------------- -Pid: org.apache.karaf.command.acl.jaas -Located: cluster/local -Blocked: -Properties: - update = admin - service.pid = org.apache.karaf.command.acl.jaas ----------------------------------------------------------------- -Pid: org.apache.karaf.service.acl.command.system.start-level -Located: cluster/local -Blocked: -Properties: - execute = admin # admin can set any start level, including < 100 - start-level[/[^0-9]*/] = viewer # viewer can obtain the current start level - execute[/.*/,/[^0-9]*/] = viewer # viewer can obtain the current start level - * = * - start-level = admin # admin can set any start level, including < 100 - service.guard = (&(osgi.command.scope=system)(osgi.command.function=start-level)) - execute[/.*/,/.*[0-9][0-9][0-9]+.*/] = manager # manager can set startlevels above 100 - service.pid = org.apache.karaf.service.acl.command.system.start-level - start-level[/.*[0-9][0-9][0-9]+.*/] = manager # manager can set startlevels above 100 ----------------------------------------------------------------- -... -{code} - -You can see that for each configuration PID, you have where the configuration is located: locally to the node or on the cluster. -You also have the blocking policy (inbound or outbound). - -You can use the cluster:config-property-list and config-property-set commands to list, add and edit the configuration. - -For instance, in the test group, we don't have any configuration: - -{code} -karaf@root()> cluster:config-list test -No PIDs found for group:test -{code} - -We can create a tstcfg config in the test group, containing name=value property: - -{code} -karaf@root()> cluster:config-property-set test tstcfg name value -{code} - -Now, we have this property in the test group: - -{code} -karaf@root()> cluster:config-property-list test testcfg -Property list for configuration PID testcfg for cluster group test - name = value - service.pid = testcfg -{code} - -h2. Group nodes - -You can declare a node member of one of more groups: - -{code} -karaf@node2()> cluster:group-join test node1:5701 - | Group | Members ------------------------------------------------ -x | default | node2:5702(x) node1:5701 - | test | node1:5701 -{code} - -The node can be local or remote. - -Now, the nodes of a given group will inherit of all configuration defined in the group. This means that -node1 now knows the tstcfg configuration because it's a member of the test group: - -{code} -karaf@root()> config:edit tstcfg -karaf@root()> property-list - service.pid = testcfg - name = value -{code} - h2. Clustered Resources and Cluster Groups h3. Features