Manage protocol services
This topic describes how to manage Cloud Parallel File Storage (CPFS) protocol services in the console, including how to create, modify, and delete protocol services.
Prerequisites
A CPFS file system is created. For more information, see Create a file system.
A fileset is created if you want to use a fileset to export the directory. For more information, see the Create a fileset section of the "Manage filesets" topic.
Up to 32 IP addresses in the specified vSwitch are occupied to create a protocol service. Make sure that the specified vSwitch contains sufficient IP addresses.
Limits
Only CPFS V2.3.0 and later support protocol services.
Only one protocol service can be created in a CPFS file system.
Usage notes
Billing
General-purpose: You can use a general-purpose protocol service for free.
Cache: You are charged for cache protocal services based on the highest internal bandwidth you use per hour. For more information, see Billable item and billing methods.
Specifications
Protocol services are available in two types: General-purpose and Cache-accelerated. Unlike the General-purpose type, the Cache-accelerated type provides caching for hot spot data. If a cache hit occurs, the bandwidth of a Cache-accelerated protocol service can exceed the bandwidth of the CPFS file system and reach the maximum bandwidth set for the protocol service.
General-purpose: Provides NFS protocol access and directory-level mount points for CPFS, eliminating the need to configure a POSIX client management cluster. This feature is free of charge.
Cache: Builds on the general-purpose type by providing a server-side memory cache that uses a Least Recently Used (LRU) policy. When data is cached in memory, CPFS can deliver higher internal bandwidth. The cache protocol service is available in two specifications, Cache I and Cache II, which differ in internal bandwidth and memory cache size.
Export directories
Before you can access the data of the CPFS file system from an Elastic Compute Service (ECS) instance using a Network File System (NFS) protocol, you must create an export agreement to export a fileset or a directory.
You can create export agreements for up to two VPCs per protocol service. For each VPC, a security group named
<cpfs-fsid>-<vpc-id>-nfs-sgis automatically created.We recommend that you export filesets. A fileset can provide more features, such as the file quantity management and dataflow. Make sure that a fileset or a directory exists when you create an export agreement.
When you export directories, you must specify a VPC and a vSwitch. Only the ECS instances in the VPC can access the CPFS file system using the protocol service. The IP addresses in the specified vSwitch are occupied to export directories. Make sure that the specified vSwitch contains sufficient IP addresses.
Create a protocol service
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 details page of the file system, click Protocol Service.
On the Protocol Service tab, click Create Protocol Service and configure the following parameters.
Parameter
Description
Protocol Service Configuration
The type of the protocol service. The default type is general-purpose.
NoteThe bandwidth of a general-purpose protocol service is the same as that of the CPFS file system. A general-purpose protocol service does not support data caching and you are not charged for any fees.
Protocol Type
Only the NFSv3 protocol is supported.
VPC Network
The VPC in which the protocol service resides. This parameter is automatically set to the VPC in which the CPFS file system resides and cannot be modified.
vSwitch
The vSwitch that is used by the protocol service. This parameter is set to the vSwitch that is used by the CPFS file system. You can select another vSwitch in the VPC.
NoteUp to 32 IP addresses in the specified vSwitch are occupied to create a protocol service. Make sure that the specified vSwitch contains sufficient IP addresses.
Export Agreement
The fileset or directory that you want to export from the CPFS file system using the protocol service. We recommend that you specify a fileset, which provides features such as dataflow and file quantity management.
NoteYou must specify a fileset or directory that exists in the CPFS file system.
An exported folder has the following format:
The path must be 1 to 1,024 characters in length.
Use UTF-8 encoding.
The path must start and end with a forward slash (/). To export the root directory, enter
/.
Export VPC
Select the VPC in which the ECS instance to which you want to mount the protocol service resides. This way, the ECS instance in the VPC can access the CPFS file system using the protocol service.
Export vSwitch
Select the vSwitch that is used by the ECS instance to which you want to mount the protocol service. This way, the protocol service can use the vSwitch to export the protocol service to the VPC in which the ECS instance resides.
NoteUp to 32 IP addresses in the specified vSwitch are occupied to create a protocol service. Make sure that the specified vSwitch contains sufficient IP addresses.
Permission Group
Only the default permission group of the VPC is supported.
After the configuration is complete, click OK.
Delete a protocol service
After a protocol service is deleted, ECS instances cannot access the CPFS file system using the protocol service. Perform this operation with caution. It takes the system 5 to 10 minutes to delete a protocol service.
On the Protocol Service tab, find the protocol service that you want to delete.
In the Actions column, click Delete.
In the message that appears, click OK.
Modify a protocol service
You can modify the internal bandwidth and description of a protocol service. The changes take 2 to 5 minutes to take effect.
On the Protocol Service tab, find the protocol service that you want to modify.
In the Actions column, click Modify.
After the modification is complete, click OK.
Change the type of a protocol service
Change the protocol service type from general-purpose to cache
ImportantYou cannot directly change a general-purpose protocol service to a cache protocol service. You must delete the general-purpose protocol service and create a cache one. Similarly, if you want to change the protocol service type from cache to general-purpose, you must delete the cache protocol service and create a general-purpose one. During the change, the service is interrupted. Reserve the change window before making the change.
You must regenerate the export folder.
Delete the general-purpose protocol service
On the Protocol Service tab, find the protocol service that you want to delete. Click Delete in the Actions column, and then click OK.
Create a cache protocol service
For more information, see the Create a protocol service section in this topic.
Change the protocol service type from one cache type to another
On the Protocol Service tab, find the protocol service that you want to modify.
In the Actions column, click Modify and select a new protocol service specification.
After the modification is complete, click OK.
View protocol services
You can view the created protocol services and export directories using the protocol services.
On the Protocol Service page, you can view information about the specified protocol service.