Compute

• 1: Virtual Server
• 1.1: Overview
• 1.1.1: Server type
• 1.1.2: Monitoring Metrics
• 1.1.3: ServiceWatch Metrics
• 1.2: How-to guides
• 1.2.1: Image
• 1.2.2: Keypair
• 1.2.3: Server Group
• 1.2.4: Change IP
• 1.2.5: Configure Linux NTP
• 1.2.6: Configure RHEL Repo and WKMS
• 1.2.7: Install ServiceWatch Agent
• 1.3: API Reference
• 1.4: CLI Reference
• 1.5: Release Note
• 2: Virtual Server Auto-Scaling
• 2.1: Overview
• 2.1.1: Monitoring Metrics
• 2.1.2: ServiceWatch Metrics
• 2.2: How-to guides
• 2.2.1: Launch Configuration
• 2.2.2: Manage Policy
• 2.2.3: Manage Schedule
• 2.2.4: Manage Notification
• 2.3: API Reference
• 2.4: CLI Reference
• 2.5: Release Note
• 3: GPU Server
• 3.1: Overview
• 3.1.1: Server type
• 3.1.2: Monitoring Metrics
• 3.1.3: ServiceWatch Metrics
• 3.2: How-to guides
• 3.2.1: Manage Image
• 3.2.2: Manage Keypair
• 3.2.3: Use Multi-instance GPU on GPU Server
• 3.2.4: Use NVSwitch on GPU Server
• 3.2.5: Install ServiceWatch Agent
• 3.3: API Reference
• 3.4: CLI Reference
• 3.5: Release Note
• 4: Bare Metal Server
• 4.1: Overview
• 4.1.1: Server type
• 4.1.2: Monitoring Metrics
• 4.2: How-to guides
• 4.2.1: Install ServiceWatch Agent
• 4.2.2: Setting up RHEL Repo and WKMS
• 4.3: API Reference
• 4.4: CLI Reference
• 4.5: Release Note
• 5: Multi-node GPU Cluster
• 5.1: Overview
• 5.1.1: Server type
• 5.1.2: Monitoring Metrics
• 5.2: How-to guides
• 5.2.1: Cluster Fabric Management
• 5.2.2: Install ServiceWatch Agent
• 5.2.3: Multi-node GPU Cluster Service Scope and Inspection Guide
• 5.3: Release Note
• 6: Cloud Functions
• 6.1: Overview
• 6.1.1: ServiceWatch Metrics
• 6.2: How-to guides
• 6.2.1: Configure Trigger
• 6.2.2: Blueprint Detailed Guide
• 6.2.3: Integrate PrivateLink Service
• 6.2.4: Resource-based Policy Guide
• 6.3: API Reference
• 6.4: CLI Reference
• 6.5: Release Note
• 7: Virtual Server DR
• 7.1: Overview
• 7.2: Release Note
• 8: Block Storage
• 8.1: Overview
• 8.1.1: Monitoring Metrics
• 8.1.2: ServiceWatch metric
• 8.2: How-to guides
• 8.2.1: Connect to Server
• 8.2.2: Using Snapshots
• 8.2.3: Transfer volume
• 8.3: API Reference
• 8.4: CLI Reference
• 8.5: Release Note

1 - Virtual Server

1.1 - Overview

Service Overview

Virtual Server is a virtual server optimized for cloud computing that lets you freely allocate and use infrastructure resources provided by the server—such as CPU and memory—without having to purchase them individually, and you can allocate as much as you need, when you need it. In a cloud environment, you can use resources with optimized performance according to the user’s computing purposes such as development, testing, and application execution.

Features

• Easy and convenient computing environment setup: Through a web-based Console, users can easily use Self Service from Virtual Server provisioning to resource management and cost management. * When using a Virtual Server, if you need to change the capacity of major resources such as CPU or Memory, you can easily scale up or down without operator intervention.

• Various Service Types Offered: Provides virtualized vCore/Memory resources based on predefined server types (1~128 vCore).

  • General Virtual Server: Provides commonly used computing specs (up to 16vCore, 256GB)
  • Large-capacity Virtual Server: Provided when resources larger than the standard Virtual Server spec are required.

• Strong Security Implementation: Through the Security Group service, control inbound/outbound traffic communicating with the external Internet or other VPC(Virtual Private Cloud) to securely protect the server. * Additionally, real-time monitoring enables stable operation of computing resources.

Service architecture diagram

Provided features

Virtual Server provides the following features.

• Auto Provisioning and Management: Provides Virtual Server provisioning, resource management, and cost management functions through a web-based console. * If you need to change the capacity of major resources such as CPU or Memory while using a Virtual Server, you can modify it immediately using the server type edit function.
• Standard Server Type and Image Provision: Provides virtualized vCore/Memory resources according to the standard server type, and supplies a standard OS Image.
• Storage Connection: Provides additional attached storage besides the OS disk. * Block Storage, File Storage, Object Storage can be additionally connected and used.
• Network Connection: You can connect the Virtual Server’s standard subnet/IP settings and Public NAT IP. * Provides a local subnet connection for inter-server communication. * This task can be edited on the detail page.
• Security Group Application: Through the Security Group service, control inbound/outbound traffic communicating with external internet or other VPCs to securely protect the server.
• Monitoring: You can view monitoring information for computing resources such as CPU, Memory, and Disk through the Cloud Monitoring service.
• Backup and Recovery: You can back up and recover Virtual Server Image using the Backup service.
• Cost Management: You can create, stop, or terminate servers as needed, and because billing is based on actual usage time, you can verify costs according to usage.
• ServiceWatch Service Integration: You can monitor data using the ServiceWatch service.

Components

Virtual Server provides standard server types and standard OS images. Users can select and use it according to the desired service scale.

Image

You can create and manage images. The main features are as follows.

• Image creation: You can create an Image from the configuration of the Virtual Server you are using, and you can create an Image by uploading your Image file to Object Storage.
• Create Shared Image: You can create an Image with Visibility set to Private as a Shared Image that can be shared.
• Share with another Account: You can share the Image with another Account.
• For instructions on creating and using images, see the How-to guides > Image document.

Keypair

To ensure a more secure OS login, we strengthen security by providing a Key Pair instead of the ID/Password entry method. The main features are as follows.

• Keypair creation: Creates a user credential for connecting to the Virtual Server.
• Retrieve Public Key: You can retrieve the public key by loading a file or by manually entering the public key. Keypair 생성 및 활용 방법은 How-to guides > Keypair문서를 참고하세요.

Server Group {#server-group}

Server Group 설정을 통해 Virtual Server 및 Virtual Server 생성 시 추가한 Block Storage를 랙(Rack) 및 호스트에 근접 또는 분산 배치 가능합니다. 주요 기능은 다음과 같습니다.

Server Group 생성: 동일 Server Group에 소속된 Virtual Server를 Anti-Affinity(분산배치), Affinity(근접배치), Partition(Virtual Server와 Block Storage 분산배치)로 설정할 수 있습니다.

• For how to create and use Server Groups, please refer to the How-to guides > Server Group document.

OS Image version provided

The OS images provided by Virtual Server are as follows.

Server type

The server types supported by Virtual Server are as follows. For detailed information about server types, see Virtual Server 서버 타입.

Standard s1v2m4

Constraints

Preceding Service

This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.

1.1.1 - Server type

Virtual Server server type

Virtual Server provides server types according to the intended use. Server types are composed of various combinations such as CPU, Memory, and Network Bandwidth. When creating a Virtual Server, the host server used for the Virtual Server is determined by the selected server type. Please select the server type according to the specifications of the application you want to run on the Virtual Server.

The server types supported by Virtual Server are as follows.

Standard s1v2m4

s1 server type

The s1 server type of Virtual Server is provided with standard specifications (vCPU, Memory) and is suitable for various applications.

• Samsung Cloud Platform v2’s first generation: Intel 3rd‑generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
• Supports up to 16 vCPUs and 256 GB of memory
• Maximum networking speed of 12.5 Gbps

s2 server type

The Virtual Server s2 server type is offered with standard specifications (vCPU, Memory) and is suitable for various applications.

• Second generation of Samsung Cloud Platform v2: Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H processor up to 3.2 GHz
• Supports up to 16 vCPUs and 256 GB of memory
• Maximum networking speed of 12.5 Gbps

s3 server type

The Virtual Server s3 server type is offered with standard specifications (vCPU, Memory) and is suitable for various applications.

• Samsung Cloud Platform v2’s 3rd generation: Intel 6th‑generation (Granite Rapids) Xeon 6737P Processor up to 4.0 GHz
• Supports up to 16 vCPUs and 256 GB of memory
• Maximum networking speed of 12.5 Gbps

h2 Server Type

The h2 server type of Virtual Server is offered with high-capacity server specifications and is suitable for applications that require large-scale data processing.

• Second generation of Samsung Cloud Platform v2: Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H processor up to 3.2 GHz
• Supports up to 128 vCPUs and 1,536 GB of memory
• Maximum networking speed of 25 Gbps

h3 Server Type

The h3 server type of Virtual Server is offered with high-capacity specifications and is suitable for applications that require large-scale data processing.

• Samsung Cloud Platform v2’s 3rd generation: Intel 6th‑generation (Granite Rapids) Xeon 6738P Processor up to 4.1 GHz
• Supports up to 128 vCPUs and 1,536 GB of memory
• Maximum networking speed of 25G bps

1.1.2 - Monitoring Metrics

Virtual Server Monitoring Metrics

The table below shows the monitoring metrics of Virtual Server that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.

Provides basic monitoring metrics even without installing an agent, as shown below table. Please check the Virtual Server monitoring metrics (default). Additionally, the metrics that can be viewed by installing the Agent are in the table below. Virtual Server additional monitoring metrics (Agent installation required)** Please refer to it.

For Windows OS, memory-related metrics can only be viewed after installing the Agent.

1.1.3 - ServiceWatch Metrics

Virtual Server sends metrics to ServiceWatch. The metrics provided by default monitoring are data collected at 5‑minute intervals. If detailed monitoring is enabled, you can view data collected at 1‑minute intervals.

See How-to guides > ServiceWatch Enable Detailed Monitoring for instructions on enabling detailed monitoring of Virtual Server.

Basic Metrics

The following are the basic metrics for the Virtual Server namespace.

The indicators whose names are displayed in bold below are the indicators selected as key metrics among the default metrics provided by Virtual Server. The key metrics are used to build service dashboards that are automatically generated for each service in ServiceWatch. They can also be viewed on the Monitoring tab of the Virtual Server detail page.

Each metric provides guidance in the user guide on which statistical value is meaningful to query, and among the meaningful statistics, the values shown in bold text are the primary statistics. In the service dashboard or monitoring tab, you can view primary metrics using these primary statistics.

1.2 - How-to guides

Users can create the service by entering the required Virtual Server information and selecting detailed options through the Samsung Cloud Platform Console.

Create Virtual Server

You can create and use the Virtual Server service in the Samsung Cloud Platform Console.

To create a Virtual Server, follow these steps.

1. All Services > Compute > Virtual Server menu, click it. 1. Navigate to the Service Home page of the Virtual Server.

2. On the Service Home page, click the Create Virtual Server button. 2. Create Virtual Server page.

3. On the Virtual Server Creation page, enter the information required to create the service and select detailed options.

   • Select the required information in the Image and version selection area.

     Category	Required	Detailed description
     Image	Essential	Select the type of Image provided Standard: Samsung Cloud Platform standard Image Alma Linux, Oracle Linux, RHEL, Rocky Linux, Ubuntu, Windows Custom: User-created Image Kubernetes: Kubernetes Image RHEL, Ubuntu Marketplace: Image subscribed from Marketplace
     Image version	Essential	Select version of the chosen Image Provide version list of the provided server Image

     Table. Virtual Server Image and version selection input items
   • Enter or select the required information in the Service Information Input area.

     Category	Required	Detailed description
     Number of servers	Essential	Number of servers to create simultaneously Only numeric input is allowed, enter a value between 1~100
     Service Type > Server Type	Essential	Virtual Server 서버 타입 Standard: standard specifications commonly used High Capacity: large-capacity server specifications beyond Standard For detailed information about the server types provided by Virtual Server, see Virtual Server 서버 타입
     Service Type > Planned Compute	Essential	Status of resources with Planned Compute set In Use: Number of resources with Planned Compute that are currently in use Configured: Number of resources with Planned Compute set Coverage Preview: Amount applied per resource by Planned Compute Apply for Planned Compute Service: Go to the Planned Compute service creation page For more details, refer to Planned Compute 신청하기
     Block Storage	Essential	Block Storage settings used by the server according to purpose Basic OS: The area where the OS is installed and used Enter the size in Units; the minimum size varies depending on the OS Image type Alma Linux: Enter a value between 2 and 1,536 Oracle Linux: Enter a value between 7 and 1,536 RHEL: Enter a value between 2 and 1,536 Rocky Linux: Enter a value between 2 and 1,536 Ubuntu: Enter a value between 2 and 1,536 Windows: Enter a value between 4 and 1,536 SSD: High‑performance general volume HDD: General volume SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management Service) encryption keys Encryption can only be applied at initial creation and cannot be changed afterward Using the SSD_KMS disk type may cause performance degradation SSD_Provisioned: SSD volume with configurable IOPS and Throughput Additional: Use when additional user space beyond the OS area is needed After selecting Use, enter the storage type and size Click the + button to add storage, or the x button to delete (up to 25 can be added) Enter the size in Units, with a value between 1 and 1,536 Since 1 Unit equals 8 GB, this creates 8 – 12,288 GB SSD: High‑performance general volume HDD: General volume SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management Service) encryption keys Encryption can only be applied at initial creation and cannot be changed afterward Using the SSD_KMS disk type may result in performance degradation SSD/HDD_MultiAttach: Volume that can be attached to two or more servers SSD_Provisioned: SSD volume with configurable IOPS and Throughput For details on each Block Storage type, see Block Storage 생성하기 Delete on termination: When Delete on Termination is selected, the volume is terminated together with the server Volumes with snapshots are not deleted even when Delete on termination is enabled A multi‑attach volume can be deleted only when the server being removed is the last remaining server attached to the volume Max IOPS: Enter a maximum IOPS value between 5,000 and 20,000 Cannot be set for disk types HDD, HDD_KMS, or HDD_MultiAttach Max Throughput: Enter a maximum Throughput value between 250 and 1,000 Cannot be set for disk types HDD, HDD_KMS, or HDD_MultiAttach
     Server Group	Selection	After selecting Use to set Anti-Affinity (distributed placement), Affinity (proximate placement), Partition (distributed placement of Virtual Server and Block Storage) for servers belonging to the same Server Group , select the Server Group , choose Create New to create a Server Group
     Place servers belonging to the same Server Group according to the selected policy using a Best Effort method
     The policy is selected from Anti-Affinity (distributed placement), Affinity (proximate placement), or Partition (distributed placement of Virtual Server and Block Storage)

     Table. Virtual Server service information input items
     Caution

     When using the Partition (distributed placement of Virtual Server and Block Storage) policy among Server Group policies, you cannot allocate additional Block Storage Volumes after creating a Virtual Server, so create all required Block Storage during the Virtual Server creation stage.
   • Required Information Input area, please enter or select the necessary information.

     Category	Required	Detailed description
     Server name	Essential	Enter a name to distinguish the server when the selected number of servers is 1 Set the hostname to the entered server name Enter using English letters, numbers, spaces, and special characters (-, _) within 63 characters
     Network Settings > Create New Network Port	Essential	Set the network where the Virtual Server will be installed VPC name: Select a pre‑created VPC General Subnet: Select a pre‑created general Subnet IP can be auto‑generated or manually entered, and if Enter is selected, the user can input the IP directly NAT: Available only when there is a single server and the VPC is attached to an Internet Gateway. Checking Use allows selection of a NAT IP NAT IP: Select a NAT IP If no NAT IP is available to select, click the Create New button to generate a Public IP Refresh button: Click to view and select the created Public IP Creating a Public IP incurs charges according to the Public IP pricing policy Local Subnet (optional): Select Use for the local Subnet It is not a required element for creating the service A pre‑created local Subnet must be selected IP can be auto‑generated or manually entered, and selecting Enter allows the user to input the IP directly
     Network Settings > Specify Existing Network Port	Essential	Set the network where the Virtual Server will be installed VPC: Select a pre-created VPC General Subnet: Select a pre-created General Subnet and Port NAT: Available only when there is a single server and the VPC has an Internet Gateway attached. When selected, you can choose a NAT IP NAT IP: Select the NAT IP If there is no NAT IP to select, click the Create New button to generate a Public IP Refresh button to view and select the created Public IP Local Subnet (optional): Select Use for the local subnet Select a pre-created local Subnet and Port
     Security Group	Selection	Settings required to connect to the server Select: Up to 5 pre‑created Security Groups can be selected Create New: If there is no applicable Security Group, create one separately in the Security Group service If a Security Group is not set, all connections are blocked, so you must configure it to allow the necessary connections
     Keypair	Essential	User authentication method to use when connecting to the server New creation: Create a new one if a new Keypair is required Refer to Keypair 생성하기 Default login account list by OS Alma Linux: almalinux Oracle Linux: cloud-user RHEL: cloud-user Rocky Linux: rocky Ubuntu: ubuntu Windows: sysadmin

     Table. Virtual Server required information input fields

     Reference

     • The default OS account can serve as the default user account in a cloud environment and can be used for initial configuration via cloud-init and SCP-related functions.
     • If you delete or change the primary account, related Samsung Cloud Platform functions may not work properly, so deletion or modification is not recommended.
   • Additional Information Input area, enter or select the required information.

     Category	Required	Detailed description
     Lock	Selection	Lock usage setting When you use Lock, it prevents actions such as terminating, starting, or stopping the server, thereby avoiding malfunctions caused by mistakes
     Init script	Selection	Script executed when the server starts The init script must be written as a Batch script for Windows, a Shell script for Linux, or cloud‑init, depending on the image type. Up to 45,000 bytes can be entered
     tag	Selection	Add Tag Up to 50 can be added per resource After clicking the Add Tag button, input or select Key, Value values

     Table. Virtual Server additional information input fields

4. Summary Verify the detailed information and estimated charges generated in the panel, then click the Create button.

5. When the popup indicating creation opens, click the Confirm button.

   • When creation is complete, verify the created resources on the Virtual Server List page.

View Virtual Server Details

The Virtual Server service lets you view and modify the complete resource list and detailed information. The Virtual Server Details page consists of Details, Monitoring, Tags, Activity History tabs.

To view detailed information about the Virtual Server service, follow these steps.

1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to view detailed information. 3. Navigate to the Virtual Server Details page.
   • Virtual Server Details page displays status information and additional feature information, and consists of Details, Monitoring, Tags, Activity Log tabs.
   • For detailed information about Virtual Server Additional Features, please refer to Virtual Server 관리 부가 기능.

     Category	Detailed description
     Virtual Server status	State of a user-created Virtual Server Build: State where a Build command has been issued Building: Build in progress Networking: Server creation process in progress Scheduling: Server creation process in progress Block_Device_Mapping: Connecting Block Storage during server creation Spawning: State where the server creation process is ongoing Active: Available state Powering_off: State when a stop request is made Deleting: Server deletion in progress Reboot_Started: Reboot in progress state Error: Error state Migrating: State where the server is migrating to another host Reboot: State where a Reboot command has been issued Rebooting: Reboot in progress Rebuild: State where a Rebuild command has been issued Rebuilding: State when a Rebuild request is made Rebuild_Spawning: State where the Rebuild process is ongoing Resize: State where a Resize command has been issued Resizing: Resize in progress Resize_Prep: State when a server type modification is requested Resize_Migrating: State where the server is moving to another host while resizing Resize_Migrated: State where the server has completed moving to another host during resize Resize_Finish: Resize completed Revert_Resize: Resize or migration of the server failed for some reason. The target server is cleaned up and the original source server is restarted Shutoff: State when powering off is completed Verity_ Resize: State after Resize_Prep is performed following a server type modification request, where the server type is finalized or can be reverted Resize_Reverting: State when a server type revert request is made Resize_Confirming: State where the server’s Resize request is being confirmed
     Server control	Button to change server status Start: Start a stopped server Stop: Stop a running server Restart: Restart a running server
     Image generation	Create a user Image from the current server’s Image For detailed Image creation instructions, refer to Image 생성하기
     Console log	Current server console log view You can view the console logs output by the current server. For more details, refer to 콘솔 로그 확인하기
     Create dump	Create a dump of the current server The dump file is created inside the Virtual Server For detailed dump creation instructions, see Dump 생성하기
     Rebuild	The OS area data and settings of the existing Virtual Server are deleted, and it is rebuilt as a new server For more details, refer to Rebuild 수행하기
     Service cancellation	Cancel service button

     Table. Virtual Server status information and additional features

Detailed Information

On the Virtual Server List page, you can view detailed information of the selected resource and, if needed, modify the information.

Monitoring

On the Virtual Server List page, you can monitor the ServiceWatch metrics of the selected resources. In the Monitoring tab, you can view monitoring charts for the Virtual Server, and each chart is based on the available Service Watch metrics.

Tag

On the Virtual Server List page, you can view the tag information of the selected resource, and you can add, modify, or delete it.

Job History

On the Virtual Server List page, you can view the operation history of the selected resource.

Control Virtual Server Operation

If you need to control the operation of a created Virtual Server resource, you can perform the task from the Virtual Server List or Virtual Server Details page. You can start, stop, and restart a running server.

Virtual Server Getting Started

You can start a Virtual Server that is shut off. To start the Virtual Server, follow the steps below.

1. Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
3. Virtual Server List page, click the resource to start among the stopped (Shutoff) servers, and navigate to the Virtual Server Details page.
   • On the Virtual Server List page, you can Start each resource using the right More button.
   • After selecting multiple servers with checkboxes, you can control multiple servers simultaneously via the Start button at the top.
4. On the Virtual Server Details page, click the Start button at the top to start the server. 4. Check the status of the changed server in the Status Indicator item.
   • When the Virtual Server start is complete, the server status changes from Shutoff to Active.
   • For detailed information about the Virtual Server status, please refer to Virtual Server 상세 정보 확인하기.

Stop Virtual Server

You can stop a Virtual Server that is running (Active). To stop the Virtual Server, follow these steps.

1. All Services > Compute > Virtual Server Click the menu. 1. Go to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Virtual Server List Navigate to the page.
3. Virtual Server List page, click the resource to stop among the servers that are active, and navigate to the Virtual Server Details page.
   • On the Virtual Server List page, you can Stop each resource using the right More button.
   • After selecting multiple servers with checkboxes, you can control multiple servers simultaneously using the Stop button at the top.
4. On the Virtual Server Details page, click the Stop button at the top to start the server. 4. Check the status of the changed server in the Status Indicator item.
   • When the Virtual Server shutdown is complete, the server status changes from Active to Shutoff.
   • For detailed information about the Virtual Server status, please refer to Virtual Server 상세 정보 확인하기.

Restart Virtual Server

You can restart the created Virtual Server. To restart the Virtual Server, follow these steps.

1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
3. Virtual Server List page, click the resource to restart, and navigate to the Virtual Server Details page.
   • Virtual Server List page allows you to restart each resource via the right More button.
   • After selecting multiple servers with checkboxes, you can control multiple servers simultaneously via the Restart button at the top.
4. On the Virtual Server Details page, click the Restart button at the top to start the server. 4. Check the status of the changed server in the Status Indicator item.
   • During a Virtual Server restart, the server status passes through Rebooting and finally changes to Active.
   • For detailed information about the Virtual Server status, please refer to Virtual Server 상세 정보 확인하기.

Managing Virtual Server Resources

If you need server control and management functions for the created Virtual Server resources, you can perform tasks from the Virtual Server List or Virtual Server Details page.

Create Image

You can create an image of a running Virtual Server.

To create a Virtual Server Image, follow the steps below.

1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.

2. On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.

3. On the Virtual Server List page, click the resource to create an Image. 3. Navigate to the Virtual Server Details page.

4. On the Virtual Server Details page, click the Create Image button. 4. Go to the Image creation page.

   • Enter the required information in the Service Information Input area.

     Category	Required	Detailed description
     Image name	Essential	the name of the Image to be created Enter within 200 characters using English letters, numbers, spaces, and special characters(-, _)

     Table. Image service information input items

5. Check the input information and click the Done button.

   • Once creation is complete, check the created resource on the All Services > Compute > Virtual Server > Image List page.

Edit server type

You can modify the server type of a Virtual Server.

To modify the server type of a Virtual Server, follow these steps.

1. All Services > Compute > Virtual Server Click the menu. 1. Go to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to control its operation. 3. Navigate to the Virtual Server Details page.
4. On the Virtual Server Details page, check the server status and click the server type Edit button. 4. Edit Server Type popup window opens.
5. Edit Server Type In the popup window, after changing the server type, click the Confirm button.
   • If you modify the Virtual Server’s server type, the Virtual Server status changes to a state related to performing a resize.
   • For detailed information about the Virtual Server status, please refer to Virtual Server 상세 정보 확인하기.

Change IP

Please refer to IP 변경하기 for instructions on changing the IP.

Enable detailed monitoring for ServiceWatch

By default, Virtual Server is linked with ServiceWatch for basic monitoring. You can enable detailed monitoring as needed to identify operational issues more quickly and take action. For detailed information about ServiceWatch, refer to the ServiceWatch 개요.

To enable detailed ServiceWatch monitoring for a Virtual Server, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Navigate to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to enable detailed ServiceWatch monitoring. 3. Navigate to the Virtual Server Details page.
4. Click the Edit button for ServiceWatch detailed monitoring on the Virtual Server Details page. 4. ServiceWatch Detailed Monitoring Edit Navigate to the popup window.
5. ServiceWatch Detailed Monitoring Edit In the popup window, after selecting Enable, review the instructions and click the Confirm button.
6. On the Virtual Server Details page, view the detailed ServiceWatch monitoring items.

Disable detailed monitoring for ServiceWatch

To disable detailed ServiceWatch monitoring of a Virtual Server, follow these steps.

1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Navigate to the Virtual Server List page.
3. Virtual Server list on the page, click the resource to disable ServiceWatch detailed monitoring. 3. Navigate to the Virtual Server Details page.
4. On the Virtual Server Details page, click the Edit button for ServiceWatch detailed monitoring. 4. ServiceWatch Detailed Monitoring Edit Navigate to the popup window.
5. ServiceWatch Detailed Monitoring Edit In the popup window, after deselecting Enable, review the guidance message and click the Confirm button.
6. On the Virtual Server Details page, check the ServiceWatch detailed monitoring items.

Virtual Server management add‑on features

For Virtual Server management, you can view console logs, generate dumps, and perform rebuilds. To view the console log, generate a dump, and rebuild a Virtual Server, follow these steps.

Check console log

You can view the current console log of the Virtual Server.

To view the console log of a Virtual Server, follow these steps.

1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
3. Virtual Server List On the page, click the resource to view the console log. 3. Navigate to the Virtual Server Details page.
4. Virtual Server Details on the page, click the Console Log button. 4. Console Log navigates to the popup window.
5. Console Log Check the console log output in the popup window.

Create Dump

To create a Dump file of the Virtual Server, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Navigate to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to view detailed information. 3. Navigate to the Virtual Server Details page.
4. Click the Create Dump button on the Virtual Server Details page.
   • The dump file is created inside the Virtual Server.

Execute Rebuild

You can delete the OS data and configuration of the existing Virtual Server and rebuild it on a new server.

To perform a Rebuild of a Virtual Server, follow these steps.

1. All Services > Compute > Virtual Server Click the menu. 1. Go to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to perform Rebuild. 3. Navigate to the Virtual Server Details page.
4. On the Virtual Server Details page, click the Rebuild button.
   • During a Virtual Server Rebuild, the server status changes to Rebuilding, and when the Rebuild is complete, it returns to its pre‑Rebuild state.
   • For detailed information about the Virtual Server status, please refer to Virtual Server 상세 정보 확인하기.

Terminate Virtual Server

If you terminate an unused Virtual Server, you can reduce operating costs. However, if you terminate a Virtual Server, the running service may be stopped immediately, so you should proceed with the termination only after fully considering the impact of service interruption.

To cancel a Virtual Server, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Virtual Server List page is accessed.
3. On the Virtual Server List page, select the resource to terminate, and click the Terminate Service button.
   • The termination of attached storage depends on the Delete on termination setting; see 해지 제약 사항.
4. If the termination is complete, check on the Virtual Server list page whether the resource has been terminated.

Termination constraints

When a Virtual Server termination request cannot be processed, a popup window will provide guidance. Please refer to the case below.

Termination of attached storage varies depending on the Delete on termination setting; please refer to it.

1.2.1 - Image

Users can create the service by entering the required information for the Image service within the Virtual Server service and selecting detailed options through the Samsung Cloud Platform Console.

Create Image

You can create and use the Image service while using the Virtual Server service in the Samsung Cloud Platform Console.

To create an Image, follow the steps below.

1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.

2. On the Service Home page, click the Image menu. 2. Go to the Image list page.

3. Click the Create Image button on the Image List page. 3. Navigate to the Image creation page.

   • Enter or select the required information in the Service Information Input area.

     Category	required status	Detailed description
     Image name	Required	the name of the Image to create Enter within 255 characters using English letters, numbers, spaces, and special characters(-, _)
     Image file > URL	Required	After uploading an image file to Object Storage, enter the URL The URL can be copied on the Object Storage Details page The bucket in Object Storage where the image file is uploaded must exist in the same zone as the server to be created Image files can only be in the .qcow2 format You must upload a secure image file to minimize security risks.
     OS type	Required	OS type of the uploaded Image file Select from Alma Linux, CentOS, Oracle Linux, RHEL, Rocky Linux, Ubuntu
     Minimum disk	Required	Minimum disk capacity (GB) of the Image to be created 0~12,288GB, please enter a value
     Minimum RAM	Required	Minimum RAM size (GB) of the Image to be created 0~2,097,151GB Enter a value
     Visibility	Required	Display access permissions for the Image Private: Only usable within the account Shared: Can be shared across accounts
     Protected	Selection	Select whether Image deletion is prohibited If you check Use, it prevents accidental deletion of the Image This setting cannot be changed after the Image is created

     Table. Image service information input items
   • Additional Information Input in this area, enter or select the required information.

     Category	required status	Detailed description
     tag	Selection	Add Tag Up to 50 per resource can be added After clicking the Add Tag button, enter or select Key, Value values

     Table. Image additional information input fields

4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Create button.

   • When creation is complete, check the created resources on the Image List page.

Check Image detailed information

The Image service allows you to view and edit the full resource list and detailed information. Image Details page consists of Details, Tags, Activity Log tabs.

To view detailed information of the Image service, follow the steps below.

1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Image menu. 2. Go to the Image list page.
3. On the Image list page, click the resource to view detailed information. 3. Navigate to the Image Details page.
   • Image Details page displays status information and additional feature information, and consists of Details, Tags, Activity Log tabs.

     Category	Detailed description
     Image status	Status of the Image created by the user Active: Available state Queued: When an Image creation request is made, the Image is uploaded and is pending processing Importing: When an Image creation request is made, the Image is uploaded and is being processed
     Create shared Image	Create an Image to share with another Account Creation is possible only when the Image’s Visibility is private and the Image contains snapshot information Creation is not allowed if the OS disk size is 500 GB or larger For more details, refer to 공유용 Image 생성하기
     Share with another account	Image can be shared with another Account If the Image’s Visibility is Shared, it can be shared with another Account Create shared Image or displayed only on Images created by uploading a qcow2 file
     Delete Image	Delete Image button Deleting the Image cannot be undone

     Table. Image status information and additional functions

Detailed Information

On the Image list page, you can view detailed information of the selected resource and edit the information if needed.

Tag

Image List page allows you to view the tag information of the selected resource, and to add, modify, or delete it.

Job History

You can view the operation history of the selected resource on the Image list page.

Image resource management

Describes the control and management functions of the generated Image.

Create shared Image

Create an Image to share with another Account.

To create a shared Image, follow the steps below.

1. Log in to the account to be shared and click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Image menu. 2. Go to the Image list page.
3. On the Image List page, click the Image to create a shared Image. 3. Navigate to the Image Details page.
4. Click the Create Image for Sharing button. 4. A popup window opens to notify the creation of a shared Image.
5. After reviewing the notification content, click the Complete button.

Share Image to another Account

Create an Image to share with another Account.

To share an Image with another Account, follow these steps.

1. Log in to the account to be shared and click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.

2. On the Service Home page, click the Image menu. 2. Go to the Image list page.

3. Image List page, click the Image you want to share with another Account. 3. Go to the Image Details page.

4. Share to another Account Click the button. 4. A popup window notifying image sharing opens.

5. After reviewing the notification content, click the Confirm button. 5. Go to the Share Image with another Account page.

6. Share Image with another Account on the page, enter Share Account ID, and click the Complete button. 6. A popup window notifying image sharing opens.

   Category	required status	Detailed description
   Image name	-	Name of the Image to share Input not allowed
   Image ID	-	Image ID to share Input not allowed
   Shared Account ID	Required	Enter another Account ID to share English letters, numbers, and special characters- using them, enter within 64 characters

   Table. Image sharing items to another account

7. After reviewing the notification content, click the Confirm button. 7. You can check the information from the sharing status on the Image Details page.

   • When the request is first made, the status is Pending, and when the receiving Account approves it, it changes to Accepted; if the approval is denied, it changes to Rejected.

Receive an Image shared from another Account

To receive an Image shared from another Account, follow these steps.

1. Log in to the account to be shared and click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.

2. On the Service Home page, click the Image menu. 2. Go to the Image list page.

3. On the Image List page, click the More > Image Share Request List button. 3. Image sharing request list The popup window opens.

4. Image Sharing Request List In the popup window, click the Approve or Reject button for the Image to be shared.

   Category	Detailed description
   Image name	Name of shared Image
   OS type	OS type of shared Image
   Owner Account ID	Owner Account ID of the shared Image
   Creation date and time	Creation time of shared Image
   Approval	Approve the shared image
   Reject	Reject the shared image

   Table. Image sharing request list item

5. After reviewing the notification content, click the Confirm button. 5. You can view the shared Image from the Image list.

Delete Image

You can delete unused Image. However, since an Image cannot be recovered once deleted, you should fully consider the impact before proceeding with the deletion.

To delete the Image, follow these steps.

1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Image menu. 2. Go to the Image list page.
3. On the Image list page, select the resource to delete, and click the Delete button.
   • On the Image List page, select multiple Image check boxes and click the Delete button at the top of the resource list.
4. After the deletion is complete, verify on the Image List page that the resource has been removed.

1.2.2 - Keypair

Users can create the service by entering the required information for the Keypair within the Virtual Server service and selecting detailed options through the Samsung Cloud Platform Console.

Creating a Keypair

In the Samsung Cloud Platform Console, you can create and use the Keypair service while using the Virtual Server service.

To create a keypair, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.

2. On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.

3. On the Keypair List page, click the Create Keypair button. You will be taken to the Create Keypair page.

   • Enter the required information in the Service Information Input area.

     Category	Required status	Detailed description
     Keypair name	Required	Name of the Keypair to create Enter within 255 characters using English letters, numbers, spaces, and special characters(-, _)
     Keypair type	Required	ssh

     Table. Keypair service information input fields
   • In the Additional Information Input area, enter or select the required information.

     Category	Required	Detailed description
     tag	Selection	Add Tag Up to 50 can be added per resource After clicking the Add Tag button, enter or select Key, Value values

     Table. Keypair additional information input fields

4. Check the input information and click the Create button.

   • After creation is complete, check the created resources on the Keypair list page.

View detailed information of the Keypair

The Keypair service allows you to view and edit the full list of resources and detailed information. On the Keypair Details page, it consists of Details, Tags, Activity Log tabs.

To view detailed information about a keypair, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.
3. On the Keypair List page, click the resource to view detailed information. You will be taken to the Keypair Details page.
   • Keypair Details page displays status information and additional feature information, and consists of Details, Tags, Activity Log tabs.

Detailed Information

On the Keypair List page, you can view detailed information of the selected resource and edit the information if needed.

tag

On the Keypair List page, you can view the tag information of the selected resource and add, modify, or delete it.

Job History

On the Keypair list page, you can view the operation history of the selected resource.

Keypair Resource Management

Describes the control and management functions of a keypair.

Get public key

To retrieve the public key, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Go to the Service Home page of Virtual Server.

2. On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.

3. On the Keypair List page, click the More button at the top and then click the Import Public Key button. You will be taken to the Import Public Key page.

   • Required Information Input area, please enter or select the required information.

     Category	Required	Detailed description
     Keypair name	Required	Keypair name to create
     Keypair type	Required	ssh
     public key	Required	Public Key Input Load File: Select the Attach File button to attach the public key file Only files with the .pem extension can be attached Public Key Input: Paste the copied public key value Keypair Details page allows copying the public key value

     Table. Required input fields for retrieving the public key

4. Review the entered information and click the Complete button.

   • When creation is complete, check the created resource on the Keypair list page.

Delete Keypair

You can delete unused Keypairs. However, once a Keypair is deleted it cannot be recovered, so please review the impact thoroughly beforehand before proceeding with deletion.

To delete a keypair, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Go to the Service Home page of Virtual Server.
2. On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.
3. On the Keypair List page, select the resource to delete, and click the Delete button.
   • On the Keypair List page, select multiple Keypair check boxes and click the Delete button at the top of the resource list.
4. After the deletion is complete, verify on the Keypair List page that the resource has been deleted.

1.2.3 - Server Group

Users can create the service by entering the required information for a Server Group within the Virtual Server service and selecting detailed options through the Samsung Cloud Platform Console.

Create Server Group

In the Samsung Cloud Platform Console, you can create and use the Server Group service while using the Virtual Server service.

To create a Server Group, follow the steps below.

1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.

2. On the Server Group page, click the Server Group menu. 2. Navigate to the Server Group List page.

3. On the Server Group List page, click the Create Server Group button. 3. Server Group creation navigate to the page.

   • Enter or select the required information in the Service Information Input area.

     Category	required status	Detailed description
     Server Group name	Required	Enter the name of the Server Group to be created using English letters, numbers, spaces, and special characters (-, _) within 255 characters
     Policy	Required	Select the placement policy for Virtual Servers belonging to the same Server Group Anti-Affinity(Distributed placement): A policy that places servers belonging to a Server Group on different racks and hosts as much as possible Affinity(Proximity placement): A policy that places servers belonging to a Server Group close together within the same rack and host as much as possible Partition(Virtual Server and Block Storage distributed placement): A policy that places Virtual Servers and their associated Block Storage from a Server Group into different distribution units (Partitions) Up to three distributions are possible, and the setting can be applied when the number of possible distributions is two or more to ensure resource availability Display the Partition number alongside to clearly indicate which Partition each Virtual Server and its associated Block Storage belong to Partition numbers are assigned based on the Partition Size (up to 3) configured for the Server Group

     Table. Server Group Service Information Input Items

     Reference

     • Virtual Servers that belong to the same Server Group are placed on a Best Effort basis according to policy, but this is not strictly guaranteed.
   • Enter or select the required information in the Additional Information Input area.

     Category	required status	Detailed description
     tag	Selection	Add Tag Up to 50 per resource can be added After clicking the Add Tag button, input or select Key, Value values

     Table. Server Group additional information input items

4. Check the input information and click the Generate button.

5. When the popup notifying creation opens, click the Confirm button.

   • When creation is complete, check the created resources on the Server Group List page.

Check Server Group detailed information

The Server Group service lets you view and modify the complete resource list and detailed information. Server Group Details page consists of Details, Tags, Activity Log tabs.

To view detailed information about the Server Group, follow the steps below.

1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Server Group menu. 2. Go to the Server Group List page.
3. On the Server Group list page, click the resource to view detailed information. 3. Navigate to the Server Group Details page.
   • The Server Group Details page displays status information and additional feature information, and consists of Details, Tags, Operation History tabs.

Detailed Information

Server Group List page allows you to view detailed information of the selected resource and, if necessary, edit the information.

Tag

Server Group list page lets you view the tag information of the selected resource, and add, modify, or delete it.

Job History

Server Group List page allows you to view the operation history of the selected resource.

Delete Server Group

You can delete unused Server Groups. However, since a Server Group cannot be recovered once deleted, please review the impact thoroughly in advance before proceeding with deletion.

To delete a Server Group, follow these steps.

1. All Services > Compute > Virtual Server menu, click. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Server Group menu. 2. Go to the Server Group List page.
3. On the Server Group List page, select the resource to delete, and click the Delete button.
   • On the Server Group List page, select multiple Server Group check boxes, and click the Delete button at the top of the resource list.
4. After deletion is complete, check on the Server Group List page whether the resource has been deleted.

1.2.4 - Change IP

You can change the Virtual Server’s IP and add a network port to the Virtual Server to configure the IP.

Change IP

You can change the IP of the Virtual Server.

To change the IP, follow these steps.

1. All Services > Compute > Virtual Server Click the menu. 1. Go to the Service Home page of the Virtual Server.
2. Click the Virtual Server menu on the Service Home page. 2. Go to the Virtual Server List page.
3. On the Virtual Server list page, click the resource whose IP you want to change. 3. Virtual Server Details navigate to the page.
4. On the Virtual Server Details page, click the Edit button for the IP entry you want to change. 4. IP edit The popup window opens.
5. Edit IP in the popup window, after selecting Subnet, enter the IP to change.
6. When the setup is complete, click the Confirm button.
7. When the popup notifying IP modification opens, click the Confirm button.

Configure IP on the server after adding a network port

If you create a Virtual Server with Ubuntu Linux, after adding a network port in Samsung Cloud Platform, you also need to configure the IP on the server.

1. As the root user on the Virtual Server’s OS, use the ip command to verify the assigned network interface name.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   ip a

   ip a

   • If an added interface is present, the following result is displayed.
   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   [root@scp-test-vm-01 ~] # ip a
   3: ens7: <BROADCAST,MULTICAST> mtu 9000 qdisc noop state DOWN group default qlen 1000
       link/ether fa:16:3e:98:b6:64 brd ff:ff:ff:ff:ff:ff
       altname enp0s7

   [root@scp-test-vm-01 ~] # ip a
   3: ens7: <BROADCAST,MULTICAST> mtu 9000 qdisc noop state DOWN group default qlen 1000
       link/ether fa:16:3e:98:b6:64 brd ff:ff:ff:ff:ff:ff
       altname enp0s7

2. Open the /etc/netplan/50-cloud-init.yaml file using a text editor (e.g., vim).

3. Add the following content to the /etc/netplan/50-cloud-init.yaml file and save it.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   network:
   version: 2
   ethernets:
   ens7:
   match:
   macaddress: "fa:16:3e:98:b6:64"
         dhcp4: true
         set-name: "ens7"
         mtu: 9000

   network:
   version: 2
   ethernets:
   ens7:
   match:
   macaddress: "fa:16:3e:98:b6:64"
         dhcp4: true
         set-name: "ens7"
         mtu: 9000

3. Use the netplan command to set an IP on the added network DEVICE.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   netplan --debug apply

   netplan --debug apply

4. Use the ip command to verify that the IP is set correctly.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   [root@scp-test-vm-01 ~] # ip a
   3: ens7: <BROADCAST,MULTICAST> mtu 9000 qdisc noop state DOWN group default qlen 1000
       link/ether fa:16:3e:98:b6:64 brd ff:ff:ff:ff:ff:ff
       altname enp0s7
       inet 10.10.10.10/24 metric 100 brd 10.10.10.255 scope global dynamic ens7
          valid_lft 43197sec preferred_lft 43197sec
       inet6 fe80::f816:3eff:fe0a:96bf/64 scope link
          valid_lft forever preferred_lft forever

   [root@scp-test-vm-01 ~] # ip a
   3: ens7: <BROADCAST,MULTICAST> mtu 9000 qdisc noop state DOWN group default qlen 1000
       link/ether fa:16:3e:98:b6:64 brd ff:ff:ff:ff:ff:ff
       altname enp0s7
       inet 10.10.10.10/24 metric 100 brd 10.10.10.255 scope global dynamic ens7
          valid_lft 43197sec preferred_lft 43197sec
       inet6 fe80::f816:3eff:fe0a:96bf/64 scope link
          valid_lft forever preferred_lft forever

1.2.5 - Configure Linux NTP

Users who create a Virtual Server with Rocky Linux or Oracle Linux via the Samsung Cloud Platform Console need additional configuration for time synchronization (NTP:Network Time Protocol). For other standard Linux images (RHEL, Alma Linux, Ubuntu), NTP is already configured, so no extra setup is required.

Installing NTP Daemon

You can configure NTP by installing the chrony daemon. To install the chrony daemon, follow the steps below.

1. Check whether the chrony package is installed by using the dnf command as the root user on the OS of the Virtual Server.

   Sample Code Download

   Copy Code

   Color mode

   dnf list chrony

   dnf list chrony

   • If the chrony package is installed, the following result is displayed.

[root@scp-test-vm-01 ~] # dnf list chrony
Last metadata expiration check: 1:47:29 ago on Wed 19 Feb 2025 05:55:57 PM KST.
Installed Packages
chrony.x86_64                              3.5-1.0.1.el8                                              @anaconda

[root@scp-test-vm-01 ~] # dnf list chrony
Last metadata expiration check: 1:47:29 ago on Wed 19 Feb 2025 05:55:57 PM KST.
Installed Packages
chrony.x86_64                              3.5-1.0.1.el8                                              @anaconda

2. If the chrony package is not installed, install the chrony package using the dnf command.
   Sample Code Download

   Copy Code

   Color mode

   dnf install chrony -y

   dnf install chrony -y

Configuring NTP Daemon

To configure the chrony daemon, follow these steps.

1. Open the /etc/chrony.conf file using a text editor (e.g., vim).
2. Add the following content to the /etc/chrony.conf file and save it.

server 198.19.0.54 iburst

server 198.19.0.54 iburst

3. Use the systemctl command to configure the chrony daemon to start automatically.

systemctl enable chronyd

systemctl enable chronyd

4. Restart the chrony daemon using the systemctl command.

   Sample Code Download

   Copy Code

   Color mode

   systemctl restart chronyd

   systemctl restart chronyd

5. Run the chronyc sources command with the “v” option (display detailed information) to check the IP address of the configured NTP server and verify whether synchronization is in progress.

   Sample Code Download

   Copy Code

   Color mode

   chronyc sources -v

   chronyc sources -v

   • When you run the chronyc sources command, the following result is displayed.

[root@scp-test-vm-01 ~] # chronyc sources -v

210 Number of sources = 1



  .-- Source mode   '^' = server,   '=' = peer,   '#' = local clock.

 / .- Source state     '*' = current synced,   '+' = combined ,   '-' = not combined,

| /    '?' = unreachable,   'x' = time may be in error,   '~' = time too variable.

|| .- xxxx [ yyyy ] +/- zzzz

||                      Reachability register (octal) -.                        |  xxxx = adjusted offset,

||                      Log2(Polling interval) --.          |                    |  yyyy = measured offset,

||                                                     ＼        |                   |  zzzz = estimated error.

||                                                        |       |                   ＼

MS Name/IP address                  Stratum   Poll   Reach   LastRx   Last    sample

=========================================================================

^* 198.19.0.54                                 2      6     377      52      -129us[  -128us] +/-     14ms

[root@scp-test-vm-01 ~] # chronyc sources -v

210 Number of sources = 1



  .-- Source mode   '^' = server,   '=' = peer,   '#' = local clock.

 / .- Source state     '*' = current synced,   '+' = combined ,   '-' = not combined,

| /    '?' = unreachable,   'x' = time may be in error,   '~' = time too variable.

|| .- xxxx [ yyyy ] +/- zzzz

||                      Reachability register (octal) -.                        |  xxxx = adjusted offset,

||                      Log2(Polling interval) --.          |                    |  yyyy = measured offset,

||                                                     ＼        |                   |  zzzz = estimated error.

||                                                        |       |                   ＼

MS Name/IP address                  Stratum   Poll   Reach   LastRx   Last    sample

=========================================================================

^* 198.19.0.54                                 2      6     377      52      -129us[  -128us] +/-     14ms

6. Run the chronyc tracking command to check the synchronization metrics.
   Sample Code Download

   Copy Code

   Color mode

   [root@scp-test-vm-01 ~] # chronyc tracking
   Reference ID        : A9FEA9FE (198.19.0.54)
   Stratum              : 3
   Ref time  (UTC)     : Wed  Feb  19  18:48:41  2025
   System time         : 0.000000039 seconds fast of NTP time
   Last offset            : -0.000084246 seconds
   RMS offset           : 0.000084246 seconds
   Frequency            : 21.667 ppm slow
   Residual freq        : +4.723 ppm
   Skew                  : 0.410 ppm
   Root delay           : 0.000564836 seconds
   Root dispersion     : 0.027399288 seconds
   Update interval      : 2.0 seconds
   Leap status           : Normal

   [root@scp-test-vm-01 ~] # chronyc tracking
   Reference ID        : A9FEA9FE (198.19.0.54)
   Stratum              : 3
   Ref time  (UTC)     : Wed  Feb  19  18:48:41  2025
   System time         : 0.000000039 seconds fast of NTP time
   Last offset            : -0.000084246 seconds
   RMS offset           : 0.000084246 seconds
   Frequency            : 21.667 ppm slow
   Residual freq        : +4.723 ppm
   Skew                  : 0.410 ppm
   Root delay           : 0.000564836 seconds
   Root dispersion     : 0.027399288 seconds
   Update interval      : 2.0 seconds
   Leap status           : Normal

1.2.6 - Configure RHEL Repo and WKMS

RHEL Repository Configuration Guide

In Samsung Cloud Platform, when using RHEL, you can install and download the same packages as the official RHEL Repository by using the RHEL Repository provided by SCP.
SCP provides the latest repository for the given major version by default. To configure the RHEL repository, follow the steps below.

1. As the root user on the Virtual Server, use the cat command to verify the /etc/yum.repos.d/scp.rhel8.repo or /etc/yum.repos.d/scp.rhel9.repo settings.

   Sample Code Download

   Copy Code

   Color mode

   cat /etc/yum.repos.d/scp.rhel8.repo

   cat /etc/yum.repos.d/scp.rhel8.repo

   Sample Code Download

   Copy Code

   Color mode

   cat /etc/yum.repos.d/scp.rhel9.repo

   cat /etc/yum.repos.d/scp.rhel9.repo

   • When checking the configuration file, the following result is displayed.
     Sample Code Download

     Copy Code

     Color mode

     [rhel-8-baseos]
     name=rhel-8-baseos
     gpgcheck=0
     enabled=1
     baseurl=http://scp-rhel8-ip/rhel/8/baseos
     [rhel-8-baseos-debug]
     name=rhel-8-baseos-debug
     gpgcheck=0
     enabled=1
     baseurl=http://scp-rhel8-ip/rhel/8/baseos-debug
     [rhel-8-appstream]
     name=rhel-8-appstream
     gpgcheck=0
     enabled=1
     baseurl=http://scp-rhel8-ip/rhel/8/appstream

     [rhel-8-baseos]
     name=rhel-8-baseos
     gpgcheck=0
     enabled=1
     baseurl=http://scp-rhel8-ip/rhel/8/baseos
     [rhel-8-baseos-debug]
     name=rhel-8-baseos-debug
     gpgcheck=0
     enabled=1
     baseurl=http://scp-rhel8-ip/rhel/8/baseos-debug
     [rhel-8-appstream]
     name=rhel-8-appstream
     gpgcheck=0
     enabled=1
     baseurl=http://scp-rhel8-ip/rhel/8/appstream

     Sample Code Download

     Copy Code

     Color mode

     [rhel-9-for-x86_64-baseos-rpms]
     name=rhel-9-for-x86_64-baseos-rpms
     baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/baseos
     gpgcheck=0
     enabled=1
     [rhel-9-for-x86_64-appstream-rpms]
     name=rhel-9-for-x86_64-appstream-rpms
     baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/appstream
     gpgcheck=0
     enabled=1
     [codeready-builder-for-rhel-9-x86_64-rpms]
     name=codeready-builder-for-rhel-9-x86_64-rpms
     baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/codeready-builder
     gpgcheck=0
     enabled=1
     [rhel-9-for-x86_64-highavailability-rpms]
     name=rhel-9-for-x86_64-highavailability-rpms
     baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/ha
     gpgcheck=0
     enabled=1
     [rhel-9-for-x86_64-supplementary-rpms]
     name=rhel-9-for-x86_64-supplementary-rpms
     baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/supplementary
     gpgcheck=0
     enabled=1

     [rhel-9-for-x86_64-baseos-rpms]
     name=rhel-9-for-x86_64-baseos-rpms
     baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/baseos
     gpgcheck=0
     enabled=1
     [rhel-9-for-x86_64-appstream-rpms]
     name=rhel-9-for-x86_64-appstream-rpms
     baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/appstream
     gpgcheck=0
     enabled=1
     [codeready-builder-for-rhel-9-x86_64-rpms]
     name=codeready-builder-for-rhel-9-x86_64-rpms
     baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/codeready-builder
     gpgcheck=0
     enabled=1
     [rhel-9-for-x86_64-highavailability-rpms]
     name=rhel-9-for-x86_64-highavailability-rpms
     baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/ha
     gpgcheck=0
     enabled=1
     [rhel-9-for-x86_64-supplementary-rpms]
     name=rhel-9-for-x86_64-supplementary-rpms
     baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/supplementary
     gpgcheck=0
     enabled=1

2. Use a text editor (e.g., vim) to open the /etc/hosts file.

3. Modify the /etc/hosts file with the following content and save it.

   Sample Code Download

   Copy Code

   Color mode

   198.19.2.13 scp-rhel8-ip scp-rhel9-ip scp-rhel-ip

   198.19.2.13 scp-rhel8-ip scp-rhel9-ip scp-rhel-ip

4. Use the yum command to verify the RHEL repository connection configured on the server.

   Sample Code Download

   Copy Code

   Color mode

   yum repolist –v

   yum repolist –v

   • If the RHEL repository is successfully connected, you can view the repository list.
     Sample Code Download

     Copy Code

     Color mode

     Repo-id            : rhel-8-appstream
     Repo-name          : rhel-8-appstream
     Repo-revision      : 1718903734
     Repo-updated       : Fri 21 Jun 2024 02:15:34 AM KST
     Repo-pkgs          : 38,260
     Repo-available-pkgs: 25,799
     Repo-size          : 122 G
     Repo-baseurl       : http://scp-rhel8-ip/rhel/8/appstream
     Repo-expire        : 172,800 second(s) (last: Thu 08 Aug 2024 07:27:57 AM KST)
     Repo-filename      : /etc/yum.repos.d/scp.rhel8.repo
     
     Repo-id            : rhel-8-baseos
     Repo-name          : rhel-8-baseos
     Repo-revision      : 1718029433
     Repo-updated       : Mon 10 Jun 2024 11:23:52 PM KST
     Repo-pkgs          : 17,487
     Repo-available-pkgs: 17,487
     Repo-size          : 32 G
     Repo-baseurl       : http://scp-rhel8-ip/rhel/8/baseos
     Repo-expire        : 172,800 second(s) (last: Thu 08 Aug 2024 07:27:57 AM KST)
     Repo-filename      : /etc/yum.repos.d/scp.rhel8.repo
     
     Repo-id            : rhel-8-baseos-debug
     Repo-name          : rhel-8-baseos-debug
     Repo-revision      : 1717662461
     Repo-updated       : Thu 06 Jun 2024 05:27:41 PM KST
     Repo-pkgs          : 17,078
     Repo-available-pkgs: 17,078
     Repo-size          : 100 G
     Repo-baseurl       : http://scp-rhel8-ip/rhel/8/baseos-debug
     Repo-expire        : 172,800 second(s) (last: Thu 08 Aug 2024 07:27:57 AM KST)
     Repo-filename      : /etc/yum.repos.d/scp.rhel8.repo

     Repo-id            : rhel-8-appstream
     Repo-name          : rhel-8-appstream
     Repo-revision      : 1718903734
     Repo-updated       : Fri 21 Jun 2024 02:15:34 AM KST
     Repo-pkgs          : 38,260
     Repo-available-pkgs: 25,799
     Repo-size          : 122 G
     Repo-baseurl       : http://scp-rhel8-ip/rhel/8/appstream
     Repo-expire        : 172,800 second(s) (last: Thu 08 Aug 2024 07:27:57 AM KST)
     Repo-filename      : /etc/yum.repos.d/scp.rhel8.repo
     
     Repo-id            : rhel-8-baseos
     Repo-name          : rhel-8-baseos
     Repo-revision      : 1718029433
     Repo-updated       : Mon 10 Jun 2024 11:23:52 PM KST
     Repo-pkgs          : 17,487
     Repo-available-pkgs: 17,487
     Repo-size          : 32 G
     Repo-baseurl       : http://scp-rhel8-ip/rhel/8/baseos
     Repo-expire        : 172,800 second(s) (last: Thu 08 Aug 2024 07:27:57 AM KST)
     Repo-filename      : /etc/yum.repos.d/scp.rhel8.repo
     
     Repo-id            : rhel-8-baseos-debug
     Repo-name          : rhel-8-baseos-debug
     Repo-revision      : 1717662461
     Repo-updated       : Thu 06 Jun 2024 05:27:41 PM KST
     Repo-pkgs          : 17,078
     Repo-available-pkgs: 17,078
     Repo-size          : 100 G
     Repo-baseurl       : http://scp-rhel8-ip/rhel/8/baseos-debug
     Repo-expire        : 172,800 second(s) (last: Thu 08 Aug 2024 07:27:57 AM KST)
     Repo-filename      : /etc/yum.repos.d/scp.rhel8.repo