Storage-level isolation in DataStage

Important: IBM Cloud Pak® for Data Version 4.8 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.

Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.8 reaches end of support. For more information, see Upgrading from IBM Cloud Pak for Data Version 4.8 to IBM Software Hub Version 5.1.

Each PX instance can access a persistent volume that is mounted at px-storage and all instances have access to a shared volume mounted at ds-storage. You can hide these volumes from PX instances by using the command line.

To hide /ds-storage from the asset browser for all PX instances, set the flag hide_ds_volume on the DataStage custom resource by running this command. The px-runtime pods of all PX instances will restart.

oc -n ${PROJECT_CPD_INST_OPERANDS} patch datastage datastage --type merge -p '{"spec": {"hide_ds_volume": true}}'

To hide both /ds-storage and /px-storage from the asset browser for a particular PX instance, set the flag hide_default_volumes on the PX custom resource with this command.

oc -n ${PROJECT_CPD_INST_OPERANDS} patch pxruntime <cr-name> --type merge -p '{"spec": {"hide_default_volumes": true}}'

By default, any target files that do not use the absolute file path are written to /ds-storage. To change the default location, set the environment variable APT_WORKING_DIRECTORY.