How-to guides

• 1: Image
• 2: Keypair
• 3: Server Group
• 4: IP Change
• 5: Linux NTP Setting
• 6: Setting up RHEL Repo and WKMS
• 7: ServiceWatch Agent Installation

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

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

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.

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

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

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.

   

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

Installation of Prometheus Exporter for Virtual Server (for Windows)

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

Windows Exporter Installation

Install the Windows Exporter according to the steps below.

1. Windows Exporter Settings

Windows Exporter Settings

1. Download the installation file to install Windows Exporter.
   • Download path: C:\Temp
   • Test version: 0.31.3
     Sample Code Download

     Copy Code

     Color mode

     $ mkdir /Temp
     $ Invoke-WebRequest -Uri "https://github.com/prometheus-community/windows_exporter/releases/download/v0.31.3/windows_exporter-0.31.3-amd64.exe" -OutFile "C:\Temp\windows_exporter-0.31.3-amd64.exe"

     $ mkdir /Temp
     $ Invoke-WebRequest -Uri "https://github.com/prometheus-community/windows_exporter/releases/download/v0.31.3/windows_exporter-0.31.3-amd64.exe" -OutFile "C:\Temp\windows_exporter-0.31.3-amd64.exe"

2. Windows Exporter execution test
   Windows Exporter enables all collectors by default, but to collect only the metrics you want, you need to enable the following collectors. Below is an example of enabling user-specified collectors.
   • Memory Metric: memory
   • Block Storage Metric: local_disk
   • Host name: os
     Sample Code Download

     Copy Code

     Color mode

     $ cd C:\Temp
     $ .\windows_exporter-0.31.3-amd64.exe --collectors.enabled memory,logical_disk,os

     $ cd C:\Temp
     $ .\windows_exporter-0.31.3-amd64.exe --collectors.enabled memory,logical_disk,os

3. Service Registration and Confirmation Register the Windows Exporter service and check the configured metrics.

   Sample Code Download

   Copy Code

   Color mode

   $ sc.exe create windows_exporter binPath= "C:\Temp\windows_exporter-0.31.3-amd64.exe --collectors.enabled memory,logical_disk,os" DisplayName= "Prometheus Windows Exporter" start= auto
   $ Start-Service windows_exporter

   $ sc.exe create windows_exporter binPath= "C:\Temp\windows_exporter-0.31.3-amd64.exe --collectors.enabled memory,logical_disk,os" DisplayName= "Prometheus Windows Exporter" start= auto
   $ Start-Service windows_exporter

   Sample Code Download

   Copy Code

   Color mode

   # Service Check
   $ Get-Service windows_exporter
     
   # Metric Check
   $ Invoke-WebRequest -Uri "http://localhost:9182/metrics" | Select-String memory

   # Service Check
   $ Get-Service windows_exporter
     
   # Metric Check
   $ Invoke-WebRequest -Uri "http://localhost:9182/metrics" | Select-String memory

4. Configuration File Settings

   • You can set it to use a YAML configuration file using the –config.file option.
     Sample Code Download

     Copy Code

     Color mode

     $ .\windows_exporter.exe --config.file=config.yml
     $ .\windows_exporter.exe --config.file="C:\Program Files\windows_exporter\config.yml" # If you use an absolute path, you must enclose the path in quotes.

     $ .\windows_exporter.exe --config.file=config.yml
     $ .\windows_exporter.exe --config.file="C:\Program Files\windows_exporter\config.yml" # If you use an absolute path, you must enclose the path in quotes.

     Sample Code Download

     Copy Code

     Color mode

     collectors:
       enabled: cpu,net,service
     collector:
       service:
         include: windows_exporter
     log:
       level: warn

     collectors:
       enabled: cpu,net,service
     collector:
       service:
         include: windows_exporter
     log:
       level: warn

• Windows Exporter > official example configuration file please refer.
  Sample Code Download

  Copy Code

  Color mode

  ---
  # Note this is not an exhaustive list of all configuration values
  collectors:
    enabled: cpu,logical_disk,net,os,service,system
  collector:
    service:
      include: "windows_exporter"
    scheduled_task:
      include: /Microsoft/.+
  log:
    level: debug
  scrape:
    timeout-margin: 0.5
  telemetry:
    path: /metrics
  web:
    listen-address: ":9182"

  ---
  # Note this is not an exhaustive list of all configuration values
  collectors:
    enabled: cpu,logical_disk,net,os,service,system
  collector:
    service:
      include: "windows_exporter"
    scheduled_task:
      include: /Microsoft/.+
  log:
    level: debug
  scrape:
    timeout-margin: 0.5
  telemetry:
    path: /metrics
  web:
    listen-address: ":9182"

  • Refer to the below to register a service using a configuration file.
    Sample Code Download

    Copy Code

    Color mode

    $ sc.exe create windows_exporter binPath= "C:\Temp\windows_exporter-0.31.3-amd64.exe --config.file=C:\Temp\config.yml" DisplayName= "Prometheus Windows Exporter" start= auto
    $ Start-Service windows_exporter

    $ sc.exe create windows_exporter binPath= "C:\Temp\windows_exporter-0.31.3-amd64.exe --config.file=C:\Temp\config.yml" DisplayName= "Prometheus Windows Exporter" start= auto
    $ Start-Service windows_exporter

Node Exporter metrics

Node Exporter Main Metrics

Below is the collector and metric information that can be checked through Node Exporter. You can set it as a Collector, or you can enable only specific metrics.

Node Exporter Collector and metric collection settings

Node Exporter enables most collectors by default, but you can enable/disable only the collectors you want.

Activate only specific Collector

• When you only want to use the memory and file system collectors:
  Sample Code Download

  Copy Code

  Color mode

  ./node_exporter
    --collector.meminfo            # Memory Collector activation
    --collector.filesystem         # File system Collector activation

  ./node_exporter
    --collector.meminfo            # Memory Collector activation
    --collector.filesystem         # File system Collector activation

• When you want to disable all Default settings and use only the memory and file system Collectors:
  Sample Code Download

  Copy Code

  Color mode

  ./node_exporter
    --collector.disable-defaults    # Disable default metrics
    --collector.meminfo             # Memory Collector activation
    --collector.filesystem          # File system Collector activation

  ./node_exporter
    --collector.disable-defaults    # Disable default metrics
    --collector.meminfo             # Memory Collector activation
    --collector.filesystem          # File system Collector activation

• Enable file system Collector for a specific mount point
  Sample Code Download

  Copy Code

  Color mode

  ./node_exporter
    --collector.disable-defaults    # disable default metrics
    --collector.filesystem.mount-points-include="/|/data"          # Activate file system Collector for /(Root) and /data mount points

  ./node_exporter
    --collector.disable-defaults    # disable default metrics
    --collector.filesystem.mount-points-include="/|/data"          # Activate file system Collector for /(Root) and /data mount points

• Enable file system Collector excluding specific mount points
  Sample Code Download

  Copy Code

  Color mode

  ./node_exporter
    --collector.disable-defaults    # disable default metrics
    --collector.filesystem.mount-points-exclude="/boot|/var/log"    # Enable file system Collector for /boot and /var/log mount points

  ./node_exporter
    --collector.disable-defaults    # disable default metrics
    --collector.filesystem.mount-points-exclude="/boot|/var/log"    # Enable file system Collector for /boot and /var/log mount points

Disable specific Collector (no-collector)

When you don’t want to use the file system collector:

./node_exporter --no-collector.filesystem

./node_exporter --no-collector.filesystem

Configure Collector with Systemd service (recommended)

[Unit]
Description=Node Exporter
After=network-online.target

[Service]
User=nodeexp
ExecStart=/usr/local/bin/node_exporter
  --collector.disable-defaults # Disable all default metric collectors
  --collector.meminfo
  --collector.filesystem

[Install]
WantedBy=multi-user.target

[Unit]
Description=Node Exporter
After=network-online.target

[Service]
User=nodeexp
ExecStart=/usr/local/bin/node_exporter
  --collector.disable-defaults # Disable all default metric collectors
  --collector.meminfo
  --collector.filesystem

[Install]
WantedBy=multi-user.target

How to filter only specific metrics

Through the Open Telemetry Collector configuration, you can set it to collect only the necessary metrics gathered from the Node Exporter. When you want to collect only specific metrics among those provided by a particular collector of Node Exporter, you can refer to Preconfiguration of Open Telemetry Collector for ServiceWatch.

Windows Exporter Metrics

Windows Exporter Main Metrics

Below is the collector and metric information that can be checked through Windows Exporter. You can set it as a Collector, or you can enable only specific metrics.

Windows Exporter Collector and metric collection settings

Windows Exporter enables most collectors by default, but you can configure only the collectors you want.

Activate only specific Collector

CPU, memory, when you want to use only logical disks:

# --collector.enabled option disables the default and activates only the specified Collector
.\windows_exporter.exe --collectors.enabled="memory,logical_disk"

# --collector.enabled option disables the default and activates only the specified Collector
.\windows_exporter.exe --collectors.enabled="memory,logical_disk"

Configure Collector as a service (recommended)

# Register windows_exporter as a service
sc.exe create windows_exporter binPath= "C:\Temp\windows_exporter-0.31.3-amd64.exe --config.file=C:\Temp\config.yml" DisplayName= "Prometheus Windows Exporter" start= auto
# Service Start
Start-Service windows_exporter

# Register windows_exporter as a service
sc.exe create windows_exporter binPath= "C:\Temp\windows_exporter-0.31.3-amd64.exe --config.file=C:\Temp\config.yml" DisplayName= "Prometheus Windows Exporter" start= auto
# Service Start
Start-Service windows_exporter

# Note this is not an exhaustive list of all configuration values
collectors:
  enabled: logical_disk,memory # collector settings to enable
collector:
  service:
    include: "windows_exporter"
  scheduled_task:
    include: /Microsoft/.+
log:
  level: debug
scrape:
  timeout-margin: 0.5
telemetry:
  path: /metrics
web:
  listen-address: ":9182"

# Note this is not an exhaustive list of all configuration values
collectors:
  enabled: logical_disk,memory # collector settings to enable
collector:
  service:
    include: "windows_exporter"
  scheduled_task:
    include: /Microsoft/.+
log:
  level: debug
scrape:
  timeout-margin: 0.5
telemetry:
  path: /metrics
web:
  listen-address: ":9182"

How to filter only specific metrics

Through the Open Telemetry Collector configuration, you can set it to collect only the necessary metrics collected from the Windows Exporter. When you want to collect only specific metrics among those provided by a particular collector of the Windows Exporter, you can refer to the Open Telemetry Collector pre‑configuration for ServiceWatch.