CFS Turbo is Tencent Cloud's high-performance parallel file storage. Compared to traditional general-purpose file storage, its client and server currently support two network types: CCN network and VPC network, each with its pros and cons. This document will compare these two network types to help you choose the network type that better suits your needs. For the complete creation process, see Using the CFS Turbo File System on Linux Clients. Use Limits
Please note the following limitations before selecting a network type:
VPC network: Before using the VPC network method, you need to submit a ticket to apply. It is recommended to plan in advance: Divide a separate subnet for Turbo use, and reserve at least 64 free IPs for subsequent normal expansion. CCN: Using CCN requires that your account has created a CCN instance. For details, see CCN Product Overview. Recommended Solution
|
CCN has been used. | CCN | No additional components required, seamless transition, supports cross-VPC access. |
Small-scale use within a single VPC | VPC | Simple configuration without the need to introduce CCN. |
Requires cross-VPC access | CCN | Natively supports cross-VPC communication. |
Large-scale scale-out scenario | CCN | Avoid subnet IP address shortage issues. |
Pursue concise solutions | VPC | Submit in advance. |
CCN
Introduction
Specified CIDR blocks are assigned to Turbo file systems, and CCN capabilities are leveraged to connect the VPC and storage server network, implementing the interaction between compute instances and storage.
|
CIDR block planning is separately conducted for storage systems for more efficient and convenient management of security groups. Turbo CFS has its own CIDR block to reserve sufficient IPs for future scaling without limits. Turbo CFS can be accessed more easily across VPCs. IPs of the existing VPC are not occupied. | CCN is required to establish connectivity. For users who do not use CCN, new components need to be introduced, which introduces some complexity. Before 00:00:00 on April 1, 2027, each account is entitled to a free quota of 2 network connection instances. For details, see CCN - Billing Overview. |
Best Practices
Assign a CIDR block that does not conflict with the selected CCN to the CFS. To avoid IP address conflicts, do not allocate this CIDR block to other resources. The selected CIDR block must fall within 10.0.0.0/8, 11.0.0.0/8, 30.0.0.0/8, 33.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16. It is recommended to assign the 11/30 CIDR block to Turbo with a subnet mask between /16 and /24. This CIDR block is used for the server-side network and does not occupy business IP addresses.
All VPCs where clients need to access the CFS Turbo file system must be associated with the same CCN, and ensure valid routing policies to enable normal access and usage of CFS. If network connectivity issues persist after the CCN association is completed, check for routing conflicts. For details, see Routing Policies. VPC
IPs are mapped to the existing VPC on the storage server for mount and access.
Note:
Turbo occupies a large number of IPs, and each scale-out operation requires additional IPs. For Turbo using VPC networks, scale-out may fail when subnet IPs are insufficient. Therefore, this creation method is not recommended. If you still need to create in this way, after careful evaluation, submit a ticket to contact us. |
It is the easiest to use and is similar to general CFS. No new components need to be introduced in this simple solution. | During large scaling, subnet IPs may be insufficient. It occupies IPs in the VPC and subnet, and the storage is bound to the VPC network, making network isolation difficult to implement. |