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: IP Change
• 1.2.5: Linux NTP Setting
• 1.2.6: Setting up RHEL Repo and WKMS
• 1.2.7: Installing 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 지표
• 2.2: How-to guides
• 2.2.1: Launch Configuration
• 2.2.2: Managing Policies
• 2.2.3: Managing Schedules
• 2.2.4: Managing Notifications
• 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: Image Management
• 3.2.2: Using Multi-instance GPU in GPU Server
• 3.2.3: Using NVSwitch on GPU Server
• 3.2.4: Keypair Management
• 3.2.5: ServiceWatch Agent Installation
• 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: Installing ServiceWatch Agent
• 4.2.2: RHEL Repo 설정하기
• 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: Installing 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: Set Trigger
• 6.2.2: AIOS Connect
• 6.2.3: Blueprint Detailed Guide
• 6.2.4: PrivateLink Service Integration
• 6.2.5: 리소스 기반 정책 가이드
• 6.3: 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.2: How-to guides
• 8.2.1: Connecting to the Server
• 8.2.2: Using Snapshots
• 8.2.3: Move 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 allows you to freely allocate and use as much as you need at the necessary time without purchasing infrastructure resources such as CPU, Memory, etc. provided by the server individually. You can use resources with optimized performance according to your computing usage purposes such as development, testing, and application execution in a cloud environment.

Key Features

• Easy and convenient computing environment configuration: Through the web-based Console, users can easily use Self Service from Virtual Server provisioning to resource management and cost management. If you need to change the capacity of major resources such as CPU or Memory while using Virtual Server, you can easily expand or reduce without operator intervention.

• Provision of various types of services: Provides virtualized vCore/Memory resources according to predefined server types (1~128 vCore).

  • General Virtual Server: Provides Computing Specs generally used (maximum 16vCore, 256GB)
  • High Capacity Virtual Server: Provides when large capacity resources larger than General Virtual Server Spec are needed

• Strong security application: Protects servers safely by controlling Inbound/Outbound traffic communicating with external internet or other VPC (Virtual Private Cloud) through Security Group service. In addition, you can stably operate computing resources through real-time monitoring.

Service Architecture

Provided Functions

Virtual Server provides the following functions.

• Automatic Provisioning and Management: Provides functions from Virtual Server provisioning to resource management and cost management through web-based Console. If you need to change the capacity of major resources such as CPU or Memory while using Virtual Server, you can change immediately using the server type modification function.
• Standard server type and Image provision: Provides virtualized vCore/Memory resources according to standard server types, and provides standard OS Image.
• Storage connection: Provides additional connection storage in addition to OS disk. You can use by additionally connecting Block Storage, File Storage, and Object Storage.
• Network connection: You can connect Virtual Server’s general subnet/IP and Public NAT IP. Provides local subnet connection for communication between servers. This task can be modified on the detail page.
• Security Group application: Protects servers safely by controlling Inbound/Outbound traffic communicating with external internet or other VPC through Security Group service.
• Monitoring: You can check monitoring information such as CPU, Memory, Disk, etc. corresponding to computing resources through Cloud Monitoring service.
• Backup and recovery: You can backup and recover Virtual Server Image through Backup service.
• Cost management: You can create, stop, and terminate servers as needed, and since billing is based on actual usage time, you can check costs according to usage.
• ServiceWatch service integration provision: You can monitor data through ServiceWatch service.

Components

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

Image

You can create and manage Image. Main functions are as follows.

• Image creation: You can create the configuration of the Virtual Server in use as an Image, and you can create an Image by uploading the user’s Image file to Object Storage.
• Shared Image creation: You can create a Shared Image that can be shared from an Image with Private Visibility.
• Share to other Account: You can share an Image to another Account.
• For Image creation and usage methods, refer to How-to guides > Image document.

Keypair

To provide more secure OS access, we strengthen security by providing Key Pair instead of ID/Password input method. Main functions are as follows.

• Keypair creation: Creates user authentication for connecting to Virtual Server.
• Import public key: You can import a public key by file upload or direct input of public key.
• For Keypair creation and usage methods, refer to How-to guides > Keypair document.

Server Group

Through Server Group settings, you can place Virtual Server and Block Storage added when creating Virtual Server close to or distributed across racks and hosts. Main functions are as follows.

• Server Group creation: You can set Virtual Servers belonging to the same Server Group as Anti-Affinity (distributed placement), Affinity (close placement), Partition (Virtual Server and Block Storage distributed placement).
• For Server Group creation and usage methods, refer to How-to guides > Server Group document.

OS Image Provided Versions

The OS Images provided by Virtual Server are as follows

Server Type

The server types supported by Virtual Server are as follows. For details on server types, refer to Virtual Server Server Type.

Standard s1v2m4

Constraints

Prerequisite Services

This is a list of services that need to be configured in advance before creating this service. For details, please prepare in advance by referring to the guide provided for each service.

1.1.1 - Server Type

Virtual Server server type

Virtual Server provides a server type suitable for the purpose of use. The server type consists of various combinations such as CPU, Memory, Network Bandwidth, etc. The host server used by the Virtual Server is determined by the server type selected when creating the Virtual Server. Please select a 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 1st generation: up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor
• Supports up to 16 vCPUs and 256 GB of memory
• Up to 12.5 Gbps networking speed

S2 Server Type

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

• Samsung Cloud Platform v2’s 2nd generation: up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
• Supports up to 16 vCPUs and 256 GB of memory
• Up to 12.5 Gbps networking speed

h2 Server Type

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

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

1.1.2 - Monitoring Metrics

Virtual Server monitoring metrics

The following table shows the monitoring metrics of Virtual Server that can be checked through Cloud Monitoring. For more information on how to use Cloud Monitoring, please refer to the Cloud Monitoring guide.

You can get basic monitoring metrics without installing Agent, and please check the metrics below in Table. Virtual Server Monitoring Metrics (Basic). In addition, you can check the metrics that can be retrieved by installing Agent in Table. Virtual Server Additional Monitoring Metrics (Agent Installation Required).

For Windows OS, memory-related metrics can only be retrieved if the Agent is installed.

1.1.3 - ServiceWatch Metrics

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

For information on how to enable detailed monitoring for Virtual Server, refer to How-to guides > Enable ServiceWatch detailed monitoring.

Basic Metrics

The following are basic metrics for the namespace Virtual Server.

In the table below, metrics with metric names marked in bold are selected as key metrics among the basic metrics provided by Virtual Server. Key metrics are used to configure service dashboards that are automatically built for each service in ServiceWatch. You can also check key metrics on the monitoring tab of the Virtual Server detail page.

Each metric guides you on which statistic value is meaningful when querying that metric through the user guide, and the statistic value marked in bold among the meaningful statistics is the key statistic value. In the service dashboard or monitoring tab, you can view key metrics through key statistic values.

1.2 - How-to guides

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

Create Virtual Server

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

To create a Virtual Server, follow the procedure below.

1. Click All Services > Compute > Virtual Server menu. You will be moved to the Service Home page of Virtual Server.

2. On the Service Home page, click the Create Virtual Server button. You will be moved to the Create Virtual Server page.

3. On the Create Virtual Server page, enter information required for service creation and select detailed options.

   • In the Image and version selection area, select the required information.

     Category	Required	Detailed Description
     Image	Required	Select the type of Image provided Standard: Samsung Cloud Platform standard provided Image Alma Linux, Oracle Linux, RHEL, Rocky Linux, Ubuntu, Windows Custom: User created Image Kubernetes: Image for Kubernetes RHEL, Ubuntu Marketplace: Image subscribed from Marketplace
     Image Version	Required	Select version of selected Image Provides version list of provided server Image

     Table. Virtual Server Image and Version Selection Input Items
   • In the Service information input area, enter or select the required information.

     Category	Required	Detailed Description
     Server Count	Required	Number of servers to create simultaneously Only numbers can be entered, enter value between 1 and 100
     Service Type > Server Type	Required	Virtual Server server type Standard: Standard specs generally used High Capacity: Large capacity server specs larger than Standard For details on server types provided by Virtual Server, refer to Virtual Server Server Type
     Service Type > Planned Compute	Required	Resource status with Planned Compute set In Use: Number in use among resources with Planned Compute set Set: Number of resources with Planned Compute set Coverage Preview: Amount applied as Planned Compute per resource Apply for Planned Compute Service: Move to Planned Compute service creation page For details, refer to Apply for Planned Compute
     Block Storage	Required	Configure Block Storage used by server according to purpose Default OS: Area where OS is installed and used Capacity is entered in Units, minimum capacity varies depending on OS Image type Alma Linux: Enter value between 2 and 1,536 Oracle Linux: Enter value between 7 and 1,536 RHEL: Enter value between 2 and 1,536 Rocky Linux: Enter value between 2 and 1,536 Ubuntu: Enter value between 2 and 1,536 Windows: Enter value between 4 and 1,536 SSD: High performance general volume HDD: General volume SSD/HDD_KMS: Additional encryption volume using Samsung Cloud Platform KMS (Key Management Service) encryption key Encryption application is only possible at initial creation and cannot be changed after creation Performance degradation occurs when using SSD_KMS disk type SSD_Provisioned: SSD volume with configurable IOPS and Throughput Additional: Use when additional user space is needed outside OS area Select Use and then enter storage type and capacity To add storage, click + button, to delete, click x button (can add up to 25) Capacity is entered in Units, enter value between 1 and 1,536 1 Unit is 8GB, so 8 to 12,288GB is created SSD: High performance general volume HDD: General volume SSD/HDD_KMS: Additional encryption volume using Samsung Cloud Platform KMS (Key Management Service) encryption key Encryption application is only possible at initial creation and cannot be changed after creation Performance degradation may occur when using SSD_KMS disk type SSD/HDD_MultiAttach: Volume that can connect to 2 or more servers SSD_Provisioned: SSD volume with configurable IOPS and Throughput For details by Block Storage type, refer to Create Block Storage Delete on termination: When Delete on Termination is selected, the Volume is also terminated when the server is terminated Volumes with snapshots are not deleted even when Delete on termination is Use Multi attach volumes are only deleted when the server to be deleted is the last remaining server connected to the volume Max IOPS: Enter IOPS maximum value within 5,000 to 20,000 Cannot set when disk type is HDD, HDD_KMS, HDD_MultiAttach
     Server Group	Optional	Set servers belonging to the same Server Group to Anti-Affinity (distributed placement), Affinity (close placement), Partition (Virtual Server and Block Storage distributed placement) Select Use and then select Server Group Select Create New to create Server Group Servers belonging to the same Server Group are placed in Best Effort manner according to selected policy Select policy from Anti-Affinity (distributed placement), Affinity (close placement), Partition (Virtual Server and Block Storage distributed placement)

     Table. Virtual Server Service Information Input Items
     Caution

     When using Partition (Virtual Server and Block Storage distributed placement) policy among Server Group policies, Block Storage Volume cannot be additionally allocated after Virtual Server creation, so create all necessary Block Storage at the Virtual Server creation stage.
   • In the Required information input area, enter or select the required information.

     Category	Required	Detailed Description
     Server Name	Required	Enter name for server identification when selected server count is 1 Set hostname with entered server name Enter within 63 characters using English, numbers, spaces, and special characters (-, _)
     Network Settings > Create New Network Port	Required	Set network where Virtual Server will be installed VPC Name: Select pre-created VPC General Subnet: Select pre-created general Subnet IP can select Auto Create or user input, if Input is selected, user can directly enter IP NAT: Can only use when server count is 1 and Internet Gateway is connected to VPC. Check Use to select NAT IP NAT IP: Select NAT IP If there is no NAT IP to select, click Create New button to create Public IP Click Refresh button to check and select created Public IP When Public IP is created, fees are charged according to Public IP fee standard Local Subnet (Optional): Select Use for Local Subnet Not required for service creation Must select pre-created Local Subnet IP can select Auto Create or user input, if Input is selected, user can directly enter IP Security Group: Settings required to connect to server Select: Select pre-created Security Group Create New: If there is no Security Group to apply, can create separately in Security Group service Can select up to 5 If Security Group is not set, all connections are blocked by default Security Group must be set to allow necessary connections
     Network Settings > Specify Existing Network Port	Required	Set network where Virtual Server will be installed VPC: Select pre-created VPC General Subnet: Select pre-created general Subnet and Port NAT: Can only use when server count is 1 and Internet Gateway is connected to VPC. Check Use to select NAT IP NAT IP: Select NAT IP If there is no NAT IP to select, click Create New button to create Public IP Click Refresh button to check and select created Public IP Local Subnet (Optional): Select Use for Local Subnet Select pre-created Local Subnet and Port
     Keypair	Required	User authentication method to use when connecting to the server Create New: Create a new one when a new Keypair is needed For the new Keypair creation method, refer to Create Keypair Default login account list by OS Alma Linux: almalinux Oracle Linux: cloud-user RHEL: cloud-user Rocky Linux: rocky Ubuntu: ubuntu Windows: sysadmin </ul

     Table. Virtual Server Required Information Input Items
   • In the Additional information input area, enter or select the required information.

     Category	Required	Detailed Description
     Lock	Optional	Set whether to use Lock When Lock is used, prevents operations such as server termination, start, stop to prevent accidental malfunction
     Init Script	Optional	Script to execute when server starts Init script must be written as Batch script for Windows or Shell script or cloud-init for Linux depending on Image type. Can enter up to 45,000 bytes
     Tag	Optional	Add tags Can add up to 50 per resource Click Add Tag button and then enter or select Key, Value values

     Table. Virtual Server Additional Information Input Items

4. On the Summary panel, check the created detailed information and estimated billing amount, then click the Create button.

   • When creation is complete, check the created resource on the Virtual Server List page.

Check Virtual Server Details

Virtual Server service can check and modify overall resource list and detailed information. Virtual Server Detail page is composed of Detail Information, Monitoring, Tags, Operation History tabs.

To check detailed information of Virtual Server service, follow the procedure below.

1. Click All Services > Compute > Virtual Server menu. You will be moved to the Service Home page of Virtual Server.
2. On the Service Home page, click the Virtual Server menu. You will be moved to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to check detailed information for. You will be moved to the Virtual Server Detail page.
   • Virtual Server Detail page displays status information and additional function information, and is composed of Detail Information, Monitoring, Tags, Operation History tabs.
   • For details on Virtual Server status, refer to Check Virtual Server Detail Information.

     Category	Detailed Description
     Virtual Server Status	Status of Virtual Server created by user Build: State where Build command is transmitted Building: Build in progress Networking: Process in progress during server creation Scheduling: Process in progress during server creation Block_Device_Mapping: Connecting Block Storage during server creation Spawning: State where server creation process is in progress Active: Usable state Powering_off: State when stop is requested Deleting: Server deletion in progress Reboot_Started: State where Reboot is in progress Error: Error state Migrating: State where server is being migrated to another host Reboot: State where Reboot command is transmitted Rebooting: Restart in progress Rebuild: State where Rebuild command is transmitted Rebuilding: State when Rebuild is requested Rebuild_Spawning: State where Rebuild process is in progress Resize: State where Resize command is transmitted Resizing: Resize in progress Resize_Prep: State when server type modification is requested Resize_Migrating: State where server is moving to another host while Resize is in progress Resize_Migrated: State where server has completed moving to another host while Resize is in progress Resize_Finish: Resize completed Revert_Resize: Server Resize or migration failed for some reason. Target server is cleaned and original source server is restarted Shutoff: State when Powering off is completed Verity_ Resize: State where server type confirmation/server type reversion is selectable after Resize_Prep progress according to server type modification request Resize_Reverting: State when server type reversion is requested Resize_Confirming: State where server Resize request is being confirmed
     Server Control	Buttons to change server status Start: Start stopped server Stop: Stop running server Restart: Restart running server
     Create Image	Create a user image from the current server image For detailed image creation method, refer to Create Image
     Console Log	Check current server console log Can check console log output from current server. For details, refer to Check Console Log
     Create Dump	Create current server Dump Dump file is created inside Virtual Server For detailed Dump creation method, refer to Create Dump
     Rebuild	Delete existing Virtual Server OS area data and settings, and configure by Rebuilding as new server For details, refer to Perform Rebuild
     Terminate Service	Button to terminate service

     Table. Virtual Server Status Information and Additional Functions

Detail Information

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

Monitoring

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

Tags

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

Operation History

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

Control Virtual Server Operation

If operation control of created Virtual Server resource is needed, you can perform tasks on Virtual Server List or Virtual Server Detail page. You can start, stop, and restart running servers.

Start Virtual Server

You can start stopped (Shutoff) Virtual Server. To start Virtual Server, follow the procedure below.

1. Click All Services > Compute > Virtual Server menu. You will be moved to the Service Home page of Virtual Server.
2. On the Service Home page, click the Virtual Server menu. You will be moved to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to start among stopped (Shutoff) servers to move to the Virtual Server Detail page.
   • On the Virtual Server List page, you can Start through More button on the right for each resource.
   • After selecting multiple servers with checkbox, you can control multiple servers simultaneously through Start button at the top.
4. On the Virtual Server Detail page, click Start button at the top to start the server. Check changed server status in Status Display item.
   • When Virtual Server start is completed, server status changes from Shutoff to Active.
   • For details on Virtual Server status, refer to Check Virtual Server Detail Information.

Stop Virtual Server

You can stop running (Active) Virtual Server. To stop Virtual Server, follow the procedure below.

1. Click All Services > Compute > Virtual Server menu. You will be moved to the Service Home page of Virtual Server.
2. On the Service Home page, click the Virtual Server menu. You will be moved to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to stop among running (Active) servers to move to the Virtual Server Detail page.
   • On the Virtual Server List page, you can Stop through More button on the right for each resource.
   • After selecting multiple servers with checkbox, you can control multiple servers simultaneously through Stop button at the top.
4. On the Virtual Server Detail page, click Stop button at the top to start the server. Check changed server status in Status Display item.
   • When Virtual Server stop is completed, server status changes from Active to Shutoff.
   • For details on Virtual Server status, refer to Check Virtual Server Detail Information.

Restart Virtual Server

You can restart created Virtual Server. To restart Virtual Server, follow the procedure below.

1. Click All Services > Compute > Virtual Server menu. You will be moved to the Service Home page of Virtual Server.
2. On the Service Home page, click the Virtual Server menu. You will be moved to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to restart to move to the Virtual Server Detail page.
   • On the Virtual Server List page, you can Restart through More button on the right for each resource.
   • After selecting multiple servers with checkbox, you can control multiple servers simultaneously through Restart button at the top.
4. On the Virtual Server Detail page, click Restart button at the top to start the server. Check changed server status in Status Display item.
   • During Virtual Server restart, server status changes to Rebooting and finally to Active.
   • For details on Virtual Server status, refer to Check Virtual Server Detail Information.

Manage Virtual Server Resources

If server control and management functions of created Virtual Server resource are needed, you can perform tasks on Virtual Server List or Virtual Server Detail page.

Create Image

You can create Image of running Virtual Server.

To create Virtual Server Image, follow the procedure below.

1. Click All Services > Compute > Virtual Server menu. You will be moved to the Service Home page of Virtual Server.

2. On the Service Home page, click the Virtual Server menu. You will be moved to the Virtual Server List page.

3. On the Virtual Server List page, click the resource to create Image. You will be moved to the Virtual Server Detail page.

4. On the Virtual Server Detail page, click the Create Image button. You will be moved to the Create Image page.

   • In the Service information input area, enter the required information.

     Category	Required	Detailed Description
     Image Name	Required	Name of Image to create Enter within 200 characters using English, numbers, spaces, and special characters (-, _)

     Table. Image Service Information Input Items

5. Check input information and click Complete button.

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

Modify Server Type

You can modify server type of Virtual Server server.

To modify Virtual Server server type, follow the procedure below.

1. Click All Services > Compute > Virtual Server menu. You will be moved to the Service Home page of Virtual Server.
2. On the Service Home page, click the Virtual Server menu. You will be moved to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to control operation. You will be moved to the Virtual Server Detail page.
4. On the Virtual Server Detail page, check server status and click server type Modify button. Modify Server Type popup window opens.
5. On the Modify Server Type popup window, change server type and then click Confirm button.
   • When Virtual Server server type is modified, Virtual Server status changes to Resize execution related status.
   • For details on Virtual Server status, refer to Check Virtual Server Detail Information.

Change IP

For method of changing IP, refer to Change IP.

Enable ServiceWatch Detailed Monitoring

By default, Virtual Server is linked with ServiceWatch for basic monitoring. If needed, you can enable detailed monitoring to more quickly identify and respond to operational issues. For details on ServiceWatch, refer to ServiceWatch Overview.

To enable Virtual Server ServiceWatch detailed monitoring, follow the procedure below.

1. Click All Services > Compute > Virtual Server menu. You will be moved to the Service Home page of Virtual Server.
2. On the Service Home page, click the Virtual Server menu. You will be moved to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to enable ServiceWatch detailed monitoring. You will be moved to the Virtual Server Detail page.
4. On the Virtual Server Detail page, click ServiceWatch detailed monitoring Modify button. You will be moved to Modify ServiceWatch Detailed Monitoring popup window.
5. On the Modify ServiceWatch Detailed Monitoring popup window, select Enable, check guide text and then click Confirm button.
6. Check ServiceWatch detailed monitoring item on Virtual Server Detail page.

Disable ServiceWatch Detailed Monitoring

To disable Virtual Server ServiceWatch detailed monitoring, follow the procedure below.

1. Click All Services > Compute > Virtual Server menu. You will be moved to the Service Home page of Virtual Server.
2. On the Service Home page, click the Virtual Server menu. You will be moved to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to disable ServiceWatch detailed monitoring. You will be moved to the Virtual Server Detail page.
4. On the Virtual Server Detail page, click ServiceWatch detailed monitoring Modify button. You will be moved to Modify ServiceWatch Detailed Monitoring popup window.
5. On the Modify ServiceWatch Detailed Monitoring popup window, deselect Enable, check guide text and then click Confirm button.
6. Check ServiceWatch detailed monitoring item on Virtual Server Detail page.

Virtual Server Management Additional Functions

For Virtual Server server management, you can check console log, create Dump, and perform Rebuild. To check Virtual Server console log, create Dump, and perform Rebuild, follow the procedure below.

Check Console Log

You can check current console log of Virtual Server.

To check Virtual Server console log, follow the procedure below.

1. Click All Services > Compute > Virtual Server menu. You will be moved to the Service Home page of Virtual Server.
2. On the Service Home page, click the Virtual Server menu. You will be moved to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to check console log. You will be moved to the Virtual Server Detail page.
4. On the Virtual Server Detail page, click Console Log button. You will be moved to Console Log popup window.
5. Check console log output on Console Log popup window.

Create Dump

To create Virtual Server Dump file, follow the procedure below.

1. Click All Services > Compute > Virtual Server menu. You will be moved to the Service Home page of Virtual Server.
2. On the Service Home page, click the Virtual Server menu. You will be moved to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to check detailed information. You will be moved to the Virtual Server Detail page.
4. On the Virtual Server Detail page, click Create Dump button.
   • Dump file is created inside Virtual Server.

Perform Rebuild

You can delete existing Virtual Server server OS area data and settings, and configure by Rebuilding as new server.

To perform Virtual Server Rebuild, follow the procedure below.

1. Click All Services > Compute > Virtual Server menu. You will be moved to the Service Home page of Virtual Server.
2. On the Service Home page, click the Virtual Server menu. You will be moved to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to perform Rebuild. You will be moved to the Virtual Server Detail page.
4. On the Virtual Server Detail page, click Rebuild button.
   • During Virtual Server Rebuild, server status changes to Rebuilding and when Rebuild is completed, returns to state before Rebuild execution.
   • For details on Virtual Server status, refer to Check Virtual Server Detail Information.

Terminate Virtual Server

Terminating unused Virtual Server can reduce operating costs. However, since Virtual Server termination can immediately stop running services, you must fully consider the impact of service interruption before proceeding with termination.

To terminate Virtual Server, follow the procedure below.

1. Click All Services > Compute > Virtual Server menu. You will be moved to the Service Home page of Virtual Server.
2. On the Service Home page, click the Virtual Server menu. You will be moved to the Virtual Server List page.
3. On the Virtual Server List page, select the resource to terminate and click Terminate Service button.
   • Termination of connected storage varies depending on the Delete on termination setting; see Termination Constraints.
4. When termination is complete, check if resource is terminated on Virtual Server List page.

Termination Constraints

If termination is not possible when Virtual Server termination is requested, you will be guided through a popup window. Refer to the cases below.

Termination of connected storage varies depending on Delete on termination setting, so please refer.

1.2.1 - Image

The user can enter the required information for the Image service within the Virtual Server service and select detailed options through the Samsung Cloud Platform Console to create the service.

Image generation

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

To create an Image, follow the steps below.

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

2. Click the Image menu on the Service Home page. Go to the Image List page.

3. Click the Image Create button on the Image List page. It navigates to the Image Create page.

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

     Category	Required	Detailed description
     Image name	Required	Name of the Image to create Enter within 255 characters using English letters, numbers, spaces, and special characters (-, _)
     Image file > URL	Required	Enter URL after uploading Image file to Object Storage Object Storage Details page allows copying URL The Bucket of Object Storage where the Image file is uploaded must be in the same zone as the server to be created Image file can only have .qcow2 extension 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 size (GB) for the Image to be created Enter a value between 0 and 12,288 GB
     Minimum RAM	Required	Minimum RAM capacity (GB) of the image to be created Enter a value between 0 and 2,097,151 GB
     Visibility	Required	Indicates access permissions for the Image Private: Can be used only within the Account Shared: Can be shared between Accounts
     Protected	Select	Select whether Image deletion is prohibited Checking Use prevents accidental deletion of the Image This setting can be changed after Image creation

     Table. Image Service Information Input Items
   • Additional Information Input Enter or select the required information in the area.

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

     Table. Image additional information input items

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

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

Image Check detailed information

Image service can view and edit the full resource list and detailed information. Image detail page consists of detailed information, tags, operation history tabs.

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

1. All Services > Compute > Virtual Server Click the menu. Go to the Service Home page of Virtual Server.
2. Click the Image menu on the Service Home page. Go to the Image list page.
3. Image List page, click the resource to view detailed information. Image Details page will be opened.
   • Image Details page displays status information and additional feature information, and consists of Detail Information, Tag, Work History tabs.

     Category	Detailed description
     Image status	Status of the Image created by the user Active: Available Queued: When an Image creation request is made, the Image is uploaded and waiting for processing Importing: When an Image creation request is made, the Image is uploaded and being processed
     Create shared Image	Create Image to share with another Account Can be created only when the Image’s Visibility is private and the Image has snapshot information
     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 Only displayed for Images created by Create shared Image or by uploading a qcow2 file
     Image Delete	Button to delete the Image If the Image is deleted, it cannot be recovered

     Table. Image status information and additional functions

Detailed Information

Image list page allows you to view detailed information of the selected resource and edit the information if needed.

Tag

Image list page, you can view the tag information of the selected resource, and you can add, modify, or delete it.

Work 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 Image for Sharing

Create an Image to share with another Account.

To create an image for sharing, follow the steps below.

1. Log in to the shared Account and click the All Services > Compute > Virtual Server menu. Go to the Virtual Server’s Service Home page.
2. Click the Image menu on the Service Home page. Navigate to the Image List page.
3. Click the Image to create a shared Image on the Image List page. You will be taken to the Image Details page.
4. Create Shared Image Click the button. A popup window notifying the creation of a shared Image will open.
5. After checking the notification content, click the Complete button.

Share Image to another Account

Create an image to share with another Account.

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

1. Log in to the shared Account and click the All Services > Compute > Virtual Server menu. Navigate to the Virtual Server’s Service Home page.

2. Click the Image menu on the Service Home page. It navigates to the Image List page.

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

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

5. After checking the notification content, click the Confirm button. It moves 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. A popup notifying Image sharing opens.

   Category	Required	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 Enter within 64 characters using English letters, numbers, and special character -

   Table. Image sharing items to another Account

7. After checking the notification content, click the Confirm button. You can check the information in the sharing status of the Image Details page.

   • When first requested, the status is Pending, and when approval is completed by the Account to be shared, it changes to Accepted, and if approval is denied, it changes to Rejected.

Receive shared Image from another Account

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

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

2. Click the Image menu on the Service Home page. It navigates to the Image List page.

3. Image List on the page More > Image Share Request List click the button. Image Share Request List popup 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	shared Image name
   OS type	OS type of shared Image
   Owner Account ID	Owner Account ID of shared Image
   Creation time	Creation time of shared Image
   Approval	Approve the shared Image
   Reject	Reject processing of the shared Image

   Table. Image sharing request list item

5. After checking the notification content, click the Confirm button. You can check the shared Image in the Image list.

Image Delete

You can delete unused images. However, once an image is deleted it cannot be recovered, so you should fully consider the impact before proceeding with the deletion.

To delete Image, follow the steps below.

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

1.2.2 - Keypair

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

Creating a Keypair

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

Follow these steps to create a Keypair.

1. All Services > Compute > Virtual Server – Click to go to the Virtual Server Service Home page.

2. On the Service Home page, click the Keypair menu to go to the Keypair List page.

3. On the Keypair List page, click the Create Keypair button to go to the Create Keypair page.

   • In the Service Information Input section, enter the required information.

     Item	Required	Description
     Keypair Name	Required	Name of the Keypair to create. Use English letters, numbers, spaces, and special characters (-, _) up to 255 characters.
     Keypair Type	Required	ssh

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

     Item	Required	Description
     Tags	Optional	Add tags (up to 50 per resource). Click the Add Tag button and enter/select Key and Value.

     Table. Additional Keypair information input items

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

   • After creation, the new Keypair will appear on the Keypair List page.

Viewing Keypair Details

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

To view the details of a Keypair, follow these steps.

1. All Services > Compute > Virtual Server – Click to go to the Virtual Server Service Home page.
2. On the Service Home page, click the Keypair menu to go to the Keypair List page.
3. On the Keypair List page, click the resource you want to view details for. You will be taken to the Keypair Details page.
   • The Keypair Details page displays status information and additional feature information, organized into Details, Tags, and Activity History tabs.

Details

You can view the detailed information of the selected resource from the Keypair List page, and modify the information if needed.

Tags

You can view, add, modify, or delete the tags of a selected resource from the Keypair List page.

Activity History

You can view the activity history of a selected resource from the Keypair List page.

Managing Keypair Resources

This section describes the control and management functions for Keypair.

Retrieving the Public Key

Follow these steps to retrieve the public key.

1. All Services > Compute > Virtual Server – Click to go to the Virtual Server Service Home page.

2. On the Service Home page, click the Keypair menu to go to the Keypair List page.

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

   • In the Required Information Input section, enter or select the required information.

     Item	Required	Description
     Keypair Name	Required	Name of the Keypair to retrieve
     Keypair Type	Required	ssh
     Public Key	Required	Enter the public key. File Upload: Click the Attach File button to attach a public key file (only .pem files are allowed). Public Key Input: Paste the copied public key value (you can copy the public key value from the Keypair Details page).

     Table. Required fields for retrieving a public key

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

   • After completion, the newly created resource will appear on the Keypair List page.

Deleting a Keypair

You can delete an unused Keypair. However, once a Keypair is deleted, it cannot be recovered, so please review the impact carefully before deletion.

To delete a Keypair, follow these steps.

1. All Services > Compute > Virtual Server – Click to go to the Virtual Server Service Home page.
2. On the Service Home page, click the Keypair menu to go to the Keypair List page.
3. On the Keypair List page, select the resource you want to delete and click the Delete button.
   • You can select multiple Keypairs using checkboxes and click the Delete button at the top of the resource list.
4. After deletion is complete, verify that the resource has been removed from the Keypair List page.

1.2.3 - Server Group

Users can enter the required information for a Server Group within the Virtual Server service and select detailed options through the Samsung Cloud Platform Console to create the service.

Server Group Create

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

To create a Server Group, follow the steps below.

1. Click the All Services > Compute > Virtual Server menu. Go to the Service Home page of Virtual Server.
2. Click the Server Group menu on the Server Group page. Go to the Server Group list page.
3. Server Group List on the page, click the Server Group Create button. Navigate to the Server Group Create page.
   • Service Information Input area, enter or select the required information.

     Category	Required	Detailed description
     Server Group name	Required	Name of the Server Group to create Enter within 255 characters using English letters, numbers, spaces, and special characters (-, _)
     Policy	Required	Set Anti-Affinity (distributed placement), Affinity (proximate placement), Partition (distributed placement of Virtual Server and Block Storage) for Virtual Servers belonging to the same Server Group Anti-Affinity (distributed placement) and Affinity (proximate placement) policies place Virtual Servers belonging to the same Server Group based on the selected policy in a Best Effort manner, but are not absolutely guaranteed. Anti-Affinity (distributed placement): A policy that places servers belonging to a Server Group on different racks and hosts as much as possible Affinity (proximate placement): A policy that places servers belonging to a Server Group close together within the same rack and host as much as possible Partition (distributed placement of Virtual Server and Block Storage): A policy that places Virtual Servers belonging to a Server Group and the Block Storage connected to those servers in different distribution units (Partitions) The Partition (distributed placement of Virtual Server and Block Storage) policy displays the Partition number together so that it is clear which Partition each Virtual Server and its associated Block Storage belong to. Partition numbers are assigned based on the Partition Size (up to 3) set for the Server Group.

     Table. Server Group Service Information Input Items
   • Add Information Input area, enter or select the required information.

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

     Table. Server Group Additional Information Input Items
4. Check the input information and click the Complete button.
   • When creation is complete, check the created resources on the Server Group List page.

Server Group View detailed information

Server Group service can view and edit the full resource list and detailed information. Server Group Details page consists of Details, Tags, Activity Log tabs.

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

1. Click the All Services > Compute > Virtual Server menu. Go to the Service Home page of Virtual Server.
2. Click the Server Group menu on the Service Home page. You will be taken to the Server Group List page.
3. Click the resource to view detailed information on the Server Group List page. It navigates to the Server Group Details page.
   • Server Group Details page displays status information and additional feature information, and consists of Details, Tags, Activity History tabs.

Detailed Information

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

Tag

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

Work History

You can view the operation history of the selected resource on the Server Group List page.

Server Group Delete

You can delete unused Server Groups. However, once a Server Group is deleted it cannot be recovered, so 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 it. Go to the Virtual Server’s Service Home page.
2. On the Service Home page, click the Server Group menu. Navigate to the Server Group List page.
3. Server Group list On the page, select the resource to delete, and click the Delete button.
   • Server Group list on the page select multiple Server Group check boxes, and click the Delete button at the top of the resource list.
4. When deletion is complete, check whether the resource has been deleted on the Server Group list page.

1.2.4 - IP Change

You can change the IP of the Virtual Server and add network ports to the Virtual Server to set the IP.

IP Change

You can change the IP of the Virtual Server.

To change the IP, follow the steps below.

1. All Services > Compute > Virtual Server Click the menu. Navigate to the Service Home page of Virtual Server.
2. Click the Virtual Server menu on the Service Home page. Move to the Virtual Server List page.
3. Virtual Server List Click the resource to change the IP on the page. Navigate to the Virtual Server Details page.
4. Virtual Server Details page, click the Edit button of the IP item to change the IP. The IP Edit popup opens.
5. Edit IP In the popup window, after selecting Subnet, set the IP to change.
   • Input: Enter the IP to be changed directly.
   • Automatic Generation: Automatically generate the IP and apply it.
6. When the settings are complete, click the Confirm button.
7. When the popup notifying IP modification opens, click the Confirm button.

Setting IP on the server after adding network ports

If you create a Virtual Server with Ubuntu Linux, after adding a network port on Samsung Cloud Platform, additional IP configuration is required on the server.

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

   Sample Code Download

   Copy Code

   Color mode

   ip a

   ip a

   • If there is an added interface, the following result is displayed.
   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. Use a text editor (e.g., vim) to open the /etc/netplan/50-cloud-init.yaml file.

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

   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. Set the IP on the added network DEVICE using the netplan command.

   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.

   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 - Linux NTP Setting

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

Install NTP Daemon

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

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

   Sample Code Download

   Copy Code

   Color mode

   dnf list chrony

   dnf list chrony

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

   Copy Code

   Color mode

   [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, use the dnf command to install the chrony package.

   Sample Code Download

   Copy Code

   Color mode

   dnf install chrony -y

   dnf install chrony -y

NTP Daemon Setup

To set up the chrony daemon, follow these steps.

1. Load 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.

   Sample Code Download

   Copy Code

   Color mode

   server 198.19.0.54 iburst

   server 198.19.0.54 iburst

3. Set it to automatically start the chrony daemon using the systemctl command.

   Sample Code Download

   Copy Code

   Color mode

   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.
   Sample Code Download

   Copy Code

   Color mode

   [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 - Setting up 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 utilizing the RHEL Repository provided by SCP.
SCP provides the latest version of the repository for the given major version by default. To set up the RHEL repository, follow the steps below.

1. Using the root user of the Virtual Server’s OS, use the cat command to check 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. /etc/hosts Modify the file with the content below and save.

   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. Verify the RHEL Repository connection configured on the server using the yum command.

   Sample Code Download

   Copy Code

   Color mode

   yum repolist –v

   yum repolist –v

   • If the RHEL Repository is successfully connected, you can check 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

Windows Key Management Service Configuration Guide

In Samsung Cloud Platform, when using Windows Server, you can authenticate genuine products by using the Key Management Service provided by SCP. Follow the steps below.

1. After right-clicking the Windows Start icon, please run cmd from Windows PowerShell (Administrator) or the Windows Run menu.

2. Windows PowerShell (administrator) or in cmd, please run the command below to register the KMS Server.

   Sample Code Download

   Copy Code

   Color mode

   slmgr /skms 198.19.2.23:1688

   slmgr /skms 198.19.2.23:1688

3. After executing the KMS Server registration command, check the notification popup indicating successful registration, then click OK.

   

4. Windows PowerShell (Administrator) or in cmd, please execute the command below to perform product activation.

   Sample Code Download

   Copy Code

   Color mode

   slmgr /ato

   slmgr /ato

5. After confirming the notification popup that the product activation was successful, click OK.

   

6. Windows PowerShell (Administrator) or cmd, run the command below to check if it has been activated.

   Sample Code Download

   Copy Code

   Color mode

   slmgr /dlv

   slmgr /dlv

7. After confirming the notification popup that the product activation was successfully performed, click OK.

   

1.2.7 - Installing ServiceWatch Agent

Users can install the ServiceWatch Agent on a Virtual Server to collect custom metrics and logs.

ServiceWatch Agent

The agents required to collect custom metrics and logs for ServiceWatch on a Virtual Server can be broadly divided into two types: Prometheus Exporter and Open Telemetry Collector.

Prerequisites for Using ServiceWatch Agent

To use the ServiceWatch Agent, please refer to Prerequisite environment configuration for ServiceWatch Agent and prepare the necessary settings.

Installing Prometheus Exporter for Virtual Server (Linux)

Install the Prometheus Exporter on a Linux server following the steps below.

Installing Node Exporter

Install Node Exporter according to the steps below.

1. Create Node Exporter User
2. Node Exporter Configuration

Create Node Exporter User

Create a dedicated user to securely isolate the Node Exporter process.

sudo useradd --no-create-home --shell /bin/false node_exporter

sudo useradd --no-create-home --shell /bin/false node_exporter

Node Exporter Configuration

1. Download Node Exporter for installation. The guide uses the following version:

   • Download path: /tmp
   • Version: 1.7.0
     Sample Code Download

     Copy Code

     Color mode

     cd /tmp
     wget https://github.com/prometheus/node_exporter/releases/download/v1.7.0/node_exporter-1.7.0.linux-amd64.tar.gz

     cd /tmp
     wget https://github.com/prometheus/node_exporter/releases/download/v1.7.0/node_exporter-1.7.0.linux-amd64.tar.gz

     Note

     The latest Node Exporter version can be found at Node Exporter > Releases > Latest, and specific versions are available at Node Exporter > Releases.

2. Install the downloaded Node Exporter and set permissions on the executable.

   Sample Code Download

   Copy Code

   Color mode

   cd /tmp
   sudo tar -xvf node_exporter-1.7.0.linux-amd64.tar.gz -C /usr/local/bin --strip-components=1 node_exporter-1.7.0.linux-amd64/node_exporter

   cd /tmp
   sudo tar -xvf node_exporter-1.7.0.linux-amd64.tar.gz -C /usr/local/bin --strip-components=1 node_exporter-1.7.0.linux-amd64/node_exporter

   Sample Code Download

   Copy Code

   Color mode

   sudo chown node_exporter:node_exporter /usr/local/bin/node_exporter

   sudo chown node_exporter:node_exporter /usr/local/bin/node_exporter

3. Create a service file. Configure Node Exporter to collect memory (meminfo) or block storage (filesystem) metrics.

   Sample Code Download

   Copy Code

   Color mode

   sudo vi /etc/systemd/system/node_exporter.service

   sudo vi /etc/systemd/system/node_exporter.service

   Sample Code Download

   Copy Code

   Color mode

   [Unit]
   Description=Prometheus Node Exporter (meminfo only)
   Wants=network-online.target
   After=network-online.target
   
   [Service]
   User=node_exporter
   Group=node_exporter
   Type=simple
   ExecStart=/usr/local/bin/node_exporter \
     --collector.disable-defaults \    # Disable default collectors
     --collector.meminfo \             # Enable memory metrics
     --collector.filesystem            # Enable block storage filesystem metrics
   
   Restart=on-failure
   
   [Install]
   WantedBy=multi-user.target

   [Unit]
   Description=Prometheus Node Exporter (meminfo only)
   Wants=network-online.target
   After=network-online.target
   
   [Service]
   User=node_exporter
   Group=node_exporter
   Type=simple
   ExecStart=/usr/local/bin/node_exporter \
     --collector.disable-defaults \    # Disable default collectors
     --collector.meminfo \             # Enable memory metrics
     --collector.filesystem            # Enable block storage filesystem metrics
   
   Restart=on-failure
   
   [Install]
   WantedBy=multi-user.target

   Note

   • Collectors can be enabled or disabled using flags.

     • <code>--collector.{name}</code>: Enables a specific metric collector.
     • <code>--no-collector.{name}</code>: Disables a specific metric collector.
     • To disable all default metrics and enable only specific collectors, use <code>--collector.disable-defaults --collector.{name} ...</code>.

   • Below is a description of the main collectors.

   Collector	Description	Labels
   meminfo	Provides memory statistics	-
   filesystem	Provides filesystem statistics such as used disk space	device: Physical or virtual device path where the filesystem is located (e.g., /dev/sda1) fstype: Filesystem type (e.g., ext4, xfs, nfs, tmpfs) mountpoint: Path where the filesystem is mounted on the host OS; serves as an intuitive way to distinguish disks (e.g., /, /var/lib/docker, /mnt/data)

   Table. Description of main Node Exporter collectors

   • For detailed information on available metrics and configuration, see the Node Exporter > Collector page.
   • Available metrics may vary depending on the version of Node Exporter you use. See the Node Exporter repository.