Templates

The Templates holds the configuration information for creating servers, and is used to quickly create servers later.

The Templates saves the configuration information of the created server, which is used for subsequent quick creation of servers.

Entry: Click “Compute/Compute/Templates” menu item in the left menu item of the cloud management platform to enter the Templates page.

Create Templates

This function is used to create a Templates. The configuration parameters for creating a Templates are much the same as those for creating a server.

Create Templates prerequisites

  • On-Premise: Requires the presence of OneCloud platform hosts with enabled status in the base resource, or the cloud management platform has been docked to the VMware platform, and the VMware platform hosts with enabled status exist in the base resource.
  • Private cloud: The cloud management platform is required to have imported the resources of OpenStack, ZStack or DStack cloud accounts, and the hosts belonging to the above platforms exist in the base resources in the enabled state, and the corresponding platforms have available IP subnets.
  • Public cloud: The cloud management platform is required to import the resources of AliCloud, AWS, Azure, Huawei Cloud, Tencent Cloud or UCloud cloud account, the cloud account is enabled and the status is normal, and the corresponding platform has an available IP subnet.

Create Templates

  1. In the Templates list, you can create On-Premise Templatess, private server templates, and public server templates.
    • On-Premise Templates: Click the “Create” button at the top of the list and select the drop-down menu “On-Premise” menu item to enter the Create On-Premise Templates page.
    • Private Server Template: Click the “Create” button at the top of the list, select the drop-down menu “Private Cloud menu item, and enter the Create Private Server Template page.
    • Public Server template: Click the “Create” button at the top of the list and select the drop-down menu “Public Cloud” menu item to enter the Create Public Server template page.
  2. Configure the following parameters.

    • Specify project: Select the project to which the Templates belongs.

    • Template name: Set the name of the Templates.

    • Region (On-Premise, private cloud): Select the region and zone. You need to determine the platform to which the server belongs by region when creating a private cloud platform server.

    • Billing type (public cloud): Including postpaid and prepaid packages.

      • This model is suitable for scenarios where the demand for equipment can increase dramatically in an instant, and the price is more expensive than prepaid packages.
      • This model is suitable for scenarios where the demand for equipment is relatively stable, and the price is cheaper than the postpaid model.

    • Platform (On-Premise): Choose the platform to which the servers belong, including OneCloud and VMware.

    • Platform and region (public cloud): You can determine the packages available to users by city, platform, region, and zone, and it is recommended to choose the closest city, which can reduce access latency and improve access speed.

    • CPU architecture: x86 and arm architectures are currently supported. Only OneCloud platforms support arm architecture, other platforms only support x86 architecture by default.

    • Configure GPU: Configure GPU card for the server, after enabling this item, you also need to select the specific GPU card.

    • CPU, Memory: set the specifications of the server. And you can choose the available packages according to the server specifications, etc.

    • Configuration: Virtual machine packages are combinations of CPU and memory specifications of servers with different package prices. Among them, On-Premise and private cloud packages can be maintained through the cloud management platform, and users can choose the packages of On-Premise or private cloud platform when creating servers of private cloud platform. The public cloud package information is synchronized with the information on the corresponding public cloud platform.

    • OS.

      • Public Cloud Image: Display the public image on the corresponding public cloud platform, which is only supported by the public cloud platform and is not displayed in the image list.
      • Public Cloud Custom Image: Support for selecting custom images on the specified cloud account of the corresponding public cloud platform, supported only by the public cloud platform, not displayed in the image list.
      • Private Cloud Image: Show the image on the corresponding private cloud platform, only supported by the private cloud platform. Not shown in the image list.
      • VMware platform images: Support to select the images of specified VMware accounts on VMware platform, only supported by VMware platform. Not shown in the image list.
      • Public image: corresponds to the public image in the list of system images, which is generally the common image of the system and maintained by the administrator.
      • Custom Image: Corresponds to the custom image in the system image list, generally uploaded by the user.
      • Boot from ISO: corresponds to the ISO format image in the system image list. When selecting an ISO image file, the user is required to install the operating system for the server. Only OneCloud platforms are supported.
      • Host image: Corresponds to the host image in the host image list, supported by OneCloud platform only.
      • Server Snapshot: Corresponds to the server snapshot in the server snapshot list, supported by OneCloud platform only.

    • System disk: Display and set different disk types and disk capacity size according to the selected package. The public cloud platform does not support setting the scheduling tab.

      • When scheduler tags and scheduling preferences are not set, the system will select the best storage for the server according to the scheduler policy and scheduler tags.
        • When there is a scheduler policy that matches the scheduler policy, the system will select the corresponding storage according to the scheduler tag and scheduler tag preference set in the scheduler policy. The scheduler tag preferences in the scheduler policy will override the default policy in the scheduler tag.
        • When there is no conforming scheduler policy, the optimal storage will be selected based on the default policy of the scheduler tag bound in the storage device.
      • When scheduler tag and scheduler tag preference are set, the set scheduler tag preference will override the default policy on the scheduler tag. The storage that provides the system disk is selected based on the scheduling preference as well as the scheduler tag.
        • Prefer: Scheduling prefers storage with this tag.
        • Avoid: Scheduling avoids storage with this tag.
        • Exclude: Exclude storage with this tag from scheduling.
        • Require: stores with this tag must be used when scheduling.
      • E.g. Take local storage as an example, local storage A is bound to scheduler tag A. The default policy for scheduler tag A is to use as much as possible. Local storage B is bound to scheduler tag B. The default policy for scheduler tag B is to prohibit its use. Scheduler policy A is when creating a server in project A, select scheduler tag B, and scheduler policy preference is must use.
        • When the scheduler tag is not set, there are two cases as follows.
          • If the server belongs to project A, the system will prefer local storage B to provide storage for the server system disk.
          • When the server does not belong to project A, the system will prefer local storage A to provide storage for the server system disk.
        • When the scheduler tag is set to A and the policy is Disable, the system will exclude local storage A and select local storage B to provide storage for the Server system disk.

    • Data disk: Optional, you can add multiple data disks according to the demand, and support up to 12 data disks. Set the type of disk and capacity size. The disk optional type is the same as the system disk.

      • Only OneCloud platform supports support for setting mount points, snapshotting build disks, and setting scheduler tags. Private clouds that use local storage also support the set scheduler tag feature.
        • Set scheduler tag: same as system disk.
        • Set mount point: Set the file type (ext4, xfs, swap) of the data disk, and the non-system directory where the data disk is mounted. Only one of them can be set: set mount point and snapshot build disk.
        • Snapshot build disk: Create data disk based on snapshot. You can view the existing snapshots in the On-Premise. You can set only one mount point and one snapshot build disk.

    • Administrator password: Set the administrator password, which is the password of root user in Linux system and administrator user in Windows OS.

      • Random Password: randomly generated administrator password, users can view the copied administrator password in the password column of the server list
      • Key Pair: You need to create key before associating the key. After associating the key, the user needs to use the private key to log in the server remotely.
      • Keep image settings: The administrator password is the existing administrator password in the image.
      • Custom Password: You can set the administrator password manually.

    • Network: Set the IP address of the server. Only OneCloud platform Servers can add up to 8 networks, other platforms only support one network.

      • Auto scheduling: When Auto scheduling is selected, IP addresses will be assigned to servers from the IP subnets where Auto scheduling is enabled.
      • Specify IP Subnet: Select the VPC and IP subnet. If you need to specify a static IP, click the “Manually Configure IP” button to set the IP address and click the “OK” button.
      • Specify scheduler tag: Set the scheduler tag and the scheduler tag preference. The set scheduler tag preference will override the default policy on the scheduler tag. Select the optimal IP subnet based on the scheduler tag and scheduling preferences.
        • Prefer: Scheduling preference is given to IP subnets that have this tag.
        • Avoid: Try to avoid IP subnets with this tag when scheduling.
        • Exclude: Exclude IP subnets with this tag from scheduling.
        • Require: IP subnets with this tag must be used in scheduling.
      • E.g. if IP subnet A is bound to scheduler tag A, the default policy is prohibit, and IP subnet B is bound to scheduler tag B, the default policy is try to use. Scheduler policy A is when the server belongs to project A. Select scheduler tag A and scheduler tag preference is must use.
        • When the network is selected as default when the server is created, there are two cases as follows.
          • When the server belongs to project A, the system will select IP subnet A to assign an IP address to the server.
          • When the server does not belong to project A, the system will select IP subnet B to assign an IP address to the server.
        • When the network selection specifies IP subnet A when creating a server, the system will select IP subnet A to assign an IP address to the server.
        • When the network selects scheduler tag A when creating a server and the tag preference is must use, the system will assign an unused IP address from IP subnet A to the server.

    • Tag: Optional, supports the selection of existing tags and new tags.

      • Create Tag: Click the Create button at the top of the list to set the tag key and tag value, and click the “Add” button to create tag and bind it to the resource.
      • Select an existing tag: Click the “Existing Tag” button to select the tag key and value Advanced Settings: Hidden by default, can be configured according to requirements.

    • Elastic public IP : Elastic public IP is a kind of NAT IP, which can realize the communication between server and public network by binding with server. The default is no binding, when you select “Create”, you need to configure the following parameters.

      • Line type: You can create the EIP of the corresponding line type according to your requirements.
      • Network billing method: Set the billing method of the EIP, including billing by traffic and billing by bandwidth.
        • Billed by traffic: charge by actual transmission traffic, which can limit the peak bandwidth to avoid the cost of unexpected traffic, and will drop packets when the instantaneous bandwidth exceeds the value, which is applicable to the occasion of large network fluctuation.
        • Billed by Bandwidth: Billed by transmission rate, choose fixed bandwidth, packets will be dropped when the bandwidth exceeds the value, suitable for scenarios with less network fluctuation.
      • Bandwidth: Set the bandwidth size.

    • Public IP (Tencent Cloud and Alibaba Cloud): Public IP enables communication between servers and the public network by binding with servers. It includes EIP and Static Public IP. EIP can be flexibly bound or unbound with servers. Static public IP does not support unbinding with servers. The default is no binding. When you select “Create EIP” or “Create Static Public IP”, you need to configure the following parameters.

    • Network billing method: Set the billing method of the EIP, including billing by traffic and billing by bandwidth.

      • Billed by traffic: Billed by actual transmission traffic, which can limit the peak bandwidth to avoid the cost of unexpected traffic, and will drop packets when the instant bandwidth exceeds the value, which is suitable for the occasion of network fluctuation.
      • Billed by Bandwidth: Billed by transmission rate, choose fixed bandwidth, packets will be dropped when the bandwidth exceeds the value, suitable for scenarios with less network fluctuation.

    • Bandwidth: Set the bandwidth size.

    • Security Group: Set security group rules for servers. Security group is a virtual packet filtering firewall that controls whether the associated servers can be accessed and the external resources that servers can access by setting security group rules. A server supports binding up to 5 security groups.

    • Boot method: Including BIOS and UEFI mode, only supported by OneCloud platform.

  3. Click the “Save Template” button to save the configuration information of the created server as a Templates.

Create server creation

This function is used to create server based on a Templates. You can create a server only when the status of the Templates is normal.

  1. Click the “Create Server” button on the right column of the Templates to enter the Create Server page.
  2. Set the name and number, and click the “OK” button to create server.

Delete Templates

This function is used to delete a Templates. When the Templates is used by the service directory, it is not allowed to be deleted.

Individual Deletion

  1. On the Templates page, click the “Delete” button in the action column on the right side of the Templates to bring up the action confirmation dialog.
  2. Click the “OK” button to complete the operation.

Batch Delete

  1. Check one or more Templatess in the Templates list, click the “Delete” button at the top of the list, and the operation confirmation dialog box pops up.
  2. Click the “OK” button to complete the operation.

View Templates Details

This function is used to view the details of the Templates.

  1. On the Templates page, click the Templates Name item to enter the Templates Details page.
  2. The menu item on the right side of the Templates name supports the management operations for the Templates.
  3. View the following information.
    • Basic Information: Including Cloud ID, ID, name, status, domain, project, associated key, platform, billing method, region, zone, cloud account, created at, updated at, and description.
    • Other information: Including OS, system image, VPC, IP subnet, security group, system disk, data disk, CPU, memory, GPU, GPU number, and administrator password.

View Templates operation log

This function is used to view the log information of Templates related operations.

  1. On the Templates details page, click the Operation Log tab to enter the Operation Log page.
    • Load More Logs: In the Operation Logs page, the list shows 20 operation logs by default. To view more operation logs, click the “Load More” button to get more logs.
    • View Log Details: Click the “View” button on the right column of the operation log to view the log details. Copy details are supported.
    • View logs of specified time period: If you want to view the operation logs of a certain time period, set the specific date in the start date and end date at the top right of the list to query the log information of the specified time period.
    • Export logs: Currently, only the logs displayed on this page are supported to be exported. Click the upper-right corner of icon, set the export data column in the pop-up export data dialog, and click the “OK” button to export the logs.