Installing and configuring Lumada DataOps Suite
To install the Lumada DataOps Suite (LDOS), ensure that your Hitachi Vantara Customer Success representative has arranged for the inclusion of all the system requirements and prerequisites on your system. See Install for system requirement and prerequisite details.
After you have your requirements and prerequisites in place, perform the following tasks to install and configure LDOS:
- Configure the properties file
- Run the install script
- Configuring DNS entries
- Adding licenses
- Test the installation
Configure the properties file
Perform the following steps to configure LDOS environment settings for your cluster:
Procedure
Navigate to the installer directory in your LDOS package, which was unpacked when the LDOS solutions were uploaded.
Open the env.properties file with any text editor.
All these properties are case-sensitive.NoteThe env.properties file also includes other properties that control the installation. For example, you can partially install LDOS by changing theinstall_mode
between LDOS, Lumada Data Integration (LDI), and Lumada Data Catalog (LDC). For more advanced settings, see the README.md file included in the installer directory of the LDOS package.Specify the following cluster properties:
Cluster property Description Example hostname
Where the instance of the Kubernetes container is running. dogfood.trylumada.com
registry
Where the Docker images are stored. registry.dogfood.trylumada.com
namespace
Name of the cluster namespace if it is different than the default value. hitachi-solutions
realm
Realm used by Keycloak if it is different than the default value. default
Perform the following steps to obtain the credentials for the Kubernetes container:
Note Contact your Hitachi Vantara Customer Success representative if you need further information about the container.Either retrieve the value for the
For example, if you are using the default client name offoundry_client_secret
credentials from Keycloak or use the echo command from the command line on the container’s client name.solution-control-plane-sso-client
, you would run the following code from the command line:# get client secret for solution-control-plane-sso-client
echo $(kubectl get secrets/keycloak-client-secret-solution-control-plane-sso-client -n hitachi-solutions --template={{.data.CLIENT_SECRET}} | base64 -- decode)
Use the echo command on
For example, if you are using the default user ofkeycloakusers
to retrieve the value of thepassword
for the user of the Kubernetes container.foundry
, you would run the following code from the command line:# get password for foundry user:
echo $(kubectl get keycloakusers -n hitachi-solutions keycloak-user -o jsonpath='{.spec.user.credentials[0].value}')
Specify the following credentials for the Kubernetes container:
Kubernetes credential Description foundry_client_name
Client ID of the Kubernetes container in Keycloak if different than the default solution-control-plane-sso-client
value.foundry_client_secret
Client secret in Keycloak that you obtained in the previous step. username
Username of the account with administrative permissions to the Kubernetes container ( foundry
for example).password
Password of the account with administrative permissions to the Kubernetes container that you obtained in the previous step. Specify the following Network File System (NFS) volume properties:
NFS volume property Description Example volume_hostname
NFS server host. my-nfs-server.example.com
volume_path
Path for the volume root directory in the NFS server. /ldos-volume Lumada DataOps Suite must point to a NFS server to store files for the Data Transformation Editor, Dataflow Importer, and Dataflow Engine solutions. See Administer for more information on these solutions.
Save and close the env.properties file.
Next steps
Run the install script
Default role | Sample username* | Description |
Administrator | cmoore | Full access to LDOS, including Solution management and Keycloak. |
Data Engineer | bwayne | Access to dataflow operations, including to the Data Transformation Editor, and access to Data Catalog as an Analyst. |
Data Steward | mpayton | Limited access to dataflow operations, and access to Data Catalog as a Steward. |
Analyst | cparker | Limited access to dataflow operations, and access to Data Catalog as an Analyst. |
Guest | jdoe | View-only access. |
*For each role provided in the table above, the sample username is also the password. |
Perform the following steps to run the install script:
Procedure
Navigate to the installer directory in your LDOS package, which was unpacked when the LDOS solutions were uploaded.
Run the following script from the command line:
./install.sh
Results
Configuring DNS entries
You need to establish Domain Name System (DNS) aliases for Lumada Data Catalog and LDOS Data Transformation Editor to the cluster to identify these solutions. Create the following DNS aliases to your cluster, replacing <HOSTNAME>
with the hostname of your cluster:
catalog-<HOSTNAME>
dte-<HOSTNAME>
Adding licenses
Before you begin, contact your Hitachi Vantara Customer Success representative for PDI and Lumada Data Catalog (LDC) licenses. The LDOS package does not include these licenses.
Apply PDI license
Perform the following steps to apply a PDI license:
Procedure
Contact your Hitachi Vantara Customer Success representative for the PDI license file.
Make sure the license file is named .installedLicenses.xml.
Upload the .installedLicenses.xml file to the NFS volume under the <volume_path>/licenses directory.
Results
Apply Lumada Data Catalog license
Perform the following steps to turn on all the features in LDC:
Procedure
Contact your Hitachi Vantara Customer Success representative for a full LDC version license.
Run the following code from the command line to upgrade the license to the full version:
kubectl create secret generic ldc-license --from-file=license-features.yaml --from-file=ldc-license-public-keystore.p12 -n hitachi-solutions
Results
Test the installation
Perform the following steps to test your installation:
Procedure
Enter the following address into a browser with
<HOSTNAME>
replaced by the hostname of your cluster:https://<HOSTNAME>/hitachi-solutions/control-plane/control-plane-lcp-app/
The browser opens the LDOS Solution Login page.
Log in with any of the default users listed in Run the install script.
Results