Deployments

A deployment is a build associated with the requisite environment.

With the Deployments section, you can:

  • Start, stop, or delete a deployment.
  • View logs of a certain deployment to make corrections on time.
  • Check deployment statuses to learn if they are starting, started, stopping, stopped, updating, deleting.
  • Start/stop/delete several profiles inside a deployment at once.
  • Set parameters to filter deployments based on their environment and build.
  • Search for and filter your deployments.
  • Enable Auto-Scaling for your deployments.
  • View detailed information (routes, services, configuration, CPU Utilization, and so on) on a selected deployment.
  1. On the Deployments page, click Deploy Build.
  2. In the Deploy Build dialog, from the drop-down list in the field Environment, select an environment or enter a name to search for an environment. Note that only the environments with the status Ready are displayed.
  3. From the drop-down list in Build, select a build for which you want to deploy your profile image. This associates the build to the environment. This is required because you can run the same build on several environments.

    In Profiles, the profile name is pulled in automatically based on the selected build.

  4. In Replicas, select the number of profile instances.
  5. In Memory Limit, select the memory size in megabytes or gigabytes to allocate the maximum amount of memory for the Compute service processes.
  6. Select the option Enable Auto-Scaling if you want the Compute service to scale your deployment up or down automatically based on the limits you specify. Auto-scaling helps you ensure that your deployments have adequate capacity to cater to the current traffic demand. It allows you to scale your deployments up or down by adding / removing profile instances when the deployment reaches the maximum / minimum limits of the memory or CPU usage that you have specified. For example, when your memory consumption reaches the specified maximum threshold, then a replica is added (but no more than the number of replicas specified in Max Replicas) to scale your deployment up. Or when your memory usage reaches the minimum threshold, then a replica is removed (but no fewer than the number of replicas you specified in Min Replicas) to scale your deployment down.
  7. Next to Operational Users, click . In User, from the drop-down list, select a user or enter the name of an operational user who is associated with this environment, has access to endpoints, and can send and receive data from/to this environment, and then click Assign.
  8. Next to Variables that are propagated to profiles, click to add a name-value pair.
    1. In the dialog that appears, in Variable Name, enter the name that describes the type of the variable, and then click Add.
    2. In the value field, enter a value for the variable type. To remove a variable, next to the value field, click and click Apply.
  9. Click Deploy.

In the list of deployments, you can view the following details on each profile:

  • The profile status,
  • The profile name,
  • The number of profile instances,
  • The path to the package archive of the profile located in the Cloud Repository,
  • The system performance estimated in percentages (CPU usage),
  • The random access memory (RAM) usage estimated in percentages,
  • The count of input and output requests of an HTTP-based inbound endpoint when RESTful components send HTTP requests to the endpoint (for the profiles that contain RESTful component).

To view more details on a particular profile in a deployment, expand the required profile from the list. The following tabs are available for a selected profile:

Field Description
HTTP Service

The automatically generated path to an HTTP service endpoint that you can use to submit your files through RESTful API (RESTful web service).

The path includes the route name and does not change when you deploy other build versions or redeploy the build within the same environment. If you deploy the build in another environment, a new path is generated.

Note The HTTP service is available for profiles that contain RESTful components.
Routes / Services

The list of routes and services that the profile contains.
#

The number of routes or services used in the profile.
Path

The path to the folder with routes or services.
Received/In Process/Processed/Exceptions/Failures

The number of data files with a specific status for each route.
Total

The total number of data files with a specific status from all the routes in a profile.

You can search for and filter the deployments and profiles.

To search for and filter profiles:

  1. On the Deployments page, from the drop-down list in Environment, select the environment where the profile that you want to retrieve resides.
  2. From the drop-down list in Build, select the build of the profile you want to retrieve.
  3. In Filter by profile status, select the current profile status.
  4. In Search, enter the name of a profile.

To start a profile:

  1. On the Deployments page, select the deployment you want to start.
  2. Click on the right and click Start.

To remove a deployment:

  1. On the Deployments page, in Environment, select the environment and in Build, select the build deployed in this environment.
  2. If the profiles of this deployment are running, click on the right of the profile.
  3. Click Stop and click OK to stop the profile.
  4. When the profiles have the status Stopped, click Delete Deployment on the top right of the page.
  5. Click OK to remove the deployment with all its profiles.