Manage instance

info

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

View instance list

You can check the list of running instances.

1. Go to Beyond Compute Service > GPU in the KakaoCloud Console.

2. In the Instance menu, check the list of currently operating instances.

   Instance list-

   Category	Description
   Instance	User-defined instance name / unique instance ID
   State	State of the instance - For more details, refer to Instance lifecycle.
   Type	Server type of the instance - Hover over to check detailed specs (vCPU, Memory)
   Image	The image installed on the instance
   Private IP	Virtual network IP address automatically assigned to the instance
   Public IP	Public IP address directly assigned and connected by the user
   AZ	Availability zone where the instance is created
   Created	Date the instance was created - Hover over to check detailed units
   More	Provides extra functions - For more details, refer to More features.

More features

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

1. Go to Beyond Compute Service > GPU in the KakaoCloud Console.

2. In the Instance menu, click on the [More] icon to execute.

   More features

   More features	Description	Instance state after execution
   Start	Start the instance - Switches a stopped or terminated instance to Active state	Active
   Stop	Stop the instance	Stopped
   Reboot	Soft reboot the instance	Active
   Hard reboot	Hard reboot the instance	Active
   Terminate	Shelve the instance	Shelved_offloaded
   Rename instance	Edit the instance name and description	-
   Change instance type	Resize the instance type	-
   Modify security group	Set the Security Group for the instance	-
   Associate public IP	Connect a public IP to the instance - Only available for project admins	-
   Disassociate public IP	Disconnect a public IP from the instance - Only available for project admins	-
   Change source/destination checks	Set stopping source/destination checks (allowed_address_pairs)	-
   Use SSH to connect	Guide on connecting to the instance via SSH - Available for instances with Linux-based OS	-
   Use RDP to connect	Guide on connecting to the instance via RDP - Username and password viewed - Available for instances with Windows OS	-
   View system log	Check system logs stored in the instance - Contains data with all records set by the audit system - Unsupported for instances with Windows OS	-
   Create image	Create an image from the instance's root volume - Instance recreated from the backed-up image - Recommended to set instance in stopped, active state	-
   Delete instance	Completely terminate and return the instance	-

tip

Creating an instance image is possible even when the instance is in an active state. For data consistency, however, it is recommended to execute it when the instance is in a stopped state.

View instance details

Check and manage detailed information, network, security, volume, action logs, and monitoring information connected to the instance.

1. Go to Beyond Compute Service > GPU in the KakaoCloud Console.

2. In the Instance menu, select an instance.

3. Check the details of the selected instance.

   Details

   Check detailed information of the instance.

   Details tab

   Category	Description
   Instance name	The name of the instance
   Instance ID	The unique ID of the instance - Icon click to copy available
   Hostname	Hostname automatically generated in Private IP form
   Availability zone	The AZ storing the instance
   Creator	The user who created the instance
   Created	The date and time the instance was created (time elapsed since creation)
   Type	The type of instance selected during creation
   vCPU	The number of vCPUs
   Image	The name of the image of the instance
   Memory	The selected memory size at creation
   Key pair	The key pair of the instance
   Volume	The number of volumes applied to the instance

   Network

   Check the network and IP information of the instance.

   info

   All GPU instances are provided in VPC. VPC offers network and security functions, allowing you to build a logically separated service environment based on your network requirements. For more details, refer to the VPC documentation.

   Category	Description
   VPC	VPC name of the instance
   VPC ID	VPC ID of the instance
   Subnet	Subnet name of the instance
   Subnet ID	Subnet ID of the instance
   Public IP	Public IP of the instance
   Public DNS	Public DNS of the instance - Automatically generated
   Private IP	Private IP of the instance
   Private DNS	Private DNS of the instance

   Security

   Check the security groups and policies applied to the instance.

   Category	Description
   Security group	List of applied security groups
   Policy details	Detailed policies of the applied security groups - Inbound tab: Applied inbound rules of the security group - Outbound tab: Applied outbound rules of the security group

   Volume

   Check the volume information connected to the instance. For more details, refer to Create and manage volume.

   Action Log

   Check the action log of which user executed which command actions.

   Category	Item	Description
   Request ID	-	The unique ID of the request log
   Type	create	Instance creation action
   	delete	Instance deletion action
   	stop	Instance stop action
   	terminate	Instance termination action
   	start	Instance start action
   	reboot	Instance reboot action
   	revertResize	Action to revert instance type change
   	confirmResize	Action to confirm instance type change
   	resize	Action to change instance type
   	attach_interface	Action to connect an interface to the instance
   	detach_interface	Action to detach an interface from the instance
   	attach_volume	Action to connect a volume to the instance
   	detach_volume	Action to detach a volume from the instance
   	detach_interface	Action to detach a volume from the instance
   	createImage	Action to create an image of the instance
   User Name	-	The account ID of the user who executed the action
   Request Date	-	The date and time the action was executed

   Monitoring

   Monitoring allows you to manage this flexibly and work with the resources needed to manage it.
   Instance monitoring is divided into Basic monitoring and Detailed monitoring.

Delete instance

Delete instances that are no longer in use.

caution

Deleted instances are completely returned after termination and cannot be recovered.
Volumes for which you selected the Delete when instance is deleted option when creating an instance will also be deleted.

1. Go to Beyond Compute Service > GPU in the KakaoCloud Console.
2. In the Instance menu, select [More] icon > Delete instance.
3. Enter the name of the instance and click the [Delete] button.

Monitoring

Basic monitoring

Check the results of Basic monitoring.

1. Go to Beyond Compute Service > GPU in the KakaoCloud Console.

2. In the Instance menu, select the instance to check action log information.

3. On the instance's detail page > Monitoring tab, click on the Basic monitoring tab and then check the information.

   Basic monitoring data

   Item	Description
   vCPU Usage (Core)	Total vCPU usage over time
   Disk Read/Write Bytes	Disk (volume) Read, Write usage over time
   Network RX	Network RX usage over time
   Network TX	Network TX usage over time

Detailed monitoring

Check detailed monitoring information after installing the Monitoring agent. The installation method for the monitoring agent for detailed monitoring of GPU instance is as follows.

1. Go to Beyond Compute Service > GPU in the KakaoCloud Console.

2. In the Instance menu, select the instance where you will install the monitoring agent.

3. On the Monitoring tab > Detailed monitoring tab, click on the [installation guide].

4. Follow the guide to install the monitoring agent, then set each item in the metric explorer tab under Management > Monitoring > Explorer . For more details, refer to Management > Monitoring > How-to Guides > Use explorer.

5. If log checking is necessary, query each item in the log explorer under Management > Monitoring > Explorer . For more details, refer to Management > Monitoring > How-to Guides > Use explorer.

6. Although a default dashboard is provided, configure a custom dashboard suitable for your monitoring purposes. For more details, refer to Management > Monitoring > How-to Guides > Use dashboards.

Public IP

Associate public IP

Associate a public IP to an instance.

Permissions

Only Project Admin can associate public IPs.

1. Go to Beyond Compute Service > GPU in the KakaoCloud Console.
2. In the Instance menu, select [More] icon > Associate public IP.
3. Verify the information and click the [OK] button.

Disassociate public IP

Disassociate a public IP.

Permissions Notice

Only Project Admin can disassociate public IPs.

1. Go to Beyond Compute Service > GPU in the KakaoCloud Console.
2. In the Instance menu, select [More] icon > Disassociate public IP.
3. Verify the information and check "Disassociate and delete the public IP".
4. Click the [Disassociate] button.

caution

If a public IP is disconnected but not deleted, the resource is not returned. Even if not used, charges may apply.

Modify security group

Modify a security group.

1. Go to Beyond Compute Service > GPU in the KakaoCloud Console.

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

3. Select a security group to apply to the instance.

   • Using multiple Security Groups applies all their policies to the instance.
   • Check the applied policies per Inbound/Outbound tab.

4. Click the [Save] button.

Set time reference

Consistent and accurate time references are important for many server operations and processes. The images provided by KakaoCloud use time synchronization services such as Network Time Protocol (NTP), Chrony, and systemd-timesyncd, which are provided by the operating system by default. These time synchronization services allow multiple servers to operate based on the same time reference and ensure consistent time references. However, these external services can only be used when the server has internet access.
In a local network environment, you can synchronize time using KakaoCloud's NTP service. For Linux environments, you can use the Chrony client to utilize KakaoCloud's NTP service within the instance.

info

• Synchronization of KakaoCloud is provided at the IPv4 address 169.254.169.123.

RHEL-based

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 Chrony to start at boot with the following command.

   sudo chkconfig chronyd on

5. Verify that Chrony is using the IP 169.254.169.123 for time synchronization. Also, check that the default time source marked with ^* is set to 169.254.169.123.

   $ chronyc sources
   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 Chrony's time synchronization status.

   $ chronyc tracking
   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

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 IP 169.254.169.123 for time synchronization. Check that the default time source marked with ^* is set to 169.254.169.123.

   $ chronyc sources
   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 Chrony's time synchronization status.

   $ chronyc tracking
   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