CLOUD PAAS / DEVELOPMENT TOOLS

CLI Tutorial: Mount Points

This guide has been reviewed and reformatted for Ruk-Com Cloud PaaS. Screens may vary slightly by platform version.

Click or tap a screenshot to view it at its original size.

Objective

This guide explains how to use CLI Tutorial: Mount Points on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.

Before you begin

  • Sign in with an account permitted to manage the relevant environment.
  • Confirm the target environment, region and resources before saving changes.
  • Create a backup or rollback plan before changing a production system.

Mount PointsIt is used to manage connections between data storage servers and clients, allowing you to work with remote shared files as easily as your local files. How to use it: Via the CLI, you can configure the mount via the terminal and include specific scripts for automation.

in the section below We provide available commands for manipulating mount points as follows:

1. The first step is to check the list of available mount points using the relevant command.GetMountPoints:

~/jelastic/environment/file/getmountpoints --envName  {env_name} --nodeId  {node_ID}

where:

  • {env_name}- The domain name of the environment for which you want to check mount points.
  • {node_ID}- Unique identifier of the node to be checked.

More:You can also use “nodeGroup"instead"nodeId” to select the environment layer and display all mount points on that layer (e.g. cp, bl, storage, etc.)

2. You can check the export using the methodGetExportedListThat's right, using the same parameters as the previous command.

~/jelastic/environment/file/getexportedlist --envName  {env_name} --nodeId  {node_ID}

3. Adding mount points for a single node uses the CLI method.AddMountPointByIdThe following:

~/jelastic/environment/file/addmountpointbyid --envName  {env_name} --nodeId  {node_ID} --path  {local_path} --protocol  {protocol} --sourcePath  {source_path} --sourceNodeId  {source_node_ID} --readOnly {true/false}

where:

  • {env_name}- The domain name of the environment where you want to add the mount point.
  • {node_ID}- Unique node ID number within the environment selected to be installed.
  • {local_path}- Path to the client node's data folder to be displayed.
  • {protocol}- Protocol to use (requirednfs)
  • {source_path}- Path to the file server where your data is stored.
  • {source_node_ID}- ID identifies the source node.

More:Alternatively, you can use the parametersourceHostTo point to the storage server via IP or domain name.

  • {true/false}– Appropriate value for setting permissionsread onlyorread & writefor client nodes while performing data installation (false by default)

If you are not sure whether mount points are allowed to connect between nodes, You can perform direct verification using the command:

~/jelastic/environment/file/checkcrossmount --envName {env_name} --nodeId {env_name} --sourceNodeId {source_node_ID}


As in the picture above you can see the cross mount (i.e.true) if mount from our storage from node(111109)to128994Information is now shared in the opposite direction (from128994to111109) But if you get the valuefalseYou can add connection points between nodes.

4. Deleting mount points (RemoveMountPointById) You can use the following command:

~/jelastic/environment/file/removemountpointbyid --envName  {env_name} --nodeId  {node_ID} --path  {local_path}

5. You can also add mount points to all environment layers without needing to run separate commands for each node.

~/jelastic/environment/file/addmountpointbygroup --envName  {env_name} --nodeGroup  {env_layer} --path  {local_path} --protocol  {protocol} --sourcePath  {source_path} --sourceNodeId  {source_node_ID} --readOnly {true/false}

where:

  • {env_name}- The domain name of the environment where you want to add the mount point.
  • {node_ID}- Unique node ID number within the environment selected to be installed.
  • {local_path}- Path to the client node's data folder to be displayed.
  • {protocol}- Protocol to use (requirednfs)
  • {source_path}- Path to the file server where your data is stored.
  • {source_node_ID}- ID identifies the source node.

More:Alternatively, you can use the parametersourceHostTo point to the storage server via IP or domain name.

  • {true/false}– Appropriate value for setting permissionsread onlyorread & writefor client nodes while performing data installation (false by default)
  • 6. You can unmount data from all layer nodes with the methodRemoveMountPointByGroup:

    ~/jelastic/environment/file/removemountpointbygroup --envName  {env_name} --nodeGroup  {env_layer} --path  {local_path}