Home > Workload Solutions > Data Analytics > Guides > Dell PowerScale and Cloudera Data Platform Private Cloud Data Services > Additional requirements using PowerScale OneFS
Ozone is inherently used to store the CDE job logs, however PowerScale OneFS S3 can be used in its place. A post-installation task to configure a bucket for the logs can be implemented before creating a CDE virtual service or CML workspace.
PowerScale OneFS is not automatically identified by the Control Plane so an additional property (hdfs_client_config_safety_valve) must be added via the Cloudera Manager user interface to the Dell PowerScale CSD Service. This will allow CDP Data Services to interact with the PowerScale WebHDFS API.
<property><name>dfs.namenode.http-address</name><value>cdp.solarch.lab.com:8082</value></property>
Where ‘cdp.solarch.lab.com’ is the PowerScale OneFS SmartConnect zone name.
Note: The value in the above figure is the same SmartConnect Zone URL which was entered when configuring the PowerScale CSD during the CDP Private Cloud Base installation. The two service principals that were created when enabling Kerberos on PowerScale OneFS are also required. Reference the Dell PowerScale and Cloudera Data Platform Private Cloud Base installation guide for details.
Additional manual user configuration is required on PowerScale OneFS when using the Hue file browser with the CDP Private Cloud Base Data Services Virtual Warehouse:
For example:
mkdir /ifs/<access zone>/hadoop-root/user/dwxdevuser
chmod dwxdevuser:supergroup /ifs/<access zone>/user/dwxdevuser
For example:
isi hdfs proxyusers modify hive --zone <access zone> --add-user dwxdevuser