Getting Started (SFS Capacity-Oriented)
Scenarios
SFS provides high-performance network-attached storage (NAS) that is scalable on demand. A shared file system can be shared with multiple Elastic Cloud Servers (ECSs) and Bare Metal Servers (BMSs). If you need a fully hosted shared file storage and want to access a file system on multiple ECSs, SFS is perfect for you.
The following describes how to call the API for Creating a Shared File System. For details, see Making an API Request.
Prerequisites
You need to plan the region where a file system resides and determine the endpoint for calling an API based on the region. It can be obtained from Regions and Endpoints.
Creating a Shared File System
{ "share": { "description": "test description", "share_type": "default", "name": "share_London", "metadata": { "key1": "value1", "key2": "value2" }, "share_proto": "NFS", "size": 10, "is_public": false } }
- description: Specifies the description of the shared file system, which adds remarks to the shared file system.
- share_type: Specifies the name of a share type. A share type is used to specify the type of the storage service to be allocated.
- share_proto: Specifies the protocol types of the shared file system.
- name: Specifies the custom name of the shared file system. For example, share_London.
- size: Specifies the size (in GB) of the shared file system.
- is_public: Specifies the visibility level of the shared file system. If it is set to true, the file system can be seen publicly. If it is set to false, the file system can be seen privately. The default value is false.
- metadata: Specifies the metadata information of the shared file system. The value consists of one or more key and value pairs organized as a dictionary of strings.
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