Creating an SFS Turbo File System

Prerequisites

1. A VPC is available.

   If no VPC is available, create one by referring to section "Creating a VPC with a Subnet"Creating a VPC with a Subnet in the Virtual Private Cloud User Guide.

2. ECSs are available and they belong to the created VPC.

   If no ECSs are available, buy ECSs by referring to Purchasing an ECS in Custom Config Mode.

3. Creating SFS Turbo file systems depends on the following services: VPC, Billing Center, BSS, DSS, and ECS. Ensure that required roles or policies have been configured.
   • The SFS Turbo FullAccess permissions already include the VPC FullAccess permissions, which are required for creating file systems. An IAM user assigned the SFS Turbo FullAccess permissions does not need to have the VPC FullAccess permissions assigned explicitly.
   • To create yearly/monthly file systems, the BSS Administrator permissions are required.
   • To create file systems in dedicated projects, the DSS FullAccess and ECS FullAccess permissions are required.

Creating an SFS Turbo File System

1. Log in to the SFS Turbo console.
2. In the upper right corner of the page, click Create File System.
3. Configure the parameters based on Table 1, as shown in Figure 1.
   Figure 1 Creating an SFS Turbo file system
   

   Table 1 File system parameters

   Parameter	Description
   Billing Mode	Mandatory. Select a billing mode for the SFS Turbo file system. Pay-per-use (preselected): This is a postpaid billing mode in which you pay nothing upfront and are not tied to any contract or commitment. For details, see Pay-per-Use Billing. Yearly/Monthly: You prepay for a certain period. It is a good choice when you need stable resources for a fixed duration. For details, see Yearly/Monthly Billing. For detailed billing standards, see Product Pricing Details.
   Region	Mandatory. Select a region where you want to create the SFS Turbo file system. Once an SFS Turbo file system is created, its region cannot be changed. For lower latency and faster access, select the region nearest to where the data will be accessed. You are advised to select the region where the servers reside. For more information about regions, see Region and AZ.
   AZ	Mandatory. Select an AZ where you want to create the SFS Turbo file system. An AZ is a geographical area with independent power supply and network facilities in a region. Accessing an SFS Turbo file system across AZs results in some performance loss. You are advised to select the AZ where your servers reside. Once an SFS Turbo file system is created, its AZ cannot be changed. For more information about AZs, see Region and AZ.
   Type	Mandatory. Select an SFS Turbo file system type. You can select from one of the following types: Standard Performance Standard-Enhanced (discontinued) Performance-Enhanced (discontinued) 20 MB/s/TiB 40 MB/s/TiB 125 MB/s/TiB 250 MB/s/TiB 500 MB/s/TiB 1,000 MB/s/TiB For details about the highlights and use cases of each file system type, see SFS Turbo File System Types. NOTE: Once an SFS Turbo file system is created, its type cannot be changed. To use a different type, you must create a new file system with that type. Plan the file system type based on your service needs.
   Capacity	Mandatory. Specify a maximum capacity for the SFS Turbo file system. When the used capacity of the file system reaches this value, no more data can be written to the file system. You need to expand the file system capacity. You cannot directly reduce the capacity of an SFS Turbo file system currently. Set an appropriate file system capacity based on your service needs. Supported SFS Turbo capacity ranges are as follows: Standard: 500 GB to 32 TB Performance: 500 GB to 32 TB Standard-Enhanced (discontinued): 10 TB to 320 TB Performance-Enhanced (discontinued): 10 TB to 320 TB 20 MB/s/TiB: 3.6 TB to 1 PB 40 MB/s/TiB: 1.2 TB to 1 PB 125 MB/s/TiB: 1.2 TB to 1 PB 250 MB/s/TiB: 1.2 TB to 1 PB 500 MB/s/TiB: 1.2 TB to 1 PB 1,000 MB/s/TiB: 1.2 TB to 1 PB
   Bandwidth (MB/s)	Defines the cache bandwidth, which is recommended for workloads with frequent reads but infrequent writes. The higher the bandwidth, the larger the capacity required. If you select the 1,000 MB/s/TiB, 500 MB/s/TiB, 125 MB/s/TiB, 250 MB/s/TiB, 40 MB/s/TiB, or 20 MB/s/TiB type, this parameter and its value will show up. Bandwidth = Capacity × Bandwidth density (type value). The minimum bandwidth is 150 MB/s. If the calculated bandwidth is less than 150, 150 MB/s will be used. For the maximum bandwidths, see SFS Turbo File System Types. If you select the Standard-Enhanced (discontinued), Standard, Performance-Enhanced (discontinued), or Performance type, this parameter will not show up. NOTE: The read/write speed is affected by the number of clients that mount the file system. For details, see How Do I Make the Most Out of My SFS Turbo File System?
   Protocol Type	Mandatory. The protocol that the SFS Turbo file system will use for shared file access. NFS (preselected): Only NFSv3 is supported. NFS is suitable for Linux ECSs. SMB: SMB 2.0, SMB 2.1, and SMB 3.0 are supported. SMB is suitable for Windows ECSs. If you want to use the SMB protocol, submit a service ticket. For more information about supported protocols, see Basic Concepts.
   VPC	Mandatory. Select a VPC and a subnet. VPC: A server cannot access file systems in a different VPC. Select the VPC to which the servers reside. Subnet: A subnet is a unique IP address range in a VPC. A subnet provides dedicated network resources that are logically isolated from other networks to improve network security. NOTE: To achieve the optimal network performance, select the VPC where your servers reside. You can also use VPC peering connections to connect two or more VPCs to share files between VPCs. When an SFS Turbo file system is accessed across VPCs, the latency, bandwidth, and IOPS loss may be high. Therefore, intra-VPC access is recommended. For details about VPC peering connections, see section "VPC Peering Connection" in Virtual Private Cloud User Guide. When you create an SFS Turbo file system, the system automatically creates IP addresses in the specified subnet. These IP addresses cannot be changed after the file system has been created. On the VPC console, you can view the type of the resource that uses each IP address.
   Automatic Backup	Optional. Cloud Backup and Recovery (CBR) provides backup protection for SFS Turbo file systems and allows you to use backup data to create SFS Turbo file systems. After you configure automatic backup, the system will associate the SFS Turbo file system with the backup vault and apply the selected policy to the vault to periodically back up the file system. The following options are available: Do not use (preselected): Skip this configuration if backup is not required. If you need backup protection for your SFS Turbo file system after it is created, perform backup by referring to Backing Up an SFS Turbo File System. Use existing Vault Name: Select an existing backup vault from the drop-down list. Backup Policy: Select a backup policy from the drop-down list, or go to the CBR console and configure a desired one. Buy new Vault Name: Enter a vault name, which can contain up to 64 characters, including letters, digits, underscores (_), and hyphens (-), for example, vault-turbo-f61e. The default naming rule is vault-turbo-xxxx. Vault Capacity (GB): Backups are stored in vaults. Enter a vault capacity required for storing file system backups. The vault capacity cannot be less than the SFS Turbo file system capacity, so enter a value ranging from the total size of associated SFS Turbo file systems to 10,485,760, in the unit of GB. Backup Policy: Select a backup policy from the drop-down list, or go to the CBR console and configure a desired one.
   Encryption	Optional. If you select KMS encryption, the SFS Turbo file system will be encrypted. Data in the SFS Turbo file system will be more secure. The following parameters will be displayed if encryption is enabled: KMS key name A key name is the identifier of the key. You can use KMS key name to specify a KMS key and use it for encryption. Select an existing key from the drop-down list or click View KMS List to create a new key. For details, see Creating a Custom Keysection "Creating a Custom Key" in the Key Management Service User Guide. KMS Key ID After you select a key name, the system automatically shows the key ID. Key Encryption Algorithm After you select a key name, the system automatically shows the encryption algorithm of the key. NOTE: You are advised to enable encryption to ensure core data security. If you use KMS encryption, any usage beyond the free quota given by KMS will be billed. For details, see DEW Pricing Details. You can create an SFS Turbo file system that is encrypted or not, but you cannot change the encryption attribute of an existing SFS Turbo file system.
   Security Group	Mandatory. A security group is a virtual firewall that provides network access control policies for SFS Turbo file systems. You can define access rules for a security group. Then, these rules will be applied to all SFS Turbo file systems added to this security group. When creating an SFS Turbo file system, you can select only one security group. If no security group is specified, the system will automatically create one named sfsturbo_{file-system-ID}. You are advised to use an independent security group for an SFS Turbo file system to isolate it from service nodes. To ensure that your clients can access the SFS Turbo file system, after the file system is created (with a security group selected), the system will automatically enable traffic on ports 111 (TCP/UDP), 2049 (TCP/UDP), 2052 (TCP), and 20048 (TCP/UDP) from all IP address ranges, including primary and secondary CIDR blocks, in the VPC of this SFS Turbo file system. If your NFS clients need to access the file system from other network ranges, you need to add inbound rules to this security group later. Otherwise, the SFS Turbo file system cannot be mounted. Inbound traffic is enabled on the following ports: NFS protocol: 111 (TCP/UDP), 2049 (TCP/UDP), 2052 (TCP), and 20048 (TCP/UDP) SMB protocol: 445 (TCP) Security group rules influence how SFS Turbo file systems can be accessed and used. For how to configure security group rules, see section "Managing Security Group Rules" in the Virtual Private Cloud User GuideManaging Security Group Rules.
   Tag	Optional. You can add tags to SFS Turbo file systems to quickly identify and search for desired file systems. You can customize tags or select those predefined on TMS. For more information about tags, see Managing SFS Turbo File System Tags. A tag is a key-value pair. Tag key (mandatory): Tag keys for the same SFS Turbo file system must be unique. It can contain up to 36 characters. It can contain letters, digits, spaces, and special characters (_.:=+-@), but cannot start or end with a space or start with _sys_. Tag value (optional): Tag values can be duplicate and can be left blank. It can contain up to 43 characters. It can contain letters, digits, spaces, and special characters (_.:/=+-@), but cannot start or end with a space. NOTE: You can add up to 20 tags to a single SFS Turbo file system. Each tag has only one key and one value. If your organization has enabled tag policies and has an SFS Turbo-related tag policy attached, you must comply with the tag policy rules when creating SFS Turbo file systems, otherwise SFS Turbo file systems may fail to be created. Contact the organization administrator to learn more about tag policies.
   Enterprise Project	Mandatory. Select an enterprise project you want to add the SFS Turbo file system to. This parameter is only available for enterprise accounts. An enterprise project makes it easy to manage projects and groups of cloud resources and users. Use the default enterprise project or create a new one. You can add an SFS Turbo file system to an enterprise project for unified management when creating an SFS Turbo file system. You can only select an existing enterprise project. To create a new one, click Create Enterprise Project next to the drop-down list. For detailed operations, see Creating an Enterprise Project. For details about enterprise projects, see Enterprise Management User Guide.
   Name	Mandatory. Customize a name for the SFS Turbo file system. Comply with the following rules when customizing the name: It must be unique within your account in a given region. If an SFS Turbo file system is deleted, you can create a new SFS Turbo file system with the same name after at least 30 minutes. It must start with a letter and can contain only letters, digits, underscores (_), and hyphens (-). It must contain 4 to 64 characters.

4. Click Create Now.
5. Confirm the SFS Turbo file system information and click Submit.
6. When the creation is complete, go back to the SFS Turbo file system list.

   If the status of the created SFS Turbo file system is Available, the file system has been created successfully. If the status is Creation failed, rectify the fault by referring to Creating an SFS Turbo File System Failed.

Follow-Up Operations

• After creating an SFS Turbo file system, you need to mount it on cloud servers so they can access and share it. For details, see Mounting an SFS Turbo File System.
• You can configure alarm policies for the file system inode usage and capacity usage by referring to Creating an SFS Turbo Alarm Rule. Later, when such an alarm is reported, you can delete data to release space or expand the file system capacity in a timely manner. Otherwise, data can no longer be written to the SFS Turbo file system when the capacity is used up, and services will be affected.