Create a File System

You can create a file system and mount it to multiple servers. Then the servers can share this file system.

Prerequisites

Before creating an SFS Turbo, SFS Capacity Oriented file system, ensure that a VPC is available.
If no VPC is available, create one by referring to section "Creating a VPC" in the Virtual Private Cloud User Guide.
Before creating an SFS Turbo, SFS Capacity Oriented file system, ensure that ECSs are available and are in the created VPC.
If no ECS is available, create an ECS by referring to "Creating an ECS" in the Elastic Cloud Server User Guide.

Logging In to the Management Console

Visit the Huawei Cloud website at www.huaweicloud.com/intl/en-us/.
Register an account.

Before using SFS, you need to register a HUAWEI ID. This account can be used to access all Huawei Cloud services, including SFS. If you already have an account, start from 3.
1. In the upper right corner of the page, click Sign Up.
2. Complete the registration as instructed.
  After you have successfully registered, the system automatically redirects you to your personal information page.
Log in to the management console.
1. In the upper right corner of the displayed page, click Console.
2. Enter the username and password as prompted, and click Sign In.
After logging in to the management console, select the region where the service is located from the drop-down list in the upper left corner of the page.
Choose Storage > Scalable File Service to go to the SFS console.
It is recommended that you top up your account and subscribe to SFS so that the service can be used properly. For details about how to purchase SFS, see

Creating an SFS Capacity-Oriented File System

Log in to the management console using a cloud account.
1. Log in to the management console and select a region and a project.
2. Choose Storage > Scalable File Service.
In the upper right corner of the page, click Create File System.

Set the parameters as described in Table 1.

**Table 1** Parameter description
Parameter	Description	Remarks
File System Type	Select SFS Capacity-Oriented or SFS Turbo.	Select SFS Capacity-Oriented.
AZ	A geographical area with an independent network and an independent power supply.	You are advised to select the same AZ as that of the ECSs.
Protocol Type	SFS supports NFS (only the NFSv3 protocol currently) and CIFS for file system access. The NFS protocol is applicable to Linux ECSs, and the CIFS protocol is applicable to Windows ECSs.	Set this parameter based on site requirements.
VPC	An ECS cannot access file systems in a different VPC. Select the VPC to which the ECS belongs. NOTE: By default, all ECSs in a VPC have the same rights. You can modify the VPC in the future. Upon creation, only one VPC can be added for each file system. After a file system is created, you can configure multiple VPCs by referring to Configuring Multi-VPC Access for the SFS file system.	Click View VPC to view existing VPCs or create a new one.
Maximum Capacity	Maximum capacity of a single file system. When the used capacity of a file system reaches this value, no more data can be written to the file system. You need to expand the file system.	The value ranges from 1 GB to 512,000 GB.
Encryption	Optional This parameter specifies whether a file system is encrypted. You can create a file system that is encrypted or not, but you cannot change the encryption settings of an existing file system. If Encryption is selected, the following parameters will be displayed: Create Agency If the KMS access rights are not granted to SFS Capacity-Oriented, this button will be displayed. Otherwise, this button will not be displayed. Click Create Agency to grant SFS Capacity-Oriented the permissions to access KMS. The system automatically creates an agency and names it SFSAccessKMS. When SFSAccessKMS is displayed for Agency Name, the KMS access rights have been granted to SFS Capacity-Oriented, and SFS Capacity-Oriented can obtain KMS keys for encrypting or decrypting the file system. After the rights are granted, follow-up operations do not need granting rights again. Agency Name Agency: An agency is a trust relationship between two tenants or services. A tenant can create an agency to grant resource access rights to another tenant or service. SFSAccessKMS: If Agency Name is SFSAccessKMS, SFS Capacity-Oriented is granted the KMS access rights to use custom keys to encrypt or decrypt file systems. KMS key name NOTE: KMS key name is displayed only after the agency named SFSAccessKMS has been created. For details, see Create Agency above. KMS key name is the identifier of the key, and you can use KMS key name to specify the KMS key that is to be used for encryption. You can select one of the following keys: Default key: After the KMS access rights have been granted to SFS Capacity-Oriented, the system automatically creates a default key and names it sfs/default. Custom key: Existing or newly created custom keys. For details, see "Creating a Custom Key" in the Key Management Service User Guide. NOTE: Before you use the encryption function, the KMS access rights must be granted to SFS Capacity-Oriented. If you have the right to grant the permission, grant SFS the permissions to access KMS directly. Otherwise, you need to contact the system administrator to obtain the "Security Administrator" rights first. For details, see File System Encryption.	-
Name	User-defined name of the file system. If you create more than one file system, a name suffix is added to each file system name automatically. For example, if you set the name to sfs-name for two new file systems, the two file system names will be sfs-name-001 and sfs-name-002.	The name can contain only letters, digits, underscores (_), and hyphens (-). When creating one file system, enter a maximum of 255 characters. When creating multiple file systems, enter 1 to 251 characters.
Quantity	Number of file systems to be created	Each cloud account can have a total of 512,000 GB for its file systems. Each cloud account can create a maximum of 10 file systems, one by one or in a batch. If the quantity or total capacity of the file systems you are creating exceeds the upper limit, click Increase quota to apply for a higher quota.

Click Create Now.
Confirm the file system information and click Submit.
Go back to the file system list.

If the status of the created file system is Available, the file system is created successfully. If the status is Creation failed, contact the administrator.

Creating an SFS Turbo File System

Log in to the management console using a cloud account.
1. Log in to the management console and select a region and a project.
2. Choose Storage > Scalable File Service.
In the upper right corner of the page, click Create File System.

Set the parameters. Table 2 describes the parameters.

**Table 2** Parameter description
Parameter	Description	Remarks
File System Type	Mandatory Select SFS Capacity-Oriented or SFS Turbo.	Select SFS Turbo.
Region	Mandatory Region of the tenant. Select the region from the drop-down list in the upper left corner of the page.	You are advised to select the same region as that of the servers.
AZ	Mandatory A geographical area with an independent network and an independent power supply.	You are advised to select the same AZ as that of the servers.
Protocol Type	Mandatory SFS Turbo supports NFS for file system access.	The default value is NFS.
Storage Class	Mandatory Includes SFS Turbo Standard and SFS Turbo Performance. For more information, see File System Types.	Select Standard. NOTE: Once a file system is created, its storage class cannot be changed. If you want to change the storage class, you need to create another file system. Therefore, you are advised to plan the storage class carefully in advance.
Capacity	Maximum capacity of a single file system. When the used capacity of a file system reaches this value, no more data can be written to the file system. You need to expand the file system. The capacity of an SFS Turbo file system cannot be decreased. Set an appropriate file system capacity based on your service needs.	Supported scope: SFS Turbo Standard: 500 GB to 32 TB SFS Turbo Performance: 500 GB to 32 TB
VPC	Mandatory Select a VPC and its subnet. VPC: A server cannot access file systems in a different VPC. Select the VPC to which the server belongs. Subnet: A subnet is an IP address range in a VPC. In a VPC, a subnet segment must be unique. A subnet provides dedicated network resources that are logically isolated from other networks, improving network security. NOTE: Upon creation, only one VPC can be added for each file system. Multi-VPC file sharing can be implemented through VPC peering connection. For details about VPC peering connection, see section "VPC Peering Connection" in Virtual Private Cloud User Guide.	-
Security Group	Mandatory A security group is a virtual firewall that provides secure network access control policies for file systems. You can define different access rules for a security group to protect the file systems that are added to this security group. When creating an SFS Turbo file system, you can select only one security group. You are advised to use an independent security group for an SFS Turbo file system to isolate it from service nodes. The security group rule configuration affects the normal access and use of SFS Turbo. For details about how to configure a security group rule, see . After an SFS Turbo file system is created, the system automatically enables the security group port required by the NFS protocol in the SFS Turbo file system. This ensures that the SFS Turbo file system can be accessed by your ECS and prevents file system mounting failures. The inbound ports required by the NFS protocol are ports 111, 445, 2049, 2051, 2052, and 20048. If you need to change the enabled ports, choose Access Control > Security Groups of the VPC console and locate the target security group.	-
Cloud Backup and Recovery	CBR provides backup protection for SFS Turbo and allows you to use backup data to create an SFS Turbo file system. After you set Cloud Backup and Recovery, the system binds the SFS Turbo file system to the cloud backup vault and associates the file system with the selected backup policy to periodically back up the file system. The following options are available, among which the default value is Do not use: Auto assign: Set the name of the cloud backup vault, which is a character string consisting of 1 to 64 characters, including letters, digits, underscores (_), and hyphens (-), for example, vault-f61e. The default naming rule is vault_xxxx. Enter the vault capacity, which is required for backing up the SFS Turbo file system. The vault capacity cannot be less than the size of the file system. Its value ranges from the total size of the associated file systems to 10,485,760 in the unit of GB. Select a backup policy from the drop-down list, or log in to the CBR console and configure a desired one. Use existing vault: Select an existing cloud backup vault from the drop-down list. Select a backup policy from the drop-down list, or log in to the CBR console and configure a desired one. Do not use: Skip this configuration if backup is not required. If you need backup protection after a file system has been created, log in to CBR Console, locate the desired vault, and associate the file system to the vault.	-
Name	Mandatory User-defined name of the file system.	The value can contain only letters, digits, and hyphens (-). The name of the created file system must contain more than four characters and less than or equal to 64 characters.

Click Create Now.
Confirm the file system information and click Submit.
Complete the creation and go back to the file system list.

If the status of the created file system is Available, the file system is created successfully. If the status is Creation failed, contact the administrator.