Function

Instance types

The instance type determines the hardware configuration and computing capacity of the virtual machine. JD Cloud provides four types of instances: General, computing-optimized, memory-optimized, and high-frequency computing ones. Instance types can be selected according to different scenarios and business levels, which can be adjusted at any time to cope with business changes. Up to 72vCPU and 576GB memory could be selected for a single instance.

Image

The image is the business running environment, and you can choose the image by yourself. JD Cloud provides public images, private images and cloud marketplace images. Public images include multiple CentOS, Ubuntu, and Windows Server released versions. Private image is one you create on the virtual machine with environment deployed, while marketplace image is one integrating the running environment or software that is created and maintained by the service provider (including the JD Cloud service team). Creating a private image of the deployed VM makes available the complete backup of the running environment and data, thus realizing the business recovery or quick deployment in batches. You can also share private images with other JD Cloud accounts.

Cloud Disk

Cloud Disk Service is Block Storage Service provided by JD Cloud for Virtual Machines. Data in Cloud Disk Service are stored in multiple real-time copies. Cloud Disk Service can expand data bucket quickly in a few minutes to achieve persistent storage of data. It provides 5 storage options including performance-oriented SSD Cloud Disk, general SSD Cloud Disk, capacity-oriented HDD Cloud Disk, SSD Cloud Disk and Premium HDD Cloud Disk. It supports incremental snapshots, and the snapshot can be used for creating Cloud Disk Service or restoring the original disk data to snapshot time point.

Networking

VPC is a logically isolated network environment defined by yourself. It supports self-planning for network deployment on demand, including setting CIDR with/without preset network range, subnet segment, routing policy, etc., and it can realize multi-level security protection via security groups and network ACL. Meanwhile, it can expand the existing network via VPC Peering or Direct Connection.An Elastic IP is a Public IP address that can be applied for independently. It supports dynamic association and disassociation operations and can make dynamic adjustment of network bandwidth without shut down. In the case of instance failure, the user can manually switch the Elastic IP address to a standby instance, thus minimizing the failure response time.

Instance Template

An instance template is a template of configuration information provided by JD Cloud to create a virtual machine, including image, virtual machine type, system disk and data disk type and capacity, VPC and subnet configuration, security group and login information, etc. Creating a VM with instance template does not require re-specifying the parameters already included in the instance template, and virtual machines with the same configuration can be created quickly for multiple times to shorten the business deployment time.

Availability group

An availability group is a physically distributed disaster recovery deployment solution across availability zones provided by JD Cloud. The virtual machines in the group are evenly deployed in multiple fault domains in the data center, which minimizes the impact of local failures on the overall high-availability application. The auto-scaling function can be enabled for the availability group to automatically expand or shrink capacity with fluctuation of the application load.

Management Tools

Manage the Virtual Machine via two means (OpenAPI and the console) by creating, starting, stopping and other ways. At the same time, two methods are supported to log in the Virtual Machine for environment configuration, i.e. the console VNC and remote SSH.

Billing Type

Virtual machine supports two billing methods: via annual/monthly subscription and by configuration: Annual/monthly subscribers shall pay for services for 1-9 months or 1-3 years in advance. Charged lower than the billing by configuration, it is preferred for scenarios where business volume (instance quantity and scale) can be predicted.

Billing by configuration is a post-payment method, providing a more flexible life cycle management. On an hourly settlement basis, it charges based on the type of VM purchased and duration (accurate to seconds). Conversion from the billing by configuration to annual/monthly subscription is available.

It is recommended to choose a virtual machine billed by configuration in the preliminary test phase, and convert to the annual/monthly subscription for an appropriate instance type according to the test situation, to save the cost.