Automating the deployment process is commonly used practice
in a production or development environments. There are many tools exist to perform this task. Puppet is our recommended tool to perform deployment automation. You can find necessary puppet modules which are relevant to WSO2 CEP 4.0.0 here. You can refer/use these puppet modules when developing your own puppet modules for WSO2 CEP. Please find further details on this below.
WSO2 CEP Puppet Modules
These puppet modules can be used to install WSO2 CEP in all its deployment modes(i.e. standalone mode, high availability mode and distributed mode). Also, it contains modules necessary to install an apache storm cluster which is required for the distributed deployment of CEP. It also has enabled deployment of 3 main deployment patterns of wso2 CEP easily using Hiera to store deployment parameters.
...
cep : Installs and manages the CEP in standalone mode
cep:hanode : Install and configure the CEP as a worker in high availability(HA) mode.
- cep:distributednode : Install and configure the CEP as a worker or manager in distributed mode.
Parameters
Parameter | Description |
version | Version of the WSO2 CEP server. These scripts can be only used for version 4.0.0 onwards. (e.g. 4.0.0) |
owner | Owner of the CEP installation folder(e.g. root) |
group | Group of the CEP installation folder(e.g. root) |
maintenance_mode | Mode of the installation, following are the allowed values, refresh : stop the server if running and restart new : delete the existing installation and redeploy and start the server zero : download a fresh copy of the wso2 CEP pack and perform a fresh deployment |
offset | Portoff set of the carbon server |
clustering | Flag to indicate if clustering is enabled or not. (e.g. true) |
depsync | Flag to indicate if deployment synchronization is enabled or not (e.g. false) |
local_member_port | The local member port to be use to be used in hazelcast cluster |
members | Members of the hazelcast cluster, should specify the hostname of each member with the local member port of each host |
membership_scheme | Hazelcast cluster membership schema |
ha_eventsynch_port | Port used for syncing events among two nodes in HA mode of CEP |
ha_mgt_port | Port on which the HA management service run in HA mode of CEP |
manager_port | Port on which the management service run in distributed mode of CEP |
managers | CEP instances acting as managers in distributed mode of CEP. Hostname and the manager service port of each manager |
worker | Flag to indicate if the instance is acting as a worker in HA or distributed mode of CEP |
manager | Flag to indicate if the instance is acting as a manager in distributed mode of CEP |
presenter | Flag to indicate if the instance is acting as a presenter in HA or distributed mode of CEP |
presenter_port | Port which presenter instances use to receive events |
registry_db_connection_url | Connection URL of registry database (e.g. jdbc:mysql://192.168.57.170:3306/regdb?autoReconnect=true) |
registry_db_user | Username to be used to connect to registry database |
registry_db_password | Password to login to registry database |
registry_db_driver_name | Driver class name to be used to connect to registry database (e.g com.mysql.jdbc.Driver) |
userstore_db_connection_url | Connection URL of userstore database |
userstore_db_user | Username to be used to connect to user store database |
userstore_db_password | Password to login to user store database |
userstore_db_driver_name | Driver class name to be used to connect to user store database |
...