Virtual Machine Based Masking Engines¶
This section will detail the hardware/software requirements needed to deploy the Delphix Engine with the Masking service. The Delphix Engine is a self-contained operating environment and application that is provided as a Virtual Appliance. Our Virtual Appliance is certified to run on a variety of platforms including VMware, AWS, and Azure.
The Delphix Engine should be placed on a server where it will not contend with other VMs for network, storage or other compute resources. The Delphix Engine is a CPU and I/O intensive application, and deploying it in an environment where it must share resources with other virtual machines can significantly reduce performance.
To use both Continuous Data and Continuous Compliance note, they must be deployed separately. One Delphix engine is required for each per each service, running both masking and virtualization operations on one engine is not supported.
Client Web Browser¶
The Delphix Engine's graphical interface can be accessed from a variety of different web browsers. The Delphix Engine currently supports the following web browsers:
- Microsoft Edge 40.x or higher
- Mozilla Firefox 35.0 or higher
- Chrome 40 or higher
AWS EC2 Platform¶
See AWS EC2 Installation for information about the virtual machine requirements for installation of a dedicated Delphix Masking Engine on Amazon's Elastic Cloud Compute (EC2) platform.
See Azure Installation for information about the virtual machine requirements for the installation of a dedicated Delphix Masking Engine on the Azure platform.
Google Cloud Platform¶
See Google Cloud Platform Installation for information about the virtual machine requirements for the installation of a dedicated Delphix Masking Engine on the GCP platform.
See IBM Cloud Installation for information about the virtual machine requirements for the installation of a dedicated Delphix Masking Engine on the IBM Cloud.
See VMware Installation for information about the virtual machine requirements for the installation of a dedicated Delphix Masking Engine on the VMware Virtual platform.
Container (Kubernetes) Based Masking Engine¶
For Containerized Masking, the product is delivered as a set of containers which is deployed as a Pod in the customer's Kubernetes infrastructure. This Pod provides a very similar set of functionality as the Delphix Engine VM based appliance.
Containerized Masking was developed to provide the ability to create ephemeral engines. I.e. small engines that can be spun up quickly for a specific need and then thrown away once that need is fulfilled.
The customer will need to provide said kubernetes infrastructure whether on-prem infrastructure (such as MiniKube or MicroK8s) or cloud based infrastructure. (such as AWS EKS)
Additionally, some functionality may require additional software be installed on the kebrnetes node systems. For example, if use of NFS mounted filesystems is planned, each node would need the NFS client software to allow kubernetes to perform the desired NFS mounts.
Differences from VMware based engines¶
The VMware based Continuous Compliance engine was deployed conjoined with the Continuous Data product, including its Engine Setup App. The containerized version of Continuous Compliance is fully divorced from the Continuous Data product which means that some functionality that was provided or enabled by the Engine Setup App is not available. Some unavailable items are on the roadmap to be re-introduced to Containerized Continuous Compliance in future releases.
The ways in which the containerized service differs from its VMware based compatriot are summarized in the following table.
|Functionality||VMware based engine||Containerized engine|
|FTP support for file masking||Yes||No (1)|
|SSL / TLS for connectors||Yes (2)||Yes (4)|
|Local file masking via NFS||Yes (2)||Yes (4)|
|Local file masking via CIFS||Yes (2)||Yes (4)|
|LDAP||Yes (2)||No (1)|
|Kerberos||Yes (2)||No (1)|
|SSO / OAuth||Yes (2)||No (3)|
|Upgrade / upgrade validation||Yes (2)||No|
|IBM's Custom DB2 Driver||Yes||No|
(1) Roadmap Item, Not currently Supported
(2) via the Engine Setup App
(3) Currently under evaluation
(4) via Kubernetes
More information about each of the above can be found in the doc sections that deal with their subject.