:Usage notes for the shared resource group

{
  "name": "tf_serving_test",
  "model_path": "http://eas-data.oss-cn-shanghai.aliyuncs.com/models/model.tar.gz",
  "processor": "tensorflow_gpu_1.12",
  "cloud":{
      "computing":{
          "instance_type":"ecs.gn6i-c24g1.6xlarge"
      }
  },
  "metadata": {
    "instance": 1,
    "cuda": "9.0",
    "memory": 7000,
    "gpu": 1,
    "cpu": 4
  }
}

• Access to EAS

  You want to access EAS from your virtual private cloud (VPC) in direct connection mode.

• Access from EAS

  You want to use EAS to access a service in your VPC, such as Redis.

• The following table describes the fields with the cloud.networking prefix.

  Field	Description
  cloud.networking.security_group_id	The ID of the security group. The ECS instance on which your client resides belongs to the security group.
  cloud.networking.vswitch_id	The ID of the vSwitch. The ECS instance on which your client resides belongs to the vSwitch. An ENI will be created for the vSwitch. Make sure that the vSwitch can have enough available IP addresses. Otherwise, service instances cannot be created for service deployment in EAS. Note By default, the access from or to the VPC to which the specified vSwitch belongs is allowed. If the CIDR block of the VPC is 10.0.0.0/8, which overlaps the CIDR block of EAS, service instances fail to be connected. To prevent this issue, you must use the destination_cidrs field to explicitly specify a subnet of the CIDR block of the VPC to or from which you allow access. For example, if you want to allow access only from or to the CIDR block (10.1.1.0/24) of the specified vSwitch, you can set the value of the destination_cidrs field to 10.1.1.0/24.
  cloud.networking.destination_cidrs	The subnet of the CIDR block of the VPC to or from which you allow access. The value must be explicitly specified.
  cloud.networking.default_route	The default network egress. Valid values: eth0 and eth1. Default value: eth0. After you connect EAS to the VPC of your client, a service instance has two network interface controllers (NICs). eth0 is the primary NIC in the VPC of EAS, and eth1 is the secondary NIC in the VPC of your client. By default, the traffic flows from eth0. However, the VPC of EAS does not allow access over the Internet. Typically, if you want to enable Internet access for EAS, you can configure a NAT gateway for the VPC of your client and set the cloud.networking.default_route field to eth1. Then, the traffic to the Internet can flow to the VPC of your client through eth1 and finally flow to the Internet through the NAT gateway.

• The following code provides an example on how to set the fields:

  {
    "model_path": "http://eas-data.oss-cn-shanghai.aliyuncs.com/models/lr_xingke4.pmml",
    "name": "test_pmml",
    "processor": "pmml",
    "metadata": {
      "instance": 1,
      "cpu": 3,
      "memory": 2000
    },
    "cloud": {
      "networking.security_group_id": "sg-2vce4xxvy5hn1hmjx7yh",
      "networking.vswitch_id": "vsw-2vcbbihcy3cg8fjdpdvdl",
      "networking.destination_cidrs": "10.2.0.0/8"
    }
  }

{
  "model_path": "http://eas-data.oss-cn-shanghai.aliyuncs.com/models/lr_xingke4.pmml",
  "name": "test_pmml",
  "processor": "pmml",
  "runtime": {
    "core_pattern": "/corefiles/%h-%t-%e-%p.core"
  },
  "metadata": {
    "instance": 1,
    "cpu": 3
  }
}