Details Instance

This document explains how to view instance details such as CPU usage, RAM usage, private IP address, gateway, floating IP, reboot instace, and more. Here’s how to view instance details.

Click on an Instance Name

Instance Page

On the instance detail page you will see the details of CPU Usage, RAM Usage, Network In Usage, Network Out Usage, Disk Read, and Disk Write.

Detail Instance - vCPU Usage

Detail Instance - Memory Total

Reboot Instance

To reboot the instance, you can do 2 reboots of which Soft Reboot is used to slowly restart your VM system by stopping all running processes one by one while Hard Reboot is used to force restart the system when your instance is already showing no response.

To get Soft Reboot and Hard Reboot, click the Power menu. Can be seen in the menu section Reboot

Power Page - Reboot Menu

To restart the VM system by stopping all running processes one by one, click the Soft Reboot button, while to restart the VM system by force stopping click the Hard Reboot button.

Reboot Menu- Soft Reboot & Hard Reboot

A confirmation window will appear to do Reboot. Then click Yes.

Reboot Menu - Confirmation Window

There is a Restarting the instance notification that your VM is being restarted.

Restart Process Notification

If your VM is successfully restarted there will be a notification Instance [your-instance name] has been successfully restarted

Restart Successful Notification

Resize Instance

You can change the existing machine type if it doesn’t suit the workload you are running on the VM. You can change the VM machine type to match the amount of vCPU and memory as your workload changes.

Instance Page

In the Action column, click More, then select Resize Instance.

Instance Page - Resize Instance

Select the machine type and adjust the cpu and memory as needed, then click the Resize button.
- General, VM size provides a balanced CPU to memory ratio.
- Compute Optimized, delivers the highest performance CPU on Compute Engine and is optimized for compute intensive workloads.
- Shared, this provides a cost-effective method for running small applications that are not resource intensive.
- Memory Optimized, provides high memory to CPU ratio, optimized for memory-intensive workloads.

vCPU/RAM

Type	Description	vCPU/RAM
Shared	Based on 1 vCPU	1 vCPU/1GB, 1 vCPU/3GB,1 vCPU/4GB
General	CPU:RAM eq 1:2,1:3	2vCPU/4GB, 2vCPU/6GB, 4vCPU/8GB, 4vCPU/12GB, 8vCPU/16GB, 8vCPU/24GB, 16vCPU/32GB, 16vCPU/48GB, 32vCPU/64GB, 32vCPU/96GB
Compute Optimized	CPU:RAM eq 1:1	2vCPU/2GB, 4vCPU/4GB, 8vCPU/8GB, 16vCPU/16GB, 32vCPU/32GB
Memory Optimized	CPU:RAM eq 1:4	2vCPU/8GB, 2vCPU/16GB, 4vCPU/16GB, 4vCPU/32GB, 8vCPU/32GB, 16vCPU/64GB, 32vCPU/128GB

Resize Instance Page

If the data has been successfully changed, there will be a notification “Instance flavor has been successfully changed”.

Resize Instance - Successful Notification

Resize Root Disk

You can increase the disk root size when your VM instance needs additional storage space. You can only resize the root disk to increase its size, you cannot reduce the size of the root disk.

Instance Page

In the Action column, click More, then select Resize Root Disk.

Instance Page - Resize Root Disk

Enter the size of Root Disk as needed, but the root disk cannot be below 20GB. then click Resize Root Disk to save or cancel if you don’t change the size of the root disk.

Instance Page - Increase Root Disk Size

There will be a process of expanding the size of the root disk.

Instance Page - Process Increase Root Disk

New data that has been saved is automatically updated in the Instance list

Instance Page

Attach Interface

On virtual machines in the Cloudka portal service, you can attach or detach VPC interfaces and Ports that are used by the virtual machine manually by specifying the IP address for your Instance to use. To attach a VPC make sure that you have created a VPC for the VPC creation step in sub-section VPC Network. Here are the steps to attach a VPC-based interface used by a virtual machine: