The lifecycle of a Cloud Virtual Machine instance refers to all states from the start of the instance to its release. By managing instances properly from enabling to disabling instances, applications running on instances can provide services efficiently and economically.
Instance State
- The states of an instance are as follows.
| Status Name | Status Attributes | Status Description |
|---|---|---|
| Creating | Intermediate State | After the instance is created, it enters the status before it is running. |
| Running | Steady State | The iThe lifecycle of a Cloud Virtual Machine instance refers to all states from the start of the instance to its release. By managing instances properly from enabling to disabling instances, applications running on instances can provide services efficiently and economically. |
Instance State
- The states of an instance are as follows.
| Status Name | Status Attributes | Status Description |
|---|---|---|
| Creating | Intermediate State | After the instance is created, it enters the status before it is running. |
| Running | Steady State | The instance is running properly. Your business can be run on this instance. |
| Restarting | Intermediate State | The instance enters the state before it is running after being restarted by the console or through the API. If this state is maintained for a long time, exceptions may occur. |
| Resetting | Intermediate State | The instance enters the state before it is running after the reinstall operation or the reset disk operation is performed in the console or through the API. |
| Shutting down | Intermediate State | The instance enters the state before it is shut down after being shut down by the console or through the API. If this state is maintained for a long time, it indicates an exception. Forced shutdown is not recommended. |
| Shut Down | Steady State | The instance is stopped normally. An instance in a shutdown state cannot provide services. Some attributes of the instance can only be modified when the system is shut down. |
| Terminating | Intermediate State | The instance has not been terminated 7 days after its expiration or after the user actively performs the termination. |
| Released | Steady State | The release operation is completed. The instance does not exist, and services are unavailable, and the data is completely cleared. |
Launch an Instance
- The instance enters the creating state after the it is started. The hardware for the instance being created is configured according to the specified instance specifications), and the system starts the instance by using the image specified at the startup.
- The instance enters the running state after it is created. Instances in the running state enable normal connections and access services.
Restart an Instance
It is recommended to choose to restart an instance by using the Converge Cloud console or Converge Cloud API instead of running the restart command of the operating system in the instance.
- The instance enters the restarting state after the restart an instance operation is performed.
- Restarting an instance is equivalent to restarting a computer. After the instance is restarted, it still retains its public IP address, private IP address, and all data on its hard disk.
- Restarting an instance usually takes from tens of seconds to several minutes, depending on the instance configuration.
Shutdown an Instance
Users can use the console or API to shut an instance down.
- Shutting down an instance is equivalent to turning off your computer.
- After the instance is shut down, it will no longer provide services, but the billing will not stop.
- An instance being shut down is still displayed in the console.
- Shutting down an instance is a prerequisite for some configuration operations, such as adjusting hardware configuration and resetting passwords.
- The shutdown operation itself does not change the public network IP address, private IP address of the Cloud Virtual Machine and all the data on its hard disk.
Terminate or Release an Instance
When users no longer needs a Cloud Virtual Machine instance, they can terminate and release the instance. The termination and release can be achieved by using the Converge Cloud console or Converge Cloud API.
- Manual termination: For an instance with no outstanding payments, you can choose to manually terminate it.
- When an instance is terminated, the instance's system disk and the data disk specified at the time of purchase is released, but the elastic cloud disk mounted on it is not affected.
|Restarting|Intermediate State|The instance enters the state before it is running after being restarted by the console or through the API. If this state is maintained for a long time, exceptions may occur.|
|Resetting|Intermediate State|The instance enters the state before it is running after the reinstall operation or the reset disk operation is performed in the console or through the API.|
|Shutting down|Intermediate State|The instance enters the state before it is shut down after being shut down by the console or through the API. If this state is maintained for a long time, it indicates an exception. Forced shutdown is not recommended.|
|Shut Down|Steady State|The instance is stopped normally. An instance in a shutdown state cannot provide services. Some attributes of the instance can only be modified when the system is shut down.|
|Terminating|Intermediate State|The instance has not been terminated 7 days after its expiration or after the user actively performs the termination.|
|Released|Steady State|The release operation is completed. The instance does not exist, and services are unavailable, and the data is completely cleared.|
Launch an Instance
- The instance enters the creating state after the it is started. The hardware for the instance being created is configured according to the specified instance specifications, and the system starts the instance by using the image specified at the startup.
- The instance enters the running state after it is created. Instances in the running state enable normal connections and access services.
Restart an Instance
It is recommended to choose to restart an instance by using the Converge Cloud console or Converge Cloud API instead of running the restart command of the operating system in the instance.
- The instance enters the restarting state after the restart an instance operation is performed.
- Restarting an instance is equivalent to restarting a computer. After the instance is restarted, it still retains its public IP address, private IP address, and all data on its hard disk.
- Restarting an instance usually takes from tens of seconds to several minutes, depending on the instance configuration.
Shutdown an Instance
Users can use the console or API to shut an instance down.
- Shutting down an instance is equivalent to turning off your computer.
- After the instance is shut down, it will no longer provide services, but the billing will not stop.
- An instance being shut down is still displayed in the console.
- Shutting down an instance is a prerequisite for some configuration operations, such as adjusting hardware configuration and resetting passwords.
- The shutdown operation itself does not change the public network IP address, private IP address of the Cloud Virtual Machine and all the data on its hard disk.
Terminate or Release an Instance
When users no longer needs a Cloud Virtual Machine instance, they can terminate and release the instance. The termination and release can be achieved by using the Converge Cloud console or Converge Cloud API.
- Manual termination: For a Pay-As-You-Go instance with no outstanding payments, you can choose to manually terminate it.
- When an instance is terminated, the instance's system disk and the data disk specified at the time of purchase is released, but the elastic cloud disk mounted on it is not affected.