Virtual Server

• 1: Overview
• 1.1: Server Type
• 1.2: Monitoring Metrics
• 1.3: ServiceWatch Metrics
• 2: How-to guides
• 2.1: Image
• 2.2: Keypair
• 2.3: Server Group
• 2.4: IP Change
• 2.5: Linux NTP Setting
• 2.6: Setting up RHEL Repo and WKMS
• 2.7: ServiceWatch Agent Installation
• 3: API Reference
• 4: CLI Reference
• 5: Release Note

1 - Overview

Service Overview

Virtual Server can be allocated freely as needed at the time needed without having to purchase infrastructure resources such as CPU, Memory provided by the server individually, and it is a virtual server optimized for cloud computing. In a cloud environment, you can use resources with optimized performance according to the user’s computing usage purpose such as development, testing, and application execution.

Features

• Easy and convenient computing environment configuration: Through a web-based console, users can easily use self-service from Virtual Server provisioning to resource management and cost management. If capacity changes of major resources such as CPU or Memory are needed while using Virtual Server, they can be easily scaled up or down without operator intervention.

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

  • General Virtual Server: Provides commonly used Computing Spec (up to 16 vCore, 256 GB)
  • Large-capacity Virtual Server: Provided when large-capacity resources beyond the standard Virtual Server Spec are needed

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

Service Architecture Diagram

Provided Features

Virtual Server provides the following functions.

• Auto Provisioning and Management: Provides functions from Virtual Server provisioning to resource management and cost management through a 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 it immediately using the server type modification feature.
• Standard server type and Image provision: Provides virtualized vCore/Memory resources according to the standard server type, and provides a standard OS Image.
• Storage Connection: Provides additional connected storage besides the OS disk. Block Storage, File Storage, and Object Storage can be added and used.
• Network Connection: You can connect the Virtual Server’s general subnet/IP settings and Public NAT IP. Provides a local subnet connection for inter-server communication. This operation can be modified on the detail page.
• Security Group applied: Through the Security Group service, it controls inbound/outbound traffic communicating with external internet or other VPCs, safely protecting the server.
• Monitoring: You can check monitoring information such as CPU, Memory, Disk that correspond to computing resources through the Cloud Monitoring service.
• Backup and Recovery: You can backup and recover Virtual Server Image through the Backup service.
• Cost Management: You can create, stop, or 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 the ServiceWatch service.

Components

Virtual Server provides standard server types and standard OS images. Users can select and use them 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 the user’s 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.
• Image creation and usage methods, please refer to the How-to guides > Image document.

Keypair

To provide a safer OS access, we enhance security by offering a Key Pair instead of the ID/Password entry method. The main features are as follows.

• Keypair creation: Create user credentials to connect to the Virtual Server.
• Get Public Key: You can retrieve the public key by loading a file or entering the public key directly.
• For creating and using Keypair, refer to the How-to guides > Keypair document.

Server Group

Through Server Group settings, you can place the Block Storage added when creating a Virtual Server near or distributed across racks and hosts. The main features are as follows.

• Server Group creation: You can set Virtual Servers belonging to the same Server Group to Anti-Affinity (distributed placement), Affinity (proximate placement), Partition (distributed placement of Virtual Server and Block Storage).
• For how to create and use Server Group, refer to the How-to guides > Server Group document.

OS Image Provided Version

The OS Image provided by Virtual Server are as follows

Server Type

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

Standard s1v2m4

Constraints

Preceding Service

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

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.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.3 - ServiceWatch Metrics

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

How to enable detailed monitoring of Virtual Server, please refer to How-to guides > ServiceWatch Detailed Monitoring Activation.

Basic Indicators

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

2 - How-to guides

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

Virtual Server Create

You can create and use Virtual Server services from the Samsung Cloud Platform Console.

To create Virtual Server, 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 Virtual Server Creation button on the Service Home page. You will be taken to the Virtual Server Creation page.
3. Virtual Server Creation page, enter the information required to create the service, and select detailed options.
   • Image and Version Selection Select the required information in the area.

     Category	Required	Detailed description
     Image	Required	Select the type of Image to provide 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 the chosen Image Provides a list of versions of the server Image offered

     Table. Virtual Server Image and version selection input items
   • 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, input a value between 1 and 100
     Service Type > Server Type	Required	Virtual Server Server Type Standard: Standard specifications commonly used High Capacity: Large server specifications above Standard For detailed information about server types provided by Virtual Server, refer to Virtual Server Server Type
     Service Type > Planned Compute	Required	Status of resources with Planned Compute set In Use: Number of resources with Planned Compute set that are in use Configured: Number of resources with Planned Compute set Coverage Preview: Amount applied by Planned Compute per resource Apply for Planned Compute Service: Go to Planned Compute service creation page For details, refer to Apply for Planned Compute
     Block Storage	Required	Block Storage settings used by the server according to purpose Basic OS: Area where OS is installed and used Enter capacity in Units; minimum capacity varies by 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 key Encryption can only be applied at initial creation and cannot be changed afterwards Using SSD_KMS disk type causes performance degradation Additional: Use when additional user space is needed outside the OS area After selecting Use, enter the storage type and capacity Click the + button to add storage, and the x button to delete (up to 25 can be added) Enter capacity in Units, value between 1 and 1,536 1 Unit is 8GB, so 8 ~ 12,288GB is created SSD: High-performance general volume HDD: General volume SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management Service) encryption key Encryption can only be applied at initial creation and cannot be changed afterwards Using SSD_KMS disk type may cause performance degradation SSD_MultiAttach: Volume that can be attached to more than one server For detailed information on each Block Storage type, refer to Create 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 Multi-attach volumes are deleted only when the server being deleted is the last remaining server attached to the volume
     Server Group	Select	Set servers belonging to the same Server Group to Anti-Affinity (distributed placement), Affinity (proximate placement), Partition (distributed placement of Virtual Server and Block Storage) Use after selecting, select Server Group Select 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 Select a policy among Anti-Affinity (distributed placement), Affinity (proximate placement), Partition (distributed placement of Virtual Server and Block Storage)

     Table. Virtual Server Service Information Input Items

* In the **Required Information Input** area, enter or select the necessary information.

Check Virtual Server detailed information

Virtual Server service allows you to view and edit the full resource list and detailed information. Virtual Server Details page is composed of Detailed Information, Tags, Activity Log tabs.

To view detailed information of the Virtual Server service, 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 Virtual Server menu on the Service Home page. You will be taken to the Virtual Server list page.
3. Click the resource to view detailed information on the Virtual Server List page. It will navigate to the Virtual Server Details page.
   • Virtual Server Details page displays status information and additional feature information, and consists of Details, Tags, Activity History tabs.
   • Virtual Server Additional Features for detailed information, please refer to Virtual Server Management Additional Features.

     Category	Detailed description
     Virtual Server Status	Status of Virtual Server created by the user Build: State where the Build command has been issued Building: Build in progress Networking: Server creation in progress process Scheduling: Server creation in progress process Block_Device_Mapping: Block Storage being attached during server creation Spawning: 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 the Reboot command has been issued Rebooting: Rebooting in progress Rebuild: State where the Rebuild command has been issued Rebuilding: State when a Rebuild request is made Rebuild_Spawning: Rebuild process is ongoing Resize: State where the Resize command has been issued Resizing: Resize in progress Resize_Prep: State when a server type modification request is made Resize_Migrating: State where the server is being moved to another host while resizing Resize_Migrated: State where the server has completed moving to another host while resizing 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 server is restarted Shutoff: State when Powering off is completed Verity_ Resize: After Resize_Prep due to a server type modification request, the server type is confirmed 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 creation	Create user Image from the current server’s Image For detailed Image creation method refer to Image creation
     Console Log	View current server’s console log You can check the console logs output by the current server. For more details, refer to Check Console Log.
     Dump creation	Create a dump of the current server The dump file is created inside the Virtual Server For detailed dump creation method, refer to Dump creation
     Rebuild	The OS area data and settings of the existing Virtual Server are deleted, and it is configured by rebuilding to a new server For details, refer to Rebuild Execution
     Service termination	Button to cancel the service

     Table. Virtual Server status information and additional functions

Detailed Information

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

Tag

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

Work History

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

Virtual Server Operation Control

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

Virtual Server Start

You can start a shutoff (Shutoff) Virtual Server. To start the Virtual Server, 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. Go to the Virtual Server list page.
3. Virtual Server List page, click the resource to start among the stopped (Shutoff) servers, and go to the Virtual Server Details page.
   • Virtual Server List page, you can start each resource via the right More button.
   • After selecting multiple servers with checkboxes, you can control multiple servers simultaneously via the Start button at the top.
4. Click the Start button at the top of the Virtual Server Details page to start the server. Check the changed server status in the Status Display item.
   • When the Virtual Server start is completed, the server status changes from Shutoff to Active.
   • For more details about Virtual Server status, see Virtual Server Detailed Information Check.

Virtual Server Stop

You can stop a Virtual Server that is active (Active). To stop the Virtual Server, 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 Virtual Server menu on the Service Home page. You will be taken to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to stop among the servers that are running (Active), and go to the Virtual Server Details page.
   • Virtual Server List page, you can Stop each resource via the right More button.
   • After selecting multiple servers with the check box, you can control multiple servers simultaneously using the Stop button at the top.
4. Click the Stop button at the top on the Virtual Server Details page to start the server. Check the changed server status in the Status Display item.
   • When the Virtual Server shutdown is completed, the server status changes from Active to Shutoff.
   • For detailed information about the Virtual Server status, please refer to Check Virtual Server detailed information.

Virtual Server Restart

You can restart the generated Virtual Server. To restart the Virtual Server, 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 Virtual Server menu on the Service Home page. You will be taken to the Virtual Server list page.
3. On the Virtual Server List page, click the resource to restart, and navigate to the Virtual Server Details page.
   • You can restart each resource via the right More button on the Virtual Server list page.
   • After selecting multiple servers with the check box, you can control multiple servers simultaneously via the Restart button at the top.
4. Virtual Server Details page, click the Restart button at the top to start the server. Check the status of the changed server in the Status Display item.
   • Virtual Server during restart, the server status goes through Rebooting and finally changes to Active.
   • For more details about Virtual Server status, refer to Virtual Server Detailed Information Check.

Virtual Server Resource Management

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

Image Create

You can create an image of a running Virtual Server.

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

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

2. Click the Virtual Server menu on the Service Home page. Go to the Virtual Server list page.

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

4. Virtual Server Details page, click the Create Image button. It navigates to the Create Image page.

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

     Category	Required	Detailed description
     Image name	Required	Name of the Image to create 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 Complete button.

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

Edit Server Type

You can modify the server type of the Virtual Server.

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

1. All Services > Compute > Virtual Server Click the menu. Go to the Service Home page of Virtual Server.
2. Click the Virtual Server menu on the Service Home page. Go to the Virtual Server list page.
3. Virtual Server List page, click the resource to control operation. Move to the Virtual Server Details page.
4. Virtual Server Details page, check the server status, and click the Edit button for server type. Server Type Edit popup opens.
5. Server Type Modification In the popup window, after changing the server type, click the Confirm button.
   • Virtual Server if you modify the server type, Virtual Server status changes to a state related to performing a resize.
   • For detailed information about the Virtual Server status, please refer to Check Virtual Server detailed information.

Change IP

How to change IP, please refer to IP Change.

ServiceWatch Enable detailed monitoring

Basically, Virtual Server is linked with ServiceWatch and basic monitoring. As needed, you can enable detailed monitoring to identify operational issues more quickly and take action. For more information about ServiceWatch, see ServiceWatch Overview.

To enable detailed monitoring of ServiceWatch on Virtual Server, 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 Virtual Server menu on the Service Home page. Navigate to the Virtual Server list page.
3. Virtual Server List page, click the resource to enable detailed ServiceWatch monitoring. Virtual Server Detail page.
4. Click the Edit button for ServiceWatch Detailed Monitoring on the Virtual Server Details page. It will navigate to the ServiceWatch Detailed Monitoring Edit popup.
5. ServiceWatch Detailed Monitoring Modification in the popup window, after selecting Enable, check the guidance text and click the Confirm button.
6. Virtual Server Details page, check the ServiceWatch detailed monitoring items.

ServiceWatch Disable detailed monitoring

To disable detailed monitoring of ServiceWatch on Virtual Server, 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 Virtual Server menu on the Service Home page. Navigate to the Virtual Server list page.
3. Virtual Server List page, click the resource to disable ServiceWatch detailed monitoring. Move to the Virtual Server Details page.
4. Click the ServiceWatch detailed monitoring Edit button on the Virtual Server Details page. You will be taken to the ServiceWatch detailed monitoring Edit popup.
5. ServiceWatch Detailed Monitoring Modification in the popup window after deselecting Activation, check the guidance text and click the Confirm button.
6. Virtual Server Details page, check the ServiceWatch detailed monitoring items.

Virtual Server Management Additional Features

Virtual Server can view console logs, generate dumps, and rebuild for server management. To view console logs, generate dumps, and rebuild the Virtual Server, follow the steps below.

Check console log

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

To check the console log of the Virtual Server, follow the steps below.

1. Click the All Services > Compute > Virtual Server menu. Go to the Service Home page of Virtual Server.
2. Service Home page, click the Virtual Server menu. Navigate to the Virtual Server list page.
3. Virtual Server list page, click the resource to view the console log. It moves to the Virtual Server details page.
4. Virtual Server Details page, click the Console Log button. It navigates to the Console Log 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 the steps below.

1. All Services > Compute > Virtual Server Click the menu. Navigate to Virtual Server’s Service Home page.
2. Click the Virtual Server menu on the Service Home page. You will be taken to the Virtual Server list page.
3. Click the resource to view detailed information on the Virtual Server List page. It navigates 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.

Rebuild perform

You can delete the OS area data and settings of the existing Virtual Server and rebuild it as a new server.

To perform a Rebuild of the Virtual Server, follow the steps below.

1. All Services > Compute > Virtual Server Click the menu. Go to the Service Home page of Virtual Server.
2. Service Home page, click the Virtual Server menu. Navigate to the Virtual Server list page.
3. Virtual Server List page, click the resource to perform Rebuild. Move to the Virtual Server Details page.
4. Virtual Server Details on the page click the Rebuild button.
   • During Virtual Server Rebuild, the server status changes to Rebuilding, and when the Rebuild is completed, it returns to the state before the Rebuild.
   • Virtual Server status detailed information, please refer to Virtual Server Check Detailed Information.

Virtual Server Cancel

If you terminate an unused Virtual Server, you can reduce operating costs. However, terminating a Virtual Server may cause the running service to stop immediately, so you should consider the impact of service interruption thoroughly before proceeding with the termination.

To cancel the Virtual Server, 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 Virtual Server menu on the Service Home page. Navigate to the Virtual Server list page.
3. Virtual Server list On the page, select the resource to cancel, and click the Cancel Service button.
   • The termination of connected storage depends on the Delete on termination setting, please refer to Termination Constraints.
4. When the termination is complete, check on the Virtual Server List page whether the resource has been terminated.

Termination Constraints

Virtual Server termination request cannot be processed, we will guide you with a popup window. Please refer to the cases below.

Termination of attached storage depends on the Delete on termination setting, please refer to it.

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. Image list 페이지에서 삭제할 자원을 선택하고, Delete 버튼을 클릭하세요.
   • 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.

2.2 - Keypair

The user can create the service by entering the required information of the Keypair in the Virtual Server service through the Samsung Cloud Platform Console and selecting detailed options.

Create Keypair

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

To create a key pair, follow these steps.

1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
2. Service Home page, click the Keypair menu. It moves to the Keypair list page.
3. Keypair list page, click the Create Keypair button. Move to the Create Keypair page.
   • Enter Service Information area, please enter the necessary information.

     Classification	Necessity	Detailed Description
     Keypair name	Required	Name of the Keypair to be created Enter within 255 characters using English, numbers, spaces, and special characters (-, _)
     Keypair type	mandatory	ssh

     Table. Keypair service information input items
   • Enter Additional Information Enter or select the required information in the area.

     Classification	Necessity	Detailed Description
     Tag	Selection	Add Tag Up to 50 can be added per resource Click the Add Tag button and enter or select Key, Value

     Table. Input items for adding Keypair information
     Caution

     • After creation is complete, you can download the Key only once for the first time. Since re-issuance is not possible, please check if it has been downloaded.
     • Please store the downloaded Private Key in a safe place.
4. Check the input information and click the Complete button.
   • Once creation is complete, check the created resource on the Keypair list page.

Check Keypair Details

The Keypair service allows you to view and modify the list of all resources and detailed information. The Keypair details page consists of details, tags, and operation history tabs.

To check the Keypair details, follow the following procedure.

1. All services > Compute > Virtual Server menu is clicked. It moves to the Service Home page of Virtual Server.
2. Service Home page, click the Keypair menu. It moves to the Keypair list page.
3. Keypair list page, click on the resource to check the detailed information. Move to the Keypair details page.
   • Keypair Details page displays status information and additional feature information, and consists of Details, Tags, Operation History tabs.

Detailed Information

On the Keypair list page, you can check the detailed information of the selected resource and modify the information if necessary.

Tag

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

Work History

Keypair list page where you can check the operation history of the selected resource.

Managing Keypair Resources

Describes the control and management functions of the Keypair.

Get Public Key

To import a public key, follow these steps.

1. Click All services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.

2. Service Home page, click the Keypair menu. It moves 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. This will move to the Import Public Key page.

   • Required Information Input Enter or select the necessary information in the required information input area.

     Classification	Necessity	Detailed Description
     Keypair name	Required	Name of Keypair to be created
     Keypair type	required	ssh
     Public Key	Required	Public Key Input File Upload: File Attach button to attach public key file Attached file only allows .pem file extension Public Key Input: Paste the copied public key value Public key value can be copied from Keypair Details page

     Table. Essential Input Items for Public Key Import

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

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

Delete Keypair

You can delete unused Keypairs. However, since deleted Keypairs cannot be recovered, please proceed with deletion after reviewing the impact in advance.

To delete a key pair, follow these steps.

1. All services > Compute > Virtual Server menu, click. Move to the Service Home page of Virtual Server.
2. On the Service Home page, click the Keypair menu. It moves to the Keypair list page.
3. Keypair list page, select the resource to be deleted, 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 deletion is complete, check the Keypair list page to see if the resource has been deleted.

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.

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

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

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.

   

2.7 - ServiceWatch Agent Installation

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

ServiceWatch Agent

The agents that need to be installed on the Virtual Server for collecting ServiceWatch’s custom metrics and logs can be divided into two main types. It is Prometheus Exporter and Open Telemetry Collector.

Installation of Prometheus Exporter for Virtual Server (for Linux)

Install the Prometheus Exporter according to the steps below for use on a Linux server.

Node Exporter Installation

Install Node Exporter according to the following steps.

1. Node Exporter User Creation
2. Node Exporter Settings

Node Exporter User Creation

Create a dedicated user to safely 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 Settings

1. Download to install Node Exporter. This guide provides the version below.
   • Download path: /tmp
   • Installation 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

2. Install the downloaded Node Exporter and grant permission to the executable file.

   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. Service file creation Set Node Exporter to collect memory metrics (meminfo) or block storage metrics (filesystem).

   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 metrics
     --collector.meminfo \             # Enable memory metrics
     --collector.filesystem            # Block Storage Enable 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 metrics
     --collector.meminfo \             # Enable memory metrics
     --collector.filesystem            # Block Storage Enable filesystem metrics
     
   Restart=on-failure
     
   [Install]
   WantedBy=multi-user.target

4. Service activation and start Register the Node Exporter service and check the registered service and configured metrics.
   Sample Code Download

   Copy Code

   Color mode

   sudo systemctl daemon-reload
   sudo systemctl enable --now node_exporter

   sudo systemctl daemon-reload
   sudo systemctl enable --now node_exporter

   Sample Code Download

   Copy Code

   Color mode

   sudo systemctl status node_exporter

   sudo systemctl status node_exporter

   Sample Code Download

   Copy Code

   Color mode

   curl http://localhost:9100/metrics | grep node_memory

   curl http://localhost:9100/metrics | grep node_memory