IBM Storage Scale Client Policy
Add this policy to an application component in a virtual application pattern or virtual system pattern to define it as a IBM Storage Scale Client.
This policy contains the required IBM Storage Scale installation process for connecting the deployed pattern instance to a IBM Storage Scale Server. The deployed pattern instance can then access and use the shared file system associated with the IBM Storage Scale Server.
- Use the deployed IBM® shared service for IBM Storage Scale instance to find the IBM Storage Scale Server to which it can connect.
- Use a remote IBM Storage Scale Server (an external
IBM Storage Scale Server instance that was not deployed
using the IBM Storage Scale Pattern Type). In this case your
deployment must include customized script packages that contain the appropriate IBM Storage Scale commands for making the connection to the external IBM Storage Scale Server. For more information on customizing
and including these script packages in your IBM Storage Scale Client deployment, see the Related
links.
In this case, you do not need to deploy an IBM shared service for IBM Storage Scale prior to deploying the IBM Storage Scale Client instance, because the IBM Storage Scale Client points directly to the IBM Storage Scale Server to which it is connecting.
- Specify the IBM Storage
Scale Manager IP address and Client Key at deployment time, or by using the Connect operation
after the client virtual machine is deployed.Note: In this case, you do not need to deploy an IBM shared service for IBM Storage Scale prior to deploying the IBM Storage Scale Client instance, because the IBM Storage Scale client points directly to the IBM Storage Scale Server to which it is connecting.
- Client maxblocksize
- This field configures the client cluster
maxblocksize
configuration parameter. If the client cluster maxblocksize configuration parameter is smaller than the IBM Storage Scale shared file system block size, the client cannot mount the file system. Update this value only when the client fails to mount the file system because the client maxblocksize is smaller than the file system block size. In this case, set the client maxblocksize to the same value as file system block size.For more information about the
maxblocksize
property, see File System Planning and Block size. - Enforce file set Quota On Root
- This field configures the client cluster
enforceFilesetQuotaOnRoot
configuration parameter. Use this parameter to enforce the file set quota on the root user. By default, the maximum quota is not enforced for the root user. If set to true, the root user is enforced to follow the file set hard quota for this client.Use this option with caution. If the quota is enforced on the root user, any processes that are executed by the root user on this client fail if the hard quota is exceeded on a file set during the process execution.
- IBM Storage Scale user group GID
- Optional. Use this value to set the
GID
of the IBM Storage Scale user group,gpfsadmin
. TheGID
must be a numeric value, such as 501, 402. - IBM Storage Scale user UID
- Optional. Use this value to set the
UID
of the IBM Storage Scale user,gpfsprod
. TheUID
must be a numeric value, such as 5001, 4002.
For virtual system patterns or classic virtual system patterns you can also use a script package approach to connect a IBM Storage Scale Client to a IBM Storage Scale Server instead of using the IBM Storage Scale Client Policy. Using script packages to configure your IBM Storage Scale Client gives you more control over when the IBM Storage Scale Client code is run, if your situation requires it. For more information on using this script package approach, see the Related links.