- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Billing
- Getting Started
- User Guide
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
API
- Lifecycle Management
- Connection Management
- Tag Management
- Name Management
- File System Management
-
Storage Interworking Management
- Adding a Backend Target
- Querying Backend Targets
- Obtaining Details About a Backend Target
- Deleting a Backend Target
- Updating the Properties of a Storage Backend
- Updating the Auto Synchronization Policy of a Storage Backend
- Creating an Import or Export Task
- Querying Details About an Import or Export Task
- Listing Import and Export Tasks
- Deleting an Import or Export Task
- Updating a File System
- Directory Management
-
Permissions Management
- Creating a Permission Rule
- Querying Permission Rules of a File System
- Querying a Permission Rule of a File System
- Modifying a Permission Rule
- Deleting a Permissions Rule
- Creating and Binding the LDAP Configuration
- Querying the LDAP Configuration
- Modifying the LDAP Configuration
- Deleting the LDAP Configuration
- Task Management
- Permissions Policies and Supported Actions
- Common Parameters
- Appendix
- SDK Reference
-
FAQs
- SFS Turbo Concepts
- SFS Turbo Specifications
- SFS Turbo Billing
-
SFS Turbo Mount
- What Can I Do If Data of My SFS Turbo File System Is Not the Same When Accessed from Two Client Servers?
- Can I Mount an SFS Turbo File System Across Regions?
- Can I Mount an SFS Turbo File System Across Accounts?
- How Many Cloud Servers Can I Mount an SFS Turbo File System To?
- How Do I Mount a File System to a Linux ECS as a Non-root User
- What Can I Do If Mounting a Subdirectory of a File System Failed?
- SFS Turbo Access
- SFS Turbo Capacity Expansion
- SFS Turbo Deletion
- SFS Turbo Migration
- SFS Turbo Performance
-
Others
- Does the Security Group of a VPC Affect the Use of SFS Turbo?
- What Resources Does SFS Turbo Occupy?
- How Do I Check Whether an SFS Turbo File System Is Available on a Linux Server?
- Can I Upgrade an SFS Turbo File System from the Standard Type to the Performance Type?
- Does SFS Turbo File Systems Support Multi-AZ Deployment?
-
Troubleshooting
- Mounting a File System Timed Out
- Mounting a File System Failed
- File System Performance Was Poor
- Creating an SFS Turbo File System Failed
- File System Automatically Unmounted
- A Client Server Failed to Access a File System
- Abnormal File System Status
- Data Fails to Be Written into a File System Mounted to ECSs Running Different Types of Operating Systems
- Writing to a File System Failed
- Error Message "wrong fs type, bad option" Was Displayed During File System Mounting
- General Reference
Copied.
Getting Started
This section describes how to use APIs by calling an API to create an SFS Turbo file system.
The token obtained from IAM is valid for only 24 hours. If you want to use one token for authentication, you can cache it to avoid frequently calling.
Involved APIs
If you use a token for authentication, you must obtain the token and add X-Auth-Token to the request header of the API when making a call. The following APIs are involved in the request for creating an SFS Turbo file system:
- API for obtaining tokens from IAM
- API for creating an SFS Turbo file system. For details, For details about how to create an SFS Turbo file system, see section "Creating a File System" in the Scalable File Service Turbo (SFS Turbo).
Procedure
- Obtain the token by following instructions in Authentication.
- Add X-Auth-Token to the request header.
- Specify the following parameters in the request body:
{ "share": { "name": "sfs-turbo-test", "share_proto": "NFS", "share_type": "STANDARD", "size": 100, "availability_zone": "az1", "vpc_id": "d651ea2b-2b20-4c6d-8bbf-2adcec18dac9", "subnet_id": "b8884abe-f47b-4917-9f6c-f64825c365db", "security_group_id": "8c4ebbd0-6edf-4aae-8353-81ce6d06e1f4" } }
- Send the request POST https://Endpoint of SFS Turbo/v1/{project_id}/sfs-turbo/shares.
- After the request is successfully responded, the ID and name of the SFS Turbo file system are returned.
If the request fails, an error code and error information are returned. For details about the error codes, see the abnormal return values of the corresponding API.
Query SFS Turbo file system details based on the returned file system ID. For details, see Querying Details About a File System.
If the returned status of the file system is 200, the SFS Turbo file system is successfully created. For details about the return values of request exceptions, see the abnormal return values of the corresponding API. For other statuses, see SFS Turbo File System Statuses.
You can query and delete an SFS Turbo file system based on the file system ID.
Configuration Example
If the token has been obtained, you can run the following curl command to create an SFS Turbo file system:
curl -k -i -X POST -H "X-Auth-Token: token_value" -H "Content-Type: application/json" -d '{"share": {"name": "sfs-turbo-test", "share_proto": "NFS", "share_type": "STANDARD", "size": 100, "availability_zone": "az1", "vpc_id": "d651ea2b-2b20-4c6d-8bbf-2adcec18dac9", "subnet_id": "b8884abe-f47b-4917-9f6c-f64825c365db", "security_group_id": "8c4ebbd0-6edf-4aae-8353-81ce6d06e1f4"}}' "https://127.0.0.1:8979/v1/xxxbxbex5cfx41f0a08ay915fd79240d/sfs-turbo/shares"
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot