How-to guides

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

1 - Image

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

Create Image

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

To create an Image, follow the steps below.

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

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

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

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

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

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

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

     Table. Image additional information input fields

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

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

Check Image detailed information

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

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

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

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

     Table. Image status information and additional functions

Detailed Information

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

Tag

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

Job History

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

Image resource management

Describes the control and management functions of the generated Image.

Create shared Image

Create an Image to share with another Account.

To create a shared Image, follow the steps below.

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

Share Image to another Account

Create an Image to share with another Account.

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

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

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

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

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

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

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

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

   Table. Image sharing items to another account

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

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

Receive an Image shared from another Account

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

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

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

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

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

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

   Table. Image sharing request list item

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

Delete Image

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

To delete the Image, follow these steps.

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

2 - Keypair

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

Creating a Keypair

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

To create a keypair, follow these steps.

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

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

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

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

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

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

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

     Table. Keypair additional information input fields

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

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

View detailed information of the Keypair

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

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

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

Detailed Information

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

tag

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

Job History

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

Keypair Resource Management

Describes the control and management functions of a keypair.

Get public key

To retrieve the public key, follow these steps.

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

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

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

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

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

     Table. Required input fields for retrieving the public key

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

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

Delete Keypair

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

To delete a keypair, follow these steps.

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

3 - Server Group

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

Create Server Group

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

To create a Server Group, follow the steps below.

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

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

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

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

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

     Table. Server Group Service Information Input Items

     Reference

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

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

     Table. Server Group additional information input items

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

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

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

Check Server Group detailed information

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

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

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

Detailed Information

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

Tag

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

Job History

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

Delete Server Group

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

To delete a Server Group, follow these steps.

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

4 - Change IP

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

Change IP

You can change the IP of the Virtual Server.

To change the IP, follow these steps.

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

Configure IP on the server after adding a network port

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

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

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   ip a

   ip a

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

   Sample Code Download

   Copy Code

   Color mode

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

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

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

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

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

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

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

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

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   netplan --debug apply

   netplan --debug apply

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

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

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

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

5 - Configure Linux NTP

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

Installing NTP Daemon

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

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

   Sample Code Download

   Copy Code

   Color mode

   dnf list chrony

   dnf list chrony

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

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

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

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

   Copy Code

   Color mode

   dnf install chrony -y

   dnf install chrony -y

Configuring NTP Daemon

To configure the chrony daemon, follow these steps.

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

server 198.19.0.54 iburst

server 198.19.0.54 iburst

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

systemctl enable chronyd

systemctl enable chronyd

4. Restart the chrony daemon using the systemctl command.

   Sample Code Download

   Copy Code

   Color mode

   systemctl restart chronyd

   systemctl restart chronyd

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

   Sample Code Download

   Copy Code

   Color mode

   chronyc sources -v

   chronyc sources -v

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

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

210 Number of sources = 1



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

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

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

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

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

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

||                                                     ＼        |                   |  zzzz = estimated error.

||                                                        |       |                   ＼

MS Name/IP address                  Stratum   Poll   Reach   LastRx   Last    sample

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

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

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

210 Number of sources = 1



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

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

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

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

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

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

||                                                     ＼        |                   |  zzzz = estimated error.

||                                                        |       |                   ＼

MS Name/IP address                  Stratum   Poll   Reach   LastRx   Last    sample

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

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

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

   Copy Code

   Color mode

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

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

6 - Configure RHEL Repo and WKMS

RHEL Repository Configuration Guide

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

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

   Sample Code Download

   Copy Code

   Color mode

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

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

   Sample Code Download

   Copy Code

   Color mode

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

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

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

     Copy Code

     Color mode

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

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

     Sample Code Download

     Copy Code

     Color mode

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

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

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

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

   Sample Code Download

   Copy Code

   Color mode

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

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

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

   Sample Code Download

   Copy Code

   Color mode

   yum repolist –v

   yum repolist –v

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

     Copy Code

     Color mode

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

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

Windows Key Management Service Configuration Guide

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

1. Right-click the Windows Start icon, then run cmd from Windows PowerShell (Administrator) or the Windows Run menu.

2. In Windows PowerShell (Administrator) or cmd, please register the KMS Server by running the command below.

   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, confirm the notification popup indicating successful registration, then click OK.

   

4. In Windows PowerShell (Administrator) or cmd, run the command below to activate the product.

   Sample Code Download

   Copy Code

   Color mode

   slmgr /ato

   slmgr /ato

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

   

6. Please run the command below in Windows PowerShell (Administrator) or cmd to verify that activation has been completed.

   Sample Code Download

   Copy Code

   Color mode

   slmgr /dlv

   slmgr /dlv

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

   

7 - Install ServiceWatch Agent

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

ServiceWatch Agent

The agents that must be installed on a Virtual Server to collect ServiceWatch’s custom metrics and logs can be divided into two main types. It is the Prometheus Exporter and OpenTelemetry Collector.

Pre-configuration for Using ServiceWatch Agent

To use the ServiceWatch Agent, please refer to ServiceWatch Agent를 위한 사전 환경 설정 and prepare the prerequisite configuration.

Install Prometheus Exporter for Virtual Server (for Linux)

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

Node Exporter installation

Install Node Exporter according to the steps below.

1. Node Exporter User Creation
2. Node Exporter configuration

Create Node Exporter User

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

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

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

Node Exporter configuration

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

   • Tab 0

   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

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

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

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

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

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

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

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

   • Tab 0

   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 filesystem metrics enable
   
   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 filesystem metrics enable
   
   Restart=on-failure
   
   [Install]
   WantedBy=multi-user.target

4. Service activation and start Register the Node Exporter service and verify the registered service and configured metrics.
   • Tab 0

   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

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   sudo systemctl status node_exporter

   sudo systemctl status node_exporter

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

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

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

Install Prometheus Exporter for Virtual Server (for Windows)

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

Install Windows Exporter

Install the Windows Exporter following the steps below.

1. Windows Exporter 설정

Windows Exporter configuration

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

     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. The following is an example that activates a collector specified by the user.
   • Memory metric: memory
   • Block storage metric: local_disk
   • Host name: os
     • Tab 0

     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 verification Register the Windows Exporter service and verify the configured metrics.

   • Tab 0

   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

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

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

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

4. Configuration file settings

   • You can set it to use a YAML configuration file by using the –config.file option.
     • Tab 0

     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.

     • Tab 0

     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

   • Please refer to Windows Exporter > Official Example Configuration File.
     • Tab 0

     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 following to register a service using a configuration file.
     • Tab 0

     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

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

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

• 메모리, 파일 시스템 Collector만 사용하고 싶을 때:
  • Tab 0

  Sample Code Download

  Copy Code

  Color mode

  ./node_exporter
    --collector.meminfo
    --collector.filesystem

  ./node_exporter
    --collector.meminfo
    --collector.filesystem

• Default 설정은 모두 해제하고 메모리, 파일 시스템 Collector만 사용하고 싶을 때:
  • Tab 0

  Sample Code Download

  Copy Code

  Color mode

  ./node_exporter
    --collector.disable-defaults
    --collector.meminfo
    --collector.filesystem

  ./node_exporter
    --collector.disable-defaults
    --collector.meminfo
    --collector.filesystem

  Enable file system Collector for a specific mount point
  • Tab 0

  Sample Code Download

  Copy Code

  Color mode

  ./node_exporter
    --collector.disable-defaults
    --collector.filesystem.mount-points-include="/|/data"

  ./node_exporter
    --collector.disable-defaults
    --collector.filesystem.mount-points-include="/|/data"

  Enable the file system Collector, excluding specific mount points
  • Tab 0

  Sample Code Download

  Copy Code

  Color mode

  ./node_exporter
    --collector.disable-defaults
    --collector.filesystem.mount-points-exclude="/boot|/var/log"

  ./node_exporter
    --collector.disable-defaults
    --collector.filesystem.mount-points-exclude="/boot|/var/log"

파일 시스템 collector를 사용하고 싶지 않을때:

./node_exporter --no-collector.filesystem

./node_exporter --no-collector.filesystem

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

[Service]
User=nodeexp
ExecStart=/usr/local/bin/node_exporter
  --collector.disable-defaults
  --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
  --collector.meminfo
  --collector.filesystem

[Install]
WantedBy=multi-user.target

You can configure the Open Telemetry Collector to select and 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, ServiceWatch를 위한 Open Telemetry Collector 사전 설정

#Windows Exporter metrics

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

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

CPU, 메모리, 논리 디스크만 사용하고 싶을 때:

#--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"

#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:
  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:
  service:
    include: windows_exporter
  scheduled_task:
    include: /Microsoft/.+
log:
  level: debug
scrape:
  timeout-margin: 0.5
telemetry:
  path: /metrics
web:
  listen-address: ":9182"

Through the Open Telemetry Collector configuration, you can set it to collect only the required metrics gathered from the Windows Exporter. When you want to collect only specific metrics among those provided by a particular collector of the Windows Exporter, [ServiceWatch를 위한 Open Telemetry Collector 사전 설정](/userguide/management/service_watch/how_to_guides/service_watch_agent/