6.1 Deployment Option Modelling
6.1.1 Concepts
|
An application's deployment can be modelled at the same time as the application is modelled.
Deployment Options
can be added at the application level - i.e. as a child node of the application node in the model;
Pu Deployment Options can be added at the processing unit level.
Both types of deployment options can be named, or left unnamed - with a missing or blank name.
Named deployment options are for deployment;
unnamed options are considered to be the default for that (application or PU) level.
Deployment Options and Pu Deployment Options with the same name define different aspects of that named deployment.
For each item of information in the final requested deployments,
GigaSystemBuilder uses a search approach so that sensible defaults can be set for a deployment.
For example, you might want to not specify the number of partitions and backups for most of the PUs
and pick that up from a default, but also have the ability to override this for a given PU.
GigaSystemBuilder implements the following search order to allow to allow you to do this
(using 'cloudDepl' as the deployment name):
- First it searches for a value in the Pu Deployment Option named 'cloudDepl', if one exists
- Then it looks for the value in the unnamed Pu Deployment Option, if one exists
- Next it looks in the named Deployment Option named 'cloudDepl' (at the application level), if one exists
- The unnamed Deployment Option (at the application level)
- Finally, if the above does not find a value, a built-in default.
Each named Deployment Option can specify a target - these are
- CommandLine - a windows command line environment - this is the default
- AmazonEC2 - for deploying to the Amazon EC2 cloud. This is used in conjunction with GigaSpaces Cloud Tools.
- Unix - a unix deployment environment. This is, at present, untested
There is no need to model deployment to the Eclipse environment because it is always generated.
(It is given a name of 'Eclipse', so you can't use this to model other environments.)
See the Eclipse Deployment section for more details.
6.1.2 How To
|
To model a Deployment Option select the application and add a new child Deployment Option:
Set the required options. In this case the name is set to 'deployment1'.
The number of partitions is 2 and the number of backups is 1.
If you want to amend the target then select the appropriate option from the 'Target' property.
This will create a command line deployment called 'deployment1'. All processing units will have 2 partitions and 1 backup.
If you want to override this deployment scenario for the CongestionZoneProcessor Processing Unit create a Pu Deployment Option
Set the name to be 'deployment1'. As this has the same name as the Deployment Option it will override the options defined in the Deployment Option.
So the CongestionZoneProcessor will have 4 partitions with 2 backups.
| 
