Configure DZS Cloud Orchestration for Geographic Redundancy

In order to set up Geographic Redundancy, you must configure openidc-provider-configure and set up a system name for each Launchpad.

Configure openidc-provider-config for Geographic Redundancy on both Launchpads

Note: openidc configuration must be done for both Launchpads.

  1. On the Launchpad Dashboard menu, click ADMINISTRATION > CONFIGURATION.

  2. On the CONFIGURATION page, click openidc-provider-config.

  3. In the OPENIDC-PROVIDER-CONFIG section, click openidc-client.

  4. In the OPENIDC-CLIENT section, click the + icon. A *Client Type screen appears.

  5. Choose the jwt-client type and click Continue. An edit box appears.

  6. Fill in the following fields:

    • *Client ID - The Client ID must match the HA Client ID listed on the REDUNDANCY > STATUS > ACTIVE INSTANCE page.

    • Client Name- Launchpad name

    • Token Expiry Timeout- Time period after which a generated Access Token expires in seconds. This is Client specific token expiry timeout. The global token-expiry-timeout is used if this value is not specified.

    • Refresh Token Expiry Timeout- Client specific refresh token expiry timeout in seconds. It is not applicable for all client types. The global token-expiry-timeout is used if this value is not specified.

    • *User Name- The User Name must be rift@rift.

    • *User Domain- The User Domain must be rift.

    • Public Key- The Public key must match the SSL PUB KEY listed on the REDUNDANCY > STATUS > ACTIVE INSTANCE page.

      Note: Include the text -----BEGIN PUBLIC KEY----- and -----END PUBLIC KEY-----.

      Launchpad1

      Launchpad2

  7. Carefully check your entries and click SAVE.

    Note: This configuration needs to be done on the local and remote Launchpads.

Set up a System Name for each Launchpad

In previous releases, the operator could modify the system ID. In this release, the system ID is now used for licensing so if you modify the system ID the license will now become invalid.

  1. On the CONFIGURATION page, click system. A System screen appears.

  2. Fill in the following fields:

    • System Name - DZS Cloud Orchestration system name. This name should be unique for each Launchpad.

    • Location- Location of the DZS Cloud Orchestration system. This is an option field.

    • Contact- Contact Information for the DZS Cloud Orchestration administrator. This is an optional field.

  3. Carefully check your entries and click SAVE.

    Note: Set up a System Name for each Launchpad.

After you Set up a System Name for each Launchpad, the System Name and Location appear on the Launchpad login screen.

See High Availability with Geographic Redundancy in the Installation and Deployment Guide.