DCI Module User's Guide

• Usage instructions
• The Packaging Assembling Tool

Usage Instructions for the DCI

Starting an OpenCCM Distributed Computing Infrastructure Manager

An OpenCCM Distributed Computing Infrastructure (DCI) is the federation of a set of distributed nodes in order to form a unified distributed deployment domain.

An OpenCCM DCI Manager provides functionalities to manage an OpenCCM DCI domain, to (un)register OpenCCM Node Managers, to install and manage CORBA component assemblies, to access meta information about the DCI domain. This manager also implements the ComponentHomeFinder service.

The dci_start script starts an OpenCCM DCI Manager.

Its usage is the following:

$ dci_start
usage: dci_start [-h|--help] <dci_name>
$

Each OpenCCM DCI Manager must be started with an unique name, e.g.:

$ dci_start MyDCIName
The OpenCCM DCI Manager MyDCIName will be started.
Launching the OpenCCM DCI Manager MyDCIName.
Default DCI Manager set.
The OpenCCM DCI Manager MyDCIName is started.
$

Warning: Each started OpenCCM DCI Manager must have a distinct name, e.g.:

$ dci_start MyDCIName
Error: The OpenCCM DCI Manager MyDCIName is already started!
$

Let's note that the CosNaming Service must be started before, see the ns_start script, e.g.:

$ ns_stop
 . . .
$
$ dci_start MyDCIName
Error: The CosNaming Service is not started!
$

The dci_start script automatically launches an OpenCCM DCI Manager process and stores its standard output, IOR and PID into the OpenCCM Configuration Repository, e.g.:

$ ls $OpenCCM_CONFIG_DIR/DCIManagers
MyDCIName.IOR  MyDCIName.output  MyDCIName.PID
$

The started OpenCCM DCI Manager is bound into the CosNaming Service under the name OpenCCM/DCIManagers/MyDCIName.

See the dci_stop script to stop a started OpenCCM DCI Manager.

Setting the OpenCCM Distributed Computing Infrastructure Manager to use

In a distributed configuration, you could want to use an OpenCCM DCI Manager already started on another remote node instead of starting the OpenCCM DCI Manager on the local node. Then the dci_set script allows you to set locally the IOR or the URL to the remote OpenCCM DCI Manager to use, e.g.:

$ dci_set
usage: dci_set [IOR | URL]
$
$ dci_set IOR:...
The OpenCCM DCI Manager is set.
$
$ dci_set http://host.domain:port/file
The OpenCCM DCI Manager is set.
$

If the OpenCCM DCI Manager to use is started on a node where the OpenCCM Comanche Server is also started, then you could set the OpenCCM DCI Manager to use as following:

$ dci_set http://host.domain:8080/DCI.IOR
The OpenCCM DCI Manager is set.
$

Warning: The dci_set script does not control the correctness of the IOR or URL given as parameter, it just copies it into the local $OpenCCM_CONFIG_DIR/DCI.IOR file.

Checking if an OpenCCM DCI Manager is started

The dci_started script checks if an OpenCCM DCI Manager is started or not, e.g.:

$ dci_started
Error: None OpenCCM DCI Manager is not started!
$

Let's note that this OpenCCM script is mainly used by other OpenCCM scripts when they need to check if an OpenCCM DCI Manager is started or not.

Obtaining the IOR of the current OpenCCM Distributed Computing Infrastructure Manager

The dci_ior displays the IOR of the current running OpenCCM DCI Manager, e.g.:

$ dci_ior
file:$OpenCCM_CONFIG_DIR/DCIManagers/MyDCIName.IOR
$

Stopping an OpenCCM Distributed Computing Infrastructure Manager

The dci_stop script stops a previously started OpenCCM DCI Manager.

Its usage is the following:

$ dci_stop
usage: dci_stop [-h|--help] <dci_name>
$

To stop an OpenCCM DCI Manager, it is required to provide its name, e.g.:

$ dci_stop MyDCIName
The OpenCCM DCI Manager MyDCIName will be stopped.
The OpenCCM DCI Manager MyDCIName is stopped.
$

When providing an invalid name, an error obscurs, e.g.:

$ dci_stop MyDCIName
Error: The OpenCCM DCI Manager MyDCIName is not started!
$

Let's note that this script shutdowns the specified OpenCCM DCI Manager process and removes its associated files from the OpenCCM Configuration Repository.

$ ls $OpenCCM_CONFIG_DIR/DCIManagers
$

Starting an OpenCCM Node Manager

An OpenCCM Node Manager represents a logical node in an OpenCCM Distributed Computing Infrastructure. It provides functionalities to start and stop OpenCCM Component Servers, to install and manage CORBA component archives, to access meta information about the node. This manager implements the CORBA Components Deployment ServerActivator and ComponentInstallation interfaces.

The node_start script starts an OpenCCM Node Manager.

Its usage is the following:

$ node_start
usage: node_start [-h|--help] [-InpdFile] <node_name>
$

Each OpenCCM Node Manager must be started with an unique node name, e.g.:

$ node_start MyNodeName
The OpenCCM Node Manager MyNodeName will be started.
Creating the .../NodeManagers/MyNodeName.ComponentInstallation directory.
Launching the OpenCCM Node Manager MyNodeName.
No User Node Properties File define, use default properties.
The OpenCCM Node Manager MyNodeName is started.
$

Warning: Each started OpenCCM Node Manager must have a distinct node name, e.g.:

$ node_start MyNodeName
Error: The OpenCCM Node Manager MyNodeName is already started!
$

The optional argument -InpdFile allows you to provide meta information describing the node to start, e.g. operating system, processor, installed software, etc. For instance, this information will be used later by tools for automatic assigments of CORBA component assemblies. More information and tools will be provided in next OpenCCM releases.

Let's note that an OpenCCM DCI Manager must be started before, see the dci_start script, e.g.:

$ node_start MyNodeName
Error: None OpenCCM DCI Manager is not started!
$

Let's note that the CosNaming Service must be started before, see the ns_start script, e.g.:

$ ns_stop
 . . .
$
$ node_start MyDCIName
Error: The CosNaming Service is not started!
$

The node_start script automatically launches an OpenCCM Node Manager process and stores its standard output, IOR and PID into the OpenCCM Configuration Repository, e.g.:

$ ls $OpenCCM_CONFIG_DIR/NodeManagers
MyNodeName.ComponentInstallation/
MyNodeName.IOR
MyNodeName.npd
MyNodeName.output
MyNodeName.PID
$

The started OpenCCM Node Manager is bound into the CosNaming Service under the name OpenCCM/NodeManagers/MyNodeName.

See the node_stop script to stop a started OpenCCM Node Manager.

Stopping an OpenCCM Node Manager

The node_stop script stops a previously started OpenCCM Node Manager.

Its usage is the following:

$ node_stop
usage: node_stop [-h|--help] <node_name>
$

To stop an OpenCCM Node Manager, it is required to provide its node name, e.g.:

$ node_stop MyNodeName
The OpenCCM Node MyNodeName will be stopped.
The OpenCCM Node MyNodeName is stopped.
$

When providing an invalid node name, an error obscurs, e.g.:

$ node_stop MyNodeName
Error: The OpenCCM Node Manager MyNodeName is not started!
$

Let's note that this script shutdowns the specified OpenCCM Node Manager process and removes its associated files from the OpenCCM Configuration Repository.

$ ls $OpenCCM_CONFIG_DIR/NodeManagers
$

Starting an OpenCCM Assembly Factory Manager

An OpenCCM Assembly Factory Manager provides functionalities to create, build, tear down and manage CORBA component assemblies. This manager implements the CORBA Components Deployment AssemblyFactory and Assembly interfaces.

The factory_start script starts an OpenCCM Assembly Factory Manager.

Its usage is the following:

$ factory_start
usage: factory_start [-h|--help] <assembly_factory_name>
$

Each OpenCCM Assembly Factory Manager must be started with an unique assembly factory name, e.g.:

$ factory_start MyAssemblyFactoryName
The OpenCCM Assembly Factory Manager MyAssemblyFactoryName will be started.
Launching the OpenCCM Assembly Factory Manager MyAssemblyFactoryName.
The OpenCCM Assembly Factory Manager MyAssemblyFactoryName is started.
$

Warning: Each started OpenCCM Assembly Factory Manager must have a distinct assembly factory name, e.g.:

$ factory_start MyAssemblyFactoryName
Error: The OpenCCM Assembly Factory Manager MyAssemblyFactoryName is already started!
$

Let's note that an OpenCCM DCI Manager must be started before, see the dci_start script, e.g.:

$ factory_start MyAssemblyFactoryName
Error: None OpenCCM DCI Manager is not started!
$

Let's note that the CosNaming Service must be started before, see the ns_start script, e.g.:

$ ns_stop
 . . .
$
$ factory_start MyAssemblyFactoryName
Error: The CosNaming Service is not started!
$

The factory_start script automatically launches an OpenCCM Assembly Factory Manager process and stores its standard output, IOR and PID into the OpenCCM Configuration Repository, e.g.:

$ ls $OpenCCM_CONFIG_DIR/AssemblyFactoryManagers
MyAssemblyFactoryName.IOR
MyAssemblyFactoryName.output
MyAssemblyFactoryName.PID
$

The started OpenCCM Assembly Factory Manager is bound into the CosNaming Service under the name OpenCCM/AssemblyFactoryManagers/MyAssemblyFactoryName.

See the factory_stop script to stop a started OpenCCM Assembly Factory Manager.

Stopping an OpenCCM Assembly Factory Manager

The factory_stop script stops a previously started OpenCCM Assembly Factory Manager.

Its usage is the following:

$ factory_stop
usage: factory_stop [-h|--help] <assembly_factory_name>
$

To stop an OpenCCM Assembly Factory Manager, it is required to provide its assembly factory name, e.g.:

$ factory_stop MyAssemblyFactoryName
The OpenCCM Assembly Factory Manager MyAssemblyFactoryName will be stopped.
The OpenCCM Assembly Factory Manager MyAssemblyFactoryName is stopped.
$

When providing an invalid assembly factory name, an error obscurs, e.g.:

$ factory_stop MyAssemblyFactoryName
Error: The OpenCCM Assembly Factory Manager MyAssemblyFactoryName is not started!
$

Let's note that this script shutdowns the specified OpenCCM Assembly Factory Manager process and removes its associated files from the OpenCCM Configuration Repository.

$ ls $OpenCCM_CONFIG_DIR/AssemblyFactoryManagers
$