Skip to main content

Manage instance

The following describes how to manage instances in the Bare Metal Server service.

View instance list and basic information​

View the list of running instances and their basic information.

  1. Go to Compute > Beyond Compute Service > Bare Metal Server in the KakaoCloud console.

  2. In the Instance menu, check the currently created instances.

    Image Instance menu

    CategoryDescription
    NameUser-defined name of the instance
    IDUnique ID (UUID) of the instance
    StatusStatus of the instance
    - For more information about status values, see Instance lifecycle
    TypeServer type of the instance
    ImageImage installed on the instance
    Primary private IPPrivate IP address assigned to the primary network interface of the instance
    Primary public IPPublic IP address connected by the user to the primary network interface of the instance
    Availability zoneAvailability zone where the instance is located
    Created atCreation date and time of the instance

Run and manage instance​

Click the [⋮] button on the right side of the instance list to run various features.

  1. Go to Compute > Beyond Compute Service > Bare Metal Server in the KakaoCloud console.

  2. In the Instance menu, select the [⋮] button for the instance you want to manage.

    Image Instance more

    CategoryDescription
    StartStart a stopped instance to the Active state
    StopTemporarily stop using the instance
    - Charges continue
    RebootRestart the instance after terminating running processes
    - Restart may fail if processes do not terminate properly
    Hard rebootRestart the instance after powering it off
    DeleteCompletely terminate and release the instance
    Edit informationModify the instance name and description
    Rebuild instanceRebuild the instance to reset and reinstall the operating system and key pair
    Connect public IPConnect a public IP to a network interface attached to the instance
    - Available only to project administrators
    Disconnect public IPDisconnect the public IP applied to a network interface attached to the instance
    - Available only to project administrators
    Connect to instanceConnect to the instance through SSH
    - Available only for instances with a Linux-based operating system installed
    - For more information, see Connect to linux instance with ssh
info

The following precautions apply when changing the instance status through the command line.

  • If you shut down the server from the operating system using the Shutdown command, it is configured to reboot automatically.
  • To shut down the server, use the console.

View instance details​

View detailed information such as instance details, networks attached to the instance, and monitoring.

  1. Go to Compute > Beyond Compute Service > Bare Metal Server in the KakaoCloud console.

  2. In the Instance menu, select the instance for which you want to view detailed information.

  3. Check the information on the instance details page.

    CategoryDescription
    NameUser-defined instance name
    IDUnique ID (UUID) of the instance
    DescriptionDescription of the instance
    StatusCurrent status of the instance
    Availability zoneAvailability zone where the instance is located
    Host nameHost name automatically generated in private IP format
    - Host name assigned in the host-{PRIVATE_IP} format
    Instance typeInstance type selected when creating the instance
    ImageImage name of the instance
    vCPUNumber of CPUs according to the instance type
    MemoryMemory size according to the instance type
    VolumeDisk capacity applied to the instance
    Key pairKey pair of the instance
    Creator UUIDUser who created the instance
    Created atCreation date and time of the instance (elapsed time since creation)

Hard reboot instance​

You can force restart the instance.
Restarting an instance is the same as rebooting the operating system. Rebooting an instance takes about 10 to 15 minutes on average, and the existing settings, such as public DNS, public and private IP addresses, and data on attached volumes, are retained. However, force restarting an instance does not start a new billing period for the instance.

  1. Go to Compute > Beyond Compute Service > Bare Metal Server in the KakaoCloud console.

  2. In the Instance menu, select [⋮] for the instance to restart > Hard reboot.

    Image Hard reboot instance

  3. In the Hard reboot instance pop-up window, check the instance and click the [Confirm] button.

Delete instance​

Delete an instance that is no longer in use.

caution

Deleted instance resources are fully released after termination and cannot be recovered.

  1. Go to Compute > Beyond Compute Service > Bare Metal Server in the KakaoCloud console.
  2. In the Instance menu, select [⋮] for the instance to delete > Delete instance.
  3. In the pop-up window, enter the confirmation text, then click the [Delete] button.

Set time reference​

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

info
  • The KakaoCloud synchronization service is provided through the IPv4 address 169.254.169.123.
  • VPCs created before February 21, 2024 do not provide an NTP service endpoint, and this will be migrated gradually.

  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 and apply the changes.

    sudo service chronyd restart

  4. Use the following command to configure chronyd to start whenever the system boots.

    sudo chkconfig chronyd on

  5. Check whether Chrony synchronizes time using the IP 169.254.169.123. Also check whether the default time source marked with ^* is set to 169.254.169.123.

    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 time synchronization status of Chrony.

    Check time 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