After you develop an application, you can deploy the application in the application hosting platform Serverless App Engine (SAE). This topic describes how to deploy a Python application by using a ZIP package in the SAE console.

Prerequisites

Procedure

  1. Log on to the SAE console.
  2. In the left-side navigation pane, click Applications. In the top navigation bar, select a region. Then, click Create Application.
  3. In the Basic Information step, configure the parameters and click Next: Application Deployment Configurations.
    ParameterDescription
    Application Name

    Enter a custom application name.

    VPC

    Select a configuration method for the VPC. Valid values:

    • Custom Configuration: If you select this option, you must manually specify the namespace, VPC, vSwitch, and security group for the application that you want to create.
    • Automatic Configuration: If you select this option, SAE automatically specifies the namespace, VPC, vSwitch, and security group for the application.
    Namespace

    This parameter is required only if the VPC parameter is set to Custom Configuration. Select an existing namespace from the drop-down list.

    Note Namespaces and VPCs are in one-to-one mapping relationships. For information about how to modify a VPC, see Create and manage a VPC.
    vSwitch

    This parameter is required only if the VPC parameter is set to Custom Configuration. Click Select vSwitch. In the Select vSwitch dialog box, configure the parameters.

    You must specify at least one vSwitch. We recommend that you specify no more than three vSwitches. Each vSwitch must match at least one application instance.

    Security Group

    This parameter is required only if the VPC parameter is set to Custom Configuration. Select a security group from the drop-down list.

    Note If you have not created a security group in your VPC, click Create Security Group to create a security group as prompted. For more information, see Create a security group.
    Application InstancesSelect the number of instances that you want to create.
    VCPUSelect the CPU specification for the instances that you want to create.
    MemorySelect the memory specification for the instances that you want to create.
    Application DescriptionEnter the basic information about the application.
  4. In the Deployment Configurations step, configure the parameters.
    1. Configure the parameters that are used to deploy an application.
      ParameterDescription
      Technology Stack Programming LanguageSelect Python.
      Application Deployment MethodSelect Deployment with ZIP Packages.
      Run componentsSelect an environment from the Python environment drop-down list.
      File Upload methodSelect Upload Zip package or Zip package address.
      • Upload Zip package: Click Select File and select the ZIP package that you want to use
      • ZIP Address: Enter the directory in which the ZIP package is stored.
      Note
      • Format of the package name: The package name can contain only letters, digits, hyphens (-), and underscores (_), and the extension must be .zip. This format is the same as the name format of the WAR package and JAR package that are used to deploy Java applications.
      • Structure of the package directory: You must make sure that the requirements on the directory structure of the ZIP package are met. For more information, see Create a ZIP package for a Python application.
      VersionThe version number of the application. Enter a version number or click Use timestamp as version number.
      Time zone settingsSelect the time zone of the application. Example: UTC+8.
      Custom installation module dependenciesSelect this option to install dependencies in the requirements.txt file in the root directory. If the package does not contain this file and you do not configure custom dependencies in the package, specify the dependencies that you want to install in the text box.
    2. Optional:Configure the following advanced settings based on your business requirements.
      Advanced settingDocumentation
      Startup Command SettingsConfigure a startup command
      Environment Variable SettingsConfigure environment variables
      Hosts Binding SettingsConfigure host bindings
      Application Health CheckConfigure application health checks
      Application Outbound/Inbound Internet Access
      Application Lifecycle ManagementConfigure application lifecycle management
      Log Collection Service
      Persistent StorageConfigure NAS storage
      Configuration ManagementInject configurations
  5. Click Next: Confirm Specifications.
  6. In the Specification Confirmation step, view the details of the application and the fee for the selected specifications. Then, click Confirm.
    The Creation Completed step appears. You can click Application Details to go to the Basic Information page of the application.
  7. Verify whether the configurations have taken effect.
    • Method 1:

      In the left-side navigation pane of the Basic Information page, click Change Records. On the Change Records page, view the change details. If Executed is displayed in the Change Status column, the application is deployed and the configurations have taken effect.

    • Method 2:

      On the Basic Information page, click the Instance Deployment Information tab to view the Status of the instances. If Running is displayed in the Status column, the application is deployed and the configurations have taken effect.

References

The following table describes the operations that you can perform on an application after you deploy the application on SAE.
OperationReferences
Lifecycle management operations, such as updating, starting, stopping, and deleting an application, and scaling in or scaling out the instances for an applicationManage the lifecycle of an application
Performance optimization operations, such as configuring auto scaling policies for an application, binding Server Load Balancer (SLB) instances to an application, and starting or stopping applications in batches
Application status-based operations, such as managing logs, configuring monitoring settings, viewing application events, and viewing change records