This glossary provides terms and definitions for theHCL™ Launch software and products.
The following cross-references are used in this glossary:
- See refers you from a nonpreferred term to the preferred term or from an abbreviation to the spelled-out form.
- See also refers you to a related or contrasting term.
For other terms and definitions, see the HCL® Terminology website (opens in new window).
A program that runs on a remote computer and communicates with the HCL UrbanCode Deploy server. Agents run processes on deployment target systems.
A communication proxy for agents that are located behind a firewall or in another network location.
One or more computer programs or software components that provide a function in direct support of a specific business process or processes.
A user-defined collection of resources that hosts an application. These application environments refer to environments that are created to be environments in HCL UrbanCode™ Deploy.
A process that is associated with an application. Unlike a component or generic process, an application process is created from application-level steps. Typically, an application process invokes component processes, and orchestrates multi-component deployments. See also component process, generic process, process.
A deployable item such as a file, image, database, configuration material, or anything else that is associated with a software project. By default, artifacts are stored in CodeStation repository.
An authentication realm manages users and determines user identity. It retrieves information from sources such as LDAP servers and Keystone identity services.
A setting that prevents deployments and snapshots from being scheduled. Blackouts solely affect the environment and application that they are applied to.
A Heat Orchestration Template (HOT) that specifies information about an automatic deployment of cloud resources to a virtual environment. Blueprints contain three sections: parameters, resources, and outputs.
blueprint design server
A server that hosts the blueprint designer and controls access to blueprints. It also hosts the cloud discovery service, which provides information about the available cloud resources to the blueprint designer. (In previous versions, this system was the HCL™ Launch with Patterns design server.)
The graphical user interface that models blueprints, which specify information about the automatic deployment of deployment of cloud resources to a virtual environment. Blueprints contain three sections: parameters, resources, and outputs.
cloud discovery service
The component that provides information about available cloud resources, such as images and security groups, to the blueprint designer. (In previous versions, this service was a component of HCL™ Launch with Patterns.)
A functional ID with access to a cloud system. By accessing this cloud project, users can work with this functional ID to request cloud services that might not be available to their personal ID.
The artifact repository for HCL UrbanCode Deploy. CodeStation tracks artifact versions as they change and maintains an archive for each artifact.
A representation of deployable items and the user-defined processes that operate on them, usually by deploying them.
A process that retrieves the output of a build, packages the output with configuration properties, and installs the package in a pre-defined location so that it can be tested or run.
A customized OpenStack Heat orchestration engine that interprets blueprints. Engines use blueprints as patterns for virtual environments.
A user-defined collection of resources that hosts an application.
A list of all of the component versions that are deployed to an environment. See also component inventory.
A template for managing dependencies, artifacts, and deployments associated with every build of a given project. Lifecycle models can be reused for separate projects.
A means of preventing uncommitted changes made by one application process from being perceived by another application process and for preventing one application process from updating data that is being accessed by another process. A lock ensures the integrity of data by preventing concurrent users from accessing inconsistent data.
A variable that specifies a value that is provided during process deployment and is associated with a specific UrbanCode Deploy object. An individual property's value can be accessed only by certain types of related objects, such as environments, processes, and components.
A proxy that can be used to access agents behind a firewall. Relay servers enable network-to-network communication.
A user-defined construct that is based on the architectural model of HCL UrbanCode Deploy. A resource represents a deployment target.
A list of all of the components that are deployed to an agent resource. See also component inventory.
A job function that identifies the tasks that a user can perform and the resources to which a user has access. A user can be assigned one or more roles.
A collection of specific versions of components. Typically, a snapshot represents a set of component versions that are known to work together.
A categorization that associates users with roles. When you assign a user to a team, you also assign that user to a role because roles are assigned to teams.
A representation of an account on the server. Users can be members of groups. Rather than having its own list of users, the server imports accounts from authentication realms, including OpenStack Keystone services and LDAP servers.
A stand-alone virtual environment, including operating system and binary files, that is used to define a virtual system.
A software implementation of a machine that executes programs like a real machine.