Application deployment

When describing managing the installation and un-installation of a Grid application on a host or a host group, we use the terms deploy and undeploy. The Grid contains an application deployment mechanism which supports managing applications deployment on one or more hosts including the primary install (deploying to the first host), scaling-in, scaling-out, upgrading and un-installing. To be functional, a grid application must be deployed on at least one host, but an application can also be installed without being deployed.

  1. An application's deploy state indicates, per host or globally, the current deploy state of the application - that is, if the deploy was successful, is in progress or failed.
  2. A deploy is considered successful if the application files could be unzipped on disk on the target host and the deployment profile was executed successfully.
  3. Note that an application binding can only be started on a host where the application is considered to be OK. An application can have one of these deployed states:
    OK An application is deployed successfully.
    In progress A deploy is currently in progress.
    Failed A deploy has failed and must be handled.

The Deployment page shows which hosts the application is currently deployed on and the deploy state.

On the Deployment page, you can do these tasks:

  • Upgrade - Upgrade the application to another version.

  • Scale Out - Deploys the application to another host so it is possible to start the application on that host. Scale Out is only available if there are hosts the application yet has not been deployed to.

  • Scale In - Undeploys the application from a host.

    Note: This stops the application on that host if it is running. Scale in is only available if the application is deployed to more than one host.

  • Uninstall - Completely removes the application and its configuration from all hosts.

  • Edit host groups, if host groups are defined in the grid.