DevOps Loop licensing information
You can find information about the licensing options and additional product licensing requirements supported by HCL DevOps Loop.
- Essentials (Tier 1): Plan, Control and Code
- Standard (Tier 2): Plan, Control, Code, Build, Test*, Deploy* and Harbor (if enabled).
- Premium (Tier 3): Plan, Control, Code, Test*, Build, Deploy*, Measure, Release and Harbor (if enabled).
*Test and Deploy capabilities include features that require additional licenses. See DevOps Loop and additional product licensing for more information.
Licenses are consumed when the admin assigns them, and only released when the admin explicitly revokes them or DevOps Loop is uninstalled. License tier re-assignments may take up to 15 minutes to reflect.
By default, non-admin users must be assigned a tier before logging in, while admin users automatically receive the highest available tier. This per-user tier assignment allows different access levels to be enforced for different users, providing flexibility in license management.
Configuration
License allocation
You must run the following command to retrieve information on the licensing allocation:
curl --cacert /path/to/your/certificate.crt https://FQDNhostname:LLSport/v1/licensepools/poolID
{
"id": "MyPoolID",
"features": {
"DevOpsAutomationEssentials": {
"total": 100,
"leased": 0,
"available": 100,
"name": "DevOps Automation Essentials User"
}
}
}
- DevOpsAutomationEssentials
- DevOpsAutomationStandard
- DevOpsAutomationPremium
DevOps Loop and additional product licensing
Most DevOps Loop capabilities are covered by the Loop user license associated with the user's assigned tier. The following table summarizes the licensing included with each capability and identifies additional licenses where applicable.
| Capability | Loop tier | Additional license required |
|---|---|---|
| Plan | All Loop tiers | No additional license required. |
| Control | All Loop tiers | No additional license required. |
| Code | All Loop tiers | No additional license required. |
| Build | Standard or above | No additional license required. |
| Deploy | Standard or above | A separate Deploy Agent license is required to run deployments. |
| Test | Standard or above | Concurrent Virtual Services are required for API and integration tests. Virtual Users are required for performance tests that require high user loads. |
| Measure (Velocity) | Premium | No additional user-tier license is required. |
| Release | Premium | No additional license required. |
For more information about Test licensing, see the applicable Test licensing documentation.
Deploy Agent licenses are separate from Loop user licenses and are acquired independently based on the requirements of the environment.
- Loop user license: Provides users with access to the DevOps Loop capabilities included in their assigned tier.
- Deploy Agent license: Allows an agent to run deployments in DevOps Deploy.
To run deployments on Deploy, work with your Account Manager to acquire the required number of Deploy Agent licenses for your environment.
For more information, see License types.
For more information about DevOps licensing options, see HCL DevOps. Under Flexible Solutions for Seamless DevOps Loop, the available add-ons include:
-
Concurrent Virtual services
-
Performance Testing Virtual users
-
Deployment agents
Usage
After the Admin user creates a user, when the user logs in to DevOps Loop, then one license of the highest available tier is consumed. The user can access the products that are included in the licensing tier that is purchased.
For Deploy, the Loop user license provides access to the Deploy capabilities included in the user's tier. A separate Deploy Agent license is required when an agent runs an actual deployment.
DevOps Loop provides a user interface to view and manage licensing. You can revoke or assign a user's license through the User Administration page. See License management and user administration and Revoking a license.
Troubleshooting
kubectl logs <licensing_pod_name> -n <namespace>
Where, the namespace is defined by the Helm installation. You can find
the licensing_pod_name by running the following command:
kubectl get pods -n <namespace>
The pod name that contains 'licensing' in the name is listed.