Hyperscale Orchestrator UI

Overview

The Hyperscale UI is Controlled Availability, meaning that Delphix highly encourages interested customers to reach out to Delphix Product and Engineering for a guided onboarding. Please contact your account team if interested. 

To disambiguate object nuances between Compliance Engines, Hyperscale Orchestrators, and DCT, please refer to the following definitions:

  • Hyperscale dataset

    • A Hyperscale dataset is a granular unit that defines source and target connector information alongside a defined database schema to be masked (the inventory on a Compliance Engine).

  • Hyperscale job

    • A Hyperscale-specific object that is comprised of a rule set along with additional running parameters such as engines to be used and memory settings.

  • Hyperscale job execution

    • The execution information such as duration, rows masked, etc. that is sent back to DCT for reporting.

Data Control Tower has the ability to connect to one or more Hyperscale Compliance Orchestrators, to serve as a complimentary user interface. The current Compliance Engine/Hyperscale Orchestrator/DCT workflow is as follows:

  1. Build the foundational objects (rule sets, connectors, inventories, etc.) within the Compliance Engine. 

  2. Build a data set on the Hyperscale cluster by either:

    1. Importing a compliance job from a Compliance Engine.

    2. Building the dataset via the connector, dataset, and jobs API on the Hyperscale cluster (DCT will read the new Hyperscale jobs and display them.)

  3. Set up the DCT-to-Hyperscale connection by following simple steps in the Connecting/authenticating page. DCT will then create references for any data sets (registered as Hyperscale jobs in DCT), cluster details (e.g. mount points, etc.), and pre-existing engine connections to the Hyperscale Orchestrator.

  4. Create a Hyperscale job on DCT by selecting an existing masking job and importing the job’s inventory and connector information into DCT to represent a hyperscale job. Users have the option to further refine the job details such as defining table-specific masking parameters. A job will appear as a special Hyperscale job on the compliance jobs page. 

  5. Execute a Hyperscale job by selecting the run option on the Hyperscale jobs detailed view.

  6. DCT will recognize this job execution and will present the execution details under the specific Hyperscale Orchestrator’s Details page. 

Related pages