Unknown macro: {next_previous_link3}
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

WSO2 Private PaaS uses two smart policies: Auto-scaling policy and Deployment policy. Auto-scaling parameters, which are defined via the auto-scaling policy related parameters and the deployment policy related parameters, are used to calibrate the elasticity of the system. The auto-scaling policies and deployment policies need to be defined and deployed before users subscribe to a cartridge. In single tenant cartridges the auto-scaling policy and deployment policy that needs to be used for the subscription needs to be selected at the time of subscription. However, in multi-tenant cartridges the auto-scaling policy and deployment policy to be used needs to be defined when deploying the multi-tenant service cluster. 

The auto-scaling and deployment policies can be used to derive a cloud SLA from the platform as a service (PaaS) layer, which in turn will benefit the software as a service (SaaS) layer applications. For example, if you want to derive five-9’s availability (99.999%) , then you have to maintain a minimum instances count and run on different cloud vendors, different regions, different zones etc. The latter requirement can be fulfilled if defined in the deployment policies. 

The following sub-sections describe how to work with smart policies via the CLI, UI and REST API:

  • No labels