Platform For AI:Create and use preemptible instances

1. Go to the Deploy Service page. For more information, see Model service deployment by using the PAI console and Machine Learning Designer.

2. On the Deploy Service page, configure the following parameters. For more information about other parameters, see Model service deployment by using the PAI console and Machine Learning Designer.

   Parameter	Description
   Resource Group Type	Select Public Resource Group.
   Resource Configuration Mode	Select Cost-effective Resource Configuration.
   Preemptible Instance Protection Period	Valid values: 1-Hour Protection Period: You can set a protection period of 1 hour for a preemptible instance. This means that during a protection period of 1 hour, the system ensures your access to the instance. No Protection Period: The preemptible instance does not have a protection period.
   Deployment	Resource Type: Select Spot. Node Type: Select an appropriate node type. Bid Price: Set a bid price to bid for preemptible instances. If the resources required to create the instance are sufficient and your bidding price is greater than or equal to the market price of the instance, the instances can be created. Specify multiple instance types: You can click the icon to configure multiple preemptible instances. You can add up to five resource types. For more information about how to configure multiple instances, see Specify multiple instance types. Note We recommend that you also select Common instances to ensure resources for service deployment.

3. Click Deploy. When Service Status changes to Running, the service is deployed.

In this topic, a Windows 64 server is used as an example.

1. Create a service configuration file named service.json in the directory where the client is located. Sample content:

   {
     "name": "service_example",
     "model_path": "http://examplebucket.aliyuncs.com/models%2Fmnist_saved_model.tar.gz",
     "processor": "tensorflow_cpu_1.12",
     "metadata": {
       "instance": 1,
     }
     "cloud": {
       "computing": {
         "instances": [
           {"type": "ecs.g7.2xlarge", "spot_price_limit": 2.00},
           {"type": "ecs.g7.4xlarge", "spot_price_limit": 4.00},
           {"type": "ecs.g7.2xlarge"},
           {"type": "ecs.g7.4xlarge"}
         ],
         "disable_spot_protection_period": true
       }
     }
   }

   The following table describes the key parameters that are required in the file. For more information about other parameters, see Run commands to use the EASCMD client.

   Parameter	Description
   instance	The number of service instances. In this example, one instance is specified in the JSON configuration file.
   instances	Instance types. You can specify one or more instance types. If resources are insufficient for the first instance type, the system prepares resources for the next instance type. type: the instance type. spot_price_limit: your highest bidding price for preemptible instances. This field is optional. If this field is specified, preemptible instances whose prices are less than the value specified by this field are used. Unit: USD. The pay-as-you-go billing method is supported. If this field is not specified, standard pay-as-you-go instances are used.
   disable_spot_protection_period	Specifies whether to disable the instance protection period. Default value: false. Valid values: false: The preemptible instance has a 1-hour protection period after the instance is created. During the protection period, the instance provides services even if the market price is higher than the bidding price. true: The preemptible instance does not have a protection period. Instances without a protection period are 10% cheaper than instances that have a protection period.

2. Run the following command in the directory where the JSON file is located to create the service:

   eascmdwin64.exe create <service.json>

   Replace <service.json> with the name of the JSON file that you created.

1. Go to the Resource Configuration dialog box. For more information, see the "Modify in the console" section in the Specify multiple instance types topic.

2. On the Cost-effective Resource Configuration tab, configure Spot Instance Protection Period, specify Spot instance types, and then click OK.

   Note

   We recommend that you also select common instances to ensure resources for service deployment.

   

   For more information about how to configure other parameters, see Use the console to specify preemptible instances.

In this topic, a Windows 64 server is used as an example.

1. Create a file named instances.json in the directory where the client is located. Sample content:

   {
     "cloud": {
       "computing": {
         "instances": [
           {"type": "ecs.g7.2xlarge", "spot_price_limit": 2.00},
           {"type": "ecs.g7.4xlarge", "spot_price_limit": 4.00},
           {"type": "ecs.g7.2xlarge"},
           {"type": "ecs.g7.4xlarge"}
         ],
         "disable_spot_protection_period": true
       }
     }
   }

   For information about the key parameters, see the "Specify preemptible instances when you create a service" section in this topic.

2. Run the following command in the directory where the JSON file is located to modify the service settings and specify preemptible instances:

   eascmdwin64.exe modify <service_name> -s <instances.json>

   Replace <service_name> with the name of the EAS service and <instances.json> with the name of the JSON file that you create.