Sample Multi-tenant Service Cluster Definition

The configuration included in the appserver-service.json file is as follows:

 {
   "serviceName": "<SERVICE_NAME>",
   "cartridgeType": "<SERVICE_TYPE>",
   "deploymentPolicyName": "<DEPOYMENT_POLICY_NAME>",
   "autoscalingPolicyName": "<AUTOSCALING_POLICY_NAME>",
   "clusterDomain": "<CLUSTER_DOMAIN>",
   "clusterSubDomain": "<CLUSTER_SUBDOMAIN>",
   "tenantRange": "*"
 }

Parameter definitions

Parameter	Description	Required	Default value	Example Value
`serviceName`	The name given to the service cluster.	Yes	N/A	appserver
`cartridgeType`	The type specified in the multi-tenant cartridge definition.	Yes	N/A	AS
`deploymentPolicyName`	The deployment policy that will be used in the multi-tenant service cluster.	Yes	N/A	dep_policy
`autoscalingPolicyName`	The auto-scaling policy that will be used in the multi-tenant service cluster.	Yes	N/A	as_policy
`clusterDomain`	The name of the multi-tenant service cluster domain.	Yes	N/A	php.hills.com
`clusterSubDomain`	The name of the multi-tenant service cluster sub-domain. This will be used to differentiate between management and worker nodes in a cluster.	Yes	N/A	mgt.php.hills.com
`tenantRange`	The ID range of the tenant's allowed to subscribe to the multi-tenant cartridge. Currently Private PaaS allows any tenant to subscribe to any multi-tenant cartridge; therefore, the value for this field should always be as follows: `"*"`	Yes	N/A	`*`