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.
-
Go to Beyond Compute Service > Bare Metal Server in the KakaoCloud Console.
-
View the created instances under the Instance menu.
Instance menu
Category Description Name Name of the instance ID Unique instance ID State State of the instance
- For details, refer to Instance lifecycle.Type Server type of the instance Image The operating system installed on the instance Private IP The internal network IP address automatically assigned to the instance Public IP The public IP address directly assigned and accessible by the user AZ Availability zone where the instance is located Created The 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.
-
Go to Beyond Compute Service > Bare Metal Server in the KakaoCloud Console.
-
Click the [More] icon of the instance to manage under the Instance menu.
More features
Category Description Start Activate a stopped instance Stop Temporarily cease the instance Restart Restart the instance after terminating running processes
- Restart may not proceed if processes fail to terminate.Hard reboot Restart the instance after shutting down its power Rename instance Modify the instance's name and description Rebuild instance Reinstall the OS image or reset the key pair Associate public IP Assign a public IP to the instance
- Only available to Project AdminDisassociate public IP Remove the instance's public IP
- Only available to Project AdminUse SSH to connect Access the instance via SSH
- Available for Linux-based instances
- For details, refer to Connect with SSH to Linux instanceDelete instance Permanently remove and return the instance
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.
-
Go to Beyond Compute Service > Bare Metal Server in the KakaoCloud Console.
-
Select the instance in the Instance menu.
-
Check the details of the selected instance by tab.
- Details tab
- Network tab
- Monitoring tab
Category Description Instance name The name of the instance set by the user Instance state For more details, refer to Instance lifecycle. Host name The host name automatically generated in the form of a private IP
- Assigned in the form ofhost-{PRIVATE_IP}
Image The name of the instance's Image Key pair The key pair of the instance Creator The user who created the instance Created at The creation date and time of the instance (time elapsed since creation) Instance ID The unique ID (UUID) of the instance Availability Zone Availability zone where the instance is located Instance type The type of instance selected during creation vCPU The number of CPUs according to the instance type Memory The size of Memory according to the instance type Volume The applied disk capacity of the instance infoAll Bare Metal instances are provisioned within a Virtual Private Cloud (VPC) environment. This configuration provides advanced networking and security features, facilitating the establishment of logically isolated service environments tailored to meet specific networking requirements.
Network
Category Description Network bonding mode Whether to use the network bonding mode Bonding type Type of network bonding VPC The VPC of the instance
- Click the link to move to VPC > Details tabSubnet The subnet of the instance
- Click the link to move to VPC > Subnet tabAvailability Zone Availability zone of the subnet Public IP The public IP of the instance Public DNS The public DNS of the instance
- To be automatically generated.Private IP The private IP of the instance Private DNS The private DNS of the instance The Bare Metal Server offers comprehensive monitoring capabilities through the installation of a monitoring agent. To access detailed monitoring information, you must install the monitoring agent as follows.
-
Move to Beyond Compute Service > Bare Metal Server in the KakaoCloud Console.
-
Select the instance to install the monitoring agent in the Instance menu.
-
Click on [Go to installation guide] displayed in the Monitoring tab.
-
Follow the guide to install the monitoring agent, then configure each metric in the metric explorer tab under Management > Monitoring > Explorer . For more details, refer to Management > Monitoring > How-to Guides > Use Explorer.
-
If log checking is necessary, you can query specific items in the log explorer under Management > Monitoring > Explorer . For more details, refer to Management > Monitoring > How-to Guides > Use Explorer.
-
While a default monitoring dashboard is provided, you can customize dashboards according to your monitoring needs. For more details, refer to Management > Monitoring > How-to Guides > Use Dashboards.
Hard reboot instance
Restarting an instance is akin to rebooting an operating system. This process usually finishes within 10-15 minutes, retaining all prior configurations, including Public DNS, Public and private IP addresses, and data stored on connected volumes. Notably, performing a hard reboot does not initiate a new billing period for the instance.
-
Go to Beyond Compute Service > Bare Metal Server in the KakaoCloud Console.
-
In the Instance menu, select [More] icon > Hard reboot.
Hard reboot instance
-
In the pop-up window, confirm the instance and click the [OK] button.
Delete instance
If an instance is no longer needed, it can be safely deleted.
Upon deletion of instances, they will be completely returned after termination and cannot be recovered.
- Go to Beyond Compute Service > Bare Metal Server in the KakaoCloud Console.
- In the Instance menu, select [More] icon > Delete.
- In the pop-up window, enter the name of the instance and click the [Delete] button.
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.
- Synchronization of KakaoCloud is provided at the IPv4 address
169.254.169.123
.
- RHEL-based
- Debian-based
-
Install the Chrony package.
sudo yum install chrony
-
Open the
/etc/chrony.conf
file and add the following line.server 169.254.169.123 prefer iburst minpoll 4 maxpoll 4
-
Restart the
chronyd
daemon to apply the changes.sudo service chronyd restart
-
Configure Chrony to start at boot using the following command.
sudo chkconfig chronyd on
-
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 to169.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 -
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
-
Install the Chrony package.
sudo apt install chrony
-
Open the
/etc/chrony/chrony.conf
file and add the following line.server 169.254.169.123 prefer iburst minpoll 4 maxpoll 4
-
Restart the
chronyd
daemon to apply the changes.sudo /etc/init.d/chrony restart
-
Check if Chrony is using the IP
169.254.169.123
for time synchronization. Verify that the default time source marked with^*
is set to169.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 -
Verify 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