Mounting a File System

Scenarios

• SFS

  Scalable File Service (SFS) is a network-attached storage (NAS) service that provides scalable high-performance file storage. With SFS, shared access can be achieved among multiple ECSs, Bare Metal Servers (BMSs), and Cloud Container Engine (CCE) and Cloud Container Instance (CCI) containers. SFS is expandable to petabytes, and provides fully hosted shared file storage. It features high availability and durability, and seamlessly handles data-intensive and bandwidth-intensive applications. SFS is suitable for high-performance computing (HPC), media processing, file sharing, content management, and web services.

• SFS Turbo

  SFS Turbo is expandable to 320 TB, and provides fully hosted shared file storage. It features high availability and durability, and supports massive quantities of small files and applications requiring low latency and high input/output operations per second (IOPS). SFS Turbo is suitable for high-performance websites, log storage, compression and decompression, DevOps, enterprise offices, and containerized applications.

• ECS

  A directory on an ECS is specified as a shared file system (see Creating an NFS Shared Directory on ECS) by using the network file system (NFS) service. The directory can then be mounted to a function in the same VPC as the ECS so that the function can read and write data in the directory. ECS file systems make it possible for dynamic expansion of compute resources. This type of file system is suitable for low service demand scenarios.

• The execution space of each function can be expanded in addition to the /tmp directory (512 MB).
• A file system can be shared by multiple functions.
• ECS compute resources can be dynamically expanded and existing ECS storage capability can be used to achieve stronger computing performance.
  Note

  You can write temporary files in the /tmp directory. The total size of these files cannot exceed 10,240 MB.

Creating an Agency

Mounting an SFS File System

User ID and group ID (just like uid and gid in Linux) let the function access a specific file system.

Mounting an SFS Turbo File System

1. On the SFS console, obtain the information about the VPC and subnet where a file system is to be mounted to your function. For details, see File System Management.
2. Enable VPC access by referring to Configuring VPC Access and enter the VPC and subnet obtained in 1.

Mounting an ECS Shared Directory

Follow-up Operations

1. Log in to the FunctionGraph console. In the navigation pane, choose Templates.
2. In the upper right corner of the Templates page, enter Web-Server-Access-Log-Statistics in the search box and press Enter.
3. In the search result, click Configure. The configuration page is displayed, as shown in Figure 1. Set the parameters as follows:

   Figure 1 Function template

   
   
   • Region: Select the same region as the created VPC and file system. For details about how to create a VPC and file system, see Configuring VPC Access and Creating a File System.
   • Project: Use default.
   • Function Name: Enter a custom name.
   • Agency: Select an agency with the file system, VPC, and APIG permissions. For details about how to create an agency, see Creating an Agency.
   • Enterprise Project: Select an enterprise project as required.
   • Environment Variables: access_log_path indicates the log file address. Set this parameter to /home/test/access_log.log.
     Note

     To specify file paths in the file system, use absolute paths starting with a slash (/). However, if no file system is mounted, you can skip adding the slash (/) and simply set the parameter to code/access_log.log.

   • Trigger Type: The default value is API Gateway (APIG). For details about how to configure APIG, see Using an APIG (Dedicated) Trigger.
   • API Name: Enter a custom name.
   • API Group: Select a group based on the actual service.
   • Environment: Select RELEASE.
   • Security Authentication: Select None.
   • Protocol and Timeout (ms): Retain the default values.

4. After parameter configuration is complete, click Create Function.
5. On the function details page, click the Code tab, add the following code to the index.py file, and click Deploy.

   import shutil
   
   

   shutil.copyfile('/opt/function/code/access_log.log', '/home/test/access_log.log')
   
   

   Figure 2 Adding code

   
   

   In addition, add the public dependency Jinja2-2.10. For details, see How Do I Add a Dependency to a Function?

   Note

   If no file system is mounted, you do not need to add the preceding code.

6. On the function details page, choose Configuration > Network and enable VPC Access. Set VPC and Subnet to the created VPC and subnet, and click Save.

   Figure 3 VPC access

   
   

7. Choose Disk Mounting, click Mount File System, and select SFS Turbo.
   • File System: Select an existing SFS Turbo file system.
   • Access Path: Set this parameter to /home/test.
   • Shared Directory: shared directory path of the file system. If this parameter is left blank by default, the function can access all directories of the file system. If a specific directory path is configured, the function can access only the directory path.

8. Click the Code tab, select Configure Test Event, create a Blank Template, and click Create.

   Figure 4 Configuring a test event

   
   

9. Select the created test event and click Test.

   Figure 5 Test result

   
   

10. Choose Configuration > Triggers, copy the URL of the APIG trigger, and open the URL using a browser.

    Figure 6 Copying a URL

    
    

    Figure 7 Results display