Skip to main content

Manage instance

To manage instances in Bare Metal Server, follow these guidelines.

View instance list​

You can check the list of running instances and their basic information.

  1. Go to KakaoCloud Console > Beyond Compute Service > Bare Metal Server.

  2. View the created instances under the Instance menu.

    Image Instance menu

    CategoryDescription
    NameName of the instance
    IDUnique instance ID
    StateState of the instance
    - For details, refer to Instance lifecycle.
    TypeServer type of the instance
    ImageThe operating system installed on the instance
    Default private IPPrivate IP address assigned to the instance's default network interface
    Default public IPPublic IP address associated by the user with the instance's default network interface
    AZAvailability zone where the instance is located
    CreatedThe date of the instance was created
    [More]Access additional functions specific to the instance
    - For details, refer to More features.

More features​

You can perform various functions by clicking the [More] icon of the instance.

  1. Go to KakaoCloud Console > Beyond Compute Service > Bare Metal Server.

  2. Click the [More] icon of the instance to manage under the Instance menu.

    CategoryDescription
    StartActivate a stopped instance
    StopTemporarily cease the instance
    RestartRestart the instance after terminating running processes
    - Restart may not proceed if processes fail to terminate.
    Hard rebootRestart the instance after shutting down its power
    DeleteFully terminate and release the instance
    RenameEdit the instance name and description
    RebuildRebuild the instance to reset and reinstall the operating system and key pair
    Attach network InterfaceAttach a secondary network interface to the instance
    Detach network InterfaceDetach a secondary network interface connected to the instance
    Associate public IPAssociate a public IP with the network interface connected to the instance
    - Available to project administrators only
    Disassociate public IPDisassociate the public IP from the network interface connected to the instance
    - Available to project administrators only
    Use SSH to connectAccess the instance via SSH
    - Available for Linux-based instances
    - For details, refer to Connect with SSH to Linux instance
info

When changing the instance state via the command line, please keep the followings in mind:

  • When you shut down the server using the shutdown command in OS, it is set to reboot automatically.
  • To fully shut down the server, please use the KakaoCloud Console instead.

View instance details​

You can check detailed information of the instance by tab.

  1. Go to KakaoCloud Console > Beyond Compute Service > Bare Metal Server.

  2. Select the instance in the Instance menu.

  3. Check the details of the selected instance by tab.

    CategoryDescription
    Instance nameThe name of the instance set by the user
    Instance stateFor more details, refer to Instance lifecycle.
    Host nameThe host name automatically generated in the form of a private IP
    - Assigned in the form of host-{PRIVATE_IP}
    ImageThe name of the instance's Image
    Key pairThe key pair of the instance
    CreatorThe user who created the instance
    Created atThe creation date and time of the instance (time elapsed since creation)
    Instance IDThe unique ID (UUID) of the instance
    Availability ZoneAvailability zone where the instance is located
    Instance typeThe type of instance selected during creation
    vCPUThe number of CPUs according to the instance type
    MemoryThe size of Memory according to the instance type
    VolumeThe applied disk capacity of the instance

Hard reboot instance​

You can force a reboot of an instance.
Rebooting an instance is similar to restarting the operating system. The process typically takes about 10–15 minutes, and existing configurations (such as public DNS, public and private IP addresses, and data in connected volumes) are preserved. However, forcing a reboot does not restart the billing period for the instance.

  1. Go to KakaoCloud Console > Beyond Compute Service > Bare Metal Server.

  2. In the Instance menu, click the [More] icon for the instance to restart and select Hard reboot.

    Image Hard reboot instance

  3. In the popup, confirm the instance and click [OK].

Delete instance​

You can delete instances that are no longer in use.

caution

Deleted instance resources are fully released and cannot be recovered.

  1. Go to KakaoCloud Console > Beyond Compute Service > Bare Metal Server.
  2. In the Instance menu, click the [More] icon for the instance to delete and select Delete instance.
  3. In the popup, enter the instance name and click [Delete].
info
  • When an instance is deleted, associated network interfaces are handled as follows:
    • Network interfaces created as "new interfaces" at instance creation are deleted along with the instance.
    • Network interfaces that were connected as "existing interfaces" during instance creation remain even after the instance is deleted. These interfaces must be deleted separately.

Set time reference​

Consistent and accurate time references are crucial for many server operations and processes. The images provided by KakaoCloud use time synchronization services like Network Time Protocol (NTP), Chrony, and systemd-timesyncd provided by the operating system.

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.

  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 using the following command.

    sudo chkconfig chronyd on

  5. Check if Chrony is using the IP 169.254.169.123 for time synchronization. Also, verify 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. Verify 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