DevOps Loop licensing information
You can find the details of licensing that HCL DevOps Loop supports.
- Essentials (Tier 1): Plan, Control and Code
- Standard (Tier 2): Plan, Control, Code, Test, and Deploy
- Premium (Tier 3): Plan, Control, Code, Test, Deploy, Measure, and Release
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
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.
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.