A dataflow enables data movement between a Cloud Parallel File Storage (CPFS) fileset and an Object Storage Service (OSS) bucket. Before you move data between a fileset and a bucket, you must create the corresponding dataflow. This topic describes how to create and manage dataflows in the CPFS console.
Prerequisites
A CPFS fileset has been created and the fileset is in the Normal state. For more information, see Create a fileset.
The source OSS bucket has been tagged (key: cpfs-dataflow, value: true). Do not delete or modify this tag while using the dataflow; otherwise, CPFS dataflow cannot access the data in the bucket. For more information, see Tag an OSS bucket.
If multiple CPFS dataflows, or multiple dataflows of the same CPFS, use the same OSS bucket as the source storage, you must enable versioning for the OSS bucket to prevent data conflicts when multiple dataflows export data to the same OSS bucket. For more information, see Overview of versioning.
If you want to configure automatic metadata update, make sure that the EventBridge service has been activated. For more information, see Activate EventBridge and grant permissions.
NoteCurrently, the automatic metadata update feature is supported only in the China (Hangzhou), China (Chengdu), China (Shanghai), China (Shenzhen), China (Zhangjiakou), and China (Beijing) regions.
Usage notes
Billing
After a dataflow is created, you are charged based on the dataflow bandwidth. For more information, see Billable items.
When you configure automatic update, CPFS uses EventBridge to collect object modification events from the source OSS storage, which incurs event fees. For more information, see EventBridge billing.
Permissions
When you create a dataflow, CPFS obtains the AliyunServiceRoleForNasOssDataflow and AliyunServiceRoleForNasEventNotification service-linked roles. For more information, see Service-linked roles for CPFS.
Create a dataflow
Log on to the NAS console.
In the left-side navigation pane, choose File System > File System List.
In the top navigation bar, select a region.
On the File System List page, click the name of the file system.
On the file system details page, click Dataflow.
On the Dataflow tab, click Create Dataflow.
In the Create Dataflow dialog box, configure the following parameters.
Parameter
Description
Fileset ID /Name
Select a fileset.
ImportantCreating a dataflow requires the fileset to be empty. Make sure that the fileset contains no data; otherwise, the creation may fail.
OSS Bucket Path
Select the source OSS bucket to associate with the CPFS fileset.
OSS Bucket SSL
Specify whether to enable transport encryption (HTTPS).
Automatic Metadata Update
Specify whether to enable the automatic metadata update feature.
Metadata update interval (minutes)
When the automatic metadata update feature is enabled, you must specify the metadata update interval in minutes.
OSS Prefix
When the automatic metadata update feature is enabled, you must specify the automatic update directory.
Limits:
The length must be 2 to 1024 characters.
The path must start and end with a forward slash (/).
The path must be an existing prefix in the OSS bucket.
EventBridge Status
The status of the EventBridge service.
Automatic update depends on the EventBridge service. Make sure that the EventBridge service is activated.
Bandwidth (MB/s)
The maximum throughput bandwidth of the dataflow. Unit: MB/s.
Valid values:
600
1200
1500
The throughput bandwidth of the dataflow cannot exceed the I/O bandwidth of the file system.
SLR Authorization
You must agree to authorize the service-linked role that allows CPFS to access OSS and EventBridge service resources. For more information, see Service-linked roles for CPFS.
Click OK.
Related operations
You can use the console to view created dataflows, modify dataflow configurations, delete dataflows, or stop dataflows.
Operation | Description | Procedure |
View a dataflow | You can view the created dataflows and create dataflow tasks on a specified dataflow. | On the Dataflow tab, you can view the configuration information of a specified dataflow. |
Modify a dataflow | You can only modify the metadata update interval, add OSS prefix automatic update directories, and modify the bandwidth and description of a dataflow. |
|
Stop a dataflow | After a dataflow is stopped, billing stops in the next billing cycle. Important After a dataflow is stopped, data cannot be imported or exported, and the tasks that are being executed are canceled. |
|
Enable a dataflow | You can enable a dataflow that is in the Stopped state. |
|
Delete a dataflow | After a dataflow is deleted, all tasks of the specified dataflow are cleared, and data can no longer be synchronized. |
|