7.21 PuDeploymentOption Object
| Used on |
|
| Description | A deployment-option as its name suggest is used when deploying a GigaSpace application. The deployment-option contains the
settings needed to allow the application to be deployed in the user's preferred structure - cluster schema, number of partitions
and backups etc. The properties are intended to capture high level concepts rather than GigaSpace specific names so that the same
settings can be used for other grid/space implementations.
The pu-deployment-option is available on a processing unit; the deployment-option is available on the application.
The difference between the two is that only the deployment-option allows the specification of
- the target (type of deployment)
- the 'startUi' flag, and
- the target directories for machines.
In the GigaSpace implementation, the only schemas supported are 'primary_backup', 'partitioned' and 'partitioned-sync2backup'
The schema to use is derived from 'number-of-partitions' and 'number-of-backups'.
|
Inherited
properties |
| template |
(base property)
| |
| jwpattern |
(base property)
| |
|
7.21.1 Property 'description'
|
7.21.2 Property 'name'
|
| Description | This is the name of this deployment option.
It is possible to have multiple deployment options and the name is used to distinguish between them.
Generated deployment configurations are identified by the names of deployment options modelled at the application level.
However, this does not apply if the name is not specified or is empty (0-length); this deployment option is used to specfy defaults.
A named deployment option at the PU level does not automatically lead to a deployment option being generated;
there must be a deployment option of the same name at the application level for that to happen.
However, deployment options at the PU level define specific properties in the deployment configuration for that PU.
See the documentation for the details of the defaulting strategy, but in same the priority order for a specific configuration value is
(1) in a named PU-level deployment option
(2) in a unnamed PU-level deployment option
(3) in a named application-level deployment option
(4) in a named application-level deployment option.
|
| Type | String |
7.21.3 Property 'numberOfBackupClusterManagers'
|
| Description | This is the number of additional cluster managers (GigaSpace GSM).
One cluster manager will always be started, which should be for test purposes, hence the default of this property is 0.
For production deployment, you may want to specify one or more backups.
|
| Type | Integer |
7.21.4 Property 'numberOfBackups'
|
| Description | This is the number of backups that the each space will have. The default value is '0', which means there are no backups.
A value of Y where Y > 0 means there will be a Y backups per space in the cluster
For a GigaSpaces deployment this will value will be used in total-members setting e.g. total-members=X,Y.
|
| Type | String |
7.21.5 Property 'numberOfPartitions'
|
| Description | This is the number of partitions that will be used in this cluster. The default value is '1', which means there will be no
partitioning. Similarly a value of '0' means . A value of X where X > 1 means the cluster will be partitioned and there will be X
partitions. For a GigaSpaces deployment this will value will be used in total-members setting such that total-members=X,Y. In this
example where Y is the number of backups. See 'number-of-backups' for more information.
|
| Type | String |
7.21.6 Property 'text'
|
7.21.7 Property 'vmsPerMachine'
|
| Description | This is the number of processing units that can exist on a single machine.
Maps to -max-instances-per-machine on pudeploy.
When the location option is set to is EC2 ... ?
|
| Type | Integer |
|
