Home
Modeling Software Deployment
Modeling software deployment in HCL DevOps Deploy (Deploy) includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
Inventories
You use different inventories to track installed components and properties in HCL DevOps Deploy (Deploy) elements.
Environment inventory and compliance
The inventory for an environment lists the component versions that are intended to be deployed to that environment. Compliance shows whether the environment contains those component versions.

Modeling Software Deployment
Modeling software deployment in HCL DevOps Deploy (Deploy) includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
- Components
  Components represent deployable items along with user-defined processes that operate on them, usually by deploying them.
- Resources
  A resource is a logical deployment target that typically resolves to an agent and a user-defined construct that is based on the architectural model of HCL DevOps Deploy (Deploy).
- Applications
  Applications are responsible for bringing together all the components that must be deployed together.
- Application environments
  An environment is a user-defined collection of resources that hosts an application.
- Application templates
  With an application template, you can save and reuse a collection of resources, environments, processes, and tagged components or component templates to create a standardized application.
- Application processes
  Application processes, like component processes, are created with the process editor. You use application processes to deploy or to roll back components.
- Application blueprints
  An application blueprint maps application components to a resource template. When you create an environment or provision one from the cloud, you can use the blueprint as a model.
- Application pipelines
  Allows you to run application processes in multiple environments and promote versions through a set of stages.
- Snapshots
  A snapshot is a collection of specific versions of components and processes. Typically, a snapshot represents a set of component versions that are known to work together. In most cases, snapshots include all of the components in an application.
- Manual application tasks
  A manual application task interrupts an application process until manual intervention is done. To create a manual task, add a manual step to an application process and select a notification template.
- Approval process
  You can add approval requirements to deployments. Deployments with approvals cannot be completed until all approvers respond. Approvers can respond to requests on the Work Items tab, or by email.
- Inventories
  You use different inventories to track installed components and properties in HCL DevOps Deploy (Deploy) elements.
  - Environment inventory and compliance
    The inventory for an environment lists the component versions that are intended to be deployed to that environment. Compliance shows whether the environment contains those component versions.
    - Managing environment inventory and compliance
      You can allow the server to manage the environment inventory and compliance automatically, or you can manage the environment inventory and compliance with steps in an application process.
  - Viewing resource configuration inventories
    You can view the configuration inventory for a component, which includes all properties that are associated with the component resource.
- Processes
  Processes are automated tasks that run on agents.
- Statuses
  Create and apply statuses to track component inventory states or to track component versions in environments and resources.
- Properties
  Properties are variables that store information about many different elements, including components, environments, processes, and applications. You can also set global properties for the system.
- Tags
  A tag is a user-defined, shared, short label that you use to classify, view, and conduct operations on objects such as applications, components, agents, and resources.
- Webhooks
  Using the webhooks, you can send text-based responses to users in messaging platform such as MS Teams and Slack when a specific event occurs during deployment process.
- Secret Stores
  Allows you to retrieve credentials of individual servers from the Vault and authenticates a plug-in step in the deployment process.

Environment inventory and compliance

The inventory for an environment lists the component versions that are intended to be deployed to that environment. Compliance shows whether the environment contains those component versions.

The inventory and compliance for an environment are updated each time that you run an application process or deploy a snapshot to the environment. For example, assume that you run an application process that deploys two component versions to an environment. Regardless of whether the application process completes successfully, the environment inventory shows that the two component versions are deployed. The compliance shows how many of the components are installed successfully. In this way, the inventory shows the intended state of a resource or environment, while the compliance shows how closely the resource or environment matches the intended state. By reviewing the difference between the environment inventory and compliance, you can determine whether another deployment is necessary to bring an environment into compliance.

The environment compliance status appears green for compliant environment and red for non-compliant environment. Inventory count is displayed along with the compliance status in the format number of actual inventory/number of desired inventory. Here are a few examples of environment inventory and compliance statuses and what they mean:


Status	Description
Compliant: 5/5	The desired inventory is the same as the actual inventory.
Noncompliant: 2/5 (3 missing)	The desired inventory has more component versions than the actual inventory.
Noncompliant: 5/5	The desired inventory has the same amount of component versions as the actual inventory, but some versions in the list don't match.
Noncompliant: 7/5	The desired inventory has less component versions than the actual inventory.

The environment inventory and compliance track components but not snapshots or applications. For example, if you successfully deploy a snapshot with two component versions, the inventory is two components and the compliance is two components. If you successfully deploy a different snapshot with versions of two different components, the inventory is four components and the compliance is four components. In this way, the server counts component versions for inventory and compliance, not the versions in a snapshot or applications.