The following section illustrates the end-to-end process flow involved in deploying an application, and the actions that can be carried out after the application is deployed.

How to deploy an application

Follow the instructions below to deploy an application:

Step 1 - Install Private PaaS with a preferred IaaS or with Kubernetes
Step 2 - Configure the WSO2 Cartridge
Step 3 - (Optional) Add a Kubernetes Cluster
Step 4 - Add a network partition
Step 5 - Add a deployment policy
Step 6 - Add an auto-scaling policy
Step 7 - Add a cartridge
Step 8 - Add a cartridge group
Step 9 - Add an application policy
Step 10 - Add an application
Step 11 - Deploy the application

Step 1 - Deploy Private PaaS with a preferred IaaS or with Kubernetes

To learn how to deploy Private PaaS locally on Mock IaaS, click here.
To learn how to deploy Private PaaS on a VM or Kubernetes, click here.

Step 2 - Configure the WSO2 Cartridge

For more information, see Configuring WSO2 Products to Run on Private PaaS.

Step 3 - (Optional) Add a Kubernetes Cluster

This is only applicable if you are using Private PaaS with Kubernetes.

To get information on how to work with Kubernetes Clusters via the REST API, CLI and UI, see Kubernetes-CoreOS Clusters.
To learn more on the Kubernetes Cluster resource definition, see Kubernetes Cluster resource definition.

Step 4 - Add a network partition

To get information on how to work with network partitions via the REST API, CLI and UI, see Network Partitions.
To learn more on the network partition resource definition, see Network Partition Resource Definition.

Step 5 - Add a deployment policy

To get information on how to work with deployment policies via the REST API, CLI and UI, see Deployment Policies.
To learn more on the deployment policy resource definition, see Deployment Policy Resource Definition.

Step 6 - Add an auto-scaling policy

To get information on how to work with auto-scaling policies via the REST API, CLI and UI, see Auto-scaling Policies.
To learn more on the auto-scaling policy resource definition, see Auto-scaling Policy Resource Definition.

Step 7 - Add a cartridge

To get information on how to work with cartridges via the REST API, CLI and UI, see Cartridges.
To learn more on the cartridge resource definition, see Cartridge Resource Definition.

Step 8 - Add a cartridge group

To get information on how to work with cartridge groups via the REST API, CLI and UI, see Cartridge Groups.
To learn more on the cartridge group resource definition, see Cartridge Group Resource Definition.

Step 9 - Add an application policy

To get information on how to work with application policies via the REST API, CLI and UI, see Application Policies.
To learn more on the application policy resource definition, see Application Policy Resource Definition.

Step 10 - Add an application

To get information on how to work with applications via the REST API, CLI and UI, see Applications.

Step 11 - Deploy the application

To get information on how to deploy an application via the REST API, CLI and UI, see Applications.

After the composite application is deployed, all the clusters that belong to the composite application are brought up by PPaaS, based on the dependency information provided in the cartridge group definition and in the application definition.

What's next?

After deploying an application, you can carryout the following actions:

Step 1 - (Optional) Sign up to the application
Step 2 - (Optional) Add domain mappings to the application

Step 1 - (Optional) Sign up to the application

This is only applicable if the application is a multi-tenant application.

To get information on how to sign up to an application via the REST API and CLI, see Working with Application Sign Up.
To learn more on the application sign up resource definition, see Application Sign Up Resource Definition.

Step 2 - (Optional) Add domain mappings to the application

To get information on how to work with domain mappings via the REST API and CLI, see Working with Domain Mappings.
To learn more on the domain mapping resource definition, see Domain Mapping Resource Definition.

The following diagram illustrates the application deployment workflow:

Browser not supported