Features
- Former user (Deleted)
- Former user (Deleted)
- Former user (Deleted)
WSO2 Private PaaS includes polyglot language and environment support together with the ability to run on top of multiple IaaS runtimes. The following are the key features available in WSO2 Private PaaS 4.1.0:
| Feature | Description |
|---|---|
WSO2 Products as a Service | This supports cartridge creation for WSO2 Carbon products on a Virtual Machine (VM) or Docker. Cartridges are available for the following WSO2 products in the PPaaS cartridges GitHub repository:
|
Composite Application Model | This allows applications, which requires different service runtimes with their relationship and dependencies, to be deployed. Furthermore, each of the service runtimes in the application can scale independently or jointly with the dependent services. The following operations are supported in composite application support:
For detailed information on how composite applications work in PPaaS, see Composite Applications. |
Docker Support | Docker support using Google Kubernetes and CoreOS. Thereby, WSO2 Private PaaS can also leverage the use of Docker in a PaaS. The following aspects are supported for Docker:
|
Cartridge Agent | A Python based and Java based cartridge agent is available in WSO2 Private PaaS. |
Automated Artifact Distribution | |
Multi-Factored Auto-scaling | The Auto-scaler uses a Complex Event Processor (CEP) for real-time decision making, and it integrates both real-time and rule-base decision making to provide better control over scaling of platforms. WSO2 Private PaaS allows users to define auto-scaling policies with multiple factors,i.e., requests in flight, memory consumption and load average, which are considered when scaling up or down. The Auto-scaler also supports scaling for non-HTTP transport. |
Smart Policies for Auto-scaling & Deployment | The Auto-scaler in WSO2 Private PaaS uses two smart policies when making auto-scaling decisions: auto-scaling policy and deployment policy. The instances will be automatically spawned based on the smart policies that are applied to the application. |
Multiple IaaS support | WSO2 Private PaaS supports AWS EC2, OpenStack, Google Compute Engine (GCE) & Kubernetes. WSO2 is currently working on extending its support to Microsoft Azure with Apache jclouds. |
Multi-cloud bursting | WSO2 Private PaaS supports multiple IaaSs. When the maximum limit of instances has been reached in an IaaS, instances are spawned on another IaaS, which is in another network partition. Thereby, this will enable resource peak times to be off-loaded to another cloud. |
Multi-cloud and multi-region deployment | It is possible for DevOps to define partitions in a network partition, to control IaaS resources. Thereby, WSO2 Private PaaS can control resources per cloud, region, and zone. Controlling of IaaS resources provide a high availability and solves disaster recovery concerns. For more information, see Cloud Partitioning. |
Multi-tenancy | WSO2 Private PaaS supports in-container multi-tenancy. Thereby, this helps to optimize the resource utilization. |
Pluggable architecture support for cartridges | A cartridge is a package of code that includes a Virtual Machine (VM) image plus additional configuration, which can be plugged into WSO2 Private PaaS to offer a new PaaS service. Private PaaS supports single tenant and multi-tenant cartridges. If needed, tenants can easily add their own cartridges to WSO2 Private PaaS. For more information on how Stratos uses cartridges, see Cartridge. |
Cartridge automation using Puppet | Cartridges can be easily configured with the use of an orchestration layer such as Puppet. |
Support for third party load balancers | Private PaaS supports third-party load balancers (LBs), i.e, HAProxy, NGINX, LVS, AWS and GCE. Thereby, if required, users can use their own LB with Private PaaS. |
Artifact distribution coordination | The Artifact Distribution Coordinator is responsible for the distribution of artifacts. Artifacts can be uploaded using git push. When a trigger event happens the ADC will find the correct matching cluster for that event from the topology and send notifications to appropriate Cartridge instances. ADC supports external Git repositories and GitHub repositories based deployment synchronization. Users are able to use their own Git repository to sync artifacts with a service instance. For more information, see Artifact Distribution Coordinator. |
WSO2 Private PaaS Console | Administrators and tenants can use the Private PaaS Console, which is a web-based UI management console, to interact with WSO2 Private PaaS. For more information, see Private PaaS Dashboard. |
WSO2 Private PaaS REST API | DevOps can use REST APIs to carry out various administering functions (e.g., adding a tenant, adding a cartridge, etc.). For more information, see API Reference Guide. |
Interactive CLI Tool | Command Line Interface (CLI) tool provides users an interface to interact with WSO2 Private PaaS and manage your applications. For more information, see CLI Guide. |
Monitoring and metering | WSO2 Private PaaS provides centralized monitoring and metering. The level of resource utilization in Private PaaS is measured using metering. |
Persistent volume support for cartridges | If required, the DevOps can enable a persistent volume for cartridges. If persistent volume is enabled, WSO2 Private PaaS automatically attaches a volume when a new cartridge instance is created. For more information, see Persistence Volume Mapping. |
WSO2 Private PaaS Mock laaS | WSO2 Private PaaS mock IaaS simulates the basic features that Private PaaS requires from an IaaS. Thereby, this provides a cost effective way of trying out WSO2 Private PaaS. |