Hi everyone, welcome to the 3rd chapter in our ten cent clouds sys ops associate course. Elastic computing deployment practices. At the end of this chapter you'll be able to manage a ten cent cloud instance. Describe CBS and images and their features and explain how to operate a ten cent CBM instance, disk and image. In this chapter will cover three sections. CBM instance operations, CBS disk operations and CBM image operations. This video will cover the first section, CBM instance operations. Subsequent videos will cover the remaining two sections. Let's get started with section one. CBM instance operations. In this video will cover CBM instances creating instances through the console logging into a CBM instance. CBM instance configuration management and automatic deployment. Will start by looking at an overview of instances including instance families instance limitations, instance, type comparison and use cases and the instance lifecycle. To provide users with the most suitable options. Each CVM series has a family of instances. Each CVM instance family represents a generation, the latest of which is the standard S5 instance. The table introduces each standard instance family starting from standard S1 to S5. As the generations move up you can see that the CPU and memory technologies both improve. Additionally, the network bandwidth increases from 10 to 29 gigabits per second with the CPU and Ram sizes also increasing as the instance family improves. There are some limitations with launching CBM's however, the number of instances that can be launched in a region is limited with a soft limit on the number of CBM instances for each availability zone. You can either have the customer submit a ticket to increase the limit or you can help the customer on the back end by communicating with other employees internally. There are also limitations on system and data disks. You can only mount one system disk to one CVM and to increase the volume you need to shut down and re install the system. To ensure the IO performance of the disc ten cent cloud has size and type limits for data disks purchased together with an instance. You can avoid instance disk limitations by purchasing a separate CBS. There are a variety of instance types which have unique features that are suitable for different use cases. The standard type which we briefly introduced has a benchmark performance for balanced computing, memory and network resources. Most standard applications that aren't CPU or RAM bound can use the standard type such as small and medium sized web applications, databases and a variety of enterprise applications. The high IO type supports low latency IO. And is suitable for no SQL databases, clustered databases and OLTP systems. The memory type carries a large memory size of 640 8GB for one instance and can be used for high performance databases. Distributed memory caches hadoop clusters or readiness. The computing type has the best performance processor and the highest cost performance and can handle high traffic web servers. MMO game servers and other computation intensive tasks. The GPU type is equipped with FPGA. And other hardware capable of real time, high speed parallel computing and floating point computing which is suitable for high performance applications such as deep learning, scientific computing, video codec and graphics workstation. The big data type carries mass storage resources with high throughput and is intended for intensive applications including mass log processing, distributed file systems and large data warehouses. The instance lifecycle can either be monthly subscription or pay as you go. For monthly subscriptions if you don't have a sufficiently high balance in your account, the instance will expire and be released in 7 days. Otherwise it will recharge and continue to run. The difference with the pay as you go life cycle is that you must manually terminate the instance. After termination it will be automatically released in two hours unless it is recovered. Okay, let's go over creating instances through the console and more specifically the instance creation process familiarizing yourself with the console and creating instances through custom configuration. You can create an instance using two methods. Quick configuration and custom configuration. Quick configuration is only available in the China console and contains preset configurations for specific types of workloads such as hosting an app, web server or word press server. Custom configuration requires you to select an instance model, configure the instance and confirm the configuration. After logging into the console you will see the CBM interface shown in the screenshot. There is a blue create button for creating an instance in addition to features that allow you to set up SSH keys. CBS, auto scaling policies and images. To create instances through custom configuration. The first step is to select an instance model. The default billing mode for international console users is pay as you go. Which is a credit based system that charges you by your usage rate. Next you can select different regions and the availability zone for that region. Then you can select which network to deploy the CVM onto and finally choose the specific instance, type. The second step in creating a CVM is to select an image and specify its image provider, operating system, system architecture and image version. Typical images include windows or Linux box, but you can also create your own custom image. After loading the image file onto the CVM, select the storage and bandwidth parameters. You can choose between premium cloud storage or SSD for the system disk and add up to 20 data disks. The public network bandwidth can be unlimited or configured to have a custom cap. You can also select a bandwidth package for a network billing model in which you are billed on a bandwidth basis. The 4th step in creating a CVM is to configure the instance. During configuration you can select different projects or security groups and name the instance. Here you can also choose between a custom password or random password for the login method. There are also options to enable the security service and cloud monitoring for free. Enabling scheduled termination allows you to create a timed session after which the CBM instance will terminate. The final step in creating a CVM is to confirm the instance, configuration and payment. You can view and edit the configuration information, including the number of CBM's purchased aeration and auto renewal. After reviewing and confirming the information you will have successfully created a CBM instance. Okay, now let's look at logging into CBM instances. Will cover CVM login methods, logging into Windows instances and logging into Linux instances. This section highlights four ways to log into a CVM instance. VNC login, remote desktop login, SSH login, and WebShell login. On Windows, VNC, RDP, or remote desktop is typically used, while on Linux, VNC, SSH, WebShell or remote login software is most commonly used. Login methods for Windows instances vary depending on the local operating system and whether the CVM instance is accessible over the Internet. If the Windows CVM instance has a public IP, then you can use the tools listed in the middle column of the chart to login. If the Windows CVM instance does not have a public IP, then you can use VNC to log in. To use VNC to log into Windows instances, first log into the CVM console. In the Operation section to the right of the corresponding instance, click Login and in the pop up window that appears, locate VNC Login and click Login Now. The VNC login page will pop up and allow you to log in to the Windows CVM instance. To use remote desktop connection to log in to Windows instances, press the Windows+R keys together to bring up the run window and type the command mst sc and hit Enter. Enter the public IP of the instance in the remote desktop connection window and click Connect. Finally enter the user name and password for the instance to login. Similarly, for logging into Linux instances, the login methods also vary depending on the local operating system, with the addition of SSH remote login as another login option. Again, if the Linux CVM instance does not have a public IP, then you can use VNC to login. Otherwise you may use the tools listed in the middle column of the chart to log in to the Linux CVM instance. You can also use remote login software to log in to Linux instances. First, install the Windows remote login software. This example uses PuTTY. Connect to the Linux CVM using PuTTY and then enter the public IP, select SSH and click Open. In the PuTTY session window, enter the administrator account and password for the instance to login. You can also log in to Linux CVM instances using WebShell. WebShell is a login method provided by Tencent Cloud that uses the web browser to connect to the Linux CVM. Advantages of WebShell includes support for copy and paste shortcuts, mouse scrolling, Chinese input, and high security. WebShell is a convenient method for accessing CVM instances from a browser and can be suitable for situations when you're using a public computer or one that is not your own. Now let's go over CVM instance configuration management. We'll look at an overview of CVM configuration management. Installing the operating system. CVM network access configuration. And adjusting the instance configuration. CVM instance configuration consists of three steps. First, install the operating system. Second, configure the network access. This includes configuring the bandwidth, defining access to internal or external networks. Configuring the security groups, and applying either elastic public IP or ENI. Third, adjust the instance configuration. You can perform operations such as upgrading or downgrading an instance, destroying an instance, or recovering and recycling an instance. Installing the operating system during initial deployment requires you to choose the operating system or image. Reinstallation allows you to restore an instance to its original launch state. And it's an important recovery method that can be used when the instance encounter system failures. To reinstall the operating system, first, make sure to confirm whether the installation is on the same platform or on a different platform. Back up the system disk and create a custom image, which you can choose during image selection. The reinstallation takes 10 to 30 minutes after starting, after which the public network IP will not change. From a billing perspective, keeping the specs the same will have no impact on costs but if you increase additional resources, then you will incur additional costs. For subsequent operations, the data disk is typically not affected because only the system disk is bound to the CVM. There are four steps to reinstall the operating system. First, log in to the CVM console. Second, select the instance to be reinstalled, click More and reinstall the system. Third, configure an instance. You can either use the current machine image or another image as well as select the disk size. Fourth, set a password. After entering the password, click Start Reinstall and the reinstallation should proceed. The process for reinstalling the operating system using another image is the same. After choosing either a public image or a custom image, you can complete the rest of the steps to reinstall to the other images. Now, let's look at CVM network access configuration. Billing for CVM instances can be based on either bandwidth in megabits per second, mbps, or traffic in gigabytes. When you allocate the outbound bandwidth on the Tencent Cloud console, it will allocate the inbound bandwidth equal to the purchased bandwidth. If the purchased Bandwidth is less than 10 Mbps, the console will still allocate 10 Mbps of inbound bandwidth. Tencent Cloud charges by gigabyte according to the user traffic from the public network. And there is no charge for inbound or ingress traffic. You can create a new instance and configure the bandwidth at the same time. During CVM instance creation, you can switch to pay-as-you-go or increase the bandwidth. After creation, you can continue to adjust the configuration settings or change the bandwidth for the CVM instance. After successfully creating and configuring the CVM instance, the next step is to achieve internal and external network access. In other words, we need to ensure that the CVM instance can communicate with the public Internet when it is deployed. In order to allow public Internet access for the instance, Tencent Cloud provides a service to the CVM instance for public data transmission. For private IP access, the Internet access is a local area network service. Only CVMs with public IP addresses can communicate with computers on the Internet. If the bandwidth is greater than 0 Mbps, Tencent Cloud will automatically allocate the public IP, and the user cannot proactively change or release the public IP associated with the instance. To achieve network access on 10 cent cloud via a public IP address. You should obtain the instances public IP address through the console. As shown in the screenshot here, a private IP cannot be accessed from the internet. It can be assigned automatically by 10 cent cloud or customized by users. Different users are isolated from each other and different regions are also isolated from each other to ensure privacy and security. To achieve network access on 10 cent cloud via a private IP address you should view the private IP through the console and operating system and then set up the internet DNS. A security group is a state full packet filtering virtual firewall that can help facilitate network isolation. To configure a security group, you should create a security group assigned the security group to the instance and configure the security group for more efficient CBM instance. Ops and management elastic public IP or EIP is the static IP associated with the account. It can be kept in your account until the elastic public IP is released. The IPs can quickly map the address to another instance in the account to mitigate instance failures to use the EIPs you can apply for the EIP. Change the EIP name and then bind the EIP to whichever CBM instance you want. Of course you can also unbind and release the EIP. If you are no longer using it elastic network interface or E and I binds to CbMS within a private network and can be migrated between multiple CbMS E and I. Is essentially the main network interface that gives you configuration options for main private IP. Secondary private IP, elastic public IP, security group and even Mac address. The applications of elastic network interface include use cases such as private networks, public networks management, network isolation and highly reliable application deployment. To prevent applications from experiencing single points of failure, you can create an E and I and bind it to the CBM which will give you different IPs with multiple instances including backups for recovery. Okay now let's look at adjusting instance configurations. The configuration can be adjusted when the CBM is in the running and shutdown modes. However, adjustments will not take effect until the instance shuts down and restarts instances whose system disks and data disks are both cloud disks support adjusting configurations. Additionally, very few instances will have private IP changes after being adjusted configurations that can only be adjusted when the instance is shut down include instance configuration such as CPU and memory. Size of the mounted cloud disk, changing the instance password and loading keys to change the password of a CBM instance. You must agree to a forced shutdown and verify the change to successfully reset the password to upgrade an instance, you can go into the console, click more, select resource adjustment and adjust configuration. 10 cent cloud offers an unlimited number of upgrades which means that you can always upgrade from a smaler instance size to a larger one. Monthly subscription instances can be downgraded at any time and up to five times in total. The cost difference is converted to the length of time that is added to the new instance configuration pay as you go instances can be downgraded at any time for an unlimited number of times. There are three different ways and instance can be destroyed manual, scheduled and automatic destruction. Manual destruction is when the user terminates the instance, which will then be kept for seven days for monthly subscriptions and two hours for pay as you go. Scheduled destruction is when the user sets scheduled destruction for pay as you go instances while automatic destruction is for instances that are expired or have overdue payments for monthly subscriptions. The instance will be kept for seven days and automatically released if not recovered in time. Pay as you go instances will be automatically released after the balance of the instance is less than zero for more than 26 hours to destroy an instance, manually, you can click terminate, return on the console. You can also destroy instances in batches by checking all of the instances to be destroyed and clicking the terminate button to completely destroy the instance. In the recycle bin you can access the CBM recycle list and destroy it. The instance stays in the recycle bin for seven days after which it is automatically destroyed within the recycle bin, the only available operations are recharge and recover and completely destroy. Now let's look at automatic deployment. We'll start with an overview of automatic deployment before taking a look at the automatic deployment operation process, creating new API keys, installing SDK tool kits and querying and creating instances through APIs. You can access 10 cent cloud resources using APIs to build your own resource management system, automatic API system sales, platform development tools and more. The advantages of cloud API's include the ability to quickly use cloud products and efficiently use cloud product features. Additional advantages include the ability to implement batch processing operation integration, automation and remote calling and support for strong compatibility and low system requirements. The objective of this section is to familiarize yourself with the entire process of automated deployment via APIs and learn how to query and create instances through APIs. The automatic deployment operation process is to create a new API key debug the API, download and install the SdK toolkit and query and create instances through APIs. To create an API key, log into the API key management console and click create key. The cloud API cannot be used directly. It should be used together with the downloaded STK which is a tool kit that allows developers to use 10 cent cloud in their own code more efficiently. The sdK toolkit can be downloaded for the corresponding development language to query the list of instances through APIs. You can configure the script to filter the instances by specific parameters and return the list of instances under the account. Creating instances through a peace requires you to define specific parameters. In this example, the availability zone, billing mode, image ID and Model are all specified for the complete list of APIs and parameters. Please refer to the official CBM documentation.
