Manage instance

info

This guide covers GPU and NPU instances.
Video transcoding instances are provided on the Virtual Machine service. For more details, refer to Virtual Machine > Manage instance.

This document explains how to manage instances in the GPU service.

View instance list

You can view, search, and manage the list of running instances and their details.

1. Navigate to the KakaoCloud console > Beyond Compute Service > GPU menu.

2. In the Instance menu, view the list of currently running instances. Click the instance filter to view instances based on specific attributes.
   

   Instance list

   Field	Description
   Name	User-defined instance name
   ID	Unique instance ID
   Status	Current state of the instance - For more details, refer to Instance lifecycle
   Type	Server type of the instance - Hover to view detailed specifications (vCPU, memory)
   Image	Image installed on the instance
   Default private IP	Private IP assigned to the instance's primary network interface
   Default public IP	Public IP linked to the instance's primary network interface by the user
   Availability zone	Availability zone where the instance is created
   Created at	Creation date of the instance - Hover to view specific details
   [More] icon	Execute functions for each field - Refer to More features for details

More features

Click the [More options] icon of an instance to execute various functions.

1. Navigate to the KakaoCloud console > Beyond Compute Service > GPU menu.

2. In the Instance menu, click the [More options] icon of an instance and select the desired function.

   More options icon

   Feature	Description	Resulting status
   Start	Start the instance (transition from Stopped or Shelved_offloaded to Active)	Active
   Stop	Stop the instance	Stopped
   Restart	Soft reboot of the instance	Active
   Force restart	Hard reboot of the instance	Active
   Terminate	Shelve the instance	Shelved_offloaded
   Delete instance	Completely delete and return the instance	-
   Rename instance	Open a popup to modify the instance's name and description	-
   Change instance type	Open a popup to resize the instance	-
   Attach network interface	Attach a secondary network interface to the instance	-
   Detach network interface	Detach a secondary network interface from the instance	-
   Configure security group	Open a popup to set the security group for the instance	-
   Associate public IP	Open a popup to associate a public IP with the instance - Available only for project administrators	-
   Disassociate public IP	Open a popup to disassociate a public IP from the instance - Available only for project administrators	-
   Modify allowed address pairs	Open a popup to configure allowed address pairs - Default: Enabled	-
   SSH connection	Open a popup with instructions for connecting to the instance via SSH - Available for instances with Linux-based operating systems	-
   RDP connection	Open a popup with instructions for connecting to the instance via RDP - Provides username and password details - Available for instances with Windows-based operating systems	-
   View system logs	Open a popup to check system logs stored in the instance - Logs include all system records for auditing - Not supported on instances with Windows-based operating systems	-
   Create image	Open a popup to create an image from the root volume of the instance - Allows creating a new instance from the backup image - Can be performed in Stopped or Active states	-

info

When creating an instance image, it is possible to perform the operation while the instance is in the Active state. However, for data consistency, it is recommended to execute this action when the instance is in the Stopped state.

View instance details

You can view and manage detailed information about the instance, including its network, security, volumes, activity logs, and monitoring data.

1. Navigate to the KakaoCloud console > Beyond Compute Service > GPU menu.

2. In the Instance menu, select the instance you want to view in detail.

3. Check the information on the instance's details page.

   Instance details page

Details

Detailed information about the selected instance can be viewed here.

Field	Description
Instance name	User-defined instance name
Instance ID	Unique ID (UUID) of the instance
Instance status	Current status of the instance
Availability zone	Availability zone where the instance is located
Hostname	Hostname generated automatically in private IP format - Assigned as host-{PRIVATE_IP}
Instance type	Type of instance selected during creation
Image	Image name of the instance
vCPU	Number of CPUs allocated to the instance type
Key pair	Key pair associated with the instance
Memory	Memory size of the instance type
CPU multithreading	Status of CPU multithreading feature
Volume count	Number of volumes attached to the instance
Creator	User who created the instance
Disk size	Total disk size of the instance's volumes
Created at	Creation timestamp of the instance (with elapsed time)

Network

View detailed information about the instance's network and network interfaces.

info

All GPU instances operate in a VPC environment. VPC provides network and security features, enabling the creation of logically isolated service environments based on specific network requirements. For more details, refer to the VPC documentation.

Field	Description
Interface name	Name assigned to the network interface
Interface ID	Unique UUID of the network interface
Connection status	Connection status of the network interface - In Use: Connected to a resource - Available: Not connected to any resource
Private IP	Private IP address assigned to the network interface
Public IP	Public IP address linked to the network interface
Availability zone	Availability zone where the network interface is located
Subnet name	Name of the subnet where the network interface is located
Subnet ID	Unique UUID of the subnet where the network interface is located
[More] icon	- Detach network interface: Detach the selected interface from the instance

Security

Check the security groups and rules applied to the instance. For more details, refer to Modify security group.

Field	Description
Security group	List of security groups applied to the instance - Displays groups applied to each network interface
Rules	Detailed rules of the applied security groups - Inbound tab: Inbound rules of the security group - Outbound tab: Outbound rules of the security group

Volumes

View information about volumes attached to the instance. For details, refer to Manage volumes.

Activity logs

Check activity logs for commands executed on the instance.

Field	Item	Description
Request ID	-	Unique ID of the request log
Type	create	Instance creation action
	delete	Instance deletion action
	stop	Instance stopping action
	shelve	Instance termination action
	start	Instance starting action
	reboot	Instance reboot action
	revertResize	Reverting instance type change
	confirmResize	Confirming instance type change
	resize	Changing instance type
	attach_interface	Attaching a network interface to the instance
	detach_interface	Detaching a network interface from the instance
	attach_volume	Attaching a volume to the instance
	detach_volume	Detaching a volume from the instance
	createImage	Creating an image from the instance
User name	-	Account ID of the user who executed the action
Request timestamp	-	Timestamp of the executed action

Monitoring

Leverage monitoring to manage resources flexibly and efficiently while minimizing necessary management efforts.
Instance monitoring is categorized into Basic monitoring and Detailed monitoring.

Delete instance

You can delete instances that are no longer needed.

caution

Deleted instance resources are permanently returned and cannot be recovered.
Volumes created with the Delete with instance option during instance creation will also be deleted.

1. Navigate to the KakaoCloud console > Beyond Compute Service > GPU menu.
2. In the Instance menu, select the [More options] icon for the instance to delete > Delete instance.
3. In the Delete instance popup, enter the instance name and click the [Delete] button.

info

• When deleting an instance, the connected network interfaces are handled as follows:
  • Network interfaces created as New interface during instance creation are deleted along with the instance.
  • Network interfaces selected as Existing interface during instance creation remain even after instance deletion. These must be deleted separately.

Monitoring

Basic monitoring

You can check the results of basic monitoring.

1. Navigate to the KakaoCloud console > Beyond Compute Service > GPU menu.

2. In the Instance menu, select the instance for which you want to view activity logs.

3. On the instance's details page, go to the Monitoring tab and click the Basic monitoring tab to view the information.

   Field	Description
   ➀ Tab selection	Choose between basic monitoring and detailed monitoring
   ➁ Data duration	Duration of the data displayed on the monitoring graph
   ➂ Refresh	Configure auto-refresh intervals or use manual refresh

   Basic monitoring data

   Metric	Description
   vCPU usage (Core)	Total vCPU usage over time
   Disk read/write bytes	Disk (volume) read and write usage over time
   Network RX	Network RX usage over time
   Network TX	Network TX usage over time

Detailed monitoring

Detailed monitoring information can be viewed after installing the monitoring agent. Follow these steps to install the monitoring agent for GPU instance services.

1. Navigate to the KakaoCloud console > Beyond Compute Service > GPU menu.
2. In the Instance menu, select the instance where you want to install the monitoring agent.
3. On the instance's details page > Monitoring tab, click [Installation guide].
4. Follow the guide to install the monitoring agent, and configure each item in the Metrics Explorer tab under Management > Monitoring > Explorer. For details, refer to Management > Monitoring > How-to Guides > Using the explorer.
5. To check logs, go to Management > Monitoring > Explorer > Log Explorer and view the relevant items. For details, refer to Management > Monitoring > How-to Guides > Using the explorer > Search logs.
6. The monitoring dashboard provides a default configuration but can be customized to meet specific monitoring requirements. For details, refer to Management > Monitoring > How-to Guides > Using dashboards.

Public IP

Associate public IP

You can associate a public IP with an instance.

Permission

Only users with project administrator privileges can associate public IPs.

1. Navigate to the KakaoCloud console > Beyond Compute Service > GPU menu.
2. In the Instance menu, select the [More options] icon for the instance > Associate public IP.
3. In the Associate public IP popup, select the network interface and private IP address, then click the [Confirm] button.

Disassociate public IP

You can disassociate a connected public IP from an instance.

Permission

Only users with project administrator privileges can disassociate public IPs.

1. Navigate to the KakaoCloud console > Beyond Compute Service > GPU menu.
2. In the Instance menu, select the [More options] icon for the instance > Disassociate public IP.
3. In the Disassociate public IP popup, select the network interface and public IP to disconnect, and check "Disassociate the public IP from the instance and automatically delete it.".
4. Click the [Disassociate] button.

caution

If the public IP is only disassociated and not deleted, it will not be returned. Even if unused, charges will apply.

Modify security group

You can modify the security groups connected to the network interface of an instance. One or more security groups are set by default on the primary network interface.

1. Navigate to the KakaoCloud console > Beyond Compute Service > GPU menu.

2. In the Instance menu, select the [More options] icon for the instance > Modify security group.

3. In the Modify security group popup, select the security groups to apply to the instance.

   • Applying multiple security groups will enforce all rules from each group on the instance.
   • Applied rules can be viewed in the Inbound/Outbound tabs.

4. Click the [Save] button.

Network interface

Attach network interface

You can attach a network interface to an instance.

Permission

• As of 2024, multiple network interfaces are not supported.

1. Navigate to the KakaoCloud console > Beyond Compute Service > GPU menu.

2. In the Instance menu, select the [More options] icon for the instance > Attach network interface.

3. In the Attach network interface popup, review the information and select the network interface to attach.

4. Click the [Confirm] button.

Detach network interface

You can detach a secondary network interface from an instance.

Permission

• Primary network interfaces cannot be detached.

1. Navigate to the KakaoCloud console > Beyond Compute Service > GPU menu.

2. In the Instance menu, select the [More options] icon for the instance > Detach network interface.

3. In the Detach network interface popup, review the information and select the network interface to detach.

4. Click the [Confirm] button.

Set time reference

Consistent and accurate time references are critical for many server tasks and processes. Images provided by KakaoCloud utilize time synchronization services such as Network Time Protocol (NTP), Chrony, and systemd-timesyncd by default. These services ensure that servers operate on the same time standard, enabling consistent time references. However, these external services require internet access.

In local network environments, KakaoCloud provides an NTP service for time synchronization. For Linux-based operating systems, the Chrony client can be used within an instance to sync time with KakaoCloud's NTP service.

info

• KakaoCloud's synchronization service is provided at the IPv4 address 169.254.169.123.

RHEL-based systems

1. Install the Chrony package.

   sudo yum install chrony

2. Open the /etc/chrony.conf file and add the following line:

   server 169.254.169.123 prefer iburst minpoll 4 maxpoll 4

3. Restart the chronyd daemon to apply the changes.

   sudo service chronyd restart

4. Configure the system to start chronyd automatically at boot.

   sudo chkconfig chronyd on

5. Verify that Chrony is using the 169.254.169.123 IP address for time synchronization. Ensure the default time source is set to ^* 169.254.169.123.

   Verify time synchronization

   chronyc sources
   Output

   MS Name/IP address         Stratum Poll Reach LastRx Last sample
   ===============================================================================
   ^- 193.123.243.2                 2   6    17     9  -8932us[-8909us] +/- 4550us
   ^- ec2-13-209-84-50.ap-nort>     2   6    17     9  -8534us[-8512us] +/- 5038us
   ^* 169.254.169.123               2   4    17     9    +11us[  +34us] +/-   39ms

6. Check the status of time synchronization.

   Check synchronization status

   chronyc tracking
   Output

   Reference ID    : A9FEA97B (169.254.169.123)
   Stratum         : 3
   Ref time (UTC)  : Wed Jun 28 08:14:40 2023
   System time     : 0.000019450 seconds fast of NTP time
   Last offset     : +0.000022669 seconds
   RMS offset      : 0.000022669 seconds
   Frequency       : 1.352 ppm slow
   Residual freq   : +2.810 ppm
   Skew            : 0.061 ppm
   Root delay      : 0.076084495 seconds
   Root dispersion : 0.000831026 seconds
   Update interval : 2.0 seconds
   Leap status     : Normal

Debian-based systems

1. Install the Chrony package.

   sudo apt install chrony

2. Open the /etc/chrony/chrony.conf file and add the following line:

   server 169.254.169.123 prefer iburst minpoll 4 maxpoll 4

3. Restart the chronyd daemon to apply the changes.

   sudo /etc/init.d/chrony restart

4. Verify that Chrony is using the 169.254.169.123 IP address for time synchronization. Ensure the default time source is set to ^* 169.254.169.123.

   chronyc sources
   Output

   MS Name/IP address         Stratum Poll Reach LastRx Last sample
   ===============================================================================
   ^* 169.254.169.123               2   4    37     4    +41us[ +189us] +/-   39ms
   ^- pugot.canonical.com           2   6    17    18  -8895us[-8864us] +/-  162ms
   ^- prod-ntp-3.ntp1.ps5.cano>     2   6    17    18  -3232us[-3203us] +/-  125ms
   ^- prod-ntp-5.ntp1.ps5.cano>     2   6    17    19  -1723us[-1707us] +/-  123ms
   ^- alphyn.canonical.com          2   6    17    18  -2344us[-2321us] +/-  140ms
   ^- 121.174.142.82                3   6    17    19  -9870us[-9853us] +/-   28ms
   ^- ntp-seoul.gombadi.com         2   6    17    20  -8532us[-8519us] +/-   52ms
   ^- send.mx.cdnetworks.com        2   6    17    18  -8997us[-8971us] +/-   29ms
   ^- 193.123.243.2                 2   6    17    19  -9014us[-8994us] +/- 4132us

5. Check the status of time synchronization.

   chronyc tracking
   Output

   Reference ID    : A9FEA97B (169.254.169.123)
   Stratum         : 3
   Ref time (UTC)  : Wed Jun 28 08:25:52 2023
   System time     : 0.000156159 seconds slow of NTP time
   Last offset     : -0.000184961 seconds
   RMS offset      : 0.000184961 seconds
   Frequency       : 5.999 ppm fast
   Residual freq   : -0.600 ppm
   Skew            : 35.807 ppm
   Root delay      : 0.076914668 seconds
   Root dispersion : 0.000669460 seconds
   Update interval : 16.2 seconds
   Leap status     : Normal