License Management

DZS Cloud Orchestration includes a method for configuring and managing licensing. If your Launchpad is not registered, then a warning banner will be displayed at the top of the display. Users obtain the license from DZS support, then enter the license using the Launchpad Dashboard. For license information, see Services & Support or contact [email protected].

Note: Configurations using the Geographic Redundancy feature require a separate license. License configuration for GR is similar to the license configuration for Launchpad without GR, but two licenses are needed; each Launchpad site is considered a separate instance of Launchpad, to be licensed separately.

Prerequisite: Locate Host Key

The Host Key is required. You provide the Host Key to DZS when you request a license. To identify the Host Key:

  2. Send the Host Key to DZS so that a license can be provided to you.

Adding the License

Use the Launchpad Dashboard to enter the license that was provided to you by DZS.

Note: An operator must have the platform-admin role (rw-rbac-platform:platform-admin) to configure a DZS Cloud Orchestration license.

  1. On the Launchpad Dashboard, click Administration.

  2. Scroll down to Configuration

  3. Select license-config.

  4. Under License-Config, click license.

  5. Click the plus icon to add a license.

  6. Copy and paste the license you obtained from DZS into the box.

  7. Click Add.

    If a valid license was entered correctly, the product will be licensed. Verify the licensing status on the home page in the DZS Cloud Orchestration Licensing widget.

If you encounter an error when attempting to add a license, that error condition will be identified under State in the DZS Cloud OrchestrationLicensing widget and in the Events > License section of the UI. Contact DZS if you require assistance. See DZS Cloud Orchestration Licensing Widget.

DZS Cloud Orchestration Licensing Widget

The DZS Cloud Orchestration Licensing widget on the Home page of the UI allows customers and DZS support to easily access licensing information. This widget includes the following data:

  • Recorded values collected periodically: A dynamic chart displays this data. You can scroll to expand or reduce the timeframe.

  • Compliance: The compliance status of the license (unlicensed or in-compliance).

  • Host key: Customer provides a host key to DZS when requesting a license. The host key uniquely identifies an instance.

  • Current VM/Pod Count: The current number of VMs and Pods under management.

  • licenses: The UI displays the features associated with each license and any limits imposed on that license.

    • Expiry: The date when the license expires.

    • State: The state of the license (licensed or compliant).

    • Features: The features supported with each license.

    • Serial Number: The serial number for the license.

    • License: The license key

Note: If your license includes a capacity limit, then it will appear on the License card.

If a valid license is entered correctly, then the product will be licensed. Verify the licensing status on the Launchpad PLATFORM Dashboard menu, click CONFIG > License card and the ALERTS > License card.

CONFIG > License card

ALERTS > License card

Users can monitor license capacities (such as host, server and VMs/Pods) by setting a threshold limit as a percentage. Once the percentage is set, DZS Cloud Orchestration notifies an operator if a threshold limit is reached. Click on the top right corner of the DZS Cloud Orchestration Licensing widget to configure the Licensing thresholds and provide the Set Alert details in the pop-up screen.

Note: An operator must have the platform-admin or platform-oper role (rw-rbac-platform:platform-admin or rw-bac-platform:platform-oper) to configure licensing thresholds.

  • Observe For: The hysteresis period in minutes over which the alert condition is monitored before triggering an alarm.

  • Threshold: The percentage of licenses beyond which an alert should be fired according to the specific metrics specified by the license.

  • Remove alert: This alert allows a user to remove an existing license usage alert (False or True).

Check your entries and click SAVE.

Adding the License for Geographic Redundancy Configurations

To configure Licenses along with Geographic Redundancy (GR):

  1. Configure licensing for Launchpadfirst. Do not configure GR first.

  2. Configure licenses on both sites following the instructions in Adding the License.