Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Gyrex/Administrator Guide/Cloud"
(New page: Cloud Admin) |
(created) |
||
| Line 1: | Line 1: | ||
| − | Cloud | + | == Cloud == |
| + | The Gyrex cloud functionality is implemented based on [http://hadoop.apache.org/zookeeper/ ZooKeeper]. When running in development mode, an embedded ZooKeeper server is started automatically so you don't have to configure anything at all. For production environments we highly recommend running a standalone ZooKeeper ensemble. Please have a look at the [http://hadoop.apache.org/zookeeper/docs/current/zookeeperAdmin.html ZooKeeper Administrator's Guide] for details on how to setup your own ensemble. | ||
| + | |||
| + | === Node Management === | ||
| + | An essential part of a cloud is node membership. Node membership in Gyrex is implemented by explicit approval of nodes. Each node has a unique identifier. Upon first start a new one is generated. It's also possible to manually set node ids. However, you need to ensure that node ids are unique. No two nodes with the same identifier are allows to join the cloud. | ||
| + | |||
| + | After a new node joins a cloud it will be registered with a pending state. In this state the node is not allowed to participate in any cloud activity other than node registration. An administrator need to explicitly approve the node first. Once the node has been approved it will become online. | ||
| + | |||
| + | === Console Commands === | ||
| + | Two commands are available in the Equinox OSGi console for managing and analyzing the cloud. They both come with a small syntax help | ||
| + | <pre> | ||
| + | osgi> help | ||
| + | [...] | ||
| + | ---Cloud Commands--- | ||
| + | cloud <cmd> [args] | ||
| + | approve nodeId | ||
| + | ls pending|approved | ||
| + | retire nodeId | ||
| + | ---ZooKeeper Commands--- | ||
| + | zk <cmd> [args] | ||
| + | create [-s] [-e] path [data] | ||
| + | get path | ||
| + | ls [-r] path | ||
| + | rm [-r] path | ||
| + | set path data | ||
| + | stat path | ||
| + | sync path | ||
| + | [...] | ||
| + | osgi> | ||
| + | </pre> | ||
| + | |||
| + | ''List pending (unapproved) nodes:'' | ||
| + | <pre> | ||
| + | osgi> cloud ls pending | ||
| + | [nodeId] (hostname) | ||
| + | ... | ||
| + | osgi> | ||
| + | </pre> | ||
| + | |||
| + | ''Approve a node:'' | ||
| + | <pre> | ||
| + | osgi> cloud approve <nodeId> | ||
| + | </pre> | ||
Revision as of 04:32, 14 January 2011
Cloud
The Gyrex cloud functionality is implemented based on ZooKeeper. When running in development mode, an embedded ZooKeeper server is started automatically so you don't have to configure anything at all. For production environments we highly recommend running a standalone ZooKeeper ensemble. Please have a look at the ZooKeeper Administrator's Guide for details on how to setup your own ensemble.
Node Management
An essential part of a cloud is node membership. Node membership in Gyrex is implemented by explicit approval of nodes. Each node has a unique identifier. Upon first start a new one is generated. It's also possible to manually set node ids. However, you need to ensure that node ids are unique. No two nodes with the same identifier are allows to join the cloud.
After a new node joins a cloud it will be registered with a pending state. In this state the node is not allowed to participate in any cloud activity other than node registration. An administrator need to explicitly approve the node first. Once the node has been approved it will become online.
Console Commands
Two commands are available in the Equinox OSGi console for managing and analyzing the cloud. They both come with a small syntax help
osgi> help [...] ---Cloud Commands--- cloud <cmd> [args] approve nodeId ls pending|approved retire nodeId ---ZooKeeper Commands--- zk <cmd> [args] create [-s] [-e] path [data] get path ls [-r] path rm [-r] path set path data stat path sync path [...] osgi>
List pending (unapproved) nodes:
osgi> cloud ls pending [nodeId] (hostname) ... osgi>
Approve a node:
osgi> cloud approve <nodeId>