This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

User Guide

1 - Samsung Cloud Platform

1.1 - New Features

New feature

Let’s take a look at the new features of Samsung Cloud Platform Console~

Resource Management using Copilot

account

Information about resources/services

create
copilot

Account and Favorites Accessibility Improvements

documentation

Providing services for large-scale organizations and systematic user management

archtecturediagram

LLM service that can be used without separate application

searchservice

1.2 - Overview

Samsung Cloud Platform

Samsung Cloud Platform is a cloud environment that virtualizes and provides various resource pools such as computing, storage, networking, and database required by companies.

Through the Samsung Cloud Platform, you can use the necessary resources in the cloud environment without having to equip hardware or physical space. The fee is charged according to the actual usage, so efficient budget operation is possible, and companies can reduce the cost of building and managing their own server environment.

The main terms used in Samsung Cloud Platform are as follows.

Term
Detailed Description
A region is a geographically separated unit of cloud service provision, consisting of one or more data centers to ensure availability
AccountThe basic unit and billing unit required to use Samsung Cloud Platform services
Root UserThe user who created the account, with the highest authority
IAM UserA user created by the Root user within the Account with limited privileges
ServiceVarious types of IT services and infrastructure (Compute, Storage, Network, etc.) provided by Samsung Cloud Platform
ResourceAn individual unit object (Entity) created and managed by the user while using the service
Fig. Samsung Cloud Platform key terms

Components

Samsung Cloud Platform provides Service Portal, Console, Documentation.

Classification
Detailed Description
Service PortalIntroduction to services and fees for Samsung Cloud Platform, providing information such as customer support
ConsoleSamsung Cloud Platform’s account and resource creation, cost verification, and other features are provided through a self-service interface
DocumentationSamsung Cloud Platform’s integrated documentation service that provides user guides, API/CLI references, etc.
Fig. Samsung Cloud Platform configuration components

Region

A region is a geographically separated unit of cloud service provision, consisting of one or more data centers to ensure availability. Services provided by Samsung Cloud Platform are managed and provided on a region-by-region basis, so some services may differ. Please refer to the user guide for each service.

Region NameRegion
West KoreaKorea West(kr-west1)
South Korea (administrative)South Korea south1(kr-south1)
South Korea (public)South Korea south2(kr-south2)
South Korea (Internet)South Korea South3(kr-south3)
Table. Samsung Cloud Platform provided region items

Account

To use the Samsung Cloud Platform, account creation is necessary, and you can create an account through membership registration. The user who creates an account through membership registration is the root user of the account and is responsible for paying the account’s fees. By registering a payment method through membership registration, resource creation is possible.

The Root user can create a user in IAM and add it to a user group, and the user created in this way is an IAM user.

The general flow from creating an Account to configuring a cloud environment and performing tasks is as follows.

  1. When the user signs up, an account is created and becomes the root user.
  2. When the Root user registers a payment method, they can create resources on the Samsung Cloud Platform.
  3. The Root user creates an IAM user and adds it to a user group to perform tasks according to each authority.
  4. IAM users apply for necessary services according to their purpose and perform tasks.

The detailed tasks for each role are as follows.

RoleResponsible Task
Root userAccount’s top-level authority user
  • Can manage all resources within the Account.
  • Can create and manage IAM users, user groups, and policies.
IAM userA user with limited privileges within an Account
  • Can manage resources only within the permissions set by the Root user
  • Can prevent unnecessary access to resources by granting only the necessary permissions
Table. Role and Responsibilities

1.3 - Getting Started with Console

1.3.1 - Login

To use the Samsung Cloud Platform Console, Account creation is required, and you can create an Account through membership registration. The user who creates an Account through membership registration is the root user of the Account and is responsible for paying the Account’s bills. After registering for membership and registering a payment method, resource creation is possible. For more information, see Registering a payment method.

Note
Root users can create users in Management > IAM and add them to user groups. Users created in this way can log in as IAM users. For more information on user creation, see IAM.

Join membership

To use the Samsung Cloud Platform Console, account creation is necessary, and you can create an account through membership registration. To create an account on the Samsung Cloud Platform Console, follow the procedure below.

  1. On the login page, select the user type as Root User and then click the Sign Up button. It moves to the Sign Up page.
  2. Member registration page where you can proceed with identity verification.
  • Once the self-authentication is completed, click the next button.
    Item
    Mandatory
    Description
    Automatic input preventionRequiredEnter the characters output in the image into the input window
    Mobile phone numberRequiredEnter mobile phone number
    • Enter the mobile phone number and click the authentication button to issue an authentication number
    • Enter the authentication number issued to your mobile phone and click the confirm button
    • If the authentication number is valid, the identity verification is complete
    Table. Personal Authentication Information
  • Enter membership information and select regional information, and agree to the terms.
    Item
    Mandatory
    Description
    RegionRequiredSelect joiner region
    Service Terms AgreementRequiredCheck whether the service terms agreement is accepted
    Personal information collection and usage agreementRequiredCheck for personal information collection and usage agreement
    Personal Information Overseas Transfer ConsentRequiredCheck for personal information overseas transfer consent
    Are you 14 years old or older?RequiredCheck if you are 14 years old or older
    Personal Information Collection and Usage AgreementSelectCheck for Personal Information Collection and Usage Agreement
    Table. Input information for membership registration
  • Member Information Input where you enter required item information.
    Item
    Mandatory
    Description
    ID(email)requiredemail to be used as subscriber ID
    UsernameRequiredSubscriber name
    • Can be entered within 60 characters using Korean and English, numbers, and spaces
    Account nameRequiredAccount that the subscriber will use
    • Can be entered within 60 characters using Korean and English, numbers, and spaces
    PasswordRequiredThe password that the member will use can be entered within 9-20 characters
    • Must include at least one uppercase letter (English), lowercase letter (English), number, and special character (! @ # $ % & * ^)
    • ID cannot be used as password
    • Same character cannot be used more than 3 times
    • Easy-to-guess passwords cannot be used
      • Continuous characters/numbers of 4 or more characters cannot be used
    • Password change cycle: 90 days
    Password ConfirmationRequiredConfirmation of the password to be used by the member
    Mobile phone numberRequiredMobile phone number used for self-authentication
    Notification LanguageRequiredNotification language setting such as email, SMS, etc. provided by Samsung Cloud Platform
    • Changed in Notification Popover > Notification Settings after logging in
    Table. Member Information Input
  1. After entering all the information and clicking the completion button, a verification email will be sent to the entered email address.
  • After receiving the mail, click the authentication button to complete membership registration.

Log in

Samsung Cloud Platform Console has two types of user types: Root user and IAM user. The Root user is the user who created the Account that performs tasks that require unlimited access rights. The IAM user is a user within the Account that performs daily tasks, and the Root user can create an IAM user. For more information related to user creation, please refer to IAM.

Root user login

To log in to the Samsung Cloud Platform Console as a root user, follow these procedures.

  1. On the login page, select the user type as Root user and enter the ID(email), then click the Next button.
  2. Root user login page moves. Password should be entered.
  3. Select the means to send the authentication number and click the Send Authentication Number button.
  4. Enter the received authentication number and click the login button.
  5. If you log in successfully, it moves to the Console Home page.
ID/Password Find
ID or password was lost in case ID/password search button to click, account information after checking, try to log in.
Caution
  • Please enter your password and authentication number correctly. If you enter your password or authentication number incorrectly more than 5 times, your account will be locked for security reasons.
  • If the account is locked, it provides the user with the locked account information.
  • If the allowed access IP is set, login through unallowed IP is not possible. Click the Access allowed IP not set item to release the IP restriction.
  • If you have logged in after releasing the allowed IP setting, please move to the Management > IAM > My info. page to reset for security reasons. For more information, please refer to Access IP Management.

IAM user login

To log in to the Samsung Cloud Platform Console as an IAM user, follow these procedures.

  1. On the login page, select the user type as IAM user and enter Account information, then click the Next button.
Reference
Account information requires entering an Account ID or Account alias. Account information is provided by the Root user.
  1. IAM User Login page moves. Enter the IAM Username and Password.
  2. Select Authentication method, and click the next button.
  3. Enter the received authentication number and click the next button.
  4. If you log in successfully, it moves to the Console Home page.
Note
In the case of IAM users, when the ID or password is lost, you must contact the Root user, and for the password, you must request the Root user to initialize the password.
Caution
  • Please enter the password and authentication number correctly. If you enter the password or authentication number incorrectly more than 5 times, the account will be locked for security reasons.
  • If the account is locked, it delivers the locked account information to the user or administrator.
  • If the allowed access IP is set, login through unallowed IP is not possible. Click the Access allowed IP not set item to release the IP restriction.
  • If you have logged in after releasing the allowed IP setting, please move to the Management > IAM > My info. page to reset for security reasons. For more information, please refer to Access IP Management.

Switch to user

You can switch to the Root user or an IAM user after logging in to the Samsung Cloud Platform Console.

Guidance
Root user and IAM user’s email and phone number must be the same in order to switch users after logging in.

To switch users, follow the following procedure.

  1. Console Home page, click the Switch User button to the right of the Account name. The Switch User popup window opens.
  2. Click the user name you want to change among the account-by-user names. A pop-up window notifying user switching will open.
  3. Check the user name and then click the Confirm button. The user switch is completed and moves to the Console Home page.

Console language change

You can set the language to be used in the Samsung Cloud Platform Console.

  1. from the login page to change
  • To change the language displayed on the Samsung Cloud Platform Console, click the language to be used on the top right of the login page and select the language to use, then log in.
  1. Change from the Console page
  • If you are logged in to the Samsung Cloud Platform Console, you can change the language by clicking the language at the bottom of the page.

Modify user information

You can change user information such as username, password, mobile phone number, etc.

To modify user information, click My menu > My Info. on the top right of the Console.

1.3.2 - Console

When you first log in to the Samsung Cloud Platform Console, you will be taken to the Console page.

Console

On the Console page, you can view the Console Home page and configure the widgets of Console Home. Additionally, you can view the list of all services of Samsung Cloud Platform. The Console left menu’s Console Home and All Services provide the functions below.

Provided FeaturesDescription
Console HomeIn the Console Home of the Console, it provides important information about the Samsung Cloud Platform and provides shortcut widgets for services
  • For detailed information about Console Home, see Console Home
All ServicesCheck all Samsung Cloud Platform service categories and service list in the Console and navigate to the respective service
  • For detailed information about all services, see All Services
Table. Console Home Function

Console Home

When you first log in to the Samsung Cloud Platform Console you are taken to the Console page and on the Console page the Console Home page is shown by default.
Console Home is composed of widgets, and can be changed by clicking the Dashboard Settings button at the top right.

Provided FeaturesDescription
WelcomeGreeting and Samsung Cloud Platform text introduction
  • My Info., Documentation, Notification List button is provided
Recent Visited ServiceList of services visited recently
  • Click the service name to go to that service
CopilotIntroduction to Copilot or list of conversations with Copilot
  • Click the conversation list to go to Copilot
  • For detailed information about Copilot, see Copilot
Architecture DiagramProvide resource information in diagram form to grasp the relationships between resources at a glance
  • In Console Home, provides three types of resources: VPC, Subnet, and Virtual Server
  • When a specific resource is clicked, the main information of the resource can be viewed directly without navigating to the resource detail screen
NoticeSamsung Cloud Platform Console Notice
Payment method registrationPayment method registration possible to use all resources of the Samsung Cloud Platform Console
  • Widget not displayed after payment method registration is completed
Support CenterA service that provides technical support, standard architecture, incident response, service inquiries/answers, etc., needed when using the Samsung Cloud Platform Console
  • Service request, inquiry, Knowledge Center provided
This month’s usage and estimated amountPredict this month’s estimated amount and check the billing amount
  • Provides this month’s usage amount, last month’s usage amount, end-of-month billing estimate, recent 6-month average amount details, and this month’s usage amount by service category
User Access TrendDaily user access count including duplicates for the past week
Service StatusService status by service category
  • When you select a service category, you can view the status of each service
  • Click the number of each service to go to that service
This month’s carbon emissionsCarbon emission data generated when using services of the Samsung Cloud Platform Console
  • Carbon emissions, monthly carbon emission trends, carbon emissions by service group, and carbon emissions by account can be viewed
Table. Console Home widget items
Note
Among the widgets of Console Home, users can rearrange them except the Welcome widget. For more details, see Dashboard Settings.

Setting up the Dashboard

  1. From the Console page, click Console Home in the left menu. You will be taken to the Console Home page.
    • When you first log in, the default page is the Console > Console Home screen.
  2. Console Home page, click the Dashboard Settings button at the top right. Dashboard Settings popup opens.
  3. Dashboard Settings In the popup’s Widget Settings, change the items and order of the widgets displayed on Console Home.
    • Welcome The other widgets, except the Welcome widget, can have their settings changed by the user.
    • If you select the widget’s checkbox, you can add it to the dashboard, and if you deselect the checkbox, you can remove it from the dashboard.
    • You can change the order by clicking and holding the hamburger button next to the widget name and moving it up or down.
  • Dashboard Settings popup window’s Widget Settings when Select All is selected, all widgets are selected. When Select All is deselected, all widgets except Welcome are deselected.
  1. Dashboard Settings in the popup window’s Preview, after checking the widget changes, click the Save button.
    • The configured widget can be previewed on the right.
  2. Console Home Check the changed settings on the page.

All Services

You can view the service categories and service list provided by Samsung Cloud Platform at a glance. And you can navigate to the respective service.

1.3.3 - Integrated Management

Integrated management means the collection of functions located at the top of the Samsung Cloud Platform Console.

Integrated Management Function

In Integrated Management, you can view the list of services and see the list of services you recently visited. You can converse with Copilot, and you can check notifications received in the Samsung Cloud Platform Console. You can view the region of the Samsung Cloud Platform and see the list of regions that can be changed. In the My menu, you can view the user’s information and Account information.

CategoryDetailed description
ServiceSearch for Samsung Cloud Platform services, etc., and go to the service
  • For detailed information about Service, see Service
CopilotCopilot provided by Samsung Cloud Platform
  • For detailed information about Copilot, see Copilot
Unified SearchSearch Samsung Cloud Platform services, internal Console documents, Marketplace, etc.
NotificationCheck notifications received from Samsung Cloud Platform Console
  • For detailed information about Notification, see Notification
SupportSupport Center, Documentation, Can navigate to Announcements
  • Support for detailed information Support see
RegionYou can view the region of Samsung Cloud Platform and check the list of regions that can be changed
  • For detailed information about Region, see Region
My MenuUser and Account Information Check
  • My Menu for detailed information see My Menu
Table. Integrated Management Items
Reference
Copilot is only available in Korea West (kr-west1) and Korea East (kr-east1).

Service

You can search for services provided by Samsung Cloud Platform by keyword, service category, recent visits, favorites, etc., and navigate to the service.

CategoryDetailed description
Search term lookupLookup using the search term within the service
  • Lookup service name and service description using the entered search term
  • Search possible when entering two or more characters
Recent VisitsList of recently visited services
  • List of recently visited services and service description
FavoritesList of bookmarked services
All servicesA list where all services are sorted in ascending order
Table. Service Items

Add to Favorites

You can add the service to favorites.

  1. Click the Service button at the top of the Console. It moves to the Service popup window.
  2. Service In the popup window, search for the service to add to favorites from All Services or Recent Visits. Click the star icon to the left of the service name you want to add to favorites.
    • Please check that the star shape has been changed to yellow.
  3. Service > Favorites you can check the services you added to favorites.
    • You can also view the services you added to favorites at the top of the Console.

Check Favorites

You can view the services added to your favorites and navigate to the respective service.

  1. Click the Service button at the top of the Console. It will move to the Service popup window.
  2. In the service popup window, click bookmark. You can check the services added to your favorites.
  3. Service > Favorites Click the name of the service you want to move to. It will navigate to that service.

Remove from Favorites

You can remove a service added to your favorites.

  1. Click the Service button at the top of the Console. Service page will open.
  2. Service in the popup window, click Bookmark. You can check the services added to your bookmarks.
  3. Please deselect the star icon to the left of the service name you added to favorites.
  • You can deselect the star icon to the left of the service name anywhere within all services, etc., service.
  1. In Service > Favorites, you can confirm that the service you unfavorited has been removed.
    • Console also at the top, the unfavorited service will be removed.

Copilot

Copilot is a generative AI-based conversational assistant that can help you understand, build, scale, and operate the Samsung Cloud Platform. You can start a conversation with Copilot by clicking the Copilot icon in the Samsung Cloud Platform Console.

For more details, refer to Copilot. Below are some example questions you can ask Copilot.

Example question

  • How can I check the estimated charges?
  • How do I create a Virtual Server?
  • Please show the list of Virtual Server resources of my Account.
  • Find the 192.168.21.1 IP among Virtual Server
  • How do I add a user to a user group?
  • Download cost details
  • What is the estimated bill amount for this month?
Reference
Copilot is only available in Korea West (kr-west1) and Korea East (kr-east1).

Integrated Search

You can easily find services and documents provided by Samsung Cloud Platform using integrated search.

To find the desired service or document using integrated search, follow these steps.

  1. Enter the keyword you want to search for in the integrated search box. A search results popup will open.
    • When you enter a keyword in the integrated search box, the keyword is auto-completed and a popup window with the search results for the completed keyword opens.
    • If you click the View All button in the search results category, the full results searched in that category will be displayed.
      CategoryDetailed description
      Service, Condole documents, MarketplaceEnter at least two characters for the keyword you want to search
      Resource Name, Resource IDEnter the resource name or resource ID you want to find in the form / + resource name (or resource ID)
      • Enter at least two characters for the resource name (or resource ID)
      Table. How to input keywords for each search item
  2. Click the information to be checked in the search result popup window. It will move to the corresponding page.
Reference

The scope that can be found with integrated search is as follows.

  • Services and resource names, resource IDs within Samsung Cloud Platform
  • User guide documents: How-to guides, API reference, CLI reference
  • Knowledge Center
  • Marketplace

Notification

You can view notifications received from the Samsung Cloud Platform Console, and you can go to the notification settings.

CategoryDetailed description
Notification ListLatest 10 notifications received from Samsung Cloud Platform Console
  • Click the View All Notifications button to go to the Notification popup window
  • All: Latest 10 of all received notifications
  • Unread: Latest 10 unread notifications among all received
  • Mark All as Read: Mark all received notifications as read
Notification SettingsClick the Notification Settings button to move to the Notification popup’s Notification Settings
Table. Notification List Items

Check notification details

  1. Click the Notification button at the top right of the Console to view the latest 10 notifications received in the Console.
  2. When you select a specific notification item from the latest 10 notifications list, you will be taken to the notification detail popup.
    CategoryDetailed description
    Resource NameName of the resource where the alert occurred
    Notification TypeNotification Occurrence Type
    • Announcement: Notification received about announcements
    • Service: Notification received per service
    • Cost Management: Notification received about Cost Management
    • IAM: Notification received about IAM
    • Notification Manager: Notification received about Notification Manager
    • Support: Notification received about Support such as inquiries, service requests, etc.
    CreatorNotification Creator
    Notification creation timeNotification creation time
    Table. Notification detailed information items

Check Notification Settings

  1. If you click the Notification button at the top right of the Console, you can view the list of the latest 10 notifications received in the Console.
  2. Click the Notification Settings button next to Notification. It moves to the Notification > Notification Settings popup.
  3. Notification > Notification Settings You can check the notification settings status in the popup window.
    CategoryDetailed description
    Notification languageLanguage to receive notifications
    Notification Target > Notification TypeNotification Types by Target
    • Announcements: Notifications received about announcements
    • Service: Notifications received per service
    • Cost Management: Notifications received about Cost Management
    • IAM: Notifications received about IAM
    • Notification Manager: Notifications received about Notification Manager
    • Support: Notifications received about Support such as inquiries, service requests, etc.
    Table. Notification Settings Items

Edit notification settings

  1. Click the Notification button at the top right of the Console to view the list of the latest 10 notifications received in the Console.
  2. Click the Notification Settings button next to Notification. It moves to the Notification > Notification Settings popup window.
  3. Notification > Notification Settings You can check the notification settings status in the popup window.
  4. Notification > Notification Settings in the popup window, click the Edit button to modify the notification settings.
    CategoryDetailed description
    Notification languageLanguage to receive notifications
    Notification Target > Notification TypeFor each notification target, you can select the notification type to receive (email, SMS). The default setting is email
    • Announcements: Notifications received about announcements
    • Service: Notifications received per service
    • Cost Management: Notifications received about Cost Management
    • IAM: Notifications received about IAM
    • Notification Manager: Notifications received about Notification Manager
    • Support: Notifications received about Support such as inquiries, service requests, etc.
    Table. Notification Settings Modification Items

Support

In support, we provide Support Center, Documentation, Announcements.

  • Support Center provides technical support, standard architecture, incident response, service inquiries/answers, etc., needed when using Samsung Cloud Platform. Please refer to Support Center.
  • Documentation is a user guide that provides easy and clear guidance on concepts of various services, Console usage, and utilization methods. Please refer to User Guide.
  • Notice is a notice provided to users in the Samsung Cloud Platform Console.

Region

You can check the region of Samsung Cloud Platform and view the list of regions that can be changed.

The services provided by Samsung Cloud Platform are managed on a per-region basis, so the services offered may differ slightly. A region is a geographically separated unit of cloud service provision, consisting of one or more data centers to ensure availability. For some services such as the Samsung Cloud Platform Console or IAM, there is no need to select a region as they are global services.

Region NameRegion
Global-
Korea WestKorea West(kr-west1)
Korea EastKorea East(kr-east1)
South Korea (administrative)South Korea 1(kr-south1)
South Korea (public)South Korea2(kr-south2)
South Korea (Internet)South Korea 3(kr-south3)
Table. Console region selectable items

My menu

Click the profile-shaped button at the top right of the Console to view the functions provided in the My menu. You can check the Account ID, IAM username, or Root username, and you can navigate to Account, My Info., Cost Management.

Provided FeaturesDescription
Account IDAccount ID logged into Samsung Cloud Platform Console
IAM username or Root usernameIAM username or Root username logged into Samsung Cloud Platform Console
Time zoneUser-set time zone
  • Example: Asia/Seoul (GMT +09:00)
AccountAccount information
  • For detailed information, refer to Account
My Info.Provides basic user information and authentication key management functions
Cost ManagementYou can view usage and billing details, payment details, cost analysis, and manage Credit, budget, Account, payment methods
Role SwitchingCan switch to another role
LogoutLogout from Samsung Cloud Platform Console
Table. My Info. Item

1.4 - Copilot

Copilot Overview

Through the generative AI-based work assistance service Copilot, you can use Samsung Cloud Platform more conveniently. Users can easily utilize Copilot using familiar interfaces and natural language, allowing them to conduct work accurately and efficiently.

You can start a conversation with Copilot by clicking the Copilot button in the Samsung Cloud Platform Console.

Ask Tip
  • Clearly describe the reason for requesting the task and the ultimate goal in order to obtain an accurate answer.
  • To solve complex problems, we request small and easy requirements step by step.
  • We utilize the terminology used in Samsung Cloud Platform.
Caution
  • Since sensitive information related to work cannot be used, please be careful not to input it.
  • Answers generated based on generative AI may contain inaccurate content, so be sure to review them before use.
  • For general questions related to Samsung Cloud Platform, select General Query, and for questions about the resources you are using, select Resource Lookup and ask.

Using Copilot

You can use Copilot via the Copilot button at the top of the Samsung Cloud Platform Console and the Copilot button at the bottom right.

You can also use Copilot through the Copilot widget on the Dashboard of the Console Home page, which is the first login screen of the Samsung Cloud Platform Console.

  1. Click the Copilot button at the top of the Console. The Copilot popup window opens.
  2. Copilot Check the popup window. The features provided by Copilot are as follows.
    CategoryDetailed description
    Ask > General InquiryGeneral questions about using Samsung Cloud Platform
    • Example questions
      • How do I create a Virtual Server?
      • How can I check the estimated charges?
      • What is the estimated bill for this month?
    Ask > Resource LookupQuestions about resources used in Samsung Cloud Platform
    • Example question
      • Please show the list of Virtual Server resources in my Account.
      • Find the 192.168.21.1 IP among Virtual Servers
    Start New ConversationStart a new conversation
    View in new windowDisplay Copilot popup in a new tab
    Conversation ListCheck the list of previous conversations
    Recommended PromptList of recommended questions from Copilot
    Table. Copilot provided features
    Reference Tip
    • When you drag text in the Samsung Cloud Platform Console, the Copilot button appears. Click the Copilot button to search the text via Copilot.
    • If you click the info button displayed next to the item on the creation page of each service, detailed guidance is provided through Copilot.

General Query

Through Copilot, you can ask general questions about the features, usage, etc. provided by Samsung Cloud Platform.

To make a general query to Copilot, follow the steps below.

  1. Click the Copilot button at the top of the Console. The Copilot popup window opens.
  2. Copilot In the bottom prompt of the popup window, select General Query and ask overall questions about Samsung Cloud Platform.
  • example question
    • Service that must be created in advance before creating Virtual Server
    • What network settings are required to create a Virtual Server?
Ask Tip
  • Clearly describe the reason for requesting the task and the ultimate goal in order to obtain an accurate answer.
  • To solve complex problems, we request small and easy requirements step by step.
  • Use the terminology used in Samsung Cloud Platform.
Caution
  • Please be careful not to input any sensitive information related to work as it cannot be used.
  • Answers generated based on generative AI may contain inaccurate information, so be sure to review them before using them.
  • For overall questions regarding Samsung Cloud Platform, please select General Query, and for questions about the resources you are using, select Resource Lookup.

Resource View

You can ask questions about resources created on the Samsung Cloud Platform through Copilot.

To ask Copilot a question related to Resource, follow the steps below.

  1. Click the Copilot button at the top of the Console. The Copilot popup window opens.
  2. Copilot In the bottom prompt of the popup window, select View Resource and ask a question about resources on Samsung Cloud Platform.
  • example question
    • Virtual Server Please show the list.
    • Active state Load Balancer
Ask Tip
  • Clearly describe the reason for requesting the work and the final goal in order to provide an accurate answer.
  • To solve complex problems, we request small and easy requirements step by step.
  • Use the terminology used in Samsung Cloud Platform.
Caution
  • Please be careful not to enter sensitive information related to work, as it cannot be used.
  • Answers generated based on generative AI may contain inaccurate content, so be sure to review them before use.
  • For general questions related to Samsung Cloud Platform, select General Inquiry, and for questions about the resources you are using, select Resource Lookup and please ask.

Start a new conversation

You can start a new conversation with Copilot.

To start a new conversation with Copilot, follow the steps below.

  1. Click the Copilot button at the top of the Console. Copilot popup window opens.
  2. Copilot Click the Start New Conversation button at the top right of the popup window. A new conversation will begin.

Check conversation list

You can view the list of conversations you had with Copilot.

To view the list of conversations with Copilot, follow the steps below.

  1. Click the Copilot button at the top of the Console. The Copilot popup window opens.
  2. Copilot Click the Conversation List button at the top left of the popup window. The Conversation List expands.
  3. Conversation List If you click the conversation you want to check among them, you will be taken to that conversation.

You can view the recommended prompt questions provided by Copilot.

To check the Copilot recommended prompt questions, follow the steps below.

  1. Click the Copilot button at the top of the Console. You will be taken to the Copilot popup window.
  2. Copilot Click the Recommended Prompt button on the left side of the bottom prompt of the popup. The Recommended Prompt popup opens.
  3. Recommended Prompt You can check the questions needed for work in the popup window.
    CategoryDetailed description
    Product
    • Are there any prerequisite services that need to be set up before creating a Virtual Server?
    • What are the constraints of Virtual Server and other Bare Metal Servers?
    • Are there any precautions when using a Bare Metal Server?
    Fee
    • What is the contract fee policy?
    • What is the time basis for fee calculation?
    • How can I check the estimated fee?
    Member
    • How do I register for an IAM member?
    • If I lose my password, how can I retrieve it?
    • How do I change user information and password?
    Other
    • How should the network configuration and firewall settings be set up to access the Samsung Cloud Platform Virtual Machine from an overseas local internal network?
    • If there are errors or improvements when using the service, how should I inquire?
    Table. Recommended Prompt Question Items
Reference
Recommended prompts can also be found on the Service Home page of the service provided by Samsung Cloud Platform Console.

View in a new window

You can check and use Copilot in a new browser tab.

To use Copilot in a new tab, follow these steps.

  1. Click the Copilot button at the top of the Console. Copilot popup window opens.
  2. Copilot Click the View New Window button at the top right. It opens in a new tab of Copilot’s browser.
  3. Click the Copilot tab opened in the browser. It will navigate to the Copilot page.
  4. Use the desired feature on the Copilot page.
CategoryDetailed description
Ask a question > General inquirySamsung Cloud Platform overall usage questions
  • Example questions
    • How do you create a Virtual Server?
    • How can I check the estimated charges?
    • What is the estimated bill for this month?
Ask Question > Resource LookupQuestions about resources used in Samsung Cloud Platform
  • Example Questions
    • Please show the list of Virtual Server resources in my Account.
    • Find the 192.168.21.1 IP among Virtual Servers
New Conversation StartStart a new conversation
Conversation ListCheck the list of previous conversations
Recommended Prompt ListDisplay list of questions recommended by Copilot
  • Product
    • Are there any prerequisite services that must be set up before creating a Virtual Server?
    • What are the constraints between Virtual Server and other Bare Metal Server?
    • Are there any precautions when using Bare Metal Server?
  • Pricing
    • What is the contract pricing policy?
    • What is the time zone used for pricing calculation?
    • How can I check the estimated cost?
  • Member
    • How do I register an IAM member?
    • If I forget my password, how do I retrieve it?
    • How do I change user information and password?
  • Other
    • How should the network configuration and firewall settings be set up to access Samsung Cloud Platform Virtual Machine from an overseas local intranet?
    • How should I inquire if there are errors or improvements when using the service?
  • You can also check by clicking the Recommended Prompt button on the left side of the question input area
Table. Copilot page detailed items
Reference
Recommended prompts can also be found on the Service Home page of the service provided in the Samsung Cloud Platform Console.

2 - Compute

Based on the best stability in Korea, it provides the optimal computing resources conveniently and flexibly according to the purpose of use.

2.1 - Virtual Server

2.1.1 - Overview

Service Overview

Virtual Server is a virtual server optimized for cloud computing that allows you to freely allocate and use as much as you need at the necessary time without purchasing infrastructure resources such as CPU, Memory, etc. provided by the server individually. You can use resources with optimized performance according to your computing usage purposes such as development, testing, and application execution in a cloud environment.

Key Features

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

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

    • General Virtual Server: Provides Computing Specs generally used (maximum 16vCore, 256GB)
    • High Capacity Virtual Server: Provides when large capacity resources larger than General Virtual Server Spec are needed
  • Strong security application: Protects servers safely by controlling Inbound/Outbound traffic communicating with external internet or other VPC (Virtual Private Cloud) through Security Group service. In addition, you can stably operate computing resources through real-time monitoring.

Service Architecture

Architecture
Figure. Virtual Server Architecture

Provided Functions

Virtual Server provides the following functions.

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

Components

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

Image

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

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

Keypair

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

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

Server Group

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

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

OS Image Provided Versions

The OS Images provided by Virtual Server are as follows

OS Image VersionEoS Date
Alma Linux 8.102029-05-31
Alma Linux 9.62025-11-17
Oracle Linux 8.102029-07-31
Oracle Linux 9.62025-11-25
RHEL 8.102029-05-31
RHEL 9.42026-04-30
RHEL 9.62027-05-31
Rocky Linux 8.102029-05-31
Rocky Linux 9.62025-11-30
Ubuntu 22.042027-06-30
Ubuntu 24.042029-06-30
Windows 20192029-01-09
Windows 20222031-10-14
Windows 20162027-01-12
Table. Virtual Server Provided OS Image Versions
Reference
  • Linux operating systems such as Alma Linux and Rocky Linux only provide even Minor versions, except for the last release version of the Major version. This is a policy to ensure the stability and consistency of the SCP system. Please check the EOS (End of Support) and EOL (End of Life) dates of the operating system and apply new or additional individual packages as needed to maintain a stable environment.

Server Type

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

Standard s1v2m4
Category
ExampleDetailed Description
Server TypeStandardClassification of provided server types
  • Standard: Composed of standard specs (vCPU, Memory) generally used
  • High Capacity: Specs of large capacity server larger than Standard
Server Specs1Classification of provided server types and generation
  • s1: s means standard spec, 1 means generation provided in Samsung Cloud Platform v2
  • s2: s means standard spec, 2 means generation provided in Samsung Cloud Platform v2
  • h2: h means large capacity server spec, 2 means generation provided in Samsung Cloud Platform v2
Server Specv2Number of vCores
  • v2: 2 virtual cores
Server Specm4Memory capacity
  • m4: 4GB Memory
Table. Virtual Server Server Type

Constraints

Reference
  • If you create Virtual Server with Rocky Linux or Oracle Linux, additional settings are required for time synchronization (NTP: Network Time Protocol). For other Images, it is automatically set and no separate settings are required.
    For details, refer to Configure Linux NTP.
  • If you create RHEL and Windows Server before August 2025, you need to modify RHEL Repository and WKMS (Windows Key Management Service) settings.
    For details, refer to Configure RHEL Repo and WKMS.

Prerequisite Services

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

Service CategoryServiceDetailed Description
NetworkingVPCService that provides independent virtual network in cloud environment
NetworkingSecurity GroupVirtual firewall that controls server traffic
Table. Virtual Server Prerequisite Services

2.1.1.1 - Server Type

Virtual Server server type

Virtual Server provides a server type suitable for the purpose of use. The server type consists of various combinations such as CPU, Memory, Network Bandwidth, etc. The host server used by the Virtual Server is determined by the server type selected when creating the Virtual Server. Please select a server type according to the specifications of the application you want to run on the Virtual Server.

The server types supported by Virtual Server are as follows.

Standard s1v2m4
Classification
ExampleDetailed Description
Server TypeStandardProvided server type distinction
  • Standard: Composed of standard specifications (vCPU, Memory) commonly used
  • High Capacity: Server specifications with higher capacity than Standard
Server Specifications1Type of server provided and generation distinction
  • s1: s means general specification, and 1 means the generation provided by Samsung Cloud Platform v2
  • s2: s means general specification, and 2 means the generation provided by Samsung Cloud Platform v2
  • h2: h means large-capacity server specification, and 2 means the generation provided by Samsung Cloud Platform v2
Server Specificationv2Number of vCores
  • v2: 2 virtual cores
Server Specificationm4Memory Capacity
  • m4: 4GB Memory
Table. Virtual Server server type format

s1 server type

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

  • Samsung Cloud Platform v2’s 1st generation: up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor
  • Supports up to 16 vCPUs and 256 GB of memory
  • Up to 12.5 Gbps networking speed
DivisionServer TypevCPUMemoryNetwork Bandwidth
Standards1v1m21 vCore2 GBup to 10 Gbps
Standards1v2m42 vCore4 GBUp to 10 Gbps
Standards1v2m82 vCore8 GBUp to 10 Gbps
Standards1v2m162 vCore16 GBUp to 10 Gbps
Standards1v2m242 vCore24 GBUp to 10 Gbps
Standards1v2m322 vCore32 GBUp to 10 Gbps
Standards1v4m84 vCore8 GBUp to 10 Gbps
Standards1v4m164 vCore16 GBUp to 10 Gbps
Standards1v4m324 vCore32 GBUp to 10 Gbps
Standards1v4m484 vCore48 GBUp to 10 Gbps
Standards1v4m644 vCore64 GBUp to 10 Gbps
Standards1v6m126 vCore12 GBUp to 10 Gbps
Standards1v6m246 vCore24 GBUp to 10 Gbps
Standards1v6m486 vCore48 GBUp to 10 Gbps
Standards1v6m726 vCore72 GBUp to 10 Gbps
Standards1v6m966 vCore96 GBUp to 10 Gbps
Standards1v8m168 vCore16 GBUp to 10 Gbps
Standards1v8m328 vCore32 GBUp to 10 Gbps
Standards1v8m648 vCore64 GBUp to 10 Gbps
Standards1v8m968 vCore96 GBUp to 10 Gbps
Standards1v8m1288 vCore128 GBUp to 10 Gbps
Standards1v10m2010 vCore20 GBup to 10 Gbps
Standards1v10m4010 vCore40 GBUp to 10 Gbps
Standards1v10m8010 vCore80 GBup to 10 Gbps
Standards1v10m12010 vCore120 GBup to 10 Gbps
Standards1v10m16010 vCore160 GBUp to 10 Gbps
Standards1v12m2412 vCore24 GBUp to 12.5 Gbps
Standards1v12m4812 vCore48 GBUp to 12.5 Gbps
Standards1v12m9612 vCore96 GBUp to 12.5 Gbps
Standards1v12m14412 vCore144 GBUp to 12.5 Gbps
Standards1v12m19212 vCore192 GBup to 12.5 Gbps
Standards1v14m2814 vCore28 GBUp to 12.5 Gbps
Standards1v14m5614 vCore56 GBUp to 12.5 Gbps
Standards1v14m11214 vCore112 GBUp to 12.5 Gbps
Standards1v14m16814 vCore168 GBUp to 12.5 Gbps
Standards1v14m22414 vCore224 GBUp to 12.5 Gbps
Standards1v16m3216 vCore32 GBup to 12.5 Gbps
Standards1v16m6416 vCore64 GBUp to 12.5 Gbps
Standards1v16m12816 vCore128 GBup to 12.5 Gbps
Standards1v16m19216 vCore192 GBUp to 12.5 Gbps
Standards1v16m25616 vCore256 GBup to 12.5 Gbps
Table. Virtual Server server type specifications - s1 server type

S2 Server Type

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

  • Samsung Cloud Platform v2’s 2nd generation: up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
  • Supports up to 16 vCPUs and 256 GB of memory
  • Up to 12.5 Gbps networking speed
ClassificationServer TypeCPU vCoreMemoryNetwork Bandwidth(Gbps)
Standards2v1m21 vCore2 GBUp to 10 Gbps
Standards2v2m42 vCore4 GBUp to 10 Gbps
Standards2v2m82 vCore8 GBUp to 10 Gbps
Standards2v2m162 vCore16 GBUp to 10 Gbps
Standards2v2m242 vCore24 GBUp to 10 Gbps
Standards2v2m322 vCore32 GBUp to 10 Gbps
Standards2v4m84 vCore8 GBUp to 10 Gbps
Standards2v4m164 vCore16 GBUp to 10 Gbps
Standards2v4m324 vCore32 GBUp to 10 Gbps
Standards2v4m484 vCore48 GBUp to 10 Gbps
Standards2v4m644 vCore64 GBUp to 10 Gbps
Standards2v6m126 vCore12 GBUp to 10 Gbps
Standards2v6m246 vCore24 GBUp to 10 Gbps
Standards2v6m486 vCore48 GBUp to 10 Gbps
Standards2v6m726 vCore72 GBUp to 10 Gbps
Standards2v6m966 vCore96 GBUp to 10 Gbps
Standards2v8m168 vCore16 GBUp to 10 Gbps
Standards2v8m328 vCore32 GBUp to 10 Gbps
Standards2v8m648 vCore64 GBUp to 10 Gbps
Standards2v8m968 vCore96 GBUp to 10 Gbps
Standards2v8m1288 vCore128 GBUp to 10 Gbps
Standards2v10m2010 vCore20 GBUp to 10 Gbps
Standards2v10m4010 vCore40 GBUp to 10 Gbps
Standards2v10m8010 vCore80 GBUp to 10 Gbps
Standards2v10m12010 vCore120 GBUp to 10 Gbps
Standards2v10m16010 vCore160 GBUp to 10 Gbps
Standards2v12m2412 vCore24 GBUp to 12.5 Gbps
Standards2v12m4812 vCore48 GBUp to 12.5 Gbps
Standards2v12m9612 vCore96 GBUp to 12.5 Gbps
Standards2v12m14412 vCore144 GBUp to 12.5 Gbps
Standards2v12m19212 vCore192 GBUp to 12.5 Gbps
Standards2v14m2814 vCore28 GBUp to 12.5 Gbps
Standards2v14m5614 vCore56 GBUp to 12.5 Gbps
Standards2v14m11214 vCore112 GBUp to 12.5 Gbps
Standards2v14m16814 vCore168 GBup to 12.5 Gbps
Standards2v14m22414 vCore224 GBUp to 12.5 Gbps
Standards2v16m3216 vCore32 GBup to 12.5 Gbps
Standards2v16m6416 vCore64 GBUp to 12.5 Gbps
Standards2v16m12816 vCore128 GBup to 12.5 Gbps
Standards2v16m19216 vCore192 GBup to 12.5 Gbps
Standards2v16m25616 vCore256 GBup to 12.5 Gbps
Table. Virtual Server server type specifications - s2 server type

h2 Server Type

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

  • Samsung Cloud Platform v2’s 2nd generation: up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor Supports up to 128 vCPUs and 1,536 GB of memory
  • up to 25Gbps networking speed
DivisionServer TypevCPUMemoryNetwork Bandwidth
High Capacityh2v24m4824 vCore48 GBUp to 25 Gbps
High Capacityh2v24m9624 vCore96 GBUp to 25 Gbps
High Capacityh2v24m19224 vCore192 GBUp to 25 Gbps
High Capacityh2v24m28824 vCore288 GBUp to 25 Gbps
High Capacityh2v32m6432 vCore64 GBUp to 25 Gbps
High Capacityh2v32m12832 vCore128 GBUp to 25 Gbps
High Capacityh2v32m25632 vCore256 GBUp to 25 Gbps
High Capacityh2v32m38432 vCore384 GBUp to 25 Gbps
High Capacityh2v48m9648 vCore96 GBup to 25 Gbps
High Capacityh2v48m19248 vCore192 GBUp to 25 Gbps
High Capacityh2v48m38448 vCore384 GBUp to 25 Gbps
High Capacityh2v48m57648 vCore576 GBUp to 25 Gbps
High Capacityh2v64m12864 vCore128 GBUp to 25 Gbps
High Capacityh2v64m25664 vCore256 GBUp to 25 Gbps
High Capacityh2v64m51264 vCore512 GBUp to 25 Gbps
High Capacityh2v64m76864 vCore768 GBUp to 25 Gbps
High Capacityh2v72m14472 vCore144 GBUp to 25 Gbps
High Capacityh2v72m28872 vCore288 GBUp to 25 Gbps
High Capacityh2v72m57672 vCore576 GBUp to 25 Gbps
High Capacityh2v72m86472 vCore864 GBUp to 25 Gbps
High Capacityh2v96m19296 vCore192 GBUp to 25 Gbps
High Capacityh2v96m38496 vCore384 GBUp to 25 Gbps
High Capacityh2v96m76896 vCore768 GBUp to 25 Gbps
High Capacityh2v96m115296 vCore1152 GBUp to 25 Gbps
High Capacityh2v128m256128 vCore256 GBUp to 25 Gbps
High Capacityh2v128m512128 vCore512 GBUp to 25 Gbps
High Capacityh2v128m1024128 vCore1024 GBUp to 25 Gbps
High Capacityh2v128m1536128 vCore1536 GBUp to 25 Gbps
Table. Virtual Server server type specifications - h2 server type

2.1.1.2 - Monitoring Metrics

Virtual Server monitoring metrics

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

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

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

Performance ItemDetailed DescriptionUnit
Memory Total [Basic]Available memory bytesbytes
Memory Used [Basic]Currently used memory bytesbytes
Memory Swap In [Basic]Swapped memory bytesbytes
Memory Swap Out [Basic]bytes of swapped memorybytes
Memory Free [Basic]Unused memory bytesbytes
Disk Read Bytes [Basic]Read bytesbytes
Disk Read Requests [Basic]Number of Read Requestscnt
Disk Write Bytes [Basic]Write bytesbytes
Disk Write Requests [Basic]Number of Write Requestscnt
CPU Usage [Basic]1-minute average system CPU usage rate%
Instance State [Basic]Instance Statusstate
Network In Bytes [Basic]Received bytesbytes
Network In Dropped [Basic]Receive Packet Dropcnt
Network In Packets [Basic]Received Packet Countcnt
Network Out Bytes [Basic]Transmission bytesbytes
Network Out Dropped [Basic]Transmission Packet Dropcnt
Network Out Packets [Basic]Transmission packet countcnt
Fig. Virtual Server Monitoring Metrics (Default Provided)
Performance ItemDetailed DescriptionUnit
Core Usage [IO Wait]The ratio of CPU time spent in waiting state (disk waiting)%
Core Usage [System]The ratio of CPU time spent in kernel space%
Core Usage [User]The ratio of CPU time spent in user space%
CPU CoresThe number of CPU cores on the hostcnt
CPU Usage [Active]Idle and IOWait status excluding the percentage of CPU time used%
CPU Usage [Idle]The ratio of CPU time spent in idle state.%
CPU Usage [IO Wait]the ratio of CPU time spent in a waiting state (disk waiting)%
CPU Usage [System]The percentage of CPU time used by the kernel%
CPU Usage [User]The percentage of CPU time used in the user area%
CPU Usage/Core [Active]Idle and IOWait status excluding the percentage of CPU time used%
CPU Usage/Core [Idle]The ratio of CPU time spent in idle state.%
CPU Usage/Core [IO Wait]the ratio of CPU time spent in waiting state (disk waiting)%
CPU Usage/Core [System]The percentage of CPU time used by the kernel%
CPU Usage/Core [User]The percentage of CPU time used in the user area%
DiskCPU Usage [IO Request]The ratio of CPU time spent executing input/output requests for the device%
Disk Queue Size [Avg]The average queue length of requests executed for the device.num
Disk Read BytesThe number of bytes read from the device per second.bytes  
Disk Read Bytes [Delta Avg]Average of system.diskio.read.bytes_delta for each Diskbytes
Disk Read Bytes [Delta Max]Individual Disks’ system.diskio.read.bytes_delta maximumbytes
Disk Read Bytes [Delta Min]Individual Disks’ system.diskio.read.bytes_delta minimumbytes
Disk Read Bytes [Delta Sum]Individual Disks’ sum of system.diskio.read.bytes_deltabytes
Disk Read Bytes [Delta]Individual Disk’s system.diskio.read.bytes value deltabytes
Disk Read Bytes [Success]Total bytes read successfullybytes
Disk Read RequestsNumber of read requests for the disk device during 1 secondcnt
Disk Read Requests [Delta Avg]Individual Disks’ average of system.diskio.read.count_deltacnt
Disk Read Requests [Delta Max]Individual Disks’ system.diskio.read.count_delta maximumcnt
Disk Read Requests [Delta Min]Individual Disks’ minimum of system.diskio.read.count_deltacnt
Disk Read Requests [Delta Sum]The sum of system.diskio.read.count_delta of individual Diskscnt
Disk Read Requests [Success Delta]Individual Disk’s system.diskio.read.count deltacnt
Disk Read Requests [Success]Successfully completed total read countcnt
Disk Request Size [Avg]The average size of requests executed for the device (unit: sector)num
Disk Service Time [Avg]The average service time (in milliseconds) for the input requests executed on the device.ms
Disk Wait Time [Avg]The average time spent on requests executed for supported devices.ms
Disk Wait Time [Read]Disk Average Wait Timems
Disk Wait Time [Write]Disk Average Wait Timems
Disk Write Bytes [Delta Avg]Individual Disks’ average of system.diskio.write.bytes_deltabytes
Disk Write Bytes [Delta Max]Individual Disks’ system.diskio.write.bytes_delta maximumbytes
Disk Write Bytes [Delta Min]Individual Disks’ system.diskio.write.bytes_delta minimumbytes
Disk Write Bytes [Delta Sum]Individual Disks’ sum of system.diskio.write.bytes_deltabytes
Disk Write Bytes [Delta]Individual Disk’s system.diskio.write.bytes value deltabytes
Disk Write Bytes [Success]Total bytes written successfullybytes
Disk Write RequestsNumber of write requests to the disk device for 1 secondcnt
Disk Write Requests [Delta Avg]Individual Disks’ average of system.diskio.write.count_deltacnt
Disk Write Requests [Delta Max]Individual Disks’ system.diskio.write.count_delta maximumcnt
Disk Write Requests [Delta Min]Minimum of system.diskio.write.count_delta for each Diskcnt
Disk Write Requests [Delta Sum]Sum of system.diskio.write.count_delta of individual Diskscnt
Disk Write Requests [Success Delta]Individual Disk’s system.diskio.write.count Deltacnt
Disk Write Requests [Success]Total number of writes completed successfullycnt
Disk Writes BytesThe number of bytes written to the device per secondbytes  
Filesystem Hang Checkfilesystem(local/NFS) hang check(Normal:1, Abnormal:0)status  
Filesystem NodesThe total number of file nodes in the file system.cnt
Filesystem Nodes [Free]The total number of available file nodes in the file system.cnt
Filesystem Size [Available]Disk space (bytes) available for use by unauthorized usersbytes
Filesystem Size [Free]Available disk space(bytes)bytes  
Filesystem Size [Total]Total disk space (bytes)bytes  
Filesystem UsageUsed disk space percentage%
Filesystem Usage [Avg]Average of individual filesystem.used.pct%
Filesystem Usage [Inode]iNode usage rate%
Filesystem Usage [Max]Individual filesystem used percentage Max%
Filesystem Usage [Min]Individual minimum of filesystem.used.pct%
Filesystem Usage [Total]-%
Filesystem UsedUsed Disk Space (bytes)bytes  
Filesystem Used [Inode]iNode usagebytes
Memory FreeTotal available memory amount (bytes)bytes
Memory Free [Actual]Actually available Memory(bytes)bytes
Memory Free [Swap]Available Swap memorybytes
Memory TotalTotal Memorybytes
Memory Total [Swap]Total Swap memory.bytes
Memory Usageused Memory percentage%
Memory Usage [Actual]Actual used Memory percentage%
Memory Usage [Cache Swap]cached swap usage rate%
Memory Usage [Swap]Used Swap memory percentage%
Memory UsedUsed Memorybytes
Memory Used [Actual]Actually used Memory(bytes)bytes
Memory Used [Swap]Used Swap memorybytes
CollisionsNetwork Collisioncnt
Network In BytesReceived byte countbytes
Network In Bytes [Delta Avg]Individual Networks’ average of system.network.in.bytes_deltabytes
Network In Bytes [Delta Max]Individual Network’s system.network.in.bytes_delta maximumbytes
Network In Bytes [Delta Min]Individual Networks’ system.network.in.bytes_delta minimum valuesbytes
Network In Bytes [Delta Sum]Individual networks’ sum of system.network.in.bytes_deltabytes
Network In Bytes [Delta]Received byte count deltabytes
Network In DroppedNumber of packets dropped among incoming packetscnt
Network In ErrorsNumber of errors during receptioncnt
Network In PacketsReceived packet countcnt
Network In Packets [Delta Avg]Individual Networks’ average of system.network.in.packets_deltacnt
Network In Packets [Delta Max]Individual Network’s system.network.in.packets_delta maximum valuecnt
Network In Packets [Delta Min]Individual Network’s system.network.in.packets_delta minimum valuecnt
Network In Packets [Delta Sum]The sum of system.network.in.packets_delta of individual Networkscnt
Network In Packets [Delta]Received packet count deltacnt
Network Out BytesSent byte countbytes
Network Out Bytes [Delta Avg]Individual Networks’ average of system.network.out.bytes_deltabytes
Network Out Bytes [Delta Max]Individual Networks’ system.network.out.bytes_delta maximumbytes
Network Out Bytes [Delta Min]Individual Networks’ system.network.out.bytes_delta minimum valuebytes
Network Out Bytes [Delta Sum]Individual Network’s system.network.out.bytes_delta sumbytes
Network Out Bytes [Delta]Sent byte count deltabytes
Network Out Droppednumber of packets dropped among outgoing packetscnt
Network Out ErrorsNumber of errors during transmissioncnt
Network Out PacketsTransmitted packet countcnt
Network Out Packets [Delta Avg]Average of system.network.out.packets_delta for individual Networkscnt
Network Out Packets [Delta Max]Individual Networks’ system.network.out.packets_delta maximum valuescnt
Network Out Packets [Delta Min]Individual Network’s system.network.out.packets_delta minimum valuecnt
Network Out Packets [Delta Sum]The sum of system.network.out.packets_delta of individual Networkscnt
Network Out Packets [Delta]Sent packet count deltacnt
Open Connections [TCP]All open TCP connectionscnt
Open Connections [UDP]All open UDP connectionscnt
Port UsageAccessible port usage rate%
SYN Sent SocketsNumber of sockets in SYN_SENT state (when connecting from local to remote)cnt
Kernel PID Maxkernel.pid_max valuecount
Kernel Thread Maxkernel threads maximum valuecount
Process CPU UsageThe percentage of CPU time consumed by the process after the last update%
Process CPU Usage/CoreThe percentage of CPU time used by the process since the last event%
Process Memory Usagemain memory(RAM) where the process occupies a ratio%
Process Memory UsedResident Set size. The amount of memory a process occupies in RAMbytes
Process PIDProcess pidpid  
Process PPIDParent process’s pidpid
Processes [Dead]number of dead processescnt
Processes [Idle]idle Number of Processescnt
Processes [Running]running Number of Processescount
Processes [Sleeping]sleeping processes countcnt
Processes [Stopped]stopped processes countcnt
Processes [Total]Total number of processescnt
Processes [Unknown]The status cannot be searched or the number of unknown processescnt  
Processes [Zombie]Number of zombie processescnt
Running Process UsageProcess Usage Rate%
Running Processesnumber of running processescount
Running Thread Usagethread usage rate%
Running Threadsrunning processes where the total number of threads being executedcnt
Context Switchesnumber of context switches (per second)cnt
Load/Core [1 min]The value divided by the number of cores for the last 1 minute loadcnt
Load/Core [15 min]The value of load divided by the number of cores for the last 15 minutescnt
Load/Core [5 min]The value divided by the number of cores for the last 5 minutescnt
Multipaths [Active]External storage connection path status = active countcnt
Multipaths [Failed]External storage connection path status = failed countcnt
Multipaths [Faulty]External storage connection path status = faulty countcnt
NTP Offset lastsample’s measured offset (time difference between NTP server and local environment)num
Run Queue LengthExecution Waiting Queue Lengthnum
UptimeOS operation time(uptime) (milliseconds)ms
Context Switchies CPUnumber of context switches (per second)cnt
Disk Read Bytes [Sec]bytes read from the Windows logical disk in 1 second
  • Windows only
cnt
Disk Read Time [Avg]Data Read Average Time (sec)
  • Windows only
sec
Disk Transfer Time [Avg]Disk average wait time (seconds)
  • Windows only
sec
Disk Write Bytes [Sec]The number of bytes written to the Windows logical disk in 1 second
  • Windows only
cnt
Disk Write Time [Avg]Data write average time (seconds)
  • Windows only
sec
Pagingfile UsagePaging file usage rate
  • Windows only
%
Pool Used [Non Paged]_KERNEL MEMORY among Nonpaged Pool usage
  • Windows only
bytes
Pool Used [Paged]Kernel memory Paged Pool usage among kernel memory
  • Windows only
bytes
Process [Running]The number of processes currently running
  • Windows only
cnt
Threads [Running]The number of threads currently running
  • Windows only
cnt
Threads [Waiting]The number of threads waiting for processor time
  • Windows only
cnt
Fig. Virtual Server Additional Monitoring Metrics (Agent Installation Required)

2.1.1.3 - ServiceWatch Metrics

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

Reference
To view metrics in ServiceWatch, refer to the ServiceWatch guide.

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

Basic Metrics

The following are basic metrics for the namespace Virtual Server.

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

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

Performance Item (Metric Name)Detailed DescriptionUnitMeaningful Statistics
Instance StateInstance state display
  • 1 - Active
  • 0 - Off
None
  • Sum
CPU UsageCPU usagePercent
  • Average
  • Maximum
  • Minimum
Disk Read BytesAmount read from block device (bytes)Bytes
  • Sum
  • Average
  • Maximum
  • Minimum
Disk Read RequestsNumber of read requests from block deviceCount
  • Sum
  • Average
  • Maximum
  • Minimum
Disk Write BytesAmount written to block device (bytes)Bytes
  • Sum
  • Average
  • Maximum
  • Minimum
Disk Write RequestsNumber of write requests to block deviceCount
  • Sum
  • Average
  • Maximum
  • Minimum
Network In BytesAmount received on network interface (bytes)Bytes
  • Sum
  • Average
  • Maximum
  • Minimum
Network In DroppedNumber of received packets dropped on network interfaceCount
  • Sum
  • Average
  • Maximum
  • Minimum
Network In PacketsNumber of received packets on network interfaceCount
  • Sum
  • Average
  • Maximum
  • Minimum
Network Out BytesAmount transmitted on network interface (bytes)Bytes
  • Sum
  • Average
  • Maximum
  • Minimum
Network Out DroppedNumber of transmitted packets dropped on network interfaceCount
  • Sum
  • Average
  • Maximum
  • Minimum
Network Out PacketsNumber of transmitted packets on network interfaceCount
  • Sum
  • Average
  • Maximum
  • Minimum
Table. Virtual Server Basic Metrics
Reference
For information on how to collect metrics using ServiceWatch Agent, refer to the ServiceWatch Agent guide.

2.1.2 - How-to guides

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

Create Virtual Server

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

To create a Virtual Server, follow the procedure below.

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

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

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

    • In the Image and version selection area, select the required information.
      Category
      Required
      Detailed Description
      ImageRequiredSelect the type of Image provided
      • Standard: Samsung Cloud Platform standard provided Image
        • Alma Linux, Oracle Linux, RHEL, Rocky Linux, Ubuntu, Windows
      • Custom: User created Image
      • Kubernetes: Image for Kubernetes
        • RHEL, Ubuntu
      • Marketplace: Image subscribed from Marketplace
      Image VersionRequiredSelect version of selected Image
      • Provides version list of provided server Image
      Table. Virtual Server Image and Version Selection Input Items
    • In the Service information input area, enter or select the required information.
      Category
      Required
      Detailed Description
      Server CountRequiredNumber of servers to create simultaneously
      • Only numbers can be entered, enter value between 1 and 100
      Service Type > Server TypeRequiredVirtual Server server type
      • Standard: Standard specs generally used
      • High Capacity: Large capacity server specs larger than Standard
      Service Type > Planned ComputeRequiredResource status with Planned Compute set
      • In Use: Number in use among resources with Planned Compute set
      • Set: Number of resources with Planned Compute set
      • Coverage Preview: Amount applied as Planned Compute per resource
      • Apply for Planned Compute Service: Move to Planned Compute service creation page
      Block StorageRequiredConfigure Block Storage used by server according to purpose
      • Default OS: Area where OS is installed and used
        • Capacity is entered in Units, minimum capacity varies depending on OS Image type
          • Alma Linux: Enter value between 2 and 1,536
          • Oracle Linux: Enter value between 7 and 1,536
          • RHEL: Enter value between 2 and 1,536
          • Rocky Linux: Enter value between 2 and 1,536
          • Ubuntu: Enter value between 2 and 1,536
          • Windows: Enter value between 4 and 1,536
        • SSD: High performance general volume
        • HDD: General volume
        • SSD/HDD_KMS: Additional encryption volume using Samsung Cloud Platform KMS (Key Management Service) encryption key
          • Encryption application is only possible at initial creation and cannot be changed after creation
          • Performance degradation occurs when using SSD_KMS disk type
        • SSD_Provisioned: SSD volume with configurable IOPS and Throughput
      • Additional: Use when additional user space is needed outside OS area
        • Select Use and then enter storage type and capacity
        • To add storage, click + button, to delete, click x button (can add up to 25)
        • Capacity is entered in Units, enter value between 1 and 1,536
          • 1 Unit is 8GB, so 8 to 12,288GB is created
        • SSD: High performance general volume
        • HDD: General volume
        • SSD/HDD_KMS: Additional encryption volume using Samsung Cloud Platform KMS (Key Management Service) encryption key
          • Encryption application is only possible at initial creation and cannot be changed after creation
          • Performance degradation may occur when using SSD_KMS disk type
        • SSD/HDD_MultiAttach: Volume that can connect to 2 or more servers
        • SSD_Provisioned: SSD volume with configurable IOPS and Throughput
      • Delete on termination: When Delete on Termination is selected, the Volume is also terminated when the server is terminated
        • Volumes with snapshots are not deleted even when Delete on termination is Use
        • Multi attach volumes are only deleted when the server to be deleted is the last remaining server connected to the volume
      • Max IOPS: Enter IOPS maximum value within 5,000 to 20,000
        • Cannot set when disk type is HDD, HDD_KMS, HDD_MultiAttach
      Server GroupOptionalSet servers belonging to the same Server Group to Anti-Affinity (distributed placement), Affinity (close placement), Partition (Virtual Server and Block Storage distributed placement)
      • Select Use and then select Server Group
      • Select Create New to create Server Group
      • Servers belonging to the same Server Group are placed in Best Effort manner according to selected policy
        • Select policy from Anti-Affinity (distributed placement), Affinity (close placement), Partition (Virtual Server and Block Storage distributed placement)
      Table. Virtual Server Service Information Input Items
      Caution
      When using Partition (Virtual Server and Block Storage distributed placement) policy among Server Group policies, Block Storage Volume cannot be additionally allocated after Virtual Server creation, so create all necessary Block Storage at the Virtual Server creation stage.
    • In the Required information input area, enter or select the required information.
      Category
      Required
      Detailed Description
      Server NameRequiredEnter name for server identification when selected server count is 1
      • Set hostname with entered server name
      • Enter within 63 characters using English, numbers, spaces, and special characters (-, _)
      Network Settings > Create New Network PortRequiredSet network where Virtual Server will be installed
      • VPC Name: Select pre-created VPC
      • General Subnet: Select pre-created general Subnet
        • IP can select Auto Create or user input, if Input is selected, user can directly enter IP
        • NAT: Can only use when server count is 1 and Internet Gateway is connected to VPC. Check Use to select NAT IP
        • NAT IP: Select NAT IP
          • If there is no NAT IP to select, click Create New button to create Public IP
          • Click Refresh button to check and select created Public IP
          • When Public IP is created, fees are charged according to Public IP fee standard
      • Local Subnet (Optional): Select Use for Local Subnet
        • Not required for service creation
        • Must select pre-created Local Subnet
        • IP can select Auto Create or user input, if Input is selected, user can directly enter IP
      • Security Group: Settings required to connect to server
        • Select: Select pre-created Security Group
        • Create New: If there is no Security Group to apply, can create separately in Security Group service
        • Can select up to 5
        • If Security Group is not set, all connections are blocked by default
        • Security Group must be set to allow necessary connections
      Network Settings > Specify Existing Network PortRequiredSet network where Virtual Server will be installed
      • VPC: Select pre-created VPC
      • General Subnet: Select pre-created general Subnet and Port
        • NAT: Can only use when server count is 1 and Internet Gateway is connected to VPC. Check Use to select NAT IP
        • NAT IP: Select NAT IP
          • If there is no NAT IP to select, click Create New button to create Public IP
          • Click Refresh button to check and select created Public IP
      • Local Subnet (Optional): Select Use for Local Subnet
        • Select pre-created Local Subnet and Port
      KeypairRequiredUser authentication method to use when connecting to the server
      • Create New: Create a new one when a new Keypair is needed
      • Default login account list by OS
        • Alma Linux: almalinux
        • Oracle Linux: cloud-user
        • RHEL: cloud-user
        • Rocky Linux: rocky
        • Ubuntu: ubuntu
        • Windows: sysadmin
      • </ul
      Table. Virtual Server Required Information Input Items
    • In the Additional information input area, enter or select the required information.
      Category
      Required
      Detailed Description
      LockOptionalSet whether to use Lock
      • When Lock is used, prevents operations such as server termination, start, stop to prevent accidental malfunction
      Init ScriptOptionalScript to execute when server starts
      • Init script must be written as Batch script for Windows or Shell script or cloud-init for Linux depending on Image type.
      • Can enter up to 45,000 bytes
      TagOptionalAdd tags
      • Can add up to 50 per resource
      • Click Add Tag button and then enter or select Key, Value values
      Table. Virtual Server Additional Information Input Items
  4. On the Summary panel, check the created detailed information and estimated billing amount, then click the Create button.

    • When creation is complete, check the created resource on the Virtual Server List page.
Notice
  • When entering server name, if spaces and special characters (_) are used, OS hostname is set with spaces and special characters (_) changed to special character (-). Please note when setting OS hostname.
    • Example: If server name is ‘server name_01’, OS hostname is set to ‘server-name-01’.
  • If you need to manage server names uniquely, create with different server names (Prefix).
    • When creating servers, numbers do not automatically increase based on server name (Prefix), so Virtual Servers with the same name may be created.
    • Example: If you first create 2 Virtual Servers using ’test’ as server name (Prefix), ’test-1’, ’test-2’ are created. Even if you create 2 Virtual Servers later using ’test’ as Prefix again, ’test-1’, ’test-2’ are created.
Reference
  • If you create Virtual Server with Rocky Linux or Oracle Linux, additional settings are required for time synchronization (NTP: Network Time Protocol). For details, refer to Configure Linux NTP.
  • If you create RHEL and Windows Server before July 2025, you need to modify RHEL Repository and WKMS (Windows Key Management Service) settings. For details, refer to Configure RHEL Repo and WKMS.

Check Virtual Server Details

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

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

  1. Click All Services > Compute > Virtual Server menu. You will be moved to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Virtual Server menu. You will be moved to the Virtual Server List page.
  3. On the Virtual Server List page, click the resource to check detailed information for. You will be moved to the Virtual Server Detail page.
    • Virtual Server Detail page displays status information and additional function information, and is composed of Detail Information, Monitoring, Tags, Operation History tabs.
    • For details on Virtual Server status, refer to Check Virtual Server Detail Information.
      CategoryDetailed Description
      Virtual Server StatusStatus of Virtual Server created by user
      • Build: State where Build command is transmitted
      • Building: Build in progress
      • Networking: Process in progress during server creation
      • Scheduling: Process in progress during server creation
      • Block_Device_Mapping: Connecting Block Storage during server creation
      • Spawning: State where server creation process is in progress
      • Active: Usable state
      • Powering_off: State when stop is requested
      • Deleting: Server deletion in progress
      • Reboot_Started: State where Reboot is in progress
      • Error: Error state
      • Migrating: State where server is being migrated to another host
      • Reboot: State where Reboot command is transmitted
      • Rebooting: Restart in progress
      • Rebuild: State where Rebuild command is transmitted
      • Rebuilding: State when Rebuild is requested
      • Rebuild_Spawning: State where Rebuild process is in progress
      • Resize: State where Resize command is transmitted
      • Resizing: Resize in progress
      • Resize_Prep: State when server type modification is requested
      • Resize_Migrating: State where server is moving to another host while Resize is in progress
      • Resize_Migrated: State where server has completed moving to another host while Resize is in progress
      • Resize_Finish: Resize completed
      • Revert_Resize: Server Resize or migration failed for some reason. Target server is cleaned and original source server is restarted
      • Shutoff: State when Powering off is completed
      • Verity_ Resize: State where server type confirmation/server type reversion is selectable after Resize_Prep progress according to server type modification request
      • Resize_Reverting: State when server type reversion is requested
      • Resize_Confirming: State where server Resize request is being confirmed
      Server ControlButtons to change server status
      • Start: Start stopped server
      • Stop: Stop running server
      • Restart: Restart running server
      Create ImageCreate a user image from the current server image
      Console LogCheck current server console log
      • Can check console log output from current server. For details, refer to Check Console Log
      Create DumpCreate current server Dump
      • Dump file is created inside Virtual Server
      • For detailed Dump creation method, refer to Create Dump
      RebuildDelete existing Virtual Server OS area data and settings, and configure by Rebuilding as new server
      Terminate ServiceButton to terminate service
      Table. Virtual Server Status Information and Additional Functions

Detail Information

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

CategoryDetailed Description
ServiceService name
Resource TypeResource type
SRNUnique resource ID in Samsung Cloud Platform
  • In Virtual Server, means Virtual Server SRN
Resource NameResource name
  • In Virtual Server service, means Virtual Server name
Resource IDUnique resource ID in service
CreatorUser who created service
Creation DateDate and time when service was created
ModifierUser who modified service information
Modification DateDate and time when service information was modified
Server NameServer name
  • Click Modify button to change name
  • When server name is changed, OS Hostname is not changed, only information in Samsung Cloud Platform Console is changed
  • Cannot modify if Virtual Server was created by other resource
Server TypeDisplay vCPU, memory information
  • If change to different server type is needed, click Modify button to set
Image NameServer OS Image and version
  • Can select Image by Image version and build date
LockDisplay whether Lock is used/not used
  • If Lock attribute value change is needed, click Modify button to set
Server GroupServer group name to which server belongs
  • If server group is not used, not displayed.
Keypair NameServer authentication information set by user
  • Default login accounts by OS are as follows.
    • Alma Linux: almalinux
    • Oracle Linux: cloud-user
    • RHEL: cloud-user
    • Rocky Linux: rocky
    • Ubuntu: ubuntu
    • Windows: sysadmin
Planned ComputeResource status with Planned Compute set
LLM EndpointURL for using LLM
ServiceWatch Detailed MonitoringDisplay whether ServiceWatch detailed monitoring is enabled
  • To **enable** ServiceWatch detailed monitoring, click **Modify** button to set
  • For details, refer to [Enable ServiceWatch Detailed Monitoring](#servicewatch-세부-모니터링-활성화하기)
  • For details on ServiceWatch service, refer to [ServiceWatch Overview](/userguide/management/service_watch/overview/_index.md)
  • Not provided for Auto-Scaling Group, Virtual Server created from Marketplace
| | Network | Virtual Server network information
  • VPC, General Subnet, IP and status, Public NAT IP and status, Private NAT IP and status, Virtual IP, Security Group
  • If IP change is needed, click **Modify** button to set
    • Can only modify when Virtual Server status is **Active**, **Shutoff**
    • For Default port, **Default** is displayed next to IP, and cannot detach
  • If Security Group change is needed, click **Modify** button to set
  • If Virtual IP change is needed, can modify on **Virtual IP Management** tab of **Networking > VPC > Subnet Detail** page
  • **Add as New Network Port**: Select General Subnet and IP
    • Can select other General Subnet within same VPC
    • IP can select auto create or user input, if input is selected, user can directly enter IP
  • **Add as Existing Network Port**: Select pre-created General Subnet and port
| | Local Subnet | Virtual Server Local Subnet information
  • Local Subnet, Local Subnet IP, Security Group name, Virtual IP
  • If Security Group change is needed, click **Modify** button to set
  • **Add as New Network Port**: Select Local Subnet and IP
    • Can select other General Subnet within same VPC
    • **IP** can select **Auto Create** or user input, if **Input** is selected, user can directly enter IP
  • **Add as Existing Network Port**: Select pre-created Local Subnet and port
| | Block Storage | Block Storage information connected to server
  • Volume ID, Volume name, Disk type, Capacity, Connection information, Type, Delete on termination, Status
  • **Add**: Connect additional Block Storage when needed
  • **Modify Delete on termination**: Modify Delete on termination value of selected Block Storage from list
  • **More > Disconnect**: Disconnect Block Storage connection of selected Block Storage from list
    • Cannot disconnect for OS default Storage
|
Table. Virtual Server Detail Information Tab Items

Monitoring

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

CategoryDetailed Description
Period Setting AreaSelect period to apply to chart
  • Metrics query can be set from current to maximum 455 days
Timezone Setting AreaSelect timezone to apply to chart
Reset ButtonReset all manipulations or settings made on chart
Refresh Setting AreaSelect refresh period of chart
  • Refresh button redisplays information based on current time
  • Click refresh period to select desired period: Off, 10 seconds, 1 minute, 2 minutes, 5 minutes, 15 minutes
Move to Service DashboardMove to ServiceWatch dashboard list screen
MoreDisplay additional work items for managing chart
Graph AreaData graph collected during period applied to chart
  • Available graphs
    • Average CPU Usage (Percent)
    • Average Disk Reads (Bytes)
    • Average Disk Writes (Bytes)
    • Summary Disk Read Requests (Count)
    • Summary Disk Write Requests (Count)
    • Maximum Network In (Bytes)
    • Maximum Network Out (Bytes)
    • Summary Instance State (Any)
  • Place mouse cursor on graph to display time, data value, metric data information of that point as popup
  • Can zoom specific area of graph by dragging mouse
  • Click label name displayed in legend to display detailed information for that legend as popup
Table. Virtual Server Monitoring Tab Chart Items
Reference
  • Metrics provided by basic monitoring are data collected at 5-minute intervals.
  • For details on Virtual Server ServiceWatch metrics, refer to Virtual Server ServiceWatch Metrics.

Tags

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

CategoryDetailed Description
Tag ListTag list
  • Can check tag Key, Value information
  • Can add up to 50 tags per resource
  • When entering tags, search and select from existing Key and Value lists
Table. Virtual Server Tag Tab Items

Operation History

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

CategoryDetailed Description
Operation History ListResource change history
  • Can check operation details, operation date and time, resource type, resource name, operation result, operator information
  • Click corresponding resource from Operation History List list. Operation History Detail popup window opens.
Table. Virtual Server Operation History Tab Detail Information Items

Control Virtual Server Operation

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

Start Virtual Server

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

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

Stop Virtual Server

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

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

Restart Virtual Server

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

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

Manage Virtual Server Resources

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

Create Image

You can create Image of running Virtual Server.

Reference

This content guides how to create user Image from running Virtual Server.

  • Create user Image by clicking Create Image button on Virtual Server List or Virtual Server Detail page.
  • For method of creating Image by uploading user’s owned Image file, refer to Create Image in Image Detail Guide.

To create Virtual Server Image, follow the procedure below.

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

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

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

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

    • In the Service information input area, enter the required information.
      Category
      Required
      Detailed Description
      Image NameRequiredName of Image to create
      • Enter within 200 characters using English, numbers, spaces, and special characters (-, _)
      Table. Image Service Information Input Items
  5. Check input information and click Complete button.

    • When creation is complete, check the created resource on All Services > Compute > Virtual Server > Image List page.
Notice
  • When Image is created, it is saved to Object Storage used as internal storage. Therefore, usage fee is charged for Image storage.
  • File system of Image created from Active Virtual Server cannot guarantee integrity, so Image creation after server stop is recommended.

Modify Server Type

You can modify server type of Virtual Server server.

Reference
For server types that can be changed provided by Virtual Server, refer to Virtual Server Server Type.

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

  1. Click All Services > Compute > Virtual Server menu. You will be moved to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Virtual Server menu. You will be moved to the Virtual Server List page.
  3. On the Virtual Server List page, click the resource to control operation. You will be moved to the Virtual Server Detail page.
  4. On the Virtual Server Detail page, check server status and click server type Modify button. Modify Server Type popup window opens.
  5. On the Modify Server Type popup window, change server type and then click Confirm button.
    • When Virtual Server server type is modified, Virtual Server status changes to Resize execution related status.
    • For details on Virtual Server status, refer to Check Virtual Server Detail Information.
Reference
When Virtual Server server type is changed, monitoring performance metric data may not be collected normally for a while. Normal performance metrics are collected in the next collection cycle (1 minute).

Change IP

For method of changing IP, refer to Change IP.

Caution
  • If IP change is performed, can no longer communicate with that IP, and IP change cannot be cancelled during progress.
  • Server is rebooted to apply changed IP.
  • If server is in Load Balancer service, must delete existing IP from LB server group and directly add changed IP as member of LB server group.
  • For servers using Public NAT/Private NAT, must disable use of Public NAT/Private NAT and then set again after IP change.
    • If Public NAT/Private NAT is in use, first disable use of Public NAT/Private NAT and after completing IP change, set again.
    • Whether Public NAT/Private NAT is used can be changed by clicking Modify button of Public NAT IP/Private NAT IP on Virtual Server Detail page.

Enable ServiceWatch Detailed Monitoring

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

Caution
Basic monitoring is provided free of charge, but additional fees are charged when detailed monitoring is enabled. Please be careful when using.

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

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

Disable ServiceWatch Detailed Monitoring

Caution
Disabling detailed monitoring is needed for cost efficiency. Keep detailed monitoring enabled only when absolutely necessary, and disable detailed monitoring for the rest.

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

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

Virtual Server Management Additional Functions

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

Check Console Log

You can check current console log of Virtual Server.

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

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

Create Dump

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

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

Perform Rebuild

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

To perform Virtual Server Rebuild, follow the procedure below.

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

Terminate Virtual Server

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

Caution
Please note that data cannot be recovered after service termination.

To terminate Virtual Server, follow the procedure below.

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

Termination Constraints

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

Termination Not Possible
  • When File Storage is connected: First disconnect File Storage connection.
  • When LB server group is connected: First disconnect LB server group Pool connection.
  • When Lock is set: Change Lock setting to not used and then try again.
  • When Backup is connected: First disconnect Backup connection.
  • When Auto-Scaling Group connected to Virtual Server is not In Service state: Change state of connected Auto-Scaling Group and then try again.

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

Deletion by Delete on termination Setting
  • Volume deletion varies depending on whether Delete on termination is set.
    • When Delete on termination is not set: Volume is not deleted even if Virtual Server is terminated.
    • When Delete on termination is set: Volume is deleted when Virtual Server is terminated.
  • Volumes with snapshots are not deleted even if Delete on termination is set.
  • Multi attach volumes are deleted only when the server to be deleted is the last remaining server connected to the volume.

2.1.2.1 - Image

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

Image generation

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

To create an Image, follow the steps below.

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

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

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

    • Service Information Input Enter or select the required information in the area.
      Category
      Required
      Detailed description
      Image nameRequiredName of the Image to create
      • Enter within 255 characters using English letters, numbers, spaces, and special characters (-, _)
      Image file > URLRequiredEnter 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 typeRequiredOS type of the uploaded Image file
      • Select from Alma Linux, CentOS, Oracle Linux, RHEL, Rocky Linux, Ubuntu
      Minimum DiskRequiredMinimum disk size (GB) for the Image to be created
      • Enter a value between 0 and 12,288 GB
      Minimum RAMRequiredMinimum RAM capacity (GB) of the image to be created
      • Enter a value between 0 and 2,097,151 GB
      VisibilityRequiredIndicates access permissions for the Image
      • Private: Can be used only within the Account
      • Shared: Can be shared between Accounts
      ProtectedSelectSelect 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
      TagSelectAdd 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.
      CategoryDetailed description
      Image statusStatus 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 ImageCreate 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 AccountImage 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 DeleteButton 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.

CategoryDetailed description
ServiceService Name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In Image, it means Image SRN
Resource NameImage Name
Resource IDImage’s unique resource ID
CreatorUser who created the Image
Creation timeImage creation time
EditorUser who modified the Image information
Modification DateDate/Time when Image information was modified
Image nameImage name
Minimum DiskImage’s minimum disk capacity (GB)
  • If you need to modify the minimum disk, click the Edit button to set it
Minimum RAMMinimum RAM capacity of the Image (GB)
OS typeImage’s OS type
  • Alma Linux, CentOS, Oracle Linux, RHEL, Rocky Linux, SLES, Ubuntu
OS hash algorithmOS hash algorithm method
VisibilityDisplays access permissions for the Image
  • Private: Can be used only within the Account
  • Shared: Can be shared between Accounts
ProtectedSelect whether image deletion is prohibited
  • enabled setting prevents accidental deletion of the Image
Image sizeImage size
  • If the generated Image size is 1GB or less, it is displayed as 1GB.
Image TypeClassification by Image creation method
  • Snapshot-Based: When the configuration of the currently used Virtual Server is created as an Image
  • Image-Based: When an Image is created by uploading a qcow2 extension file or by creating a shared Image
Image file URLImage file URL uploaded to Object Storage when creating an Image
  • Not displayed for Images created via the Image creation menu on the Virtual Server detail page, but displayed when the Image file is uploaded to Object Storage.
Sharing StatusStatus of sharing images with other Accounts
  • Approved Account ID: ID of the Account that has been approved for sharing
  • Modification Date/Time: The date/time when sharing was requested to another Account, after the sharing status changes Pending → Accepted it is updated to that date/time
  • Status: Approval status
    • Accepted: Approved and being shared
    • Pending: Waiting for approval
  • Sharing stopped: Sharing has been stopped
Table. Image detailed information tab items

Tag

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

CategoryDetailed description
Tag ListTag List
  • You can view the tag’s Key, Value information
  • Up to 50 tags can be added per resource
  • When entering a tag, search and select from the existing list of Keys and Values
Table. Image tag tab items

Work History

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

CategoryDetailed description
Work History ListResource Change History
  • Work date/time, Resource ID, Resource name, Work details, Event topic, Work result, Verify worker information
Table. Image work history tab detailed information items

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.

Notice
  • Image’s Visibility is private and only when the Image has snapshot information can a shared Image be created.
  • Shared Image includes only one OS area disk volume as the imaging target. Additionally, connected data volumes are not included in the Image, so if needed, please copy the data to a separate volume and use the volume migration function.

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.

Notice
  • .qcow2 extension file uploaded to create, or only Images created via Image Details page with Create Shared Image can be shared with other Accounts.
  • The Image to be shared must have Visibility set to Shared.

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

    CategoryDetailed description
    Image nameshared Image name
    OS typeOS type of shared Image
    Owner Account IDOwner Account ID of shared Image
    Creation timeCreation time of shared Image
    ApprovalApprove the shared Image
    RejectReject 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.

Caution
Please be careful as data cannot be recovered after deleting the service.

To delete Image, follow the steps below.

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

2.1.2.2 - Keypair

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

Creating a Keypair

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

Follow these steps to create a Keypair.

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

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

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

    • In the Service Information Input section, enter the required information.
      ItemRequiredDescription
      Keypair NameRequiredName of the Keypair to create. Use English letters, numbers, spaces, and special characters (-, _) up to 255 characters.
      Keypair TypeRequiredssh
      Table. Keypair service information input items
    • In the Additional Information Input section, enter or select the required information.
      ItemRequiredDescription
      TagsOptionalAdd tags (up to 50 per resource). Click the Add Tag button and enter/select Key and Value.
      Table. Additional Keypair information input items
  4. Review the entered information and click the Create button.

    • After creation, the new Keypair will appear on the Keypair List page.
Caution
  • After creation, you can download the Private Key only once. It cannot be reissued, so ensure you have downloaded it.
  • Store the downloaded Private Key in a secure location.

Viewing Keypair Details

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

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

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

Details

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

ItemDescription
ServiceService name
Resource TypeResource type
SRNUnique resource ID in Samsung Cloud Platform (for Keypair, refers to Keypair SRN)
Resource NameKeypair name
Resource IDUnique resource ID of the Keypair
CreatorUser who created the Keypair
Creation TimeTimestamp when the Keypair was created
ModifierUser who modified the Keypair information
Modification TimeTimestamp when the Keypair information was modified
Keypair NameName of the Keypair
FingerprintUnique value to identify the key
User IDUser ID of the Keypair creator
Public KeyPublic key information
Table. Keypair details tab items

Tags

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

ItemDescription
Tag ListList of tags. You can view the Key and Value of each tag. Up to 50 tags can be added per resource. When entering a tag, you can search the existing Key and Value lists to select them.
Table. Keypair tags tab items

Activity History

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

ItemDescription
Activity History ListResource change history, including operation time, resource ID, resource name, operation details, event topic, operation result, and operator information.
Table. Keypair activity history tab details

Managing Keypair Resources

This section describes the control and management functions for Keypair.

Retrieving the Public Key

Follow these steps to retrieve the public key.

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

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

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

    • In the Required Information Input section, enter or select the required information.
      ItemRequiredDescription
      Keypair NameRequiredName of the Keypair to retrieve
      Keypair TypeRequiredssh
      Public KeyRequiredEnter the public key.
      • File Upload: Click the Attach File button to attach a public key file (only .pem files are allowed).
      • Public Key Input: Paste the copied public key value (you can copy the public key value from the Keypair Details page).
      Table. Required fields for retrieving a public key
  4. Review the entered information and click the Complete button.

    • After completion, the newly created resource will appear on the Keypair List page.
Info
Even if you create a new Keypair via Retrieve Public Key, the Keypair cannot be re‑downloaded. Use the Keypair that was issued at the time of creation.

Deleting a Keypair

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

Caution
After deleting the service, the data cannot be recovered, so please be careful.

To delete a Keypair, follow these steps.

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

2.1.2.3 - Server Group

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

Server Group Create

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

To create a Server Group, follow the steps below.

  1. Click the All Services > Compute > Virtual Server menu. Go to the Service Home page of Virtual Server.
  2. Click the Server Group menu on the Server Group page. Go to the Server Group list page.
  3. Server Group List on the page, click the Server Group Create button. Navigate to the Server Group Create page.
    • Service Information Input area, enter or select the required information.
      Category
      Required
      Detailed description
      Server Group nameRequiredName of the Server Group to create
      • Enter within 255 characters using English letters, numbers, spaces, and special characters (-, _)
      PolicyRequiredSet 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
      TagSelectAdd 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.

CategoryDetailed description
ServiceService Name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In Server Group, it means Server Group SRN
Resource NameServer Group Name
Resource IDUnique resource ID of Server Group
CreatorUser who created the Server Group
Creation timeServer Group creation time
Server Group nameServer Group name
PolicyAnti-Affinity(distributed placement), Affinity(proximal placement), Partition(distributed placement of Virtual Server and Block Storage)
Server Group MemberList of Virtual Servers belonging to the Server Group
  • Members cannot be modified after the initial Virtual Server is created
  • Anti-Affinity (distributed placement) and Affinity (proximate placement) policies define only the relative placement relationships between Virtual Servers, and the SCP Console provides only the list of Virtual Servers belonging to the policy.
  • The Partition (distributed placement of Virtual Server and Block Storage) policy displays the Partition number together to clearly indicate which Partition the Virtual Server and its associated Block Storage belong to. The Partition number is assigned based on the Partition Size set for the Server Group (maximum 3).
Table. Server Group detailed information tab items

Tag

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

CategoryDetailed description
Tag ListTag List
  • Can view the tag’s Key and Value information
  • Up to 50 tags can be added per resource
  • When entering tags, search and select from the previously created Key and Value list
Table. Server Group Tag Tab Items

Work History

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

CategoryDetailed description
Work History ListResource Change History
  • Work date/time, Resource ID, Resource name, Work details, Event topic, Work result, Check worker information
Table. Server Group Task History Tab Detailed Information Items

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.

Caution
Please be careful as data cannot be recovered after deleting the service.

To delete a Server Group, follow these steps.

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

2.1.2.4 - IP Change

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

IP Change

You can change the IP of the Virtual Server.

Caution
  • If you proceed with changing the IP, you will no longer be able to communicate with that IP, and you cannot cancel the IP change while it is in progress.
  • The server will be rebooted to apply the changed IP.
  • If the server is running the Load Balancer service, you must delete the existing IP from the LB server group and directly add the changed IP as a member of the LB server group.
  • Servers using Public NAT/Private NAT must disable and reconfigure Public NAT/Private NAT after changing the IP.
    • If you are using Public NAT/Private NAT, first disable the use of Public NAT/Private NAT, complete the IP change, and then set it again.
  • Whether to use Public NAT/Private NAT can be changed by clicking the Edit button of Public NAT IP/Private NAT IP on the Virtual Server Details page.

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.

    Color mode
    ip a
    ip a
    Code block. ip command - network interface check command

    • If there is an added interface, the following result is displayed.
    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
    Code block. ip command - Network interface check result
  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.

    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
    Code block. Edit YAML file
Reference
Indentation is important in YAML files that configure netplan. When modifying a YAML file, please refer to the existing settings and be careful.
  1. Set the IP on the added network DEVICE using the netplan command.

    Color mode
    netplan --debug apply
    netplan --debug apply
    Code block. netplan applied
  2. Use the ip command to verify that the IP is set correctly.

    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
    Code block. Check IP settings

2.1.2.5 - Linux NTP Setting

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

Install NTP Daemon

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

Reference
For detailed information about chrony, please refer to the chronyc page.
  1. Check whether the chrony package is installed using the dnf command as the root user of the OS of the Virtual Server.

    Color mode
    dnf list chrony
    dnf list chrony
    Code block. dnf command - chrony package installation verification command

    • chrony If the chrony package is installed, the following result is displayed.
    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  
    Code block. dnf command - chrony package installation verification result
  2. If the chrony package is not installed, use the dnf command to install the chrony package.

    Color mode
    dnf install chrony -y
    dnf install chrony -y
    Code block. dnf command - chrony package installation verification command

NTP Daemon Setup

Reference
For detailed information about chrony, refer to the chronyc page.

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.

    Color mode
    server 198.19.0.54 iburst
    server 198.19.0.54 iburst
    Code block. /etc/chrony.conf edit
  3. Set it to automatically start the chrony daemon using the systemctl command.

    Color mode
    systemctl enable chronyd
    systemctl enable chronyd
    Code block. systemctl command - chrony daemon auto start setting
  4. Restart the chrony daemon using the systemctl command.

    Color mode
    systemctl restart chronyd
    systemctl restart chronyd
    Code block. systemctl command - restart chrony daemon

  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.

    Color mode
    chronyc sources -v
    chronyc sources -v
    Code block. chronyc sources command - NTP synchronization check

    • When you run the chronyc sources command, the following result is displayed.
    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
    Code block. chronyc sources command - NTP synchronization check
  6. Run the chronyc tracking command to check the synchronization metrics.

    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
    Code block. chronyc tracking command - NTP synchronization metric

2.1.2.6 - Setting up RHEL Repo and WKMS

Notice
  • If the user created RHEL and Windows Server prior to August 2025 via the Samsung Cloud Platform Console, they need to modify the RHEL Repository and WKMS (Windows Key Management Service) settings.
  • The SCP RHEL Repository is a repository provided by SCP to support user environments such as VPC Private Subnet where external access is restricted.
    Since the SCP RHEL Repository synchronizes with each Region Local Repository according to the internal schedule, it is recommended to switch to an external Public Mirror site to quickly apply the latest patches.

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.

    Color mode
    cat /etc/yum.repos.d/scp.rhel8.repo
    cat /etc/yum.repos.d/scp.rhel8.repo
    Code block. repo configuration check (RHEL8)
    Color mode
    cat /etc/yum.repos.d/scp.rhel9.repo
    cat /etc/yum.repos.d/scp.rhel9.repo
    Code block. repo configuration check (RHEL9)

    • When checking the configuration file, the following result is displayed.
      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
      Code block. Check repo settings (RHEL8)
      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
      Code block. Check repo settings (RHEL9)
  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.

    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
    Code block. /etc/hosts file setting change

  4. Verify the RHEL Repository connection configured on the server using the yum command.

    Color mode
    yum repolist –v
    yum repolist –v
    Code block. repository connection settings check

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

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.

    Color mode
    slmgr /skms 198.19.2.23:1688
    slmgr /skms 198.19.2.23:1688
    Code block. WKMS Settings

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

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

    Color mode
    slmgr /ato
    slmgr /ato
    Code block. Windows Server activation settings

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

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

    Color mode
    slmgr /dlv
    slmgr /dlv
    Code block. Windows Server genuine activation verification

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

    Figure
    Figure. Windows Server genuine activation verification

2.1.2.7 - Installing ServiceWatch Agent

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

Note
Collecting custom metrics/logs via the ServiceWatch Agent is currently only available on Samsung Cloud Platform for Enterprise. It will be offered for other offerings in the future.
Caution
Metrics collected via the ServiceWatch Agent are considered custom metrics and incur charges, unlike the default metrics collected from each service. Therefore, it is recommended to remove or disable unnecessary metric collection settings.

ServiceWatch Agent

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

CategoryDescription
Prometheus ExporterProvides metrics of a specific application or service in a format that Prometheus can scrape.
  • Depending on the OS, you can use the Node Exporter for Linux servers and the Windows Exporter for Windows servers.
Open Telemetry CollectorActs as a centralized collector that gathers telemetry data such as metrics and logs from distributed systems, processes them (filtering, sampling, etc.), and exports them to multiple backends (e.g., Prometheus, Jaeger, Elasticsearch).
  • Exports data to the ServiceWatch Gateway so that ServiceWatch can collect metric and log data.
Table. Description of Prometheus Exporter and Open Telemetry Collector

Prerequisites for Using ServiceWatch Agent

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

Installing Prometheus Exporter for Virtual Server (Linux)

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

Installing Node Exporter

Install Node Exporter according to the steps below.

  1. Create Node Exporter User
  2. Node Exporter Configuration

Create Node Exporter User

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

Color mode
sudo useradd --no-create-home --shell /bin/false node_exporter
sudo useradd --no-create-home --shell /bin/false node_exporter
Code block. Node Exporter User creation command

Node Exporter Configuration

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

    • Download path: /tmp
    • Version: 1.7.0
      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
      Code block. Node Exporter download command
      Note
      The latest Node Exporter version can be found at Node Exporter > Releases > Latest, and specific versions are available at Node Exporter > Releases.
  2. Install the downloaded Node Exporter and set permissions on the executable.

    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
    Code block. Node Exporter installation command
    Color mode
    sudo chown node_exporter:node_exporter /usr/local/bin/node_exporter
    sudo chown node_exporter:node_exporter /usr/local/bin/node_exporter
    Code block. Node Exporter permission setting command

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

    Color mode
    sudo vi /etc/systemd/system/node_exporter.service
    sudo vi /etc/systemd/system/node_exporter.service
    Code block. Open Node Exporter service file
    Color mode
    [Unit]
    Description=Prometheus Node Exporter (meminfo only)
    Wants=network-online.target
    After=network-online.target
    
    [Service]
    User=node_exporter
    Group=node_exporter
    Type=simple
    ExecStart=/usr/local/bin/node_exporter \
      --collector.disable-defaults \    # Disable default collectors
      --collector.meminfo \             # Enable memory metrics
      --collector.filesystem            # Enable block storage filesystem metrics
    
    Restart=on-failure
    
    [Install]
    WantedBy=multi-user.target
    [Unit]
    Description=Prometheus Node Exporter (meminfo only)
    Wants=network-online.target
    After=network-online.target
    
    [Service]
    User=node_exporter
    Group=node_exporter
    Type=simple
    ExecStart=/usr/local/bin/node_exporter \
      --collector.disable-defaults \    # Disable default collectors
      --collector.meminfo \             # Enable memory metrics
      --collector.filesystem            # Enable block storage filesystem metrics
    
    Restart=on-failure
    
    [Install]
    WantedBy=multi-user.target
    Code block. Node Exporter service file content
    Note
    • Collectors can be enabled or disabled using flags.

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

    CollectorDescriptionLabels
    meminfoProvides memory statistics-
    filesystemProvides filesystem statistics such as used disk space
    • device: Physical or virtual device path where the filesystem is located (e.g., /dev/sda1)
    • fstype: Filesystem type (e.g., ext4, xfs, nfs, tmpfs)
    • mountpoint: Path where the filesystem is mounted on the host OS; serves as an intuitive way to distinguish disks (e.g., /, /var/lib/docker, /mnt/data)
    Table. Description of main Node Exporter collectors
    • For detailed information on available metrics and configuration, see the Node Exporter > Collector page.
    • Available metrics may vary depending on the version of Node Exporter you use. See the Node Exporter repository.

Caution
Metrics collected via the ServiceWatch Agent are considered custom metrics and incur charges, unlike the default metrics collected from each service. Remove or disable unnecessary metric collection to avoid excessive charges.
  1. Enable and start the service. Register the Node Exporter service and verify the registered service and configured metrics.
    Color mode
    sudo systemctl daemon-reload
    sudo systemctl enable --now node_exporter
    sudo systemctl daemon-reload
    sudo systemctl enable --now node_exporter
    Code block. Enable and start Node Exporter service
    Color mode
    sudo systemctl status node_exporter
    sudo systemctl status node_exporter
    Code block. Check Node Exporter service status
    Color mode
    curl http://localhost:9100/metrics | grep node_memory
    curl http://localhost:9100/metrics | grep node_memory
    Code block. Verify Node Exporter metrics
Info
After completing the Node Exporter setup, you must install the Open Telemetry Collector provided by ServiceWatch to finish the ServiceWatch Agent configuration.
See ServiceWatch > Using ServiceWatch Agent for details.

Installing Prometheus Exporter for Virtual Server (Windows)

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

Installing Windows Exporter

Install the Windows Exporter according to the steps below.

  1. Windows Exporter Configuration

Windows Exporter Configuration

  1. Download the Windows Exporter installation file.

    • Download path: C:\Temp
    • Test version: 0.31.3
      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"
      Code block. Windows Exporter download
      Note
      Windows Exporter versions and installation files can be found at Windows Exporter > Releases.
  2. Test the Windows Exporter execution. By default, Windows Exporter enables all collectors, but to collect only desired metrics, enable the following collectors:

    • Memory metrics: memory
    • Block storage metrics: logical_disk
    • Host name: os
      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
      Code block. Test Windows Exporter execution
Note
  • Collectors can be enabled using flags.

    • <code>--collectors.enabled "[defaults]"</code>: Enables the default provided metrics.
    • <code>--collector.enabled {name},{name},{name}...</code>: Enables specific metrics.
  • Below is a description of the main collectors.

CollectorDescriptionLabels
memoryProvides memory statistics
logical_diskCollects performance and status metrics of local logical disks (e.g., C:, D: drives)
  • volume: Physical or virtual device path where the filesystem resides (e.g., C:, D:)
Table. Description of main Windows Exporter collectors
참고
  • Available metrics may vary depending on the version of Windows Exporter you use. See the Windows Exporter repository.
Caution
Metrics collected via the ServiceWatch Agent are considered custom metrics and incur charges, unlike the default metrics collected from each service. Remove or disable unnecessary metric collection to avoid excessive charges.
  1. Register the service and verify.

    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
    Code block. Register Windows Exporter service
    Color mode
    # Verify service
    $ Get-Service windows_exporter
    
    # Verify metrics
    $ Invoke-WebRequest -Uri "http://localhost:9182/metrics" | Select-String memory
    # Verify service
    $ Get-Service windows_exporter
    
    # Verify metrics
    $ Invoke-WebRequest -Uri "http://localhost:9182/metrics" | Select-String memory
    Code block. Verify Windows Exporter service

  2. Set configuration file.

    • Use the --config.file option to specify a YAML configuration file.
      Color mode
      $ .\windows_exporter.exe --config.file=config.yml
      $ .\windows_exporter.exe --config.file="C:\Program Files\windows_exporter\config.yml" # When using an absolute path, wrap it in quotes
      $ .\windows_exporter.exe --config.file=config.yml
      $ .\windows_exporter.exe --config.file="C:\Program Files\windows_exporter\config.yml" # When using an absolute path, wrap it in quotes
      Code block. Run Windows Exporter with config file
      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
      Code block. Sample Windows Exporter config

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
Code block. Register Windows Exporter with config file
Note
When using both a configuration file and command‑line options, command‑line options take precedence over configuration file values.

Info
After completing the Windows Exporter setup, you must install the Open Telemetry Collector provided by ServiceWatch to finish the ServiceWatch Agent configuration.
See ServiceWatch > Using ServiceWatch Agent for details.

Node Exporter Metrics

Main Node Exporter metrics

The following are the collector and metric information available through Node Exporter. Collectors can be enabled, and specific metrics can be activated.

CategoryCollectorMetricDescription
Memorymeminfonode_memory_MemTotal_bytesTotal memory
Memorymeminfonode_memory_MemAvailable_bytesAvailable memory (used for determining memory shortage)
Memorymeminfonode_memory_MemFree_bytesFree memory
Memorymeminfonode_memory_Buffers_bytesIO buffers
Memorymeminfonode_memory_Cached_bytesPage cache
Memorymeminfonode_memory_SwapTotal_bytesTotal swap
Memorymeminfonode_memory_SwapFree_bytesRemaining swap
Filesystemfilesystemnode_filesystem_size_bytesTotal filesystem size
Filesystemfilesystemnode_filesystem_free_bytesTotal free space
Filesystemfilesystemnode_filesystem_avail_bytesSpace actually available to unprivileged users
Table. Main Node Exporter metrics

Node Exporter collector and metric collection settings

Node Exporter enables most collectors by default, but you can enable or disable specific collectors as needed.

Enable specific collectors only

  • When you want to use only memory and filesystem collectors:
    Color mode
    ./node_exporter \
      --collector.meminfo            # Enable memory collector
      --collector.filesystem         # Enable filesystem collector
    ./node_exporter \
      --collector.meminfo            # Enable memory collector
      --collector.filesystem         # Enable filesystem collector
    Code block. Enable specific Node Exporter collectors
  • When you want to disable all default collectors and use only memory and filesystem collectors:
    Color mode
    ./node_exporter \
      --collector.disable-defaults    # Disable default metrics
      --collector.meminfo             # Enable memory collector
      --collector.filesystem          # Enable filesystem collector
    ./node_exporter \
      --collector.disable-defaults    # Disable default metrics
      --collector.meminfo             # Enable memory collector
      --collector.filesystem          # Enable filesystem collector
    Code block. Enable specific Node Exporter collectors (disable defaults)
  • Enable filesystem collector for specific mount points:
    Color mode
    ./node_exporter \
      --collector.disable-defaults \
      --collector.filesystem.mount-points-include="/|/data"          # Enable filesystem collector for / (root) and /data mount points
    ./node_exporter \
      --collector.disable-defaults \
      --collector.filesystem.mount-points-include="/|/data"          # Enable filesystem collector for / (root) and /data mount points
    Code block. Enable filesystem collector for specific mount points
  • Enable filesystem collector excluding specific mount points:
    Color mode
    ./node_exporter \
      --collector.disable-defaults \
      --collector.filesystem.mount-points-exclude="/boot|/var/log"    # Exclude /boot and /var/log mount points
    ./node_exporter \
      --collector.disable-defaults \
      --collector.filesystem.mount-points-exclude="/boot|/var/log"    # Exclude /boot and /var/log mount points
    Code block. Exclude specific mount points from filesystem collector

Disable specific collectors (no-collector)

When you do not want to use the filesystem collector:

Color mode
./node_exporter --no-collector.filesystem
./node_exporter --no-collector.filesystem
Code block. Disable specific Node Exporter collector

Color mode
[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
Code block. /etc/systemd/system/node_exporter.service configuration

Filter specific metrics

Using the Open Telemetry Collector configuration, you can select only the required metrics collected by Node Exporter.
For guidance on pre‑configuring the Open Telemetry Collector for ServiceWatch, see Prerequisite Open Telemetry Collector configuration for ServiceWatch.

Caution
Metrics collected via the ServiceWatch Agent are considered custom metrics and incur charges, unlike the default metrics collected from each service. It is recommended to configure only the necessary metrics.

Windows Exporter Metrics

Main Windows Exporter metrics

The following are the collector and metric information available through Windows Exporter. Collectors can be enabled, and specific metrics can be activated.

CategoryCollectorMetricDescription
Memorymemorywindows_memory_available_bytesAvailable memory
Memorymemorywindows_memory_cache_bytesCached memory
Memorymemorywindows_memory_committed_bytesCommitted memory
Memorymemorywindows_memory_commit_limitCommit limit
Memorymemorywindows_memory_pool_paged_bytesPaged pool
Memorymemorywindows_memory_pool_nonpaged_bytesNon‑paged pool
Disklogical_diskwindows_logical_disk_free_bytesFree space
Disklogical_diskwindows_logical_disk_size_bytesTotal capacity
Disklogical_diskwindows_logical_disk_read_bytes_totalTotal read bytes
Disklogical_diskwindows_logical_disk_write_bytes_totalTotal written bytes
Disklogical_diskwindows_logical_disk_read_seconds_totalRead latency
Disklogical_diskwindows_logical_disk_write_seconds_totalWrite latency
Disklogical_diskwindows_logical_disk_idle_seconds_totalIdle time
Table. Main Windows Exporter metrics

Windows Exporter collector and metric collection settings

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

Enable specific collectors only

If you want to use only CPU, memory, and logical disk collectors:

Color mode
# The --collector.enabled option disables defaults and enables only the listed collectors
.\windows_exporter.exe --collectors.enabled="memory,logical_disk"
# The --collector.enabled option disables defaults and enables only the listed collectors
.\windows_exporter.exe --collectors.enabled="memory,logical_disk"
Code block. Enable specific Windows Exporter collectors

Note
Windows Exporter does not need you to disable unused collectors; using --collector.enabled will collect only the collectors specified in the option.

Color mode
# 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
# Start the service
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
# Start the service
Start-Service windows_exporter
Code block. Register service
Color mode
# Note this is not an exhaustive list of all configuration values
collectors:
  enabled: logical_disk,memory # Set collectors 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 # Set collectors 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"
Code block. Service configuration file

Filter specific metrics

Using the Open Telemetry Collector configuration, you can select only the required metrics collected by Windows Exporter.
For guidance on pre‑configuring the Open Telemetry Collector for ServiceWatch, see Prerequisite Open Telemetry Collector configuration for ServiceWatch.

Caution
Metrics collected via the ServiceWatch Agent are considered custom metrics and incur charges, unlike the default metrics collected from each service. It is recommended to configure only the necessary metrics.

2.1.3 - API Reference

API Reference

2.1.4 - CLI Reference

CLI Reference

2.1.5 - Release Note

Virtual Server

2026.03.19
FEATURE Standard image addition and SSD_Provisioned disk type addition and ServiceWatch metric monitoring feature addition
  • OS Image addition provision
    • Standard Image has been added. (Window server 2016)
  • SSD volume with configurable IOPS and Throughput has been added.
    • You can select SSD_Provisioned disk type when creating Block Storage.
    • You can set IOPS and Throughput maximum values.
  • You can view Virtual Server ServiceWatch metric monitoring graphs on the detail page.
2025.12.16
FEATURE Virtual Server feature addition
  • OS Image addition provision
    • Standard Image has been added. (Alma Linux 9.6, Oracle Linux 9.6, RHEL 9.6, Rocky Linux 9.6)
  • New Server Group policy addition
    • Partition (Virtual Server and Block Storage distributed placement) policy has been added.
  • You can collect custom metrics and logs by installing Virtual Server ServiceWatch Agent.
2025.10.23
FEATURE Server name change feature addition and ServiceWatch service integration provision
  • You can change the server name on the Virtual Server detail page of Samsung Cloud Platform Console.
    • When changing the server name, only the information in Samsung Cloud Platform Console is changed, not the OS’s Hostname.
  • ServiceWatch service integration provision
    • You can monitor data through ServiceWatch service.
2025.07.01
FEATURE Virtual Server feature addition and Image sharing method change
  • Virtual Server feature addition
    • IP, Public NAT IP, Private NAT IP configuration feature has been added.
    • LLM Endpoint for using LLM is provided.
    • You can select OS Image subscribed from Marketplace when creating Virtual Server.
    • 2nd generation server type has been added.
      • 2nd generation (s2) server type based on Intel 4th generation (Sapphire Rapids) Processor has been added. For details, refer to Virtual Server Server Type
  • Image sharing method between Accounts has been changed.
    • You can share by creating a new qcow2 Image or Image for sharing.
2025.02.27
FEATURE NAT configuration feature and OS Image, server type addition
  • Virtual Server feature addition
    • NAT configuration feature has been added in Virtual Server.
    • OS Image addition provision
      • Standard Image has been added. (Alma Linux 8.10, Alma Linux 9.4, Oracle Linux 8.10, Oracle Linux 9.4, RHEL 8.10, RHEL 9.4, Rocky Linux 8.10, Rocky Linux 9.4, Ubuntu 24.04)
      • Image for Kubernetes has been added. You can create Kubernetes Engine using Image for Kubernetes.
    • 2nd generation server type addition
      • 2nd generation (h2) server type based on Intel 4th generation (Sapphire Rapids) Processor has been added. For details, refer to Virtual Server Server Type
  • Samsung Cloud Platform common function change
    • Common CX changes such as Account, IAM and Service Home, tags have been reflected.
2024.10.01
NEW Virtual Server service official version release
  • Virtual Server service official release.
  • We have released a virtualization server that allows you to freely allocate and use as much as you need at the necessary time without purchasing infrastructure resources individually.
2024.07.02
NEW Beta version release
  • We have released a virtualization server that allows you to freely allocate and use as much as you need at the necessary time without purchasing infrastructure resources individually.

2.2 - Virtual Server Auto-Scaling

2.2.1 - Overview

Service Overview

Virtual Server Auto-Scaling is a service that automatically scales resources up or down according to demand. You can add or terminate the number of servers running the application according to predefined conditions or schedule.
Auto-Scaling Group uses a pre-created Launch Configuration as a pre-configuration template to create servers, and can adjust and manage the number of servers. It adjusts so that the number does not fall below the specified minimum number of servers or exceed the maximum number of servers.
If you register a schedule with Auto-Scaling Group, you can set the number of servers according to the predetermined schedule. If you register a policy, you can increase or decrease the number of servers based on predefined conditions.

Features

  • Easy and convenient computing environment configuration: Through the web-based Console, users can easily configure the required computing environment themselves via Self Service, from creating Launch Configurations to creating/modifying/deleting Auto-Scaling Groups.

  • Elastic Resource Usage: You can elastically use computing resources according to the service’s load and usage. Users can schedule resource usage for predictable specific time periods, and can adjust resource usage to prepare for temporary connections from an unspecified large number of users.

  • Availability Improvement: Virtual Server Auto-Scaling adjusts resources to match variable demand so that the traffic required by the user can always be processed. Through this, users can achieve improved application performance and availability.

  • Maximizing Cost Reduction Effect: By using resources only as needed according to demand fluctuations, unnecessary costs can be reduced. Through flexible resource usage according to traffic increases or decreases at specific times such as night, weekends, and month-end, the cost reduction effect can be maximized.

Service Architecture Diagram

Diagram
Figure. Virtual Server Auto-Scaling Diagram

Provided Features

Virtual Server Auto-Scaling provides the following features.

  • Launch Configuration: It is a configuration template used to create a Virtual Server in an Auto-Scaling Group. When creating a Launch Configuration, you set information about the Virtual Server such as image, server type, key pair, block storage, etc.
  • Server Count Adjustment: Provides several ways to adjust the number of servers. Using policies, you can add a Virtual Server when the load exceeds a threshold and release the Virtual Server when demand is low, maintaining application availability and reducing costs. You can add and release Virtual Servers according to a schedule, and you can also manually adjust the number of servers in an Auto-Scaling Group as needed.
  • Load Balancer integration: You can use a Load Balancer to evenly distribute application traffic to Virtual Server. Whenever a Virtual Server is added or removed, it is automatically registered and deregistered with the Load Balancer.
  • Network Connection: You can connect the general subnet of the Auto-Scaling Group, automatic IP allocation, and a Public NAT IP. It provides a local subnet connection for inter-server communication.
  • Security Group applied: Security Group is a virtual logical firewall that controls inbound/outbound traffic generated on a Virtual Server. Inbound rules control incoming traffic to the Virtual Server, and Outbound rules control outgoing traffic from the Virtual Server.
  • Monitoring: You can view monitoring information such as CPU, Memory, Disk of Virtual Servers created in the Auto-Scaling Group through the Cloud Monitoring service. Based on the monitoring information, you can use Auto-Scaling policies to set thresholds for load, and when the threshold is exceeded, you can add or remove servers.

Components

Virtual Server Auto-Scaling creates an Auto-Scaling Group through Launch Configuration and checks and manages the server.

Launch Configuration

This is a Configuration template used to create a Virtual Server in an Auto-Scaling Group. The main features are as follows.

  • Image: Provides OS standard images and user-created custom images. Users can select and use them according to the service they want to configure.
  • Keypair: Provides the Keypair method for a secure OS access method.
  • Init script: The user can define a script to be executed when the Virtual Server starts.
  • For more details, please refer to Launch Configuration Creating.
Reference
For images and server types selectable in Launch Configuration, refer to Virtual Server OS Image Provision Version and Virtual Server Server Type.

Auto-Scaling Group

Use Launch Configuration as a pre-configuration template for server creation. You can create an Auto-Scaling Group to adjust and manage the number of servers. The main features are as follows.

  • Launch Configuration: It is a configuration template used to create a Virtual Server in an Auto-Scaling Group.
  • Server Count Settings: Virtual Server Auto-Scaling provides several ways to adjust the number of servers in an Auto-Scaling Group.
    • Fixed Server Count Method: When creating an Auto-Scaling Group, this method keeps the default settings by maintaining the configured number of servers without any added schedules or policies. Refer to Create Auto-Scaling Group and set the Min, Desired, Max server counts.
    • Manual Server Count Adjustment Method: In an Auto-Scaling Group, this method increases or decreases the number of servers by modifying the server count to the desired amount. You can choose whether to manually set the desired number of servers. Refer to Modify Server Count.
    • Schedule Reservation Method: You can schedule daily, weekly, monthly, or one-time, and set the desired number of servers at a specified time. This is useful when you can predict when to reduce or increase the number of servers. If you use the schedule method, refer to Manage Schedule to add and manage schedules.
    • Policy Method: You can use a policy as a way to dynamically adjust servers. When the set threshold based on monitoring metrics is exceeded, it adjusts the number of servers. At this time, you can choose one of three ways to adjust the server count. Increase or decrease the number of servers by a specified number, increase or decrease by a specified ratio, or fix the number of servers to an entered value. When servers start and terminate due to the policy, the monitoring metric CPU usage may temporarily exceed the threshold registered in the policy. However, because this is a temporary moment, a cooldown period is set to avoid judging it as an abnormal situation. If you want to use the policy method, refer to Manage Policies.
  • Load Balancer: Whenever a Virtual Server is added or terminated, it automatically connects to and disconnects from the Load Balancer registered in the Auto-Scaling Group.
Reference
Auo-Scaling Group’s Load Balancer operates in conjunction with Load Balancer from February 2025.

Constraints

The constraints of Virtual Server Auto-Scaling are as follows.

CategoryDescription
Number of Virtual Servers per Auto-Scaling Group50 or less
Number of policies per Auto-Scaling Group12 or fewer
Number of schedules per Auto-Scaling Group20 or fewer
Number of LB server groups and ports per Auto-Scaling Group3 or less
Table. Virtual Server Auto-Scaling Group Constraints
Caution
  • If the Image you are using is a discontinued standard Image, Scale-out will not work.
    If the Image you are using is a Custom Image, Scale out will continue to work properly even after the version is no longer provided.
  • Before the end of support for the Image you are using, we recommend replacing the Launch Configuration with the latest version of the Image or a Custom Image.
  • For detailed information about the OS Image provided by Virtual Server, see OS Image Provided Versions.

Preliminary Service

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

Service CategoryServiceDetailed Description
NetworkingVPCA service that provides an independent virtual network in a cloud environment
NetworkingSecurity GroupVirtual firewall that controls server traffic
Table. Virtual Server Auto-Scaling Preliminary Service

2.2.1.1 - Monitoring Metrics

Virtual Server Auto-Scaling is a service provided for Virtual Server targets, providing individual Virtual Server monitoring metrics and monitoring metrics provided by Cloud Monitoring-based policies.

Virtual Server monitoring metrics

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

For Windows OS, memory-related metrics are not provided.

Performance ItemDetailed DescriptionUnit
Memory Total [Basic]Available memory bytesbytes
Memory Used [Basic]Currently used memory bytesbytes
Memory Swap In [Basic]Replaced memory bytesbytes
Memory Swap Out [Basic]Replaced memory bytesbytes
Memory Free [Basic]Unused memory bytesbytes
Disk Read Bytes [Basic]Read bytesbytes
Disk Read Requests [Basic]Number of Read Requestscnt
Disk Write Bytes [Basic]Write bytesbytes
Disk Write Requests [Basic]Write Request Countcnt
CPU Usage [Basic]1-minute average system CPU usage rate%
Instance State [Basic]Instance Statusstate
Network In Bytes [Basic]Received bytesbytes
Network In Dropped [Basic]Received Packet Dropcnt
Network In Packets [Basic]Received Packet Countcnt
Network Out Bytes [Basic]Transmission bytesbytes
Network Out Dropped [Basic]Transmission Packet Dropcnt
Network Out Packets [Basic]Transmission Packet Countcnt
Fig. Virtual Server Monitoring Metrics (Default Provided)

Monitoring metrics provided by Cloud Monitoring-based policies

The following table shows the monitoring metrics provided by the policy of Cloud Monitoring-based Auto-Scaling Group. For more information on policy settings, see Managing Policies.

Performance ItemDetailed DescriptionUnit
CPU Usage [Basic]1-minute average system CPU usage rate%
Memory Used [Basic]Currently used memory bytesbytes
Network In Bytes [Basic]Received bytesbytes
Network In Packets [Basic]Number of Received Packetscnt
Network Out Bytes [Basic]Transmission bytesbytes
Network Out Packets [Basic]Transmission Packet Countcnt
Fig. Monitoring metrics provided by Cloud Monitoring-based policies

2.2.1.2 - ServiceWatch 지표

Virtual Server Auto-Scaling is a service offered for Virtual Servers that provides individual Virtual Server monitoring metrics as well as monitoring metrics supplied by ServiceWatch‑based policies.

Virtual Server Monitoring Metrics

The basic metrics provided by Virtual Server can be found in ServiceWatch > Virtual Server Basic Metrics.

참고
Refer to the ServiceWatch guide for how to view metrics in ServiceWatch.

ServiceWatch monitoring metrics provided by the Auto-Scaling Group policy

The table below shows the ServiceWatch monitoring metrics provided by the Auto-Scaling Group policy. For detailed information on Auto-Scaling Group policy configuration, see Managing Policies.

Performance ItemsDetailed descriptionunit
CPU UsageCPU usagePercent
Network In BytesBytes received on the network interfaceBytes
Network In PacketsNumber of packets received on the network interfaceCount
Network Out BytesData transmitted on the network interface (bytes)Bytes
Network Out PacketsNumber of packets transmitted on the network interfaceCount
표. Auto-Scaling Group의 정책에서 제공하는 ServiceWatch 모니터링 지표

2.2.2 - How-to guides

Users can create an Auto-Scaling Group service by entering the required information and selecting detailed options through the Samsung Cloud Platform Console.

Creating an Auto-Scaling Group

You can create an Auto-Scaling Group service through the Samsung Cloud Platform Console.

Note
To create an Auto-Scaling Group, you need to create a Launch Configuration in advance. Please refer to Creating a Launch Configuration.

To create an Auto-Scaling Group, follow these steps:

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

  2. Click the Auto-Scaling Group menu. It will move to the Auto-Scaling Group list page.

  3. On the Auto-Scaling Group list page, click the Create Auto-Scaling Group button. It will move to the Create Auto-Scaling Group page.

  4. On the Create Auto-Scaling Group page, enter the information required to create the service.

    • In the Launch Configuration section, select a Launch Configuration.
      • You can create a new Launch Configuration by clicking the Create Launch Configuration button.
    • In the Service Information Input section, enter or select the required information.
      Category
      Required
      Detailed Description
      Auto-Scaling Group NameRequiredAuto-Scaling Group name
      • Manage servers of the same type and purpose as a group
      Server NameRequiredServer name within the Auto-Scaling Group
      • An identifier to distinguish servers created within the Auto-Scaling Group, automatically assigned based on the input server name and sequence
      Number of ServersRequiredNumber of servers to create in the Auto-Scaling Group
      • Enter a value between 0 and 20 (Min≤Desired≤Max)
      • Min: Set the minimum number of servers for the Auto-Scaling Group to maintain
      • Desired: Set the target number of servers within the Auto-Scaling Group, also meaning the initial number of servers created when the Auto-Scaling Group is created
      • Max: Set the maximum number of servers that the Auto-Scaling Group can maintain
      Manual Desired Server Count SettingOptionalChoose whether to manually change the Desired server count
      Network Settings > Network SettingsRequiredNetwork settings for the Auto-Scaling Group
      • Select the desired VPC and general Subnet
      • IP can only be automatically generated
      • If you select a local Subnet, you can choose the desired local Subnet, and IP can only be automatically generated
      Network Settings > Security GroupOptionalSet a Security Group to allow necessary access
      • If you don’t set a Security Group, it will follow the default rule (Any/Deny) and block all inbound and outbound traffic
      • For Linux servers, allow SSH traffic
      • For Windows servers, allow RDP traffic
      • After creating the Auto-Scaling Group, you can modify the settings using the Modify button. For more information, refer to Setting Security Group
      Load BalancerOptionalConnect the Auto-Scaling Group to a Load Balancer
      • Register the servers in the Auto-Scaling Group as members of the LB server group
      • LB server group: Select an existing LB server group in the chosen VPC
      • Port: Enter a value between 1 and 65,534
      • Click the + button to add an LB server group (up to 3 LB server groups and ports can be added)
      • Weighted Round Robin or Weighted Least Connection load balancing LB server groups cannot be selected
      • Draining Timeout value: If Draining Timeout is checked as used, set the Draining Timeout value
        • Draining Timeout: The time to wait before disconnecting the server from the Load Balancer
          • This allows for safe session cleanup, as sessions connected to the server may still exist
        • If Load Balancer is not used, Draining Timeout setting is not available
        • The default value is 300 seconds, and you can enter a value between 1 second and 3,600 seconds
      Table. Auto-Scaling Group Service Information Input Items
    • In the Scaling Policy Settings section, set the scaling policy.
      • For more information on policy settings, refer to Adding a Policy.
        Category
        Required
        Detailed Description
        Set NowOptionalSet the scaling policy now
        • Click the Add Policy button to display the policy information input items
        Set LaterOptionalSet the policy after creating the Auto-Scaling Group, on the detailed information page
        Table. Auto-Scaling Group Scaling Policy Settings Items
    • In the Notification Settings section, set the notification recipient and method.
      • For more information on notification settings, refer to Adding a Notification.
        Category
        Required
        Detailed Description
        Set NowOptionalSet the notification recipient and method now
        • Click the Add Notification button to open the Add Notification popup window
        • For more information on notification settings, refer to the detailed information
        • Click the Modify button in the notification recipient list to change the notification information
        Set LaterOptionalSet the notification recipient and method after creating the Auto-Scaling Group, on the detailed information page
        Table. Auto-Scaling Group Notification Settings Items
    • In the Additional Information Input section, enter or select the required information.
      Category
      Required
      Detailed Description
      TagOptionalAdd a tag
      • Up to 50 tags can be added per resource
      • Click the Add Tag button, then enter or select the Key and Value
      Table. Auto-Scaling Group Additional Information Input Items
  5. In the Summary panel, review the created details and estimated billing amount, then click the Complete button.

    • After creation is complete, you can find the created Auto-Scaling Group on the Auto-Scaling Group list page.

Checking Auto-Scaling Group Details

The Auto-Scaling Group service allows you to view and modify the overall resource list and detailed information. The Auto-Scaling Group details page consists of Details, Policy, Schedule, Virtual Server, Load Balancer, Tag, and Work History tabs.

To check the Auto-Scaling Group details, follow these steps:

  1. Click All Services > Compute > Virtual Server menu. It will move to the Virtual Server’s Service Home page.
  2. Click the Auto-Scaling Group menu. It will move to the Auto-Scaling Group list page.
  3. On the Auto-Scaling Group list page, click the resource you want to check the details for. It will move to the Auto-Scaling Group details page.
    • The Auto-Scaling Group details page displays status information and additional feature information, and consists of Details, Policy, Schedule, Virtual Server, Load Balancer, Tag, and Work History tabs.
      CategoryDetailed Description
      Auto-Scaling Group StatusThe status of the Auto-Scaling Group created by the user
      • Creating: Auto-Scaling Group creation in progress
      • In Service: Serviceable state
      • Scale In: Scale In in progress
      • Scale Out: Scale Out in progress
      • Cool Down: Cool-down wait in progress
      • Terminating: Auto-Scaling Group deletion in progress
      • Attach to LB: Connecting to Load Balancer in progress
      • Detach from LB: Detaching from Load Balancer in progress
      Auto-Scaling Group DeletionButton to delete the Auto-Scaling Group
      Table. Auto-Scaling Group Status Information and Additional Features

Details

… (rest of the content remains the same) Auto-Scaling Group Details page where you can check the detailed information of the selected resource and modify the information if necessary.

CategoryDetailed Description
ServiceService name
Resource TypeResource type
SRNUnique resource ID in Samsung Cloud Platform
  • Auto-Scaling Group refers to Auto-Scaling Group SRN
Resource NameResource name
  • Auto-Scaling Group refers to Auto-Scaling Group name
Resource IDUnique resource ID in the service
CreatorUser who created the service
Creation TimeTime when the service was created
ModifierUser who modified the service information
Modification TimeTime when the service information was modified
Auto-Scaling Group NameAuto-Scaling Group name
Launch Configuration NameLaunch Configuration name selected when creating the Auto-Scaling Group
  • Image template used when creating a Virtual Server in the Auto-Scaling Group
Number of ServersCurrent number of servers in the Auto-Scaling Group and set Min, Desired, Max server numbers
Manual Setting of Desired Server NumberUse or do not use manual setting of Desired server number
VPCVPC information of the Auto-Scaling Group
General SubnetGeneral Subnet and NAT IP usage information of the Auto-Scaling Group
Local SubnetLocal Subnet information of the Auto-Scaling Group
Security GroupSecurity Group information of the Auto-Scaling Group
  • If you want to change the Security Group, click the Modify button to set. For more information, see Setting Security Group
Table. Auto-Scaling Group Details - Details Tab Items

Policy

On the Auto-Scaling Group List page, you can check the policy list of the selected resource and add or manage policies if necessary.

CategoryDetailed Description
CategoryPolicy category
  • Scale In: Server number return
  • Scale Out: Server number increase
Policy NamePolicy name
Execution ConditionCondition for executing the policy
  • Statistic: Method of calculating Metric Type
    • Average: Average of servers in the Auto-Scaling Group
    • Min: Minimum value among servers in the Auto-Scaling Group
    • Max: Maximum value among servers in the Auto-Scaling Group
  • Metric Type: CPU Usage, Memory Usage, Network In(Bytes), Network Out(Bytes), Network In(Packets), Network Out(Packets)
  • Operator: >= > <= <
  • Threshold: Threshold for Metric Type
  • Period: Continuous time to trigger the execution condition (N minutes)
Execution UnitMethod of executing the policy
  • Policy Type: Type of policy to execute
    • Increase or decrease server number by a specified number: Increase or decrease server number by a target value
    • Increase or decrease server number by a specified ratio: Increase or decrease server number by a target ratio
    • Fix server number to a specified value: Fix server number to a target value
  • Target Value: Number or ratio to execute the selected Policy Type
Cool-downWaiting time (in seconds) after the policy starts or stops a server
  • Default value is 300 seconds, and can be set between 1 second and 3,600 seconds
More > ModifyModify the policy information
More > ActivateActivate the policy
  • Only available when the policy is deactivated
More > DeactivateDeactivate the policy
  • Only available when the policy is activated
Table. Auto-Scaling Group Details - Policy Tab Items

For more information on policy management and policy examples, see Policy Management.

Schedule

On the Auto-Scaling Group List page, you can check the schedule list of the selected resource and add or manage schedules if necessary.

CategoryDetailed Description
NameSchedule name
MinMinimum server number set in the schedule
DesiredTarget server number set in the schedule
MaxMaximum server number set in the schedule
PeriodSchedule execution period
  • Can be set to daily, weekly, monthly, or one-time
Date/Day of the WeekSchedule execution date or day of the week
  • Depends on the selected schedule period
Execution TimeSchedule execution time
Time ZoneSchedule execution time zone
StatusSchedule status
More > ModifyModify the schedule information
More > ActivateActivate the schedule
  • Only available when the schedule is deactivated
More > DeactivateDeactivate the schedule
  • Only available when the schedule is activated
Table. Auto-Scaling Group Details - Schedule Tab Items

For more information on schedule management, see Adding Schedule and Deleting Schedule.

Virtual Server

On the Auto-Scaling Group List page, you can check the Virtual Server list of the selected resource.

CategoryDetailed Description
Server NameName of the server created in the Auto-Scaling Group
  • Clicking the Server Name will move to the Virtual Server Details page
IPIP assigned to the server
Creation TimeDate and time when the server was created
StatusServer status
Load Balancer Connection StatusLoad Balancer connection status
  • Attaching: Load Balancer connection in progress
  • Attached: Load Balancer connected
  • Attach Error: Load Balancer connection error
  • Detaching: Load Balancer disconnection in progress
  • Detached: Load Balancer disconnected
  • Detach Error: Load Balancer disconnection error
Table. Auto-Scaling Group Details - Virtual Server Tab Items

Load Balancer

On the Auto-Scaling Group List page, you can check the Load Balancer list of the selected resource and add or manage Load Balancers if necessary.

CategoryDetailed Description
Draining TimeoutDraining Timeout usage
  • Click the Modify button to set the Draining Timeout usage
  • If already in use, change the time
  • Load Balancer is not in use, Draining Timeout setting is not possible.
Load BalancerLoad Balancer usage
  • Click the Modify button to set the Load Balancer usage
  • If already in use, add or change the Load Balancer
  • Up to 3 Load Balancer server groups can be added
Load Balancer > Load Balancer NameLoad Balancer name to connect to the Auto-Scaling Group
Load Balancer > LB Server GroupLoad Balancer’s LB server group
  • LB server groups using Weighted Round Robin or Weighted Least Connection load balancing are not selectable
Load Balancer > PortPort registered as a member of the LB server group
Table. Auto-Scaling Group Details - Load Balancer Tab Items
Note

Notification

You can check the notification recipient information and notification method for the selected resource on the Auto-Scaling Group List page.

CategoryDetailed Description
Notification RecipientName of the notification recipient
EmailEmail of the notification recipient
Server CreationWhether to send a notification when a server creation-related notification occurs
  • Success: Whether to send when creation is successful
  • Failure: Whether to send when creation fails
Server TerminationWhether to send a notification when a server termination-related notification occurs
  • Success: Whether to send when termination is successful
  • Failure: Whether to send when termination fails
Policy Execution ConditionWhether to send a notification when the policy execution condition is met
StatusNotification activation status
  • Active: Activated
More > EditEdit the notification information
More > ActivateActivate the notification information
  • Only available when the notification is deactivated
More > DeactivateDeactivate the notification information
  • Only available when the notification is activated
Table. Auto-Scaling Group Details - Notification Tab Items

For more information on notification settings, refer to Managing Notifications.

Tag

You can check the tag information of the selected resource on the Auto-Scaling Group List page and add, modify, or delete tags.

CategoryDetailed Description
Tag ListTag list
  • Key and Value information of the tag can be checked
  • Up to 50 tags can be added per resource
  • When entering a tag, you can search and select from the existing Key and Value list
Table. Auto-Scaling Group Details - Tag Tab Items

Work History

You can check the work history of the selected resource on the Auto-Scaling Group List page.

CategoryDetailed Description
Work History ListResource change history
  • Work time, resource ID, resource name, work details, event topic, work result, and worker information can be checked
Table. Auto-Scaling Group Details - Work History Tab Items

Managing Auto-Scaling Group Resources

If you need to manage the created Auto-Scaling Group, you can perform tasks on the Auto-Scaling Group Details page.

Modifying Launch Configuration

You can modify the Launch Configuration of the Auto-Scaling Group.

Note
Modifying the Launch Configuration does not apply to existing servers in the Auto-Scaling Group. It only applies to newly created servers. If you want to apply the modified Launch Configuration to all servers in the Auto-Scaling Group, adjust the server count (Desired) to 0 to delete all existing servers, and then modify the server count (Desired) to the desired quantity.

To modify the Launch Configuration of the Auto-Scaling Group, follow these steps:

  1. Click All Services > Compute > Virtual Server. The Virtual Server Service Home page opens.

  2. Click Auto-Scaling Group. The Auto-Scaling Group List page opens.

  3. On the Auto-Scaling Group List page, click the resource for which you want to modify the Launch Configuration. The Auto-Scaling Group Details page opens.

  4. Click the Modify button next to the Launch Configuration name. The Modify Launch Configuration popup window opens, where you can view the list of available Launch Configurations.

    Category
    Detailed Description
    Launch Configuration NameLaunch Configuration name
    ImageLaunch Configuration OS image
    Server TypeLaunch Configuration server type
    Block StorageLaunch Configuration Block Storage settings
    Auto-Scaling Group CountNumber of Auto-Scaling Groups to which the Launch Configuration is applied
    Detailed ViewButton to view detailed Launch Configuration information
    Table. Launch Configuration List Items

  5. In the Modify Launch Configuration popup window, select the Launch Configuration you want to modify and click OK. The Launch Configuration Modification Notification popup window opens. Check the message and click OK.

Modifying Server Count

You can modify the server count of the Auto-Scaling Group.

Note
The maximum number of servers that can be set is 50. However, if a Load Balancer is present, the number of servers not connected to the Load Balancer is excluded.

To modify the server count of the Auto-Scaling Group, follow these steps:

  1. Click All Services > Compute > Virtual Server. The Virtual Server Service Home page opens.
  2. Click Auto-Scaling Group. The Auto-Scaling Group List page opens.
  3. On the Auto-Scaling Group List page, click the resource for which you want to modify the server count. The Auto-Scaling Group Details page opens.
  4. Click the Edit Server Count button. The Edit Server Count popup window opens.
  5. In the Edit Server Count popup window, enter the required items and click the Confirm button.
    Classification
    Required
    Detailed Description
    Server Count > MinRequiredModify the minimum number of servers
    • Set the minimum number of servers that the Auto-Scaling Group will maintain
    Server Count > DesiredRequiredModify the target server count
    • Set the target server count in the Auto-Scaling Group
    Server Count > MaxRequiredModify the maximum server count
    • Set the maximum number of servers that the Auto-Scaling Group can maintain
    Table. Auto-Scaling Group Server Count Modification Items

Canceling a Virtual Server Created in an Auto-Scaling Group

A Virtual Server created in an Auto-Scaling Group can be canceled by reducing the desired number of servers.

To cancel a Virtual Server created in an Auto-Scaling Group, follow these steps:

  1. Click All Services > Compute > Virtual Server. You will be taken to the Virtual Server’s Service Home page.
  2. Click Auto-Scaling Group. You will be taken to the Auto-Scaling Group List page.
  3. On the Auto-Scaling Group List page, click the resource you want to cancel. You will be taken to the Auto-Scaling Group Details page.
  4. Click the Edit button in the Server Count section. The Edit Server Count popup window will open.
  5. In the Edit Server Count popup window, reduce the Desired count and click the Confirm button. The Desired server count will be adjusted, and the Virtual Server will be canceled.
Notice
If Manual Setting of Desired Server Count is set to Not Used, you will not be able to modify the Desired server count. To modify the Desired server count, refer to Modifying Manual Setting of Desired Server Count.

Modifying Desired Server Count Manual Setting

You can change the Desired server count manual setting of the Auto-Scaling Group.

Note
If you do not select Use for the Desired server count manual setting, you cannot modify the Desired server count in the detailed information server count modification.

To modify the Desired server count manual setting of the Auto-Scaling Group, follow these steps:

  1. Click the All Services > Compute > Virtual Server menu. The Virtual Server Service Home page opens.
  2. Click the Auto-Scaling Group menu. The Auto-Scaling Group List page opens.
  3. On the Auto-Scaling Group List page, click the resource for which you want to change the Desired server count manual setting. The Auto-Scaling Group Details page opens.
  4. Click the Edit button for the server count. The Desired Server Count Manual Setting popup window opens.
  5. In the Desired Server Count Manual Setting popup window, select whether to use it and click the Confirm button.

Setting Security Group

You can set the Security Group for the Auto-Scaling Group.

Note
If you modify the Security Group, it will not be applied to the existing servers in the Auto-Scaling Group, but only to new servers created afterwards. If you want to apply the modified Security Group to all servers in the Auto-Scaling Group, adjust the server count (Desired) to 0 to delete all existing servers, and then modify the server count (Desired) to the desired number.

To set the Security Group for the Auto-Scaling Group, follow these steps:

  1. Click the All Services > Compute > Virtual Server menu. The Virtual Server Service Home page opens.

  2. Click the Auto-Scaling Group menu. The Auto-Scaling Group List page opens.

  3. On the Auto-Scaling Group List page, click the resource for which you want to set the Security Group. The Auto-Scaling Group Details page opens.

  4. Click the Edit button for the Security Group. The Security Group Modification popup window opens, where you can view the list of available Security Groups.

    ClassificationDetailed Description
    Security Group NameSecurity Group name
    Table. Security Group List Items

  5. In the Security Group Modification popup window, select the Security Group and click the Confirm button. The Security Group Modification Notification popup window opens. Check the message in the notification popup window and click the Confirm button.

Managing Additional Auto-Scaling Group Information

You can set the Load Balancer to use and select the LB server group for the Auto-Scaling Group. For an Auto-Scaling Group that is using a Load Balancer, you can change it to not use it.

Modifying Load Balancer Draining Timeout

You can set the Load Balancer Draining Timeout for the Auto-Scaling Group.

Note

Draining Timeout is the time to wait before disconnecting the server from the Load Balancer.

  • You can set the Draining Timeout to safely clean up sessions, as there may be remaining sessions connected to the server.
  • If the Load Balancer is Not Used, the Draining Timeout cannot be set.
  • The default value is 300 seconds, and you can set it to a minimum of 1 second and a maximum of 3,600 seconds.

To set the Load Balancer Draining Timeout for the Auto-Scaling Group, follow these steps:

  1. Click the All Services > Compute > Virtual Server menu. The Virtual Server Service Home page opens.
  2. Click the Auto-Scaling Group menu. The Auto-Scaling Group List page opens.
  3. On the Auto-Scaling Group List page, click the resource for which you want to set the Load Balancer Draining Timeout. The Auto-Scaling Group Details page opens.
  4. Click the Load Balancer tab. The Load Balancer list page opens.
  5. Click the Edit button for the Draining Timeout. The Draining Timeout Modification popup window opens.
  6. In the Draining Timeout Modification popup window, select whether to use the Draining Timeout and enter the Draining Timeout time (in seconds).
  7. In the Draining Timeout Modification popup window, check the input values and click the Confirm button. The Draining Timeout Modification Notification popup window opens. Check the message in the notification popup window and click the Confirm button.

Using Load Balancer

You can modify the Load Balancer for the Auto-Scaling Group. To set the Load Balancer for the Auto-Scaling Group, follow these steps:

Note
  • When the Auto-Scaling Group’s server is created, it is automatically connected to the selected Load Balancer’s LB server group as a member, and when the server is terminated, it is disconnected from the LB server group.
  • If the Draining Timeout is Used, the server is disconnected from the LB server group after waiting for the Draining Timeout (in seconds).
  • For Load Balancer modification, the member is detached from the LB server group and waits in the Detach from LB state. For Scale In, the member is disconnected from the LB server group and waits in the Scale In state.
  1. Click the All Services > Compute > Virtual Server menu. The Virtual Server Service Home page opens.
  2. Click the Auto-Scaling Group menu. The Auto-Scaling Group List page opens.
  3. On the Auto-Scaling Group List page, click the resource for which you want to set the Load Balancer. The Auto-Scaling Group Details page opens.
  4. Click the Load Balancer tab. The Load Balancer list page opens.
  5. Click the Edit button for the Load Balancer. The Load Balancer Modification popup window opens.
  6. In the Load Balancer Modification popup window, select whether to use it. If you select Use, you can select the Load Balancer.
    ClassificationDetailed Description
    LB Server GroupLB server group name
    • Select the LB server group created in the selected VPC
    • LB server groups using Weighted Round Robin or Weighted Least Connection load balancing cannot be selected
    PortLB server group port information
    • Enter the port information required for registering the LB server group member
    • Enter a value between 1 and 65,534
    Table. Load Balancer List Items
    • You can add an LB server group by clicking the + button. Up to 3 can be added. You can remove the added Load Balancer by clicking the X button.
  7. Check the Load Balancer list and click the Confirm button. The Load Balancer Modification Notification popup window opens. Check the message in the notification popup window and click the Confirm button.
    Caution
    • Be cautious when detaching/attaching servers from Load Balancer, as it may affect the service.
    • If Draining Timeout is in use, setting Load Balancer to not in use or removing some connected Load Balancers using the X button will not immediately detach the server. The server will be detached from Load Balancer after waiting for the Draining Timeout (seconds). At this time, Auto-Scaling Group will be in Detach from LB state.
Note

Not using Load Balancer

You can modify the Load Balancer of Auto-Scaling Group to not in use. To set Load Balancer to not in use in Auto-Scaling Group, follow the procedure below.

Caution
  • Be cautious when detaching/attaching servers from Load Balancer, as it may affect the service.
  • If Draining Timeout is in use, setting Load Balancer to not in use or removing some connected Load Balancers using the X button will not immediately detach the server. The server will be detached from Load Balancer after waiting for the Draining Timeout (seconds). At this time, Auto-Scaling Group will be in Detach from LB state.
  1. Click All Services > Compute > Virtual Server menu. Move to the Service Home page of Virtual Server.
  2. Click Auto-Scaling Group menu. Move to the Auto-Scaling Group list page.
  3. Click the resource to set Load Balancer in the Auto-Scaling Group list page. Move to the Auto-Scaling Group details page.
  4. Click the Load Balancer tab. Move to the Load Balancer list page.
  5. Click the Modify button of Load Balancer. The Load Balancer modification popup window opens.
  6. Select whether to use Load Balancer in the Load Balancer modification popup window. If you deselect Use, Load Balancer will not be used.
  7. Confirm the deselection of Use and click the OK button. The Load Balancer modification notification popup window opens. Check the message in the notification popup window and click the OK button.

Deleting Auto-Scaling Group

Deleting unused Auto-Scaling Groups can reduce operating costs. However, deleting an Auto-Scaling Group may immediately stop the service in operation, so you must consider the impact of service termination before proceeding with the deletion.

Caution
Be cautious, as data cannot be recovered after deletion.

To delete an Auto-Scaling Group, follow the procedure below.

  1. Click All Services > Compute > Virtual Server menu. Move to the Service Home page of Virtual Server.
  2. Click Auto-Scaling Group menu. Move to the Auto-Scaling Group list page.
  3. Click the resource to delete in the Auto-Scaling Group list page. Move to the Auto-Scaling Group details page.
  4. Click the Delete Auto-Scaling Group button.
  5. After deletion is complete, check if the resource has been deleted in the Auto-Scaling Group list page.

2.2.2.1 - Launch Configuration

To create an Auto-Scaling Group, you need to create a Launch Configuration in advance.

Creating a Launch Configuration

You can create a Launch Configuration service on the Samsung Cloud Platform Console and use it.

To create a Launch Configuration, follow these steps:

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

  2. Click the Launch Configuration menu. It moves to the Launch Configuration list page.

  3. Click the Create Launch Configuration button on the Launch Configuration list page. It moves to the Create Launch Configuration page.

  4. Select the required information in the Image and Version Selection section of the Create Launch Configuration page and click the Next button.

    Note
    The images that can be selected in the Launch Configuration are as follows: Virtual Server OS Image Provided Version.

  5. Enter the required information in the Service Information Input section of the Create Launch Configuration page.

    Category
    Required
    Description
    Launch Configuration NameRequiredThe name of the Launch Configuration
    • A name to distinguish the Launch Configuration
    Service Type > Server TypeRequiredThe server type of the Launch Configuration
    • Standard: Standard specifications commonly used
    • High Capacity: Server specifications with higher capacity than Standard
    Block StorageRequiredBlock Storage settings according to the purpose of the Launch Configuration
    • Basic OS: The area where the OS is installed and used
      • The capacity is entered in Units, and the minimum capacity varies depending on the OS image type
        • Alma Linux: Enter a value between 2 and 1,536
        • Oracle Linux: Enter a value between 5 and 1,536
        • RHEL: Enter a value between 2 and 1,536
        • Rocky Linux: Enter a value between 2 and 1,536
        • Ubuntu: Enter a value between 1 and 1,536
        • Windows: Enter a value between 4 and 1,536
      • SSD: High-performance general volume
      • HDD: General volume
      • SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption key
        • Encryption can only be applied when created, and cannot be changed after creation
        • Using the SSD_KMS disk type may cause performance degradation
    • Add: Additional user space outside the OS area
      • Select Use and enter the storage type and capacity
      • Click the + button to add storage, and click the x button to delete (up to 25 can be added)
      • Capacity is entered in Units, and enter a value between 1 and 1,536
        • 1 Unit is 8GB, so 8 to 12,288GB is created
      • SSD: High-performance general volume
      • HDD: General volume
      • SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption key
        • Encryption can only be applied when created, and cannot be changed after creation
        • Using the SSD_KMS disk type may cause performance degradation
      • SSD_MultiAttach: Volume that can be connected to two or more servers
    KeypairRequiredSelect the authentication method for the Launch Configuration
    • Server authentication information to access the server created by creating an Auto-Scaling Group with the Launch Configuration
    • Create New: Create a new Keypair if needed
    • Default access account list by OS
      • Alma Linux: almalinux
      • RHEL: cloud-user
      • Rocky Linux: rocky
      • Ubuntu: ubuntu
      • Windows: sysadmin
    Table. Launch Configuration Service Information Input Items

  6. Enter the information in the Additional Information Input section of the Create Launch Configuration page and click the Next button.

    Category
    Required
    Description
    Init ScriptOptionalScript that runs when the server starts using the Launch Configuration
    • Enter within 45,000 bytes
    • The Init Script must be a batch script for Windows or a shell script or cloud-init for Linux, depending on the selected image.
    TagOptionalAdd a tag
    • Up to 50 tags can be added per resource
    • Click the Add Tag button, enter the Key and Value, or select them
    Table. Launch Configuration Additional Information Input Items

  7. Check the input information and estimated cost on the Create Information Confirmation page, and click the Complete button.

    • After creation is complete, check the created Launch Configuration on the Launch Configuration list page.

Checking Launch Configuration Details

The Launch Configuration service allows you to check the overall resource list and detailed information, and modify it. The Launch Configuration details page consists of Details, Tags, and Work History tabs.

To check the Launch Configuration details, follow these steps:

  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Click the Launch Configuration menu. It moves to the Launch Configuration list page.
  3. Click the resource to check the details on the Launch Configuration list page. It moves to the Launch Configuration details page.
    • The top of the Launch Configuration details page displays status information and additional feature information, and consists of Details, Tags, and Work History tabs.
CategoryDescription
Launch Configuration StatusThe status of the Launch Configuration created by the user
  • Active: Available status
Launch Configuration DeletionButton to delete the Launch Configuration
Table. Launch Configuration Status Information and Additional Features

Details

You can check and modify the detailed information of the selected resource on the Launch Configuration list page.

CategoryDescription
ServiceService category
Resource TypeService name
SRNUnique resource ID in Samsung Cloud Platform
  • In the case of Launch Configuration, it refers to the Launch Configuration SRN
Resource NameResource name
  • In the case of Launch Configuration, it refers to the Launch Configuration name
Resource IDUnique resource ID in the service
CreatorThe user who created the service
Creation TimeThe time when the service was created
ModifierThe user who modified the service information
Modification TimeThe time when the service information was modified
Launch Configuration NameLaunch Configuration name
ImageThe image name selected when creating the Launch Configuration
  • The OS image used when creating a server using the Launch Configuration for the Auto-Scaling Group
Number of Auto-Scaling GroupsThe number of Auto-Scaling Groups using the Launch Configuration
Server TypeThe server type set in the Launch Configuration
Block StorageBlock Storage information set in the Launch Configuration
  • Type, capacity, and type
KeypairServer authentication information set in the Launch Configuration
  • Keypair information used to connect to the server created using the Launch Configuration for the Auto-Scaling Group
Init ScriptInit Script set in the Launch Configuration
  • Script that runs when the server starts using the Launch Configuration for the Auto-Scaling Group
Table. Launch Configuration Details Tab Items

Tags

You can check the tag information of the selected resource on the Launch Configuration list page, and add, change, or delete it.

CategoryDescription
Tag ListTag list
  • Check the Key and Value information of the tag
  • Up to 50 tags can be added per resource
  • Search and select from the existing Key and Value list when entering tags
Table. Launch Configuration Tags Tab Items

Work History

You can check the work history of the selected resource on the Launch Configuration list page.

CategoryDescription
Work History ListResource change history
  • Check the work time, resource ID, resource name, work details, event topic, work result, and worker information
Table. Launch Configuration Work History Tab Detailed Information Items

Deleting a Launch Configuration

You can reduce operating costs by deleting unused Launch Configurations. However, deleting a Launch Configuration may immediately stop the operating service, so you should consider the impact of stopping the service before proceeding with the deletion.

Caution
Data cannot be recovered after deletion, so proceed with caution.

To delete a Launch Configuration, follow these steps:

  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Click the Launch Configuration menu. It moves to the Launch Configuration list page.
  3. Click the resource to delete on the Launch Configuration list page. It moves to the Launch Configuration details page.
  4. Click the Delete Launch Configuration button.
  5. After deletion is complete, check that the resource has been deleted on the Launch Configuration list page.
Caution
A Launch Configuration applied to an Auto-Scaling Group cannot be deleted. Delete the Auto-Scaling Group first, and then delete the Launch Configuration.

2.2.2.2 - Managing Policies

The number of servers in an Auto-Scaling Group can be dynamically adjusted based on monitoring metrics. When the set threshold is exceeded based on the monitoring metrics, the number of servers is adjusted. At this time, you can choose one of three ways to adjust the number of servers: increase or decrease the number of servers by a specified number, increase or decrease the number of servers by a specified ratio, or fix the number of servers to a specified value. When a server is started or terminated due to a policy, the monitoring metric, such as CPU usage, may temporarily exceed the threshold set in the policy. However, since this is a temporary moment, a cooldown time is set so that it is not judged as an abnormal situation. You can add and manage policies for an Auto-Scaling Group created in the Samsung Cloud Platform Console.

Adding a Policy

You can add a policy to an Auto-Scaling Group. To add a policy to an Auto-Scaling Group, follow these steps:

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

  2. Click the Auto-Scaling Group menu. Move to the Auto-Scaling Group List page.

  3. On the Auto-Scaling Group List page, click the resource to view detailed information. Move to the Auto-Scaling Group Details page.

  4. Click the Policy Tab. Move to the Policy Tab page.

  5. Click the Add Policy button. The Add Policy popup window opens.

    Classification
    Required
    Detailed Description
    ClassificationRequiredPolicy classification
    • Scale In: Server reduction
    • Scale Out: Server increase
    Policy NameRequiredPolicy name for distinction
    Execution ConditionRequiredCondition for executing the policy
    • Statistic: Method of calculating the metric type
      • Average: Average of servers in the Auto-Scaling Group
      • Min: Minimum value among servers in the Auto-Scaling Group
      • Max: Maximum value among servers in the Auto-Scaling Group
    • Metric Type: CPU Usage, Memory Usage, Network In(bytes), Network Out(bytes), Network In(Packets), Network Out(Packets)
      • Note: Memory usage policy is not available for Windows servers
    • Operator: >= > <= <
    • Threshold: Threshold for the metric type
    • Period: Continuous time to trigger the execution condition (N minutes)
    Execution UnitRequiredMethod of executing the policy
    • Policy Type: Select the type of policy to execute.
      • Increase or decrease the number of servers by a specified number: Increase or decrease the target value
      • Increase or decrease the number of servers by a specified ratio: Increase or decrease the target value ratio
      • Fix the number of servers to a specified value: Fix the target value
    • Target Value: Number or ratio to execute the selected Policy Type
    CooldownRequiredTime to wait (in seconds) when a server is started or terminated due to a policy
    • Default value is 300 seconds, and it can be set between 60 seconds and 3,600 seconds.
    Table. Add Policy Popup Items
    Note

    Policy > Cooldown Setting

    • When a server is started or terminated due to a policy, wait for the cooldown time set. The monitoring metric, such as CPU usage, may temporarily exceed the threshold set in the policy. However, since this is a temporary moment and not a condition for adjusting the number of servers, the cooldown time is set to wait.
    Guide

    Policy execution operates within the set minimum and maximum number of servers.

    • Even if the number of servers is increased or decreased, or fixed, beyond the minimum and maximum number of servers, it operates within the set minimum and maximum number of servers.
    • Example: If the minimum number of servers is 3, even if the number of servers is fixed to 1, the number of servers will not decrease to 1, but will be maintained at the minimum number of servers, which is 3.

  6. In the Add Policy popup window, enter the required values and click the Confirm button. The added policy can be checked in the Policy List.

Policy Creation Example

The following is an explanation of the policy example. Refer to it when creating a policy.

Policy Example Explanation 1
ClassificationExecution ConditionExecution UnitCooldown
Scale OutAverage CPU Usage >= 60% for 1 minuteIncrease the number of servers by a specified number, 1 server300 seconds
Table. Auto-Scaling Group Policy Example 1
  • If the average CPU usage of the servers in the Auto-Scaling Group is 60% or higher for 1 minute, 1 server is added.
  • When a server is added, the cooldown time is 300 seconds. During the cooldown time, no additional servers are added or terminated due to the policy.
  • After the cooldown time ends, the policy execution condition is checked again.
Policy Example Explanation 2
ClassificationExecution ConditionExecution UnitCooldown
Scale InMin CPU Usage <= 5% for 1 minuteDecrease the number of servers by a specified ratio, 50%300 seconds
Table. Auto-Scaling Group Policy Example 2
  • If the minimum CPU usage of the servers in the Auto-Scaling Group is 5% or lower for 1 minute, 50% of the current number of servers are terminated.
  • When a server is terminated, the cooldown time is 300 seconds. During the cooldown time, no additional servers are added or terminated due to the policy.
  • After the cooldown time ends, the policy execution condition is checked again.
Policy Example Explanation 3
ClassificationExecution ConditionExecution UnitCooldown
Scale OutMax CPU Usage >= 90% for 1 minuteFix the number of servers to a specified value, 5 servers300 seconds
Table. Auto-Scaling Group Policy Example 3
  • If the maximum CPU usage of the servers in the Auto-Scaling Group is 90% or higher for 1 minute, the number of servers is fixed to 5.
  • During the server creation, the cooldown time is 300 seconds. During the cooldown time, no additional servers are added or terminated due to the policy.
  • After the cooldown time ends, the policy execution condition is checked again.

Modifying a Policy

You can modify a policy of an Auto-Scaling Group. To modify a policy of an Auto-Scaling Group, follow these steps:

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

  2. Auto-Scaling Group menu should be clicked. It moves to the Auto-Scaling Group list page.

  3. In the Auto-Scaling Group list page, click on the resource to check the detailed information. It moves to the Auto-Scaling Group details page.

  4. Click on the Policy tab. It moves to the Policy tab page.

  5. Click on the More > Edit button of the policy to be modified. The Policy modification popup opens.

    Classification
    Required
    Detailed Description
    ClassificationRequiredPolicy classification
    • Scale In: Server count return
    • Scale Out: Server count increase
    Policy NameRequiredPolicy name for distinction
    Execution ConditionRequiredCondition for executing the policy
    • Statistic: Method of calculating Metric Type
      • Average: Average of servers in Auto-Scaling Group
      • Min: Minimum value among servers in Auto-Scaling Group
      • Max: Maximum value among servers in Auto-Scaling Group
    • Metric Type: CPU Usage, Memory Usage, Network In(bytes), Network Out(bytes), Network In(Packets), Network Out(Packets)
      • Note: Memory usage policy cannot be set for Windows servers
    • Operator: >= > <= <
    • Threshold: Threshold corresponding to Metric Type
    • Period: Continuous time (N minutes) to trigger the execution condition
    Execution UnitRequiredMethod of executing the policy
    • Policy Type: Select the type of policy to be executed.
      • Increase or decrease the server count by a specified number: Increase or decrease the server count by the target value
      • Increase or decrease the server count by a specified ratio: Increase or decrease the server count by the target value ratio
      • Fix the server count to the input value: Fix the server count to the target value
    • Target Value: The number or ratio of the selected Policy Type to be executed
    CooldownRequiredWaiting time (in seconds) when a server is started or terminated due to a policy
    • Default value is 300 seconds, and it can be set from 1 second to a maximum of 3,600 seconds
    Table. Policy modification popup items

  6. Click the Confirm button after entering the required values in the Policy modification popup window.

Policy Addition and Modification Restrictions

There are restrictions when adding or modifying policies, depending on the policy classification, execution condition, and execution condition range. Refer to the examples of restrictions below and add or modify policies accordingly.

Example 1 - Check for duplicate registration of policy classification and execution condition

Duplicate registration is not allowed when the policy classification (Scale Out or Scale In) and execution condition (Metric type) are the same.

Policy ClassificationPolicy NameExecution Condition (Statistic)Execution Condition (Metric Type)Execution Condition Range
Scale OutScaleOutPolicyAverageCPU Usage>= 60%
Table. Policy restriction example 1 - Pre-registered policy

If a policy is already registered as shown above, it is not possible to add or modify a policy with the same classification (Scale Out) and execution condition (Metric type = CPU Usage).

Example 2 - Check the execution condition range for the same execution condition (Metric type) and execution condition (Statistic)

When the policy distinction (Scale Out or Scale In) is different, the execution condition range (Comparison operator + Threshold) cannot be duplicated for the same execution condition (Metric type) and execution condition (Statistic).

Policy DistinctionPolicy NameExecution Condition (Statistic)Execution Condition (Metric type)Execution Condition Range
Scale OutScaleOutPolicyAverageCPU Usage>= 60%
Table. Policy Constraint Example 2 - Pre-registered Policy

In the case where a policy is registered as above, it is not possible to add a policy or modify it as follows: If the CPU Usage is 60% or higher on average, since the Scale Out policy is already registered, it is not possible to register a Scale In policy for CPU Usage average of 60% or lower, as the 60% case would be a duplicate of the same execution condition.

Policy DistinctionPolicy NameExecution Condition (Statistic)Execution Condition (Metric type)Execution Condition Range
Scale InAddUpdatePolicyAverageCPU Usage<= 60%
Table. Policy Constraint Example 2 - Policy that cannot be added

If a policy is already registered as shown above, it is not possible to add or modify a policy with the same execution condition (Metric type = CPU Usage) and execution condition (Statistic = Average), and an execution condition range that overlaps with the existing policy.

Example 3 - Check the execution condition range for the same execution condition (Metric type) and execution condition (Statistic)

When the policy distinction (Scale Out or Scale In) is different, the execution condition range (Comparison operator + Threshold) cannot be duplicated for the same execution condition (Metric type) and execution condition (Statistic).

Policy DistinctionPolicy NameExecution Condition (Statistic)Execution Condition (Metric type)Execution Condition Range
Scale InScaleInPolicyAverageCPU Usage<= 10%
Table. Policy Constraint Example 3 - Pre-registered Policy

In the case where a policy is registered as above, it is not possible to add or modify a policy as follows: Since the Scale In policy is already registered when the CPU usage is 10% or less on average, it is not possible to register a Scale Out policy when the CPU usage is less than 60%, less than or equal to 60%, greater than 10%, or greater than 9%.

Policy DistinctionPolicy NameExecution Condition (Statistic)Execution Condition (Metric type)Execution Condition Range
Scale OutAddUpdatePolicy1AverageCPU Usage< 60%
Scale OutAddUpdatePolicy2AverageCPU Usage<= 60%
Scale OutAddUpdatePolicy3AverageCPU Usage>= 10%
Scale OutAddUpdatePolicy4AverageCPU Usage> 9%
Table. Policy Constraint Example 3 - Policies that cannot be added

Example 4 - Registration is possible when the execution condition range does not overlap

When the policy distinction (Scale Out or Scale In) is different, it is possible to register even if the execution condition (Statistic) is different or the execution condition range (Comparison operator + Threshold) does not overlap for the same execution condition (Metric type).

Policy DistinctionPolicy NameExecution Condition (Statistic)Execution Condition (Metric type)Execution Condition Range
Scale OutScaleOutPolicyAverageCPU Usage>= 60%
Table. Policy constraint example 4 - Pre-registered policy

In the case where a policy is registered as above, it is possible to add or modify a policy as follows. If the execution condition range does not overlap or the execution condition (Statistic) is different, registration is possible.

Policy DistinctionPolicy NameExecution Condition (Statistic)Execution Condition (Metric type)Execution Condition Range
Scale InAddUpdatePolicy1AverageCPU Usage<= 10%
Scale InAddUpdatePolicy2MinCPU Usage<= 60%
Table. Policy constraint example 4 - Policies that can be added

Deleting a Policy

It is possible to delete a policy from an Auto-Scaling Group. To delete a policy, follow the procedure below.

  1. All Services > Compute > Virtual Server menu, click. Move to the Service Home page of Virtual Server.
  2. Auto-Scaling Group menu, click. Move to the Auto-Scaling Group List page.
  3. On the Auto-Scaling Group List page, click the resource to check the detailed information. Move to the Auto-Scaling Group Details page.
  4. Click the Policy Tab. Move to the Policy Tab page.
  5. Select the policy to delete and click the Delete button. The Policy Delete Confirmation popup window opens.
  6. Confirm the Policy Delete Confirmation popup window and click the Confirm button.

2.2.2.3 - Managing Schedules

You can schedule daily, weekly, monthly, or one-time, and set the desired number of servers at a fixed time. This is useful when it is possible to predict when to reduce or increase the number of servers.

Add schedule

You can add a schedule to the Auto-Scaling Group. To add a schedule to the Auto-Scaling Group, follow these steps.

  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Auto-Scaling Group menu is clicked. It moves to the Auto-Scaling Group list page.
  3. Auto-Scaling Group list page, click the resource to check the detailed information. It moves to the Auto-Scaling Group details page.
  4. Click the Schedule Tab. It moves to the Schedule Tab page.
  5. Click the Add Schedule button. The Add Schedule popup window opens.
    Classification
    Required
    Detailed Description
    Schedule NameRequiredSchedule-specific distinguishing name
    Server count selectionRequiredWhen performing a schedule, select the number of servers to adjust
    • Min: The minimum number of servers that the Auto-Scailg Group will maintain
    • Desired: The target number of servers within the Auto-Scailg Group
    • Max: The maximum number of servers that the Auto-Scailg Group can maintain
    Enter the number of serversRequiredEnter the value of the selected server number
    • Min value: Please enter a value between 0 and 50. (Min≤Desired≤Max)
    • Desired value: Please enter a value between 0 and 50. (Min≤Desired≤Max)
    • Max value: Please enter a value between 0 and 50. (Min≤Desired≤Max)
    PeriodRequiredSchedule execution period
    • Daily: You can set the start date and end date, and permanent settings for daily schedule execution. You can also set time and time zone
    • Weekly: You can set start date and end date, permanent settings, and time and time zone settings. You can also select the day of the week for weekly schedule execution
    • Monthly: You can set start date and end date, permanent settings, and time and time zone settings. You can also enter the date for monthly schedule execution
    • Once: You can set time and time zone settings. You can also set the date for one-time schedule execution
    Start DateSelectSet schedule start date
    • Cannot be set to a date prior to the current date. The default is the current date.
    End DateSelectSet schedule end date
    • Cannot be set to a date prior to the current date. The default is the current date + 7.
    PermanentSelectIf permanent is set, the schedule end date is set to 9999-12-31
    TimeRequiredSchedule execution time setting
    • Can be set in 30-minute units. Time faster than the current date and time cannot be set
    Time ZoneRequiredTime zone corresponding to the schedule execution time (e.g., Asia/Seoul (GMT +09:00))
    Day of the weekRequiredIf you select cycle as every week, select the day of the week to perform the schedule
    DateEssential
    • Cycle is selected as every month, enter the Date to perform the schedule
      • Please enter one or more between -31 and 31, excluding 0. (Example: 3,4,5)
    • Cycle is selected as once, set the Date to perform the schedule
      • It cannot be set before the current date. The default value is the current date.
    Table. Schedule Add Popup Item
  6. In the Add Schedule popup window, enter the required values and click the OK button.
  7. Check the message in the Add Schedule Confirmation popup window, then click the Confirm button.
Reference

If you select monthly for the schedule cycle, you must enter the schedule execution date, which is Date. Please refer to the following contents to register the schedule.

  • If you enter a number greater than 0, it means the date of the month.
    • Example: If you enter 1, it will be August 1, September 1, …, December 1
  • If you enter a number less than 0, it will be calculated from the last day of the month.
    • Entering -1 means the last day of the month.
  • Example: August 31, September 30, …, December 31
    • If -2 is entered, it means the day before the last day of the month.
  • Example: August 30, September 29, …, December 30
    • Since the last day of each month is different, such as 31st, 30th, 29th, 28th, to handle cases where a schedule should be executed on the last day of each month, negative numbers are used to calculate from the last day, as shown above.
Notice
  • When the schedule is executed, if the minimum number of servers set in the schedule is greater than the desired number of servers, or the maximum number of servers is less than the desired number of servers, the desired number of servers is also modified.
  • If there are schedules with overlapping execution times, they may not run normally. Please try to avoid overlapping execution times if possible.

Modify Schedule

You can modify the schedule of the Auto-Scaling Group. To modify the schedule of the Auto-Scaling Group, follow these steps.

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

  2. Auto-Scaling Group menu is clicked. It moves to the Auto-Scaling Group list page.

  3. Auto-Scaling Group list page, click the resource to check the detailed information. Move to the Auto-Scaling Group details page.

  4. Click the Schedule Tab. It moves to the Schedule Tab page.

  5. Click the More > Edit button of the schedule you want to modify. The Edit Schedule popup window will open.

    Classification
    Required
    Detailed Description
    Schedule NameRequiredSchedule name to distinguish by schedule
    Number of servers to selectRequiredWhen performing a schedule, select the number of servers to adjust
    • Min: The minimum number of servers that the Auto-Scailg Group will maintain
    • Desired: The target number of servers within the Auto-Scailg Group
    • Max: The maximum number of servers that the Auto-Scailg Group can maintain
    Enter the number of serversRequiredEnter the value of the selected server number
    • Min value: Please enter a value between 0 and 50. (Min≤Desired≤Max)
    • Desired value: Please enter a value between 0 and 50. (Min≤Desired≤Max)
    • Max value: Please enter a value between 0 and 50. (Min≤Desired≤Max)
    PeriodRequiredSchedule execution period
    • Daily: You can set the start date and end date, and permanent settings for daily schedule execution. You can also set time and time zone
    • Weekly: You can set start date and end date, permanent settings, and time and time zone. You can also select the day of the week for weekly schedule execution
    • Monthly: You can set start date and end date, permanent settings, and time and time zone. You can also enter the date for monthly schedule execution
    • Once: You can set time and time zone. You can also set the date for one-time schedule execution
    Start DateSelectSet schedule start date
    • Cannot be set to a date prior to the current date. The default is the current date.
    End DateSelectSet schedule end date
    • Cannot be set to a date prior to the current date. The default is the current date + 7.
    PermanentSelectIf permanent is set, the schedule end date is set to 9999-12-31
    TimeRequiredSchedule execution time setting
    • Can be set in 30-minute units. Time faster than the current date and time cannot be set
    Time ZoneRequiredTime zone corresponding to the schedule execution time (e.g. Asia/Seoul (GMT +09:00))
    DayRequiredIf you select Weekly as the Cycle, select the day of the week to perform the schedule
    DateEssential
    • When Cycle is set to Every Month, enter the Date to perform the schedule
      • Please enter one or more values from -31 to 31, excluding 0. (Example: 3,4,5)
    • When Cycle is set to Once, set the Date to perform the schedule
      • Cannot be set to a date before the current date. The default value is the current date.
    Fig. Schedule modification popup item
  6. In the Modify Schedule popup window, enter the required values and click the Confirm button.

  7. Schedule Modification Confirmation Check the message in the popup window and click the Confirm button.

Delete Schedule

You can delete the schedule of the Auto-Scaling Group. To delete the schedule of the Auto-Scaling Group, follow the next procedure.

  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Auto-Scaling Group menu is clicked. It moves to the Auto-Scaling Group list page.
  3. Auto-Scaling Group list page, click the resource to check the detailed information. Move to the Auto-Scaling Group details page.
  4. Click the Schedule Tab. It moves to the Schedule Tab page.
  5. Select the schedule to be deleted and click the Delete button. The Schedule Deletion Confirmation popup window will open.
  6. Schedule deletion confirmation popup window, confirm and click the Confirm button.

2.2.2.4 - Managing Notifications

You can specify the notification recipient to send a notification message via E-mail or SMS for a specific situation.

Reference
  • Notification method (E-mail or SMS) can be set by selecting Notification target as Service > Virtual Server Auto-Scaling on the Notification settings page.
  • For more information about modifying alert settings, see Modifying Alert Settings.

Add Alert

You can add notifications to the Auto-Scaling Group. To add notifications to the Auto-Scaling Group, follow these steps.

  1. All services > Compute > Virtual Server menu, click. It moves to the Service Home page of Virtual Server.
  2. Auto-Scaling Group menu is clicked. It moves to the Auto-Scaling Group list page.
  3. Click the resource to add notification information on the Auto-Scaling Group list page. It moves to the Auto-Scaling Group details page.
  4. Click the Notification Tab. You will be taken to the Notification Tab page.
  5. Click the Add Notification button. The Add Notification popup window opens.
  6. In the Add Notification popup window, enter the required values and click the Confirm button.
    DivisionDetailed Description
    Notification PointNotification point when Auto-Scaling Group alert occurs
    • Server creation, Server termination, Server creation failure, Server termination failure, When policy execution conditions are met
    • Multiple selections are possible
    Notification RecipientUser to receive notification when notification occurs
    • Add Notification Recipient button to select user
    • Only Samsung Cloud Platform users can be selected as recipients
    Table. Notification Items
Caution
When adding a notification recipient, check if there is an email address and add it. Only users with a login history (users who have registered their email or mobile phone number) can receive notifications.
  1. Check the message in the Add Alert Confirmation popup window, then click the Confirm button.

Modify Alert

You can modify the notification information of the Auto-Scaling Group. To modify the notification information of the Auto-Scaling Group, follow the procedure below.

  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Auto-Scaling Group menu will be clicked. It moves to the Auto-Scaling Group list page.
  3. Click the resource to modify the notification information on the Auto-Scaling Group list page. It moves to the Auto-Scaling Group details page.
  4. Click the Notification Tab. It moves to the Notification Tab page.
  5. Click the More > Edit button for the notification information you want to modify in the notification list. The Edit Notification popup window opens.
  6. Modify Notification In the notification modification popup window, modify the notification information and click the Confirm button.
    ClassificationDetailed Description
    Notification PointNotification point when Auto-Scaling Group alert occurs
    • Server creation, Server termination, Server creation failure, Server termination failure, When policy execution conditions are met
    • Multiple selections are possible
    Table. Notification Modification Items
  7. Check the message in the Notification Modification Confirmation popup window, then click the Confirm button.

Delete Notification

You can delete the notification of Auto-Scaling Group. To delete the notification of Auto-Scaling Group, follow the procedure below.

  1. All Services > Compute > Virtual Server menu should be clicked. It moves to the Service Home page of Virtual Server.
  2. Auto-Scaling Group menu is clicked. It moves to the Auto-Scaling Group list page.
  3. Auto-Scaling Group list page, click the resource to modify the notification information. Move to the Auto-Scaling Group details page.
  4. Click the Notification Tab. It moves to the Notification Tab page.
  5. Select the notification to be deleted from the notification list, then click the Delete button. The Delete Notification Confirmation popup window will open.
  6. Notification deletion confirmation popup window, confirm and click the Confirm button.

2.2.3 - API Reference

API Reference

2.2.4 - CLI Reference

CLI Reference

2.2.5 - Release Note

Virtual Server Auto-Scaling

2025.07.01
FEATURE New feature added
  • Added notification feature to Virtual Server Auto-Scaling.
    • You can add notification settings in the Auto-Scaling Group creation or detail screen.
  • You can set the scaling policy when creating an Auto-Scaling Group.
  • Added Metric Type of Auto-Scaling Group policy.
    • Added: Memory Usage, Network In(bytes), Network Out(bytes), Network In(Packets), Network Out(Packets)
  • You can set the Draining Timeout when connecting to the Load Balancer.
  • In an Auto-Scaling Group, a Virtual Server can be connected to up to 50 instances, and an LB server group and port can be connected up to 3 instances.
2025.02.27
FEATURE Virtual Server Auto Scaling-Load Balancer service linkage release and NAT setting feature addition
  • Virtual Server Auto-Scaling feature change
    • It will be released in conjunction with the Load Balancer service to be released in February 2025.
    • NAT setting feature has been added to Auto-Scaling Group.
  • Samsung Cloud Platform common feature changes
    • Account, IAM and Service Home, tags, etc. reflected common CX changes.
2024.11.19
NEW Virtual Server Auto Scaling Service Official Version Release
  • Virtual Server Auto-Scaling creates and manages Auto-Scaling Group through Launch Configuration and checks and manages the server.
  • It provides a schedule method that can set the desired number of servers at a fixed time and a policy method that adjusts the number of servers based on CPU usage rate.

2.3 - GPU Server

2.3.1 - Overview

Service Overview

GPU Server is a virtualized computing service that allows you to freely allocate and use as much infrastructure resources provided by the server such as CPU, GPU, and memory as needed at the desired time without having to purchase them individually. It is suitable for tasks that require fast computing speed such as AI model experimentation, prediction, and inference in a cloud environment, and allows you to flexibly select and use resources with optimized performance according to task type and scale. GPU Server provides the following features:

Provided Features

  • GPU Server Management: Users can directly manage creation, deletion, and changes as a Self Service from GPU Server provisioning to monitoring and billing through a web-based Console.
  • Provisioning by GPU Quantity: You can configure a virtual server by freely selecting the quantity of H100/A100 GPUs according to project purpose and scale.
  • High Performance GPU Provision: Provides high-performance GPU servers at the physical server level using the Pass-through method.
  • Storage Connection: Provides additional connected storage besides OS disks. You can connect and use Block Storage, File Storage, and Object Storage.
  • Strong Security Application: Protects servers safely by controlling Inbound/Outbound traffic exchanged with external internet or other VPCs (Virtual Private Cloud) through the Security Group service.
  • Monitoring: You can check monitoring information such as CPU, Memory, Disk, and GPU status corresponding to computing resources through the Cloud Monitoring service.
  • Network Setting Management: The server’s subnet/IP can be easily changed from the values set at initial creation. Provides management functionality that allows you to set use/terminate NAT IP as needed.
  • Key Pair Method: Provides a Key Pair method instead of ID/PW access for secure OS access.
  • Image Management: You can create and manage Custom Images and provides sharing functionality between projects.
  • ServiceWatch Service Integration Provision: You can monitor data through the ServiceWatch service.

Components

GPU Server provides GPU, NVSwitch, and NVLink on top of virtualized computing resources.

Warning
  • NVSwitch can be activated and used only for instance types that allocate 8 GPUs to a single GPU Server.

Specifications by GPU Type

GPU (Graphic Processing Unit) plays the role of performing calculations necessary to create images that make up the computer screen and is specialized for parallel processing, enabling it to process large amounts of data quickly, handling large-scale parallel operations such as artificial intelligence (AI) and data analysis.

The following are the specifications of GPU types provided by the GPU Server service.

ItemA100 TypeH100 Type
Service Provision MethodPass-throughPass-through
GPU ArchitectureNVIDIA AmpereNVIDIA Hopper
GPU Memory80 GB80 GB
GPU Transistors54 billion 7N TSMC80 billion 4N TSMC
FP16 Tensor Core (Dense)312 TFLOPs989 TFLOPs
FP8 Tensor Core (Dense)Not supported1,979 TFLOPs
FP4 Tensor Core (Dense)Not supportedNot supported
GPU Memory Bandwidth2,039 GB/s HBM2e3,352 GB/s HBM3
NVLink PerformanceNVLink 3NVLink 4
NVLink Signaling Rate25 GB/s (x12)25 GB/s (x18)
NVSwitch GPU-to-GPU Bandwidth600 GB/s900 GB/s
Total NVSwitch Aggregate Bandwidth4.8 TB/s7.2 TB/s
Table. GPU Type Specifications

Server Type

The server types provided by GPU Server are as follows. For a detailed description of the server types provided by GPU Server, see GPU Server Server Types.

ItemServer TypeCPU vCoreMemory(GB)GPU Quantity
GPU-A100-1g1v16a1162341
GPU-A100-1g1v32a2324682
GPU-A100-1g1v64a4649364
GPU-A100-1g1v128a812818728
GPU-H100-2g2v12h1122341
GPU-H100-2g2v24h2244682
GPU-H100-2g2v48h4489364
GPU-H100-2g2v96h89618728
Table. GPU Server Server Types

OS and GPU Driver Version

The operating systems (OS) supported by GPU Server are as follows:

OSOS VersionGPU Driver Version
Ubuntu22.04535.183.06
Ubuntu24.04570.195.03
RHEL8.10535.183.06
Table. GPU Server OS and GPU Driver Version

Prerequisite Services

This is a service that must be pre-installed before creating this service. Please prepare by referring to the user guide provided in advance.

Service CategoryServiceDescription
NetworkingVPCService that provides independent virtual networks in cloud environment
NetworkingSecurity GroupVirtual firewall that controls server traffic
Table. GPU Server prerequisite services

2.3.1.1 - Server Type

GPU Server Server Type

GPU Server is classified according to the GPU Type provided, and the GPU used in the GPU Server is determined by the server type selected when creating the GPU Server. Please select the server type according to the specifications of the application you want to run on the GPU Server.

The server types supported by the GPU Server are as follows.

GPU-H100-2 g2v12h1
Category
ExampleDetailed description
Server TypeGPU-H100-2Provided server type classification
  • GPU-H100-2
    • GPU-H100 means the provided GPU type
    • 2 means the generation
  • GPU-A100-1
    • GPU-A100 means the provided GPU type
    • 1 means the generation
Server specificationsg2Provided server type classification and generation
  • g2
    • g means GPU server specifications
    • 2 means generation
Server specificationsv12Number of vCores
  • v2: 2 virtual cores
Server specificationsh1GPU type and quantity
  • h1
    • h means GPU-H100
    • 1 means 1 GPU
  • a2
    • a means GPU-A100
    • 2 means 2 GPUs
Table. GPU Server server type format

g1 server type

The g1 server type is a GPU Server that uses NVIDIA A100 Tensor Core GPU, suitable for high-performance applications.

  • Provides up to 8 NVIDIA A100 Tensor Core GPUs
  • Equipped with 6,912 CUDA cores and 432 Tensor cores per GPU
  • Supports up to 128 vCPUs and 1,920 GB of memory
  • Maximum 40 Gbps networking speed
  • 600GB/s GPU and NVIDIA NVSwitch P2P communication
CategoryServer TypeGPUCPUMemoryGPU MemoryNetwork Bandwidth
GPU-A100-1g1v16a1116 vCore234 GB80 GBup to 20 Gbps
GPU-A100-1g1v32a2232 vCore468 GB160 GBup to 20 Gbps
GPU-A100-1g1v64a4464 vCore936 GB320 GBup to 40 Gbps
GPU-A100-1g1v128a88128 vCore1872 GB640 GBMaximum 40 Gbps
Table. GPU Server server type > GPU-A100-1 server type

g2 server type

The g2 server type is a GPU Server that uses NVIDIA H100 Tensor Core GPU, suitable for high-performance applications.

  • Up to 8 NVIDIA H100 Tensor Core GPUs provided
  • Equipped with 16,896 CUDA cores and 528 Tensor cores per GPU
  • Supports up to 96 vCPUs and 1,920 GB of memory
  • Maximum networking speed of 40Gbps
  • 900GB/s GPU and NVIDIA NVSwitch P2P communication
CategoryServer TypeGPUCPUMemoryGPU MemoryNetwork Bandwidth
GPU-H100-2g2v12h1112 vCore234 GB80 GBup to 20 Gbps
GPU-H100-2g2v24h2224 vCore468 GB160 GBup to 20 Gbps
GPU-H100-2g2v48h4448 vCore936 GB320 GBMaximum 40 Gbps
GPU-H100-2g2v96h8896 vCore1872 GB640 GBup to 40 Gbps
Table. GPU Server server type > GPU-H100-2 server type

2.3.1.2 - Monitoring Metrics

GPU Server Monitoring Metrics

The following table shows the monitoring metrics of the GPU Server that can be checked through Cloud Monitoring.

Even without installing an Agent, basic monitoring metrics are provided. Please check the Table. GPU Server Monitoring Metrics (Basic) below. Additionally, metrics that can be retrieved by installing an Agent are referenced in the Table. GPU Server Additional Monitoring Metrics (Agent Installation Required) below.

For detailed Cloud Monitoring usage, please refer to the Cloud Monitoring guide.

Performance Item NameDescriptionUnit
Memory Total [Basic]Total available memory in bytesbytes
Memory Used [Basic]Currently used memory in bytesbytes
Memory Swap In [Basic]Swapped memory in bytesbytes
Memory Swap Out [Basic]Swapped memory in bytesbytes
Memory Free [Basic]Unused memory in bytesbytes
Disk Read Bytes [Basic]Read bytesbytes
Disk Read Requests [Basic]Number of read requestscnt
Disk Write Bytes [Basic]Written bytesbytes
Disk Write Requests [Basic]Number of write requestscnt
CPU Usage [Basic]Average system CPU usage over 1 minute%
Instance State [Basic]Instance statestate
Network In Bytes [Basic]Received bytesbytes
Network In Dropped [Basic]Dropped received packetscnt
Network In Packets [Basic]Received packetscnt
Network Out Bytes [Basic]Sent bytesbytes
Network Out Dropped [Basic]Dropped sent packetscnt
Network Out Packets [Basic]Sent packetscnt
Table. GPU Server Basic Monitoring Metrics (Basic)
Performance Item NameDescriptionUnit
GPU CountNumber of GPUscnt
GPU Memory UsageGPU memory usage rate%
GPU Memory UsedUsed GPU memoryMB
GPU TemperatureGPU temperature
GPU UsageGPU utilization%
GPU Usage [Avg]Average GPU usage rate%
GPU Power CapMaximum power capacity of the GPUW
GPU Power UsageCurrent power usage of the GPUW
GPU Memory Usage [Avg]Average GPU memory usage rate%
GPU Count in useNumber of GPUs in use by jobs on the nodecnt
Execution Status for nvidia-smiExecution result of the nvidia-smi commandstatus
Core Usage [IO Wait]CPU time spent in IO wait state%
Core Usage [System]CPU time spent in system space%
Core Usage [User]CPU time spent in user space%
CPU CoresNumber of CPU cores on the hostcnt
CPU Usage [Active]CPU time used, excluding idle and IO wait states%
CPU Usage [Idle]CPU time spent in idle state%
CPU Usage [IO Wait]CPU time spent in IO wait state%
CPU Usage [System]CPU time used by the kernel%
CPU Usage [User]CPU time used by user space%
CPU Usage/Core [Active]CPU time used per core, excluding idle and IO wait states%
CPU Usage/Core [Idle]CPU time spent in idle state per core%
CPU Usage/Core [IO Wait]CPU time spent in IO wait state per core%
CPU Usage/Core [System]CPU time used by the kernel per core%
CPU Usage/Core [User]CPU time used by user space per core%
Disk CPU Usage [IO Request]CPU time spent on IO requests%
Disk Queue Size [Avg]Average queue length of requestsnum
Disk Read BytesBytes read from the device per secondbytes
Disk Read Bytes [Delta Avg]Average delta of bytes read from the devicebytes
Disk Read Bytes [Delta Max]Maximum delta of bytes read from the devicebytes
Disk Read Bytes [Delta Min]Minimum delta of bytes read from the devicebytes
Disk Read Bytes [Delta Sum]Sum of delta of bytes read from the devicebytes
Disk Read Bytes [Delta]Delta of bytes read from the devicebytes
Disk Read Bytes [Success]Total bytes successfully readbytes
Disk Read RequestsNumber of read requests to the device per secondcnt
Disk Read Requests [Delta Avg]Average delta of read requests to the devicecnt
Disk Read Requests [Delta Max]Maximum delta of read requests to the devicecnt
Disk Read Requests [Delta Min]Minimum delta of read requests to the devicecnt
Disk Read Requests [Delta Sum]Sum of delta of read requests to the devicecnt
Disk Read Requests [Success Delta]Delta of successful read requests to the devicecnt
Disk Read Requests [Success]Total successful read requestscnt
Disk Request Size [Avg]Average size of requests to the devicenum
Disk Service Time [Avg]Average service time of requests to the devicems
Disk Wait Time [Avg]Average wait time of requests to the devicems
Disk Wait Time [Read]Average read wait time of the devicems
Disk Wait Time [Write]Average write wait time of the devicems
Disk Write Bytes [Delta Avg]Average delta of bytes written to the devicebytes
Disk Write Bytes [Delta Max]Maximum delta of bytes written to the devicebytes
Disk Write Bytes [Delta Min]Minimum delta of bytes written to the devicebytes
Disk Write Bytes [Delta Sum]Sum of delta of bytes written to the devicebytes
Disk Write Bytes [Delta]Delta of bytes written to the devicebytes
Disk Write Bytes [Success]Total bytes successfully writtenbytes
Disk Write RequestsNumber of write requests to the device per secondcnt
Disk Write Requests [Delta Avg]Average delta of write requests to the devicecnt
Disk Write Requests [Delta Max]Maximum delta of write requests to the devicecnt
Disk Write Requests [Delta Min]Minimum delta of write requests to the devicecnt
Disk Write Requests [Delta Sum]Sum of delta of write requests to the devicecnt
Disk Write Requests [Success Delta]Delta of successful write requests to the devicecnt
Disk Write Requests [Success]Total successful write requestscnt
Disk Writes BytesBytes written to the device per secondbytes
Filesystem Hang CheckFilesystem hang check (normal: 1, abnormal: 0)status
Filesystem NodesTotal number of filesystem nodescnt
Filesystem Nodes [Free]Total number of available filesystem nodescnt
Filesystem Size [Available]Available disk space in bytesbytes
Filesystem Size [Free]Free disk space in bytesbytes
Filesystem Size [Total]Total disk space in bytesbytes
Filesystem UsageDisk space usage rate%
Filesystem Usage [Avg]Average disk space usage rate%
Filesystem Usage [Inode]Inode usage rate%
Filesystem Usage [Max]Maximum disk space usage rate%
Filesystem Usage [Min]Minimum disk space usage rate%
Filesystem Usage [Total]Total disk space usage rate%
Filesystem UsedUsed disk space in bytesbytes
Filesystem Used [Inode]Used inode space in bytesbytes
Memory FreeTotal available memory in bytesbytes
Memory Free [Actual]Actual available memory in bytesbytes
Memory Free [Swap]Available swap memory in bytesbytes
Memory TotalTotal memory in bytesbytes
Memory Total [Swap]Total swap memory in bytesbytes
Memory UsageMemory usage rate%
Memory Usage [Actual]Actual memory usage rate%
Memory Usage [Cache Swap]Cache swap usage rate%
Memory Usage [Swap]Swap memory usage rate%
Memory UsedUsed memory in bytesbytes
Memory Used [Actual]Actual used memory in bytesbytes
Memory Used [Swap]Used swap memory in bytesbytes
CollisionsNetwork collisionscnt
Network In BytesReceived bytesbytes
Network In Bytes [Delta Avg]Average delta of received bytesbytes
Network In Bytes [Delta Max]Maximum delta of received bytesbytes
Network In Bytes [Delta Min]Minimum delta of received bytesbytes
Network In Bytes [Delta Sum]Sum of delta of received bytesbytes
Network In Bytes [Delta]Delta of received bytesbytes
Network In DroppedDropped received packetscnt
Network In ErrorsReceived errorscnt
Network In PacketsReceived packetscnt
Network In Packets [Delta Avg]Average delta of received packetscnt
Network In Packets [Delta Max]Maximum delta of received packetscnt
Network In Packets [Delta Min]Minimum delta of received packetscnt
Network In Packets [Delta Sum]Sum of delta of received packetscnt
Network In Packets [Delta]Delta of received packetscnt
Network Out BytesSent bytesbytes
Network Out Bytes [Delta Avg]Average delta of sent bytesbytes
Network Out Bytes [Delta Max]Maximum delta of sent bytesbytes
Network Out Bytes [Delta Min]Minimum delta of sent bytesbytes
Network Out Bytes [Delta Sum]Sum of delta of sent bytesbytes
Network Out Bytes [Delta]Delta of sent bytesbytes
Network Out DroppedDropped sent packetscnt
Network Out ErrorsSent errorscnt
Network Out PacketsSent packetscnt
Network Out Packets [Delta Avg]Average delta of sent packetscnt
Network Out Packets [Delta Max]Maximum delta of sent packetscnt
Network Out Packets [Delta Min]Minimum delta of sent packetscnt
Network Out Packets [Delta Sum]Sum of delta of sent packetscnt
Network Out Packets [Delta]Delta of sent packetscnt
Open Connections [TCP]Open TCP connectionscnt
Open Connections [UDP]Open UDP connectionscnt
Port UsagePort usage rate%
SYN Sent SocketsNumber of sockets in SYN_SENT statecnt
Kernel PID MaxMaximum PID valuecnt
Kernel Thread MaxMaximum thread valuecnt
Process CPU UsageCPU time used by the process%
Process CPU Usage/CoreCPU time used by the process per core%
Process Memory UsageResident Set size%
Process Memory UsedUsed memory by the processbytes
Process PIDProcess IDPID
Process PPIDParent process IDPID
Processes [Dead]Number of dead processescnt
Processes [Idle]Number of idle processescnt
Processes [Running]Number of running processescnt
Processes [Sleeping]Number of sleeping processescnt
Processes [Stopped]Number of stopped processescnt
Processes [Total]Total number of processescnt
Processes [Unknown]Number of unknown processescnt
Processes [Zombie]Number of zombie processescnt
Running Process UsageProcess usage rate%
Running ProcessesNumber of running processescnt
Running Thread UsageThread usage rate%
Running ThreadsNumber of running threadscnt
Context SwitchesContext switches per secondcnt
Load/Core [1 min]Load per core over 1 minutecnt
Load/Core [15 min]Load per core over 15 minutescnt
Load/Core [5 min]Load per core over 5 minutescnt
Multipaths [Active]Number of active multipath connectionscnt
Multipaths [Failed]Number of failed multipath connectionscnt
Multipaths [Faulty]Number of faulty multipath connectionscnt
NTP OffsetMeasured offset from the NTP servernum
Run Queue LengthRun queue lengthnum
UptimeSystem uptime in millisecondsms
Context SwitchiesContext switches per secondcnt
Disk Read Bytes [Sec]Bytes read from the device per secondcnt
Disk Read Time [Avg]Average read time from the devicesec
Disk Transfer Time [Avg]Average disk transfer timesec
Disk UsageDisk usage rate%
Disk Write Bytes [Sec]Bytes written to the device per secondcnt
Disk Write Time [Avg]Average write time to the devicesec
Pagingfile UsagePaging file usage rate%
Pool Used [Non Paged]Non-paged pool usagebytes
Pool Used [Paged]Paged pool usagebytes
Process [Running]Number of running processescnt
Threads [Running]Number of running threadscnt
Threads [Waiting]Number of waiting threadscnt
Table. GPU Server Additional Monitoring Metrics (Agent Installation Required)

2.3.1.3 - ServiceWatch Metrics

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

Notice
  • GPU Server’s basic monitoring and detailed monitoring are provided with the same metrics as Virtual Server, and the namespace is also provided as Virtual Server.
  • GPU-related metrics are provided through ServiceWatch Agent. For information on how to collect metrics using ServiceWatch Agent, refer to the ServiceWatch Agent guide.
Reference
To view metrics in ServiceWatch, refer to the ServiceWatch guide.

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

Basic Metrics

The following are basic metrics for the namespace Virtual Server.

In the table below, metrics with metric names marked in bold are selected as key metrics among the basic metrics provided by Virtual Server. Key metrics are used to configure service dashboards that are automatically built for each service in ServiceWatch.

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

Performance ItemDetailed DescriptionUnitMeaningful Statistics
Instance StateInstance state display
  • 1 - Active
  • 0 - Off
None
  • Sum
CPU UsageCPU usagePercent
  • Average
  • Maximum
  • Minimum
Disk Read BytesAmount read from block device (bytes)Bytes
  • Sum
  • Average
  • Maximum
  • Minimum
Disk Read RequestsNumber of read requests from block deviceCount
  • Sum
  • Average
  • Maximum
  • Minimum
Disk Write BytesAmount written to block device (bytes)Bytes
  • Sum
  • Average
  • Maximum
  • Minimum
Disk Write RequestsNumber of write requests to block deviceCount
  • Sum
  • Average
  • Maximum
  • Minimum
Network In BytesAmount received on network interface (bytes)Bytes
  • Sum
  • Average
  • Maximum
  • Minimum
Network In DroppedNumber of received packets dropped on network interfaceCount
  • Sum
  • Average
  • Maximum
  • Minimum
Network In PacketsNumber of received packets on network interfaceCount
  • Sum
  • Average
  • Maximum
  • Minimum
Network Out BytesAmount transmitted on network interface (bytes)Bytes
  • Sum
  • Average
  • Maximum
  • Minimum
Network Out DroppedNumber of transmitted packets dropped on network interfaceCount
  • Sum
  • Average
  • Maximum
  • Minimum
Network Out PacketsAmount transmitted on network interfaceCount
  • Sum
  • Average
  • Maximum
  • Minimum
Table. Virtual Server Basic Metrics

2.3.2 - How-to guides

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

Create GPU Server

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

If you want to create a GPU Server, follow the steps below.

  1. All Services > Compute > GPU Server Please click the menu. Navigate to the GPU Server’s Service Home page.
  2. Service Home on the page, click the Create GPU Server button. Navigate to the Create GPU Server page.
  3. GPU Server creation On the page, enter the information required to create the service, and select detailed options.
    • Image and version selection Select the required information in the area.
      Category
      Required or not
      Detailed description
      ImageRequiredSelect provided image type
      • Ubuntu
      Image versionRequiredSelect version of the chosen image
      • Provides a list of server image versions offered
      Table. GPU Server image and version selection input items
    • Service Information Input Enter or select the required information in the area.
      Category
      Required or not
      Detailed description
      Server countRequiredNumber of GPU Server servers to create simultaneously
      • Only numbers can be entered, and input a value between 1 and 100
      Service Type > Server TypeRequiredGPU Server Server Type
      • Indicates the server specifications of GPU type, select a server that includes 1, 2, 4, or 8 GPUs
      Service Type > Planned ComputeSelectResource status with Planned Compute set
      • In Use: Number of resources with Planned Compute set that are currently in use
      • Configured: Number of resources with Planned Compute set
      • Coverage Preview: Amount applied per resource by Planned Compute
      • Planned Compute Service Application: Go to the Planned Compute service application page
      Block StorageRequiredSet the Block Storage used by the GPU Server according to its purpose
      • Basic: Area where the OS is installed and used
        • Capacity can be entered in Units (minimum capacity varies depending on the OS image type)
          • RHEL: values between 3 and 1,536 can be entered
          • Ubuntu: values between 3 and 1,536 can be entered
        • SSD: high-performance general volume
        • HDD: general volume
        • SSD/HDD_KMS: additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption key
          • Encryption can only be applied at initial creation (cannot be changed after creation)
          • Performance degradation occurs when using SSD_KMS disk type
      • Additional: Used when additional user space is needed outside the OS area
        • After selecting Use, enter the storage type and capacity
        • To add storage, click the + button (up to 25 can be added); to delete, click the x button
        • Capacity can be entered in Units, values between 1 and 1,536
          • Since 1 Unit equals 8 GB, 8 to 12,288 GB can be created
        • SSD: high-performance general volume
        • HDD: general volume
        • SSD/HDD_KMS: additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption key
          • Encryption can only be applied at initial creation (cannot be changed after creation)
          • Performance degradation may occur when using SSD_KMS disk type
      • Delete on termination: If Delete on Termination is set to Enabled, the volume will be terminated together when the server is terminated
        • Volumes with snapshots are not deleted even if Delete on termination is set to Enabled
        • A multi-attach volume is deleted only when the server being terminated is the last remaining server attached to the volume
      Table. GPU Server Service Configuration Items
    • Required Information Input Please enter or select the required information in the area.
      Category
      Required
      Detailed description
      Server NameRequiredEnter a name to distinguish the server when the selected server count is 1
      • Set hostname with the entered server name
      • Use English letters, numbers, spaces, and special characters (- _) within 63 characters
      Server name PrefixRequiredEnter Prefix to distinguish each server generated when the selected number of servers is 2 or more
      • Automatically generated as user input value (prefix) + ‘-#’ format
      • Enter within 59 characters using English letters, numbers, spaces, and special characters (-, _)
      Network Settings > Create New Network PortRequiredSet the network where the GPU Server will be installed
      • Select a pre-created VPC.
      • General Subnet: Select a pre-created General Subnet
        • IP can be set to auto-generate or user input; if input is selected, the user can directly enter the IP
        • NAT: Can be used only if there is one server and the VPC has an Internet Gateway attached. Use checked allows selection of NAT IP
        • NAT IP: Select NAT IP
          • If there is no NAT IP to select, click the Create New button to generate a Public IP
          • Refresh button click to view and select the created Public IP
          • Creating a Public IP incurs charges according to the Public IP pricing policy
      • Local Subnet (Optional): Select Local Subnet Use
        • Not a required element for creating the service
        • A pre-created Local Subnet must be selected
        • IP can be set to auto-generate or user input; input selected allows user to directly enter IP
        • Security Group: Settings required to access the server
          • Select: Choose a pre-created Security Group
          • Create New: If there is no applicable Security Group, it can be created separately in the Security Group service
          • Up to 5 can be selected
          • If no Security Group is set, all access is blocked by default
          • A Security Group must be set to allow required access
      Network Settings > Existing Network Port SpecificationRequiredSet the network where the GPU Server will be installed
      • Select a pre-created VPC
      • General Subnet: Select a pre-created General Subnet and Port
        • NAT: Can be used only if there is one server and the VPC has an Internet Gateway attached; checking use allows selection of a NAT IP.
        • NAT IP: Select NAT IP
          • If there is no NAT IP to select, click the New Creation button to generate a Public IP
          • Click the Refresh button to view and select the created Public IP
      • Local Subnet (Optional): Select Use of Local Subnet
        • Select a pre-created Local Subnet and Port
      KeypairRequiredUser authentication method to use when connecting to the server
      • New Creation: If a new Keypair is needed, create a new one
      • List of default login accounts by OS
        • RHEL: cloud-user
        • Ubuntu: ubuntu
      • </ul
      Table. GPU Server required information input items
    • Additional Information Input Enter or select the required information in the area.
      Category
      Required
      Detailed description
      LockSelectSet whether to use Lock
      • Using Lock prevents actions such as server termination, start, stop from being executed, preventing malfunctions caused by mistakes
      Init scriptSelectScript executed when the server starts
      • The Init script must be written as a Batch script for Windows, a Shell script or cloud‑init for Linux, depending on the image type.
      • Up to 45,000 bytes can be entered
      TagSelectAdd Tag
      • Up to 50 can be added per resource
      • After clicking the Add Tag button, enter or select Key, Value values
      Table. GPU Server 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 GPU Server list page.

GPU Server Check detailed information

GPU Server service can view and edit the full resource list and detailed information. GPU Server Detail page consists of Detail Information, Tags, Job History tabs.

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

  1. All Services > Compute > GPU Server Click the menu. Go to the GPU Server’s Service Home page.
  2. Click the GPU Server menu on the Service Home page. Navigate to the GPU Server list page.
  3. GPU Server List Click the resource to view detailed information on the page. GPU Server Details You will be taken to the page.
    • GPU Server Details page displays status information and additional feature information, and consists of Details, Tags, Job History tabs.
    • For detailed information about the GPU Server status, please refer to Check GPU Server detailed information.
      CategoryDetailed description
      GPU Server statusStatus of GPU Server created by the user
      • Build: State where Build command has been delivered
      • Building: Build in progress
      • Networking: Server creation in‑progress process
      • Scheduling: Server creation in‑progress process
      • Block_Device_Mapping: Connecting Block Storage during server creation
      • Spawning: State where server creation process is ongoing
      • Active: Usable state
      • Powering_off: State when stop request is made
      • Deleting: Server deletion in progress
      • Reboot_Started: Reboot in progress state
      • Error: Error state
      • Migrating: State where server is migrating to another host
      • Reboot: State where Reboot command has been delivered
      • Rebooting: Restart in progress
      • Rebuild: State where Rebuild command has been delivered
      • Rebuilding: State when Rebuild is requested
      • Rebuild_Spawning: State where Rebuild process is ongoing
      • Resize: State where Resize command has been delivered
      • Resizing: Resize in progress
      • Resize_Prep: State when server type modification is requested
      • Resize_Migrating: State where server is moving to another host while Resize is in progress
      • Resize_Migrated: State where server has completed moving to another host while Resize is in progress
      • Resize_Finish: Resize completed
      • Revert_Resize: Resize or migration of the server failed for some reason. The target server is cleaned up and the original server restarts
      • Shutoff: State when Powering off is completed
      • Verity_Resize: After Resize_Prep due to server type modification request, state where server type is confirmed / can choose to revert server type
      • Resize_Reverting: State when server type revert is requested
      • Resize_Confirming: State where server’s Resize request is being confirmed
      Server ControlButton to change server status
      • Start: Start a stopped server
      • Stop: Stop a running server
      • Restart: Restart a running server
      Image GenerationCreate user custom image using the current server’s image
      Console LogView current server’s console log
      • You can check the console log output from the current server. For more details, refer to Check Console Log.
      Dump creationCreate a dump of the current server
      • The dump file is created inside the GPU Server
      • For detailed dump creation method, refer to [Create Dump](#dump-생성하기)
      | | Rebuild | All data and settings of the existing server are deleted, and a new server is set up
      • For details, refer to [Perform Rebuild](#rebuild-수행하기).
      | | Service Cancellation | Button to cancel the service |
      Table. GPU Server status information and additional features

Detailed Information

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

CategoryDetailed description
serviceservice name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In the GPU Server service, it means GPU Server SRN
Resource NameResource Name
  • In the GPU Server service, it refers to the GPU Server name
Resource IDUnique resource ID in the service
CreatorUser who created the service
Creation timeService creation time
EditorUser who edited the service information
Modification DateDate Service Information Was Modified
Server nameServer name
Server TypevCPU, Memory, GPU Information Display
  • If you need to change to a different server type, click the Edit button to set
Image NameService OS Image and Version
LockDisplay Lock usage status
  • If you need to change the Lock attribute value, click the Edit button to set
Server GroupServer group name the server belongs to
Keypair nameServer authentication information set by the user
Planned ComputeResource status with Planned Compute set
NetworkNetwork information of GPU Server
  • VPC, general Subnet, IP, NAT IP, NAT IP status, Security Group
  • If you need to change the NAT IP value, you can set it by clicking the Edit button
  • If you need to change the Security Group, you can set it by clicking the Edit button
  • Add as new network: select a general Subnet and IP
    • You can select another general Subnet within the same VPC
    • IP can be set to auto-generate or user input; if input is selected, the user can directly enter the IP
  • Add with existing port: select a pre-created general Subnet and port
Local SubnetGPU Server’s Local Subnet Information
  • Local Subnet, Local Subnet IP, Security Group
  • If a Security Group change is needed, you can click the Edit button to set it
  • Add as New Network: Select Local Subnet and IP
    • You can select a different Local Subnet within the same VPC
    • IP can be auto-generated or user input; if Input is selected, the user enters the IP directly
  • Add with Existing Port: Select a pre-created Local Subnet and port
Block StorageInformation of Block Storage connected to the server
  • Volume ID, Volume Name, Type, Capacity, Connection Info, Category, Delete on termination, Status
  • Add: Additional Block Storage can be connected if needed
  • Modify Delete on termination: Modify Delete on termination value
  • Disconnect: Disconnect the additionally connected Block Storage
Table. GPU Server detailed information tab items

tag

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

CategoryDetailed description
Tag ListTag List
  • Tag’s Key, Value information can be checked
  • Up to 50 tags can be added per resource
  • When entering tags, you can search and select from existing Key and Value lists
Table. GPU Server Tag Tab Items

Work History

You can view the job history of the selected resource on the GPU Server List page.

CategoryDetailed description
Work History ListResource Change History
  • Work date and time, Resource ID, Resource name, Work details, Event topic, Work result, Verify worker information
Table. Work History Tab Detailed Information Items

GPU Server Operation Control

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

GPU Server Start

You can start a shutoff GPU Server. To start the GPU Server, follow the steps below.

  1. All Services > Compute > GPU Server Please click the menu. Navigate to the GPU Server’s Service Home page.
  2. Click the GPU Server menu on the Service Home page. Go to the GPU Server List page.
  3. GPU Server List page, click the resource to start among the shutoff servers, and go to the GPU Server Details page.
  • GPU Server list page, you can start each resource via the right more button.
    • After selecting multiple servers with the check box, you can control multiple servers simultaneously through the Start button at the top.
  1. GPU Server Details On the page, click the Start button at the top to start the server. Check the changed server status in the Status Display item.
    • When the GPU Server start is completed, the server status changes from Shutoff to Active.
    • For detailed information about the GPU Server status, please refer to Check GPU Server detailed information.

GPU Server Stop

You can stop a GPU Server that is active. To stop the GPU Server, follow the steps below.

  1. All Services > Compute > GPU Server Click the menu. Go to the Service Home page of GPU Server.
  2. Service Home page, click the GPU Server menu. Navigate to the GPU Server List page.
  3. GPU Server List page, click the resource to stop among the servers that are active (Active), and go to the GPU Server Details page.
  • GPU Server List on the page, you can stop each resource via the right More button.
    • After selecting multiple servers with the checkbox, you can control multiple servers simultaneously through the Stop button at the top.
  1. GPU Server Details page, click the top Stop button to start the server. Check the changed server status in the Status Display item.
    • When GPU Server shutdown is completed, the server status changes from Active to Shutoff.
    • For detailed information about the GPU Server status, please refer to Check GPU Server detailed information.

GPU Server Restart

You can restart the generated GPU Server. To restart the GPU Server, follow the steps below.

  1. All Services > Compute > GPU Server Please click the menu. Navigate to the GPU Server’s Service Home page.
  2. Click the GPU Server menu on the Service Home page. It navigates to the GPU Server List page.
  3. GPU Server List page, click the resource to restart, and navigate to the GPU Server Details page.
    • GPU Server List page, you can restart each resource by using the right More button.
    • After selecting multiple servers with the checkbox, you can control multiple servers simultaneously through the Restart button at the top.
  4. GPU Server Details on the page, click the Restart button at the top to start the server. Check the changed server status in the Status Display item.
    • GPU Server during restart, the server status goes through Rebooting and finally changes to Active.
    • For detailed information about the GPU Server status, please refer to Check GPU Server detailed information.

GPU Server Resource Management

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

Image Create

You can create an image of a running GPU server.

Reference

This content provides instructions on how to create a user custom image using the image of a running GPU server.

  • GPU Server list or GPU Server details page, click the Create Image button to create a user Custom Image.

To create an Image of the GPU Server, follow the steps below.

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

  2. Service Home page, click the GPU Server menu. Go to the GPU Server list page.

  3. Click the resource to create an Image on the GPU Server List page. It navigates to the GPU Server Details page.

  4. GPU Server Details on the page, click the Image Generation button. Navigate to the Image Generation page.

    • Service Information Input area, please enter the required information.
      Category
      Required
      Detailed description
      Image NameRequiredImage name to be generated
      • Enter within 200 characters using English letters, numbers, spaces, and special characters (- _)
      Table. Image Service Information Input Items
  5. Check the input information and click the Complete button.

    • When creation is complete, check the created resources on the All Services > Compute > GPU Server > Image List page.
Notice
  • If you create an Image, the generated Image is stored in the Object Storage used as internal storage. Therefore, Object Storage usage fees are charged.
  • Active state GPU Server-generated image’s file system cannot guarantee integrity, so image creation after server shutdown is recommended.

ServiceWatch Enable Detailed Monitoring

Basically, the GPU Server is linked with the basic monitoring of ServiceWatch and the Virtual Server namespace. You can enable detailed monitoring as needed to more quickly identify and address operational issues. For more information about ServiceWatch, see the ServiceWatch Overview (/userguide/management/service_watch/overview/).

Reference
GPU Server provides basic and detailed monitoring in the same namespace as Virtual Server. GPU Server’s GPU metrics are scheduled to be provided by ServiceWatch Agent. (Scheduled for Dec 2025)
Caution
Basic monitoring is provided for free, but activating detailed monitoring incurs additional charges. Please be aware when using.

To enable detailed monitoring of ServiceWatch on the GPU Server, follow these steps.

  1. All Services > Compute > GPU Server Please click the menu. Navigate to the GPU Server’s Service Home page.
  2. Click the GPU Server menu on the Service Home page. Navigate to the GPU Server list page.
  3. On the GPU Server List page, click the resource to enable ServiceWatch detailed monitoring. You will be taken to the GPU Server Details page.
  4. GPU Server Details page, click the ServiceWatch detailed monitoring Edit button. You will be taken to the ServiceWatch Detailed Monitoring Edit popup.
  5. ServiceWatch Detailed Monitoring Modification In the popup window, after selecting Enable, check the guidance text and click the Confirm button.
  6. GPU Server Details page, check the ServiceWatch detailed monitoring items.

ServiceWatch Disable detailed monitoring

Caution
Disabling detailed monitoring is required for cost efficiency. Keep detailed monitoring enabled only when absolutely necessary, and disable detailed monitoring for the rest.

To disable the detailed monitoring of ServiceWatch on the GPU Server, follow the steps below.

  1. All Services > Compute > GPU Server Please click the menu. Navigate to the GPU Server’s Service Home page.
  2. Service Home page, click the GPU Server menu. Navigate to the GPU Server list page.
  3. Click the resource to disable ServiceWatch detailed monitoring on the GPU Server List page. It navigates to the GPU Server Details page.
  4. GPU Server Details page, click the ServiceWatch detailed monitoring Edit button. It moves to the ServiceWatch Detailed Monitoring Edit popup.
  5. ServiceWatch Detailed Monitoring Edit in the popup window, after deselecting Enable, check the guide text and click the Confirm button.
  6. GPU Server Details page, check the ServiceWatch detailed monitoring items.

GPU Server Management Additional Features

For GPU Server management, you can view Console logs, generate Dump, and Rebuild. To view Console logs, generate Dump, and Rebuild the GPU Server, follow the steps below.

Check console log

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

To check the console logs of the GPU Server, follow the steps below.

  1. All Services > Compute > GPU Server Please click the menu. Navigate to the GPU Server’s Service Home page.
  2. Click the GPU Server menu on the Service Home page. Navigate to the GPU Server List page.
  3. On the GPU Server List page, click the resource to view the console log. Navigate to the GPU Server Details page.
  4. GPU Server Details on the page, click the Console Log button. It will move to the Console Log popup window.
  5. Console Log Check the console log displayed in the popup window.

Create Dump

To create a Dump file of the GPU Server, follow the steps below.

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

Rebuild perform

You can delete all data and settings of the existing GPU Server and rebuild it on a new server.

To perform the Rebuild of the GPU Server, follow the steps below.

  1. All Services > Compute > GPU Server Click the menu. Navigate to the Service Home page of GPU Server.
  2. Click the GPU Server menu on the Service Home page. It navigates to the GPU Server List page.
  3. GPU Server List page, click the resource to perform Rebuild. GPU Server Details page will be opened.
  4. GPU Server Details on the page click the Rebuild button.
    • During GPU Server Rebuild, the server status changes to Rebuilding, and when the Rebuild is completed, it returns to the state before the Rebuild.
    • For detailed information about the GPU Server status, please refer to Check GPU Server detailed information.

GPU Server Cancel

If you cancel an unused GPU Server, you can reduce operating costs. However, if you cancel a GPU Server, the service currently running may be stopped immediately, so you should proceed with the cancellation after fully considering the impact that may occur when the service is interrupted.

Caution
Please note that data cannot be recovered after service termination.

To cancel the GPU Server, follow the steps below.

  1. All Services > Compute > GPU Server Click the menu. Navigate to the GPU Server’s Service Home page.
  2. Click the GPU Server menu on the Service Home page. Navigate to the GPU Server List page.
  3. GPU Server List on the page, select the resource to cancel, and click the Cancel Service button.
    • The termination of connected storage depends on the Delete on termination setting, so please refer to Termination Constraints.
  4. When termination is completed, check on the GPU Server List page whether the resource has been terminated.

Termination Constraints

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

Cancellation not allowed
  • If File Storage is connected, please disconnect the File Storage connection first.
  • If LB Pool is connected please disconnect the LB Pool connection first.
  • When Lock is set please change the Lock setting to unused and try again.

The termination of attached storage depends on the Delete on termination setting.

Delete on termination Delete per setting
  • Delete on termination Whether the volume deletion also varies depending on the setting.
    • Delete on termination If not set: Even if you terminate the GPU Server, the volume will not be deleted.
    • Delete on termination when set: If you terminate the GPU Server, the volume will be deleted.
  • Volumes with a Snapshot will not be deleted even if Delete on termination is set.
  • Multi attach volume is deleted only when the server you are trying to delete is the last remaining server attached to the volume.

2.3.2.1 - Image Management

Users can enter the required information for the Image service within the GPU Server service and select detailed options through the Samsung Cloud Platform Console to create the respective service.

Image Generation

You can create an image of a running GPU Server. To create an image of a GPU Server, please refer to Create Image.

Image Check detailed information

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

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

  1. All Services > Compute > GPU Server Click the menu. Navigate to the Service Home page of GPU 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. You will be taken to the Image Detail page.
    • Image Details page displays status information and additional feature information, and consists of Detail Information, Tag, Work History tabs.
      CategoryDetailed description
      Image StatusUser-generated Image’s status
      • Active: Available state
      • Queued: When creating Image, Image is uploaded and waiting for processing
      • Importing: When creating Image, Image is uploaded and being processed
      Share to another AccountImage can be shared to another Account
      • Image’s Visibility must be in Shared state to be able to share to another Account
      Delete ImageButton to delete the Image
      • If the Image is deleted, it cannot be recovered
      Table. GPU Server Image status information and additional features

Detailed Information

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

CategoryDetailed description
ServiceService Name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • Means the SRN of a GPU Server Image
Resource NameImage Name
Resource IDImage ID
CreatorUser who created the Image
Creation date/timeDate/time when the image was created
EditorUser who edited the Image
Edit date/timeDate and time the image was edited
Image nameImage name
Minimum DiskImage’s minimum disk capacity (GB)
  • If you need to modify the minimum disk, click the Edit button to set it
Minimum RAMImage’s minimum RAM capacity (GB)
OS typeImage’s OS type
OS hash algorithmOS hash algorithm method
VisibilityDisplays access permissions for images
  • Private can be used only within the project, and Shared can be shared across projects
ProtectedSelect whether image deletion is prohibited
  • If checked, it can prevent accidental deletion of images
  • This setting can be changed after image creation
Image File URLImage file URL uploaded when generating image
  • Not displayed for images created via the image generation menu on the GPU Server detail page
Sharing StatusStatus of sharing images with other Accounts
  • Approved Account ID: ID of the Account that has been approved for sharing
  • Modification Date/Time: The date/time when sharing was requested to another Account, if the sharing status later changes from Pending → Accepted it is updated to that date/time
  • Status: Approval Status
    • Accepted: Approved and being shared
    • Pending: Waiting for approval
  • Delete: Sharing has been stopped
Table. Image detailed information tab items

Tag

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

CategoryDetailed description
Tag ListTag List
  • Tag’s Key and Value information can be checked
  • Up to 50 tags can be added per resource
  • When entering tags, you can search and select from previously created Key and Value lists
Table. Image tag tab items

Work History

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

CategoryDetailed description
Work History ListResource Change History
  • Work date and time, Resource ID, Resource name, Work details, Event topic, Work result, Verify worker information
Table. GPU Server Image Job History Tab Detailed Information Items

Image Resource Management

Describes the control and management functions of the generated image.

Share to another account

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

  1. Log in to the shared Account and click the All Services > Compute > GPU Server menu. Navigate to the GPU 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 to control on the Image List page. It moves to the Image Detail page.
  4. Click the Share to another Account button. It navigates to the Share image to another Account page.
    • Share to another Account feature allows you to share the Image with another Account. To share the Image with another Account, the Image’s Visibility must be Shared.
  5. Share images to another Account On the page, enter the required information and click the Complete button.
    Category
    Required or not
    Detailed description
    Image Name-Name of the image to share
    • Input not allowed
    Image ID-Image ID to share
    • Input not allowed
    Shared Account IDRequiredEnter another Account ID to share
    • Enter within 64 characters using English letters, numbers, special characters-
    Table. Required input items for sharing images to another Account
  6. Image Details page’s sharing status can be checked for information.
    • At the initial request, the status is Pending, and when approval is completed in the account to be shared, it changes to Accepted.
Notice
Only the Image created by the current user’s Image file upload can be shared with another Account. If a Custom Image is created from the Image of a running GPU Server, it cannot be shared with another Account, and this feature is planned to be provided, so please note.

Receive sharing 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 > GPU Server menu. Navigate to the Service Home page of the GPU Server.
  2. Click the Image menu on the Service Home page. Go to the Image list page.
  3. Image List on the page click the Get Image Share button. Go to the Get Image Share popup window.
  4. Receive Image Share In the popup window, enter the resource ID of the Image you want to receive, and click the Confirm button.
  5. When image sharing is completed, 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.

Caution
Please be careful because data cannot be recovered after deleting the service.

To delete the image, follow the steps below.

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

2.3.2.2 - Using Multi-instance GPU in GPU Server

After creating a GPU Server, you can enable the MIG (Multi-instance GPU) feature on the GPU Server’s VM (Guest OS) and create an instance to use it.

Multi-instance GPU (NVIDIA A100) Overview

NVIDIA A100 is a Multi-instance GPU (MIG) based on the NVIDIA Ampere architecture, which can be securely divided into up to 7 independent GPU instances to operate CUDA (Compute Unified Device Architecture) applications. The NVIDIA A100 provides independent GPU resources to multiple users by allocating computing resources in a way optimized for GPU usage while utilizing high-bandwidth memory (HBM) and cache. Users can maximize GPU utilization by utilizing workloads that have not reached the maximum computing capacity of the GPU through parallel execution of each workload.

Multi-instance GPU configuration diagram
Figure. Multi-instance GPU configuration diagram

Using Multi-instance GPU Feature

To use the multi-instance GPU feature, you must create a GPU Server service on the Samsung Cloud Platform and then create a VM Instance (GuestOS) with an A100 GPU assigned. After completing the GPU Server creation, you can follow the MIG application order and MIG release order below to apply it.

Multi-instance GPU creation
Figure. Multi-instance GPU creation

MIG Application Order
MIG activation → GPU Instance creation → Compute Instance creation → MIG usage
MIG Removal Order
Compute Instance deletion → GPU Instance deletion → MIG feature deactivation(disabling)

Reference
  • The system requirements for using the MIG feature are as follows (refer to NVIDIA - Supported GPUs).
    • CUDA toolkit 11, NVIDIA driver 450.80.02 or later version
    • Linux distribution operating system supporting CUDA toolkit 11
  • When operating a container or Kubernetes service, the requirements for using the MIG feature are as follows.
    • NVIDIA Container Toolkit(nvidia-docker2) v 2.5.0 or later version
    • NVIDIA K8s Device Plugin v 0.7.0 or later version
    • NVIDIA gpu-feature-discovery v 0.2.0 or later version

MIG Application and Usage

To activate MIG and create an instance to assign a task, follow these steps.

MIG Application Order
MIG activation → GPU Instance creation → Compute Instance creation → MIG usage

MIG Activation

  1. Check the GPU status on the VM Instance (GuestOS) before applying MIG.

    • MIG mode is Disabled status, please check.
      Color mode
      $ nvidia-smi
      Mon Sep 27 08:37:08 2021
      +-----------------------------------------------------------------------------+
      | NVIDIA-SMI 470.57.02    Driver Version: 470.57.02    CUDA Version: 11.4     |
      |-------------------------------+----------------------+----------------------|
      | GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
      | Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
      |                               |                      |               MIG M. |
      |===============================+======================+======================|
      |   0  NVDIA A100-SXM...  Off   | 00000000:05:00.0 Off |                    0 |
      | N/A   32C   P0    59W / 400W  |      0MiB / 81251MiB |      0%      Default |
      |                               |                      |             Disabled |
      +-------------------------------+----------------------+----------------------+
      
      +-----------------------------------------------------------------------------+
      | Processes:                                                                  |
      |  GPU   GI   CI       PID   Type   Process name                   GPU Memory |
      |        ID   ID                                                   Usage      |
      |=============================================================================|
      | No running processes found                                                  |
      +-----------------------------------------------------------------------------+
      $ nvidia-smi
      Mon Sep 27 08:37:08 2021
      +-----------------------------------------------------------------------------+
      | NVIDIA-SMI 470.57.02    Driver Version: 470.57.02    CUDA Version: 11.4     |
      |-------------------------------+----------------------+----------------------|
      | GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
      | Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
      |                               |                      |               MIG M. |
      |===============================+======================+======================|
      |   0  NVDIA A100-SXM...  Off   | 00000000:05:00.0 Off |                    0 |
      | N/A   32C   P0    59W / 400W  |      0MiB / 81251MiB |      0%      Default |
      |                               |                      |             Disabled |
      +-------------------------------+----------------------+----------------------+
      
      +-----------------------------------------------------------------------------+
      | Processes:                                                                  |
      |  GPU   GI   CI       PID   Type   Process name                   GPU Memory |
      |        ID   ID                                                   Usage      |
      |=============================================================================|
      | No running processes found                                                  |
      +-----------------------------------------------------------------------------+
      Code block. nvidia-smi command - Check GPU inactive state (1)
      Color mode
      $ nvidia-smi –L
      GPU 0: NVIDIA A100-SXM-80GB (UUID: GPU-c956838f-494a-92b2-6818-56eb28fe25e0)
      $ nvidia-smi –L
      GPU 0: NVIDIA A100-SXM-80GB (UUID: GPU-c956838f-494a-92b2-6818-56eb28fe25e0)
      Code block. nvidia-smi command - Check GPU inactive state (2)
  2. In the VM Instance(GuestOS), enable MIG for each GPU and reboot the VM Instance.

    Color mode
    $ nvidia-smi –I 0 –mig 1
    Enabled MIG mode for GPU 00000000:05:00.0
    All done.
    
    # reboot
    $ nvidia-smi –I 0 –mig 1
    Enabled MIG mode for GPU 00000000:05:00.0
    All done.
    
    # reboot
    Code Block. nvidia-smi Command - MIG Activation

Note

If the GPU monitoring agent displays the following warning message, stop the nvsm and dcgm services before enabling MIG.

Warning: MIG mode is in pending enable state for GPU 00000000:05:00.0: In use by another client. 00000000:05:00.0 is currently being used by one or more other processes (e.g. CUDA application or a monitoring application such as another instance of nvidia-smi).

# systemctl stop nvsm
# systemctl stop dcgm
  • After completing the MIG work, restart the nvsm and dcgm services.
  1. Check the GPU status after applying MIG in the VM Instance(GuestOS).
    • MIG mode must be in Enabled state.
      Color mode
      $ nvidia-smi
      Mon Sep 27 09:44:33 2021
      +-----------------------------------------------------------------------------+
      | NVIDIA-SMI 470.57.02    Driver Version: 470.57.02    CUDA Version: 11.4     |
      |-------------------------------+----------------------+----------------------|
      | GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
      | Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
      |                               |                      |               MIG M. |
      |===============================+======================+======================|
      |   0  NVDIA A100-SXM...  Off   | 00000000:05:00.0 Off |                   On |
      | N/A   32C   P0    59W / 400W  |      0MiB / 81251MiB |      0%      Default |
      |                               |                      |              Enabled |
      +-------------------------------+----------------------+----------------------+
      +-----------------------------------------------------------------------------+
      | MIG devices:                                                                |
      +-----------------------------------------------------------------------------+
      |  GPU  GI  CI  MIG |        Memory-Usage |        Vol|        Shared         |
      |       ID  ID  Dev |          BAR1-Usage | SM     Unc| CE  ENC  DEC  OFA  JPG|
      |                   |                     |        ECC|                       |
      |=============================================================================|
      | No MIG devices found                                                        |
      +-----------------------------------------------------------------------------+
      +-----------------------------------------------------------------------------+
      | Processes:                                                                  |
      |  GPU   GI   CI       PID   Type   Process name                   GPU Memory |
      |        ID   ID                                                   Usage      |
      |=============================================================================|
      | No running processes found                                                  |
      +-----------------------------------------------------------------------------+
      $ nvidia-smi
      Mon Sep 27 09:44:33 2021
      +-----------------------------------------------------------------------------+
      | NVIDIA-SMI 470.57.02    Driver Version: 470.57.02    CUDA Version: 11.4     |
      |-------------------------------+----------------------+----------------------|
      | GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
      | Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
      |                               |                      |               MIG M. |
      |===============================+======================+======================|
      |   0  NVDIA A100-SXM...  Off   | 00000000:05:00.0 Off |                   On |
      | N/A   32C   P0    59W / 400W  |      0MiB / 81251MiB |      0%      Default |
      |                               |                      |              Enabled |
      +-------------------------------+----------------------+----------------------+
      +-----------------------------------------------------------------------------+
      | MIG devices:                                                                |
      +-----------------------------------------------------------------------------+
      |  GPU  GI  CI  MIG |        Memory-Usage |        Vol|        Shared         |
      |       ID  ID  Dev |          BAR1-Usage | SM     Unc| CE  ENC  DEC  OFA  JPG|
      |                   |                     |        ECC|                       |
      |=============================================================================|
      | No MIG devices found                                                        |
      +-----------------------------------------------------------------------------+
      +-----------------------------------------------------------------------------+
      | Processes:                                                                  |
      |  GPU   GI   CI       PID   Type   Process name                   GPU Memory |
      |        ID   ID                                                   Usage      |
      |=============================================================================|
      | No running processes found                                                  |
      +-----------------------------------------------------------------------------+
      Code block. nvidia-smi command - Check GPU activation status (1)
      Color mode
      $ nvidia-smi –L
      GPU 0: NVIDIA A100-SXM-80GB (UUID: GPU-c956838f-494a-92b2-6818-56eb28fe25e0)
      $ nvidia-smi –L
      GPU 0: NVIDIA A100-SXM-80GB (UUID: GPU-c956838f-494a-92b2-6818-56eb28fe25e0)
      Code block. nvidia-smi command - Check GPU activation status (2)

GPU Instance Creation

After activating MIG and checking the status, you can create a GPU Instance.

  1. Check the list of MIG GPU instance profiles that can be created.

    Color mode
    $ nvidia-smi mig -i [GPU ID] -lgip
    $ nvidia-smi mig -i [GPU ID] -lgip
    Code block. nvidia-smi command - MIG GPU Instance profile list check

    Color mode
    $ nvidia-smi mig -i 0 -lgip
    +-----------------------------------------------------------------------------+
    | GPU instance profiles:                                                      |
    | GPU   Name             ID    Instances   Memory     P2P    SM    DEC   ENC  |
    |                              Free/Total   GiB              CE    JPEG  OFA  |
    |=============================================================================|
    |   0 MIG 1g.10gb        19    7/7         9.50       No     14     0     0   |
    |                                                             1     0     0   |
    +-----------------------------------------------------------------------------+
    |   0 MIG 1g.10gb+me     20    1/1         9.50       No     14     0     0   |
    |                                                             1     1     1   |
    +-----------------------------------------------------------------------------+
    |   0 MIG 2g.20gb        14    3/3         19.50      No     28     1     0   |
    |                                                             2     0     0   |
    +-----------------------------------------------------------------------------+
    |   0 MIG 3g.40gb         9    2/2         39.50      No     42     2     0   |
    |                                                             3     0     0   |
    +-----------------------------------------------------------------------------+
    |   0 MIG 4g.40gb         5    1/1         39.50      No     56     2     0   |
    |                                                             4     0     0   |
    +-----------------------------------------------------------------------------+
    |   0 MIG 7g.80gb         0    1/1         79.25      No     98     0     0   |
    |                                                             7     1     1   |
    +-----------------------------------------------------------------------------+
    $ nvidia-smi mig -i 0 -lgip
    +-----------------------------------------------------------------------------+
    | GPU instance profiles:                                                      |
    | GPU   Name             ID    Instances   Memory     P2P    SM    DEC   ENC  |
    |                              Free/Total   GiB              CE    JPEG  OFA  |
    |=============================================================================|
    |   0 MIG 1g.10gb        19    7/7         9.50       No     14     0     0   |
    |                                                             1     0     0   |
    +-----------------------------------------------------------------------------+
    |   0 MIG 1g.10gb+me     20    1/1         9.50       No     14     0     0   |
    |                                                             1     1     1   |
    +-----------------------------------------------------------------------------+
    |   0 MIG 2g.20gb        14    3/3         19.50      No     28     1     0   |
    |                                                             2     0     0   |
    +-----------------------------------------------------------------------------+
    |   0 MIG 3g.40gb         9    2/2         39.50      No     42     2     0   |
    |                                                             3     0     0   |
    +-----------------------------------------------------------------------------+
    |   0 MIG 4g.40gb         5    1/1         39.50      No     56     2     0   |
    |                                                             4     0     0   |
    +-----------------------------------------------------------------------------+
    |   0 MIG 7g.80gb         0    1/1         79.25      No     98     0     0   |
    |                                                             7     1     1   |
    +-----------------------------------------------------------------------------+
    Code Block. MIG GPU Instance Profile List
Note
A100 GPU Instance profile refers to the example of NVIDIA A100 MIG Profile.
MIG Device Naming
Figure. MIG Device Naming
Profile NameFraction of MemoryFraction of SMsHardware UnitsL2 Cache SizeNumber of Instances Available
MIG 1g.10gb1/81/70 NVDECs /0 JPEG /0 OFA1/87
MIG 1g.10gb+me1/81/71 NVDEC /1 JPEG /1 OFA1/81 (A single 1g profile can include media extensions)
MIG 2g.20gb2/82/71 NVDECs /0 JPEG /0 OFA2/83
MIG 3g.40gb4/83/72 NVDECs /0 JPEG /0 OFA4/82
MIG 4g.40gb4/84/72 NVDECs /0 JPEG /0 OFA4/81
MIG 7g.80gbFull7/75 NVDECs /1 JPEG /1 OFAFull1
Table. NVIDIA A100 MIG Profile
Note
MIG 1g.10gb+me profile can only be used when starting with the R470 driver.
  1. Check after creating the MIG GPU Instance.
    • GPU Instance creation

      Color mode
      $ nvidia-smi mig -i [GPU ID] -cgi [Profile ID]
      $ nvidia-smi mig -i [GPU ID] -cgi [Profile ID]
      Code Block. nvidia-smi command - GPU Instance creation
      Color mode
      $ nvidia-smi mig -i 0 -cgi 0
      Successfully created GPU instance ID 0 on GPU 0 using profile MIG 7g.80gb (ID 0)
      $ nvidia-smi mig -i 0 -cgi 0
      Successfully created GPU instance ID 0 on GPU 0 using profile MIG 7g.80gb (ID 0)
      Code block. nvidia-smi command - GPU Instance creation example

    • GPU Instance check

      Color mode
      $ nvidia-smi mig -i [GPU ID] -lgi
      $ nvidia-smi mig -i [GPU ID] -lgi
      Code Block. nvidia-smi Command - GPU Instance Check
      Color mode
      $ nvidia-smi mig -i 0 -lgi
      +--------------------------------------------------------+
      | GPU instances:                                         |
      | GPU   Name               Profile  Instance  Placement  |
      |                            ID       ID      Start:Size |
      |========================================================|
      |   0  MIG 7g.80gb            0        0         0:8     |
      +--------------------------------------------------------+
      $ nvidia-smi mig -i 0 -lgi
      +--------------------------------------------------------+
      | GPU instances:                                         |
      | GPU   Name               Profile  Instance  Placement  |
      |                            ID       ID      Start:Size |
      |========================================================|
      |   0  MIG 7g.80gb            0        0         0:8     |
      +--------------------------------------------------------+
      Code block. nvidia-smi command - GPU Instance check example

Compute Instance Creation

If you have created a GPU Instance, you can create a Compute Instance.

  1. Check the MIG Compute Instance profile that can be created.

    Color mode
    $ nvidia-smi mig -i [GPU ID] -gi [GPU Instance ID] -lcip
    $ nvidia-smi mig -i [GPU ID] -gi [GPU Instance ID] -lcip
    Code Block. nvidia-smi command - MIG Compute Instance profile check
    Color mode
    $ nvidia-smi mig -i 0 -gi 0 -lcip
    +---------------------------------------------------------------------------------+
    | Compute instance profiles:                                                      |
    | GPU     GPU     Name            Profile  Instances   Exclusive      Shared      |
    | GPU   Instance                     ID    Free/Total     SM       DEC  ENC  OFA  |
    |         ID                                                       CE   JPEG      |
    |=================================================================================|
    |   0      0      MIG 1c.7g.80gb     0      7/7           14       5    0    1    |
    |                                                                  7    1         |
    +---------------------------------------------------------------------------------+
    |   0      0      MIG 2c.7g.80gb     1      3/3           28       5    0    1    |
    |                                                                  7    1         |
    +---------------------------------------------------------------------------------+
    |   0      0      MIG 3c.7g.80gb     2      2/2           42       5    0    1    |
    |                                                                  7    1         |
    +---------------------------------------------------------------------------------+
    |   0      0      MIG 4c.7g.80gb     3      1/1           56       5    0    1    |
    |                                                                  7    1         |
    +---------------------------------------------------------------------------------+
    |   0      0      MIG 7g.80gb        4*     1/1           98       5    0    1    |
    |                                                                  7    1         |
    +---------------------------------------------------------------------------------+
    $ nvidia-smi mig -i 0 -gi 0 -lcip
    +---------------------------------------------------------------------------------+
    | Compute instance profiles:                                                      |
    | GPU     GPU     Name            Profile  Instances   Exclusive      Shared      |
    | GPU   Instance                     ID    Free/Total     SM       DEC  ENC  OFA  |
    |         ID                                                       CE   JPEG      |
    |=================================================================================|
    |   0      0      MIG 1c.7g.80gb     0      7/7           14       5    0    1    |
    |                                                                  7    1         |
    +---------------------------------------------------------------------------------+
    |   0      0      MIG 2c.7g.80gb     1      3/3           28       5    0    1    |
    |                                                                  7    1         |
    +---------------------------------------------------------------------------------+
    |   0      0      MIG 3c.7g.80gb     2      2/2           42       5    0    1    |
    |                                                                  7    1         |
    +---------------------------------------------------------------------------------+
    |   0      0      MIG 4c.7g.80gb     3      1/1           56       5    0    1    |
    |                                                                  7    1         |
    +---------------------------------------------------------------------------------+
    |   0      0      MIG 7g.80gb        4*     1/1           98       5    0    1    |
    |                                                                  7    1         |
    +---------------------------------------------------------------------------------+
    Code block. MIG Compute Instance profile list example

  2. Create and check the MIG Compute Instance.

    • MIG Compute Instance creation
      Color mode
      $ nvidia-smi mig -i [GPU ID] -gi [GPU Instance ID] -cci [Compute Profile ID]
      $ nvidia-smi mig -i [GPU ID] -gi [GPU Instance ID] -cci [Compute Profile ID]
      Code Block. nvidia-smi command - MIG Compute Instance creation
      Color mode
      $ nvidia-smi mig -i 0 -gi 0 -cci 4
      Successfully created compute instance ID 0 on GPU instance ID 0 using profile MIG 7g.80gb(ID 4)
      $ nvidia-smi mig -i 0 -gi 0 -cci 4
      Successfully created compute instance ID 0 on GPU instance ID 0 using profile MIG 7g.80gb(ID 4)
      Code block. nvidia-smi command - MIG Compute Instance creation example
    • MIG Compute Instance check
      Color mode
      $ nvidia-smi mig -i [GPU ID] -gi [GPU Instance ID] –lci
      $ nvidia-smi mig -i [GPU ID] -gi [GPU Instance ID] –lci
      Code block. nvidia-smi command - MIG Compute Instance check
      Color mode
      $ nvidia-smi mig -i 0 -gi 0 –lci
      +-----------------------------------------------------------------+
      | Compute instance profiles:                                      |
      | GPU     GPU     Name            Profile  Instances   Placement  |
      | GPU   Instance                     ID      ID        Start:Size |
      |         ID                                                      |
      |=================================================================|
      |   0      0      MIG 7g.80gb         4       0            0:7    |
      +-----------------------------------------------------------------+
      $ nvidia-smi mig -i 0 -gi 0 –lci
      +-----------------------------------------------------------------+
      | Compute instance profiles:                                      |
      | GPU     GPU     Name            Profile  Instances   Placement  |
      | GPU   Instance                     ID      ID        Start:Size |
      |         ID                                                      |
      |=================================================================|
      |   0      0      MIG 7g.80gb         4       0            0:7    |
      +-----------------------------------------------------------------+
      Code block. MIG Compute Instance confirmation example
      Color mode
      $ nvidia-smi –L
      GPU 0: NVIDIA A100-SXM-80GB (UUID: GPU-c956838f-494a-92b2-6818-56eb28fe25e0)
        MIG 7g.80gb     Device  0: (UUID: MIG-53e20040-758b-5ecb-948e-c626d03a9a32)
      $ nvidia-smi –L
      GPU 0: NVIDIA A100-SXM-80GB (UUID: GPU-c956838f-494a-92b2-6818-56eb28fe25e0)
        MIG 7g.80gb     Device  0: (UUID: MIG-53e20040-758b-5ecb-948e-c626d03a9a32)
      Code block. nvidia-smi command - Check GPU status (1)
      Color mode
      $ nvidia-smi
      Mon Sep 27 09:52:17 2021
      +-----------------------------------------------------------------------------+
      | NVIDIA-SMI 470.57.02    Driver Version: 470.57.02    CUDA Version: 11.4     |
      |-------------------------------+----------------------+----------------------|
      | GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
      | Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
      |                               |                      |               MIG M. |
      |===============================+======================+======================|
      |   0  NVDIA A100-SXM...  Off   | 00000000:05:00.0 Off |                   On |
      | N/A   32C   P0    49W / 400W  |      0MiB / 81251MiB |     N/A      Default |
      |                               |                      |              Enabled |
      +-------------------------------+----------------------+----------------------+
      
      +-----------------------------------------------------------------------------+
      | MIG devices:                                                                |
      +-----------------------------------------------------------------------------+
      |  GPU  GI  CI  MIG |        Memory-Usage |        Vol|        Shared         |
      |       ID  ID  Dev |          BAR1-Usage | SM     Unc| CE  ENC  DEC  OFA  JPG|
      |                   |                     |        ECC|                       |
      |=============================================================================|
      |   0    0   0    0 |     0MiB / 81251MiB | 98      0 |  7   0    5    1    1 |
      |                   |     1MiB / 13107... |           |                       |
      +-----------------------------------------------------------------------------+
      +-----------------------------------------------------------------------------+
      | Processes:                                                                  |
      |  GPU   GI   CI       PID   Type   Process name                   GPU Memory |
      |        ID   ID                                                   Usage      |
      |=============================================================================|
      | No running processes found                                                  |
      +-----------------------------------------------------------------------------+
      $ nvidia-smi
      Mon Sep 27 09:52:17 2021
      +-----------------------------------------------------------------------------+
      | NVIDIA-SMI 470.57.02    Driver Version: 470.57.02    CUDA Version: 11.4     |
      |-------------------------------+----------------------+----------------------|
      | GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
      | Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
      |                               |                      |               MIG M. |
      |===============================+======================+======================|
      |   0  NVDIA A100-SXM...  Off   | 00000000:05:00.0 Off |                   On |
      | N/A   32C   P0    49W / 400W  |      0MiB / 81251MiB |     N/A      Default |
      |                               |                      |              Enabled |
      +-------------------------------+----------------------+----------------------+
      
      +-----------------------------------------------------------------------------+
      | MIG devices:                                                                |
      +-----------------------------------------------------------------------------+
      |  GPU  GI  CI  MIG |        Memory-Usage |        Vol|        Shared         |
      |       ID  ID  Dev |          BAR1-Usage | SM     Unc| CE  ENC  DEC  OFA  JPG|
      |                   |                     |        ECC|                       |
      |=============================================================================|
      |   0    0   0    0 |     0MiB / 81251MiB | 98      0 |  7   0    5    1    1 |
      |                   |     1MiB / 13107... |           |                       |
      +-----------------------------------------------------------------------------+
      +-----------------------------------------------------------------------------+
      | Processes:                                                                  |
      |  GPU   GI   CI       PID   Type   Process name                   GPU Memory |
      |        ID   ID                                                   Usage      |
      |=============================================================================|
      | No running processes found                                                  |
      +-----------------------------------------------------------------------------+
      Code block. nvidia-smi command - Check GPU status (2)

Using MIG

  1. Use the MIG Instance to perform the Job.
    • Work execution example
      Color mode
      $ docker run --gpus '"device=[GPU ID]:[MIG ID]"' -rm nvcr.io/nvidia/cuda nvidia-smi
      $ docker run --gpus '"device=[GPU ID]:[MIG ID]"' -rm nvcr.io/nvidia/cuda nvidia-smi
      Code Block. Work Execution Example
      You can check an example of how to perform the task as follows.
      Color mode
      $ docker run --gpus '"device=0:0"' -rm -it --network=host --shm-size=1g --ipc=host -v /root/.ssh/:/root/.ssh
      
      ================
      == TensorFlow ==
      ================
      
      NVIDIA Release 21.08-tf1 (build 26012104)
      TensorFlow Version 1.15.5
      
      Container image Copyright (c) 2021, NVIDIA CORPORATION. All right reserved.
      ...
      
      # Python process execution
      root@d622a93c9281:/workspace# python /workspace/nvidia-examples/cnn/resnet.py --num_iter 100 
      ...
      PY 3.8.10 (default, Jun 2 2021, 10:49:15)
      [GCC 9.4.0]
      TF 1.15.5
      ...
      $ docker run --gpus '"device=0:0"' -rm -it --network=host --shm-size=1g --ipc=host -v /root/.ssh/:/root/.ssh
      
      ================
      == TensorFlow ==
      ================
      
      NVIDIA Release 21.08-tf1 (build 26012104)
      TensorFlow Version 1.15.5
      
      Container image Copyright (c) 2021, NVIDIA CORPORATION. All right reserved.
      ...
      
      # Python process execution
      root@d622a93c9281:/workspace# python /workspace/nvidia-examples/cnn/resnet.py --num_iter 100 
      ...
      PY 3.8.10 (default, Jun 2 2021, 10:49:15)
      [GCC 9.4.0]
      TF 1.15.5
      ...
      Code Block. Work Result
  2. Check the GPU usage rate. (Creating a JOB process)
    • You can see that when the Job is driven, the process is assigned to the MIG device and the usage rate increases.
      Color mode
      $ nvidia-smi mig -i [GPU ID] -gi [GPU Instance ID] -lcip
      $ nvidia-smi mig -i [GPU ID] -gi [GPU Instance ID] -lcip
      Code Block. nvidia-smi command - Check GPU usage
      You can check the GPU usage rate as follows.
      Color mode
      +-----------------------------------------------------------------------------+
      | MIG devices:                                                                |
      +-----------------------------------------------------------------------------+
      |  GPU  GI  CI  MIG |        Memory-Usage |        Vol|        Shared         |
      |       ID  ID  Dev |          BAR1-Usage | SM     Unc| CE  ENC  DEC  OFA  JPG|
      |                   |                     |        ECC|                       |
      |=============================================================================|
      |   0    0   0    0 | 66562MiB / 81251MiB | 98      0 |  7   0    5    1    1 |
      |                   |     5MiB / 13107... |           |                       |
      +-----------------------------------------------------------------------------+
      +-----------------------------------------------------------------------------+
      | Processes:                                                                  |
      |  GPU   GI   CI       PID   Type   Process name                   GPU Memory |
      |        ID   ID                                                   Usage      |
      |=============================================================================|
      |   0     0    0     17483      C   python                           66559MiB |
      +-----------------------------------------------------------------------------+
      +-----------------------------------------------------------------------------+
      | MIG devices:                                                                |
      +-----------------------------------------------------------------------------+
      |  GPU  GI  CI  MIG |        Memory-Usage |        Vol|        Shared         |
      |       ID  ID  Dev |          BAR1-Usage | SM     Unc| CE  ENC  DEC  OFA  JPG|
      |                   |                     |        ECC|                       |
      |=============================================================================|
      |   0    0   0    0 | 66562MiB / 81251MiB | 98      0 |  7   0    5    1    1 |
      |                   |     5MiB / 13107... |           |                       |
      +-----------------------------------------------------------------------------+
      +-----------------------------------------------------------------------------+
      | Processes:                                                                  |
      |  GPU   GI   CI       PID   Type   Process name                   GPU Memory |
      |        ID   ID                                                   Usage      |
      |=============================================================================|
      |   0     0    0     17483      C   python                           66559MiB |
      +-----------------------------------------------------------------------------+
      Code block. Example of checking GPU usage

MIG Instance deletion and release

To delete a MIG instance and release the MIG, follow these procedures.

MIG Removal Order
Compute Instance deletion → GPU Instance deletion → MIG feature disablement (deactivation)

Compute Instance deletion

  • Delete the Compute Instance.
    Color mode
    $ nvidia-smi mig -i [GPU ID] -gi [GPU Instance ID] –dci
    $ nvidia-smi mig -i [GPU ID] -gi [GPU Instance ID] -ci [Compute Instance] –dci
    $ nvidia-smi mig -i [GPU ID] -gi [GPU Instance ID] –dci
    $ nvidia-smi mig -i [GPU ID] -gi [GPU Instance ID] -ci [Compute Instance] –dci
    Code Block. nvidia-smi command - Compute Instance deletion
    Color mode
    $ nvidia-smi mig -i 0 -gi 0 –lci
    +-----------------------------------------------------------------+
    | Compute instance profiles:                                      |
    | GPU     GPU     Name            Profile  Instances   Placement  |
    | GPU   Instance                     ID      ID        Start:Size |
    |         ID                                                      |
    |=================================================================|
    |   0      0      MIG 7g.80gb         4       0            0:7    |
    +-----------------------------------------------------------------+
    $ nvidia-smi mig -i 0 -gi 0 –lci
    +-----------------------------------------------------------------+
    | Compute instance profiles:                                      |
    | GPU     GPU     Name            Profile  Instances   Placement  |
    | GPU   Instance                     ID      ID        Start:Size |
    |         ID                                                      |
    |=================================================================|
    |   0      0      MIG 7g.80gb         4       0            0:7    |
    +-----------------------------------------------------------------+
    Code Block. MIG Compute Instance Check Example
    Color mode
    $ nvidia-smi mig -i 0 -gi 0 –dci
    Successfully destroyed compute instance ID  0 from GPU instance ID  0
    $ nvidia-smi mig -i 0 -gi 0 –dci
    Successfully destroyed compute instance ID  0 from GPU instance ID  0
    Code Block. Compute Instance deletion example
    Color mode
    $ nvidia-smi mig -i 0 -gi 0 –lci
    No compute instances found: Not found
    $ nvidia-smi mig -i 0 -gi 0 –lci
    No compute instances found: Not found
    Code Block. Compute Instance deletion confirmation

GPU Instance deletion

  • Delete the GPU Instance.
    Color mode
    $ nvidia-smi mig -i [GPU ID] –dgi
    $ nvidia-smi mig -i [GPU ID] -gi [GPU Instance ID] –dgi
    $ nvidia-smi mig -i [GPU ID] –dgi
    $ nvidia-smi mig -i [GPU ID] -gi [GPU Instance ID] –dgi
    Code block. nvidia-smi command - GPU Instance deletion
    Color mode
    $ nvidia-smi mig -i 0 -lgi
    +--------------------------------------------------------+
    | GPU instances:                                         |
    | GPU   Name               Profile  Instance  Placement  |
    |                            ID       ID      Start:Size |
    |========================================================|
    |   0  MIG 7g.80gb            0        0         0:8     |
    +--------------------------------------------------------+
    $ nvidia-smi mig -i 0 -lgi
    +--------------------------------------------------------+
    | GPU instances:                                         |
    | GPU   Name               Profile  Instance  Placement  |
    |                            ID       ID      Start:Size |
    |========================================================|
    |   0  MIG 7g.80gb            0        0         0:8     |
    +--------------------------------------------------------+
    Code block. nvidia-smi command - GPU Instance check example
    Color mode
    $ nvidia-smi mig -i 0 -dgi
    Successfully destroyed GPU instance ID  0 from GPU  0
    $ nvidia-smi mig -i 0 -dgi
    Successfully destroyed GPU instance ID  0 from GPU  0
    Code block. nvidia-smi command - GPU Instance deletion example
    Color mode
    $ nvidia-smi mig -i 0 -lgi
    No GPU instances found: Not found
    $ nvidia-smi mig -i 0 -lgi
    No GPU instances found: Not found
    Code block. nvidia-smi command - GPU Instance deletion example

MIG Function Disablement (Deactivation)

  • Disable MIG and then reboot.
    Color mode
    $ nvidia-smi -mig 0
    Disabled MIG Mode for GPU 00000000:05:00.0
    
    All done.
    $ nvidia-smi -mig 0
    Disabled MIG Mode for GPU 00000000:05:00.0
    
    All done.
    Code Block. nvidia-smi command - MIG disable
    Color mode
    $ nvidia-smi
    Mon Sep 30 05:18:28 2021
    +-----------------------------------------------------------------------------+
    | NVIDIA-SMI 470.57.02    Driver Version: 470.57.02    CUDA Version: 11.4     |
    |-------------------------------+----------------------+----------------------|
    | GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
    | Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
    |                               |                      |               MIG M. |
    |===============================+======================+======================|
    |   0  NVDIA A100-SXM...  Off   | 00000000:05:00.0 Off |                    0 |
    | N/A   33C   P0    60W / 400W  |      0MiB / 81251MiB |      0%      Default |
    |                               |                      |             Disabled |
    +-------------------------------+----------------------+----------------------+
    +-----------------------------------------------------------------------------+
    | MIG devices:                                                                |
    +-----------------------------------------------------------------------------+
    |  GPU  GI  CI  MIG |        Memory-Usage |        Vol|        Shared         |
    |       ID  ID  Dev |          BAR1-Usage | SM     Unc| CE  ENC  DEC  OFA  JPG|
    |                   |                     |        ECC|                       |
    |=============================================================================|
    | No MIG devices found                                                        |
    +-----------------------------------------------------------------------------+
    +-----------------------------------------------------------------------------+
    | Processes:                                                                  |
    |  GPU   GI   CI       PID   Type   Process name                   GPU Memory |
    |        ID   ID                                                   Usage      |
    |=============================================================================|
    | No running processes found                                                  |
    +-----------------------------------------------------------------------------+
    $ nvidia-smi
    Mon Sep 30 05:18:28 2021
    +-----------------------------------------------------------------------------+
    | NVIDIA-SMI 470.57.02    Driver Version: 470.57.02    CUDA Version: 11.4     |
    |-------------------------------+----------------------+----------------------|
    | GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
    | Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
    |                               |                      |               MIG M. |
    |===============================+======================+======================|
    |   0  NVDIA A100-SXM...  Off   | 00000000:05:00.0 Off |                    0 |
    | N/A   33C   P0    60W / 400W  |      0MiB / 81251MiB |      0%      Default |
    |                               |                      |             Disabled |
    +-------------------------------+----------------------+----------------------+
    +-----------------------------------------------------------------------------+
    | MIG devices:                                                                |
    +-----------------------------------------------------------------------------+
    |  GPU  GI  CI  MIG |        Memory-Usage |        Vol|        Shared         |
    |       ID  ID  Dev |          BAR1-Usage | SM     Unc| CE  ENC  DEC  OFA  JPG|
    |                   |                     |        ECC|                       |
    |=============================================================================|
    | No MIG devices found                                                        |
    +-----------------------------------------------------------------------------+
    +-----------------------------------------------------------------------------+
    | Processes:                                                                  |
    |  GPU   GI   CI       PID   Type   Process name                   GPU Memory |
    |        ID   ID                                                   Usage      |
    |=============================================================================|
    | No running processes found                                                  |
    +-----------------------------------------------------------------------------+
    Code Block. nvidia-smi command - Check GPU status

2.3.2.3 - Using NVSwitch on GPU Server

After creating a GPU Server, you can enable the NVSwitch feature in the GPU Server’s VM (Guest OS) and quickly use P2P (GPU to GPU) communication between GPUs.

Exploring NVIDIA NVSwitch for Multi GPU

NVIDIA A100 GPU server is a multi-GPU based on the NVIDIA Ampere architecture, with 8 Ampere 80 GB GPUs installed on the baseboard. The GPUs installed on the baseboard are connected to 6 NVSwitches via NVLink ports. Communication between GPUs on the baseboard is done using the full 600 GBps bandwidth. For this reason, the 8 GPUs installed on the A100 GPU server can be connected and operated like one, thereby maximizing GPU-to-GPU usage.

  • NVLink(25 GBps) 12 Lane 8 GPU configuration
NVLink(25 GBps) 12 lanes 8 GPU configuration diagram
Figure. NVLink(25 GBps) 12 lanes 8 GPU configuration diagram
  • NVSwitch(600 GBps) 6 units 8 GPU configuration diagram
NVSwitch(600 GBps) 6 units 8 GPU configuration diagram
Figure. NVSwitch(600 GBps) 6 units 8 GPU configuration diagram

Create GPU NVSwitch

To use the GPU NVSwitch feature, create a GPU Server service on the Samsung Cloud Platform, create a VM Instance (GuestOS) with 8 A100 GPUs assigned, and activate the Fabricmanager.

주의
  • NVSwitch can only be activated and used for products with 8 A100 GPUs assigned to a single GPU server (g1v128a8 (vCPU 128 | Memory 1920G | A100(80GB)*8)).
  • Currently, GPU Server created with Windows OS does not support NVSwitch (Fabricmanager).

NVSwitch Installation and Operation Check (Fabric Manager Activation)

To operate NVSwitch, install Fabricmanager on the GPU Instance and follow the next procedure.

  1. Install NVIDIA GPU Driver (470.52.02 Version) on the GPU server.

    Color mode
    $ add-apt-repository ppa:graphics-drivers/ppa
    $ apt-get update
    $ apt-get install nvidia-driver-470-server
    $ add-apt-repository ppa:graphics-drivers/ppa
    $ apt-get update
    $ apt-get install nvidia-driver-470-server
    Code Block. NVIDIA GPU Driver Installation

  2. Install and run NVIDIA Fabric Manager (470 Version) on the GPU server (For NVSwitch).

    Color mode
    $ apt-get install cuda-drivers-fabricmanager-470
    $ systemctl enable nvidia-fabricmanager
    $ systemctl start nvidia-fabricmanager
    $ apt-get install cuda-drivers-fabricmanager-470
    $ systemctl enable nvidia-fabricmanager
    $ systemctl start nvidia-fabricmanager
    Code Block. NVIDIA Fabric Manager Installation and Operation

  3. Check the status of NVIDIA Fabric Manager running on the GPU server.

    • Normal operation indicates active (running)
      Color mode
      $ systemctl status nvidia-fabricmanager
      $ systemctl status nvidia-fabricmanager
      Code Block. Check NVIDIA Fabric Manager Operation Status
NVSwitch installation - Checking the operation status of Fabric Manager
Figure. NVSwitch installation - Checking the operation status of Fabric Manager
  1. Check the NVSwitch operation status on the GPU server.
    • Normal operation indicates NV12
      Color mode
      $ nvidia-smi topo --matrix
      $ nvidia-smi topo --matrix
      Code block. NVSwitch operation status check
NVSwitch Installation - Checking NVSwitch Operation Status
Figure. NVSwitch Installation - Checking NVSwitch Operation Status

2.3.2.4 - Keypair Management

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

Keypair Create

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

To create a keypair, follow these steps.

  1. All Services > Compute > GPU Server Click the menu. Navigate to the Service Home page of GPU Server.
  2. Click the Keypair menu on the Service Home page. It will go to the Keypair List page.
  3. Click the Keypair List page’s Create Keypair button. It navigates to the Create Keypair page.
    • Service Information Input Enter the required information in the area.
      Category
      Required or not
      Detailed description
      Keypair nameRequiredName of the Keypair to create
      • Enter within 255 characters using English letters, numbers, spaces, and special characters (-, _)
      Keypair typeRequiredssh
      Table. Keypair Service Information Input Items
    • Additional Information Input Enter or select the required information in the area.
      Category
      Required or not
      Detailed description
      TagSelectAdd 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 items
      Caution
      • After creation is complete, you can download the Key only once for the first time. Since reissuance is not possible, make sure it has been downloaded.
      • Save the downloaded Private Key in a safe place.
  4. Check the input information and click the Complete button.
    • When creation is complete, check the created resource on the Keypair List page.

Keypair Check detailed information

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

To view detailed information about the Keypair, follow the steps below.

  1. All Services > Compute > GPU Server Click the menu. Navigate to the GPU Server’s Service Home page.
  2. Service Home page, click the Keypair menu. Navigate to the Keypair list page.
  3. Keypair List Click the resource to view detailed information on the page. Go to the Keypair Detail page.
    • Keypair Details page displays status information and additional feature information, and consists of Details, Tags, Activity History tabs.

Detailed Information

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

CategoryDetailed description
ServiceService Name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In Keypair, it means Keypair SRN
Resource NameKeypair Name
Resource IDKeypair’s unique resource ID
CreatorUser who created the Keypair
Creation timeTime when the keypair was created
EditorUser who modified the Keypair information
Modification Date/TimeTimestamp of Keypair information modification
Keypair nameKeypair name
FingerprintUnique value for identifying a Key
User IDUser ID of the user who created the Keypair
Public KeyPublic Key Information
Table. Keypair detailed information tab items

Tag

Keypair list page allows you to view the tag information of selected resources, and you can add, modify, or delete them.

CategoryDetailed description
Tag ListTag List
  • Tag’s Key, Value information can be checked
  • Up to 50 tags can be added per resource
  • When entering a tag, search and select from the list of previously created Keys and Values
Table. Keypair Tag Tab Items

Work History

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

CategoryDetailed description
Work History ListResource Change History
  • Task date/time, Resource ID, Resource name, Task details, Event topic, Task result, Operator information verification
Table. Keypair operation history tab detailed information items

Keypair Resource Management

Describes the control and management functions of the keypair.

Get public key

To retrieve the public key, follow the steps below.

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

  2. Service Home page, click the Keypair menu. Navigate to the Keypair list page.

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

    • Required Information Input Enter or select the required information in the area.
      Category
      Required
      Detailed description
      Keypair namerequiredName of the Keypair to create
      Keypair typerequiredssh
      Public KeyRequiredEnter Public Key
      • Load File: Attach File button to select and attach the public key file
        • Only files with the following extension (.pem) can be attached
      • Enter Public Key: Paste the copied public key value
        • Public key value can be copied from the Keypair Details page
      Table. Required input items for fetching public key
  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, once a Keypair is deleted it cannot be recovered, so please review the impact thoroughly in advance before proceeding with deletion.

Caution
Please be careful as data cannot be recovered after deleting the service.

To delete a keypair, follow the steps below.

  1. All Services > Compute > GPU Server Click the menu. Navigate to the GPU Server’s Service Home page.
  2. Click the Keypair menu on the Service Home page. It moves 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.
  1. After deletion is complete, check on the Keypair List page whether the resource has been deleted.

2.3.2.5 - ServiceWatch Agent Installation

Users can install ServiceWatch Agent on GPU Server to collect custom metrics and logs.

Reference
Custom metrics/log collection through ServiceWatch Agent is currently available only in Samsung Cloud Platform For Enterprise. It will be available in other offerings in the future.
Caution
Metric collection through ServiceWatch Agent is classified as custom metrics, and unlike basic metrics collected from each service, fees are charged. Therefore, it is recommended to remove or disable unnecessary metric collection settings.

ServiceWatch Agent

There are two main types of Agents that must be installed to collect ServiceWatch custom metrics and logs on GPU Server. Prometheus Exporter and Open Telemetry Collector.

CategoryDetailed Description
Prometheus ExporterProvides metrics of specific applications or services in a format that Prometheus can scrape
  • For collecting server OS metrics, you can use Node Exporter for Linux servers and Windows Exporter for Windows servers depending on the OS type.
Open Telemetry CollectorA centralized collector that collects telemetry data such as metrics and logs from distributed systems, processes (filtering, sampling, etc.), and sends them to multiple backends (e.g., Prometheus, Jaeger, Elasticsearch, etc.)
  • Sends data to ServiceWatch Gateway to enable ServiceWatch to collect metric and log data.
Table. Description of Prometheus Exporter and Open Telemetry Collector
Caution

If Kubernetes Engine is configured on GPU Server, please check GPU metrics through the metrics provided by Kubernetes Engine.

  • If you install DCGM Exporter on a GPU Server with Kubernetes Engine configured, it may not work properly.

Prerequisites for Using ServiceWatch Agent

Step 1. Check NVIDIA Driver installation

Install Prometheus Exporter for GPU Metrics (for Ubuntu)

Install the Prometheus Exporter to collect GPU Server metrics in the following order.

Check NVDIA Driver Installation

  • Check the installed NVDIA Driver.
    Color mode
    nvidia-smi --query-gpu driver_version --format csv
    nvidia-smi --query-gpu driver_version --format csv
    Code block. Check NVDIA Driver version command
    Color mode
    driver_version
    535.183.06
    ...
    535.183.06
    driver_version
    535.183.06
    ...
    535.183.06
    Code block. Check NVDIA Driver version example

Install NVSwitch Configuration and Query (NSCQ) Library

Reference
NVSwitch Configuration and Query (NSCQ) Library is required for Hopper or earlier Generation GPUs.
Notice
The installation commands below are possible in an environment where internet is available. If internet is not available, you must download libnvdia-nscq from https://developer.download.nvidia.com/compute/cuda/repos/ and upload it.
  1. Install cuda-keyring.

    Color mode
    wget https://developer.download.nvidia.com/compute/cuda/repos/<distro>/<arch>/cuda-keyring_1.1-1_all.deb
    wget https://developer.download.nvidia.com/compute/cuda/repos/<distro>/<arch>/cuda-keyring_1.1-1_all.deb
    Code block. NSCQ library download command
    Color mode
    sudo dpkg -i cuda-keyring_1.1-1_all.deb
    apt update
    sudo dpkg -i cuda-keyring_1.1-1_all.deb
    apt update
    Code block. NSCQ library installation command
    Color mode
    nvidia-smi --query-gpu driver_version --format csv
    nvidia-smi --query-gpu driver_version --format csv
    Code block. Check NVDIA Driver version command
    Color mode
    driver_version
    535.183.06
    ...
    
    535.183.06
    driver_version
    535.183.06
    ...
    
    535.183.06
    Code block. Check NVDIA Driver version example

  2. Install libnvidia-nscq.

    Color mode
    apt-cache policy libnvidia-nscq-535
    apt-cache policy libnvidia-nscq-535
    Code block. NSCQ library apt-cache command
    Color mode
    libnvidia-nscq-535:
      Installed: (none)
      Candidate: 535.247.01-1
      Version table:
         535.247.01-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
     ...
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         535.216.01-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         535.183.06-1 600  # Install the version that matches the Driver
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         535.183.01-1 600
     ...
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         535.54.03-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
    libnvidia-nscq-535:
      Installed: (none)
      Candidate: 535.247.01-1
      Version table:
         535.247.01-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
     ...
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         535.216.01-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         535.183.06-1 600  # Install the version that matches the Driver
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         535.183.01-1 600
     ...
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         535.54.03-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
    Code block. NSCQ library apt-cache command result
    Color mode
    apt install libnvidia-nscq-535=535.183.06-1
    apt install libnvidia-nscq-535=535.183.06-1
    Code block. NSCQ library installation command
    Notice

    You must install the same version as the NVDIA Driver version.

    • Example) driver version: 535.183.06, libnvdia-nscq version: 535.183.06-1

Install NVSwitch Device Monitoring API(NVSDM) Library

Reference
NVSDM Library installation is required for Blackwell and later GPU Architectures. NVSDM Library is not provided for NVDIA Driver version 560 or lower.
  • Install NVSDM library.
    Color mode
    apt-cache policy libnvsdm
    apt-cache policy libnvsdm
    Code block. NVSDM library apt-cache command
    Color mode
    libnvsdm:
      Installed: (none)
      Candidate: 580.105.08-1
      Version table:
         580.105.08-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         580.95.05-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         580.82.07-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         580.65.06-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
    libnvsdm:
      Installed: (none)
      Candidate: 580.105.08-1
      Version table:
         580.105.08-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         580.95.05-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         580.82.07-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         580.65.06-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
    Code block. NVSDM library apt-cache command result
    Color mode
    apt install libnvsdm=580.105.08-1
    apt install libnvsdm=580.105.08-1
    Code block. NVSDM library installation

Install NVIDIA DCGM (for Ubuntu)

Install DCGM Exporter in the following order.

  1. Install datacenter-gpu-manager-exporter
  2. Enable and start DCGM service
  3. For metrics that can be collected with GPU DCGM Exporter and configuration methods, refer to DCGM Exporter Metrics.

Install DCGM(datacenter-gpu-manager)

Refers to a specific version of NVIDIA’s Data Center GPU Manager (DCGM) tool, which is a package for managing and monitoring NVIDIA data center GPUs. In particular, cuda12 indicates that this management tool is installed for CUDA 12 version, and datacenter-gpu-manager-4 means DCGM version 4.x. This tool provides various functions including GPU status monitoring, diagnostics, alert systems, and power/clock management.

  1. Check CUDA version.
    Color mode
    nvidia-smi | grep CUDA
    nvidia-smi | grep CUDA
    Code block. Check CUDA version
    Color mode
    | NVIDIA-SMI 535.183.06             Driver Version: 535.183.06     CUDA Version: 12.2     |
    | NVIDIA-SMI 535.183.06             Driver Version: 535.183.06     CUDA Version: 12.2     |
    Code block. Check CUDA version result example
    Color mode
    CUDA_VERSION=12
    CUDA_VERSION=12
    Code block. Set CUDA version command
  2. Install datacenter-gpu-manager-cuda.
    Color mode
    apt install datacenter-gpu-manager-4-cuda${CUDA_VERSION}
    apt install datacenter-gpu-manager-4-cuda${CUDA_VERSION}
    Code block. datacenter-gpu-manager-cuda installation command

Install datacenter-gpu-manager-exporter

This is a tool that collects various GPU metrics such as GPU usage, memory usage, temperature, and power consumption based on NVIDIA Data Center GPU Manager (DCGM) and exposes them for use in monitoring systems like Prometheus.

  1. Install datacenter-gpu-manager-exporter.
    Color mode
    apt install datacenter-gpu-manager-exporter
    apt install datacenter-gpu-manager-exporter
    Code block. datacenter-gpu-manager-exporter installation command
  2. Check DCGM Exporter configuration file.
    Color mode
    cat /usr/lib/systemd/system/nvidia-dcgm-exporter.service | grep ExecStart
    cat /usr/lib/systemd/system/nvidia-dcgm-exporter.service | grep ExecStart
    Code block. Check datacenter-gpu-manager-exporter configuration file command
    Color mode
    ExecStart=/usr/bin/dcgm-exporter -f /etc/dcgm-exporter/default-counters.csv
    ExecStart=/usr/bin/dcgm-exporter -f /etc/dcgm-exporter/default-counters.csv
    Code block. Check datacenter-gpu-manager-exporter configuration file result example
  3. Check the configuration provided at DCGM Exporter installation, remove # for necessary metrics, and add # for unnecessary metrics.
    Color mode
    vi /etc/dcgm-exporter/default-counters.csv
    ## Example ##
    ...
    DCGM_FI_PROF_PIPE_TENSOR_ACTIVE, gauge, Ratio of cycles the tensor (HMMA) pipe is active.
    DCGM_FI_PROF_DRAM_ACTIVE,        gauge, Ratio of cycles the device memory interface is active sending or receiving data.
    # DCGM_FI_PROF_PIPE_FP64_ACTIVE,   gauge, Ratio of cycles the fp64 pipes are active.
    # DCGM_FI_PROF_PIPE_FP32_ACTIVE,   gauge, Ratio of cycles the fp32 pipes are active.
    ...
    vi /etc/dcgm-exporter/default-counters.csv
    ## Example ##
    ...
    DCGM_FI_PROF_PIPE_TENSOR_ACTIVE, gauge, Ratio of cycles the tensor (HMMA) pipe is active.
    DCGM_FI_PROF_DRAM_ACTIVE,        gauge, Ratio of cycles the device memory interface is active sending or receiving data.
    # DCGM_FI_PROF_PIPE_FP64_ACTIVE,   gauge, Ratio of cycles the fp64 pipes are active.
    # DCGM_FI_PROF_PIPE_FP32_ACTIVE,   gauge, Ratio of cycles the fp32 pipes are active.
    ...
    Code block. datacenter-gpu-manager-exporter metric configuration example
    Caution
    Metric collection through ServiceWatch Agent is classified as custom metrics, and unlike basic metrics collected from each service, fees are charged. Therefore, unnecessary metric collection should be removed or disabled to avoid excessive charges.

Enable and Start DCGM Service

  1. Enable and start nvdia-dcgm service.

    Color mode
    systemctl enable --now nvidia-dcgm
    systemctl enable --now nvidia-dcgm
    Code block. Enable and start nvdia-dcgm service command

  2. Enable and start nvdia-dcgm-exporter service.

    Color mode
    systemctl enable --now nvidia-dcgm-exporter
    systemctl enable --now nvidia-dcgm-exporter
    Code block. Enable and start nvdia-dcgm-exporter service command

Notice
If you have completed DCGM Exporter configuration, you must install the Open Telemetry Collector provided by ServiceWatch to complete ServiceWatch Agent configuration.
For details, refer to ServiceWatch > Use ServiceWatch Agent.

Install Prometheus Exporter for GPU Metrics (for RHEL)

Install ServiceWatch Agent to collect GPU Server metrics in the following order.

Check NVDIA Driver Installation (for RHEL)

  1. Check the installed NVDIA Driver.
    Color mode
    nvidia-smi --query-gpu driver_version --format csv
    nvidia-smi --query-gpu driver_version --format csv
    Code block. Check NVDIA Driver version command
    Color mode
    driver_version
    535.183.06
    ...
    
    535.183.06
    driver_version
    535.183.06
    ...
    
    535.183.06
    Code block. Check NVDIA Driver version example

Install NVSwitch Configuration and Query (NSCQ) Library (for RHEL)

Reference

NVSwitch Configuration and Query (NSCQ) Library is required for Hopper or earlier Generation GPUs.

  • For RHEL, check if libnvdia-nscq is installed and then install it.
Notice
The installation commands below are possible in an environment where internet is available. If internet is not available, you must download libnvdia-nscq from https://developer.download.nvidia.com/compute/cuda/repos/ and upload it.
  1. Check libnvdia-nscq package.

    Color mode
    rpm -qa | grep libnvidia-nscq libnvidia-nscq-535-535.183.06-1.x86_64
    rpm -qa | grep libnvidia-nscq libnvidia-nscq-535-535.183.06-1.x86_64
    Code block. Check NSCQ library package

  2. Add CUDA Repository to DNF.

    Color mode
    dnf config-manager --add-repo https://developer.download.nvidia.com/compute/cuda/repos/rhel8/x86_64/cuda-rhel8.repo
    dnf config-manager --add-repo https://developer.download.nvidia.com/compute/cuda/repos/rhel8/x86_64/cuda-rhel8.repo
    Code block. Add DNF Repository

  3. Reset NVDIA Driver status

    Color mode
    dnf module reset nvidia-driver
    dnf module reset nvidia-driver
    Code block. Reset NVIDIA Driver DNF module status
    Color mode
    Updating Subscription Management repositories.
    Last metadata expiration check: 0:03:15 ago on Wed 19 Nov 2025 01:23:48 AM EST.
    Dependencies resolved.
    =============================================
    Package Architecture Version Repository Size
    =============================================
    Disabling module profiles:
    nvidia-driver/default
    nvidia-driver/fm
    Resetting modules:
    nvidia-driver
    
    Transaction Summary
    =============================================
    
    Is this ok [y/N]: y
    Updating Subscription Management repositories.
    Last metadata expiration check: 0:03:15 ago on Wed 19 Nov 2025 01:23:48 AM EST.
    Dependencies resolved.
    =============================================
    Package Architecture Version Repository Size
    =============================================
    Disabling module profiles:
    nvidia-driver/default
    nvidia-driver/fm
    Resetting modules:
    nvidia-driver
    
    Transaction Summary
    =============================================
    
    Is this ok [y/N]: y
    Code block. Reset NVIDIA Driver DNF module status result example

  4. Enable NVDIA Driver module.

    Color mode
    dnf module enable nvidia-driver:535-open
    dnf module enable nvidia-driver:535-open
    Code block. Enable NVDIA Driver module
    Color mode
    Updating Subscription Management repositories.
    Last metadata expiration check: 0:04:22 ago on Wed 19 Nov 2025 01:23:48 AM EST.
    Dependencies resolved.
    =============================================
    Package Architecture Version Repository Size
    =============================================
    Enabling module streams:
    nvidia-driver 535-open
    
    Transaction Summary
    =============================================
    
    Is this ok [y/N]: y
    Updating Subscription Management repositories.
    Last metadata expiration check: 0:04:22 ago on Wed 19 Nov 2025 01:23:48 AM EST.
    Dependencies resolved.
    =============================================
    Package Architecture Version Repository Size
    =============================================
    Enabling module streams:
    nvidia-driver 535-open
    
    Transaction Summary
    =============================================
    
    Is this ok [y/N]: y
    Code block. Enable NVDIA Driver module result example

  5. Check libnvdia-nscq module list.

    Color mode
    dnf list libnvidia-nscq-535 --showduplicates
    dnf list libnvidia-nscq-535 --showduplicates
    Code block. Check libnvdia-nscq module list

  6. Install libnvdia-nscq.

    Color mode
    dnf install libnvidia-nscq-535-535.183.06-1
    dnf install libnvidia-nscq-535-535.183.06-1
    Code block. libnvdia-nscq installation command

Install NVSwitch Device Monitoring API(NVSDM) Library (for RHEL)

Reference
NVSDM Library installation is required for Blackwell and later GPU Architectures. NVSDM Library is not provided for NVDIA Driver version 560 or lower.
  1. Check NVSDM library module list.

    Color mode
    dnf list libnvsdm --showduplicates
    dnf list libnvsdm --showduplicates
    Code block. Check NVSDM library module list
    Color mode
    libnvsdm:
      Installed: (none)
      Candidate: 580.105.08-1
      Version table:
         580.105.08-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         580.95.05-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         580.82.07-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         580.65.06-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
    libnvsdm:
      Installed: (none)
      Candidate: 580.105.08-1
      Version table:
         580.105.08-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         580.95.05-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         580.82.07-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
         580.65.06-1 600
            600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64  Packages
    Code block. Check NVSDM library module list result example

  2. Install libnvsdm.

    Color mode
    dnf install libnvsdm-580.105.08-1
    dnf install libnvsdm-580.105.08-1
    Code block. NVSDM library installation
    Color mode
    Updating Subscription Management repositories.
    Last metadata expiration check: 0:08:18 ago on Wed 19 Nov 2025 01:05:28 AM EST.
    Dependencies resolved.
    ========================================================================
    Package Architecture Version Repository Size
    ========================================================================
    Installing:
    libnvsdm x86_64 580.105.08-1 cuda-rhel8-x86_64 675 k
    Installing dependencies:
    infiniband-diags x86_64 48.0-1.el8 rhel-8-for-x86_64-baseos-rpms 323 k
    libibumad x86_64 48.0-1.el8 rhel-8-for-x86_64-baseos-rpms 34 k
    
    Transaction Summary
    ========================================================================
    Install 3 Packages
    
    Total download size: 1.0 M
    Installed size: 3.2 M
    Is this ok [y/N]: y
    Updating Subscription Management repositories.
    Last metadata expiration check: 0:08:18 ago on Wed 19 Nov 2025 01:05:28 AM EST.
    Dependencies resolved.
    ========================================================================
    Package Architecture Version Repository Size
    ========================================================================
    Installing:
    libnvsdm x86_64 580.105.08-1 cuda-rhel8-x86_64 675 k
    Installing dependencies:
    infiniband-diags x86_64 48.0-1.el8 rhel-8-for-x86_64-baseos-rpms 323 k
    libibumad x86_64 48.0-1.el8 rhel-8-for-x86_64-baseos-rpms 34 k
    
    Transaction Summary
    ========================================================================
    Install 3 Packages
    
    Total download size: 1.0 M
    Installed size: 3.2 M
    Is this ok [y/N]: y
    Code block. NVSDM library installation command result example

Install NVIDIA DCGM (for RHEL)

Install Node Exporter in the following order.

  1. Install datacenter-gpu-manager-exporter
  2. Enable and start DCGM service
  3. For metrics that can be collected with GPU DCGM Exporter and configuration methods, refer to DCGM Exporter Metrics.

Install DCGM(datacenter-gpu-manager) (for RHEL)

Refers to a specific version of NVIDIA’s Data Center GPU Manager (DCGM) tool, which is a package for managing and monitoring NVIDIA data center GPUs. In particular, cuda12 indicates that this management tool is installed for CUDA 12 version, and datacenter-gpu-manager-4 means DCGM version 4.x. This tool provides various functions including GPU status monitoring, diagnostics, alert systems, and power/clock management.

  1. Add CUDA Repository to DNF.
    Color mode
    dnf config-manager --add-repo https://developer.download.nvidia.com/compute/cuda/repos/rhel8/x86_64/cuda-rhel8.repo
    dnf config-manager --add-repo https://developer.download.nvidia.com/compute/cuda/repos/rhel8/x86_64/cuda-rhel8.repo
    Code block. Add DNF Repository
  2. Check CUDA version.
    Color mode
    nvidia-smi | grep CUDA
    nvidia-smi | grep CUDA
    Code block. Check CUDA version
    Color mode
    | NVIDIA-SMI 535.183.06             Driver Version: 535.183.06     CUDA Version: 12.2     |
    | NVIDIA-SMI 535.183.06             Driver Version: 535.183.06     CUDA Version: 12.2     |
    Code block. Check CUDA version result example
    Color mode
    CUDA_VERSION=12
    CUDA_VERSION=12
    Code block. Set CUDA version command
  3. Check datacenter-gpu-manager-cuda module list.
    Color mode
    dnf list datacenter-gpu-manager-4-cuda${CUDA_VERSION} --showduplicates
    dnf list datacenter-gpu-manager-4-cuda${CUDA_VERSION} --showduplicates
    Code block. Check datacenter-gpu-manager-cuda module list
    Color mode
    Updating Subscription Management repositories.
    Unable to read consumer identity
    
    This system is not registered with an entitlement server. You can use subscription-manager to register.
    
    Last metadata expiration check: 0:00:34 ago on Wed 19 Nov 2025 12:26:56 AM EST.
    Available Packages
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.0.0-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.1.0-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.1.1-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.2.0-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.2.2-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.2.3-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.2.3-2    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.3.0-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.3.1-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.4.0-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.4.1-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.4.2-1    cuda-rhel8-x86_64
    Updating Subscription Management repositories.
    Unable to read consumer identity
    
    This system is not registered with an entitlement server. You can use subscription-manager to register.
    
    Last metadata expiration check: 0:00:34 ago on Wed 19 Nov 2025 12:26:56 AM EST.
    Available Packages
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.0.0-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.1.0-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.1.1-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.2.0-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.2.2-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.2.3-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.2.3-2    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.3.0-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.3.1-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.4.0-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.4.1-1    cuda-rhel8-x86_64
    datacenter-gpu-manager-4-cuda12.x86_64   1:4.4.2-1    cuda-rhel8-x86_64
    Code block. Check datacenter-gpu-manager-cuda module list result example
  4. Install datacenter-gpu-manager-cuda.
    Color mode
    dnf install datacenter-gpu-manager-4-cuda${CUDA_VERSION}
    dnf install datacenter-gpu-manager-4-cuda${CUDA_VERSION}
    Code block. datacenter-gpu-manager-cuda installation
    Color mode
    Updating Subscription Management repositories.
    Unable to read consumer identity
    
    This system is not registered with an entitlement server. You can use subscription-manager to register.
    
    Last metadata expiration check: 0:07:12 ago on Wed 19 Nov 2025 12:26:56 AM EST.
    Dependencies resolved.
    ===================================================================================================
     Package                                       Architecture   Version     Repository          Size
    ===================================================================================================
    Installing:
     datacenter-gpu-manager-4-cuda12               x86_64         1:4.4.2-1   cuda-rhel8-x86_64   554 M
    Installing dependencies:
     datacenter-gpu-manager-4-core                 x86_64         1:4.4.2-1   cuda-rhel8-x86_64   9.9 M
    Installing weak dependencies:
     datacenter-gpu-manager-4-proprietary          x86_64         1:4.4.2-1   cuda-rhel8-x86_64   5.3 M
     datacenter-gpu-manager-4-proprietary-cuda12   x86_64         1:4.4.2-1   cuda-rhel8-x86_64   289 M
    
    Transaction Summary
    ====================================================================================================
    Install  4 Packages
    ...
    Is this ok [y/N]: y
    Updating Subscription Management repositories.
    Unable to read consumer identity
    
    This system is not registered with an entitlement server. You can use subscription-manager to register.
    
    Last metadata expiration check: 0:07:12 ago on Wed 19 Nov 2025 12:26:56 AM EST.
    Dependencies resolved.
    ===================================================================================================
     Package                                       Architecture   Version     Repository          Size
    ===================================================================================================
    Installing:
     datacenter-gpu-manager-4-cuda12               x86_64         1:4.4.2-1   cuda-rhel8-x86_64   554 M
    Installing dependencies:
     datacenter-gpu-manager-4-core                 x86_64         1:4.4.2-1   cuda-rhel8-x86_64   9.9 M
    Installing weak dependencies:
     datacenter-gpu-manager-4-proprietary          x86_64         1:4.4.2-1   cuda-rhel8-x86_64   5.3 M
     datacenter-gpu-manager-4-proprietary-cuda12   x86_64         1:4.4.2-1   cuda-rhel8-x86_64   289 M
    
    Transaction Summary
    ====================================================================================================
    Install  4 Packages
    ...
    Is this ok [y/N]: y
    Code block. datacenter-gpu-manager-cuda installation result example

Install datacenter-gpu-manager-exporter (for RHEL)

This is a tool that collects various GPU metrics such as GPU usage, memory usage, temperature, and power consumption based on NVIDIA Data Center GPU Manager (DCGM) and exposes them for use in monitoring systems like Prometheus.

  1. Add CUDA Repository to DNF. (If you have already run this command, proceed to the next step.)

    Color mode
    dnf config-manager --add-repo https://developer.download.nvidia.com/compute/cuda/repos/rhel8/x86_64/cuda-rhel8.repo
    dnf config-manager --add-repo https://developer.download.nvidia.com/compute/cuda/repos/rhel8/x86_64/cuda-rhel8.repo
    Code block. Add DNF Repository

  2. Check CUDA version. (If you have already run this command, proceed to the next step.)

    Color mode
    nvidia-smi | grep CUDA
    nvidia-smi | grep CUDA
    Code block. Check CUDA version
    Color mode
    | NVIDIA-SMI 535.183.06             Driver Version: 535.183.06     CUDA Version: 12.2     |
    | NVIDIA-SMI 535.183.06             Driver Version: 535.183.06     CUDA Version: 12.2     |
    Code block. Check CUDA version result example
    Color mode
    CUDA_VERSION=12
    CUDA_VERSION=12
    Code block. Set CUDA version command

  3. Check datacenter-gpu-manager-exporter module list.

    Color mode
    dnf list datacenter-gpu-manager-exporter --showduplicates
    dnf list datacenter-gpu-manager-exporter --showduplicates
    Code block. Check datacenter-gpu-manager-exporter module list
    Color mode
    Updating Subscription Management repositories.
    Unable to read consumer identity
    
    This system is not registered with an entitlement server. You can use subscription-manager to register.
    
    Last metadata expiration check: 0:02:11 ago on Wed 19 Nov 2025 12:26:56 AM EST.
    Available Packages
    datacenter-gpu-manager-exporter.x86_64   4.0.1-1   cuda-rhel8-x86_64
    datacenter-gpu-manager-exporter.x86_64   4.1.0-1   cuda-rhel8-x86_64
    datacenter-gpu-manager-exporter.x86_64   4.1.1-1   cuda-rhel8-x86_64
    datacenter-gpu-manager-exporter.x86_64   4.1.3-1   cuda-rhel8-x86_64
    datacenter-gpu-manager-exporter.x86_64   4.5.0-1   cuda-rhel8-x86_64
    datacenter-gpu-manager-exporter.x86_64   4.5.1-1   cuda-rhel8-x86_64
    datacenter-gpu-manager-exporter.x86_64   4.5.2-1   cuda-rhel8-x86_64
    datacenter-gpu-manager-exporter.x86_64   4.6.0-1   cuda-rhel8-x86_64
    Updating Subscription Management repositories.
    Unable to read consumer identity
    
    This system is not registered with an entitlement server. You can use subscription-manager to register.
    
    Last metadata expiration check: 0:02:11 ago on Wed 19 Nov 2025 12:26:56 AM EST.
    Available Packages
    datacenter-gpu-manager-exporter.x86_64   4.0.1-1   cuda-rhel8-x86_64
    datacenter-gpu-manager-exporter.x86_64   4.1.0-1   cuda-rhel8-x86_64
    datacenter-gpu-manager-exporter.x86_64   4.1.1-1   cuda-rhel8-x86_64
    datacenter-gpu-manager-exporter.x86_64   4.1.3-1   cuda-rhel8-x86_64
    datacenter-gpu-manager-exporter.x86_64   4.5.0-1   cuda-rhel8-x86_64
    datacenter-gpu-manager-exporter.x86_64   4.5.1-1   cuda-rhel8-x86_64
    datacenter-gpu-manager-exporter.x86_64   4.5.2-1   cuda-rhel8-x86_64
    datacenter-gpu-manager-exporter.x86_64   4.6.0-1   cuda-rhel8-x86_64
    Code block. Check datacenter-gpu-manager-exporter module list result example

  4. Install datacenter-gpu-manager-cuda. dcgm-exporter 4.5.X requires glibc 2.34 or higher, but RHEL9 provides glibc 2.34, so specify version 4.1.3-1 to install.

    Color mode
    dnf install datacenter-gpu-manager-exporter-4.1.3-1
    dnf install datacenter-gpu-manager-exporter-4.1.3-1
    Code block. datacenter-gpu-manager-cuda installation
    Color mode
    Updating Subscription Management repositories.
    Unable to read consumer identity
    
    This system is not registered with an entitlement server. You can use subscription-manager to register.
    
    Last metadata expiration check: 0:07:12 ago on Wed 19 Nov 2025 12:26:56 AM EST.
    Dependencies resolved.
    ====================================================================================================
     Package                                       Architecture   Version     Repository          Size
    ====================================================================================================
    Installing:
     datacenter-gpu-manager-exporter               x86_64         4.1.3-1     cuda-rhel8-x86_64   26 M
    
    ...
    Is this ok [y/N]: y
    Updating Subscription Management repositories.
    Unable to read consumer identity
    
    This system is not registered with an entitlement server. You can use subscription-manager to register.
    
    Last metadata expiration check: 0:07:12 ago on Wed 19 Nov 2025 12:26:56 AM EST.
    Dependencies resolved.
    ====================================================================================================
     Package                                       Architecture   Version     Repository          Size
    ====================================================================================================
    Installing:
     datacenter-gpu-manager-exporter               x86_64         4.1.3-1     cuda-rhel8-x86_64   26 M
    
    ...
    Is this ok [y/N]: y
    Code block. datacenter-gpu-manager-cuda installation result example
    Color mode
    cat /usr/lib/systemd/system/nvidia-dcgm-exporter.service | grep ExecStart
    cat /usr/lib/systemd/system/nvidia-dcgm-exporter.service | grep ExecStart
    Code block. datacenter-gpu-manager-exporter configuration file
    Color mode
    ExecStart=/usr/bin/dcgm-exporter -f /etc/dcgm-exporter/default-counters.csv
    ExecStart=/usr/bin/dcgm-exporter -f /etc/dcgm-exporter/default-counters.csv
    Code block. Check datacenter-gpu-manager-exporter configuration file result example

  5. Check the configuration provided at DCGM Exporter installation, remove # for necessary metrics, and add # for unnecessary metrics.

    Color mode
    vi /etc/dcgm-exporter/default-counters.csv
    ## Example ##
    ...
    DCGM_FI_PROF_PIPE_TENSOR_ACTIVE, gauge, Ratio of cycles the tensor (HMMA) pipe is active.
    DCGM_FI_PROF_DRAM_ACTIVE,        gauge, Ratio of cycles the device memory interface is active sending or receiving data.
    # DCGM_FI_PROF_PIPE_FP64_ACTIVE,   gauge, Ratio of cycles the fp64 pipes are active.
    # DCGM_FI_PROF_PIPE_FP32_ACTIVE,   gauge, Ratio of cycles the fp32 pipes are active.
    ...
    vi /etc/dcgm-exporter/default-counters.csv
    ## Example ##
    ...
    DCGM_FI_PROF_PIPE_TENSOR_ACTIVE, gauge, Ratio of cycles the tensor (HMMA) pipe is active.
    DCGM_FI_PROF_DRAM_ACTIVE,        gauge, Ratio of cycles the device memory interface is active sending or receiving data.
    # DCGM_FI_PROF_PIPE_FP64_ACTIVE,   gauge, Ratio of cycles the fp64 pipes are active.
    # DCGM_FI_PROF_PIPE_FP32_ACTIVE,   gauge, Ratio of cycles the fp32 pipes are active.
    ...
    Code block. datacenter-gpu-manager-exporter metric configuration example
    Reference
    For metrics that can be collected with the GPU DCGM Exporter and configuration methods, refer to DCGM Exporter Metrics.
    Caution
    Metric collection through ServiceWatch Agent is classified as custom metrics, and unlike basic metrics collected from each service, fees are charged. Therefore, unnecessary metric collection should be removed or disabled to avoid excessive charges.

Enable and Start DCGM Service (for RHEL)

  1. Enable and start nvdia-dcgm service.

    Color mode
    systemctl enable --now nvidia-dcgm
    systemctl enable --now nvidia-dcgm
    Code block. Enable and start nvdia-dcgm service command

  2. Enable and start nvdia-dcgm-exporter service.

    Color mode
    systemctl enable --now nvidia-dcgm-exporter
    systemctl enable --now nvidia-dcgm-exporter
    Code block. Enable and start nvdia-dcgm-exporter service command

Notice
If you have completed DCGM Exporter configuration, you must install the Open Telemetry Collector provided by ServiceWatch to complete ServiceWatch Agent configuration.
For details, refer to ServiceWatch > Use ServiceWatch Agent.

DCGM Exporter Metrics

DCGM Exporter Key Metrics

The key GPU metrics provided by DCGM Exporter are as follows.

CategoryDCGM FieldPrometheus Metric TypeSummary
ClocksDCGM_FI_DEV_SM_CLOCKgaugeSM clock frequency (in MHz)
ClocksDCGM_FI_DEV_MEM_CLOCKgaugeMemory clock frequency (in MHz)
TemperatureDCGM_FI_DEV_GPU_TEMPgaugeGPU temperature (in C)
PowerDCGM_FI_DEV_POWER_USAGEgaugePower draw (in W)
UtilizationDCGM_FI_DEV_GPU_UTILgaugeGPU utilization (in %)
UtilizationDCGM_FI_DEV_MEM_COPY_UTILgaugeMemory utilization (in %)
Memory UsageDCGM_FI_DEV_FB_FREEgaugeFrame buffer memory free (in MiB)
Memory UsageDCGM_FI_DEV_FB_USEDgaugeFrame buffer memory used (in MiB)
NvlinkDCGM_FI_DEV_NVLINK_BANDWIDTH_TOTAL(8 GPU only)counterTotal number of NVLink bandwidth counters for all lanes
Table. Key GPU metrics provided by DCGM Exporter

DCGM Exporter Metrics Collection Configuration

For the metrics configured by default in DCGM Exporter, refer to DCGM Exporter > Default Metrics.

  • For additional metrics to configure beyond the default settings, remove # in default-counters.csv.
  • For metrics you do not want to collect among the default configured metrics, add # or delete the item.
Color mode
# Format
# If line starts with a '#' it is considered a comment
# DCGM FIELD, Prometheus metric type, help message

# Clocks
DCGM_FI_DEV_SM_CLOCK,  gauge, SM clock frequency (in MHz).
DCGM_FI_DEV_MEM_CLOCK, gauge, Memory clock frequency (in MHz).

# Temperature
DCGM_FI_DEV_MEMORY_TEMP, gauge, Memory temperature (in C).
DCGM_FI_DEV_GPU_TEMP,    gauge, GPU temperature (in C).

# Power
DCGM_FI_DEV_POWER_USAGE,              gauge, Power draw (in W).
DCGM_FI_DEV_TOTAL_ENERGY_CONSUMPTION, counter, Total energy consumption since boot (in mJ).

# PCIE
# DCGM_FI_PROF_PCIE_TX_BYTES,  counter, Total number of bytes transmitted through PCIe TX via NVML.
# DCGM_FI_PROF_PCIE_RX_BYTES,  counter, Total number of bytes received through PCIe RX via NVML.
...
# Format
# If line starts with a '#' it is considered a comment
# DCGM FIELD, Prometheus metric type, help message

# Clocks
DCGM_FI_DEV_SM_CLOCK,  gauge, SM clock frequency (in MHz).
DCGM_FI_DEV_MEM_CLOCK, gauge, Memory clock frequency (in MHz).

# Temperature
DCGM_FI_DEV_MEMORY_TEMP, gauge, Memory temperature (in C).
DCGM_FI_DEV_GPU_TEMP,    gauge, GPU temperature (in C).

# Power
DCGM_FI_DEV_POWER_USAGE,              gauge, Power draw (in W).
DCGM_FI_DEV_TOTAL_ENERGY_CONSUMPTION, counter, Total energy consumption since boot (in mJ).

# PCIE
# DCGM_FI_PROF_PCIE_TX_BYTES,  counter, Total number of bytes transmitted through PCIe TX via NVML.
# DCGM_FI_PROF_PCIE_RX_BYTES,  counter, Total number of bytes received through PCIe RX via NVML.
...
Code block. default-counters.csv configuration example

2.3.3 - API Reference

API Reference

2.3.4 - CLI Reference

CLI Reference

2.3.5 - Release Note

GPU Server

2025.10.23
FEATURE Add new features and provide ServiceWatch service integration functionality
  • ServiceWatch service integration provision
    • You can monitor data through the ServiceWatch service.
  • You can select a RHEL image when creating a GPU Server.
  • Keypair management feature has been added.
  • You can create a keypair to use, or retrieve a public key and apply it.
2025.07.01
FEATURE GPU Server feature addition, Image sharing method change and GPU Server usage guide addition
  • GPU Server feature addition
    • IP, Public NAT IP, Private NAT IP configuration feature has been added.
    • LLM Endpoint is provided for LLM usage.
  • The method of sharing images between accounts has been changed.
    • You can create a new shared Image and share it.
  • Add GPU Server usage guide
2025.04.28
FEATURE Add OS image
  • GPU Server RHEL OS and GPU driver version have been added.
2025.02.27
FEATURE Common Feature Change
  • GPU Server feature addition
    • NAT setting feature has been added to GPU Server.
  • Samsung Cloud Platform Common Feature Change
    • Account, IAM and Service Home, tags, etc. have been reflected in common CX changes.
2024.10.01
NEW GPU Server Service Official Version Release
  • GPU Server service has been officially launched.
  • CPU, GPU, memory, etc., we have launched a virtualization computing service that allows you to allocate and use the infrastructure resources provided by the server as needed at the required time without having to purchase them individually.

2.4 - Bare Metal Server

2.4.1 - Overview

Service Overview

Bare Metal Server does not use virtualization technology and a high-performance cloud computing service that can allocate and use physically separated computing resources such as CPU and memory individually. Since it is not affected by other cloud users, you can reliably operate performance-sensitive services.

Features

  • Easy and convenient computing environment setup: Through the web-based console, you can easily use everything from Bare Metal Server provisioning to resource management and cost management. You can receive a server with standard specs (CPU, Memory, Disk) allocated exclusively and use it immediately.

  • Providing High-Performance Computing Environment: We provide servers suitable for workloads that require large capacity and high performance, such as real-time (Real-Time) systems, HPC (High Performance Computing), and servers that demand excessive I/O usage, in a physically isolated environment.

  • Efficient Service Provision: We ensure performance and stability through optimal server selection and in-house testing. Customers can select the optimal resources for their service environment through the various specifications of Bare Metal Servers offered by Samsung Cloud Platform.

Service Diagram

Diagram
Figure. Bare Metal Server diagram

Provided Features

Bare Metal Server provides the following features.

  • Auto Provisioning and Management: Through the web-based console, you can easily use everything from Bare Metal Server provisioning to resource management and cost management.
  • Providing various types of server types and OS images: Provides CPU/Memory/Disk resources of standard server types, and offers various standard OS images.
  • Storage Connection: Provides additional connected storage besides the OS disk. You can connect and use Block Storage, File Storage, and Object Storage.
  • Network Connection: You can connect the general subnet/IP settings of the Bare Metal Server and the Public NAT IP. Provides a local subnet connection for communication between servers. This operation can be modified on the detail page.
  • Monitoring: You can view monitoring information such as CPU, Memory, Disk, which are computing resources, through Cloud Monitoring. To use the Cloud Monitoring service of Bare Metal Server, you need to install the Agent. Please be sure to install the Agent for stable Bare Metal Server service usage. For more details, refer to Bare Metal Server Monitoring Metrics.
  • Backup and Recovery: Bare Metal Server’s Filesystem backup and recovery can be used through the Backup service.
  • Efficient Cost Management: You can easily create/terminate servers as needed, and because billing is based on actual usage time, you can use it cost-effectively in various unpredictable situations.
  • Local disk partition creation You can create and use up to 10 local disk partitions.
  • Terraform provision: Provides an IaC environment through Terraform.

Components

Bare Metal Server provides various OS standard images and standard server types. Users can select and use them according to the scale of the service they want to configure.

OS Image Provided Version

The OS images supported by Bare Metal Server are as follows

OS Image VersionEoS Date
Oracle Linux 9.62032-06-30
RHEL 8.102029-05-31
RHEL 9.42026-04-30
RHEL 9.62027-05-31
Rocky Linux 8.102029-05-31
Rocky Linux 9.62025-11-30
Ubuntu 22.042027-06-30
Ubuntu 24.042029-06-30
Windows 20192029-01-09
Windows 20222031-10-14
Table. Bare Metal Server Provided OS Image Version

Server Type

The server types supported by Bare Metal Server are as follows. For more details about the server types supported by Bare Metal Server, see Bare Metal Server Server Type.

s3v16m64_metal
CategoryExampleDetailed description
Server Generations3Provided server classification and generation
  • s3: s means the standard specification (vCPU, Memory) commonly used for Standard, and 1 means the generation
CPU vCorev16vCore count
  • v16: Allocated vCores are twice the number of physical cores
    • 16 vCores correspond to physically 8 cores
    • Provided with Hyperthreading enabled by default, which can be disabled when creating a service
Memorym64Memory Capacity
  • m64: 64GB Memory
Table. Bare Metal Server Server Type

Preceding Service

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

Service CategoryServiceDetailed Description
NetworkingVPCA service that provides an independent virtual network in a cloud environment
Table. Bare Metal Server Pre-service

2.4.1.1 - Server Type

Bare Metal Server Server Types

Bare Metal Server provides server types according to usage purposes. Server types are configured with various combinations of CPU, Memory, etc. The server used for Bare Metal Server is determined by the server type selected when creating Bare Metal Server. Please select a server type according to the specifications of the application you want to run on Bare Metal Server.

The server types supported by Bare Metal Server follow the format below.

s3v16m64_metal
Category
ExampleDescription
Server Generations3Server category and generation provided
  • s3
    • s means standard specifications
    • 3 means generation
  • h3
    • h means high-capacity server specifications
    • 3 means generation
CPU vCorev16Number of vCores
  • v16: Allocated vCore is double the physical cores
    • 16 vCore is physically 8 cores
    • Hyper-Threading is enabled by default and can be disabled when creating the service
Memorym64Memory capacity
  • m64: 64GB Memory
Table. Bare Metal Server server type format

s4/h4 Server Types

Bare Metal Server s4 server type is provided with standard specifications (vCPU, Memory) and is suitable for high-performance applications because it receives physically isolated resources for use. Also, Bare Metal Server h4 server type is provided with high-capacity server specifications and is suitable for high-performance applications for large-scale data processing.

  • Supports 5 types of vCPU in total (16, 32, 64, 96, 128 vCore)
    • Intel 6th generation (Granite Rapids) Processor
  • Supports up to 64 physical cores, 128 vCPUs, and 2,048 GB of memory
  • Provides up to 2 x 1.92 TB Internal Disks (for OS)
Server TypePhysical CPUvCPUMemoryCPU TypeInternal Disk(OS)
s4v16m64_metal8 Core16 vCore64 GBIntel Xeon 6507P up to 4.3GHz480GB * 2EA
s4v16m128_metal8 Core16 vCore128 GBIntel Xeon 6507P up to 4.3GHz480GB * 2EA
s4v16m256_metal8 Core16 vCore256 GBIntel Xeon 6507P up to 4.3GHz480GB * 2EA
h4v32m128_metal16 Core32 vCore128 GBIntel Xeon 6517P up to 4.0GHz960GB * 2EA
h4v32m256_metal16 Core32 vCore256 GBIntel Xeon 6517P up to 4.0GHz960GB * 2EA
h4v32m512_metal16 Core32 vCore512 GBIntel Xeon 6517P up to 4.0GHz960GB * 2EA
h4v64m256_metal32 Core64 vCore256 GBIntel Xeon 6737P up to 4.0GHz1.92TB * 2EA
h4v64m512_metal32 Core64 vCore512 GBIntel Xeon 6737P up to 4.0GHz1.92TB * 2EA
h4v64m1024_metal32 Core64 vCore1024 GBIntel Xeon 6737P up to 4.0GHz1.92TB * 2EA
h4v96m512_metal48 Core96 vCore512 GBIntel Xeon 6520P up to 3.4GHz1.92TB * 2EA
h4v96m768_metal48 Core96 vCore768 GBIntel Xeon 6520P up to 3.4GHz1.92TB * 2EA
h4v96m2048_metal48 Core96 vCore2048 GBIntel Xeon 6520P up to 3.4GHz1.92TB * 2EA
h4v128m512_metal64 Core128 vCore512 GBIntel Xeon 6737P up to 4.0GHz1.92TB * 2EA
h4v128m1024_metal64 Core128 vCore1024 GBIntel Xeon 6737P up to 4.0GHz1.92TB * 2EA
h4v128m2048_metal64 Core128 vCore2048 GBIntel Xeon 6737P up to 4.0GHz1.92TB * 2EA
Table. Bare Metal Server server type specifications > s4/h4 server types

s3/h3 Server Types

Bare Metal Server s3 server type is provided with standard specifications (vCPU, Memory) and is suitable for high-performance applications because it receives physically isolated resources for use. Also, Bare Metal Server h3 server type is provided with high-capacity server specifications and is suitable for high-performance applications for large-scale data processing.

  • Supports 5 types of vCPU in total (16, 32, 64, 96, 128 vCore)
    • Intel 4th generation (Sapphire Rapids) Processor
  • Supports up to 64 physical cores, 128 vCPUs, and 2,048 GB of memory
  • Provides up to 2 x 1.92 TB Internal Disks (for OS)
Server TypePhysical CPUvCPUMemoryCPU TypeInternal Disk(OS)
s3v16m64_metal8 Core16 vCore64 GBIntel Xeon Gold 6434 up to 4.1GHz480 GB * 2EA
s3v16m128_metal8 Core16 vCore128 GBIntel Xeon Gold 6434 up to 4.1GHz480 GB * 2EA
s3v16m256_metal8 Core16 vCore256 GBIntel Xeon Gold 6434 up to 4.1GHz480 GB * 2EA
h3v32m128_metal16 Core32 vCore128 GBIntel Xeon Gold 6444Y up to 4.0GHz960 GB * 2EA
h3v32m256_metal16 Core32 vCore256 GBIntel Xeon Gold 6444Y up to 4.0GHz960 GB * 2EA
h3v32m512_metal16 Core32 vCore512 GBIntel Xeon Gold 6444Y up to 4.0GHz960 GB * 2EA
h3v64m256_metal32 Core64 vCore256 GBIntel Xeon Gold 6448H up to 3.2GHz1.92 TB * 2EA
h3v64m512_metal32 Core64 vCore512 GBIntel Xeon Gold 6448H up to 3.2GHz1.92 TB * 2EA
h3v64m1024_metal32 Core64 vCore1024 GBIntel Xeon Gold 6448H up to 3.2GHz1.92 TB * 2EA
h3v96m384_metal48 Core96 vCore384 GBIntel Xeon Gold 6442Y up to 3.3GHz1.92 TB * 2EA
h3v96m768_metal48 Core96 vCore768 GBIntel Xeon Gold 6442Y up to 3.3GHz1.92 TB * 2EA
h3v96m1536_metal48 Core96 vCore1536 GBIntel Xeon Gold 6442Y up to 3.3GHz1.92 TB * 2EA
h3v128m512_metal64 Core128 vCore512 GBIntel Xeon Gold 6448H up to 3.2GHz1.92 TB * 2EA
h3v128m1024_metal64 Core128 vCore1024 GBIntel Xeon Gold 6448H up to 3.2GHz1.92 TB * 2EA
h3v128m2048_metal64 Core128 vCore2048 GBIntel Xeon Gold 6448H up to 3.2GHz1.92 TB * 2EA
Table. Bare Metal Server server type specifications > s3/h3 server types

s2/h2 Server Types

Notice
New service applications for s2/h2 server types have been discontinued. Existing services are not affected.

Bare Metal Server s2 server type is provided with standard specifications (vCPU, Memory) and is suitable for high-performance applications because it receives physically isolated resources for use.

Also, Bare Metal Server h2 server type is provided with high-capacity server specifications and is suitable for high-performance applications for large-scale data processing.

  • Supports 5 types of vCPU in total (16, 24, 32, 72, 96 vCore)
    • Intel 3rd generation (Ice Lake) Processor
  • Supports up to 48 physical cores, 96 vCPUs, and 1,024 GB of memory
  • Provides up to 2 x 1.92 TB Internal Disks (for OS)
Server TypePhysical CPUvCPUMemoryCPU TypeInternal Disk(OS)
s2v16m64_metal8 Core16 vCore64 GBIntel Xeon Gold 6334 up to 3.6GHz480 GB * 2EA
s2v16m128_metal8 Core16 vCore128 GBIntel Xeon Gold 6334 up to 3.6GHz480 GB * 2EA
s2v16m256_metal8 Core16 vCore256 GBIntel Xeon Gold 6334 up to 3.6GHz480 GB * 2EA
h2v24m96_metal12 Core24 vCore96 GBIntel Xeon Gold 5317 up to 3.4GHz960 GB * 2EA
h2v24m192_metal12 Core24 vCore192 GBIntel Xeon Gold 5317 up to 3.4GHz960 GB * 2EA
h2v24m384_metal12 Core24 vCore384 GBIntel Xeon Gold 5317 up to 3.4GHz960 GB * 2EA
h2v32m128_metal16 Core32 vCore128 GBIntel Xeon Gold 6346 up to 3.6GHz960 GB * 2EA
h2v32m256_metal16 Core32 vCore256 GBIntel Xeon Gold 6346 up to 3.6GHz960 GB * 2EA
h2v32m512_metal16 Core32 vCore512 GBIntel Xeon Gold 6346 up to 3.6GHz960 GB * 2EA
h2v72m256_metal36 Core72 vCore256 GBIntel Xeon Gold 6354 up to 3.6GHz1.92 TB * 2EA
h2v72m512_metal36 Core72 vCore512 GBIntel Xeon Gold 6354 up to 3.6GHz1.92 TB * 2EA
h2v72m1024_metal36 Core72 vCore1024 GBIntel Xeon Gold 6354 up to 3.6GHz1.92 TB * 2EA
h2v96m384_metal48 Core96 vCore384 GBIntel Xeon Gold 6342 up to 3.3GHz1.92 TB * 2EA
h2v96m768_metal48 Core96 vCore768 GBIntel Xeon Gold 6342 up to 3.3GHz1.92 TB * 2EA
Table. Bare Metal Server server type specifications > s2/h2 server types

2.4.1.2 - Monitoring Metrics

Bare Metal Server Monitoring Metrics

The following table shows the monitoring metrics for Bare Metal Server that can be checked through Cloud Monitoring.

Guide
Bare Metal Server requires the user to install the Agent through a guide to retrieve monitoring metrics. Please install the Agent before using the stable Bare Metal Server service. For the Agent installation method and detailed Cloud Monitoring usage, refer to the Cloud Monitoring guide.
Performance ItemDetailed DescriptionUnit
Core Usage [IO Wait]The ratio of CPU time spent in a waiting state (disk wait)%
Core Usage [System]The ratio of CPU time spent in kernel space%
Core Usage [User]The ratio of CPU time spent in user space%
CPU CoresThe number of CPU cores on the hostcnt
CPU Usage [Active]The percentage of CPU time used, excluding idle and IOWait states%
CPU Usage [Idle]The ratio of CPU time spent in an idle state%
CPU Usage [IO Wait]The ratio of CPU time spent in a waiting state (disk wait)%
CPU Usage [System]The percentage of CPU time used by the kernel%
CPU Usage [User]The percentage of CPU time used by the user area%
CPU Usage/Core [Active]The percentage of CPU time used, excluding idle and IOWait states%
CPU Usage/Core [Idle]The ratio of CPU time spent in an idle state%
CPU Usage/Core [IO Wait]The ratio of CPU time spent in a waiting state (disk wait)%
CPU Usage/Core [System]The percentage of CPU time used by the kernel%
CPU Usage/Core [User]The percentage of CPU time used by the user area%
Disk CPU Usage [IO Request]The ratio of CPU time spent executing I/O requests for the device%
Disk Queue Size [Avg]The average queue length of requests executed for the devicenum
Disk Read BytesThe number of bytes read from the device per secondbytes
Disk Read Bytes [Delta Avg]The average of system.diskio.read.bytes_delta for individual disksbytes
Disk Read Bytes [Delta Max]The maximum of system.diskio.read.bytes_delta for individual disksbytes
Disk Read Bytes [Delta Min]The minimum of system.diskio.read.bytes_delta for individual disksbytes
Disk Read Bytes [Delta Sum]The sum of system.diskio.read.bytes_delta for individual disksbytes
Disk Read Bytes [Delta]The delta of system.diskio.read.bytes for individual disksbytes
Disk Read Bytes [Success]The total number of bytes read successfullybytes
Disk Read RequestsThe number of read requests for the disk device per secondcnt
Disk Read Requests [Delta Avg]The average of system.diskio.read.count_delta for individual diskscnt
Disk Read Requests [Delta Max]The maximum of system.diskio.read.count_delta for individual diskscnt
Disk Read Requests [Delta Min]The minimum of system.diskio.read.count_delta for individual diskscnt
Disk Read Requests [Delta Sum]The sum of system.diskio.read.count_delta for individual diskscnt
Disk Read Requests [Success Delta]The delta of system.diskio.read.count for individual diskscnt
Disk Read Requests [Success]The total number of successful readscnt
Disk Request Size [Avg]The average size of requests executed for the device (in sectors)num
Disk Service Time [Avg]The average service time for I/O requests executed for the device (in milliseconds)ms
Disk Wait Time [Avg]The average time spent waiting for I/O requests executed for the devicems
Disk Wait Time [Read]The average disk read wait timems
Disk Wait Time [Write]The average disk write wait timems
Disk Write Bytes [Delta Avg]The average of system.diskio.write.bytes_delta for individual disksbytes
Disk Write Bytes [Delta Max]The maximum of system.diskio.write.bytes_delta for individual disksbytes
Disk Write Bytes [Delta Min]The minimum of system.diskio.write.bytes_delta for individual disksbytes
Disk Write Bytes [Delta Sum]The sum of system.diskio.write.bytes_delta for individual disksbytes
Disk Write Bytes [Delta]The delta of system.diskio.write.bytes for individual disksbytes
Disk Write Bytes [Success]The total number of bytes written successfullybytes
Disk Write RequestsThe number of write requests for the disk device per secondcnt
Disk Write Requests [Delta Avg]The average of system.diskio.write.count_delta for individual diskscnt
Disk Write Requests [Delta Max]The maximum of system.diskio.write.count_delta for individual diskscnt
Disk Write Requests [Delta Min]The minimum of system.diskio.write.count_delta for individual diskscnt
Disk Write Requests [Delta Sum]The sum of system.diskio.write.count_delta for individual diskscnt
Disk Write Requests [Success Delta]The delta of system.diskio.write.count for individual diskscnt
Disk Write Requests [Success]The total number of successful writescnt
Disk Writes BytesThe number of bytes written to the device per secondbytes
Filesystem Hang CheckFilesystem (local/NFS) hang check (normal: 1, abnormal: 0)status
Filesystem NodesThe total number of file nodes in the filesystemcnt
Filesystem Nodes [Free]The total number of available file nodes in the filesystemcnt
Filesystem Size [Available]The available disk space for non-privileged users (in bytes)bytes
Filesystem Size [Free]The available disk space (in bytes)bytes
Filesystem Size [Total]The total disk space (in bytes)bytes
Filesystem UsageThe percentage of used disk space%
Filesystem Usage [Avg]The average of filesystem.used.pct for individual filesystems%
Filesystem Usage [Inode]The inode usage rate%
Filesystem Usage [Max]The maximum of filesystem.used.pct for individual filesystems%
Filesystem Usage [Min]The minimum of filesystem.used.pct for individual filesystems%
Filesystem Usage [Total]The total filesystem usage%
Filesystem UsedThe used disk space (in bytes)bytes
Filesystem Used [Inode]The inode usagebytes
Memory FreeThe total available memory (in bytes), excluding system cache and buffer memorybytes
Memory Free [Actual]The actual available memory (in bytes)bytes
Memory Free [Swap]The available swap memorybytes
Memory TotalThe total memorybytes
Memory Total [Swap]The total swap memorybytes
Memory UsageThe percentage of used memory%
Memory Usage [Actual]The percentage of actual used memory%
Memory Usage [Cache Swap]The cache swap usage rate%
Memory Usage [Swap]The percentage of used swap memory%
Memory UsedThe used memorybytes
Memory Used [Actual]The actual used memory (in bytes), subtracted from the total memorybytes
Memory Used [Swap]The used swap memorybytes
CollisionsNetwork collisionscnt
Network In BytesThe number of received bytesbytes
Network In Bytes [Delta Avg]The average of system.network.in.bytes_delta for individual networksbytes
Network In Bytes [Delta Max]The maximum of system.network.in.bytes_delta for individual networksbytes
Network In Bytes [Delta Min]The minimum of system.network.in.bytes_delta for individual networksbytes
Network In Bytes [Delta Sum]The sum of system.network.in.bytes_delta for individual networksbytes
Network In Bytes [Delta]The delta of received bytesbytes
Network In DroppedThe number of dropped incoming packetscnt
Network In ErrorsThe number of errors during receptioncnt
Network In PacketsThe number of received packetscnt
Network In Packets [Delta Avg]The average of system.network.in.packets_delta for individual networkscnt
Network In Packets [Delta Max]The maximum of system.network.in.packets_delta for individual networkscnt
Network In Packets [Delta Min]The minimum of system.network.in.packets_delta for individual networkscnt
Network In Packets [Delta Sum]The sum of system.network.in.packets_delta for individual networkscnt
Network In Packets [Delta]The delta of received packetscnt
Network Out BytesThe number of transmitted bytesbytes
Network Out Bytes [Delta Avg]The average of system.network.out.bytes_delta for individual networksbytes
Network Out Bytes [Delta Max]The maximum of system.network.out.bytes_delta for individual networksbytes
Network Out Bytes [Delta Min]The minimum of system.network.out.bytes_delta for individual networksbytes
Network Out Bytes [Delta Sum]The sum of system.network.out.bytes_delta for individual networksbytes
Network Out Bytes [Delta]The delta of transmitted bytesbytes
Network Out DroppedThe number of dropped outgoing packetscnt
Network Out ErrorsThe number of errors during transmissioncnt
Network Out PacketsThe number of transmitted packetscnt
Network Out Packets [Delta Avg]The average of system.network.out.packets_delta for individual networkscnt
Network Out Packets [Delta Max]The maximum of system.network.out.packets_delta for individual networkscnt
Network Out Packets [Delta Min]The minimum of system.network.out.packets_delta for individual networkscnt
Network Out Packets [Delta Sum]The sum of system.network.out.packets_delta for individual networkscnt
Network Out Packets [Delta]The delta of transmitted packetscnt
Open Connections [TCP]The number of open TCP connectionscnt
Open Connections [UDP]The number of open UDP connectionscnt
Port UsageThe port usage rate%
SYN Sent SocketsThe number of sockets in the SYN_SENT state (when connecting from local to remote)cnt
Kernel PID MaxThe value of kernel.pid_maxcnt
Kernel Thread MaxThe value of kernel.threads-maxcnt
Process CPU UsageThe percentage of CPU time consumed by the process since the last update%
Process CPU Usage/CoreThe percentage of CPU time used by the process since the last event%
Process Memory UsageThe percentage of main memory (RAM) used by the process%
Process Memory UsedThe resident set size, which is the amount of memory used by the process in RAMbytes
Process PIDThe process IDpid
Process PPIDThe parent process IDpid
Processes [Dead]The number of dead processescnt
Processes [Idle]The number of idle processescnt
Processes [Running]The number of running processescnt
Processes [Sleeping]The number of sleeping processescnt
Processes [Stopped]The number of stopped processescnt
Processes [Total]The total number of processescnt
Processes [Unknown]The number of processes with unknown or unsearchable statuscnt
Processes [Zombie]The number of zombie processescnt
Running Process UsageThe process usage rate%
Running ProcessesThe number of running processescnt
Running Thread UsageThe thread usage rate%
Running ThreadsThe total number of threads running in running processescnt
Context SwitchesThe number of context switches (per second)cnt
Load/Core [1 min]The load averaged over the last 1 minute, divided by the number of corescnt
Load/Core [15 min]The load averaged over the last 15 minutes, divided by the number of corescnt
Load/Core [5 min]The load averaged over the last 5 minutes, divided by the number of corescnt
Multipaths [Active]The number of external storage connection paths with status = activecnt
Multipaths [Failed]The number of external storage connection paths with status = failedcnt
Multipaths [Faulty]The number of external storage connection paths with status = faultycnt
NTP OffsetThe measured offset (time difference between the NTP server and the local environment) of the last samplenum
Run Queue LengthThe length of the run queuenum
UptimeThe OS uptime (in milliseconds)ms
Context SwitchiesThe number of CPU context switches (per second)cnt
Disk Read Bytes [Sec]The number of bytes read from the Windows logical disk per secondcnt
Disk Read Time [Avg]The average data read time (in seconds)sec
Disk Transfer Time [Avg]The average disk wait timesec
Disk UsageThe disk usage rate%
Disk Write Bytes [Sec]The number of bytes written to the Windows logical disk per secondcnt
Disk Write Time [Avg]The average data write time (in seconds)sec
Pagingfile UsageThe paging file usage rate%
Pool Used [Non Paged]The non-paged pool usage in kernel memorybytes
Pool Used [Paged]The paged pool usage in kernel memorybytes
Process [Running]The number of currently running processescnt
Threads [Running]The number of currently running threadscnt
Threads [Waiting]The number of threads waiting for processor timecnt
Table. Bare Metal Server Monitoring Metrics (Available when Agent is installed)

2.4.2 - How-to guides

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

Bare Metal Server Create

You can create and use the Bare Metal Server service from the Samsung Cloud Platform Console.

To create a Bare Metal Server, follow the steps below.

  1. All Services > Compute > Bare Metal Server Click the menu. Go to the Service Home page of Bare Metal Server.
  2. Click the Bare Metal Server Create button on the Service Home page. It navigates to the Bare Metal Server Create page.
  3. Bare Metal Server creation On the page, enter the information required to create the service, and select detailed options.
    • Image and Version Selection area, select the required information.
      Category
      Required or not
      Detailed description
      ImageRequiredSelect the type of image provided
      • RHEL
      • Rocky Linux
      • Ubuntu
      • Windows
      Image VersionRequiredSelect version of the chosen image
      • Provides a list of versions of the provided server images
      Table. Bare Metal Server Image and Version Input Items
    • Service Information Input area, please input or select the required information.
      Category
      Required or not
      Detailed description
      Server countRequiredNumber of Bare Metal Server servers to create simultaneously
      • Only numbers can be entered, and must be between 1 and 5
      Service Type > Server TypeRequiredBare Metal Server Server Type
      • Select desired vCPU, Memory, Disk specifications
      Service Type > Planned ComputeRequiredStatus of resources with Planned Compute set
      • In Use: Number of resources with Planned Compute set that are in use
      • Configured: Number of resources with Planned Compute set
      • Coverage Preview: Amount applied by Planned Compute per resource
      Automation AccountRequiredAutomatically creates an account to provide automation functions after Bare Metal Server creation
      • The account is used only for inter-system interface purposes
      • Password is encrypted and cannot be accessed outside the system
      • If the account is deleted, network changes and some automation functions will be restricted
      Table. Bare Metal Server Service Information Input Items
    • In the Required Information Input area, enter or select the required information.
      Category
      Required or not
      Detailed description
      Administrator AccountRequiredSet the administrator account and password to be used when connecting to the server
      • RHEL, Ubuntu OS are provided fixed as root
      • For Windows OS, enter using lowercase English letters and numbers, 5~20 characters
        • Administrator not allowed
      Server NameRequiredEnter a name to distinguish the Bare Metal Server when the selected number of servers is 1
      • Set the hostname to the entered server name
      • Start with a lowercase English letter, and use lowercase letters, numbers, and special character (-) to enter within 3 to 15 characters
      • Must not end with a special character (-)
      Server Name PrefixRequiredInput Prefix to distinguish each Bare Metal Server generated when the selected number of servers is 2 or more
      • Automatically generated in the form of user input value (prefix) + ‘-###
      • Must start with a lowercase English letter, and be entered using lowercase letters, numbers, and special characters (-) within 3 to 15 characters
      • Must not end with a special character (-)
      Network SettingsRequiredSet the network where the Bare Metal Server will be installed
      • Select a pre-created VPC
      • General Subnet: Select a pre-created general Subnet
        • IP can be set to Auto-generated or User input; if Input is selected, the user enters the IP directly
      • NAT: Available only when there is a single server and the VPC has an Internet Gateway attached
        • When checked, a NAT IP can be selected
      • NAT IP: Select a NAT IP
        • If there is no NAT IP to select, click the Create New button to generate a Public IP
        • Click the Refresh button to view and select the created Public IP
        • Creating a Public IP incurs charges according to the Public IP pricing policy
      • Local Subnet (Optional): Choose to use a local Subnet
        • Not a required element for creating the service
        • Select a pre-created local Subnet
        • IP can be set to Auto-generated or User input; if Input is selected, the user enters the IP directly
      Table. Bare Metal Server Required Information Input Items
Caution

Please use a firewall etc. to control traffic access for Bare Metal Server. Security Group is not provided.
The firewall of the Bare Metal Server can only be used for traffic control between the Bare Metal Server and the Virtual Server. To use the Bare Metal Server’s firewall, follow the steps below.

  1. Separate the VPC of the Bare Metal Server: Separate them so that the Bare Metal Server and Virtual Server do not use the same VPC.
  2. Create Transit Gateway: Please create the Transit Gateway.
    • The integration between the VPC of Virtual Server and the VPC of Bare Metal Server uses a Transit Gateway.
    • When creating a Transit Gateway integration in the VPC of a Bare Metal Server, you must also create the Bare Metal Server’s firewall.
  3. Firewall Rule registration: Register a rule in the Firewall of the Bare Metal Server.
  1. Bare Metal Server Creation on the page Additional Information Input area, enter or select the required information.
    Category
    Required or not
    Detailed description
    Local disk partitionSelectSet whether to use local disk partition
    • Up to 10 can be created, including the root partition
    • Up to 90% of total capacity can be used
    • After checking Use, partition information can be set
    • Root partition information setting
      • Partition type: flat, lvm selectable
      • Partition name: enter partition name
        • Can be entered only when partition type is lvm
        • Enter within 15 characters, starting with a letter and including letters, numbers, and special characters (-)
      • Partition size: enter at least 50 GB
      • Filesystem type: select according to the used image
        • For RHEL, Rocky Linux: xfs, ext4
        • For Ubuntu: ext4, xfs, btrfs
        • For SLES: btrfs, xfs, ext4
      • Mount point: start with special character / and enter within 15 characters, including letters, numbers, and special characters (-)
        • If Filesystem type is swap, entry not allowed
      • Available capacity: 90% of the default disk capacity provided when selecting a server
        • When setting partition size, the remaining capacity is automatically calculated and displayed
        • Total partition disk amount cannot exceed available capacity
    • Additional partition information setting
      • Partition type: flat, lvm selectable
      • Partition name: enter partition name
        • Can be entered only when partition type is lvm
        • Enter within 15 characters, starting with a letter and including letters, numbers, and special characters (-)
      • Partition size: enter at least 1 GB
      • Filesystem type: select according to the used image>
        • For RHEL, Rocky Linux: xfs, ext4, swap
        • For Ubuntu: ext4, xfs, btrfs, swap
        • For SLES: btrfs, xfs, ext4, swap
      • Mount point: start with special character / and enter within 15 characters, including letters, numbers, and special characters (-)
        • If Filesystem type is swap, entry not allowed
      • Available capacity: 90% of the default disk capacity provided when selecting a server
        • When setting partition size, the remaining capacity is automatically calculated and displayed
        • Total partition disk amount cannot exceed available capacity
    Placement GroupSelectServers belonging to the same Placement group are distributed across different racks
    • Provides distributed placement for up to 2 servers belonging to the same Placement group
      • For distribution of 3 or more servers, add additional Placement groups
    • Applicable only at initial creation; cannot be modified after creation
    • If you terminate the last server belonging to a Placement group, that Placement group is automatically deleted
    LockSelectUsing Lock prevents actions caused by mistakes, preventing the server from being terminated, started, or stopped
    Hyper ThreadingSelectSet logical cores to operate at twice the number of physical cores
    • Uncheck the box to turn off Hyper Threading
    • Cannot be changed after server creation
    Init ScriptSelectScript to run when the server starts
    • Init Script must be selected differently depending on the image type
      • For Windows: Select Batch Script
      • For Linux: Shell Script
    Table. Bare Metal Server Additional Information Input Items
  2. 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 Bare Metal Server List page.

Bare Metal Server Check detailed information

The Bare Metal Server service can view and edit the full resource list and detailed information. Bare Metal Server Details page consists of Details, Tags, Activity History tabs.

Bare Metal Server If you want to view detailed information, follow the steps below.

  1. All Services > Compute > Bare Metal Server Click the menu. Navigate to the Service Home page of Bare Metal Server.
  2. Click the Bare Metal Server menu on the Service Home page. Go to the Bare Metal Server List page.
  3. Bare Metal Server List page, click the resource to view detailed information. Bare Metal Server Details page moves.
  • Bare Metal Server Detail page displays status information and additional feature information, and consists of Detail Information, Tag, Operation History tabs.
    CategoryDetailed description
    Bare Metal Server statusStatus of the Bare Metal Server created by the user
    • Creating: server is being created
    • Running:: creation complete and usable
    • Editing:: IP is being changed
    • Unknown: error state
    • Starting: server is starting
    • Stopping: server is stopping
    • Stopped: server has stopped
    • Terminating: termination in progress
    • Terminated: termination complete
    Server ControlButton to change server status
    • Start: Start a stopped server
    • Stop: Stop a running server
    Service terminationButton to cancel the service
    Table. Bare Metal Server status information and additional functions

Detailed Information

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

CategoryDetailed description
ServiceService Name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In Bare Metal Server, it means Bare Metal Server SRN
Resource NameResource Name
  • In Bare Metal Server, it means the server name
Resource IDUnique resource ID in the service
CreatorUser who created the service
Creation timeService creation time
EditorUser who edited the service information
Modification DateTimeDate and time when service information was modified
Server nameServer name
Image/VersionServer’s OS image and version
Server TypevCPU, memory information display
Planned ComputeResource status with Planned Compute set
LockDisplay lock usage status
  • If lock is used, it prevents server termination/start/stop to avoid accidental actions
  • If you need to change the lock property value, click the Edit button to set
Hyper ThreadingHyper Threading usage/not usage indication
  • Hyper Threading is a setting that makes the logical core count operate at twice the number of physical cores
NetworkNetwork information of Bare Metal Server
  • VPC, General Subnet, IP and status, Public NAT IP and status, Private NAT IP and status
  • If IP change is needed, click the Edit button to set
Local SubnetLocal Subnet information of Bare Metal Server
  • Local Subnet name, Local Subnet IP, Vlan ID, Interface Name
  • If you need to add a Local Subnet, click the Add button to set
Block StorageBlock Storage information connected to the server
  • Volume name, disk type, capacity, status
  • Click the Add button to go to the Block Storage creation screen
Init ScriptView the Init Script entered when creating the server
Table. Bare Metal Server detailed information tab items

Tag

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

CategoryDetailed description
Tag ListTag List
  • Can view the tag’s Key and Value information
  • Up to 50 tags can be added per resource
  • When entering tags, search and select from the existing list of created Keys and Values
Table. Bare Metal Server Tag Tab Items

Work History

You can view the operation history of the selected resources on the Bare Metal Server List page.

CategoryDetailed description
Work History ListResource Change History
  • Work date and time, Resource ID, Resource name, Work details, Event topic, Work result, Check worker information
Table. Bare Metal Server Work History Tab Detailed Information Items

Bare Metal Server Resource Management

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

Bare Metal Server Operation Control

You can start, stop, and restart a running Bare Metal Server.

To control the operation of Bare Metal Server, follow the steps below.

  1. All Services > Compute > Bare Metal Server Click the menu. Navigate to the Service Home page of Bare Metal Server.
  2. Click the Bare Metal Server menu on the Service Home page. Navigate to the Bare Metal Server List page.
  3. Bare Metal Server list On the page, after selecting multiple servers, you can control multiple servers simultaneously using the start and stop buttons at the top of the table.
    • Bare Metal Server Details page also allows you to start and stop the server.
  4. Bare Metal Server List on the page click the resource to control operation and navigate to the Bare Metal Server Detail page.
  5. Check the server status and complete the changes using each Server Management button.
    • Start: Start the stopped server.
    • Stop: Stops the running server.
Guide

When a Bare Metal Server is stopped, the server’s power turns off.

  • Since it may affect applications or storage in use, we recommend shutting down the OS and then stopping.
  • After shutting down the OS, be sure to also stop in the Console.
Operation control unavailable
  • Bare Metal Server If you cannot start when requesting a start, see below.
      • When Lock is set: After changing the Lock setting to disabled, try again.
    • If the Bare Metal Server’s status is not Stopped: Change the Bare Metal Server’s status to Stopped, then try again.
  • If stopping a Bare Metal Server request is not possible, refer to the following.
    • If Lock is set: Change the Lock setting to disabled, then try again.
    • If the Bare Metal Server’s status is not Running: Change the Bare Metal Server’s status to Running, then try again.

Add Block Storage

You can add Block Storage to a Bare Metal Server.

To add Block Storage, follow the steps below.

  1. All Services > Compute > Bare Metal Server Click the menu. Navigate to the Service Home page of Bare Metal Server.
  2. Click the Bare Metal Server menu on the Service Home page. Go to the Bare Metal Server list page.
  3. On the Bare Metal Server List page, click the server to add Block Storage. You will be taken to the Bare Metal Server Details page.
  4. Click the Add button in the Block Storage item on the Bare Metal Server Details page.
  5. If the popup window confirming Block Storage addition opens, click the Confirm button. Move to the Block Storage (BM) Creation page.
  6. Block Storage(BM) Creation on the page, enter the information required to create the service and create the Block Storage.
  7. Navigate to the Bare Metal Server Details page after adding Block Storage and verify that Block Storage has been added.
Caution
After creating Block Storage, you cannot increase the capacity.

Bare Metal Server Termination

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

Caution
Please note that data cannot be recovered after service termination.
Caution
If you terminate the servers one by one that have Block Storage(BM) attached, the servers will be terminated but the attached Block Storage(BM) will not be terminated, so please terminate it directly from Block Storage(BM).

To cancel the Bare Metal Server, follow the steps below.

  1. All Services > Compute > Bare Metal Server Click the menu. Navigate to the Service Home page of Bare Metal Server.
  2. Click the Bare Metal Server menu on the Service Home page. Go to the Bare Metal Server list page.
  3. Bare Metal Server List page, select the resource to cancel, and click the Cancel Service button.
    • You can select multiple resources and delete them simultaneously.
    • You can also delete by clicking the Service Termination button on the Bare metal Server details page of the resource to be terminated.
  4. When termination is complete, check on the Bare Metal Server List page whether the resource has been terminated.

Termination Constraints

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

Cancellation not allowed
  • Block Storage(BM) is connected (simultaneous termination of 2 or more servers): Disconnect the Block Storage(BM) first.

  • If File Storage is connected: Please disconnect the File Storage first.

  • If Lock is set: After changing the Lock setting to disabled, try again.

  • If there is a Backup Agent or Load Balancer connection resource: Terminate the connection of that resource first.

  • If resource management tasks for Bare Metal Server are in progress on the same account: After the Bare Metal Server resource management tasks are completed, please try again.

  • If the Bare Metal Server’s status is not Running or Stopped: Change the Bare Metal Server’s status to Running or Stopped, then try again.

  • If the server that cannot be terminated simultaneously is included: Please select only the resources that can be terminated and try again.

Local Subnet Setup

After completing the creation of a Bare Metal Server, if you add a local Subnet on the Bare Metal Server Details page, you must configure the network settings of the local Subnet yourself.

First Connection(kr-west)

There is no local subnet connected to the Bare Metal Server, and if you are adding the first connection, proceed according to the guide below.

Caution

This guide applies to kr-west (Korea West) when adding the first local Subnet connection to the server.

Linux - Setting up Subnet on Ubuntu

On the Ubuntu operating system, add a local Subnet, and to proceed with network configuration, follow the steps below.

  1. On the Bare Metal Server Details page, check the Interface Name.

  2. View the network configuration information.

    Color mode
    [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
    network:
    ethernets:
     ens2f1:
     match:
    macaddress: 68:05:ca:d4:09:91
    mtu: 1500
     set-name: ens2f1
     ens4f1:
     match:
     macaddress: 68:05:ca:d4:09:01
    mtu: 1500
     set-name: ens4f1
    [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
    network:
    ethernets:
     ens2f1:
     match:
    macaddress: 68:05:ca:d4:09:91
    mtu: 1500
     set-name: ens2f1
     ens4f1:
     match:
     macaddress: 68:05:ca:d4:09:01
    mtu: 1500
     set-name: ens4f1
    Code block. Network configuration file lookup

  3. After adding a new VLAN, set the IP for the Bonding configuration.

    • Change the ID and IP in the example code to the assigned ID and IP.
      Color mode
      [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
      network:
          bonds:
              bond-mgt:
                  interfaces:  
                  - ens2f1      // **Bare Metal Server Details** page, enter the Interface Name you confirmed.
                  - ens4f1      // **Bare Metal Server detailed** page, enter the Interface Name you verified.  
                  mtu: 1500
                  parameters:
                      mii-monitor-interval: 100
                      mode: active-backup
                      transmit-hash-policy: layer2
          ethernets:
              ens2f1:
                  match:
                  macaddress: 68:05:ca:d4:09:91
                  mtu: 1500
                  set-name: ens2f1
              ens4f1:
                  match:
                  macaddress: 68:05:ca:d4:09:01
                  mtu: 1500
                  set-name: ens4f1
          vlans:
              bond-mgt.20:   // Enter the Vlan ID confirmed in the SCP Console instead of 20.
              addresses:
                  - 192.168.0.10/24 // Set it to the local Subnet IP confirmed in the SCP Console.
                  id: 20    // Set it to the VLAN ID confirmed in the SCP Console.
                  link: bond-mgt
                  mtu: 1500
      [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
      network:
          bonds:
              bond-mgt:
                  interfaces:  
                  - ens2f1      // **Bare Metal Server Details** page, enter the Interface Name you confirmed.
                  - ens4f1      // **Bare Metal Server detailed** page, enter the Interface Name you verified.  
                  mtu: 1500
                  parameters:
                      mii-monitor-interval: 100
                      mode: active-backup
                      transmit-hash-policy: layer2
          ethernets:
              ens2f1:
                  match:
                  macaddress: 68:05:ca:d4:09:91
                  mtu: 1500
                  set-name: ens2f1
              ens4f1:
                  match:
                  macaddress: 68:05:ca:d4:09:01
                  mtu: 1500
                  set-name: ens4f1
          vlans:
              bond-mgt.20:   // Enter the Vlan ID confirmed in the SCP Console instead of 20.
              addresses:
                  - 192.168.0.10/24 // Set it to the local Subnet IP confirmed in the SCP Console.
                  id: 20    // Set it to the VLAN ID confirmed in the SCP Console.
                  link: bond-mgt
                  mtu: 1500
      Code block. IP Settings
  4. Apply the changes to the system.

    Color mode
    # netplan apply
    # netplan apply
    Code block. Reflect changes

  5. Check the interface status.

    Color mode
    # ip a
    or
    # bash /usr/local/bin/ip.sh
    # ip a
    or
    # bash /usr/local/bin/ip.sh
    Code block. Interface lookup

Linux – Setting up Subnet on CentOS/Red Hat

After adding a local Subnet on the CentOS/Red Hat operating system, follow the steps below to configure the network.

Caution
If you set the Interface name incorrectly, the IP information in use may be deleted, so be careful.
  1. On the Bare Metal Server Details page, check the Interface Name.

  2. Modify the following command and execute.

    Color mode
    #!/usr/bin/bash
    
    IP_ADDR="10.1.1.3/24"   // Set the local Subnet IP that you checked from the Console.
    VLAN_ID="7"             // Set the Vlan ID confirmed in the Console.
    
    BOND_NAME="bond-mgt"
    BOND_IF_name1="ens2f1"  // Enter the Interface Name you verified on the **Bare Metal Server Details** page.
    BOND_IF_name2="ens4f0"  // **Bare Metal Server Details** Enter the Interface Name you verified on the page.
    
    
    # Delete Connection
    nmcli con down "Bond ${BOND_NAME}"
    nmcli con del  "Bond ${BOND_NAME}"
    
    nmcli con down "System ${BOND_IF_name1}"
    nmcli con down "System ${BOND_IF_name2}"
    
    nmcli con del  "System ${BOND_IF_name1}"
    nmcli con del  "System ${BOND_IF_name2}"
    
    
    # Create Bonding
    nmcli con add con-name ${BOND_NAME} type bond ifname ${BOND_NAME}
    nmcli conn mod ${BOND_NAME} con-name "Bond ${BOND_NAME}"
    nmcli conn mod "Bond ${BOND_NAME}" ipv4.method    disabled
    nmcli conn mod "Bond ${BOND_NAME}" ipv6.method    ignore
    nmcli conn mod "Bond ${BOND_NAME}" connect.autoconnect yes
    
    nmcli conn mod "Bond ${BOND_NAME}" +bond.options mode=active-backup      \
                                       +bond.options xmit_hash_policy=layer2 \
                                       +bond.options miimon=100              \
                                       +bond.options num_grat_arp=1          \
                                       +bond.options downdelay=0             \
                                       +bond.options updelay=0
    
    # Assign bond-slave
    nmcli conn add type bond-slave ifname ${BOND_IF_name1}  con-name "${BOND_IF_name1}" master ${BOND_NAME}
    nmcli conn mod ${BOND_IF_name1} con-name "System ${BOND_IF_name1}"
    
    nmcli conn add type bond-slave ifname ${BOND_IF_name2}  con-name "${BOND_IF_name2}" master ${BOND_NAME}
    nmcli conn mod ${BOND_IF_name2} con-name "System ${BOND_IF_name2}"
    
    # Connection UP
    nmcli conn up   "Bond ${BOND_NAME}"
    # add vlan
    nmcli conn add type vlan ifname "${BOND_NAME}.${VLAN_ID}" con-name "${BOND_NAME}.${VLAN_ID}" id ${VLAN_ID} dev ${BOND_NAME}
    nmcli con  mod ${BOND_NAME}.${VLAN_ID} con-name "Vlan ${BOND_NAME}.${VLAN_ID}"
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.addresses ${IP_ADDR}
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.method manual
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv6.method "ignore"
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" connect.autoconnect yes
    nmcli con  up  "Vlan ${BOND_NAME}.${VLAN_ID}"
    nmcli      device reapply ${BOND_NAME}.${VLAN_ID}
    #!/usr/bin/bash
    
    IP_ADDR="10.1.1.3/24"   // Set the local Subnet IP that you checked from the Console.
    VLAN_ID="7"             // Set the Vlan ID confirmed in the Console.
    
    BOND_NAME="bond-mgt"
    BOND_IF_name1="ens2f1"  // Enter the Interface Name you verified on the **Bare Metal Server Details** page.
    BOND_IF_name2="ens4f0"  // **Bare Metal Server Details** Enter the Interface Name you verified on the page.
    
    
    # Delete Connection
    nmcli con down "Bond ${BOND_NAME}"
    nmcli con del  "Bond ${BOND_NAME}"
    
    nmcli con down "System ${BOND_IF_name1}"
    nmcli con down "System ${BOND_IF_name2}"
    
    nmcli con del  "System ${BOND_IF_name1}"
    nmcli con del  "System ${BOND_IF_name2}"
    
    
    # Create Bonding
    nmcli con add con-name ${BOND_NAME} type bond ifname ${BOND_NAME}
    nmcli conn mod ${BOND_NAME} con-name "Bond ${BOND_NAME}"
    nmcli conn mod "Bond ${BOND_NAME}" ipv4.method    disabled
    nmcli conn mod "Bond ${BOND_NAME}" ipv6.method    ignore
    nmcli conn mod "Bond ${BOND_NAME}" connect.autoconnect yes
    
    nmcli conn mod "Bond ${BOND_NAME}" +bond.options mode=active-backup      \
                                       +bond.options xmit_hash_policy=layer2 \
                                       +bond.options miimon=100              \
                                       +bond.options num_grat_arp=1          \
                                       +bond.options downdelay=0             \
                                       +bond.options updelay=0
    
    # Assign bond-slave
    nmcli conn add type bond-slave ifname ${BOND_IF_name1}  con-name "${BOND_IF_name1}" master ${BOND_NAME}
    nmcli conn mod ${BOND_IF_name1} con-name "System ${BOND_IF_name1}"
    
    nmcli conn add type bond-slave ifname ${BOND_IF_name2}  con-name "${BOND_IF_name2}" master ${BOND_NAME}
    nmcli conn mod ${BOND_IF_name2} con-name "System ${BOND_IF_name2}"
    
    # Connection UP
    nmcli conn up   "Bond ${BOND_NAME}"
    # add vlan
    nmcli conn add type vlan ifname "${BOND_NAME}.${VLAN_ID}" con-name "${BOND_NAME}.${VLAN_ID}" id ${VLAN_ID} dev ${BOND_NAME}
    nmcli con  mod ${BOND_NAME}.${VLAN_ID} con-name "Vlan ${BOND_NAME}.${VLAN_ID}"
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.addresses ${IP_ADDR}
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.method manual
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv6.method "ignore"
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" connect.autoconnect yes
    nmcli con  up  "Vlan ${BOND_NAME}.${VLAN_ID}"
    nmcli      device reapply ${BOND_NAME}.${VLAN_ID}
    Code block. IP configuration script

  3. Check the interface status.

    Color mode
    # ip a
    or
    # bash /usr/local/bin/ip.sh
    # ip a
    or
    # bash /usr/local/bin/ip.sh
    Code block. Interface lookup

Setting up Subnet on Windows

After adding a local Subnet in the Windows operating system, follow these steps to configure the network.

  1. Windows Start icon, right-click, then run the Windows PowerShell (Administrator) program.

  2. Check the Interface Name on the Bare Metal Server Details page.

  3. Run ncpa.cpl from the Windows Run menu.

    Image

  4. Check whether the interface is activated, and if necessary, activate it.

  • Bare Metal Server detail checked on the page Interface Name activate.
    Image
  1. Create a Teaming.

    Color mode
    PS C:\> New-NetLbfoTeam Name bond-mgt TeamMembers ens2f1,ens4f1
    PS C:\> Set-NetLbfoTeam Name bond-mgt LoadBalancingAlgorithm Dynamic
    PS C:\> New-NetLbfoTeam Name bond-mgt TeamMembers ens2f1,ens4f1
    PS C:\> Set-NetLbfoTeam Name bond-mgt LoadBalancingAlgorithm Dynamic
    Code block. Teaming creation
    Image

  2. After adding a new VLAN, set the IP.

  • Enter the VLAN ID and local Subnet IP confirmed on the Bare Metal Server Details page.
    Color mode
    PS C:\> Add-NetLbfoTeamNIC -Team bond_bond-mgt -VlanID 20 -Name bond-mgt.20
    PS C:\> Get-NetAdapter
    PS C:\> netsh interface ip set address bond-mgt.20 static 192.168.0.10/24
    PS C:\> Add-NetLbfoTeamNIC -Team bond_bond-mgt -VlanID 20 -Name bond-mgt.20
    PS C:\> Get-NetAdapter
    PS C:\> netsh interface ip set address bond-mgt.20 static 192.168.0.10/24
    Code block. Windows IP Settings
  1. Run ncpa.cpl from the Windows Run menu to check the interface status.

First connection(kr-south)

If there is no local subnet connected to the Bare Metal Server initially, and you are adding the first connection, proceed according to the guide below.

Caution

This guide is for kr-south (Korean region) when adding the first local Subnet connection to the server.

Linux - Setting up Subnet on Ubuntu

To add a local Subnet on the Ubuntu operating system and proceed with network settings, follow the steps below.

  1. After adding a new Vlan, set the IP.

    • Change the ID and IP in the example code to the assigned ID and IP.
      Color mode
      [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
      network:
          bonds:
              bond-mgt:
                  interfaces:  
                  - ens2f1  
                  - ens4f1  
                  mtu: 1500
                  parameters:
                      mii-monitor-interval: 100
                      mode: active-backup
                      transmit-hash-policy: layer2
          ethernets:
              ens2f1:
                  match:
                  macaddress: 68:05:ca:d4:09:91
                  mtu: 1500
                  set-name: ens2f1
              ens4f1:
                  match:
                  macaddress: 68:05:ca:d4:09:01
                  mtu: 1500
                  set-name: ens4f1
          vlans:
              bond-mgt.20:
              addresses:
                  - 192.168.0.10/24
                  id: 20
                  link: bond-mgt
                  mtu: 1500
          vlans:
              bond-mgt.21: // Enter the Vlan ID you checked on the Console instead of 21.
              addresses:
                  - 192.168.0.20/24 // Set to the local Subnet IP confirmed in the Console.
                  id: 21    // Set it to the Vlan ID verified in the Console.
                  link: bond-mgt
                  mtu: 1500
      [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
      network:
          bonds:
              bond-mgt:
                  interfaces:  
                  - ens2f1  
                  - ens4f1  
                  mtu: 1500
                  parameters:
                      mii-monitor-interval: 100
                      mode: active-backup
                      transmit-hash-policy: layer2
          ethernets:
              ens2f1:
                  match:
                  macaddress: 68:05:ca:d4:09:91
                  mtu: 1500
                  set-name: ens2f1
              ens4f1:
                  match:
                  macaddress: 68:05:ca:d4:09:01
                  mtu: 1500
                  set-name: ens4f1
          vlans:
              bond-mgt.20:
              addresses:
                  - 192.168.0.10/24
                  id: 20
                  link: bond-mgt
                  mtu: 1500
          vlans:
              bond-mgt.21: // Enter the Vlan ID you checked on the Console instead of 21.
              addresses:
                  - 192.168.0.20/24 // Set to the local Subnet IP confirmed in the Console.
                  id: 21    // Set it to the Vlan ID verified in the Console.
                  link: bond-mgt
                  mtu: 1500
      Code block. Vlan addition and IP setting
  2. Reflect the modifications in the system.

    Color mode
    # netplan apply
    # netplan apply
    Code block. Reflect changes

  3. Check the interface status.

    Color mode
    # ip a
    or
    # bash /usr/local/bin/ip.sh
    # ip a
    or
    # bash /usr/local/bin/ip.sh
    Code block. Interface lookup

Linux – Setting up Subnet on CentOS/Red Hat

After adding a local Subnet on CentOS/Red Hat operating system, follow the steps below to configure the network.

Caution
If you add a local Subnet and configure the network incorrectly, be careful as the IP information in use may be deleted.
  1. Check the Bond Name for local Subnet.
    Color mode
    # sh /usr/local/bin/ip.sh
    # sh /usr/local/bin/ip.sh
    Code block. Bonding check
  2. Modify the following command and execute.
    Color mode
    #!/usr/bin/bash
    
    IP_ADDR="10.1.1.3/24"   // Set the local Subnet IP as confirmed from the Console.
    VLAN_ID="7"             // Set the Vlan ID confirmed in the console.
    
    BOND_NAME="bond-mgt" // Set the Bond Name confirmed in step 1.
      
    # add vlan
    nmcli conn add type vlan ifname "${BOND_NAME}.${VLAN_ID}" con-name "${BOND_NAME}.${VLAN_ID}" id ${VLAN_ID} dev ${BOND_NAME}
    nmcli con  mod ${BOND_NAME}.${VLAN_ID} con-name "Vlan ${BOND_NAME}.${VLAN_ID}"
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.addresses ${IP_ADDR}
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.method manual
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv6.method "ignore"
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" connect.autoconnect yes
    nmcli con  up  "Vlan ${BOND_NAME}.${VLAN_ID}"
    
    nmcli      device reapply ${BOND_NAME}.${VLAN_ID}
    #!/usr/bin/bash
    
    IP_ADDR="10.1.1.3/24"   // Set the local Subnet IP as confirmed from the Console.
    VLAN_ID="7"             // Set the Vlan ID confirmed in the console.
    
    BOND_NAME="bond-mgt" // Set the Bond Name confirmed in step 1.
      
    # add vlan
    nmcli conn add type vlan ifname "${BOND_NAME}.${VLAN_ID}" con-name "${BOND_NAME}.${VLAN_ID}" id ${VLAN_ID} dev ${BOND_NAME}
    nmcli con  mod ${BOND_NAME}.${VLAN_ID} con-name "Vlan ${BOND_NAME}.${VLAN_ID}"
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.addresses ${IP_ADDR}
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.method manual
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv6.method "ignore"
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" connect.autoconnect yes
    nmcli con  up  "Vlan ${BOND_NAME}.${VLAN_ID}"
    
    nmcli      device reapply ${BOND_NAME}.${VLAN_ID}
    Code block. IP configuration script
  3. Check the interface status.
    Color mode
    # ip a
    or
    # bash /usr/local/bin/ip.sh
    # ip a
    or
    # bash /usr/local/bin/ip.sh
    Code block. Interface lookup

Setting up Subnet on Windows

After adding a local Subnet on the Windows operating system, follow these steps to configure the network.

  1. Windows Start icon, right-click, then run the Windows PowerShell (Administrator) program.

  2. Check the Teaming name for local Subnet.

    Color mode
    PS C:\> Get-NetAdapter
    PS C:\> Get-NetAdapter
    Code block. Windows interface check

  3. After adding a new VLAN, set the IP.

    • Enter the Teaming name confirmed in step 2, and the Vlan ID and Local Subnet IP confirmed in the Console.
      Color mode
      PS C:\> Add-NetLbfoTeamNIC -Team bond_bond-mgt -VlanID 20 -Name bond-mgt.20
      PS C:\> Get-NetAdapter
      PS C:\> netsh interface ip set address bond-mgt.20 static 192.168.0.10/24
      PS C:\> Add-NetLbfoTeamNIC -Team bond_bond-mgt -VlanID 20 -Name bond-mgt.20
      PS C:\> Get-NetAdapter
      PS C:\> netsh interface ip set address bond-mgt.20 static 192.168.0.10/24
      Code block. Create Teaming
  4. In the Windows Start menu, run ncpa.cpl to check the interface status.

    image

Add second connection (kr-west, kr-south)

If there is a local Subnet connected to the Bare Metal Server, the guide for the second additional connection is as follows.

Because a Bonding was already created when connecting the first local Subnet, there is no procedure to create Bonding when connecting the second local Subnet.

Please refer to the details below.

Notice
This is a guide that can be applied commonly to kr-west, kr-south.

Linux - Setting up Subnet on Ubuntu

To add a local Subnet on the Ubuntu operating system and proceed with network configuration, follow the steps below.

  1. After adding a new Vlan, set the IP.

    • Change the ID and IP of the example code to the assigned ID and IP.
      Color mode
      [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
      network:
          bonds:
              bond-mgt:
                  interfaces:  
                  - ens2f1  
                  - ens4f1  
                  mtu: 1500
                  parameters:
                      mii-monitor-interval: 100
                      mode: active-backup
                      transmit-hash-policy: layer2
          ethernets:
              ens2f1:
                  match:
                  macaddress: 68:05:ca:d4:09:91
                  mtu: 1500
                  set-name: ens2f1
              ens4f1:
                  match:
                  macaddress: 68:05:ca:d4:09:01
                  mtu: 1500
                  set-name: ens4f1
          vlans:
              bond-mgt.20:
              addresses:
                  - 192.168.0.10/24
                  id: 20
                  link: bond-mgt
                  mtu: 1500
          vlans:
              bond-mgt.21: // Enter the Vlan ID you checked on the console instead of 21.
              addresses:
                  - 192.168.0.20/24 // Set it to the local Subnet IP confirmed from the Console.
                  id: 21    // Set it to the Vlan ID confirmed in the Console.
                  link: bond-mgt
                  mtu: 1500
      [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
      network:
          bonds:
              bond-mgt:
                  interfaces:  
                  - ens2f1  
                  - ens4f1  
                  mtu: 1500
                  parameters:
                      mii-monitor-interval: 100
                      mode: active-backup
                      transmit-hash-policy: layer2
          ethernets:
              ens2f1:
                  match:
                  macaddress: 68:05:ca:d4:09:91
                  mtu: 1500
                  set-name: ens2f1
              ens4f1:
                  match:
                  macaddress: 68:05:ca:d4:09:01
                  mtu: 1500
                  set-name: ens4f1
          vlans:
              bond-mgt.20:
              addresses:
                  - 192.168.0.10/24
                  id: 20
                  link: bond-mgt
                  mtu: 1500
          vlans:
              bond-mgt.21: // Enter the Vlan ID you checked on the console instead of 21.
              addresses:
                  - 192.168.0.20/24 // Set it to the local Subnet IP confirmed from the Console.
                  id: 21    // Set it to the Vlan ID confirmed in the Console.
                  link: bond-mgt
                  mtu: 1500
      Code block. Vlan addition and IP configuration
  2. Apply the changes to the system.

    Color mode
    # netplan apply
    # netplan apply
    Code block. Reflect changes

  3. Check the interface status.

    Color mode
    # ip a
    or
    # bash /usr/local/bin/ip.sh
    # ip a
    or
    # bash /usr/local/bin/ip.sh
    Code block. Interface lookup

Linux – Setting up Subnet on CentOS/Red Hat

After adding a local Subnet on CentOS/Red Hat operating system, follow the steps below to configure the network.

Caution
If you add a local Subnet and configure the network incorrectly, be careful as the IP information in use may be deleted.
  1. Check the Bond Name for the local Subnet.
    Color mode
    # sh /usr/local/bin/ip.sh
    # sh /usr/local/bin/ip.sh
    Code block. Bonding check
  2. Modify the following command and execute.
    Color mode
    #!/usr/bin/bash
    
    IP_ADDR="10.1.1.3/24"   // Set the local Subnet IP as confirmed from the console.
    VLAN_ID="7"             // Set the Vlan ID confirmed in the console.
    
    BOND_NAME="bond-mgt" // Set the Bond Name confirmed in step 1.
      
    # add vlan
    nmcli conn add type vlan ifname "${BOND_NAME}.${VLAN_ID}" con-name "${BOND_NAME}.${VLAN_ID}" id ${VLAN_ID} dev ${BOND_NAME}
    nmcli con  mod ${BOND_NAME}.${VLAN_ID} con-name "Vlan ${BOND_NAME}.${VLAN_ID}"
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.addresses ${IP_ADDR}
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.method manual
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv6.method "ignore"
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" connect.autoconnect yes
    nmcli con  up  "Vlan ${BOND_NAME}.${VLAN_ID}"
    
    nmcli      device reapply ${BOND_NAME}.${VLAN_ID}
    #!/usr/bin/bash
    
    IP_ADDR="10.1.1.3/24"   // Set the local Subnet IP as confirmed from the console.
    VLAN_ID="7"             // Set the Vlan ID confirmed in the console.
    
    BOND_NAME="bond-mgt" // Set the Bond Name confirmed in step 1.
      
    # add vlan
    nmcli conn add type vlan ifname "${BOND_NAME}.${VLAN_ID}" con-name "${BOND_NAME}.${VLAN_ID}" id ${VLAN_ID} dev ${BOND_NAME}
    nmcli con  mod ${BOND_NAME}.${VLAN_ID} con-name "Vlan ${BOND_NAME}.${VLAN_ID}"
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.addresses ${IP_ADDR}
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.method manual
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv6.method "ignore"
    nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" connect.autoconnect yes
    nmcli con  up  "Vlan ${BOND_NAME}.${VLAN_ID}"
    
    nmcli      device reapply ${BOND_NAME}.${VLAN_ID}
    Code block. IP configuration script
  3. Check the interface status.
    Color mode
    # ip a
    or
    # bash /usr/local/bin/ip.sh
    # ip a
    or
    # bash /usr/local/bin/ip.sh
    Code block. Interface lookup

Setting Subnet in Windows

After adding a local Subnet in the Windows operating system, follow the steps below to set up the network.

  1. Right-click the Windows Start icon, then run the Windows PowerShell (Administrator) program.

  2. Check the Teaming name for local Subnet.

    Color mode
    PS C:\> Get-NetAdapter
    PS C:\> Get-NetAdapter
    Code block. Windows interface check

  3. After adding a new VLAN, set the IP.

    • Enter the Teaming name confirmed in step 2, the Vlan ID and Local Subnet IP confirmed in the Console.
      Color mode
      PS C:\> Add-NetLbfoTeamNIC -Team bond_bond-mgt -VlanID 20 -Name bond-mgt.20
      PS C:\> Get-NetAdapter
      PS C:\> netsh interface ip set address bond-mgt.20 static 192.168.0.10/24
      PS C:\> Add-NetLbfoTeamNIC -Team bond_bond-mgt -VlanID 20 -Name bond-mgt.20
      PS C:\> Get-NetAdapter
      PS C:\> netsh interface ip set address bond-mgt.20 static 192.168.0.10/24
      Code block. Teaming creation
  4. In the Windows Run menu, execute ncpa.cpl to check the interface status.

    Image

IP Change

IP can be changed for migration, server replacement, etc.

Caution
  • If you proceed with changing the IP, you will no longer be able to communicate with that IP, and you cannot cancel the IP change while it is in progress.
  • If it is a server running the Load Balancer service, you must delete the existing IP from the LB server group and directly add the changed IP as a member of the LB server group.
  • Servers using Public NAT, Privat NAT must disable and reconfigure Public NAT, Privat NAT after an IP change.
  • If you are using Public NAT, Privat NAT, first disable the use of Public NAT, Privat NAT, complete the IP change, and then set it again.
  • Public NAT, Privat NAT usage can be changed by clicking the Edit button of Public NAT IP, Privat NAT on the Bare Metal Server Details page.

If you want to change the IP, follow the steps below.

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

  2. Click the Bare Metal Server menu on the Service Home page. You will be taken to the Bare Metal Server list page.

  3. Bare Metal Server List page, click the server to change the IP. Bare Metal Server Details page will be opened.

  4. Click the Edit button next to the IP item on the Bare Metal Server Details page.

  5. When the popup notifying IP modification opens, click the Confirm button. The IP Change popup opens.

  6. IP change popup window’s Step 1, Step 2, Step 3Proceed with the tasks in order.

    Guide
    • When changing the IP, the detailed configuration method of the IP change step varies depending on the subnet of the IP to be changed. Be sure to refer to the following example and proceed with the work for each step.
    • When each progress step is completed successfully, the task status in the upper right corner is displayed as Completed, and you can proceed to the next step.
    • When performing the final check of Step 3, it is recommended to restart the server and then proceed with the inspection.

  7. After confirming that all tasks have been completed successfully, click the Confirm button.

Change to the same Subnet’s IP

Explains how to set IP per operating system when the IP to be changed uses the same subnet.

Linux – centos/redhat operating system

Step 1

Follow the next procedure and proceed with Step 1 work.

  1. Select the Subnet to change.
  2. Enter the IP to change.
  3. IP allocation request Click the button.
  4. When the popup notifying IP change confirmation opens, click the Confirm button.
    • If the task completes successfully, the task status in the upper right corner will be displayed as Completed.
      Caution
      If you proceed with the IP allocation request of Step 1, you cannot cancel or restore the IP change.

Step 2

Follow the next procedure and proceed with Step 2 work.

  1. Connect to the IP change target server using NAT IP for the IP change operation.

    Notice
    To prevent situations where communication is impossible during operation, it is recommended to connect via another Virtual Server or Bare Metal Server created in the same subnet.

  2. Step 1 Enter the assigned IP and set the IP to be changed on the server.

    • In the following example, replace 172.17.34.150 with the assigned IP.
    • After checking the information of the Interface you want to change on the server, enter it instead of the example bond-srv.9.
      Color mode
      # nmcli con mod "Vlan bond-srv.9" ipv4.addresses 172.17.34.150/24
      # nmcli con mod "Vlan bond-srv.9" ipv4.method manual
      # nmcli  device reapply bond-srv.9
      # nmcli con mod "Vlan bond-srv.9" ipv4.addresses 172.17.34.150/24
      # nmcli con mod "Vlan bond-srv.9" ipv4.method manual
      # nmcli  device reapply bond-srv.9
      Code block. IP settings to change
      Guide
      • If you set the IP, the terminal session will be disconnected.
      • Step 2 After completing the task, if the task status changes to Completed, you can reconnect to the terminal.
  3. When all tasks are completed, select the task completion checkbox of Step 2 in the IP Change popup window.

    • If the task completes successfully, the task status in the upper right corner will be displayed as Completed.
      Guide
      • If the task status of Step 2 has been changed to Completed but there is still an issue with terminal connection, go to the All Services > Management > Support Center Contact menu and inquire.

Step 3

Follow the next procedure and proceed with Step 3 work.

  1. Connect to the target server for IP change using NAT IP and check the communication status.

    • Use the following command to check again whether the previous configuration information remains and whether it has been changed correctly. If you can connect normally to the IP change target server, the changed IP is in normal communication status.
      Color mode
      # bash /usr/local/bin/ip.sh
      # bash /usr/local/bin/ip.sh
      Code block. Communication status check
      Reference
      NAT IP does not change.
  2. Once all tasks are completed, restart the server and then perform a final check.

    Reference
    It is recommended to perform the final check after restarting the server.

  3. If there are no issues in the final inspection results, select the work completion checkbox of Step 3 in the IP Change popup window.

Linux – Ubuntu Operating System

Step 1

Follow the next procedure and proceed with Step 1 work.

  1. Select the Subnet to change.
  2. Enter the IP to change.
  3. IP Allocation Request Click the button.
  4. If a popup notifying IP change confirmation opens, click the Confirm button.
    • If the task completes successfully, the task status in the upper right corner will be displayed as Completed.
      Caution
      If you proceed with the IP allocation request of Step 1, you cannot cancel or restore the IP change.

Step 2

Proceed with Step 2 work following the next procedure.

  1. To perform the IP change operation, connect to the IP change target server using a NAT IP.

    Guide
    To prevent situations where communication is impossible during operation, it is recommended to connect via another Virtual Server or Bare Metal Server created in the same subnet.

  2. Step 1Enter the IP assigned in Step 1 and set the IP to be changed on the server.

    • In the following example, replace 172.17.34.150/24 with the assigned IP.
    • After checking the information of the Interface you want to change on the server, enter it instead of the example bond-srv.9.
      Color mode
      [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
      network:
          bonds:
          ...................... omitted
          ethernets:
          ...................... omitted
          vlans:
              bond-srv.9:
              addresses:
                  - 172.17.34.150/24   # Enter the IP assigned in Step1.
                  gateway4: 172.17.34.2
                  id: 9
                  link: bond-srv
                  mtu: 1500
              bond-srv.350:
                  addresses:
                  - 172.16.87.150/24
                  routes:
                  - to: 172.17.87.0/24
                    via: 172.16.87.1
      - to: 172.17.87.0/24
                    via: 172.16.87.1
                  id: 350
                  link: bond-srv
      [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
      network:
          bonds:
          ...................... omitted
          ethernets:
          ...................... omitted
          vlans:
              bond-srv.9:
              addresses:
                  - 172.17.34.150/24   # Enter the IP assigned in Step1.
                  gateway4: 172.17.34.2
                  id: 9
                  link: bond-srv
                  mtu: 1500
              bond-srv.350:
                  addresses:
                  - 172.16.87.150/24
                  routes:
                  - to: 172.17.87.0/24
                    via: 172.16.87.1
      - to: 172.17.87.0/24
                    via: 172.16.87.1
                  id: 350
                  link: bond-srv
      Code block. IP settings to change
  3. Use the Netplan apply command to apply the changes to the system.

    Color mode
    [root@localhost ~]# netplan apply
    [root@localhost ~]# netplan apply
    Code block. Run Netplan apply
    Notice
    • If you set the IP, the terminal session will be disconnected.
    • Step 2 After completing the task, if the task status changes to Completed, you can reconnect to the terminal.

  4. When all tasks are completed, select the task completion checkbox of Step 2 in the IP Change popup window.

    • If the task completes successfully, the task status in the upper right corner will be displayed as Completed.
      Notice
      • If the task status of Step 2 has been changed to Completed but there is an issue with terminal access, go to the All Services > Management > Support Center Contact menu and inquire.

Step 3

Follow the next procedure and proceed with Step 3 work.

  1. Check the communication status by connecting to the IP change target server with NAT IP.

    • Use the following command to check again whether the pre-change configuration information remains and whether it has been changed correctly. If you can connect normally to the IP change target server, the changed IP is in normal communication status.
      Color mode
      # bash /usr/local/bin/ip.sh
      # bash /usr/local/bin/ip.sh
      Code block. Communication status check
      Reference
      NAT IP does not change.
  2. Once all tasks are completed, restart the server and then perform a final check.

    Reference
    It is recommended to perform the final check after restarting the server.

  3. If there are no issues in the final inspection results, select the work completion checkbox of Step 3 in the IP Change popup window.

Windows Operating System

Step 1

Follow the next procedure and proceed with Step 1 work.

  1. Select the Subnet to change.
  2. Please enter the IP to change.
  3. IP Allocation Request Click the button.
  4. When the popup notifying IP change confirmation opens, click the Confirm button.
    • If the task completes successfully, the task status in the upper right corner will be displayed as Completed.
      Caution
      If you proceed with Step 1’s IP allocation request, you cannot cancel or restore the IP change.

Step 2

Follow the next procedure and proceed with Step 2 work.

  1. Connect to the target server for IP change using NAT IP for the IP change operation.

    Guide
    To prevent situations where communication is impossible during operation, it is recommended to connect via another Virtual Server or Bare Metal Server created in the same subnet.

  2. Right-click the Windows Start icon, then run Windows PowerShell (Administrator).

  3. Step 1Enter the assigned IP and set the IP to be changed on the server.

    • In the following example, replace 172.17.34.150 with the assigned IP.
      Color mode
      PS C:\> netsh interface ip set address "bond-srv.20" static 172.17.34.150 255.255.255.0
      PS C:\> netsh interface ip set address "bond-srv.20" static 172.17.34.150 255.255.255.0
      Code block. IP settings to change
      Notice
      • If you set the IP, the terminal session will be disconnected.
      • Step 2 After completing the task, if the task status changes to Completed, you can reconnect to the terminal.
  4. When all tasks are completed, select the task completion checkbox of Step 2 in the IP change popup window.

    • If the task completes successfully, the task status in the upper right corner will be displayed as Completed.
      Notice
      • Step 2’s task status changed to Completed, and if there is an issue with terminal access, go to the All Services > Management > Support Center’s Contact Us menu and inquire.

Step 3

Follow the next procedure and proceed with Step 3 work.

  1. Connect to the server targeted for IP change using NAT IP and check the communication status.

    • Use the following command to check again whether the previous configuration information remains and whether it has been changed correctly. If you can connect normally to the IP change target server, the changed IP is in normal communication status.
      Color mode
      PS C:\> Get-NetIPAddress | Format-Table
      PS C:\> Get-NetIPAddress | Format-Table
      Code block. Communication status check
      Reference
      NAT IP does not change.
  2. Once all tasks are completed, restart the server and then perform a final check.

    Reference
    It is recommended to perform the final check after restarting the server.

  3. If there are no issues with the final inspection results, select the work completion checkbox of Step 3 in the IP change popup window.

Change to IP of another Subnet

Explains how to set IP per operating system when the IP to be changed uses a different subnet.

Linux – centos/redhat operating system

Step 1

Follow the next procedure and proceed with Step 1 work.

  1. Please select the Subnet to change.
  2. Enter the IP to change.
  3. Click the IP Allocation Request button.
  4. When the popup that notifies IP change confirmation opens, click the Confirm button.
    • If the task completes successfully, Check Vlan ID, Check Default Gateway information is displayed, and the task status at the top right is shown as Completed.
      Caution
      If you proceed with the IP allocation request of Step 1, you cannot cancel or restore the IP change.

Step 2

Proceed with Step 2 work following the next procedure.

  1. Connect to the IP change target server with a NAT IP to perform the IP change operation.

    Guide
    To prevent situations where communication is impossible during operation, it is recommended to connect via another Virtual Server or Bare Metal Server created in the same subnet.

  2. Add a new VLAN and set the IP to add the IP to the server.

    • Add VLAN: Create the interface of the Vlan ID confirmed in Step 1. In the following example, enter the assigned ID instead of 20.
  • IP Settings: Enter the IP assigned in Step 1. In the following example, replace 192.168.0.10/24 with the assigned IP.
    Color mode
    # nmcli conn add type vlan ifname "bond-srv.20" con-name "bond-srv.20" id 20 dev bond-srv
    # nmcli con mod bond-srv.20 con-name "Vlan bond-srv.20"
    # nmcli con mod "Vlan bond-srv.20" ipv4.addresses 192.168.0.10/24
    # nmcli con mod "Vlan bond-srv.20" ipv4.method manual
    # nmcli con mod "Vlan bond-srv.20" ipv6.method "ignore"
    # nmcli con up  "Vlan bond-srv.20"
    # nmcli conn add type vlan ifname "bond-srv.20" con-name "bond-srv.20" id 20 dev bond-srv
    # nmcli con mod bond-srv.20 con-name "Vlan bond-srv.20"
    # nmcli con mod "Vlan bond-srv.20" ipv4.addresses 192.168.0.10/24
    # nmcli con mod "Vlan bond-srv.20" ipv4.method manual
    # nmcli con mod "Vlan bond-srv.20" ipv6.method "ignore"
    # nmcli con up  "Vlan bond-srv.20"
    Code block. IP settings to change
  1. Set the Default Gateway on the new VLAN.

    • Default gateway setting: Enter the Default gateway IP assigned in Step 1. In the following example, replace 192.168.0.1 with the assigned Default gateway IP.
      Color mode
      # nmcli con mod "Vlan bond-srv.20"  ipv4.gateway 192.168.0.1
      # nmcli device reapply bond-srv.20
      # nmcli con mod "Vlan bond-srv.20"  ipv4.gateway 192.168.0.1
      # nmcli device reapply bond-srv.20
      Code block. IP settings to change
      Guide
      • If you set the Default Gateway on a new VLAN, the terminal session will be disconnected.
      • Step 2 After completing the task, if the task status changes to Completed, you can reconnect to the terminal.
  2. When all tasks are completed, select the task completion checkbox of Step 2 in the IP Change popup window.

    • If the task completes successfully, the task status in the upper right corner will be displayed as Completed.
      Guide
      • Step 2’s work status changed to Completed, but if there is still an issue with terminal access, go to the All Services > Management > Support Center Contact menu and inquire.

Step 3

Follow the next procedure and proceed with Step 3 work.

  1. Connect to the target server for IP change using NAT IP.

  2. After checking the Default Gateway IP of the existing (pre-change) interface, delete it.

    • In the following example, enter the verified IP instead of 192.168.10.1.
      Color mode
      # ip route del   default  via 192.168.10.1
      # ip route del   default  via 192.168.10.1
      Code block. Delete Default Gateway IP of existing interface
  3. Connect to the IP change target server with a NAT IP and check the communication status.

    • Use the following command to check again whether the previous configuration information remains and whether it has been changed correctly. If you can connect normally to the IP change target server, the changed IP is in normal communication status.
      Color mode
      # netstat nr
      # bash /usr/local/bin/ip.sh
      # netstat nr
      # bash /usr/local/bin/ip.sh
      Code block. Communication status check
      Reference
      NAT IP does not change.
  4. After checking the VLAN information of the existing IP, delete it from the server.

    • In the following example, replace 30 with the ID you verified.
      Color mode
      # nmcli con delete "Vlan bond-srv.30"
      # nmcli con delete "Vlan bond-srv.30"
      Code block. Delete Vlan information of existing IP
  5. Once all tasks are completed, restart the server and then perform a final check.

    Reference
    It is recommended to perform the final check after restarting the server.

  6. If there is no issue with the final inspection results, select the work completion checkbox of Step 3 in the IP Change popup.

Linux – Ubuntu operating system

Step 1

Follow the next procedure and proceed with Step 1 work.

  1. Please select the Subnet to change.
  2. Enter the IP to change.
  3. IP allocation request Click the button.
  4. When the popup notifying IP change confirmation opens, click the Confirm button.
    • If the task completes successfully, Check Vlan ID, Check Default Gateway information is displayed, and the task status at the top right is shown as Completed.
      Caution
      Step 1’s IP allocation request cannot be cancelled or restored once processed.

Step 2

Follow the next procedure and proceed with Step 2 work.

  1. Connect to the IP change target server using a NAT IP for the IP change operation.

    Guide
    To prevent situations where communication is impossible during operation, it is recommended to connect via another Virtual Server or Bare Metal Server created in the same subnet.

  2. To add the IP to be changed to the server, add a new VLAN and set the IP and Default Gateway.

    • This is the part where content is added below the Step 1 work description in the following example.
    • In the following example, enter the assigned ID and IP instead of ID and IP.
      Color mode
      [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
      network:
          bonds:
          ...................... omitted
          ethernets:
          ...................... omitted
          vlans:
              bond-srv.9:
              addresses:
                  - 172.17.34.150/24
      
                  gateway4: 172.17.34.2
                  id: 9
                  link: bond-srv
                  mtu: 1500
              bond-srv.350:
                  addresses:
                  - 172.16.87.150/24
                  routes:
                  - to: 172.17.87.0/24
                    via: 172.16.87.1
      - to: 172.17.87.0/24
                    via: 172.16.87.1
                  id: 350
                  link: bond-srv
      
      # Create the interface of the Vlan ID confirmed in Step1.
      # Enter the IP assigned in Step1.
      # Enter the Default gateway IP assigned from Step1.
      bond-srv.20:
              addresses:
                  - 192.168.0.10/24
                  gateway4: 192.168.0.1
                  id: 20
                  link: bond-srv
                  mtu: 1500
      [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
      network:
          bonds:
          ...................... omitted
          ethernets:
          ...................... omitted
          vlans:
              bond-srv.9:
              addresses:
                  - 172.17.34.150/24
      
                  gateway4: 172.17.34.2
                  id: 9
                  link: bond-srv
                  mtu: 1500
              bond-srv.350:
                  addresses:
                  - 172.16.87.150/24
                  routes:
                  - to: 172.17.87.0/24
                    via: 172.16.87.1
      - to: 172.17.87.0/24
                    via: 172.16.87.1
                  id: 350
                  link: bond-srv
      
      # Create the interface of the Vlan ID confirmed in Step1.
      # Enter the IP assigned in Step1.
      # Enter the Default gateway IP assigned from Step1.
      bond-srv.20:
              addresses:
                  - 192.168.0.10/24
                  gateway4: 192.168.0.1
                  id: 20
                  link: bond-srv
                  mtu: 1500
      Code block. IP settings to change
  3. Use the Netplan apply command to apply the changes to the system.

    Color mode
    [root@localhost ~]# netplan apply
    [root@localhost ~]# netplan apply
    Code block. Netplan apply execution
    Notice
    • If you set a new Default Gateway, the terminal session will be disconnected.
    • Step 2 After completing the task, if the task status changes to Completed, you can reconnect to the terminal.

  4. When all tasks are completed, select the task completion checkbox of Step 2 in the IP Change popup window.

    • If the task completes successfully, the task status in the upper right corner will be displayed as Completed.
      Notice
      • If the task status of Step 2 has been changed to Completed but there is still an issue with terminal access, go to the All Services > Management > Support Center Contact menu and inquire.

Step 3

Follow the next procedure and proceed with Step 3 work.

  1. Connect to the target server for IP change using NAT IP.

  2. After checking the Default Gateway IP of the existing (pre-change) interface, delete it.

    • In the following example, the Delete this line row is the part that gets deleted.
      Color mode
      [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
      network:
          bonds:
          ...................... omitted
          ethernets:
          ...................... Omitted
          vlans:
              bond-srv.9:
              addresses:
                  - 172.17.34.150/24
                  gateway4: 172.17.34.2    # Delete this line
                  id: 9
                  link: bond-srv
                  mtu: 1500
              bond-srv.350:
                  addresses:
                  - 172.16.87.150/24
                  routes:
                  - to: 172.17.87.0/24
                    via: 172.16.87.1
      - to: 172.17.87.0/24
                    via: 172.16.87.1
                  id: 350
                  link: bond-srv
      
      bond-srv.20:
              addresses:
                  - 192.168.0.10/24
                  gateway4: 192.168.0.1
                  id: 20
                  link: bond-srv
                  mtu: 1500
      [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
      network:
          bonds:
          ...................... omitted
          ethernets:
          ...................... Omitted
          vlans:
              bond-srv.9:
              addresses:
                  - 172.17.34.150/24
                  gateway4: 172.17.34.2    # Delete this line
                  id: 9
                  link: bond-srv
                  mtu: 1500
              bond-srv.350:
                  addresses:
                  - 172.16.87.150/24
                  routes:
                  - to: 172.17.87.0/24
                    via: 172.16.87.1
      - to: 172.17.87.0/24
                    via: 172.16.87.1
                  id: 350
                  link: bond-srv
      
      bond-srv.20:
              addresses:
                  - 192.168.0.10/24
                  gateway4: 192.168.0.1
                  id: 20
                  link: bond-srv
                  mtu: 1500
      Code block. Delete Default Gateway IP of existing interface
  3. Connect to the IP change target server using NAT IP and check the communication status.

    • Use the following command to check again whether the previous configuration information remains and whether it has been changed correctly. If you can connect normally to the IP change target server, the changed IP is in normal communication state.
      Color mode
      # netstat nr
      # bash /usr/local/bin/ip.sh
      # netstat nr
      # bash /usr/local/bin/ip.sh
      Code block. Communication status check
      Reference
      NAT IP does not change.
  4. Delete the existing IP.

    • In the following example, the Delete this line row is the part that gets deleted.
      Color mode
      [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
      network:
          bonds:
          ...................... omitted
          ethernets:
          ...................... omitted
          vlans:
              bond-srv.9:                   #Delete this line
              addresses:                    # delete this line
                  - 172.17.34.150/24        #Delete this line
                  gateway4: 172.17.34.2     #Delete this line
                  id: 9                     #Delete this line
                  link: bond-srv            #Delete this line
                  mtu: 1500                 #Delete this line
              bond-srv.350:
                  addresses:
                  - 172.16.87.150/24
                  routes:
                  - to: 172.17.87.0/24
                    via: 172.16.87.1
      - to: 172.17.87.0/24
                    via: 172.16.87.1
                  id: 350
                  link: bond-srv
      
      bond-srv.20:
              addresses:
                  - 192.168.0.10/24
                  gateway4: 192.168.0.1
                  id: 20
                  link: bond-srv
                  mtu: 1
      [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
      network:
          bonds:
          ...................... omitted
          ethernets:
          ...................... omitted
          vlans:
              bond-srv.9:                   #Delete this line
              addresses:                    # delete this line
                  - 172.17.34.150/24        #Delete this line
                  gateway4: 172.17.34.2     #Delete this line
                  id: 9                     #Delete this line
                  link: bond-srv            #Delete this line
                  mtu: 1500                 #Delete this line
              bond-srv.350:
                  addresses:
                  - 172.16.87.150/24
                  routes:
                  - to: 172.17.87.0/24
                    via: 172.16.87.1
      - to: 172.17.87.0/24
                    via: 172.16.87.1
                  id: 350
                  link: bond-srv
      
      bond-srv.20:
              addresses:
                  - 192.168.0.10/24
                  gateway4: 192.168.0.1
                  id: 20
                  link: bond-srv
                  mtu: 1
      Code block. Delete existing IP
  5. Apply the modified items to the system.

    Color mode
    [root@localhost ~]# netplan apply
    [root@localhost ~]#  ip link delete bond-srv.9 # Additional actions when VLAN is deleted
    [root@localhost ~]# netplan apply
    [root@localhost ~]#  ip link delete bond-srv.9 # Additional actions when VLAN is deleted
    Code block. Apply changes

  6. When all tasks are completed, restart the server and then conduct a final check.

Reference
It is recommended to perform the final check after restarting the server.
  1. If there are no issues in the final inspection results, select the work completion checkbox of Step 3 in the IP Change popup window.

Windows Operating System

Step 1

Follow the next procedure and proceed with Step 1 work.

  1. Select the Subnet to change.
  2. Enter the IP to change.
  3. IP Allocation Request Click the button.
  4. When the popup that notifies IP change confirmation opens, click the Confirm button.
    • If the task completes successfully, Check Vlan ID, Check Default Gateway information is displayed, and the task status at the top right is shown as Completed.
      Caution
      If you proceed with the IP allocation request of Step 1, you cannot cancel or revert the IP change.

Step 2

Proceed with Step 2 work following the next procedure.

  1. Connect to the IP change target server using NAT IP for the IP change operation.

    Guide
    To prevent situations where communication is impossible during operation, it is recommended to connect via another Virtual Server or Bare Metal Server created in the same subnet.

  2. Windows Start icon, right-click, then run Windows PowerShell (Administrator).

  3. Add a VLAN and set the IP and default gateway.

    • Add VLAN: Create the interface for the Vlan ID identified in Step 1. In the following example, replace 20 with the assigned ID.
    • IP setting: Enter the IP assigned in Step 1. In the following example, replace 46 with the ifindex confirmed by Get-NetAdapter, and replace 192.168.0.10 with the assigned IP.
    • Default gateway setting: Enter the assigned Default gateway IP from Step 1. In the following example, replace 192.168.0.1 with the assigned Default gateway IP.
      Color mode
      PS C:\> Add-NetLbfoTeamNIC -Team bond_bond-srv -VlanID 20 -Name bond-srv.20 -Confirm:$false
      PS C:\> Get-NetAdapter
      PS C:\> New-NetIPAddress -InterfaceIndex 46 -IPAddress 192.168.0.10 -PrefixLength 24 defaultgateway 192.168.0.1
      PS C:\> Add-NetLbfoTeamNIC -Team bond_bond-srv -VlanID 20 -Name bond-srv.20 -Confirm:$false
      PS C:\> Get-NetAdapter
      PS C:\> New-NetIPAddress -InterfaceIndex 46 -IPAddress 192.168.0.10 -PrefixLength 24 defaultgateway 192.168.0.1
      Code block. IP settings to change
      Guide
      • If you set a new Default Gateway, the terminal session will be disconnected.
      • Step 2 After completing the task, if the task status changes to Completed, you can reconnect to the terminal.
  4. When all tasks are completed, select the task completion checkbox of Step 2 in the IP Change popup window.

    • If the task completes successfully, the task status in the upper right corner will be displayed as Completed.
      Guide
      • If the work status of Step 2 has been changed to Completed but there is still an issue with terminal access, go to the All Services > Management > Support Center Contact menu and inquire.

Step 3

Follow the next procedure and proceed with Step 3 work.

  1. Connect to the IP change target server using NAT IP.

  2. Run the interface index (ifindex) to check the existing Default Gateway IP.

    Color mode
    PS C:\> Get-NetAdapter
    Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed
    ----                      --------------------                    ------- ------       ----------             ---------
    bond-srv.9                Microsoft Network Adapter Multiple...#4      30 Up           40-A6-B7-27-96-D5        50 Gbps
    bond-srv                  Microsoft Network Adapter Multiple...#3      19 Up           40-A6-B7-27-96-D5        50 Gbps
    bond-iscsi                Microsoft Network Adapter Multiple...#2      18 Up           40-A6-B7-27-96-D4        50 Gbps
    bond-backup               Microsoft Network Adapter Multiplexo...      22 Up           68-05-CA-C9-EB-88        20 Gbps
    eno2                      Intel(R) Ethernet Connection X722 fo...      12 Disabled     38-68-DD-36-A0-59         1 Gbps
    ens3f0                    Intel(R) Ethernet Network Adapter XX...      11 Up           40-A6-B7-27-96-D4        25 Gbps
    …………………………………………..  omitted
    PS C:\> Get-NetAdapter
    Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed
    ----                      --------------------                    ------- ------       ----------             ---------
    bond-srv.9                Microsoft Network Adapter Multiple...#4      30 Up           40-A6-B7-27-96-D5        50 Gbps
    bond-srv                  Microsoft Network Adapter Multiple...#3      19 Up           40-A6-B7-27-96-D5        50 Gbps
    bond-iscsi                Microsoft Network Adapter Multiple...#2      18 Up           40-A6-B7-27-96-D4        50 Gbps
    bond-backup               Microsoft Network Adapter Multiplexo...      22 Up           68-05-CA-C9-EB-88        20 Gbps
    eno2                      Intel(R) Ethernet Connection X722 fo...      12 Disabled     38-68-DD-36-A0-59         1 Gbps
    ens3f0                    Intel(R) Ethernet Network Adapter XX...      11 Up           40-A6-B7-27-96-D4        25 Gbps
    …………………………………………..  omitted
    Code block. Get-NetAdapter execution
    Color mode
    PS C:\> get-netroute -ifindex 30
    
    ifIndex DestinationPrefix                              NextHop                                  RouteMetric PolicyStore
    ------- -----------------                              -------                                  ----------- -----------
    30      255.255.255.255/32                             0.0.0.0                                          256 ActiveStore
    30      224.0.0.0/4                                    0.0.0.0                                          256 ActiveStore
    30      172.17.35.0/24                                 172.17.35.1                                      256 ActiveStore
    30      172.17.34.255/32                               0.0.0.0                                          256 ActiveStore
    30      172.17.34.14/32                                0.0.0.0                                          256 ActiveStore
    30      172.17.34.0/24                                 0.0.0.0                                          256 ActiveStore
    30      0.0.0.0/0                                      172.17.34.1                                        1 ActiveStore
    PS C:\> get-netroute -ifindex 30
    
    ifIndex DestinationPrefix                              NextHop                                  RouteMetric PolicyStore
    ------- -----------------                              -------                                  ----------- -----------
    30      255.255.255.255/32                             0.0.0.0                                          256 ActiveStore
    30      224.0.0.0/4                                    0.0.0.0                                          256 ActiveStore
    30      172.17.35.0/24                                 172.17.35.1                                      256 ActiveStore
    30      172.17.34.255/32                               0.0.0.0                                          256 ActiveStore
    30      172.17.34.14/32                                0.0.0.0                                          256 ActiveStore
    30      172.17.34.0/24                                 0.0.0.0                                          256 ActiveStore
    30      0.0.0.0/0                                      172.17.34.1                                        1 ActiveStore
    Code block. -ifindex execution

  3. Delete the existing Default Gateway IP.

    • In the following example, replace 30 with the ifindex obtained via Get-NetAdapter, and replace 172.17.34.1 with the IP you verified.
      Color mode
      PS C:\> Remove-NetRoute -ifIndex 30 -DestinationPrefix 0.0.0.0/0 -NextHop 172.17.34.1 -Confirm:$false
      PS C:\> Remove-NetRoute -ifIndex 30 -DestinationPrefix 0.0.0.0/0 -NextHop 172.17.34.1 -Confirm:$false
      Code block. Delete Default Gateway IP
      Color mode
      PS C:\> get-netroute -ifindex 30
      
      ifIndex DestinationPrefix                              NextHop                                  RouteMetric PolicyStore
      ------- -----------------                              -------                                  ----------- -----------
      30      255.255.255.255/32                             0.0.0.0                                          256 ActiveStore
      30      224.0.0.0/4                                    0.0.0.0                                          256 ActiveStore
      30      172.17.34.255/32                               0.0.0.0                                          256 ActiveStore
      30      172.17.34.14/32                                0.0.0.0                                          256 ActiveStore
      30      172.17.34.0/24                                 0.0.0.0                                          256 ActiveStore
      PS C:\> get-netroute -ifindex 30
      
      ifIndex DestinationPrefix                              NextHop                                  RouteMetric PolicyStore
      ------- -----------------                              -------                                  ----------- -----------
      30      255.255.255.255/32                             0.0.0.0                                          256 ActiveStore
      30      224.0.0.0/4                                    0.0.0.0                                          256 ActiveStore
      30      172.17.34.255/32                               0.0.0.0                                          256 ActiveStore
      30      172.17.34.14/32                                0.0.0.0                                          256 ActiveStore
      30      172.17.34.0/24                                 0.0.0.0                                          256 ActiveStore
      Code block. -ifindex execution
      Notice
      • If you delete the existing Default Gateway, the terminal session will be disconnected.
      • Step 2 After completing the task, if the task status changes to Completed, you can reconnect to the terminal.
  4. Check the communication status by connecting to the IP change target server with a NAT IP.

    • Use the following command to check again whether the previous configuration information remains and whether it has been changed correctly. If you can connect normally to the target server whose IP was changed, the changed IP is in normal communication state.
      Color mode
      PS C:\> netstat nr | findstr Default
      PS C:\> Get-NetIPAddress | Format-Table
      PS C:\> netstat nr | findstr Default
      PS C:\> Get-NetIPAddress | Format-Table
      Code block. Communication status check
      Reference
      NAT IP does not change.
  5. Check the existing IP’s VLAN information in the Team information.

    Color mode
    PS C:\> Get-NetLbfoTeam
    
    Name                   : bond_bond-srv
    Members                : {ens6f1, ens3f1}
    TeamNics               : {bond-srv, bond-srv.9}
    TeamingMode            : SwitchIndependent
    LoadBalancingAlgorithm : Dynamic
    Status                 : Up
    
    Name                   : bond_bond-iscsi
    Members                : {ens6f0, ens3f0}
    TeamNics               : bond-iscsi
    TeamingMode            : SwitchIndependent
    LoadBalancingAlgorithm : Dynamic
    Status                 : Up
    
    Name                   : bond_bond-backup
    Members                : {ens2f0, ens4f1}
    TeamNics               : bond-backup
    TeamingMode            : SwitchIndependent
    LoadBalancingAlgorithm : Dynamic
    Status                 : Up
    
    PS C:\> Get-NetAdapter
    
    Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed
    ----                      --------------------                    ------- ------       ----------             ---------
    bond-srv.9                Microsoft Network Adapter Multiple...#4      30 Up           40-A6-B7-27-96-D5        50 Gbps
    bond-srv                  Microsoft Network Adapter Multiple...#3      19 Up           40-A6-B7-27-96-D5        50 Gbps
    bond-iscsi                Microsoft Network Adapter Multiple...#2      18 Up           40-A6-B7-27-96-D4        50 Gbps
    bond-backup               Microsoft Network Adapter Multiplexo...      22 Up           68-05-CA-C9-EB-88        20 Gbps
    eno2                      Intel(R) Ethernet Connection X722 fo...      12 Disabled     38-68-DD-36-A0-59         1 Gbps
    ens3f0                    Intel(R) Ethernet Network Adapter XX...      11 Up           40-A6-B7-27-96-D4        25 Gbps
    …………………………………………..  omitted
    PS C:\> Get-NetLbfoTeam
    
    Name                   : bond_bond-srv
    Members                : {ens6f1, ens3f1}
    TeamNics               : {bond-srv, bond-srv.9}
    TeamingMode            : SwitchIndependent
    LoadBalancingAlgorithm : Dynamic
    Status                 : Up
    
    Name                   : bond_bond-iscsi
    Members                : {ens6f0, ens3f0}
    TeamNics               : bond-iscsi
    TeamingMode            : SwitchIndependent
    LoadBalancingAlgorithm : Dynamic
    Status                 : Up
    
    Name                   : bond_bond-backup
    Members                : {ens2f0, ens4f1}
    TeamNics               : bond-backup
    TeamingMode            : SwitchIndependent
    LoadBalancingAlgorithm : Dynamic
    Status                 : Up
    
    PS C:\> Get-NetAdapter
    
    Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed
    ----                      --------------------                    ------- ------       ----------             ---------
    bond-srv.9                Microsoft Network Adapter Multiple...#4      30 Up           40-A6-B7-27-96-D5        50 Gbps
    bond-srv                  Microsoft Network Adapter Multiple...#3      19 Up           40-A6-B7-27-96-D5        50 Gbps
    bond-iscsi                Microsoft Network Adapter Multiple...#2      18 Up           40-A6-B7-27-96-D4        50 Gbps
    bond-backup               Microsoft Network Adapter Multiplexo...      22 Up           68-05-CA-C9-EB-88        20 Gbps
    eno2                      Intel(R) Ethernet Connection X722 fo...      12 Disabled     38-68-DD-36-A0-59         1 Gbps
    ens3f0                    Intel(R) Ethernet Network Adapter XX...      11 Up           40-A6-B7-27-96-D4        25 Gbps
    …………………………………………..  omitted
    Code block. Run Get-NetLbfoTeam

  6. Delete the existing IP’s VLAN information from the server.

    • In the following example, enter the verified ID instead of 30.
      Color mode
      PS C:\> Remove-NetLbfoTeamNic -Team bond_bond-srv -VlanID 30 -Confirm:$false
      
      PS C:\> Get-NetAdapter
      
      Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed
      ----                      --------------------                    ------- ------       ----------             ---------
      bond-srv                  Microsoft Network Adapter Multiple...#3      19 Up           40-A6-B7-27-96-D5        50 Gbps
      bond-iscsi                Microsoft Network Adapter Multiple...#2      18 Up           40-A6-B7-27-96-D4        50 Gbps
      bond-backup               Microsoft Network Adapter Multiplexo...      22 Up           68-05-CA-C9-EB-88        20 Gbps
      eno2                      Intel(R) Ethernet Connection X722 fo...      12 Disabled     38-68-DD-36-A0-59         1 Gbps
      ens3f0                    Intel(R) Ethernet Network Adapter XX...      11 Up           40-A6-B7-27-96-D4        25 Gbps
      …………………………………………..  omitted
      PS C:\> Remove-NetLbfoTeamNic -Team bond_bond-srv -VlanID 30 -Confirm:$false
      
      PS C:\> Get-NetAdapter
      
      Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed
      ----                      --------------------                    ------- ------       ----------             ---------
      bond-srv                  Microsoft Network Adapter Multiple...#3      19 Up           40-A6-B7-27-96-D5        50 Gbps
      bond-iscsi                Microsoft Network Adapter Multiple...#2      18 Up           40-A6-B7-27-96-D4        50 Gbps
      bond-backup               Microsoft Network Adapter Multiplexo...      22 Up           68-05-CA-C9-EB-88        20 Gbps
      eno2                      Intel(R) Ethernet Connection X722 fo...      12 Disabled     38-68-DD-36-A0-59         1 Gbps
      ens3f0                    Intel(R) Ethernet Network Adapter XX...      11 Up           40-A6-B7-27-96-D4        25 Gbps
      …………………………………………..  omitted
      Code block. Run Get-NetLbfoTeam
  7. Once all tasks are completed, restart the server and then perform a final check.

    Reference
    It is recommended to perform the final check after restarting the server.

  8. If there are no issues in the final inspection results, select the work completion checkbox of Step 3 in the IP Change popup window.

2.4.2.1 - Installing ServiceWatch Agent

Users can install the ServiceWatch Agent on Bare Metal Server to collect custom metrics and logs.

Note
Custom metrics/logs collection via ServiceWatch Agent is currently available only on Samsung Cloud Platform For Enterprise. It will be provided in other offerings in the future.
Caution
Metrics collection via ServiceWatch Agent is classified as custom metrics and incurs charges, unlike default collected metrics. Therefore, it is recommended to remove or disable unnecessary metric collection settings.

ServiceWatch Agent

The agents that need to be installed on Bare Metal Server for ServiceWatch’s custom metrics and log collection can be broadly divided into two types: Prometheus Exporter and Open Telemetry Collector.

CategoryDescription
Prometheus ExporterProvides metrics of specific applications or services in a format that Prometheus can scrape
  • For collecting server OS metrics, Node Exporter for Linux servers and Windows Exporter for Windows servers can be used depending on the OS type.
Open Telemetry CollectorServes as a centralized collector that collects telemetry data such as metrics and logs from distributed systems, processes them (filtering, sampling, etc.), and sends them to multiple backends (e.g., Prometheus, Jaeger, Elasticsearch, etc.)
  • Sends data to ServiceWatch Gateway to enable ServiceWatch to collect metrics and log data.
Table. Description of Prometheus Exporter and Open Telemetry Collector
Note
The ServiceWatch Agent guide can be used in the same way as Virtual Server. For more information, please refer to Virtual Server > ServiceWatch Agent.

Prerequisites for Using ServiceWatch Agent

To use the ServiceWatch Agent, please prepare the prerequisites by referring to Pre-environment Setup for ServiceWatch Agent.

2.4.2.2 - RHEL Repo 설정하기

The Samsung Cloud Platform Console provides the SCP RHEL Repository to support user environments where external access is restricted, such as VPC Private Subnets. By using the SCP RHEL Repository, you can install and download the same packages as the official RHEL Repository.

안내
  • If the user created RHEL before August 2025 through the Samsung Cloud Platform Console, they must modify the RHEL Repository settings.
  • Since the SCP RHEL Repository synchronizes with each Region Local Repository according to an internal schedule, it is recommended to switch to an external public mirror site to apply the latest patches quickly.
  • Samsung Cloud Platform provides the latest repository for the specified major version.

RHEL Repository Configuration Guide

When using RHEL, you can configure the SCP RHEL Repository to install and download the same packages as the official RHEL Repository. To set up the RHEL repository, follow these steps.

  1. On the Virtual Server, as the OS root user, use the cat command to check the /etc/yum.repos.d/scp.rhel8.repo or /etc/yum.repos.d/scp.rhel9.repo configuration.

    Color mode
    cat /etc/yum.repos.d/scp.rhel8.repo
    cat /etc/yum.repos.d/scp.rhel8.repo
    코드블록. repo 설정 확인(RHEL8)
    Color mode
    cat /etc/yum.repos.d/scp.rhel9.repo
    cat /etc/yum.repos.d/scp.rhel9.repo
    코드블록. repo 설정 확인(RHEL9)

    • When checking the configuration file, the following result is displayed.
      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
      코드블록. repo 설정 확인(RHEL8)
      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
      코드블록. repo 설정 확인(RHEL9)
  2. Open the /etc/hosts file using a text editor (e.g., vim).

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

    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
    코드블록. /etc/hosts 파일 설정 변경

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

    Color mode
    yum repolist –v
    yum repolist –v
    코드블록. repository 연결 설정 확인

    • If the RHEL repository is successfully connected, you can view the repository list.
      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
      코드블록. Repository list 확인

2.4.3 - API Reference

API Reference

2.4.4 - CLI Reference

CLI Reference

2.4.5 - Release Note

Bare Metal Server

2026.03.19
CHANGE New Server Type Added
  • BM 4th generation based on Intel 6th generation (Granite Rapids) Processor has been released.
    • Bare Metal Server s4 and h4 server types have been added.
    • For details on s4/h4 server types, please refer to s3/h3 server types.
2025.10.23
FEATURE Local Disk Partition Feature Added
  • Local disk partition feature provided
    • You can now create and use up to 10 local disk partitions.
2025.07.01
FEATURE New Features Added and OS Images Added
  • You can release multiple resources simultaneously from the Bare Metal Server list.
  • You can change the IP of a general Subnet.
  • OS Images have been added.
    • RHEL 8.10, Ubuntu 24.04
2025.02.27
FEATURE Placement Group Feature and OS Images, Server Types Added
  • Bare Metal Server features added
    • Distributes servers belonging to the same Placement Group across different racks.
    • OS Images added (RHEL 9.4, Rocky Linux 8.6, Rocky Linux 9.4)
    • 3rd generation (s3/h3) server types based on Intel 4th generation (Sapphire Rapids) Processor added. For details, please refer to Bare Metal Server Server Types.
  • Samsung Cloud Platform common feature changes
    • Common CX changes for Account, IAM and Service Home, tags, etc. have been reflected.
2024.10.01
NEW Bare Metal Server Service Official Version Release
  • Bare Metal Server service has been officially released.
  • Bare Metal Server service has been released, which allows customers to exclusively use physical servers without virtualization.

2.5 - Multi-node GPU Cluster

2.5.1 - Overview

Service Overview

Multi-node GPU Cluster is a service that provides physical GPU servers without virtualization for large-scale high-performance AI calculations. It can cluster multiple GPUs using two or more bare metal servers with GPUs, and can be used conveniently with Samsung Cloud Platform’s high-performance storage and networking services.

Provided Features

Multi-node GPU Cluster provides the following functions.

  • Auto Provisioning and Management: Through the web-based Console, you can easily use the standard GPU Bare Metal model server with 8 GPU cards, from provisioning to resource and cost management.
  • Network Connection: Two or more Bare Metal Servers can be clustered through high-speed interconnects to process multiple GPUs, and by configuring the GPU Direct RDMA (Remote Direct Memory Access) environment, direct data IO between GPU memories is possible, enabling high-speed AI/Machine Learning calculations.
  • Storage Connection: It provides various additional connection storages other than OS disks. High-speed network and high-performance SSD NAS File Storage, Block Storage, and Object Storage that are directly linked can also be used in conjunction.
  • Network Setting Management: The server’s subnet/IP can be easily changed with the initially set value. NAT IP provides a management function that can be used or cancelled according to needs.
  • Monitoring: You can check the monitoring information of computing resources such as CPU, GPU, Memory, Disk, etc. through Cloud Monitoring. To use the Cloud Monitoring service for Multi-node GPU Cluster, you need to install the Agent. Please install the Agent for stable service use. For more information, please refer to Multi-node GPU Cluster Monitoring Metrics.

Component

Multi-node GPU Cluster provides GPU as a Bare Metal Server type with standard images and server types, and NVSwitch and NVLink are provided.

GPU(H100)

GPU (Graphic Processing Unit) is specialized in parallel calculations that can process a large amount of data quickly, enabling large-scale parallel calculation processing in fields such as artificial intelligence (AI) and data analysis.

The following are the specifications of the GPU Type provided by the Multi-node GPU Cluster service.

ClassificationH100 Type
Product Provisioning MethodBare Metal
GPU ArchitectureNNVIDIA Hopper
GPU Memory80GB
GPU Transistors80 billion 4N TSMC
GPU Tensor Performance(based on FP16)989.4 TFLOPs, 1,978.9 TFLOPs*
GPU Memory Bandwidth3,352 GB/sec HBM3
GPU CUDA Cores16,896 Cores
GPU Tensor Cores528(4th Generation)
NVLink performanceNVLink 4
Total NVLink bandwidth900 GB/s
NVLink Signaling Rate25 Gbps (x18)
NVSwitch performanceNVSwitch 3
NVSwitch GPU bandwidth900 GB/s
Total NVSwitch Aggregate Bandwidth7.2TB/s
  • With Sparsity
Table. GPU Type Specifications

OS and GPU Driver Version

The operating systems (OS) supported by Multi-node GPU Cluster are as follows.

OSOS versionGPU driver version
Ubuntu22.04535.86.10, 535.183.06
Table. Multi-node GPU Cluster OS and GPU Driver Version

Server Type

The server types provided by Multi-node GPU Cluster are as follows. For a detailed description of the server types provided by Multi-node GPU Cluster, please refer to Multi-node GPU Cluster server type.

g2c96h8_metal
ClassificationExampleDetailed Description
Server Generationg2Provided server generation
  • g2: g means GPU server, and 2 means generation
CPUc96Number of Cores
  • c96: Assigned Core is a physical core
GPUh8GPU type and quantity
  • h8: h means GPU type, and 8 means GPU quantity
Table. Multi-node GPU Cluster server type format

Preceding Service

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

Service CategoryServiceDetailed Description
NetworkingVPCA service that provides an independent virtual network in a cloud environment
Fig. Multi-node GPU Cluster Pre-service

2.5.1.1 - Server Type

Multi-node GPU Cluster Server Type

Multi-node GPU Cluster is divided based on the provided GPU Type, and the GPU used in the Multi-node GPU Cluster is determined by the server type selected when creating a GPU Node. Please select the server type according to the specifications of the application you want to run in the Multi-node GPU Cluster.

The server types supported by Multi-node GPU Cluster are in the following format:

g2c96h8_metal
ClassificationExampleDetailed Description
Server Generationg2Provided server generation
  • g2
    • g means GPU server specification
    • 2 means generation
CPUc96Number of cores
  • c96: Assigned cores are physical cores
GPUh8GPU type and quantity
  • h8: h means GPU type, and 8 means GPU quantity
Table. Multi-node GPU Cluster server type format

g2 Server Type

The g2 server type is a GPU Bare Metal Server using NVIDIA H100 Tensor Core GPU, suitable for large-scale high-performance AI computing.

  • Provides up to 8 NVIDIA H100 Tensor Core GPUs
  • Each GPU has 16,896 CUDA cores and 528 Tensor cores
  • Supports up to 96 vCPUs and 1,920 GB of memory
  • Supports up to 100 Gbps networking speed
  • 900GB/s GPU and NVIDIA NVSwitch P2P communication
Server TypeGPUGPU MemoryCPU(Core)MemoryDiskGPU P2P
g2c96h8_metalH100640 GB96 vCore2 TBSSD(OS) 960 GB * 2, NVMeSSD 3.84 TB * 4900GB/s NVSwitch
Table. Multi-node GPU Cluster server type specification > H100 server type

2.5.1.2 - Monitoring Metrics

Multi-node GPU Cluster monitoring metrics

The following table shows the monitoring metrics of Multi-node GPU Cluster that can be checked through Cloud Monitoring.

Guide
Multi-node GPU Cluster requires the user to install the Agent through the guide to view monitoring metrics. Please install the Agent before using the stable service. For the Agent installation method and detailed Cloud Monitoring usage, please refer to the Cloud Monitoring guide.

Multi-node GPU Cluster [Cluster]

Performance ItemDetailed DescriptionUnit
Memory Total [Basic]Available memory bytesbytes
Memory Used [Basic]Currently used memory bytesbytes
Memory Swap In [Basic]Replaced memory bytesbytes
Memory Swap Out [Basic]Swapped out memory bytesbytes
Memory Free [Basic]Unused memory bytesbytes
Disk Read Bytes [Basic]Read bytesbytes
Disk Read Requests [Basic]Number of Read Requestscnt
Disk Write Bytes [Basic]Write bytesbytes
Disk Write Requests [Basic]Write Request Countcnt
CPU Usage [Basic]1-minute average system CPU usage rate%
Instance State [Basic]Instance Statusstate
Network In Bytes [Basic]Received bytesbytes
Network In Dropped [Basic]Receive Packet Dropcnt
Network In Packets [Basic]Received Packet Countcnt
Network Out Bytes [Basic]Transmission bytesbytes
Network Out Dropped [Basic]Transmission Packet Dropcnt
Network Out Packets [Basic]Transmission Packet Countcnt
Fig. Multi-node GPU Cluster [Cluster] Monitoring Metrics (Default Provided)
Performance ItemDetailed DescriptionUnit
Cluster GPU CountGPU Count SUM in the Cluster
  • Sum value of GPU Count of nodes in the cluster: Calculate the sum of GPU Count of each node in the same GPU CLUSTER
cnt
Cluster GPU Count In UseNumber of GPUs used by jobs in the cluster
  • Cluster internal Process using GPU count: the sum of the number of GPUs held by the process by parsing the ‘Processes:’ information at the bottom of the nvidia-smi result of the nodes in the same GPU CLUSTER
cnt
Cluster GPU UsageCluster internal GPU Utilization AVG
  • Cluster internal node GPU utilization Average value: Average calculation of each node’s GPU utilization value among nodes in the same GPU CLUSTER
%
Cluster GPU Memory Usage [Avg]Cluster GPU Memory Utilization AVG
  • Cluster node Memory utilization Average value: Average calculation of Memory utilization values of each node in the same GPU cluster
%
Table. Multi-node GPU Cluster [Cluster] additional monitoring metrics (Agent installation required)

Multi-node GPU Cluster [Node]

Performance ItemDetailed DescriptionUnit
Memory Total [Basic]Available memory bytesbytes
Memory Used [Basic]bytes of memory currently being usedbytes
Memory Swap In [Basic]Replaced memory bytesbytes
Memory Swap Out [Basic]Swapped out memory bytesbytes
Memory Free [Basic]unused memory bytesbytes
Disk Read Bytes [Basic]Read bytesbytes
Disk Read Requests [Basic] Disk Read Requests Countcnt
Disk Write Bytes [Basic]Write bytesbytes
Disk Write Requests [Basic]Write Request Countcnt
CPU Usage [Basic]1-minute average system CPU usage rate%
Instance State [Basic]Instance Statusstate
Network In Bytes [Basic]Received bytesbytes
Network In Dropped [Basic]Received Packet Dropcnt
Network In Packets [Basic]Received Packet Countcnt
Network Out Bytes [Basic]Transmission bytesbytes
Network Out Dropped [Basic]Transmission Packet Dropcnt
Network Out Packets [Basic]Transmission packet countcnt
Fig. Multi-node GPU Cluster [Node] Monitoring Metrics (Default Provided)
Performance ItemDetailed DescriptionUnit
GPU CountGPU countcnt
GPU TemperatureGPU temperature
GPU Usageutilization%
GPU Usage [Avg]GPU Overall Average Usage Rate(%)%
GPU Power CapGPU’s maximum power capacityW
GPU Power UsageGPU’s current power usageW
GPU Memory Usage [Avg]GPU Memory Uti. AVG%
GPU Count in useNode’s Job-running GPU countcnt
Execution Status for nvidia-sminvidia-smi command execution resultstatus
Core Usage [IO Wait]The ratio of CPU time spent in waiting state (disk waiting)%
Core Usage [System]The ratio of CPU time spent in kernel space%
-Core Usage [User]--The ratio of CPU time spent in user space--%-
CPU CoresThe number of CPU cores on the host. The maximum value of the unnormalized ratio is 100%* of the cores. The unnormalized ratio already reflects this value, and the maximum value is 100%* of the cores.cnt
CPU Usage [Active]Percentage of CPU time used excluding Idle and IOWait states (if all 4 cores are used at 100%: 400%)%
CPU Usage [Idle]The ratio of CPU time spent in idle state.%
CPU Usage [IO Wait]The percentage of CPU time spent in waiting state (disk waiting)%
CPU Usage [System]Percentage of CPU time used by the kernel (in case of using all 4 cores 100%: 400%)%
CPU Usage [User]Percentage of CPU time used in the user area. (In case of using all 4 cores 100%, 400%)%
CPU Usage/Core [Active]Percentage of CPU time used excluding Idle and IOWait states (normalized value by number of cores, 100% if all 4 cores are used at 100%)%
CPU Usage/Core [Idle]The ratio of CPU time spent in idle state.%
CPU Usage/Core [IO Wait]The ratio of CPU time spent in waiting state (disk waiting)%
CPU Usage/Core [System]Percentage of CPU time used by the kernel (normalized value by number of cores, 100% if all 4 cores are used at 100%)%
CPU Usage/Core [User]Percentage of CPU time used in the user area. (normalized value by number of cores, 100% if all 4 cores are used at 100%)%
Disk CPU Usage [IO Request]The ratio of CPU time spent executing input/output requests for the device (device bandwidth utilization). If this value is close to 100%, the device is in a saturated state.%
Disk Queue Size [Avg]The average queue length of requests executed for the device.num
Disk Read BytesThe number of bytes read from the device per second.bytes
Disk Read Bytes [Delta Avg]Average of system.diskio.read.bytes_delta for each diskbytes
Disk Read Bytes [Delta Max]Individual disks’ system.diskio.read.bytes_delta maximumbytes
Disk Read Bytes [Delta Min]Individual disks’ minimum system.diskio.read.bytes_deltabytes
Disk Read Bytes [Delta Sum]The sum of system.diskio.read.bytes_delta of individual disksbytes
Disk Read Bytes [Delta]Delta value of system.diskio.read.bytes for each diskbytes
Disk Read Bytes [Success]The total number of bytes read successfully. In Linux, it is assumed that the sector size is 512 and the value multiplied by the number of sectors read by 512bytes
Disk Read RequestsThe number of read requests for the disk device in 1 secondcnt
Disk Read Requests [Delta Avg]Average of system.diskio.read.count_delta for each diskcnt
Disk Read Requests [Delta Max]Maximum of system.diskio.read.count_delta for individual diskscnt
Disk Read Requests [Delta Min]Minimum of system.diskio.read.count_delta for each diskcnt
Disk Read Requests [Delta Sum]Sum of system.diskio.read.count_delta of individual diskscnt
Disk Read Requests [Success Delta]Individual disk’s system.diskio.read.count deltacnt
Disk Read Requests [Success]Total number of successful read completionscnt
Disk Request Size [Avg]The average size of requests executed for the device (unit: sector)num
Disk Service Time [Avg]The average service time (in milliseconds) for input requests executed on the device.ms
Disk Wait Time [Avg]The average time spent on requests executed for supported devices.ms
Disk Wait Time [Read]Disk Average Wait Timems
Disk Wait Time [Write]Disk Average Wait Timems
Disk Write Bytes [Delta Avg]Average of system.diskio.write.bytes_delta for each diskbytes
Disk Write Bytes [Delta Max]Maximum of system.diskio.write.bytes_delta for each diskbytes
Disk Write Bytes [Delta Min]Individual disks’ minimum system.diskio.write.bytes_deltabytes
Disk Write Bytes [Delta Sum]The sum of system.diskio.write.bytes_delta of individual disksbytes
Disk Write Bytes [Delta]Delta value of system.diskio.write.bytes for each diskbytes
Disk Write Bytes [Success]The total number of bytes written successfully. In Linux, it is assumed that the sector size is 512 and the value is multiplied by 512 to the number of sectors writtenbytes
Disk Write RequestsThe number of write requests to the disk device for 1 secondcnt
Disk Write Requests [Delta Avg]Average of system.diskio.write.count_delta of individual diskscnt
Disk Write Requests [Delta Max]Maximum of system.diskio.write.count_delta for each diskcnt
Disk Write Requests [Delta Min]Minimum of system.diskio.write.count_delta for individual diskscnt
Disk Write Requests [Delta Sum]Sum of system.diskio.write.count_delta of individual diskscnt
Disk Write Requests [Success Delta]Individual disk’s system.diskio.write.count deltacnt
Disk Write Requests [Success]Total number of writes completed successfullycnt
Disk Writes BytesThe number of bytes written to the device per second.bytes
Filesystem Hang Checkfilesystem(local/NFS) hang check (normal:1, abnormal:0)status
Filesystem NodesThe total number of file nodes in the file system.cnt
Filesystem Nodes [Free]The total number of available file nodes in the file system.cnt
Filesystem Size [Available]This is the disk space (in bytes) that can be used by unauthorized users.bytes
Filesystem Size [Free]Available disk space (bytes)bytes
Filesystem Size [Total]Total Disk Space (bytes)bytes
Filesystem UsageUsed Disk Space Percentage%
Filesystem Usage [Avg]Average of individual filesystem.used.pct%
Filesystem Usage [Inode]_inode usage rate%
Filesystem Usage [Max]Maximum value among individual filesystem usage percentages%
Filesystem Usage [Min]Minimum of individual filesystem used percentages%
Filesystem Usage [Total]-%
Filesystem UsedUsed Disk Space (bytes)bytes
Filesystem Used [Inode]Inode usagebytes
Memory FreeThe total amount of available memory (bytes). It does not include memory used by system cache and buffers (see system.memory.actual.free).bytes
Memory Free [Actual]Actual available memory (bytes). The calculation method varies depending on the OS, and in Linux, it is either MemAvailable from /proc/meminfo or calculated from available memory, cache, and buffer if meminfo is not available. On OSX, it is the sum of available memory and inactive memory. On Windows, it is the same as system.memory.free.bytes
Memory Free [Swap]Available swap memory.bytes
Memory TotalTotal Memorybytes
Memory Total [Swap]Total swap memory.bytes
Memory UsageUsed memory percentage
  • ((Memory Total - Memory Free) / Memory Total) * 100
  • Memory Free: Current available free memory capacity
%
Memory Usage [Actual]The percentage of memory actually used
  • ((Memory Total - Memory Available) / Memory Total) * 100 or ((Memory Total - (Memory Free + Buffers + Cached)) / Memory Total) * 100
  • Memory Free: The capacity of free memory currently available
  • Buffers: The capacity of memory used by buffers
  • Cached: The capacity of memory used by page cache
%
Memory Usage [Cache Swap]Cache swap usage rate%
Memory Usage [Swap]Used swap memory percentage%
Memory UsedUsed Memorybytes
Memory Used [Actual]Actual used memory (bytes). The value subtracted from the total memory by the used memory. The available memory is calculated differently depending on the OS (refer to system.actual.free)bytes
Memory Used [Swap]Used swap memory.bytes
CollisionsNetwork Collisionscnt
Network In BytesReceived byte countbytes
Network In Bytes [Delta Avg]Average of system.network.in.bytes_delta for each networkbytes
Network In Bytes [Delta Max]Maximum of system.network.in.bytes_delta for each networkbytes
Network In Bytes [Delta Min]Minimum of system.network.in.bytes_delta for each networkbytes
Network In Bytes [Delta Sum]Sum of each network’s system.network.in.bytes_deltabytes
Network In Bytes [Delta]Received byte count deltabytes
Network In DroppedThe number of packets deleted among incoming packetscnt
Network In ErrorsNumber of errors during receptioncnt
Network In PacketsReceived packet countcnt
Network In Packets [Delta Avg]Average of system.network.in.packets_delta for each networkcnt
Network In Packets [Delta Max]Individual networks’ system.network.in.packets_delta maximumcnt
Network In Packets [Delta Min]Minimum of system.network.in.packets_delta for each networkcnt
Network In Packets [Delta Sum]Sum of system.network.in.packets_delta of individual networkscnt
Network In Packets [Delta]Received packet count deltacnt
Network Out BytesTransmitted byte countbytes
Network Out Bytes [Delta Avg]Average of system.network.out.bytes_delta for each networkbytes
Network Out Bytes [Delta Max]Individual networks’ system.network.out.bytes_delta maximumbytes
Network Out Bytes [Delta Min]Minimum of system.network.out.bytes_delta for each networkbytes
Network Out Bytes [Delta Sum]The sum of system.network.out.bytes_delta of individual networksbytes
Network Out Bytes [Delta]Transmitted byte count deltabytes
Network Out DroppedNumber of packets dropped among outgoing packets. This value is not reported by the operating system, so it is always 0 in Darwin and BSDcnt
Network Out ErrorsNumber of errors during transmissioncnt
Network Out PacketsNumber of transmitted packetscnt
Network Out Packets [Delta Avg]Average of system.network.out.packets_delta for each networkcnt
Network Out Packets [Delta Max]Maximum of system.network.out.packets_delta for each networkcnt
Network Out Packets [Delta Min]Individual networks’ minimum system.network.out.packets_deltacnt
Network Out Packets [Delta Sum]Sum of system.network.out.packets_delta of individual networkscnt
Network Out Packets [Delta]Number of transmitted packets deltacnt
Open Connections [TCP]All open TCP connectionscnt
Open Connections [UDP]All open UDP connectionscnt
Port UsagePort usage available for connection%
SYN Sent SocketsNumber of sockets in SYN_SENT state (when connecting from local to remote)cnt
Kernel PID Maxkernel.pid_max valuecnt
Kernel Thread Maxkernel threads-max valuecnt
Process CPU UsagePercentage of CPU time consumed by the process after the last update. This value is similar to the %CPU value of the process displayed by the top command on Unix systems%
Process CPU Usage/CorePercentage of CPU time used by the process since the last event, normalized by the number of cores, with a value between 0~100%%
Process Memory Usagemain memory (RAM) where the process occupies a ratio%
Process Memory UsedResident Set size. The amount of memory a process occupies in RAM. In Windows, it is the current working set sizebytes
Process PIDProcess PIDPID
Process PPIDParent process’s pidPID
Processes [Dead].dead processes countcnt
Processes [Idle]idle process countcnt
Processes [Running]Number of running processescnt
Processes [Sleeping]sleeping processes countcnt
Processes [Stopped]Number of stopped processescnt
Processes [Total]Total number of processescnt
Processes [Unknown]Cannot search or unknown number of processescnt
Processes [Zombie]Number of zombie processescnt
Running Process Usageprocess usage rate%
Running ProcessesNumber of running processescnt
Running Thread UsageThread usage rate%
Running Threadsnumber of threads running in running processescnt
Instance Status_instance statusstate
Context Switchescontext switch count (per second)cnt
Load/Core [1 min]Load for the last 1 minute divided by the number of corescnt
Load/Core [15 min]The value of load divided by the number of cores for the last 15 minutescnt
Load/Core [5 min]The value of load divided by the number of cores over the last 5 minutescnt
Multipaths [Active]External storage connection path status = active countcnt
Multipaths [Failed]External storage connection path status = failed countcnt
Multipaths [Faulty]External storage connection path status = faulty countcnt
NTP Offsetlast sample’s measured offset (time difference between NTP server and local environment)num
Run Queue LengthExecution Waiting Queue Lengthnum
UptimeOS operation time (uptime). (milliseconds)ms
Context SwitchiesCPU context switch count (per second)cnt
Disk Read Bytes [Sec]number of bytes read from the windows logical disk in 1 secondcnt
Disk Read Time [Avg]Data Read Average Time (sec)sec
Disk Transfer Time [Avg]Disk average wait timesec
Disk UsageDisk Usage Rate%
Disk Write Bytes [Sec]number of bytes written to the windows logical disk in 1 secondcnt
Disk Write Time [Avg]Data Write Average Time (sec)sec
Pagingfile UsagePaging file usage rate%
Pool Used [Non Paged]Kernel memory Non-paged pool usagebytes
Pool Used [Paged]Paged Pool usage among kernel memorybytes
Process [Running]The number of processes currently runningcnt
Threads [Running]Number of threads currently runningcnt
Threads [Waiting]The number of threads waiting for processor timecnt
Table. Multi-node GPU Cluster [Node] additional monitoring metrics (Agent installation required)

2.5.2 - How-to guides

The user can enter the required information for the Multi-node GPU Cluster service through the Samsung Cloud Platform Console, select detailed options, and create the service.

Multi-node GPU Cluster Getting Started

You can create and use a Multi-node GPU Cluster service in the Samsung Cloud Platform Console.

This service consists of GPU Node and Cluster Fabric services.

GPU Node Creation

To create a Multi-node GPU Cluster, follow the steps below.

  1. All Services > Compute > Multi-node GPU Cluster Click the menu. Navigate to the Service Home page of Multi-node GPU Cluster.
  2. Click the GPU Node creation button on the Service Home page. You will be taken to the GPU Node creation page.
  3. GPU Node creation on the page, enter the information required to create the service, and select detailed options.
    • Image and Version Selection Select the required information in the area.
      Category
      Required
      Detailed description
      ImageRequiredSelect provided image type
      • Ubuntu
      Image VersionRequiredSelect version of the chosen image
      • Provides a list of versions of the provided server images
      Table. GPU Node image and version selection items
  • Enter service information area, input or select the required information.
    Category
    Required
    Detailed description
    Number of serversRequiredNumber of GPU Node servers to create simultaneously
    • Only numbers can be entered, and the minimum number of servers to create is 2.
    • Only during the initial setup can you create 2 or more, and expansion is possible one at a time.
    Service Type > Server TypeRequiredGPU Node Server Type
    • Select desired CPU, Memory, GPU, Disk specifications
    Service Type > Planned ComputeRequiredStatus of resources with Planned Compute set
    • In Use: Number of resources with Planned Compute that are currently in use
    • Configured: Number of resources with Planned Compute set
    • Coverage Preview: Amount applied per resource by Planned Compute
    • Planned Compute Service Application: Go to the Planned Compute service application page
    Table. GPU Node Service Information Input Items
    • Required Information Input area, enter or select the required information.
      Category
      Required or not
      Detailed description
      Administrator AccountRequiredSet the administrator account and password to be used when connecting to the server
      • Ubuntu OS is provided fixed as root
      Server Name PrefixRequiredEnter a Prefix to distinguish each GPU Node generated when the number of selected servers is 2 or more
      • Automatically generated as user input value (prefix) + ‘-###’ format
      • Start with a lowercase English letter, and use lowercase letters, numbers, and special characters (-) within 3 to 11 characters
      • Must not end with a special character (-)
      Network SettingsRequiredSet the network where the GPU Node will be installed
      • VPC Name:Select a pre-created VPC
      • General Subnet Name: Select a pre-created general Subnet
        • IP can be set to auto-generate or user input, and if input is selected, the user enters the IP directly
      • NAT: Can be used only when there is 1 server and the VPC has an Internet Gateway attached. Checking ‘use’ allows selection of a NAT IP. (When first created, it is generated only with 2 or more servers, so modify on the resource detail page)
      • NAT IP: Select NAT IP
        • If there is no NAT IP to select, click the Create New button to generate a Public IP
        • Click the Refresh button to view and select the created Public IP
        • Creating a Public IP incurs charges according to the Public IP pricing policy
      Table. GPU Node required information entry items
  • Cluster selection area, create or select a Cluster Fabric.
    Category
    Required
    Detailed description
    Cluster FabricRequiredSetting of a group of GPU Node servers that can apply GPU Direct RDMA together
    • Optimal GPU performance and speed can be secured only within the same Cluster Fabric
    • When creating a new Cluster Fabric, select *New Input > Node pool, then enter the name of the Cluster Fabric to be created
    • To add to an existing Cluster Fabric, select Existing Input > Node pool, then select the already created Cluster Fabric
    Table. GPU Node Cluster Fabric selection items
    • Additional Information Input Enter or select the required information in the area.
      Category
      Required or not
      Detailed description
      LockSelectUsing Lock prevents accidental actions that could terminate/start/stop the server
      Init ScriptSelectScript to run when the server starts
      • Init Script must be selected differently depending on the image type
        • For Linux: Select Shell Script or cloud-init
      TagSelectAdd Tag
      • Up to 50 can be added per resource
      • After clicking the Add Tag button, enter or select Key, Value values
      Table. GPU Node additional information input items
  1. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resources on the GPU Node List page.
Caution
  • When creating a service, the GPU MIG/ECC settings are reset. However, to apply the correct settings, perform a one-time reboot initially, verify whether the settings have been applied, and then use it.
  • For detailed information about GPU MIG/ECC settings reset, please refer to GPU MIG/ECC Settings Reset Checklist Guide.

GPU Node Check Detailed Information

The Multi-node GPU Cluster service allows you to view and edit the full list of GPU Node resources and detailed information.

GPU Node Details page consists of Details, Tags, Job History tabs.

To view detailed information of the GPU Node, follow the steps below.

  1. All Services > Compute > Multi-node GPU Cluster > GPU Node Click the menu. Navigate to the Service Home page of Multi-node GPU Cluster.

  2. Click the GPU Node menu on the Service Home page. Navigate to the GPU Node List page.

    • Resource items other than required columns can be added via the Settings button.
      Category
      Required or not
      Detailed description
      Resource IDSelectUser-created GPU Node ID
      Cluster Fabric namerequiredCluster Fabric name created by the user
      Server nameRequiredUser-created GPU Node name
      Server TypeRequiredServer type of GPU Node
      • User can check the number of cores, memory capacity, GPU type and count of the created resources
      ImageRequiredUser-generated GPU Node image version
      IPRequiredIP of the GPU Node created by the user
      StatusRequiredStatus of the GPU Node created by the user
      Creation TimeSelectGPU Node creation time
      Table. GPU Node Resource List Items
  3. GPU Node List Click the resource to view detailed information. GPU Node Details You will be taken to the page.

    • GPU Server Details At the top of the page, status information and descriptions of additional features are displayed.
      CategoryDetailed description
      GPU Node statusStatus of GPU Node created by the user
      • Creating: State where the server is being created
      • Running:: State where creation is complete and usable
      • Editing:: State where IP is being changed
      • Unknown: Error state
      • Starting: State where the server is starting
      • Stopping: State where the server is stopping
      • Stopped: State where the server has stopped
      • Terminating: State where termination is in progress
      • Terminated: State where termination is complete
      Server ControlButton to change server status
      • Start: Start a stopped server
      • Stop: Stop a running server
      Service cancellationButton to cancel the service
      Table. GPU Node status information and additional features

Detailed Information

GPU Node List page’s Details Tab you can view the detailed information of the selected resource, and if necessary, edit the information.

CategoryDetailed description
ServiceService Name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In GPU Node, it means GPU Node SRN
Resource NameResource Name
  • In the GPU Node service, it means the GPU Node name
Resource IDUnique resource ID in the service
CreatorUser who created the service
Creation timeService creation time
ModifierUser who edited the service information
Modification date/timeDate and time when the service information was modified
Server nameServer name
Node poolA group of nodes that can be grouped together with the same Cluster Fabric
Cluster Fabric nameCluster Fabric name created by the user
Image/VersionServer’s OS image and version
Server TypeCPU, Memory, GPU, Information Display
Planned ComputeResource status with Planned Compute set
LockDisplay lock usage status
  • If lock is used, it prevents server termination/start/stop to avoid accidental actions
  • If you need to change the lock attribute value, click the Edit button to set
NetworkGPU Node network information
  • VPC name, general Subnet name, IP, IP status, NAT IP, NAT IP status
Block StorageBlock Storage information connected to the server
  • Volume name, disk type, capacity, status
Init ScriptView the Init Script content entered when creating the server
Table. GPU Node detailed information tab items

Tag

GPU Node List page’s Tag Tab you can view the tag information of the selected resource, and add, modify, or delete it.

CategoryDetailed description
Tag ListTag List
  • Tag’s Key, Value information can be checked
  • Up to 50 tags can be added per resource
  • When entering a tag, search and select from the existing list of Keys and Values
Table. GPU Node Tag Tab Items

Work History

GPU Node List page’s Job History tab allows you to view the job history of the selected resource.

CategoryDetailed description
Work History ListResource Change History
  • Work details, work date and time, resource type, resource name, event topic, work result, check worker information
  • Detailed Search button provides detailed search function
Table. GPU Node Job History Tab Detailed Information Items

GPU Node Operation Control

If you need server control and management functions for the generated GPU Node resources, you can perform tasks on the GPU Node List or GPU Node Details page. You can start and stop the running GPU Node resources.

GPU Node Getting Started

You can start a stopped GPU Node. To start the GPU Node, follow the steps below.

  1. All Services > Compute > Multi-node GPU Cluster Click the menu. Navigate to the Service Home page of Multi-node GPU Cluster.
  2. Click the GPU Node menu on the Service Home page. You will be taken to the GPU Node List page.
    • On the GPU Node List page, after selecting individual or multiple servers with the checkbox, you can Start via the More button at the top.
  3. GPU Node List page, click the resource. GPU Node Details page will be opened.
    • GPU Node Details on the page, click the Start button at the top to start the server.
  4. Check the server status and complete the status change.

Stop GPU Node

You can stop a GPU Node that is active. To stop the GPU Node, follow the steps below.

  1. All Services > Compute > Multi-node GPU Cluster Click the menu. Move to Multi-node GPU Cluster’s Service Home page.
  2. Click the GPU Node menu on the Service Home page. You will be taken to the GPU Node List page.
    • GPU Node List page, you can control individual or multiple servers by selecting the checkboxes and then using the Stop button at the top.
  3. GPU Node List page, click the resource. GPU Node Details page, navigate.
    • GPU Node Details on the page, click the Stop button at the top to stop the server.
  4. Check the server status and complete the status change.

GPU Node Cancel

You can cancel unused GPU nodes to reduce operating costs. However, if you cancel the service, the running service may be stopped immediately, so you should consider the impact of service interruption sufficiently before proceeding with the cancellation.

Caution
Please note that data cannot be recovered after service termination.

To cancel the GPU Node, follow the steps below.

  1. All Services > Compute > Multi-node GPU Server Click the menu. Navigate to the Service Home page of the Multi-node GPU Cluster.
  2. Click the Cluster Fabric menu on the Service Home page. You will be taken to the Cluster Fabric List page.
  3. Cluster Fabric List page, select the resource to cancel, and click the Cancel Service button.
    • Resources using the same Cluster Fabric can be terminated simultaneously.
  4. Once the termination is complete, check on the GPU Node List page whether the resources have been terminated.
Guide

The cases where GPU Node termination is not possible are as follows.

  • When Block Storage (BM) is connected: Please disconnect the Block Storage (BM) connection first.
  • If File Storage is connected: Please disconnect the File Storage first.
  • When Lock is set: Please change the Lock setting to unused and try again.
  • If the server that cannot be terminated simultaneously is included: Please re-select only the resources that can be terminated.
  • If the Cluster Fabric of the server you want to terminate is different: Select only resources that use the same Cluster Fabric.
Reference
If all GPU Nodes in the Cluster Fabric are deleted, the Cluster Fabric is automatically deleted.

2.5.2.1 - Cluster Fabric Management

Cluster Fabric is a service that helps manage servers (GPU Nodes) included in a GPU Cluster. Using Cluster Fabric, you can move servers between GPU Clusters in the same Node pool and optimize the performance and speed of GPUs within the same GPU Cluster.

Creating Cluster Fabric

Cluster Fabric can be created together with a GPU Node, and it cannot be created or deleted separately. When all GPU Nodes within a Cluster Fabric are terminated, the Cluster Fabric is automatically deleted. If you haven’t created a GPU Node, please create one first. For more information, refer to Creating a GPU Node.

Checking Cluster Fabric Details

Guide
  • Cluster Fabric can be created together with a GPU Node, and it cannot be created or deleted separately.
  • When all GPU Nodes within a Cluster Fabric are terminated, the Cluster Fabric is automatically deleted.
  • If you haven’t created a GPU Node, please create one first. For more information, refer to Creating a GPU Node.

You can check the created Cluster Fabric list and details, and move servers on the Cluster Fabric List page and Cluster Fabric Details page.

  1. Click on All Services > Compute > Multi-node GPU Server menu. It will move to the Service Home page of the Multi-node GPU Cluster.

  2. Click on the Cluster Fabric menu on the Service Home page. It will move to the Cluster Fabric List page.

    • On the Cluster Fabric List page, you can view the list of resources of the GPU Cluster created by the user.
    • Resource items other than required columns can be added through the Settings button.
      Category
      Required
      Description
      Resource IDOptionalCluster Fabric ID created by the user
      Cluster Fabric NameRequiredCluster Fabric name created by the user
      Node PoolOptionalA collection of nodes that can be bundled into the same Cluster Fabric
      Number of ServersOptionalNumber of GPU Nodes
      Server TypeOptionalServer type of the GPU Node
      • The user can check the number of cores, memory capacity, and GPU type and number of the created resource
      StatusOptionalStatus of the Cluster Fabric created by the user
      Creation TimeOptionalTime when the Cluster Fabric was created
      Table. Cluster Fabric resource list items
  3. Click on the resource to check the details on the Cluster Fabric List page. It will move to the Cluster Fabric Details page.

    • At the top of the Cluster Fabric Details page, status information and additional feature descriptions are displayed.
      CategoryDescription
      Cluster Fabric StatusStatus of the Cluster Fabric created by the user
      • Creating: Cluster creation in progress
      • Active: Creation completed and available
      • Editing: IP change in progress
      • Deleting: Termination in progress
      • Deleted: Termination completed
      Add Target ServerFunction to move a server from another cluster to this cluster
      Table. Cluster Fabric status information and additional features

Details

On the Details tab of the Cluster Fabric List page, you can check the details of the selected resource and bring in servers from other clusters.

CategoryDescription
ServiceService category
Resource TypeService name
SRNUnique resource ID in Samsung Cloud Platform
  • In Cluster Fabric, it means Cluster Fabric SRN
Resource NameResource name
  • In Cluster Fabric service, it means Cluster Fabric name
Resource IDUnique resource ID in the service
CreatorUser who created the service
Creation TimeTime when the service was created
ModifierUser who modified the service information
Modification TimeTime when the service information was modified
Cluster Fabric NameCluster Fabric name created by the user
Node PoolA collection of nodes that can be bundled into the same Cluster Fabric
Target ServerList of GPU Nodes bound to the Cluster Fabric
  • Server name, server type, IP, status
Table. Cluster Fabric details tab items

Bringing in Cluster Fabric Servers

Using the Add Target Server feature on the Cluster Fabric Details page, you can bring in servers from other clusters and add them to the selected cluster.

  1. Click on All Services > Compute > Multi-node GPU Server menu. It will move to the Service Home page of the Multi-node GPU Cluster.
  2. Click on the Cluster Fabric menu on the Service Home page. It will move to the Cluster Fabric List page.
  3. Click on the resource to check the details on the Cluster Fabric List page. It will move to the Cluster Fabric Details page.
  4. Click the Add button on the right side of the target server on the details tab.
    • The target server addition popup window opens.
      • Cluster Fabric Select a cluster.
      • The GPU Node bound to the selected cluster is retrieved, and you can select the GPU Node to bring in.
      • The selected GPU Node is listed at the bottom with the GPU Node name.
      • Click the Confirm button to complete.
      • Click the Cancel button to cancel the task.
    • Check if the added GPU Node is retrieved in the target server.

Terminating Cluster Fabric

When all GPU Nodes within a Cluster Fabric are terminated, the Cluster Fabric is automatically deleted. For more information, refer to Terminating a GPU Node.

2.5.2.2 - Installing ServiceWatch Agent

Users can install ServiceWatch Agent on the GPU Node of Multi-node GPU Cluster to collect custom metrics and logs.

Note
Custom metrics/logs collection through ServiceWatch Agent is currently available only in Samsung Cloud Platform For Enterprise. It is planned to be provided in other offerings in the future.
Warning
Metrics collection through ServiceWatch Agent is classified as custom metrics and charges are applied unlike default collected metrics, so it is recommended to remove or disable unnecessary metric collection settings.

ServiceWatch Agent

The agents that need to be installed to collect ServiceWatch’s custom metrics and logs on the GPU Node of Multi-node GPU Cluster can be divided into two main types: Prometheus Exporter and Open Telemetry Collector.

ItemDescription
Prometheus ExporterProvides metrics of specific applications or services in a format that Prometheus can scrape
  • For OS metric collection on GPU Nodes, you can use Node Exporter for Linux servers and Windows Exporter for Windows servers depending on the OS type.
Open Telemetry CollectorActs as a central collector that collects telemetry data such as metrics and logs from distributed systems, processes them (filtering, sampling, etc.), and sends them to multiple backends (e.g., Prometheus, Jaeger, Elasticsearch, etc.)
  • Enables ServiceWatch to collect metrics and log data by sending data to ServiceWatch Gateway.
Table. Description of Prometheus Exporter and Open Telemetry Collector
Notice

If Kubernetes Engine is configured on the GPU Node, please check GPU metrics through the metrics provided by Kubernetes Engine.

  • If DCGM Exporter is installed on a GPU Node where Kubernetes Engine is configured, it may not operate normally.
Note
The ServiceWatch Agent guide for GPU metric collection on GPU Nodes can be used in the same way as for GPU Server. For details, see GPU Server > ServiceWatch Agent.

Pre-settings for Using ServiceWatch Agent

To use ServiceWatch Agent, please prepare pre-settings by referring to Pre-environment Setup for ServiceWatch Agent.

2.5.2.3 - Multi-node GPU Cluster Service Scope and Inspection Guide

Multi-node GPU Cluster service scope

In the event of an IaaS HW level issue with the Multi-node GPU Cluster service, technical support can be received through the Support Center’s Contact Us. However, risks due to changes such as OS Kernel updates or application installation are the responsibility of the user, so technical support may be difficult, please be cautious when performing system updates or other tasks.

IaaS HW level problem

  • IPMI(iLO) HW monitoring console where the server’s internal HW fault event occurrence message occurs
  • GPU HW operation error confirmed in nvdia-smi command
  • HW error messages occurring from InfiniBand HCA card or InfiniBand Switch inspection
Caution
Multi-node GPU Cluster is a service sensitive to software version compatibility of Ubuntu OS / NVDIA / Infiniband, so official technical support is not available after changes such as the user’s OS kernel update or application installation.

IaaS HW Inspection Guide

After applying for the Multi-node GPU Cluster service, it is recommended to check the IaaS HW level according to the inspection guide.

OS Kernel and Package Holding

Notice
  • If you do not want automatic updates of package versions, it is recommended to block package updates using the apt-mark command.
  • It is recommended to block the update of Linux kernel or IB related package versions.

To proceed with OS Kernel and Package holding, follow the procedure below.

  1. Use the following command to check the version of the kernel and IB-related packages.
    Color mode
    root@bm-dev-001:~# dpkg -l | egrep -i "kernel | mlnx"
    root@bm-dev-001:~# dpkg -l | egrep -i "kernel | nvidia"
    root@bm-dev-001:~# dpkg -l | egrep -i "kernel | linux-image"
    ii  crash                                 7.2.8-1ubuntu1.20.04.1                  amd64        kernel debugging utility, allowing gdb like syntax
    ii  dkms                                  2.8.1-5ubuntu2                          all          Dynamic Kernel Module Support Framework
    ii  dmeventd                              2:1.02.167-1ubuntu1                     amd64        Linux Kernel Device Mapper event daemon
    ii  dmsetup                               2:1.02.167-1ubuntu1                     amd64        Linux Kernel Device Mapper userspace library
    ii  iser-dkms                             5.4-OFED.5.4.3.0.1.1                    all          DKMS support fo iser kernel modules
    ii  isert-dkms                            5.4-OFED.5.4.3.0.1.1                    all          DKMS support fo isert kernel modules
    ii  kernel-mft-dkms                       4.17.2-12                               all          DKMS support for kernel-mft kernel modules
    ii  kmod                                  27-1ubuntu2                             amd64        tools for managing Linux kernel modules
    ii  knem                                  1.1.4.90mlnx1-OFED.5.1.2.5.0.1          amd64        userspace tools for the KNEM kernel module
    ii  knem-dkms                             1.1.4.90mlnx1-OFED.5.1.2.5.0.1          all          DKMS support for mlnx-ofed kernel modules
    ii  libaio1:amd64                         0.3.112-5                               amd64        Linux kernel AIO access library - shared library
    ii  libdevmapper-event1.02.1:amd64        2:1.02.167-1ubuntu1                     amd64        Linux Kernel Device Mapper event support library
    ii  libdevmapper1.02.1:amd64              2:1.02.167-1ubuntu1                     amd64        Linux Kernel Device Mapper userspace library
    ii  libdrm-amdgpu1:amd64                  2.4.107-8ubuntu1~20.04.2                amd64        Userspace interface to amdgpu-specific kernel DRM services -- runtime
    ii  libdrm-common                         2.4.107-8ubuntu1~20.04.2                all          Userspace interface to kernel DRM services -- common files
    ii  libdrm-intel1:amd64                   2.4.107-8ubuntu1~20.04.2                amd64        Userspace interface to intel-specific kernel DRM services -- runtime
    ii  libdrm-nouveau2:amd64                 2.4.107-8ubuntu1~20.04.2                amd64        Userspace interface to nouveau-specific kernel DRM services -- runtime
    ii  libdrm-radeon1:amd64                  2.4.107-8ubuntu1~20.04.2                amd64        Userspace interface to radeon-specific kernel DRM services -- runtime
    ii  libdrm2:amd64                         2.4.107-8ubuntu1~20.04.2                amd64        Userspace interface to kernel DRM services -- runtime
    ii  linux-firmware                        1.187.29                                all          Firmware for Linux kernel drivers
    hi  linux-generic                         5.4.0.105.109                           amd64        Complete Generic Linux kernel and headers
    ii  linux-headers-5.4.0-104               5.4.0-104.118                           all          Header files related to Linux kernel version 5.4.0
    ii  linux-headers-5.4.0-104-generic       5.4.0-104.118                           amd64        Linux kernel headers for version 5.4.0 on 64 bit x86 SMP
    ii  linux-headers-5.4.0-105               5.4.0-105.119                           all          Header files related to Linux kernel version 5.4.0
    ii  linux-headers-5.4.0-105-generic       5.4.0-105.119                           amd64        Linux kernel headers for version 5.4.0 on 64 bit x86 SMP
    hi  linux-headers-generic                 5.4.0.105.109                           amd64        Generic Linux kernel headers
    ii  linux-image-5.4.0-104-generic         5.4.0-104.118                           amd64        Signed kernel image generic
    ii  linux-image-5.4.0-105-generic         5.4.0-105.119                           amd64        Signed kernel image generic
    hi  linux-image-generic                   5.4.0.105.109                           amd64        Generic Linux kernel image
    ii  linux-libc-dev:amd64                  5.4.0-105.119                           amd64        Linux Kernel Headers for development
    ii  linux-modules-5.4.0-104-generic       5.4.0-104.118                           amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
    ii  linux-modules-5.4.0-105-generic       5.4.0-105.119                           amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
    ii  linux-modules-extra-5.4.0-104-generic 5.4.0-104.118                           amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
    ii  linux-modules-extra-5.4.0-105-generic 5.4.0-105.119                           amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
    ii  mlnx-ofed-kernel-dkms                 5.4-OFED.5.4.3.0.3.1                    all          DKMS support for mlnx-ofed kernel modules
    ii  mlnx-ofed-kernel-utils                5.4-OFED.5.4.3.0.3.1                    amd64        Userspace tools to restart and tune mlnx-ofed kernel modules
    ii  mlnx-tools                            5.2.0-0.54303                           amd64        Userspace tools to restart and tune MLNX_OFED kernel modules
    ii  nvidia-kernel-common-470              470.103.01-0ubuntu0.20.04.1             amd64        Shared files used with the kernel module
    ii  nvidia-kernel-source-470              470.103.01-0ubuntu0.20.04.1             amd64        NVIDIA kernel source package
    ii  nvidia-peer-memory                    1.2-0                                   all          nvidia peer memory kernel module.
    ii  nvidia-peer-memory-dkms               1.2-0                                   all          DKMS support for nvidia-peer-memory kernel modules
    ii  rsyslog                               8.2001.0-1ubuntu1.1                     amd64        reliable system and kernel logging daemon
    ii  srp-dkms                              5.4-OFED.5.4.3.0.1.1                    all          DKMS support fo srp kernel modules
    root@bm-dev-001:~# dpkg -l | egrep -i "kernel | mlnx"
    root@bm-dev-001:~# dpkg -l | egrep -i "kernel | nvidia"
    root@bm-dev-001:~# dpkg -l | egrep -i "kernel | linux-image"
    ii  crash                                 7.2.8-1ubuntu1.20.04.1                  amd64        kernel debugging utility, allowing gdb like syntax
    ii  dkms                                  2.8.1-5ubuntu2                          all          Dynamic Kernel Module Support Framework
    ii  dmeventd                              2:1.02.167-1ubuntu1                     amd64        Linux Kernel Device Mapper event daemon
    ii  dmsetup                               2:1.02.167-1ubuntu1                     amd64        Linux Kernel Device Mapper userspace library
    ii  iser-dkms                             5.4-OFED.5.4.3.0.1.1                    all          DKMS support fo iser kernel modules
    ii  isert-dkms                            5.4-OFED.5.4.3.0.1.1                    all          DKMS support fo isert kernel modules
    ii  kernel-mft-dkms                       4.17.2-12                               all          DKMS support for kernel-mft kernel modules
    ii  kmod                                  27-1ubuntu2                             amd64        tools for managing Linux kernel modules
    ii  knem                                  1.1.4.90mlnx1-OFED.5.1.2.5.0.1          amd64        userspace tools for the KNEM kernel module
    ii  knem-dkms                             1.1.4.90mlnx1-OFED.5.1.2.5.0.1          all          DKMS support for mlnx-ofed kernel modules
    ii  libaio1:amd64                         0.3.112-5                               amd64        Linux kernel AIO access library - shared library
    ii  libdevmapper-event1.02.1:amd64        2:1.02.167-1ubuntu1                     amd64        Linux Kernel Device Mapper event support library
    ii  libdevmapper1.02.1:amd64              2:1.02.167-1ubuntu1                     amd64        Linux Kernel Device Mapper userspace library
    ii  libdrm-amdgpu1:amd64                  2.4.107-8ubuntu1~20.04.2                amd64        Userspace interface to amdgpu-specific kernel DRM services -- runtime
    ii  libdrm-common                         2.4.107-8ubuntu1~20.04.2                all          Userspace interface to kernel DRM services -- common files
    ii  libdrm-intel1:amd64                   2.4.107-8ubuntu1~20.04.2                amd64        Userspace interface to intel-specific kernel DRM services -- runtime
    ii  libdrm-nouveau2:amd64                 2.4.107-8ubuntu1~20.04.2                amd64        Userspace interface to nouveau-specific kernel DRM services -- runtime
    ii  libdrm-radeon1:amd64                  2.4.107-8ubuntu1~20.04.2                amd64        Userspace interface to radeon-specific kernel DRM services -- runtime
    ii  libdrm2:amd64                         2.4.107-8ubuntu1~20.04.2                amd64        Userspace interface to kernel DRM services -- runtime
    ii  linux-firmware                        1.187.29                                all          Firmware for Linux kernel drivers
    hi  linux-generic                         5.4.0.105.109                           amd64        Complete Generic Linux kernel and headers
    ii  linux-headers-5.4.0-104               5.4.0-104.118                           all          Header files related to Linux kernel version 5.4.0
    ii  linux-headers-5.4.0-104-generic       5.4.0-104.118                           amd64        Linux kernel headers for version 5.4.0 on 64 bit x86 SMP
    ii  linux-headers-5.4.0-105               5.4.0-105.119                           all          Header files related to Linux kernel version 5.4.0
    ii  linux-headers-5.4.0-105-generic       5.4.0-105.119                           amd64        Linux kernel headers for version 5.4.0 on 64 bit x86 SMP
    hi  linux-headers-generic                 5.4.0.105.109                           amd64        Generic Linux kernel headers
    ii  linux-image-5.4.0-104-generic         5.4.0-104.118                           amd64        Signed kernel image generic
    ii  linux-image-5.4.0-105-generic         5.4.0-105.119                           amd64        Signed kernel image generic
    hi  linux-image-generic                   5.4.0.105.109                           amd64        Generic Linux kernel image
    ii  linux-libc-dev:amd64                  5.4.0-105.119                           amd64        Linux Kernel Headers for development
    ii  linux-modules-5.4.0-104-generic       5.4.0-104.118                           amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
    ii  linux-modules-5.4.0-105-generic       5.4.0-105.119                           amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
    ii  linux-modules-extra-5.4.0-104-generic 5.4.0-104.118                           amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
    ii  linux-modules-extra-5.4.0-105-generic 5.4.0-105.119                           amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
    ii  mlnx-ofed-kernel-dkms                 5.4-OFED.5.4.3.0.3.1                    all          DKMS support for mlnx-ofed kernel modules
    ii  mlnx-ofed-kernel-utils                5.4-OFED.5.4.3.0.3.1                    amd64        Userspace tools to restart and tune mlnx-ofed kernel modules
    ii  mlnx-tools                            5.2.0-0.54303                           amd64        Userspace tools to restart and tune MLNX_OFED kernel modules
    ii  nvidia-kernel-common-470              470.103.01-0ubuntu0.20.04.1             amd64        Shared files used with the kernel module
    ii  nvidia-kernel-source-470              470.103.01-0ubuntu0.20.04.1             amd64        NVIDIA kernel source package
    ii  nvidia-peer-memory                    1.2-0                                   all          nvidia peer memory kernel module.
    ii  nvidia-peer-memory-dkms               1.2-0                                   all          DKMS support for nvidia-peer-memory kernel modules
    ii  rsyslog                               8.2001.0-1ubuntu1.1                     amd64        reliable system and kernel logging daemon
    ii  srp-dkms                              5.4-OFED.5.4.3.0.1.1                    all          DKMS support fo srp kernel modules
    Code block. Kernel, IB related package version check
  2. Use the apt-mark command to hold the package update.
    Color mode
    # apt-mark hold <package name>
    # apt-mark hold <package name>
    Code block. Package update hold

Intel E810 Driver Update

Check the version of the Intel E810 driver and update it to the recommended version.

Notice

The driver update method is as follows.

  1. Move the basic driver tar file to the desired directory.
Example: /home/username/ice or /usr/local/src/ice
  1. Untar / unzip the Archiver file.

    • x.x.x is the version number of the driver tar file.
      Color mode
      tar zxf ice-x.x.x.tar.gz
      tar zxf ice-x.x.x.tar.gz
      Code block. Unzip file
  2. Change to the driver src directory.

    • x.x.x is the version number of the driver tar file.
      Color mode
      cd ice-x.x.x/src/
      cd ice-x.x.x/src/
      Code block. Directory change
  3. Compile the driver module.

    Color mode
    make install
    make install
    Code Block. Driver Module Compile

  4. After the update is complete, check the version.

    Color mode
    lsmod | grep ice
    modinfo ice | grep version
    lsmod | grep ice
    modinfo ice | grep version
    Code Block. Version Check

NVIDIA driver check

Note
nvidia-smi topo, IB nv_peer_mem status check

To check the NVIDIA driver (nvidia-smi topo, IB nv_peer_mem status) and inspect the IaaS HW level, follow the next procedure.

  1. Check the GPU driver and HW status.

    Color mode
    user@bm-dev-001:~$ nvidia-smi topo -m
            GPU0    GPU1    GPU2    GPU3    GPU4    GPU5    GPU6    GPU7    mlx5_0  mlx5_1  mlx5_2  mlx5_3  CPU Affinity    NUMA Affinity
    GPU0     X      NV12    NV12    NV12    NV12    NV12    NV12    NV12    SYS     PXB     SYS     SYS     48-63   3
    GPU1    NV12     X      NV12    NV12    NV12    NV12    NV12    NV12    SYS     PXB     SYS     SYS     48-63   3
    GPU2    NV12    NV12     X      NV12    NV12    NV12    NV12    NV12    PXB     SYS     SYS     SYS     16-31   1
    GPU3    NV12    NV12    NV12     X      NV12    NV12    NV12    NV12    PXB     SYS     SYS     SYS     16-31   1
    GPU4    NV12    NV12    NV12    NV12     X      NV12    NV12    NV12    SYS     SYS     SYS     PXB     112-127 7
    GPU5    NV12    NV12    NV12    NV12    NV12     X      NV12    NV12    SYS     SYS     SYS     PXB     112-127 7
    GPU6    NV12    NV12    NV12    NV12    NV12    NV12     X      NV12    SYS     SYS     PXB     SYS     80-95   5
    GPU7    NV12    NV12    NV12    NV12    NV12    NV12    NV12     X      SYS     SYS     PXB     SYS     80-95   5
    mlx5_0  SYS     SYS     PXB     PXB     SYS     SYS     SYS     SYS      X      SYS     SYS     SYS
    mlx5_1  PXB     PXB     SYS     SYS     SYS     SYS     SYS     SYS     SYS      X      SYS     SYS
    mlx5_2  SYS     SYS     SYS     SYS     SYS     SYS     PXB     PXB     SYS     SYS      X      SYS
    mlx5_3  SYS     SYS     SYS     SYS     PXB     PXB     SYS     SYS     SYS     SYS     SYS      X
    
    Legend:
    
      X    = Self
      SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
      NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
      PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
      PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
      PIX  = Connection traversing at most a single PCIe bridge
      NV#  = Connection traversing a bonded set of # NVLinks
    user@bm-dev-001:~$ nvidia-smi topo -m
            GPU0    GPU1    GPU2    GPU3    GPU4    GPU5    GPU6    GPU7    mlx5_0  mlx5_1  mlx5_2  mlx5_3  CPU Affinity    NUMA Affinity
    GPU0     X      NV12    NV12    NV12    NV12    NV12    NV12    NV12    SYS     PXB     SYS     SYS     48-63   3
    GPU1    NV12     X      NV12    NV12    NV12    NV12    NV12    NV12    SYS     PXB     SYS     SYS     48-63   3
    GPU2    NV12    NV12     X      NV12    NV12    NV12    NV12    NV12    PXB     SYS     SYS     SYS     16-31   1
    GPU3    NV12    NV12    NV12     X      NV12    NV12    NV12    NV12    PXB     SYS     SYS     SYS     16-31   1
    GPU4    NV12    NV12    NV12    NV12     X      NV12    NV12    NV12    SYS     SYS     SYS     PXB     112-127 7
    GPU5    NV12    NV12    NV12    NV12    NV12     X      NV12    NV12    SYS     SYS     SYS     PXB     112-127 7
    GPU6    NV12    NV12    NV12    NV12    NV12    NV12     X      NV12    SYS     SYS     PXB     SYS     80-95   5
    GPU7    NV12    NV12    NV12    NV12    NV12    NV12    NV12     X      SYS     SYS     PXB     SYS     80-95   5
    mlx5_0  SYS     SYS     PXB     PXB     SYS     SYS     SYS     SYS      X      SYS     SYS     SYS
    mlx5_1  PXB     PXB     SYS     SYS     SYS     SYS     SYS     SYS     SYS      X      SYS     SYS
    mlx5_2  SYS     SYS     SYS     SYS     SYS     SYS     PXB     PXB     SYS     SYS      X      SYS
    mlx5_3  SYS     SYS     SYS     SYS     PXB     PXB     SYS     SYS     SYS     SYS     SYS      X
    
    Legend:
    
      X    = Self
      SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
      NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
      PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
      PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
      PIX  = Connection traversing at most a single PCIe bridge
      NV#  = Connection traversing a bonded set of # NVLinks
    Code Block. GPU Driver and HW Status Check

  2. Check the NVSwitch HW status.

    Color mode
    user@bm-dev-001:~$ nvidia-smi nvlink --status
    GPU 0: NVIDIA A100-SXM4-80GB (UUID: GPU-2c0d1d6b-e348-55fc-44cf-cd65a954b36c)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    GPU 1: NVIDIA A100-SXM4-80GB (UUID: GPU-96f429d8-893a-a9ea-deca-feffd90669e9)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    GPU 2: NVIDIA A100-SXM4-80GB (UUID: GPU-2e601952-b442-b757-a035-725cd320f589)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    GPU 3: NVIDIA A100-SXM4-80GB (UUID: GPU-bcbfd885-a9f8-ec8c-045b-c521472b4fed)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    GPU 4: NVIDIA A100-SXM4-80GB (UUID: GPU-30273090-2d78-fc7a-a360-ec5f871dd488)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    GPU 5: NVIDIA A100-SXM4-80GB (UUID: GPU-5ce7ef61-56dd-fb18-aa7c-be610c8d51c3)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    GPU 6: NVIDIA A100-SXM4-80GB (UUID: GPU-740a527b-b286-8b85-35eb-b6b41c0bb6d7)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    GPU 7: NVIDIA A100-SXM4-80GB (UUID: GPU-1fb6de95-60f6-dbf2-ffca-f7680577e37c)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    user@bm-dev-001:~$ nvidia-smi nvlink --status
    GPU 0: NVIDIA A100-SXM4-80GB (UUID: GPU-2c0d1d6b-e348-55fc-44cf-cd65a954b36c)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    GPU 1: NVIDIA A100-SXM4-80GB (UUID: GPU-96f429d8-893a-a9ea-deca-feffd90669e9)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    GPU 2: NVIDIA A100-SXM4-80GB (UUID: GPU-2e601952-b442-b757-a035-725cd320f589)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    GPU 3: NVIDIA A100-SXM4-80GB (UUID: GPU-bcbfd885-a9f8-ec8c-045b-c521472b4fed)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    GPU 4: NVIDIA A100-SXM4-80GB (UUID: GPU-30273090-2d78-fc7a-a360-ec5f871dd488)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    GPU 5: NVIDIA A100-SXM4-80GB (UUID: GPU-5ce7ef61-56dd-fb18-aa7c-be610c8d51c3)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    GPU 6: NVIDIA A100-SXM4-80GB (UUID: GPU-740a527b-b286-8b85-35eb-b6b41c0bb6d7)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    GPU 7: NVIDIA A100-SXM4-80GB (UUID: GPU-1fb6de95-60f6-dbf2-ffca-f7680577e37c)
             Link 0: 25 GB/s
             Link 1: 25 GB/s
             Link 2: 25 GB/s
             Link 3: 25 GB/s
             Link 4: 25 GB/s
             Link 5: 25 GB/s
             Link 6: 25 GB/s
             Link 7: 25 GB/s
             Link 8: 25 GB/s
             Link 9: 25 GB/s
             Link 10: 25 GB/s
             Link 11: 25 GB/s
    Code block. NVSwitch HW status check

  3. Check the InfiniBand(IB) HCA card HW status and Link.

    Color mode
    user@bm-dev-001:~$ ibdev2netdev -v
    cat: /sys/class/infiniband/mlx5_0/device/vpd: Permission denied
    0000:45:00.0 mlx5_0 (MT4123 -            )                 fw 20.29.1016 port 1 (ACTIVE) ==> ibs18 (Down)
    cat: /sys/class/infiniband/mlx5_1/device/vpd: Permission denied
    0000:0e:00.0 mlx5_1 (MT4123 -            )                 fw 20.29.1016 port 1 (ACTIVE) ==> ibs17 (Down)
    cat: /sys/class/infiniband/mlx5_2/device/vpd: Permission denied
    0000:c5:00.0 mlx5_2 (MT4123 -            )                 fw 20.29.1016 port 1 (ACTIVE) ==> ibs20 (Down)
    cat: /sys/class/infiniband/mlx5_3/device/vpd: Permission denied
    0000:85:00.0 mlx5_3 (MT4123 -            )                 fw 20.29.1016 port 1 (ACTIVE) ==> ibs19 (Down)
    user@bm-dev-001:~$
    
    
    root@bm-dev-001:~# ibstat
    CA 'mlx5_0'
            CA type: MT4123
            Number of ports: 1
            Firmware version: 20.29.1016
            Hardware version: 0
            Node GUID: 0x88e9a4ffff5060ac
            System image GUID: 0x88e9a4ffff5060ac
            Port 1:
                    State: Active
                    Physical state: LinkUp
                    Rate: 200
                    Base lid: 8
                    LMC: 0
                    SM lid: 1
                    Capability mask: 0x2651e848
                    Port GUID: 0x88e9a4ffff5060ac
                    Link layer: InfiniBand
    CA 'mlx5_1'
            CA type: MT4123
            Number of ports: 1
            Firmware version: 20.29.1016
            Hardware version: 0
            Node GUID: 0x88e9a4ffff504080
            System image GUID: 0x88e9a4ffff504080
            Port 1:
                    State: Active
                    Physical state: LinkUp
                    Rate: 200
                    Base lid: 5
                    LMC: 0
                    SM lid: 1
                    Capability mask: 0x2651e848
                    Port GUID: 0x88e9a4ffff504080
                    Link layer: InfiniBand
    CA 'mlx5_2'
            CA type: MT4123
            Number of ports: 1
            Firmware version: 20.29.1016
            Hardware version: 0
            Node GUID: 0x88e9a4ffff505038
            System image GUID: 0x88e9a4ffff505038
            Port 1:
                    State: Active
                    Physical state: LinkUp
                    Rate: 200
                    Base lid: 2
                    LMC: 0
                    SM lid: 1
                    Capability mask: 0x2651e848
                    Port GUID: 0x88e9a4ffff505038
                    Link layer: InfiniBand
    CA 'mlx5_3'
            CA type: MT4123
            Number of ports: 1
            Firmware version: 20.29.1016
            Hardware version: 0
            Node GUID: 0x88e9a4ffff504094
            System image GUID: 0x88e9a4ffff504094
            Port 1:
                    State: Active
                    Physical state: LinkUp
                    Rate: 200
                    Base lid: 7
                    LMC: 0
                    SM lid: 1
                    Capability mask: 0x2651e848
                    Port GUID: 0x88e9a4ffff504094
                    Link layer: InfiniBand
    user@bm-dev-001:~$ ibdev2netdev -v
    cat: /sys/class/infiniband/mlx5_0/device/vpd: Permission denied
    0000:45:00.0 mlx5_0 (MT4123 -            )                 fw 20.29.1016 port 1 (ACTIVE) ==> ibs18 (Down)
    cat: /sys/class/infiniband/mlx5_1/device/vpd: Permission denied
    0000:0e:00.0 mlx5_1 (MT4123 -            )                 fw 20.29.1016 port 1 (ACTIVE) ==> ibs17 (Down)
    cat: /sys/class/infiniband/mlx5_2/device/vpd: Permission denied
    0000:c5:00.0 mlx5_2 (MT4123 -            )                 fw 20.29.1016 port 1 (ACTIVE) ==> ibs20 (Down)
    cat: /sys/class/infiniband/mlx5_3/device/vpd: Permission denied
    0000:85:00.0 mlx5_3 (MT4123 -            )                 fw 20.29.1016 port 1 (ACTIVE) ==> ibs19 (Down)
    user@bm-dev-001:~$
    
    
    root@bm-dev-001:~# ibstat
    CA 'mlx5_0'
            CA type: MT4123
            Number of ports: 1
            Firmware version: 20.29.1016
            Hardware version: 0
            Node GUID: 0x88e9a4ffff5060ac
            System image GUID: 0x88e9a4ffff5060ac
            Port 1:
                    State: Active
                    Physical state: LinkUp
                    Rate: 200
                    Base lid: 8
                    LMC: 0
                    SM lid: 1
                    Capability mask: 0x2651e848
                    Port GUID: 0x88e9a4ffff5060ac
                    Link layer: InfiniBand
    CA 'mlx5_1'
            CA type: MT4123
            Number of ports: 1
            Firmware version: 20.29.1016
            Hardware version: 0
            Node GUID: 0x88e9a4ffff504080
            System image GUID: 0x88e9a4ffff504080
            Port 1:
                    State: Active
                    Physical state: LinkUp
                    Rate: 200
                    Base lid: 5
                    LMC: 0
                    SM lid: 1
                    Capability mask: 0x2651e848
                    Port GUID: 0x88e9a4ffff504080
                    Link layer: InfiniBand
    CA 'mlx5_2'
            CA type: MT4123
            Number of ports: 1
            Firmware version: 20.29.1016
            Hardware version: 0
            Node GUID: 0x88e9a4ffff505038
            System image GUID: 0x88e9a4ffff505038
            Port 1:
                    State: Active
                    Physical state: LinkUp
                    Rate: 200
                    Base lid: 2
                    LMC: 0
                    SM lid: 1
                    Capability mask: 0x2651e848
                    Port GUID: 0x88e9a4ffff505038
                    Link layer: InfiniBand
    CA 'mlx5_3'
            CA type: MT4123
            Number of ports: 1
            Firmware version: 20.29.1016
            Hardware version: 0
            Node GUID: 0x88e9a4ffff504094
            System image GUID: 0x88e9a4ffff504094
            Port 1:
                    State: Active
                    Physical state: LinkUp
                    Rate: 200
                    Base lid: 7
                    LMC: 0
                    SM lid: 1
                    Capability mask: 0x2651e848
                    Port GUID: 0x88e9a4ffff504094
                    Link layer: InfiniBand
    Code block. InfiniBand(IB) HCA card HW status and Link check

IB bandwidth communication check

To check the IB bandwidth communication status (ib_send_bw) and inspect the IaaS HW level, follow these steps.

  1. Check the name of the IB HCA interface.

    Color mode
    user@bm-dev-001:~$ ibdev2netdev
    mlx5_0 port 1 ==> ibs18 (Down)
    mlx5_1 port 1 ==> ibs17 (Down)
    mlx5_2 port 1 ==> ibs20 (Down)
    mlx5_3 port 1 ==> ibs19 (Down)
    user@bm-dev-001:~$ ibdev2netdev
    mlx5_0 port 1 ==> ibs18 (Down)
    mlx5_1 port 1 ==> ibs17 (Down)
    mlx5_2 port 1 ==> ibs20 (Down)
    mlx5_3 port 1 ==> ibs19 (Down)
    Code block. Check the name of IB HCA interface

  2. Check the HCA interface that can communicate with IB Switch#1.

    Color mode
    mlx5_0 port 1 ==> ibs18 (Down)
    mlx5_2 port 1 ==> ibs20 (Down)
    mlx5_0 port 1 ==> ibs18 (Down)
    mlx5_2 port 1 ==> ibs20 (Down)
    Code Block. HCA Interface Check

  3. Check the HCA interface that can communicate with IB Switch#2.

    Color mode
    mlx5_1 port 1 ==> ibs17 (Down)
    mlx5_3 port 1 ==> ibs19 (Down)
    mlx5_1 port 1 ==> ibs17 (Down)
    mlx5_3 port 1 ==> ibs19 (Down)
    Code Block. HCA Interface Check

  4. Use SERVER Side commands to check the communication status.

    • Client Side command is entered secondarily for mutual communication
      Color mode
      user@bm-dev-001:~$ ib_send_bw -d mlx5_3 -i 1 –F
      ************************************
      * Waiting for client to connect... *
      ************************************
      ---------------------------------------------------------------------------------------
                          Send BW Test
       Dual-port       : OFF          Device         : mlx5_3
       Number of qps   : 1            Transport type : IB
       Connection type : RC           Using SRQ      : OFF
       PCIe relax order: ON
       ibv_wr* API     : ON
       RX depth        : 512
       CQ Moderation   : 1
       Mtu             : 4096[B]
       Link type       : IB
       Max inline data : 0[B]
       rdma_cm QPs     : OFF
       Data ex. method : Ethernet
      ---------------------------------------------------------------------------------------
       local address: LID 0x07 QPN 0x002e PSN 0xa86622
       remote address: LID 0x0a QPN 0x002d PSN 0xfc58dd
      ---------------------------------------------------------------------------------------
       #bytes     #iterations    BW peak[MB/sec]    BW average[MB/sec]   MsgRate[Mpps]
       65536      1000             0.00               19827.40                   0.317238
      ---------------------------------------------------------------------------------------
      user@bm-dev-001:~$ ib_send_bw -d mlx5_3 -i 1 –F
      ************************************
      * Waiting for client to connect... *
      ************************************
      ---------------------------------------------------------------------------------------
                          Send BW Test
       Dual-port       : OFF          Device         : mlx5_3
       Number of qps   : 1            Transport type : IB
       Connection type : RC           Using SRQ      : OFF
       PCIe relax order: ON
       ibv_wr* API     : ON
       RX depth        : 512
       CQ Moderation   : 1
       Mtu             : 4096[B]
       Link type       : IB
       Max inline data : 0[B]
       rdma_cm QPs     : OFF
       Data ex. method : Ethernet
      ---------------------------------------------------------------------------------------
       local address: LID 0x07 QPN 0x002e PSN 0xa86622
       remote address: LID 0x0a QPN 0x002d PSN 0xfc58dd
      ---------------------------------------------------------------------------------------
       #bytes     #iterations    BW peak[MB/sec]    BW average[MB/sec]   MsgRate[Mpps]
       65536      1000             0.00               19827.40                   0.317238
      ---------------------------------------------------------------------------------------
      Code Block. Communication Status Check
  5. Use the CLIENT Side command to check the communication status.

    • SERVER Side command is entered first for mutual communication
      Color mode
      root@bm-dev-003:~# ib_send_bw -d mlx5_3 -i 1 -F <SERVER Side IP>
      ---------------------------------------------------------------------------------------
                          Send BW Test
       Dual-port       : OFF          Device         : mlx5_3
       Number of qps   : 1            Transport type : IB
       Connection type : RC           Using SRQ      : OFF
       PCIe relax order: ON
       ibv_wr* API     : ON
       TX depth        : 128
       CQ Moderation   : 1
       Mtu             : 4096[B]
       Link type       : IB
       Max inline data : 0[B]
       rdma_cm QPs     : OFF
       Data ex. method : Ethernet
      ---------------------------------------------------------------------------------------
       local address: LID 0x0a QPN 0x002a PSN 0x98a48e
       remote address: LID 0x07 QPN 0x002c PSN 0xe68304
      ---------------------------------------------------------------------------------------
       #bytes     #iterations    BW peak[MB/sec]    BW average[MB/sec]   MsgRate[Mpps]
       65536      1000             19008.49            19006.37                  0.304102
      ---------------------------------------------------------------------------------------
      root@bm-dev-003:~# ib_send_bw -d mlx5_3 -i 1 -F <SERVER Side IP>
      ---------------------------------------------------------------------------------------
                          Send BW Test
       Dual-port       : OFF          Device         : mlx5_3
       Number of qps   : 1            Transport type : IB
       Connection type : RC           Using SRQ      : OFF
       PCIe relax order: ON
       ibv_wr* API     : ON
       TX depth        : 128
       CQ Moderation   : 1
       Mtu             : 4096[B]
       Link type       : IB
       Max inline data : 0[B]
       rdma_cm QPs     : OFF
       Data ex. method : Ethernet
      ---------------------------------------------------------------------------------------
       local address: LID 0x0a QPN 0x002a PSN 0x98a48e
       remote address: LID 0x07 QPN 0x002c PSN 0xe68304
      ---------------------------------------------------------------------------------------
       #bytes     #iterations    BW peak[MB/sec]    BW average[MB/sec]   MsgRate[Mpps]
       65536      1000             19008.49            19006.37                  0.304102
      ---------------------------------------------------------------------------------------
      Code Block. Communication Status Check

Check the IB service-related kernel modules (lsmod) to inspect the IaaS HW level.

Color mode
user@bm-dev-001:~$ lsmod | grep nv_peer_mem
nv_peer_mem            16384  0
ib_core               315392  9 rdma_cm,ib_ipoib,nv_peer_mem,iw_cm,ib_umad,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm
nvidia              35315712  156 nvidia_uvm,nv_peer_mem,nvidia_modeset
user@bm-dev-001:~$ lsmod | grep nv_peer_mem
nv_peer_mem            16384  0
ib_core               315392  9 rdma_cm,ib_ipoib,nv_peer_mem,iw_cm,ib_umad,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm
nvidia              35315712  156 nvidia_uvm,nv_peer_mem,nvidia_modeset
Code block. IB service related kernel module check(1)
Color mode
user@bm-dev-001:~$ service nv_peer_mem status
  nv_peer_mem.service - LSB: Activates/Deactivates nv_peer_mem to \ start at boot time.
     Loaded: loaded (/etc/init.d/nv_peer_mem; generated)
     Active: active (exited) since Mon 2023-03-13 16:21:33 KST; 2 days ago
       Docs: man:systemd-sysv-generator(8)
    Process: 4913 ExecStart=/etc/init.d/nv_peer_mem start (code=exited, status=0/SUCCESS)
user@bm-dev-001:~$ service nv_peer_mem status
  nv_peer_mem.service - LSB: Activates/Deactivates nv_peer_mem to \ start at boot time.
     Loaded: loaded (/etc/init.d/nv_peer_mem; generated)
     Active: active (exited) since Mon 2023-03-13 16:21:33 KST; 2 days ago
       Docs: man:systemd-sysv-generator(8)
    Process: 4913 ExecStart=/etc/init.d/nv_peer_mem start (code=exited, status=0/SUCCESS)
Code block. IB service-related kernel module check(2)
Color mode
user@bm-dev-001:~$ lsmod | grep ib
libiscsi_tcp           32768  1 iscsi_tcp
libiscsi               57344  2 libiscsi_tcp,iscsi_tcp
scsi_transport_iscsi   110592  4 libiscsi_tcp,iscsi_tcp,libiscsi
ib_ipoib              131072  0
ib_cm                  57344  2 rdma_cm,ib_ipoib
ib_umad                24576  8
mlx5_ib               380928  0
ib_uverbs             135168  18 rdma_ucm,mlx5_ib
ib_core               315392  9 rdma_cm,ib_ipoib,nv_peer_mem,iw_cm,ib_umad,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm
libcrc32c              16384  2 btrfs,raid456
mlx5_core            1458176  1 mlx5_ib
auxiliary              16384  2 mlx5_ib,mlx5_core
mlx_compat             65536  12 rdma_cm,ib_ipoib,mlxdevm,iw_cm,auxiliary,ib_umad,ib_core,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm,mlx5_core
user@bm-dev-001:~$ lsmod | grep ib
libiscsi_tcp           32768  1 iscsi_tcp
libiscsi               57344  2 libiscsi_tcp,iscsi_tcp
scsi_transport_iscsi   110592  4 libiscsi_tcp,iscsi_tcp,libiscsi
ib_ipoib              131072  0
ib_cm                  57344  2 rdma_cm,ib_ipoib
ib_umad                24576  8
mlx5_ib               380928  0
ib_uverbs             135168  18 rdma_ucm,mlx5_ib
ib_core               315392  9 rdma_cm,ib_ipoib,nv_peer_mem,iw_cm,ib_umad,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm
libcrc32c              16384  2 btrfs,raid456
mlx5_core            1458176  1 mlx5_ib
auxiliary              16384  2 mlx5_ib,mlx5_core
mlx_compat             65536  12 rdma_cm,ib_ipoib,mlxdevm,iw_cm,auxiliary,ib_umad,ib_core,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm,mlx5_core
Code block. IB service-related kernel module check(3)

Storage Physical Disk Resources and Multi-Path Check

Check the IaaS HW level by checking the storage physical disk resources and Multi-Path.

Color mode
root@bm-dev-002:/tmp# fdisk –l
root@bm-dev-002:/tmp# fdisk –l
Code block. Storage physical disk resource check result
Color mode
root@bm-dev-002:/tmp# multipath –ll
root@bm-dev-002:/tmp# multipath –ll
Code Block. Multi-Path Verification Result

Multi-node GPU Cluster new deployment after checking Service Network

Use the following command to check if the MII Status of Bonding and Slave Interface is up.

  • command

    Color mode
    root@mngc-001:~# cat /proc/net/bonding/bond-srv
    Ethernet Channel Bonding Driver: v5.15.0-25-generic
    root@mngc-001:~# cat /proc/net/bonding/bond-srv
    Ethernet Channel Bonding Driver: v5.15.0-25-generic
    Code Block. Service Network Check Command

  • confirmation result

    Color mode
    Bonding Mode: fault-tolerance (active-backup)
    Primary Slave: None
    Currently Active Slave: ens9f0
    MII Status: up
    MII Polling Interval (ms): 100
    Up Delay (ms): 0
    Down Delay (ms): 0
    Peer Notification Delay (ms): 0
    
    Slave Interface: ens9f0
    MII Status: up
    Speed: 100000 Mbps
    Duplex: full
    Link Failure Count: 0
    Permanent HW addr: 30:3e:a7:02:35:70
    Slave queue ID: 0
    
    Slave Interface: ens11f0
    MII Status: up
    Speed: 100000 Mbps
    Duplex: full
    Link Failure Count: 0
    Permanent HW addr: 30:3e:a7:02:2f:e8
    Slave queue ID: 0
    Bonding Mode: fault-tolerance (active-backup)
    Primary Slave: None
    Currently Active Slave: ens9f0
    MII Status: up
    MII Polling Interval (ms): 100
    Up Delay (ms): 0
    Down Delay (ms): 0
    Peer Notification Delay (ms): 0
    
    Slave Interface: ens9f0
    MII Status: up
    Speed: 100000 Mbps
    Duplex: full
    Link Failure Count: 0
    Permanent HW addr: 30:3e:a7:02:35:70
    Slave queue ID: 0
    
    Slave Interface: ens11f0
    MII Status: up
    Speed: 100000 Mbps
    Duplex: full
    Link Failure Count: 0
    Permanent HW addr: 30:3e:a7:02:2f:e8
    Slave queue ID: 0
    Code Block. Service Network Check Command Result

Reference
If some Slave Interface is in a down state, please use the Support Center’s Contact Us to report the abnormal situation and take action.

Multi-node GPU Cluster new deployment after checking Time Server and time synchronization

The OS image has the chrony daemon installed and set to synchronize with the SCP NTP server. Use the following command to check if there are any lines marked with ^* in the MS Name column.

  • command

    Color mode
    root@mngc-001:~# chronyc sources -V
    root@mngc-001:~# chronyc sources -V
    Code Block. chrony daemon installation command

  • confirmation result

    Color mode
    MS Name/IP address         Stratum Poll Reach LastRx Last sample
    ===============================================================================
    ^+ 198.19.1.53                   4  10   377  1040    -16us[  -37us] +/- 9982us
    ^* 198.19.1.54                   4  10   377   312   -367us[ -388us] +/-   13ms
    MS Name/IP address         Stratum Poll Reach LastRx Last sample
    ===============================================================================
    ^+ 198.19.1.53                   4  10   377  1040    -16us[  -37us] +/- 9982us
    ^* 198.19.1.54                   4  10   377   312   -367us[ -388us] +/-   13ms
    Code block. chrony daemon installation check result

GPU MIG/ECC Setting Initialization Check Guide

When applying for a multi-node GPU cluster product, the GPU MIG/ECC setting is initialized. However, to apply the exact setting value, please restart it once at the beginning, and then check and use it according to the inspection guide to see if the setting value is applied.

Reference
  • MIG: Multi-Instance GPU
  • ECC: Error Correction Code

MIG Setup Initialization

Refer to the following for how to check and initialize MIG settings.

Use the following command to check if the status value of MIG M is Disabled.

  • command

    Color mode
    root@bm-dev-001:~#nvidia-smi
    root@bm-dev-001:~#nvidia-smi
    Code Block. MIG M. Initialize Settings

  • confirmation result

    Color mode
    +-----------------------------------------------------------------------------------------+
    |  NVIDIA-SMI 470.129.06        Driver version: 470.129.06        CUDA Version: 11.4      |
    |----------------------------------+-----------------------------+------------------------|
    |  GPU  Name        Persistence-M  |  Bus-Id             Disp.A  |  Volatile Uncorr. ECC  |
    |  Fan  Temp  Perf  Pwr:Usage/Cap  |               Memory-Usage  |  GPU-Util  Compute M.  |
    |                                  |                             |                MIG M.  |
    |==================================+=============================+========================|
    |    0  NVIDIA A100-SXM...    Off  |  00000000:03:00.0      Off  |                   Off  |
    |  N/A  29C     P0    57W  /  400W |          0MiB  /  81251MiB  |    0%         Default  |
    |                                  |                             |              Disabled  |
    +----------------------------------+-----------------------------+------------------------+
    |    0  NVIDIA A100-SXM...    Off  |  00000000:0C:00.0      Off  |                   Off  |
    |  N/A  30C     P0    58W  /  400W |          0MiB  /  81251MiB  |    18%        Default  |
    |                                  |                             |              Disabled  |
    +-----------------------------------------------------------------------------------------+
    +-----------------------------------------------------------------------------------------+
    |  NVIDIA-SMI 470.129.06        Driver version: 470.129.06        CUDA Version: 11.4      |
    |----------------------------------+-----------------------------+------------------------|
    |  GPU  Name        Persistence-M  |  Bus-Id             Disp.A  |  Volatile Uncorr. ECC  |
    |  Fan  Temp  Perf  Pwr:Usage/Cap  |               Memory-Usage  |  GPU-Util  Compute M.  |
    |                                  |                             |                MIG M.  |
    |==================================+=============================+========================|
    |    0  NVIDIA A100-SXM...    Off  |  00000000:03:00.0      Off  |                   Off  |
    |  N/A  29C     P0    57W  /  400W |          0MiB  /  81251MiB  |    0%         Default  |
    |                                  |                             |              Disabled  |
    +----------------------------------+-----------------------------+------------------------+
    |    0  NVIDIA A100-SXM...    Off  |  00000000:0C:00.0      Off  |                   Off  |
    |  N/A  30C     P0    58W  /  400W |          0MiB  /  81251MiB  |    18%        Default  |
    |                                  |                             |              Disabled  |
    +-----------------------------------------------------------------------------------------+
    Code Block. MIG M. Initialization Setting Check Result

  • If MIG M.’s status value is not Disabled, use the following command to initialize MIG.

    Color mode
    root@bm-dev-001:~# nvidia-smi -mig 0
    root@bm-dev-001:~# nvidia-smi --gpu-reset
    root@bm-dev-001:~# nvidia-smi -mig 0
    root@bm-dev-001:~# nvidia-smi --gpu-reset
    Code Block. MIG M. Status Value Initialization

ECC Setting Initialization

Refer to the following for how to check and initialize the ECC settings.

Use the following command to check if the status value of Volatile Uncorr. ECC is Off.

  • command

    Color mode
    root@bm-dev-001:~#nvidia-smi
    root@bm-dev-001:~#nvidia-smi
    Code Block. ECC Setting Command

  • confirmation result

    Color mode
    +-----------------------------------------------------------------------------------------+
    |  NVIDIA-SMI 470.129.06        Driver version: 470.129.06        CUDA Version: 11.4      |
    |----------------------------------+-----------------------------+------------------------|
    |  GPU  Name        Persistence-M  |  Bus-Id             Disp.A  |  Volatile Uncorr. ECC  |
    |  Fan  Temp  Perf  Pwr:Usage/Cap  |               Memory-Usage  |  GPU-Util  Compute M.  |
    |                                  |                             |                MIG M.  |
    |==================================+=============================+========================|
    |    0  NVIDIA A100-SXM...    Off  |  00000000:03:00.0      Off  |                   Off  |
    |  N/A  29C     P0    57W  /  400W |          0MiB  /  81251MiB  |    0%         Default  |
    |                                  |                             |              Disabled  |
    +----------------------------------+-----------------------------+------------------------+
    |    0  NVIDIA A100-SXM...    Off  |  00000000:0C:00.0      Off  |                   Off  |
    |  N/A  30C     P0    61W  /  400W |          0MiB  /  81251MiB  |    18%        Default  |
    |                                  |                             |              Disabled  |
    +-----------------------------------------------------------------------------------------+
    +-----------------------------------------------------------------------------------------+
    |  NVIDIA-SMI 470.129.06        Driver version: 470.129.06        CUDA Version: 11.4      |
    |----------------------------------+-----------------------------+------------------------|
    |  GPU  Name        Persistence-M  |  Bus-Id             Disp.A  |  Volatile Uncorr. ECC  |
    |  Fan  Temp  Perf  Pwr:Usage/Cap  |               Memory-Usage  |  GPU-Util  Compute M.  |
    |                                  |                             |                MIG M.  |
    |==================================+=============================+========================|
    |    0  NVIDIA A100-SXM...    Off  |  00000000:03:00.0      Off  |                   Off  |
    |  N/A  29C     P0    57W  /  400W |          0MiB  /  81251MiB  |    0%         Default  |
    |                                  |                             |              Disabled  |
    +----------------------------------+-----------------------------+------------------------+
    |    0  NVIDIA A100-SXM...    Off  |  00000000:0C:00.0      Off  |                   Off  |
    |  N/A  30C     P0    61W  /  400W |          0MiB  /  81251MiB  |    18%        Default  |
    |                                  |                             |              Disabled  |
    +-----------------------------------------------------------------------------------------+
    Code Block. ECC Setting Check Result

  • Volatile Uncorr. ECC’s status value is On*, please proceed with rebooting.

  • Volatile Uncorr. ECC status value is not On* or Off, use the following command to initialize ECC. After initialization, reboot and check if the status value is Off.

Color mode
root@bm-dev-001:~# nvidia-smi --ecc-config=0
root@bm-dev-001:~# nvidia-smi --ecc-config=0
Code Block. ECC Status Value Check

2.5.3 - Release Note

Multi-node GPU Cluster

2025.07.01
FEATURE New feature added and monitoring linked
  • You can cancel multiple resources at the same time from the GPU Node list.
  • The nodes must use the same DataSet and Cluster Fabric.
  • It has been linked with Cloud Monitoring.
    • You can check major performance items in real-time in Cloud Monitoring.
2025.02.27
NEW Multi-node GPU Cluster Service Official Version Release
  • Multi-node GPU Cluster service has been launched.
    • Provides a service that offers physical GPU servers without virtualization for large-scale high-performance AI computing.

2.6 - Cloud Functions

2.6.1 - Overview

Service Overview

Cloud Functions is a serverless computing-based FaaS (Function as a Service) that allows you to run applications in the form of functions without the need for server provisioning. The user does not need to manage servers or containers cumbersomely for scale adjustment, and can focus on writing and deploying code for application development.

Features

  • Easy and convenient development environment: Developers can easily create Function resources connected to events in various environments using a Code Editor suitable for the chosen runtime, and can write and call code easily.
  • Serverless Computing: You can use a serverless type of code execution service for development in the Samsung Cloud Platform environment. The resources required to call and execute function-type applications are allocated and managed by Samsung Cloud Platform according to the scale of execution.
  • Efficient Cost Management: The called Function is charged only for the actual application runtime by aggregating usage (total number of calls, total call time). Functions with low usage are adjusted to Scale-to-zero state by Cloud Functions’ Scaler, preventing resource consumption, thus enabling efficient cost management.

Service Composition Diagram

composition diagram
Figure. Cloud_Functions composition diagram

Provided Features

Cloud Functions provides the following features.

  • Code Writing Environment: Runtime-optimized Function creation, Code writing and editing
  • Function execution, environment management, monitoring: endpoint definition, Token management, access control setting, trigger setting, etc., definition and modification of operating environment/variables, calling/testing output for Deploy/Test, service deployment, progress status monitoring/logging
  • Serverless Computing: all elements required for code writing and deployment are managed by Samsung Cloud Platform, with automatic scale adjustment according to deployment
  • Sample Code Provided: Provides various sample codes through Blueprint, allowing for easy and quick start

Component

Runtime

Cloud Functions currently supports the following Runtime, and more supported Runtime will be added continuously.

RuntimeVersion
GO1.21, 1.23
java17
Node.js18, 20
PHP8.1
Python3.9, 3.10, 3.11
Table. Supported Runtime Items

Regional Provision Status

Cloud Functions service is available in the following environments.

RegionAvailability
Korea West 1(kr-west1)Provided
Korean East 1 (kr-east1)Provided
South Korea (kr-south1)Not provided
South Korea southern region 2(kr-south2)Not provided
South Korea southern region 3(kr-south3)Not provided
Table. Cloud Functions Region-wise Availability

Preceding Service

This is a list of services that can be configured as optional before creating the service. Please refer to the guide provided for each service and prepare in advance for more information.

Service CategoryServiceDetailed Description
Application ServiceAPI GatewayA service that easily manages and monitors APIs
Fig. Preceding Cloud Functions Service

2.6.1.1 - ServiceWatch Metrics

Cloud Functions sends metrics to ServiceWatch. The metrics provided by default monitoring are data collected at a 1‑minute interval.

Reference
To check metrics in ServiceWatch, refer to the ServiceWatch guide.

Basic Indicators

The following are the basic metrics for the Cloud Functions namespace.

Performance ItemDetailed DescriptionUnitMeaningful Statistics
Table. Cloud Functions Basic Metrics

2.6.2 - How-to guides

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

Cloud Functions Create

  1. Click the All Services > Compute > Cloud Functions menu. Navigate to the Service Home page of Cloud Functions.

  2. Click the Create Cloud Functions button on the Service Home page. It navigates to the Create Cloud Functions page.

  3. Create Cloud Functions page, enter the information required to create the service.

    Category
    Required
    Detailed description
    Funtion nameRequiredEnter the Funtion name to create
    • Start with a lowercase English letter and use lowercase English letters, numbers, and special characters (-) to input within 3 ~ 64 characters
    RuntimeRequiredSelect Runtime creation method
    • Create new: Create a new Runtime
    • Start with Blueprint: Create using the Runtime source code provided by the service
    Runtime & VersionRequiredSelect Runtime and Version
    • When Create New is selected
      • For Java runtime, UI code editing is not supported, but you can run by fetching a Jar file from Object Storage
    • When Start with Blueprint is selected
      • You can view source code examples by clicking the View Source Code button for the selected Runtime & Version
    Table. Cloud Functions Service 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 resource on the Cloud Functions list page.

Cloud Functions Check Detailed Information

Cloud Functions Details page consists of Detail Information, Monitoring, Log, Code, Configuration, Trigger, Tag, Job History tabs.

To view detailed information about the Cloud Functions service, follow these steps.

  1. All Services > Compute > Cloud Functions Click the menu. Go to the Service Home page of Cloud Functions.
  2. Click the Function menu on the Service Home page. Move to the Function List page.
  3. Click the resource to view detailed information on the Function list page. Go to the Function detail page.
  • Function Details The page displays status information and additional feature information, and consists of the Details, Monitoring, Log, Code, Configuration, Trigger, Tag, Task History tabs.
    CategoryDetailed description
    Cloud Functions statusCloud Functions status information
    • Ready: green icon, state where normal function calls are possible
    • Not Ready: gray icon, state where normal function calls are not possible
    • Deploying: yellow icon, state where function is being created or changed, triggered by the following actions
      • function creation and modification
      • modify code with editor in the Code tab
      • inspect jar file in the Code tab
      • add and modify in the Trigger tab
      • modify in the Configuration tab
    • Running: blue icon, state where normal function calls are possible and cold start prevention policy is applied
    Service cancellationButton to cancel the service
    Table. Cloud Functions status information and additional features

Detailed Information

Function list page, you can view detailed information of the selected resource and, if necessary, edit the information.

CategoryDetailed description
serviceservice name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
Resource NameResource Name
  • In the Cloud Functions service, it refers to the Function name
Resource IDUnique resource ID of the service
CreatorUser who created the service
Creation timeDate/time the service was created
EditorUser who modified the service
Modification Date and TimeDate and time the service was modified
Function nameName of Cloud Function
RuntimeRuntime types and versions
LLM EndpointClick User Guide to view LLM Endpoint information and usage instructions
Table. Cloud Functions Details - Detailed Information Tab Items
Reference
For detailed information on how to use LLM by integrating AIOS, please refer to Integrate AIOS.

Monitoring

You can view the Cloud Functions usage information of the selected resource on the Function List page.

CategoryDetailed description
Number of callsAverage number of times the function was called during the unit time (instances)
Execution TimeAverage execution time (seconds) of the function during the unit time
Memory usageAverage memory usage (kb) used during the execution of the function per unit time
Current task countIf the function is called multiple times simultaneously, the average number of tasks generated per unit time for concurrent processing (count)
Successful call countAverage number of times (cases) the runtime code operated normally and delivered a response code per unit time when the function is called
Failed call countAverage number of calls with errors per unit time when the function is invoked
  • Including runtime due to response timeouts and logic errors
Table. Cloud Functions Details - Monitoring Tab Items

Log

You can view the Cloud Functions logs of the selected resource on the Function list page.

CategoryDetailed description
Unit periodSelect the period to view Cloud Functions log information
  • Select in time units (1 hour, 3 hours, 12 hours) or set manually
Log MessageDisplayed in order from the most recent occurring function.
Table. Cloud Functions Details - Log Tab Items
Reference
Log messages can be viewed up to the previous 1,000 messages based on the most recent occurrence.

Code

Function list page allows you to view and edit the Cloud Functions code of the selected resource.

Reference

The way to view and edit source code changes depending on the runtime used.

  • Inline Editor: Node.js, Python, PHP, Go
  • Run compressed file (.jar/.zip): Java
CategoryDetailed description
Source CodeInline Editor Mode
Code InformationDisplay code information
EditEdit After clicking the button, you can edit the code in the inline editor
Table. Cloud Functions Details - Inline Editor Items in Code Tab
CategoryDetailed description
Source codeCompressed file (.jar/.zip) execution method
Code InformationCompressed File Information Display
  • Java Runtime: Java Runtime version information
  • Handler Information: Execution Class and Method information
  • Compressed file name (.jar/.zip): Name of the currently set compressed file
  • File upload date and time: Upload date and time of the currently set compressed file
  • Transmission status: Compressed file transmission history
    • Transmission success: When the compressed file setting is successful
    • Reason for failure when compressed file transmission fails
EditJar file can be changed
  • Can be changed by clicking the Get from Object Storage button on the Function code edit page
  • Enter the Private URL of the file in the Object Storage bucket to be fetched
  • For details on changing compressed files, refer to [Java Runtime code change](#java-runtime code change)
Table. Cloud Functions Details - Execution Items of Compressed Files (.jar/.zip) in Code Tab
Reference
  • In the case of Java Runtime, it does not provide UI code editing functionality, and you must select a compressed file (.jar/.zip) from the bucket of the Object Storage service.
  • In case of users whose Object Storage service authentication key has not been generated, Import from Object Storage cannot be executed, so you must generate the authentication key in advance.
  • Cloud Functions service’s Object Storage bucket’s access control must be changed to allow state.

Composition

Function list page allows you to view the Cloud Functions configuration of the selected resource.

CategoryDetailed description
General ConfigurationCloud Function memory and timeout settings
  • Memory: Maximum memory limit per function
  • Timeout: Maximum waiting time for a function call per function. After the timeout, the function goes into a Scale-to-zero state and terminates
  • Function execution: Minimum and maximum number of tasks
  • Click the Edit button to change the General Configuration settings
Environment VariableSet runtime environment variables
  • When using environment variables, you can adjust the function’s behavior without updating the code
  • Edit button to environment variable can be added or edited
Function URLIssue an HTTPS URL address that can access the function
  • Click the Edit button to set activation status, authentication type, and allowed IP
  • When calling the function authenticated with IAM type, the header must include “x-scf-access-key”, “x-scf-secret-key”. In this case, policy and authentication key IP access control are not applied
Private connection configurationCan be used in conjunction with PrivateLink Service
Table. Cloud Functions Details - Configuration Tab Items
Caution
If you disable Access Control, the registered access information will be deleted, making function access control impossible, so it may be exposed to security attacks such as external scanning and hacking.
Reference
  • General Configuration’s memory allocation proportionally determines the number of CPU cores that are automatically assigned.
  • General configuration’s minimum execution count of 1 or more prevents Cold Start, but costs are incurred continuously.

Trigger

Function List page allows you to view and configure trigger information of the selected resource. If you set a trigger, the Function can be automatically executed when an event occurs.

CategoryDetailed description
CronjobUse Cronjob as a trigger
  • Automatically invoke the function according to time or a scheduled interval
  • Click the Edit button to change the frequency and time zone
API GatewayUse API Gateway as a trigger
  • You can view the API Gateway name and detailed information.
Table. Cloud Functions Details - Trigger Tab Items
Caution
If you call the Cronjob trigger before the function timeout, the function will run nestedly, increasing the execution count and duration. Consequently, continuous additional costs can accrue, leading to high expenses, so be careful.
Reference
  • Deploying If in this state, cannot be edited.
  • About trigger settings, please refer to Trigger Setup.

Tag

In the Tag tab, you can view the resource’s tag information, and add, modify, or delete it.

CategoryDetailed description
Tag ListTag List
  • Tag’s Key, Value information can be checked
  • Up to 50 tags can be added per resource
  • When entering tags, search and select from the existing list of created Keys and Values
Table. Cloud Functions Details - Tag Tab Items

Work History

You can check the work history of resources on the Work History page.

CategoryDetailed description
Work History ListResource Change History
  • Work details, work date and time, resource type, resource name, work result, worker information can be checked
  • When you click the corresponding resource in the Work History List, the Work History Details popup opens
Table. Cloud Functions Details - Job History Tab Items

Java Runtime Code Change

If you are using Java Runtime, you cannot modify the code directly, so you need to select and change the compressed file (.jar/.zip) in the bucket of the Object Storage service.

Follow the steps below to change the compressed file.

To cancel the Cloud Functions service, follow the steps below.

  1. Click the All Services > Compute > Cloud Functions menu. Go to the Service Home page of Cloud Functions.
  2. Service Home on the page click the Function menu. Navigate to the Function list page.
  3. Click the resource to change the compressed file within the code on the Function List page. Navigate to the Function Details page.
  4. Click the Edit button on the Code tab of the Function Details page. It moves to the Function Code Edit page.
  5. Import from Object Storage Click the button. Import from Object Storage popup opens.
CategoryDetailed description
Java RuntimeJava Runtime information
Handler InformationHandler Information
  • Execution Class: Automatically entered when setting compressed file (.jar/.zip)
  • Execution Method: Automatically entered when setting compressed file (.jar/.zip)
Compressed file (.jar/.zip)Set the compressed file to modify
  • Compressed file name (.jar/.zip): Displays the name of the compressed file. After setting Get from Object Storage, it is entered automatically
  • Get from Object Storage: Set the Object Storage to retrieve the compressed file (.jar/.zip)
Table. Cloud Functions Details - Function Code Modification Items
  1. Object Storage URL After entering the URL information of the Object Storage from which to retrieve the compressed file, click the Confirm button. A notification popup will open.
    • The URL information can be found in the Folder List tab of the detailed page of the Object Storage to be retrieved, under the File Information > Private URL item.
  2. Click the Confirm button. The name of the imported archive file is displayed in the Function code edit page’s Archive file name (.jar/.zip).
  3. Click the Save button.
Caution
  • In case of a user whose authentication key has not been generated, Import from Object Storage cannot be executed.
  • If the URL does not exist or the compressed file corresponds to the following, it cannot be changed.
    • When using an unsupported extension
    • If there is a harmful file in the compressed file
    • If it exceeds the supported size

Cloud Functions Cancel

To cancel the Cloud Functions service, follow the steps below.

  1. All Services > Compute > Cloud Functions Click the menu. Navigate to the Service Home page of Cloud Functions.
  2. Click the Function menu on the Service Home page. Go to the Function List page.
  3. Function list page, click the resource to be terminated and click the Cancel Service button.
  4. When the termination is completed, check whether the resource has been terminated on the Function List page.

2.6.2.1 - Set Trigger

Set up trigger

Reference
  • By default, all triggers can be added in Cloud Functions.
  • If triggered from a specific product, it must be passed to Cloud Functions.

Cronjob Trigger Setup

To set up a Cronjob trigger, follow these steps.

  1. All Services > Compute > Cloud Functions Click the menu. Navigate to the Service Home page of Cloud Functions.
  2. Click the Function menu on the Service Home page. It moves to the Function List page.
  3. On the Function List page, click the resource to set a trigger. You will be taken to the Function Details page.
  4. After clicking the Trigger tab, click the Add Trigger button. Set it. The Add Trigger popup opens.
  5. Add Trigger In the popup window, select Trigger Type Cronjob. The required information input area appears at the bottom.
    CategoryDetailed description
    Cronjob SettingsSet the trigger’s repeat frequency
    • Can be set in minutes, hours, days, months, and weekdays
    Timezone settingSet the trigger’s reference time zone
    Table. Cronjob Trigger Required Information Items
  6. After entering the required information, click the Confirm button.
  7. When the pop-up window notifying addition opens, click the Confirm button.

API Gateway Trigger Setup

To set up an API Gateway trigger, follow these steps.

  1. All Services > Compute > Cloud Functions Click the menu. Go to the Service Home page of Cloud Functions.
  2. Click the Function menu on the Service Home page. Go to the Function List page.
  3. Function List on the page, click the resource to set the trigger. Function Details go to the page.
  4. After clicking the Trigger tab, click the Add Trigger button. Set it. The Add Trigger popup window opens.
  5. Add Trigger In the popup window, select Trigger Type API Gateway. A required information input area appears at the bottom.
    CategoryDetailed description
    API nameAPI selection
    • You can select an existing API or create a new one
    StageSelect deployment target
    • You can select an existing stage or create a new one
    Table. API Gateway Trigger Required Information Items
  6. After entering the required information, click the Confirm button.
  7. When the popup notifying addition opens, click the Confirm button.

Setting up Multi Trigger

You can connect multiple triggers to a single function and use them.

Edit Trigger

To modify the added trigger, follow the steps below.

  1. All Services > Compute > Cloud Functions Click the menu. Go to the Service Home page of Cloud Functions.
  2. Click the Function menu on the Service Home page. Navigate to the Function List page.
  3. On the Function List page, click the resource to edit the trigger. It moves to the Function Details page.
  4. After clicking the Trigger tab, click the Edit button of the trigger whose settings you want to modify in the trigger list. The Edit Trigger popup window opens.
  5. Trigger Edit After modifying the setting values in the popup window, click the Confirm button.
  1. When the popup notifying the edit opens, click Confirm.

Delete Trigger

To delete the trigger, follow the steps below.

Caution
Triggers linked to a specific product only manage the product delivered at the time of linking in that product, and when Functions are terminated, a deletion status must be delivered to that product.
  1. All Services > Compute > Cloud Functions Click the menu. Navigate to the Service Home page of Cloud Functions.
  2. Click the Function menu on the Service Home page. Navigate to the Function List page.
  3. Function List page, click the resource to set the trigger. Function Details page will be navigated.
  4. In the Trigger tab’s trigger list, after selecting the trigger to delete, click the Delete button.
  5. Click the Confirm button when the popup notifying trigger deletion opens.

2.6.2.2 - AIOS Connect

AIOS Linking

You can use LLM by linking Cloud Functions with AIOS.

AIOS LLM Private Endpoint

The URL of the AIOS LLM private endpoint is as follows.

Reference

Refer to the following for detailed information on the availability and provision model of AIOS services by region.

Blueprint Change Source Code

To integrate Cloud Functions with AIOS, you need to change the URL address in the Blueprint to match the LLM Endpoint used in each region. To change the Blueprint source code, follow the steps below.

  1. All Services > Compute > Cloud Functions Click the menu. Go to the Service Home page of Cloud Functions.
  2. Service Home on the page click the Cloud Functions menu. Navigate to the Function list page.
  3. On the Function List page, click the resource to be called via URL. You will be taken to the Function Detail page.
  4. After clicking the Code tab, click the Edit button. Navigate to the Function Code Edit page.
  5. After modifying the Blueprint using Python, Node.js, Go Runtime source code, click the Save button.
  • Python source code

    Color mode
    import json
    import requests
    
    def handle_request(params):
      # User writing area (Function details)
      url = "{AIOS LLM private endpoint}/{API}" # Destination URL
      data = { "model": "openai/gpt-oss-120b"
        , "prompt" : "Write a haiku about recursion in programming."
        , "temperature": 0
        , "max_tokens": 100
        , "stream": False
      }
      try:
        response = requests.post(url, json=data, verify=True)
    
        return {
          'statusCode': response.status_code,
          'body': json.dumps(response.text)
        }
      except requests.exceptions.RequestException as e:
        return str(e)
    import json
    import requests
    
    def handle_request(params):
      # User writing area (Function details)
      url = "{AIOS LLM private endpoint}/{API}" # Destination URL
      data = { "model": "openai/gpt-oss-120b"
        , "prompt" : "Write a haiku about recursion in programming."
        , "temperature": 0
        , "max_tokens": 100
        , "stream": False
      }
      try:
        response = requests.post(url, json=data, verify=True)
    
        return {
          'statusCode': response.status_code,
          'body': json.dumps(response.text)
        }
      except requests.exceptions.RequestException as e:
        return str(e)
    Python source code

  • Node.js source code

    Color mode
    const request = require('request');
    
    /**
    * @description User writing area (Function details)
    */
    exports.handleRequest = async function (params) {
    return await sendRequest(params);
    };
    
    async function sendRequest(req) {
      return new Promise((resolve, reject) => {
        url = "{AIOS LLM private endpoint}/{API}"
        data = { model: 'openai/gpt-oss-120b'
          , prompt : 'Write a haiku about recursion in programming.'
          , temperature: 0
          , max_tokens: 100
          , stream: false
        }
    
        const options = {
          uri: url,
          method:'POST',
          body: data,
          json: true,
          strictSSL: false,
          rejectUnauthorized: false
        }
        
        request(options, (error, response, body) => {
          if (error) {
            reject(error);
          } else {
            resolve({
              statusCode: response.statusCode,
              body: JSON.stringify(body)
            });
          }
        });
      });
    }
    const request = require('request');
    
    /**
    * @description User writing area (Function details)
    */
    exports.handleRequest = async function (params) {
    return await sendRequest(params);
    };
    
    async function sendRequest(req) {
      return new Promise((resolve, reject) => {
        url = "{AIOS LLM private endpoint}/{API}"
        data = { model: 'openai/gpt-oss-120b'
          , prompt : 'Write a haiku about recursion in programming.'
          , temperature: 0
          , max_tokens: 100
          , stream: false
        }
    
        const options = {
          uri: url,
          method:'POST',
          body: data,
          json: true,
          strictSSL: false,
          rejectUnauthorized: false
        }
        
        request(options, (error, response, body) => {
          if (error) {
            reject(error);
          } else {
            resolve({
              statusCode: response.statusCode,
              body: JSON.stringify(body)
            });
          }
        });
      });
    }
    Node.js Source Code

  • GO source code

    Color mode
    package gofunction
    
    import (
      "bytes"
      "net/http"
      "encoding/json"
      "io/ioutil"
    )
    
    type PostData struct {
      Model string `json:"model"`
      Prompt string `json:"prompt"`
      Temperature int `json:"temperature"`
      MaxTokens int `json:"max_tokens"`
      Stream bool `json:"stream"`
    }
    
    func HandleRequest(r *http.Request)(string, error) {
      url := "{AIOS LLM private endpoint}/{API}"
      data := PostData {
        Model: "openai/gpt-oss-120b",
        Prompt: "Write a haiku about recursion in programming.",
        Temperature: 0,
        MaxTokens: 100,
        Stream: false,
      }
      
    
      jsonData, err := json.Marshal(data)
      if err != nil {
        panic(err)
      }
    
      req, err := http.NewRequest("POST", url, bytes.NewBuffer(jsonData))
      if err != nil {
        panic(err)
      }
    
      req.Header.Set("Content-Type", "application/json")
    
      client := &http.Client{}
      resp, err := client.Do(req)
      if err != nil {
        panic(err)
      }
      defer resp.Body.Close()
    
      // Read response body
      body, err := ioutil.ReadAll(resp.Body)
      if err != nil {
        panic(err)
      }
    
      return string(body), nil
    "}
    package gofunction
    
    import (
      "bytes"
      "net/http"
      "encoding/json"
      "io/ioutil"
    )
    
    type PostData struct {
      Model string `json:"model"`
      Prompt string `json:"prompt"`
      Temperature int `json:"temperature"`
      MaxTokens int `json:"max_tokens"`
      Stream bool `json:"stream"`
    }
    
    func HandleRequest(r *http.Request)(string, error) {
      url := "{AIOS LLM private endpoint}/{API}"
      data := PostData {
        Model: "openai/gpt-oss-120b",
        Prompt: "Write a haiku about recursion in programming.",
        Temperature: 0,
        MaxTokens: 100,
        Stream: false,
      }
      
    
      jsonData, err := json.Marshal(data)
      if err != nil {
        panic(err)
      }
    
      req, err := http.NewRequest("POST", url, bytes.NewBuffer(jsonData))
      if err != nil {
        panic(err)
      }
    
      req.Header.Set("Content-Type", "application/json")
    
      client := &http.Client{}
      resp, err := client.Do(req)
      if err != nil {
        panic(err)
      }
      defer resp.Body.Close()
    
      // Read response body
      body, err := ioutil.ReadAll(resp.Body)
      if err != nil {
        panic(err)
      }
    
      return string(body), nil
    "}
    GO source code

2.6.2.3 - Blueprint Detailed Guide

Blueprint Overview

When creating Cloud Functions, you can set the Blueprint to utilize the Runtime source code provided by Cloud Functions. Refer to the following for Blueprint items provided by Cloud Functions.

CategoryDetailed DescriptionRemarks
Hello WorldWhen the function is called, it responds with Hello Serverless World!
Execution after timeoutOutputs code that should be executed after the function call time has exceeded, but does not execute.PHP, Python not supported
HTTP request bodyParses the request body.PHP not supported
Send HTTP requestsSend HTTP requests from Cloud functions.PHP not supported
Print logsOutputs the user’s Samsung Cloud Platform Console Request to the log.PHP not supported
Throw a custom errorEnter the error logic directly to handle the error.
Using Environment VariableConfigure environment variables within the Cloud function and execute.
Table. Blueprint Items

Hello World

Hello World explains how to set up receiving responses and an example of function call (using function URL).

Hello World Setting

To set Hello World, follow the steps below.

  1. All Services > Compute > Cloud Functions Click the menu. Navigate to the Service Home page of Cloud Functions.

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

  3. Function list page, click the resource to be called via URL. Navigate to the Function detail page.

  4. Click the Configuration tab, then click the Edit button of the Function URL item. The Edit Function URL popup opens.

  5. Edit Function URL in the popup window, after setting Activation Status to Enabled, click the Confirm button.

    CategoryDetailed description
    Activation statusSet whether to use function URL
    Authentication TypeSelect whether to use IAM authentication when requesting the function URL
    Access ControlCan manage by adding accessible IPs
    • After setting to Use, public access IP can be entered and added
    Table. Required input fields when adding a trigger

  6. After moving to the Code tab, click the Edit button. You will be taken to the Function Code Edit page.

  7. After adding the processing logic for success and failure cases, click the Save button.

    • Node.js source code
      Color mode
      exports.handleRequest = async function (params) {
          /**
          * @description User writing area (Function details)
          */
          const response = {
          statusCode: 200,
          body: JSON.stringify('Hello Serverless World!'),
          };"
          return response;
      };
      exports.handleRequest = async function (params) {
          /**
          * @description User writing area (Function details)
          */
          const response = {
          statusCode: 200,
          body: JSON.stringify('Hello Serverless World!'),
          };"
          return response;
      };
      Hello World - Node.js source code
    • Python source code
      Color mode
      import json
      
      def handle_request(params):
          # User writing area (Function details)
          return {
          'statusCode': 200,
          'body': json.dumps('Hello Serverless World!')
          }
      import json
      
      def handle_request(params):
          # User writing area (Function details)
          return {
          'statusCode': 200,
          'body': json.dumps('Hello Serverless World!')
          }
      Hello World - Python source code
    • PHP source code
      Color mode
      <?php
      function handle_request() {
          # User writing area (Function details)
          $res = array(
              'statusCode' => 200,
              'body' => 'Hello Serverless World!',
          );
          return $res;
      }
      ?>
      
      <?php
      function handle_request() {
          # User writing area (Function details)
          $res = array(
              'statusCode' => 200,
              'body' => 'Hello Serverless World!',
          );
          return $res;
      }
      ?>
      
      Hello World - PHP source code

Check function call

After calling the function URL in the Configuration tab of the Function Details page, verify the response.

Hello Serverless World!


# Execution after timeout

Explain the setting for execution after timeout and an example of function call (using function URL).


## Execution after timeout Setting

To set Execution after timeout, follow the steps below.

1. **All Services > Compute > Cloud Functions** Click the menu. Go to the **Service Home** page of Cloud Functions.
2. Click the **Function** menu on the **Service Home** page. Navigate to the **Function List** page.
3. **Function List** page, click the resource to set the trigger. **Function Details** page will be opened.
4. After clicking the **Trigger** tab, click the **Add Trigger** button. The **Add Trigger** popup opens.
5. **Add Trigger** In the popup window, after selecting the **Trigger Type** item, enter the required information displayed at the bottom and click the **Confirm** button.
      * Required information varies depending on the trigger type.





Trigger Type Input Item
API Gateway
  • API name: You can select an existing API or create a new one
  • Stage: You can select an existing stage or create a new one
Cronjob
  • Refer to the example and enter the trigger’s repeat frequency (minute, hour, day, month, day of week)
  • Timezone setting: select the reference time zone to apply
Table. Required input items when adding a trigger
6. **Code** after moving to the tab, click the **Edit** button. You will be taken to the **Function Code Edit** page. 7. After adding the processing logic for success and failure cases, click the **Save** button. * Node.js source code
Color mode
exports.handleRequest = async function (params) {
    /**
     * @description User writing area (Function details)
     */
    console.log("Hello world 3");
    await delay(3000);

    const response = {
        statusCode: 200,
        body: JSON.stringify('Hello Serverless World!'),
    };;
    return response;
};

const delay = (ms) => {
    return new Promise(resolve=>{
        setTimeout(resolve,ms)
    })
}
exports.handleRequest = async function (params) {
    /**
     * @description User writing area (Function details)
     */
    console.log("Hello world 3");
    await delay(3000);

    const response = {
        statusCode: 200,
        body: JSON.stringify('Hello Serverless World!'),
    };;
    return response;
};

const delay = (ms) => {
    return new Promise(resolve=>{
        setTimeout(resolve,ms)
    })
}
Execution after timeout - Node.js source code
## Check function call **Function Details** page's **configuration** tab call the **function URL** and after a certain amount of time, check the response.

Hello Serverless World!


# HTTP request body

Explains the Request Body parsing settings and function call example (using function URL).

## Setting HTTP request body

To set the HTTP request body, follow these steps.

1. Click the **All Services > Compute > Cloud Functions** menu. Go to the **Service Home** page of Cloud Functions.
2. Click the **Function** menu on the **Service Home** page. Navigate to the **Function** list page.
3. **Function List** page, click the resource to set the trigger. **Function Details** page will be opened.
4. After clicking the **Trigger** tab, click the **Add Trigger** button. The **Add Trigger** popup opens.
5. **Add Trigger** in the popup window, after selecting the **Trigger Type** item, enter the required information displayed at the bottom and click the **Confirm** button.
    * Required information varies depending on the trigger type.





Trigger Type Input Item
API Gateway
  • API name: You can select an existing API or create a new one
  • Stage: You can select an existing stage or create a new one
Cronjob
  • Refer to the example and enter the trigger’s repeat frequency (minute, hour, day, month, day of week)
  • Timezone setting: select the time zone to apply
Table. Required input items when adding a trigger
6. After moving to the **Code** tab, click the **Edit** button. You will be taken to the **Function Code Edit** page. 7. After adding processing logic for success and failure cases, click the **Save** button. * Node.js source code
Color mode
exports.handleRequest = async function (params) {
    /**
    * @description User writing area (Function details)
    */
    const response = {
    statusCode: 200,
    body: JSON.stringify(params.body),
    };;
    return response;
};
exports.handleRequest = async function (params) {
    /**
    * @description User writing area (Function details)
    */
    const response = {
    statusCode: 200,
    body: JSON.stringify(params.body),
    };;
    return response;
};
Execution after timeout - Node.js source code
* Python source code
Color mode
import json

def handle_request(params):
    # User writing area (Function details)
    return {
        'statusCode': 200,
        'body': json.dumps(params.json)
}
import json

def handle_request(params):
    # User writing area (Function details)
    return {
        'statusCode': 200,
        'body': json.dumps(params.json)
}
Execution after timeout - Python source code
## Check function call **Function Details** page's **Configuration** tab after calling the **function URL**, check the Body data, request Body value, and response Body value. * request Body value
Color mode
{
    "testKey" :"cloud-001",
    "testNames": ["

        {
            "name": "Son"
        },
        {
            "name": "Kim"
        }
    ],
    "testCode":"test"
}
{
    "testKey" :"cloud-001",
    "testNames": ["

        {
            "name": "Son"
        },
        {
            "name": "Kim"
        }
    ],
    "testCode":"test"
}
Request Body Value
* Response Body value
Color mode
{
    "testKey" :"cloud-001",
    "testNames": [
        {
            "name": "Son"
        },
        {
            "name": "Kim"
        }
    ],
    "testCode":"test"
}
{
    "testKey" :"cloud-001",
    "testNames": [
        {
            "name": "Son"
        },
        {
            "name": "Kim"
        }
    ],
    "testCode":"test"
}
Response Body Value
# Send HTTP requests Explains the HTTP request settings and function call example (using function URL). ## Send HTTP requests Setup To configure Send HTTP requests, follow the steps below. 1. **All Services > Compute > Cloud Functions** Click the menu. Go to the **Service Home** page of Cloud Functions. 2. Click the **Function** menu on the **Service Home** page. Go to the **Function List** page. 3. Click the resource to set the trigger on the **Function List** page. It navigates to the **Function Details** page. 4. After clicking the **Trigger** tab, click the **Add Trigger** button. The **Add Trigger** popup opens. 5. **Add Trigger** In the popup window, after selecting the **Trigger Type** item, enter the required information displayed at the bottom and click the **Confirm** button. * Required information varies depending on the type of trigger.
Trigger TypeInput Item
API Gateway
  • API name: You can select an existing API or create a new one
  • Stage: You can select an existing stage or create a new one
Cronjob
  • Refer to the example and enter the trigger’s repeat frequency (minute, hour, day, month, day of week)
  • Timezone setting: select the reference time zone to apply
Table. Required input items when adding a trigger
6. After moving to the **Code** tab, click the **Edit** button. You will be taken to the **Function Code Edit** page. 7. After adding the processing logic for success and failure cases, click the **Save** button. * Node.js source code
Color mode
const request = require('request');

/**
* @description User writing area (Function details)
*/
exports.handleRequest = async function (params) {
return await sendRequest(params);
};

async function sendRequest(req) {
    return new Promise((resolve, reject) => {
        // Port 80 and Port 443 are available
        url = "https://example.com"; // Destination URL
  
            const options = {
            uri: url,
            method:'GET',
            json: true,
            strictSSL: false,
            rejectUnauthorized: false
        }
        request(options, (error, response, body) => {
            if (error) {
                reject(error);
            } else {
                resolve({
                    statusCode: response.statusCode,
                    body: JSON.stringify(body)
                });
            }
        });
    });
}
const request = require('request');

/**
* @description User writing area (Function details)
*/
exports.handleRequest = async function (params) {
return await sendRequest(params);
};

async function sendRequest(req) {
    return new Promise((resolve, reject) => {
        // Port 80 and Port 443 are available
        url = "https://example.com"; // Destination URL
  
            const options = {
            uri: url,
            method:'GET',
            json: true,
            strictSSL: false,
            rejectUnauthorized: false
        }
        request(options, (error, response, body) => {
            if (error) {
                reject(error);
            } else {
                resolve({
                    statusCode: response.statusCode,
                    body: JSON.stringify(body)
                });
            }
        });
    });
}
Send HTTP requests - Node.js source code
* Python source code
Color mode
import json
import requests

def handle_request(params):
    # User writing area (Function details)
    
    # Port 80 and Port 443 are available
    url = "https://example.com" # Destination URL

    try:
        response = requests.get(url, verify=True)
        return {
            'statusCode': response.status_code,
            'body': json.dumps(response.text)
        }
    except requests.exceptions.RequestException as e:
        return str(e)
import json
import requests

def handle_request(params):
    # User writing area (Function details)
    
    # Port 80 and Port 443 are available
    url = "https://example.com" # Destination URL

    try:
        response = requests.get(url, verify=True)
        return {
            'statusCode': response.status_code,
            'body': json.dumps(response.text)
        }
    except requests.exceptions.RequestException as e:
        return str(e)
Send HTTP requests - Python source code
## Check function call **Function Details** page's **Configuration** tab, after calling the **function URL**, check the response.
Color mode
<!doctype html>
<html>
<head>
    <title>Example Domain</title>

    <meta charset="utf-8" />
    <meta http-equiv="Content-type" content="text/html; charset=utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <style type="text/css">
    body {
        background-color: #f0f0f2;
        margin: 0;
        padding: 0;
        font-family: -apple-system, system-ui, BlinkMacSystemFont, "Segoe UI", "Open Sans", "Helvetica Neue", Helvetica, Arial, sans-serif;
    }
    div {
        width: 600px;
        margin: 5em auto;
        padding: 2em;
        background-color: #fdfdff;
        border-radius: 0.5em;
        box-shadow: 2px 3px 7px 2px rgba(0,0,0,0.02);
    }
    a:link, a:visited {
        color: #38488f;
        text-decoration: none;
    }
    @media (max-width: 700px) {
        div {
            margin: 0 auto;
            width: auto;
        }
    }
    </style>
</head>

<body>
<div>
    <h1>Example Domain</h1>

    <p>This domain is for use in illustrative examples in documents. You may use this
    domain in literature without prior coordination or asking for permission.</p>
    <p><a href="https://www.iana.org/domains/example">More information...</a></p>
</div>
</body>
</html>
<!doctype html>
<html>
<head>
    <title>Example Domain</title>

    <meta charset="utf-8" />
    <meta http-equiv="Content-type" content="text/html; charset=utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <style type="text/css">
    body {
        background-color: #f0f0f2;
        margin: 0;
        padding: 0;
        font-family: -apple-system, system-ui, BlinkMacSystemFont, "Segoe UI", "Open Sans", "Helvetica Neue", Helvetica, Arial, sans-serif;
    }
    div {
        width: 600px;
        margin: 5em auto;
        padding: 2em;
        background-color: #fdfdff;
        border-radius: 0.5em;
        box-shadow: 2px 3px 7px 2px rgba(0,0,0,0.02);
    }
    a:link, a:visited {
        color: #38488f;
        text-decoration: none;
    }
    @media (max-width: 700px) {
        div {
            margin: 0 auto;
            width: auto;
        }
    }
    </style>
</head>

<body>
<div>
    <h1>Example Domain</h1>

    <p>This domain is for use in illustrative examples in documents. You may use this
    domain in literature without prior coordination or asking for permission.</p>
    <p><a href="https://www.iana.org/domains/example">More information...</a></p>
</div>
</body>
</html>
Check function call response
# Print logs Explains the log output settings and function call example (using function URL). ## Print logs Setup Print logs To set up receiving responses, follow the steps below. 1. Click the **All Services > Compute > Cloud Functions** menu. Navigate to the **Service Home** page of Cloud Functions. 2. Click the **Function** menu on the **Service Home** page. Move to the **Function List** page. 3. **Function List** page, click the resource to set the trigger. **Function Details** page will be opened. 4. Click the **Trigger** tab, then click the **Add Trigger** button. The **Add Trigger** popup opens. 5. **Add Trigger** In the popup window, after selecting the **Trigger Type** item, enter the required information displayed at the bottom and click the **Confirm** button. * Required information varies depending on the trigger type.
Trigger TypeInput Item
API Gateway
  • API name: You can select an existing API or create a new one
  • Stage: You can select an existing stage or create a new one
Cronjob
  • Refer to the example and enter the trigger’s repeat frequency (minute, hour, day, month, day of week)
  • Timezone setting: select the reference time zone to apply
Table. Required input items when adding a trigger
6. After moving to the **Code** tab, click the **Edit** button. You will be taken to the **Function Code Edit** page. 7. After adding the processing logic for success and failure cases, click the **Save** button. * Node.js source code
Color mode
const winston = require('winston');

// Log module setting
const logger = winston.createLogger({
    format: winston.format.combine(
        winston.format.timestamp(),
        winston.format.printf(info => info.timestamp + ' ' + info.level + ': ' + info.message)
        ),
        transports: [
            new winston.transports.Console()
            ]
});

exports.handleRequest = async function (params) {
    /**
    * @description User writing area (Function details)
    */
    const response = {
        statusCode: 200,
        body: JSON.stringify(params.body),
    };"

    logger.info(JSON.stringify(response, null, 2));

    return response;
};
const winston = require('winston');

// Log module setting
const logger = winston.createLogger({
    format: winston.format.combine(
        winston.format.timestamp(),
        winston.format.printf(info => info.timestamp + ' ' + info.level + ': ' + info.message)
        ),
        transports: [
            new winston.transports.Console()
            ]
});

exports.handleRequest = async function (params) {
    /**
    * @description User writing area (Function details)
    */
    const response = {
        statusCode: 200,
        body: JSON.stringify(params.body),
    };"

    logger.info(JSON.stringify(response, null, 2));

    return response;
};
Print logs - Node.js source code
* Python source code
Color mode
import json
import logging

# Log module setting
logging.basicConfig(level=logging.INFO)

def handle_request(params):
    # User writing area (Function details)
    response = {
        'statusCode': 200,
        'body': json.dumps(params.json)
    }

    logging.info(response)

    return response
import json
import logging

# Log module setting
logging.basicConfig(level=logging.INFO)

def handle_request(params):
    # User writing area (Function details)
    response = {
        'statusCode': 200,
        'body': json.dumps(params.json)
    }

    logging.info(response)

    return response
Print logs - Python source code
## Check function call **Function Details** page's **Configuration** tab after calling the **function URL**, check the log in the **Log** tab.
Color mode
[2023-09-07] 12:06:23] "host": "scf-xxxxxxxxxxxxxxxxxxxxx",
[2023-09-07] 12:06:23] "ce-id": "xxxxxxxxxxxxxxxxxxxxx",
[2023-09-07] 12:06:23] "ce-source": "xxxxxxxxxxxxxxxxxxxxx",
[2023-09-07] 12:06:23] "host": "scf-xxxxxxxxxxxxxxxxxxxxx",
[2023-09-07] 12:06:23] "ce-id": "xxxxxxxxxxxxxxxxxxxxx",
[2023-09-07] 12:06:23] "ce-source": "xxxxxxxxxxxxxxxxxxxxx",
Check function call response
# Throw a custom error Custom error occurrence (Throw a custom error) setting and function call example (function URL usage) is explained. ## Throw a custom error Setting To set Throw a custom error, follow the steps below. 1. **All Services > Compute > Cloud Functions** Click the menu. Go to the **Service Home** page of Cloud Functions. 2. Click the **Function** menu on the **Service Home** page. Move to the **Function List** page. 3. **Function List** page, click the resource to set the trigger. **Function Details** page will be navigated. 4. **Trigger** tab after clicking, click the **Add Trigger** button. The **Add Trigger** popup window opens. 5. **Add Trigger** In the popup window, after selecting the **Trigger Type** item, enter the required information displayed at the bottom and click the **Confirm** button. * Required information varies depending on the trigger type.
Trigger TypeInput Item
API Gateway
  • API name: You can select an existing API or create a new one
  • Stage: You can select an existing stage or create a new one
Cronjob
  • Refer to the example and enter the trigger’s repeat frequency (minute, hour, day, month, day of week)
  • Timezone setting: select the time zone to apply
Table. Required input items when adding a trigger
6. After moving to the **Code** tab, click the **Edit** button. You will be taken to the **Function Code Edit** page. 7. After adding the processing logic for success and failure cases, click the **Save** button. * Node.js source code
Color mode
class CustomError extends Error {
    constructor(message) {
        super(message);
        this.name = 'CustomError';
    }
}

exports.handleRequest = async function (params) {
    /**
    * @description User writing area (Function details)
    */
    throw new CustomError('This is a custom error!');
};
class CustomError extends Error {
    constructor(message) {
        super(message);
        this.name = 'CustomError';
    }
}

exports.handleRequest = async function (params) {
    /**
    * @description User writing area (Function details)
    */
    throw new CustomError('This is a custom error!');
};
Throw a custom error - Node.js source code
* Python source code
Color mode
class CustomError(Exception):
    def __init__(self, message):
    self.message = message

def handle_request(parmas):
    raise CustomError('This is a custom error!')
class CustomError(Exception):
    def __init__(self, message):
    self.message = message

def handle_request(parmas):
    raise CustomError('This is a custom error!')
Throw a custom error - Python source code
* PHP source code
Color mode
<?php
    class CustomError extends Exception {
        public function __construct($message) {
            parent::__construct($message);
            $this->message = $message;
        }
    }

    function handle_request() {
        throw new CustomError('This is a custom error!');
    }
?>
<?php
    class CustomError extends Exception {
        public function __construct($message) {
            parent::__construct($message);
            $this->message = $message;
        }
    }

    function handle_request() {
        throw new CustomError('This is a custom error!');
    }
?>
Throw a custom error - PHP source code
## Check function call **Function Details** page's **Configuration** tab after calling the **function URL**, check for errors in the **Log** tab. # Using Environment Variable Using Environment Variable (Using Environment Variable) configuration and function call example (using function URL) is explained. ## Using Environment Variable Setup To set Using Environment Variable, follow the steps below. 1. **All Services > Compute > Cloud Functions** Click the menu. Go to the **Service Home** page of Cloud Functions. 2. Click the **Function** menu on the **Service Home** page. Navigate to the **Function List** page. 3. **Function List** Click the resource to set the trigger on the page. **Function Details** Navigate to the page. 4. After clicking the **Trigger** tab, click the **Add Trigger** button. The **Add Trigger** popup opens. 5. **Add Trigger** In the popup window, after selecting the **Trigger Type** item, enter the required information displayed at the bottom and click the **Confirm** button. * Required information varies depending on the type of trigger.
Trigger TypeInput Item
API Gateway
  • API name: You can select an existing API or create a new one
  • Stage: You can select an existing stage or create a new one
Cronjob
  • Refer to the example and enter the trigger’s repeat frequency (minute, hour, day, month, day of week)
  • Timezone setting: select the reference time zone to apply
Table. Required input items when adding a trigger
6. After moving to the **Code** tab, click the **Edit** button. You will be taken to the **Function Code Edit** page. 7. After adding the processing logic for success and failure cases, click the **Save** button. * Node.js source code
Color mode
exports.handleRequest = async function (params) {
    /**
    * @description User writing area (Function details)
    */
    return process.env.test;
};
exports.handleRequest = async function (params) {
    /**
    * @description User writing area (Function details)
    */
    return process.env.test;
};
Using Environment Variable - Node.js source code
* Python source code
Color mode
import json

import os

def handle_request(params):
    # User writing area (Function details)
    return os.environ.get("test")
import json

import os

def handle_request(params):
    # User writing area (Function details)
    return os.environ.get("test")
Using Environment Variable - Python source code
* PHP source code
Color mode
import json

def handle_request(params):
    # User writing area (Function details)
    return os.environ.get("test")
import json

def handle_request(params):
    # User writing area (Function details)
    return os.environ.get("test")
Using Environment Variable - PHP source code
9. After moving to the **Configuration** tab, click the **Edit** button in the **Environment Variable** area. The **Edit Environment Variable** popup window opens. 10. After entering the environment variable information, click the **Confirm** button.
CategoryDetailed description
NameEnter Key value
valueValueEnter value
Table. Environment Variable Input Items
## Check function call **Function Details** page's **Configuration** tab, after calling the **Function URL**, check the environment variable values in the **Log** tab.

2.6.2.4 - PrivateLink Service Integration

By linking Cloud Functions and PrivateLink services, you can connect VPCs within the Samsung Cloud Platform and VPCs to services without external internet.
The data uses only the internal network, which enhances security, and does not require a public IP, NAT, VPN, internet gateway, etc.

PrivateLink Service Integration

You can expose the function via PrivateLink Service so that it can be accessed privately from another VPC.

To integrate the PrivateLink service, follow the steps below.

  1. All Services > Compute > Cloud Functions Click the menu. Navigate to the Service Home page of Cloud Functions.
  2. Click the Cloud Functions menu on the Service Home page. You will be taken to the Function list page.
  3. Click the resource to associate PrivateLink on the Function List page. It moves to the Function Details page.
  4. Click the Configuration tab on the Function Details page.
  5. Click the Edit button of PrivateLink Service in Private connection configuration. Edit PrivateLink Service popup window opens.
  6. PrivateLink Service Edit in the popup window, after checking the Use item of Activation Status, click the Confirm button. In the Configuration tab’s Private Connection Configuration, the PrivateLink Service information is displayed.
CategoryDetailed description
Private URLPrivateLink Service URL information
PrivateLink Service IDPrivateLink Service ID information
Request Endpoint ManagementList of PrivateLink Endpoints that requested connection to PrivateLink Service
  • Endpoint ID and approval status
  • Approval Management Click the button to change status
    • Requesting: Endpoint that is requesting connection. Click Approve or Reject button to select approval
    • Active: Endpoint with completed connection. Click Block button to disconnect
    • Disconnected: Endpoint whose connection has been terminated. Click Reconnect button to connect
    • Reject: Endpoint whose connection request was denied
Table. PrivateLink Service Detailed Information Items

PrivateLink Endpoint Create

Create an entry point to access the user’s VPC PrivateLink Service.

Caution
Additional costs may be incurred when creating an endpoint.

To create a PrivateLink Endpoint, follow these steps.

  1. All Services > Compute > Cloud Functions Click the menu. Go to the Service Home page of Cloud Functions.
  2. On the Service Home page, click the Cloud Functions menu. It navigates to the Function list page.
  3. Click the resource to associate with PrivateLink on the Function List page. You will be taken to the Function Details page.
  4. Click the Configuration tab on the Function Details page.
  5. Click the Add button of PrivateLink Endpoint in Configure Private Connection. Add PrivateLink Endpoint popup opens.
  6. PrivateLink Service Add in the popup window, after entering PrivateLink Service ID and Alias information, click the Confirm button.
  7. When the popup notifying creation opens, click the Confirm button. In the Configuration tab’s Private connection configuration, the PrivateLink Endpoint information is displayed.
CategoryDetailed description
PrivateLink Endpoint IDPrivateLink Endpoint ID information
PrivateLink Service IDPrivateLink Service ID information
AliasAlias information
StatusApproval status of PrivateLink Endpoint
  • Requesting: Pending approval
  • Active: Approved and connected
  • Disconnected: Disconnected
  • Reject: Approval denied. Click the Re-request button to request again
  • Delete: Delete the endpoint
Table. PrivateLink Endpoint detailed information items

2.6.2.5 - 리소스 기반 정책 가이드

Overview of Resource-Based Policies

A resource-based policy for Cloud Functions is a policy attached to a resource that can allow or deny (Effect) specific actions (Action) for a given principal (Principal). You can directly define the principal that can execute (Invoke) a function using resource-based policies.

참고
While a typical IAM policy (Identity-based) grants permissions to a user, a resource-based policy is applied to the function itself to allow external access.

You can allow function calls by defining the following in a resource-based policy.

  • User of the specified Samsung Cloud Platform account
  • Specified source IP address range or CIDR block

Source policies are defined as JSON policy documents attached to an API, which control whether a specified security principal (typically an IAM role or group) can call the API.

CategoryExplanationExample
PrincipalSpecify the function callerspecific object storage bucket, API Gateway, other Samsung Cloud Platform accounts, etc.
Task (Action)Define the allowed functionalityMostly scf:InvokeFunction
Condition (Condition)Restrict to allow only in specific situationsAllow only requests from a bucket with a specific SRN.
표. API 호출 여부를 제어하는 Entity
참고
  • Cloud Functions’ resource-based policies leverage the rules of IAM’s resource-based policies.
  • Refer to the JSON Mode Usage Guide for how to create or modify policies using JSON.

Resource-based policy usage scenario

The primary use cases for resource-based policies are as follows.

Resource-based policy scenario

The resource-based policy scenarios used when a Cloud Functions function runs are as follows.

CategoryExplanationReference example
Function URL - Authentication Type NoneIt is required when generating a URL for a function and invoking it.
  • If there is no resource-based policy, authorization fails, making it impossible to invoke the function using a Public URL.
Function URL (Auth Type None) Example
Function URL - Authentication Type IAM
  • Must be registered with a resource-based policy or have credential permissions.
  • For resources in the same account: you can invoke if you have a resource-based policy or credential permission (InvokeFunctionUrl).
  • For resources in a different account: you must have both a resource-based policy and credential permission (InvokeFunction) to invoke.
Function URL (Authentication Type IAM) Example
API Gateway triggerIt is required when API Gateway calls Lambda to handle external API requests.
  • A resource-based policy must be registered.
  • Without a resource-based policy, authorization fails, making it impossible to invoke the function via API Gateway.
API Gateway Trigger Example
PrivateLink connectionYou can define a PrivateLink Service connection to allow private access to a function from another VPC.
  • It must be registered with a resource-based policy or have credential permissions.
  • If the resource is in the same account: you can invoke it if you have a resource-based policy or credential permission (InvokeFunction).
  • If the resource belongs to a different account: you must have both a resource-based policy and credential permission (InvokeFunction) to invoke it.
PrivateLink connection example
표. 리소스 기반 정책 시나리오

Additional user usage scenarios

Although it is not automatically registered as a resource‑based policy for Cloud Functions, users can add and use it as needed. The scenarios that users can add and utilize are as follows.

  • Cross-Account Access
    • When an IAM user in account A wants to invoke a Lambda function in account B, add account A to the function policy of account B.
  • Hybrid Access Control
    • You can configure it so that access is allowed only when both conditions are met—a specific user and a specific IP range—rather than restricting just the account or IP alone.

Resource-based policy management for Cloud Functions

To view and configure resource-based policies for Cloud Functions, follow these steps.

  1. Click the All Services > Compute > Cloud Functions menu. 1. Navigate to the Service Home page of Cloud Functions.
  2. On the Service Home page, click the Function menu. 2. Navigate to the Function list page.
  3. On the Function List page, click the resource for which you want to set a policy. 3. Go to the Function Details page.
  4. Click the Configuration tab on the Function Details page.
  5. Click the Edit button for the Resource-based policy permissions item. 5. Resource Policy edit popup window opens.
  6. In the Resource Policy edit popup, select a Policy Template and then write the policy.
  7. When you have finished writing, click the Confirm button.
    • When you click the Delete button, the registered policy is deleted.

Resource-based policy example

Users can define additional resource-based policies as needed or modify existing policies for use.

참고
  • For some features, a resource‑based policy (or credential) must be registered to use them in Cloud Functions.
  • In the resource-based policy example described in this guide, Cloud Functions automatically registers the example resource-based policy when each feature is enabled or linked.

Function URL - Authentication Type None

A policy that permits public calls when the Principal is /*.

Policy Template

Color mode
    "Statement": [
        
        	"Action": ["scf:InvokeFunctionUrl"],
        	"Condition": {
            	"StringEquals": {
                	"scf:CloudFunctionAuthType": ["NONE"]
            	}
        	},
        	"Effect": "Allow",
        	"Principal": "*"
            "Resource": ["{{CloudFunctionSrn}}"],
            "Sid": "InvokeFunctionURLAllowPublicAccess"
        }
    ],
    "Version": "2024-07-01"
}
    "Statement": [
        
        	"Action": ["scf:InvokeFunctionUrl"],
        	"Condition": {
            	"StringEquals": {
                	"scf:CloudFunctionAuthType": ["NONE"]
            	}
        	},
        	"Effect": "Allow",
        	"Principal": "*"
            "Resource": ["{{CloudFunctionSrn}}"],
            "Sid": "InvokeFunctionURLAllowPublicAccess"
        }
    ],
    "Version": "2024-07-01"
}
함수 URL - 인증타입 None 정책 템플릿 예시

Policy example

Color mode
    "Statement": [
        
            "Action": ["scf:InvokeFunctionUrl"],
            "Condition": {
                "StringEquals": {
                    "scf:CloudFunctionAuthType": ["NONE"]
                }
            },
            "Effect": "Allow",
            "Principal": "*"
            "Resource": ["srn:e::accountID:kr-west1::scf:cloud-function/functionsID"],
            "Sid": "InvokeFunctionURLAllowPublicAccess"
        }
    ],
    "Version": "2024-07-01"
}
    "Statement": [
        
            "Action": ["scf:InvokeFunctionUrl"],
            "Condition": {
                "StringEquals": {
                    "scf:CloudFunctionAuthType": ["NONE"]
                }
            },
            "Effect": "Allow",
            "Principal": "*"
            "Resource": ["srn:e::accountID:kr-west1::scf:cloud-function/functionsID"],
            "Sid": "InvokeFunctionURLAllowPublicAccess"
        }
    ],
    "Version": "2024-07-01"
}
함수 URL - 인증타입 None 정책 예시

Function URL - Authentication Type IAM

This is a policy that permits specific users to invoke the public URL.

Policy Template

Color mode
    "Statement": [
        
            "Action": ["scf:InvokeFunctionUrl"],
            "Condition": {
                "StringEquals": {
                    "scf:CloudFunctionAuthType": ["SCP_IAM"]
                }
            },
            "Effect": "Allow"
            "Principal": {
                "scp": ["srn:{{Environment}}::{{AccountID}}:::iam:user/{{UserId}}"]
            },
            "Resource": ["{{CloudFunctionSrn}}"],
            "Sid": "Statement1"
        }
    ],
    "Version": "2024-07-01"
}
    "Statement": [
        
            "Action": ["scf:InvokeFunctionUrl"],
            "Condition": {
                "StringEquals": {
                    "scf:CloudFunctionAuthType": ["SCP_IAM"]
                }
            },
            "Effect": "Allow"
            "Principal": {
                "scp": ["srn:{{Environment}}::{{AccountID}}:::iam:user/{{UserId}}"]
            },
            "Resource": ["{{CloudFunctionSrn}}"],
            "Sid": "Statement1"
        }
    ],
    "Version": "2024-07-01"
}
함수 URL - 인증타입 IAM 정책 템플릿 예시

Policy example

Color mode
    "Statement": [
        
            "Action": ["scf:InvokeFunctionUrl"],
            "Condition": {
                "StringEquals": {
                    "scf:CloudFunctionAuthType": ["SCP_IAM"]
                }
            },
            "Effect": "Allow"
            "Principal": "*"
            "Resource":  ["srn:e::accountID:kr-west1::scf:cloud-function/functionsID"],
            "Sid": "accountID-iam-invokefunctionurl"
        }
    ],
    "Version": "2024-07-01"
}
    "Statement": [
        
            "Action": ["scf:InvokeFunctionUrl"],
            "Condition": {
                "StringEquals": {
                    "scf:CloudFunctionAuthType": ["SCP_IAM"]
                }
            },
            "Effect": "Allow"
            "Principal": "*"
            "Resource":  ["srn:e::accountID:kr-west1::scf:cloud-function/functionsID"],
            "Sid": "accountID-iam-invokefunctionurl"
        }
    ],
    "Version": "2024-07-01"
}
함수 URL - 인증타입 IAM 정책 예시

API Gateway trigger

A policy that allows public calls with Principal set to *.

Policy Template

Color mode
    "Statement": [
        
            "Action": ["scf:InvokeFunction"],
            "Condition": {
                "SrnLike": {
                    "scp:RequestAttribute/body['x-scf-request-obj-srn']": ["{{ApiGatewayMethodSrn}}"]
                }
            },
            "Effect": "Allow",
            "Principal": {
                "Service": ["apigateway.samsungsdscloud.com"]
            },
            "Resource": ["{{CloudFunctionSrn}}"],
            "Sid": "Statement1"
        }
    ],
    "Version": "2024-07-01"
}
    "Statement": [
        
            "Action": ["scf:InvokeFunction"],
            "Condition": {
                "SrnLike": {
                    "scp:RequestAttribute/body['x-scf-request-obj-srn']": ["{{ApiGatewayMethodSrn}}"]
                }
            },
            "Effect": "Allow",
            "Principal": {
                "Service": ["apigateway.samsungsdscloud.com"]
            },
            "Resource": ["{{CloudFunctionSrn}}"],
            "Sid": "Statement1"
        }
    ],
    "Version": "2024-07-01"
}
API Gateway 트리거 정책 템플릿 예시

Policy example

Color mode
{
    "Statement": [
        
            "Action": [
                scf:InvokeFunction
            ],
            "Condition": {
                "SrnLike": {
                    "scp:RequestAttribute/body['x-scf-request-obj-srn']": [
                        srn:e::accountID:kr-west1::apigateway:method/MethodID/*/GET/test
                    ]
                }
            },
            "Effect": "Allow"
            "Principal": {
                "Service": [
                    apigateway.samsungsdscloud.com
                ]
            },
            "Resource": [
                srn:e::accountID:kr-west1::scf:cloud-function/functionID
            ],
            "Sid": "999e9a9999de4d4683c9e10c74ee999z"
        }
    ],
    "Version": "2024-07-01"
}
{
    "Statement": [
        
            "Action": [
                scf:InvokeFunction
            ],
            "Condition": {
                "SrnLike": {
                    "scp:RequestAttribute/body['x-scf-request-obj-srn']": [
                        srn:e::accountID:kr-west1::apigateway:method/MethodID/*/GET/test
                    ]
                }
            },
            "Effect": "Allow"
            "Principal": {
                "Service": [
                    apigateway.samsungsdscloud.com
                ]
            },
            "Resource": [
                srn:e::accountID:kr-west1::scf:cloud-function/functionID
            ],
            "Sid": "999e9a9999de4d4683c9e10c74ee999z"
        }
    ],
    "Version": "2024-07-01"
}
API Gateway 트리거 정책 예시

This is a policy that permits function calls via a Privatelink Endpoint for specific users.

Policy Template

Color mode
    "Statement": [
        
            "Action": ["scf:InvokeFunction"],
            "Condition": {
                "StringEquals": {
           			"scf:CloudFunctionPrivatelinkServiceAuthType": ["SCP_IAM"]
                }
            },
            "Effect": "Allow",
            "Principal": {
                "scp": ["srn:{{Environment}}::{{AccountID}}:::iam:user/{{UserId}}"]
            },
            "Resource": ["{{CloudFunctionSrn}}"],
            "Sid": "Statement1"
        }
    ],
    "Version": "2024-07-01"
}
    "Statement": [
        
            "Action": ["scf:InvokeFunction"],
            "Condition": {
                "StringEquals": {
           			"scf:CloudFunctionPrivatelinkServiceAuthType": ["SCP_IAM"]
                }
            },
            "Effect": "Allow",
            "Principal": {
                "scp": ["srn:{{Environment}}::{{AccountID}}:::iam:user/{{UserId}}"]
            },
            "Resource": ["{{CloudFunctionSrn}}"],
            "Sid": "Statement1"
        }
    ],
    "Version": "2024-07-01"
}
PrivateLink 연결 정책 템플릿 예시

Policy example

Color mode
    "Statement": [
        
            "Action": [
                scf:InvokeFunction
            ],
            "Condition": {
                "StringEquals": {
                    "scf:CloudFunctionAuthType": [
                        SCP_IAM
                    ]
                }
            },
            "Effect": "Allow"
            "Principal": {
                "scp": [
                    srn:e::accountID:::iam:user/userID
                ]
            },
            "Resource": [
                srn:e::accountID:kr-west1::scf:cloud-function/functionID
            ],
            "Sid": "rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr-privatelink-invokefunction"
        }
    ],
    "Version": "2024-07-01"
}
    "Statement": [
        
            "Action": [
                scf:InvokeFunction
            ],
            "Condition": {
                "StringEquals": {
                    "scf:CloudFunctionAuthType": [
                        SCP_IAM
                    ]
                }
            },
            "Effect": "Allow"
            "Principal": {
                "scp": [
                    srn:e::accountID:::iam:user/userID
                ]
            },
            "Resource": [
                srn:e::accountID:kr-west1::scf:cloud-function/functionID
            ],
            "Sid": "rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr-privatelink-invokefunction"
        }
    ],
    "Version": "2024-07-01"
}
PrivateLink 연결 정책 예시

2.6.3 - Release Note

Cloud Functions

2025.12.16
FEATURE AIOS, PrivateLink service integration
  • You can use functions in conjunction with the AIOS service.
    • Cloud Functions can be linked with AIOS to utilize LLM.
  • You can use functions in conjunction with the PrivateLink service.
    • Through Private connection (PrivateLink), you can internally connect Samsung Cloud Platform’s VPC to VPC, and VPC to services without going through the Internet.
2025.10.23
FEATURE Java Runtime executable file upload feature added
  • The feature to upload Java Runtime executable files has been added.
    • You can fetch and configure a Java Runtime executable archive file (.jar/.zip) to Object Storage.
2025.07.01
NEW Cloud Functions Service Official Version Release
  • Cloud Functions service has been officially launched.
    • It is a serverless computing-based FaaS (Function as a Service) that easily runs function-style applications without the need for server provisioning.

2.7 - Virtual Server DR

In the event of a system disruption due to various disasters and risk factors, the Block Storage connected to the Virtual Server in another region can be replicated to restore normal operating conditions in a short period of time.

2.7.1 - Overview

Service Overview

Virtual Server DR is a service that can quickly recover the system by replicating Virtual Server and connected Block Storage in a different region from the currently used region. Even in the event of various disasters and unexpected situations that interrupt the system, Virtual Server DR can be used to quickly recover to a normal operating state.

Notice
  • Virtual Server DR service can be configured through a partner solution sold in the Samsung Cloud Platform’s Marketplace.
  • For more information about using Marketplace, please refer to Marketplace.
Caution
  • When purchasing and using services sold on the Marketplace, a separate contract with the Marketplace software supplier is issued in accordance with a separate tax invoice.
  • If you have applied for a partner solution product for Virtual Server DR on the Marketplace, the application information will be sent to the person in charge by email. Please coordinate the product details and schedule with the person in charge. The software installation and cost will be charged based on the confirmed date.
  • Services sold in the Samsung Cloud Platform’s Marketplace are services sold by individual sellers, and SamsungSDS is an intermediary of electronic commerce and is not a party to the electronic commerce. Therefore, SamsungSDS does not guarantee or take responsibility for the service information and transactions sold by individual sellers.

Features

  • Easy DR Environment Configuration: You can easily configure a Virtual Server for DR configuration through partner solutions in Samsung Cloud Platform’s Marketplace.
  • Various Environment Configuration: Using partner solutions, you can configure various environments such as physical to virtual environment (P2V), virtual to virtual environment (V2V), and support multiple operating systems (Windows, Linux).

Service Composition Diagram

Configuration Diagram
Figure. Virtual Server DR Configuration Diagram

Provided Features

The main feature is to refer to the product catalog details page of the partner solution being sold in the Samsung Cloud Platform’s Marketplace.

Note
For more information on using the Marketplace, please refer to Marketplace.

Preceding Service

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

Service CategoryServiceDetailed Description
NetworkingVPCA service that provides an independent virtual network in a cloud environment
NetworkingSecurity GroupA virtual firewall that controls the server’s traffic
ComputeVirtual ServerCloud computing-optimized virtual server
Fig. Virtual Server DR Pre-service

2.7.2 - Release Note

Virtual Server DR

2025.07.01
NEW Official Launch of Virtual Server DR Service
  • Virtual Server DR service has been officially released.
  • The system can be restored to normal operating conditions in a short period of time when it is interrupted by various disasters and risk factors.

2.8 - Block Storage

2.8.1 - Overview

Service Overview

Block Storage is a high-performance storage that stores data in block units arranged in a certain size and array.
It is suitable for large-capacity, high-performance requirements such as databases and mail servers, and users can directly assign volumes to servers for use.

Key Features

  • Large-capacity Volume Provision: Volumes for OS configuration are created with at least the minimum capacity per image and can be expanded up to 12TB, and volumes for data storage other than OS can be created and expanded with capacities from a minimum of 8GB to a maximum of 12TB. Capacity expansion is performed stably in an online state.
  • High Performance Based on Full SSD: Provides high durability and availability based on redundant Controllers and Disk Array Raid. Since Full SSD disks are provided by default, it is suitable for high-speed data processing tasks such as database workloads.
  • Snapshot Backup: Recovery of changed and deleted data is possible through the image snapshot function. Users can select a snapshot created at the desired time point from the list to perform recovery.

Service Architecture

Architecture
Figure. Block Storage Architecture

Provided Features

Block Storage provides the following features:

  • Volume Name: Users can set or modify names for each volume.
  • Capacity: Volumes can be created with capacities from a minimum of 8GB to a maximum of 12TB, and can be expanded during use. OS basic volumes can be created with at least the minimum capacity per image.
  • Connected Server: You can connect or disconnect by selecting a Virtual Server.
    • Multi Attach: Connects to 2 or more servers, no limit on the number of connected servers per volume, and Virtual Server can connect up to 26 volumes
  • Encryption: AES-256 algorithm encryption is applied by default to all volumes of Block Storage, and when the volume is HDD/SSD_KMS disk type, it additionally provides transfer encryption between the instance and the Block Storage section connected to the instance.
  • Snapshot: Recovery of changed and deleted data is possible through the image snapshot function. Users select a snapshot created at the desired time point from the list to recover.
  • Volume Transfer: You can transfer volumes to another Account through the volume transfer function.
  • Monitoring: You can check monitoring information such as IOPS, Latency, Throughput, etc. through the Cloud Monitoring service.

Components

You can create a volume by entering capacity according to your service scale and performance requirements and selecting a disk type. When using the snapshot function, you can recover data to the desired time point.

Volume

Volume is the basic creation unit of the Block Storage service and is used as data storage space. Users create a volume by selecting a name, capacity, and disk type, then connect it to a Virtual Server for use.
The volume name creation rules are as follows:

Note
Enter within 255 characters using English letters, numbers, spaces, and special characters (-, _).

Snapshot

Snapshot is an image backup of a volume at a specific point in time. Users can check the snapshot name and creation date/time from the snapshot list and select the snapshot they want to recover, and can recover changed or deleted data through that snapshot.
Notes for using snapshots are as follows:

Note
  • Snapshot creation date/time is based on Asia/Seoul(GMT +09:00).
  • You can recover a Block Storage volume to the latest snapshot by selecting the snapshot recovery button.
  • When selecting a specific snapshot from the snapshot list, you can recover by creating a new snapshot-based volume.
  • Snapshots are charged according to the size of the original Block Storage, so please delete unnecessary snapshots.

Prerequisite Services

This is a list of services that must be pre-configured before creating this service. Please prepare in advance by referring to the guides provided for each service.

Service CategoryServiceDescription
ComputeVirtual ServerVirtual server optimized for cloud computing
Table. Block Storage prerequisite services

2.8.1.1 - Monitoring Metrics

Block Storage monitoring metrics

The table below shows the monitoring metrics of Block Storage that can be checked through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.

Performance Item NameDescriptionUnit
Volume TotalTotal Bytesbytes
IOPS [Read]iops(reading)iops
IOPS [Write]iops(writing)iops
Latency Time [Read]Delay Time (Read)usec
Latency Time [write]Delay Time (write)usec
Throughput [Read]Throughput (Read)bytes/s
Throughput [Write]Throughput (Write)bytes/s
Table. Block Storage monitoring metrics

2.8.2 - How-to guides

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

Creating Block Storage

You can create and use the Block Storage service through the Samsung Cloud Platform Console.

To create Block Storage, follow these steps:

  1. Click the All Services > Compute > Virtual Server menu. This will take you to the Virtual Server Service Home page.

  2. Click the Block Storage menu. This will take you to the Block Storage List page.

  3. Click the Create Service button on the Block Storage page. This will take you to the Create Block Storage page.

  4. Enter the required information for creating the service on the Create Block Storage page and select detailed options.

    Item
    Required
    Description
    Volume NameRequiredVolume name
    • Enter 255 characters using English letters, numbers, spaces, and special characters (-, _)
    SnapshotOptionalSelect snapshot to use when creating volume through snapshot
    • After checking the Use item, you can select a snapshot
    • When creating service through snapshot recovery volume, provides recovery snapshot name
    • If not selected, an empty volume is created
    Disk TypeRequiredSelect disk type
    • SSD_Provisioned: SSD volume where IOPS and Throughput can be set
    • SSD/HDD: General SSD/HDD volume
    • SSD/HDD_KMS: Additional encryption volume
    • SSD/HDD_MultiAttach: Volume that can be connected to 2 or more servers
    • Cannot modify after service creation
    • When creating service through snapshot recovery volume, it is set the same as the original and cannot be modified
    CapacityOptionalSet capacity
    • Can create within 8~12,228GB
    • Enter number of Units provided in 8GB increments
    • When creating service through snapshot recovery volume, enter capacity equal to or larger than the original
    Max IOPSRequiredEnter maximum IOPS value between 5,000~20,000
    • Can only set when Disk Type is SSD_Provisioned
    Max ThroughputRequiredEnter maximum Throughput value between 250~1,000
    • Can only set when Disk Type is SSD_Provisioned
    Table. Block Storage service information input items

  5. Review the detailed information and estimated charges in the Summary panel, then click the Create button.

    • Once creation is complete, verify the created resource on the Block Storage List page.
Note
  • AES-256 algorithm encryption is applied by default to all volumes of Block Storage.
  • Windows-based Virtual Server cannot use MultiAttach disks. Please use a separate replication method or solution.
  • When the volume is HDD/SSD_KMS disk type, it additionally provides transfer encryption between the instance and the Block Storage section connected to the instance.
Warning
When using HDD/SSD_KMS disk type, approximately 60% performance degradation may occur.

Viewing Block Storage Details

Block Storage service allows you to view and modify the complete resource list and detailed information. The Block Storage Details page consists of Details, Snapshot List, Tags, and Operation History tabs.

To view detailed information of Block Storage service, follow these steps:

  1. Click the All Services > Compute > Virtual Server menu. This will take you to the Virtual Server Service Home page.
  2. Click the Block Storage menu. This will take you to the Block Storage List page.
  3. Click the resource for which you want to view detailed information on the Block Storage List page. This will take you to the Block Storage Details page.
    • The Block Storage Details page displays status information and additional feature information, and consists of Details, Snapshot List, Tags, and Operation History tabs.
      ItemDescription
      Volume StatusStatus of the volume
      • Creating: Being created
      • Downloading: Being created (OS image being applied)
      • Available: Creation complete, can connect to server
      • Reserved: Waiting for server connection
      • Attaching: Connecting to server
      • Detaching: Disconnecting from server
      • In Use: Server connection complete
      • Deleting: Service being terminated
      • Awaiting Transfer: Waiting for volume transfer
      • Extending: Capacity expansion
      • Error Extending: Abnormal state during capacity expansion
      • Backing Up: Volume being backed up
      • Restoring Backup: Volume backup being recovered
      • Error Backing Up: Volume backup abnormal state
      • Error Restoring: Volume backup recovery abnormal state
      • Error Deleting: Abnormal state during deletion
      • Error Managing: Abnormal state
      • Error: Abnormal state
      • Maintenance: Temporary maintenance state
      • Reverting: Recovering from snapshot
      Volume TransferTransfer volume to another Account
      Create SnapshotImmediately create a snapshot at the creation point
      Snapshot RecoveryRecover volume to the latest snapshot in Available state
      Service TerminationButton to terminate the service
      Table. Status information and additional features

Details

On the Block Storage List page, you can view detailed information of the selected resource and modify information if necessary.

ItemDescription
ServiceService group
Resource TypeResource type
SRNUnique resource ID in Samsung Cloud Platform
  • In Block Storage service, means volume SRN
Resource NameResource name
  • In Block Storage service, means volume name
Resource IDUnique resource ID of the service
CreatorUser who created the service
Creation DateDate and time when the service was created
ModifierUser who modified the service
Modification DateDate and time when the service was modified
Volume NameVolume name
  • If volume name modification is needed, click the Modify button
Volume IDUnique volume ID
Disk TypeDisk type
TypeClassification according to volume creation method and usage
CapacityVolume capacity
  • Can expand to capacity that is a multiple of 8 within 12,288GB
  • Cannot reduce capacity
  • If capacity expansion is needed, click the Modify button
Max IOPSRequired
Max ThroughputRequired
Connected ServerConnected Virtual Server
  • Server ID: Unique server ID
  • Server Name: Server name
  • Status: Server status
  • Connection Information: Connection information of the volume for server connection
  • When adding Virtual Server connection, click the Add button
  • When removing Virtual Server connection, click the Disconnect button
Table. Block Storage details items
Note
Volumes containing the name vProtect are temporary volumes created when using the Backup service and are not charged.

Snapshot List

On the Block Storage List page, you can view snapshots of the selected resource.

ItemDescription
Snapshot NameSnapshot name
DescriptionSnapshot description
Volume CapacityCapacity of the Block Storage original volume that is the snapshot target
  • If the original volume capacity and the snapshot volume capacity are different, only recovery by creating a recovery volume is possible
Creation DateSnapshot creation date/time
StatusStatus of the snapshot
  • Available: Creation complete, can recover
  • Creating: Being created
  • Error: Abnormal state
  • Deleting: Being deleted
  • Error Deleting: Abnormal state during deletion
  • Restoring: Recovering
  • Backing Up: Being backed up
Additional Features > MoreSnapshot management buttons
  • Modify: Modify snapshot name and description
DeleteCan delete by selecting snapshot to delete from snapshot list
Table. Snapshot list tab detailed information items
Warning
  • Snapshots can affect volume capacity management. Please delete unnecessary snapshots after use.
  • Snapshot recovery is possible when not connected to a server.
Note
  • Snapshot creation date/time is based on Asia/Seoul (GMT +09:00).
  • When clicking the snapshot recovery button, the volume is recovered to the latest snapshot in Available status.
  • When selecting create recovery volume on the snapshot list page, a new snapshot-based volume is created without changing the existing volume.
  • Snapshots containing the name vProtect are temporary snapshots created when using the Backup service and are not charged.

Tags

On the Block Storage List page, you can view tag information of the selected resource, and add, modify, or delete tags.

ItemDescription
Tag ListTag list
  • Can view Key, Value information of tags
  • Can add up to 50 tags per resource
  • When entering tags, search and select from existing Key and Value lists
Table. Block Storage tag tab items

Operation History

On the Block Storage List page, you can view the operation history of the selected resource.

ItemDescription
Operation History ListResource change history
  • View operation date/time, resource type, resource ID, resource name, operation details, event topic, operation result, operator information
  • To perform detailed search, click the detailed search button
Table. Operation history tab detailed information items

Managing Block Storage Resources

If you need to modify settings of created Block Storage or add or delete connected servers, you can perform tasks on the Block Storage Details page.

Modifying Volume Name

You can modify the name of a volume. To modify the volume name, follow these steps:

  1. Click the All Services > Compute > Virtual Server menu. This will take you to the Virtual Server Service Home page.
  2. Click the Block Storage menu. This will take you to the Block Storage List page.
  3. Click the resource for which you want to modify the volume name on the Block Storage List page. This will take you to the Block Storage Details page.
  4. Click the Modify button of Volume Name. The Modify Volume Name popup window opens.
  5. Enter the volume name and click the Confirm button.
Note
Enter within 255 characters using English letters, numbers, spaces, and special characters (-, _).

Expanding Capacity

You can expand the capacity of a volume. To expand capacity, follow these steps:

  1. Click the All Services > Compute > Virtual Server menu. This will take you to the Virtual Server Service Home page.
  2. Click the Block Storage menu. This will take you to the Block Storage List page.
  3. Click the resource for which you want to expand capacity on the Block Storage List page. This will take you to the Block Storage Details page.
  4. Click the Modify button of Capacity. The Modify Capacity popup window opens.
  5. Enter the capacity and click the Confirm button.
Warning
  • Capacity reduction is not provided.
  • After capacity expansion, recovery to snapshots before expansion is not possible.
  • Only recovery by creating a new volume is possible with snapshots created before capacity expansion.
Note
  • Can expand to capacity larger than existing capacity within 8~12,228GB.
  • Enter the number of Units provided in 8GB increments.

Modifying Connected Server

You can connect or disconnect servers. To modify connected server, follow these steps:

  1. Click the All Services > Compute > Virtual Server menu. This will take you to the Virtual Server Service Home page.
  2. Click the Block Storage menu. This will take you to the Block Storage List page.
  3. Click the resource for which you want to modify connected server on the Block Storage List page. This will take you to the Block Storage Details page.
  4. When adding Virtual Server connection, click the Add button in the Connected Server item. The Add Connected Server popup window opens.
  5. Select the Virtual Server you want to connect and click the Confirm button.
  6. When disconnecting Virtual Server connection, click the Disconnect button in the Connected Server item.
    • Be sure to perform disconnection work (Umount, Disk Offline) from the server before disconnecting.
Warning
Be sure to perform disconnection work (Umount, Disk Offline) from the server before disconnecting the connected server. If disconnected without OS work, a status error (Hang) may occur on the connected server. For details on server disconnection, see Disconnecting Server.
Note
  • You can connect Virtual Servers created in the same location as Block Storage.
  • Virtual Servers using Partition with Server Group policy cannot be connected.
  • For HDD/SSD_MultiAttach disk type, can connect with 2 or more Virtual Servers and there is no limit on the number of connections.
    • Windows-based Virtual Server cannot use MultiAttach disks and must use a separate replication method or solution.
  • Virtual Server can connect up to 26 volumes including OS basic.
  • OS basic volume cannot modify connected server and cannot terminate service.
  • When adding connected server, can use after performing connection work (Mount, Disk Online) from the server. For details on server connection, see Connecting Server.

Terminating Block Storage

You can reduce operating costs by terminating unused Block Storage. However, since terminating a service may immediately stop the operating service, you should proceed with termination after fully considering the impact of service interruption.

Warning
  • Be careful as data cannot be recovered after termination.
  • Block Storage volumes cannot be terminated in the following cases.
    • While connected to server
    • OS basic volume
    • Connected to Custom Image of Virtual Server
    • When volume status is not Available, Error, Error Extending, Error Restoring, Error Managing
  • When terminating by selecting 2 or more volumes, only volumes that can be terminated will be terminated.

To terminate Block Storage, follow these steps:

  1. Click the All Services > Compute > Virtual Server menu. This will take you to the Virtual Server Service Home page.
  2. Click the Block Storage menu. This will take you to the Block Storage List page.
  3. Select the resource to terminate on the Block Storage List page and click the Terminate Service button.
  4. When termination is complete, verify that the resource has been terminated on the Block Storage List page.

2.8.2.1 - Connecting to the Server

When using a volume on a server, connection or disconnection work is required.
From the Block Storage Details page, add the connection server and then connect to the server to perform the connection work (Mount, Disk Online). After use, perform the disconnection work (Umount, Disk Offline) and then remove the connection server.

Connecting to the Server (Mount, Disk Online)

To use the volume added to the connection server, you must connect to the server and perform the connection work (Mount, Disk Online). Follow the procedure below.

Linux Operating System

Server Connection Example Configuration
  • Server OS: LINUX
  • Mount location: /data
  • Volume capacity: 24 GB
  • File system: ext3, ext4, xfs etc
  • Additional allocated disk: /dev/vdb
  1. Click the All Services > Compute > Virtual Server menu. Move to the Service Home page of Virtual Server.
  2. Click the Block Storage menu. Move to the Block Storage List page.
  3. On the Block Storage List page, click the resource to be used by the connection server. Move to the Block Storage Details page.
  4. Check the server in the Connection Server section and connect to it.
  5. Refer to the procedure below to connect (Mount) the volume.
  • Switch to root privileges

    $ sudo -i
    
  • Check the disk

    # lsblk
    NAME    MAJ:MIN  RM   SIZE RO TYPE MOUNTPOINT
    vda       252:0   0    24G  0 disk
    ├─vda1    252:1   0  23.9G  0 part [SWAP]
    └─vda14   252:14  0     4M  0 part /
    └─vda15   252:15  0   106M  0 part /boot/efi
    vdb       252:16  0    24G  0 disk
    
  • Create a partition

    # fdisk /dev/vdb
    Command (m for help): n
    
    Partition type:
       p   primary (0 primary, 0 extended, 4 free)
       e   extended
    Select (default p): p
    Partition number (1-4, default 1): 1
    First sector (2048-50331646, default 2048):
    Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-50331646, default 50331646):
    
    Created a new partition 1 of type 'Linux' and of size 24 GiB.
    
    Command (m for help): w
    The partition table has been altered!
    Calling ioctl() to re-read partition table.
    Syncing disks.
    
  • Set the partition format (e.g., ext4)

    # lsblk
    NAME    MAJ:MIN  RM   SIZE RO TYPE MOUNTPOINT
    vda       252:0   0    24G  0 disk
    ├─vda1    252:1   0  23.9G  0 part [SWAP]
    └─vda14   252:14  0     4M  0 part /
    └─vda15   252:15  0   106M  0 part /boot/efi
    vdb       252:16  0    24G  0 disk
    └─vdb1    252:17  0    24G  0 part
    
    # mkfs.ext4 /dev/vdb1
    mke2fs 1.46.5 (30-Dec-2021)
    ...
    Writing superblocks and filesystem accounting information: done
    
  • Mount the volume

    # mkdir /data
    
    # mount /dev/vdb1 /data
    
    # lsblk
    NAME    MAJ:MIN  RM   SIZE RO TYPE MOUNTPOINT
    vda       252:0   0    24G  0 disk
    ├─vda1    252:1   0  23.9G  0 part [SWAP]
    └─vda14   252:14  0     4M  0 part /
    └─vda15   252:15  0   106M  0 part /boot/efi
    vdb       252:16  0    24G  0 disk
    └─vdb1    252:17  0    24G  0 part /data
    
    # vi /etc/fstab
    (add) /dev/vdb1     /data       ext4     defaults   0 0
    
ItemDescription
cat /etc/fstabFile system information file
  • Used when the server starts
df -hCheck the total disk usage of the mounted disk
fdisk -lCheck partition information
  • Physical disks are displayed with letters such as /dev/sda, /dev/sdb, /dev/sdc
  • Disk partitions are displayed with numbers such as /dev/sda1, /dev/sda2, /dev/sda3
Table. Mount Command Reference
CommandDescription
mCheck the usage of the fdisk command
nCreate a new partition
pCheck the changed partition information
tChange the system ID of the partition
wSave the partition information and exit the fdisk settings
Table. Partition Creation Command (fdisk) Reference

Windows Operating System

  1. Click the All Services > Compute > Virtual Server menu. Move to the Service Home page of Virtual Server.
  2. Click the Block Storage menu. Move to the Block Storage List page.
  3. On the Block Storage List page, click the resource to be used by the connection server. Move to the Block Storage Details page.
  4. Check the server in the Connection Server section and connect to it.
  5. Refer to the procedure below to connect (Disk Online) the volume.
    • Right-click the Windows start icon and run Computer Management

    • In the Computer Management tree structure, select Storage > Disk Management

    • Check the disk

      Mount

    • Bring the disk online

      Mount

    • Initialize the disk

      Mount

      Mount
    • Format the partition

      Mount

      Mount
      Mount
    • Check the volume

      Mount

Disconnecting from the Server (Umount, Disk Offline)

Connect to the server and perform the disconnection work (Umount, Disk Offline), and then remove the connection server from the console.

Follow the procedure below.

Note
  • If you disconnect the server from the console without performing the disconnection work (Umount, Disk Offline) on the server, a server status error (Hang) may occur.
    • Be sure to perform the OS work first.
  • For the OS basic volume, connection server modification and service termination are not allowed.

Linux Operating System

  1. Click the All Services > Compute > Virtual Server menu. Move to the Service Home page of Virtual Server.
  2. Click the Block Storage menu. Move to the Block Storage List page.
  3. On the Block Storage List page, click the resource to be disconnected from the connection server. Move to the Block Storage Details page.
  4. Check the server in the Connection Server section and connect to it.
  5. Refer to the procedure below to disconnect (Umount) the volume.
    • Umount the volume
  # umount /dev/vdb1 /data
   
  # lsblk
  NAME    MAJ:MIN  RM   SIZE RO TYPE MOUNTPOINT
  vda       252:0   0    24G  0 disk
  ├─vda1    252:1   0  23.9G  0 part [SWAP]
  └─vda14   252:14  0     4M  0 part /
  └─vda15   252:15  0   106M  0 part /boot/efi
  vdb       252:16  0    24G  0 disk
  └─vdb1    252:17  0    24G  0 part
   
  # vi /etc/fstab
  (delete) /dev/vdb1     /data       ext4     defaults   0 0

Windows Operating System

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

  2. Click the Block Storage menu. Move to the Block Storage List page.

  3. On the Block Storage List page, click the resource to be disconnected from the connection server. Move to the Block Storage Details page.

  4. Check the server in the Connection Server section and connect to it.

  5. Unmount the file system.

  6. Refer to the procedure below to disconnect (Disk Offline) the volume.

    • Right-click the Windows start icon and run Computer Management

    • In the Computer Management tree structure, select Storage > Disk Management

    • Right-click the disk to be removed and run Offline

      Umount
    • Check the disk status

      Umount

2.8.2.2 - Using Snapshots

You can create, delete, or restore snapshots of the created Block Storage using snapshots. You can perform actions on the Block Storage Details page and Snapshot List page.

Create Snapshot

You can create a snapshot of the current point in time. To create a snapshot, follow these steps.

  1. All Services > Compute > Virtual Server Click the menu. Navigate to the Service Home page of Virtual Server.
  2. Click the Block Storage menu. Go to the Block Storage List page.
  3. Block Storage List On the page, click the resource to create a snapshot. Block Storage Details Go to the page.
  4. Click the Create Snapshot button. The Create Snapshot popup window opens.
  5. Enter Snapshot Name and Description, then click the Confirm button. It creates a snapshot of the current point in time.
  6. Snapshot List Click the button. Block Storage Snapshot List Navigate to the page.
  7. Check the generated snapshot.
Caution
Snapshots are charged based on the size of the original Block Storage, so please delete unnecessary snapshots.
Reference
The snapshot creation time is based on Asia/Seoul (GMT +09:00).

Edit Snapshot

You can edit snapshot information. To edit the snapshot name or description, follow the steps below.

  1. All Services > Compute > Virtual Server Click the menu. Navigate to the Service Home page of Virtual Server.
  2. Block Storage Click the menu. Navigate to the Block Storage List page.
  3. Block Storage List page, click the resource to edit the snapshot information. You will be taken to the Block Storage Details page.
  4. Snapshot List Click the button. Block Storage Snapshot List Navigate to the page.
  5. After confirming the snapshot to edit, click the More button.
  6. Click the Edit button. The Edit Snapshot popup opens.
  7. Enter Snapshot name or Description and click the Confirm button.

Recover Snapshot

You can restore a Block Storage volume to the latest snapshot in Available state. To perform snapshot restoration, follow the steps below.

  1. All Services > Compute > Virtual Server Click the menu. Navigate to Virtual Server’s Service Home page.
  2. Click the Block Storage menu. Navigate to the Block Storage List page.
  3. Click the resource to recover from a snapshot on the Block Storage List page. You will be taken to the Block Storage Details page.
  4. Connection Server If there is a server added in the item, after connecting to the server, perform the disconnect operation (Umount, Disk Offline).
  • For detailed information about server disconnection, please refer to Disconnect Server.
  1. Block Storage Details page, click the Disconnect button in the Connected Server item to remove the server. The connected server will be removed.
  2. Snapshot List Click the button. Block Storage Snapshot List Navigate to the page.
  3. Check the latest snapshot in Available state. The volume will be restored with that snapshot.
  4. Click the Snapshot Recovery button. The Snapshot Recovery popup opens.
  5. After checking the Snapshot name and creation date/time, click the Confirm button.
    • When recovery starts, it becomes Reverting, and when completed, it becomes Available.
  6. Detailed Information Click the page button. Block Storage Detailed Page will navigate to.
  7. Click the Add button of the Connected Server. Reconnect the Virtual Server.
  8. After connecting to the added server, perform the connection tasks (Mount, Disk Online) according to the operating system.
Caution
  • Snapshot recovery is possible when not connected to the server.
  • If you want to recover using a snapshot that is not the latest snapshot, recovery is possible by creating a recovery volume.
  • In the situation below, recovery is not possible.
    • Block Storage when the volume is not in Available state
    • Block Storage if there is a server connected to the volume
    • If there are no recoverable snapshots
    • If the latest snapshot changes during recovery creation
    • If the latest snapshot is not in Available state
    • If the snapshot’s volume size differs from the Block Storage volume size (when the volume has been expanded)

Create snapshot recovery volume

You can create a volume using a snapshot. To create a snapshot recovery volume, 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 Block Storage menu. You will be taken to the Block Storage list page.
  3. Click the resource to create a snapshot recovery volume on the Block Storage List page. You will be taken to the Block Storage Details page.
  4. Snapshot List Click the button. Block Storage Snapshot List Navigate to the page.
  5. After checking Snapshot name, description and Creation date/time, click the More button of the snapshot you want to restore.
  6. Click Create Recovery Volume. The Create Snapshot Recovery Volume popup opens.
  7. Click the Confirm button. You will be taken to the Create Block Storage page.
  8. Block Storage creation On the page, enter the information required to create the service, and select detailed options.
    • Please enter the volume name and size. You can enter a size that is greater than or equal to the original volume.
    • Disk type is set the same as the original and cannot be modified.
      Category
      Required
      Detailed description
      Volume NameRequiredVolume Name
      • Enter up to 255 characters using English letters, numbers, spaces, and special characters (-, _)
      Disk TypeRequiredSelect Disk Type
      • HDD: Standard volume
      • SSD: High-performance standard volume
      • HDD/SSD_KMS: Volume that additionally provides transmission encryption between the instance and Block Storage
      • HDD/SSD_MultiAttach: Volume that can be attached to more than one server
      • Cannot be modified after service creation
      • When creating a service via snapshot recovery volume creation, it is set identical to the original and cannot be modified
      CapacitySelectCapacity Setting
      • Can be created within 8~12,228GB
      • Enter the number of units provided in 8GB increments
      • When creating a service via snapshot recovery volume creation, input a capacity equal to or larger than the original
      Recovery Snapshot NameOptionalName of the recovery snapshot used when creating the volume
      • Provides the recovery snapshot name when creating a service through snapshot recovery volume creation
      Table. Block Storage Service Information Input Items
  9. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resource on the Block Storage List page.

Delete Snapshot

You can select a snapshot to delete. To delete a snapshot, follow these steps.

  1. All Services > Compute > Virtual Server Click the menu. Go to the Service Home page of Virtual Server.
  2. Click the Block Storage menu. Go to the Block Storage List page.
  3. Block Storage List on the page, click the resource to delete the snapshot. Block Storage Details navigate to the page.
  4. Snapshot List button, click it. Block Storage Snapshot List page, navigate to it.
  5. After checking the snapshot name, description and creation date/time, click the more button of the snapshot you want to delete.
  6. Delete Click the button. Snapshot List page, the snapshot will be removed.

2.8.2.3 - Move Volume

You can move the volume to a different Account, and if you move it, the volume will be removed from the existing location. You can perform volume migration from the Block Storage list or Block Storage detail page.

Volume previous

You can move a volume to a different account within the region. To move a volume, follow these steps.

  1. Click All services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Block Storage menu is clicked. It moves to the Block Storage list page.
  3. Block Storage list page, select the resource to be moved, and then click the More > Move Volume button at the top left of the list.
    • or click the Volume Migration button at the top of the Block Storage details page of the resource to be migrated.
  4. When the pop-up window for volume migration appears, check the volume name you want to migrate and click the Confirm button.
  5. When the popup window for previous completion opens, click the Confirm button. The Volume Transfer ID and Approval Key information will be downloaded as a text file.
  6. The volume will be changed to Awaiting Transfer status.
Caution
  • Volume migration is possible within the same region.
  • Volume migration is only possible when the volume is in the Available state. If it is in the In Use state, release all connected servers.

Volume rollback cancel

The volume move can be cancelled after it is created. To cancel the volume move, follow these steps.

  1. Click All services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Block Storage menu is clicked. It moves to the Block Storage list page.
  3. Block Storage list page, click the resource to cancel the volume move. It moves to the Block Storage detail page.
    • You can cancel if the volume is in the Awaiting Transfer state.
  4. Click the Volume Move Cancel button. The Volume Move Cancel popup window will open.
  5. Check the volume name you want to cancel the volume move and click the Confirm button.
  6. The volume will be changed to Available status.

Get previous volume

You can receive volumes from other accounts within the region. To receive a volume, follow these steps.

  1. Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
  2. Block Storage menu is clicked. It moves to the Block Storage list page.
  3. On the Block Storage list page, click the More > Receive Volume Transfer button in the upper left corner of the list. The Receive Volume Transfer popup window opens.4. Volume Migration Enter the Volume Migration ID and Approval Key provided when creating the volume migration.
  4. Block Storage list page will have the volume created.
Notice
  • It may take some time for the changes to be reflected.
  • The account that created the volume transfer will have the transferred volume removed.

2.8.3 - API Reference

API Reference

2.8.4 - CLI Reference

CLI Reference

2.8.5 - Release Note

Block Storage

2025.07.01
FEATURE Snapshot Billing Policy Change and Monitoring Linkage
  • The snapshot is charged based on the size of the original Block Storage.
  • It has been linked with Cloud Monitoring.
    • You can check IOPS, Latency, Throughput information in Cloud Monitoring.
2025.02.27
FEATURE Block Storage disk type added
  • Block Storage feature change
    • The HDD disk type has been added, and you can select the added type (HDD, HDD_MultiAttach, HDD_KMS) according to the purpose.
  • Samsung Cloud Platform common feature changes
    • Account, IAM and Service Home, tags, etc. reflected common CX changes.
2024.10.01
NEW Block Storage Service Official Version Release
  • SSD_KMS disk type has been added.
  • When SSD_KMS is selected, encryption through the KMS (Key Management Service) encryption key is added.
  • Released a high-performance storage service suitable for handling large-scale data and database workloads.
2024.07.02
NEW Beta version release
  • Released a high-performance storage service suitable for handling large-scale data and database workloads.

3 - Storage

Provides a data storage service that enhances stability and efficiency through various storage configurations.

3.1 - Block Storage(BM)

3.1.1 - Overview

Service Overview

Block Storage is a high-performance storage that stores data in block units with a certain size and arrangement.
It is suitable for large-capacity, high-performance requirements such as databases, mail servers, etc. and users can directly assign volumes to the server for use.

Key Features

  • High-capacity volume provision: you can create volumes of up to 16TB in size.
  • Full SSD-based high-performance delivery: Dualized Controller and Disk Array Raid-based, providing high durability and availability. Since the full SSD disk is provided by default, it is suitable for high-speed data processing tasks such as database workloads.
  • Snapshot Backup: Through the image snapshot function, it is possible to recover data that has been changed or deleted. The user selects a snapshot created at the desired recovery point from the list and performs the recovery.
  • Replication: creates identical replica volumes in different locations, and users can set the data replication cycle, in case the original volume is unavailable due to a disaster or failure, services can be provided through the replica volume.

Composition Diagram

Configuration Diagram
Figure. Block Storage configuration diagram

Provided Function

Block Storage provides the following functions.

  • Volume Name: The user can set or modify the name by volume.
  • Capacity: Volume creation is possible with a capacity of at least 1GB and up to 16TB.
  • Connection Server : Bare Metal Server, Multi Node GPU Cluster can be selected to connect or disconnect.
  • Multi Attach: connect up to 5 servers, no limit on the number of volumes that can be attached to a Bare Metal Server
  • Encryption: Regardless of the disk type, all volumes have AES-256 algorithm encryption enabled by default.
  • Snapshot: You can create a snapshot at a specific point in time using the image snapshot feature or generate snapshots at regular intervals.
  • Capacity: The capacity of snapshot storage space
  • Schedule: snapshot automatic creation cycle
  • Recovery: Restore the original volume to the latest snapshot, select a snapshot at a specific point in time to create a recovery volume
  • Recovery volume a separate volume created with the same capacity as the original (incurring additional costs)
  • Replication: replicates the volume to a different location, and users can set the replication cycle.
  • The replica volume can also serve as the original role in the event of a disaster through the snapshot function
  • Volume Group: Sets a group of up to 16 Block Storage volumes, allowing for snapshot and replication settings at the group level.
  • Monitoring: You can check performance information such as IOPS, Latency, Throughput through the Cloud Monitoring service.

Components

You can create a volume by entering the capacity based on the user’s service size and performance requirements and selecting the disk type.
When using the snapshot function, you can restore the data to the point you want to restore.

Volume

Volume is the basic creation unit of the Block Storage service and is used as a data storage space. The user creates a volume by setting the name, capacity, disk type, snapshot, etc., and then connects and uses it to the Bare Metal Server.
The volume name creation rule is as follows.

  • It starts with English and can be set within 3-28 characters using English, numbers, and special characters (-).

Snapshot

Snapshot is an image backup of a volume at a specific point in time. The user can select the snapshot to be recovered by checking the snapshot name and creation time in the snapshot list, and can recover the data changed or deleted through the snapshot.
The notes to refer to when using snapshots are as follows.

Reference
  • The snapshot creation time is based on Asia/Seoul (GMT +09:00) standard.
  • Snapshots can be created up to 1,023. (Automatic creation through scheduling is up to 128.)
  • Automatic generation through snapshot schedule setting is possible.
  • The snapshot capacity is added to the Block Storage(BM) fee, so adjust the capacity of the snapshot storage space.

Volume Group

Volume Group is a group unit management function that allows users who have configured databases and applications with two or more volumes to create snapshots and replicas at a consistent point in time, users can create a Volume Group by selecting a name and target Block Storage.

Preceding Service

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

Service CategoryServiceDetailed Description
ComputeBare Metal ServerHigh-performance physical server used without virtualization
Table. Block Storage(BM) Preceding Service

3.1.1.1 - Monitoring Metrics

Block Storage BM Monitoring Metrics

The following table shows the monitoring metrics of Block Storage BM that can be checked through Cloud Monitoring. For detailed usage of Cloud Monitoring, please refer to the Cloud Monitoring guide.

Performance Item NameDescriptionUnit
Instance StatusFile Storage Volume Statusstatus
Volume TotalTotal Bytesbytes
IOPS [Total]iops(total)iops
IOPS [Read]iops(reading)iops
IOPS [Write]iops(writing)iops
IOPS [Other]iops (etc.)iops
Latency Time [Total]Delay Time (Total)usec
Latency Time [Read]Delay Time (Read)usec
Latency Time [write]Delay Time (write)usec
Latency Time [Other]Delayed time (etc.)usec
Throughput [Total]Processing amount (total)bytes/s
Throughput [Read]Throughput (Read)bytes/s
Throughput [Write]Throughput (Write)bytes/s
Throughput [Other]Processing capacity (etc.)bytes/s
Table. Block Storage BM Monitoring Metrics

3.1.2 - How-to Guides

The user can enter the required information for Block Storage (BM) and select detailed options through the Samsung Cloud Platform Console to create the service.

Block Storage(BM) Create

You can create and use the Block Storage (BM) service from the Samsung Cloud Platform Console.

To create Block Storage (BM), follow the steps below.

  1. Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).

  2. Click the Block Storage(BM) Create button on the Service Home page. You will be taken to the Block Storage(BM) Create page.

  3. Block Storage(BM) Creation On the page, enter the information required to create the service, and select detailed options.

    Category
    Required
    Detailed description
    Volume NameRequiredVolume Name
    • Must start with an English letter and use English letters, numbers, and the special character (-) to input 3~28 characters
    • Cannot be modified after service creation
    Disk TypeRequiredSelect Disk Type
    • SSD: High-performance general volume
    • HDD: General volume
    • Cannot be modified after service creation
    CapacityRequiredCapacity Setting
    • Enter a number between 1~16,384GB
    • Cannot be modified after service creation
    IOPSRequiredEnter IOPS value
    • Enter a number between 3,000~16,000
    • HDD type does not provide performance metric setting function
    ThroughputRequiredEnter Throughput speed (MB/s)
    • Enter a number between 125~1,000
    • HDD type does not provide performance metric setting function
    Connection ServerRequiredSelect Connected Bare Metal Server
    • Provide up to 8 Bare Metal Server connections
    • No limit on the number of volumes that can be connected to a Bare Metal Server
    Table. Block Storage(BM) Service 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 Block Storage (BM) List page.
Note
  • All volumes are encrypted by default with server-side encryption based on the AES-256 algorithm, regardless of disk type.
  • Snapshot schedule can be set on the detail page.
  • The performance metrics (IOPS, Throughput) of the configured storage are based on the maximum values and do not guarantee consistent values.
Caution
Capacity cannot be modified after service creation. If needed, add a volume to the same server.

iSCSI Setting up

Volumes created by the user in addition to the OS default volume require iSCSI configuration.

Block Storage(BM) Details page’s iSCSI information after checking the IP provided, follow the iSCSI configuration method for each OS.

Linux Operating System

Notice

iSCSI information (Storage Target IP) was written assuming 10.40.40.41, 10.40.40.42.

  • Block Storage(BM) Check iSCSI information on the detail page.
  1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
  2. Click the Block Storage(BM) menu on the Service Home page. You will be taken to the Block Storage(BM) List page.
  3. Block Storage(BM) List page, click the resource to be used on the connected server. You will be taken to the Block Storage(BM) Details page.
  4. Connection Server Check the server in the item and then connect.
  5. Follow the procedure below to configure iSCSI.
    • Storage (target IP) Discover the connection information.
      Color mode
      [root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.41
      10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169
      
      [root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.42
      10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169
      [root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.41
      10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169
      
      [root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.42
      10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169
      Code Block. Storage (target IP) Connection Information Discovery
    • Connect to Storage (target IP). If already connected, proceed to the next step.
      Color mode
      [root@localhost ~]# iscsiadm -m node -p 10.40.40.41:3260 --login
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful.
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful
      
      [root@localhost ~]# iscsiadm -m node -p 10.40.40.42:3260 --login
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
      [root@localhost ~]# iscsiadm -m node -p 10.40.40.41:3260 --login
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful.
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful
      
      [root@localhost ~]# iscsiadm -m node -p 10.40.40.42:3260 --login
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
      Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
      Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
      Code block. Storage (target IP) connection
    • To minimize search time, delete all unused Storage (target IP).
      Color mode
      [root@localhost ~]# iscsiadm -m node show
      100.100.100.10:3260,1026 iqn.1992-08.com.netapp:sn.c9adbd09cf301d039ea2bc878:vs.3
      10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169
      10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169
      
      [root@localhost ~]# iscsiadm -m node -o delete -p 100.100.100.10:3260
      [root@localhost ~]# iscsiadm -m node show
      100.100.100.10:3260,1026 iqn.1992-08.com.netapp:sn.c9adbd09cf301d039ea2bc878:vs.3
      10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169
      10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169
      
      [root@localhost ~]# iscsiadm -m node -o delete -p 100.100.100.10:3260
      Code block. Delete unused Storage (target IP)
    • Please rescan to check additional Disk.
      Color mode
      [root@localhost ~]# iscsiadm -m session --rescan
      Rescanning session [sid: 65, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
      Rescanning session [sid: 66, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
      Rescanning session [sid: 67, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
      Rescanning session [sid: 68, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
      [root@localhost ~]# iscsiadm -m session --rescan
      Rescanning session [sid: 65, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
      Rescanning session [sid: 66, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
      Rescanning session [sid: 67, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
      Rescanning session [sid: 68, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
      Code block. Rescan
    • Set Auto Login so that it automatically logs in even after reboot.
      Color mode
      [root@localhost ~]# iscsiadm -m node --op=update -n node.conn[0].startup -v automatic
      [root@localhost ~]# iscsiadm -m node --op=update -n node.startup -v automatic
      [root@localhost ~]# iscsiadm -m node --op=update -n node.conn[0].startup -v automatic
      [root@localhost ~]# iscsiadm -m node --op=update -n node.startup -v automatic
      Code block. Auto Login setting
    • Please confirm the final settings using the following command.
      Color mode
      [root@localhost ~]# lsblk
      [root@localhost ~]# lsblk
      Code block. Check configuration content

Windows Operating System

Notice

iSCSI information (Storage Target IP) was written assuming 10.40.40.41, 10.40.40.42.

  • Block Storage(BM) Check iSCSI information on the detail page.
  1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Block Storage(BM) menu. Go to the Block Storage(BM) list page.
  3. Click the resource to be used on the connected server on the Block Storage(BM) List page. It moves to the Block Storage(BM) Details page.
  4. After checking the server in the Connection Server item, connect.
  5. Follow the procedure below to configure iSCSI.
    • Open Command Prompt (Admin) and run PowerShell.
      Color mode
      Windows PowerShell
      Copyright (C) Microsoft Corporation. All rights reserved.
      
      PS C:\Users> cd ..
      PS C:\>
      Windows PowerShell
      Copyright (C) Microsoft Corporation. All rights reserved.
      
      PS C:\Users> cd ..
      PS C:\>
      Code block. powershell execution
    • Start the volume service.
      Color mode
      PS C:\> Set-Service -Name MSiSCSI -StartupType Automatic
      PS C:\> Start-Service -Name MSiSCSI
      PS C:\> get-service -Name MSiSCSI |  select -Property Name, DisplayName, Status, StartType
      
      Name       DisplayName                           Status    StartType
      -------    --------------                        -------   -----------
      MSiSCSI    Microsoft iSCSI Initiator Service     Running   Automatic
      PS C:\> Set-Service -Name MSiSCSI -StartupType Automatic
      PS C:\> Start-Service -Name MSiSCSI
      PS C:\> get-service -Name MSiSCSI |  select -Property Name, DisplayName, Status, StartType
      
      Name       DisplayName                           Status    StartType
      -------    --------------                        -------   -----------
      MSiSCSI    Microsoft iSCSI Initiator Service     Running   Automatic
      Code block. Volume service start
    • Please install Multipath I/O. If the Restart Needed item is displayed as Yes, a restart is required.
      Color mode
      PS C:\> Install-WindowsFeature -name Multipath-IO
      
      Success   Restart Needed   Exit Code   Feature Result
      -------   --------------   ---------   -----------------
      True      No               Success     {Multipath I/O}
      PS C:\> Install-WindowsFeature -name Multipath-IO
      
      Success   Restart Needed   Exit Code   Feature Result
      -------   --------------   ---------   -----------------
      True      No               Success     {Multipath I/O}
      Code block. Multipath I/O installation
    • Please modify the Initiator Port Address.
      If you are not an Active Directory Member, skip this procedure. The Initiator Port Address needs to be modified only if you are an Active Directory Member.
      • iqn is generated based on the Hostname, but when joined to Active Dicrectory it changes to DNS format.
        Based on the basic hostname, it is registered in Storage, so for iqn.1991-05.com.microsoft:iqn01.scp.com, iqn01 is the Hostname. Remove DNS information and change it to the name registered when creating the OS in the user Console, such as iqn.1991-05.com.microsoft:iqn01.
      • If you are not an AD Member, no changes are required.
        Color mode
        PS C:\> $address = (Get-InitiatorPort | select NodeAddress)
        PS C:\> echo $address
        NodeAddress
        -----------
        iqn.1991-05.com.microsoft:iqn01.scp.com
        
        PS C:\> Set-InitiatorPort -NodeAddress $address.NodeAddress -NewNodeAddress "iqn.1991-05.com.microsoft:iqn01"
        PS C:\> Get-InitiatorPort | select NodeAddress
        NodeAddress
        -----------
        iqn.1991-05.com.microsoft:iqn01
        PS C:\> $address = (Get-InitiatorPort | select NodeAddress)
        PS C:\> echo $address
        NodeAddress
        -----------
        iqn.1991-05.com.microsoft:iqn01.scp.com
        
        PS C:\> Set-InitiatorPort -NodeAddress $address.NodeAddress -NewNodeAddress "iqn.1991-05.com.microsoft:iqn01"
        PS C:\> Get-InitiatorPort | select NodeAddress
        NodeAddress
        -----------
        iqn.1991-05.com.microsoft:iqn01
        Code Block. Initiator Port Address Edit
    • Storage (target Portal) Set the address as a variable.
      Color mode
      PS C:\> $TargetPortalAddresses = @("10.40.40.41", "10.40.40.42")
      PS C:\> $TargetPortalAddresses = @("10.40.40.41", "10.40.40.42")
      Code block. Set Storage (target Portal) address as variable
    • Discover the Storage (target Portal).
      Color mode
      PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
          New-IscsiTargetPortal -TargetPortalAddress $TargetPortalAddress
      }
      InitiatorInstanceName   :
      InitiatorPortalAddress  :
      IsDataDigest            : False
      IsHeaderDigest          : False
      TargetPortalAddress     : 10.40.40.41
      TargetPortalPortNumber  : 3260
      PSComputerName          :
      
      InitiatorInstanceName   :
      InitiatorPortalAddress  :
      IsDataDigest            : False
      IsHeaderDigest          : False
      TargetPortalAddress     : 10.40.40.42
      TargetPortalPortNumber  : 3260
      PSComputerName          :
      PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
          New-IscsiTargetPortal -TargetPortalAddress $TargetPortalAddress
      }
      InitiatorInstanceName   :
      InitiatorPortalAddress  :
      IsDataDigest            : False
      IsHeaderDigest          : False
      TargetPortalAddress     : 10.40.40.41
      TargetPortalPortNumber  : 3260
      PSComputerName          :
      
      InitiatorInstanceName   :
      InitiatorPortalAddress  :
      IsDataDigest            : False
      IsHeaderDigest          : False
      TargetPortalAddress     : 10.40.40.42
      TargetPortalPortNumber  : 3260
      PSComputerName          :
      Code block. Storage (target Portal) Discovery
    • Connect the disk (target).
      Color mode
      PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
          Get-IscsiTarget | Connect-IscsiTarget -IsMultipathEnabled $true -IsPersistent $true -TargetPortalAddress $TargetPortalAddress
      }
      AuthenticationType      : NONE
      InitiatorInstanceName   : ROOT\ISCSIPRT\0000_0
      InitiatorNodeAddress    : iqn.1991-05.com.microsoft:iqn01
      InitiatorPortalAddress  : 0.0.0.0
      InitiatorSideIdentifier : 400001370000
      IsConnected             : True
      IsDataDigest            : False
      IsDiscovered            : True
      IsHeaderDigest          : False
      IsPersistent            : True
      NumberOfConnections     : 1
      SessionIdentifier       : ffffcd0b7ba58010-4000013700000006
      TargetNodeAddress       : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
      TargetSideIdentifier    : 1100
      PSComputerName          :
      
      AuthenticationType      : NONE
      InitiatorInstanceName   : ROOT\ISCSIPRT\0000_0
      InitiatorNodeAddress    : iqn.1991-05.com.microsoft:iqn01
      InitiatorPortalAddress  : 0.0.0.0
      InitiatorSideIdentifier : 400001370002
      IsConnected             : True
      IsDataDigest            : False
      IsDiscovered            : True
      IsHeaderDigest          : False
      IsPersistent            : True
      NumberOfConnections     : 1
      SessionIdentifier       : ffffcd0b7ba58010-4000013700000007
      TargetNodeAddress       : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
      TargetSideIdentifier    : 1000
      PSComputerName          :IsHeaderDigest         : False
      TargetPortalAddress     : 10.40.40.42
      TargetPortalPortNumber  : 3260
      PSComputerName          :
      PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
          Get-IscsiTarget | Connect-IscsiTarget -IsMultipathEnabled $true -IsPersistent $true -TargetPortalAddress $TargetPortalAddress
      }
      AuthenticationType      : NONE
      InitiatorInstanceName   : ROOT\ISCSIPRT\0000_0
      InitiatorNodeAddress    : iqn.1991-05.com.microsoft:iqn01
      InitiatorPortalAddress  : 0.0.0.0
      InitiatorSideIdentifier : 400001370000
      IsConnected             : True
      IsDataDigest            : False
      IsDiscovered            : True
      IsHeaderDigest          : False
      IsPersistent            : True
      NumberOfConnections     : 1
      SessionIdentifier       : ffffcd0b7ba58010-4000013700000006
      TargetNodeAddress       : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
      TargetSideIdentifier    : 1100
      PSComputerName          :
      
      AuthenticationType      : NONE
      InitiatorInstanceName   : ROOT\ISCSIPRT\0000_0
      InitiatorNodeAddress    : iqn.1991-05.com.microsoft:iqn01
      InitiatorPortalAddress  : 0.0.0.0
      InitiatorSideIdentifier : 400001370002
      IsConnected             : True
      IsDataDigest            : False
      IsDiscovered            : True
      IsHeaderDigest          : False
      IsPersistent            : True
      NumberOfConnections     : 1
      SessionIdentifier       : ffffcd0b7ba58010-4000013700000007
      TargetNodeAddress       : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
      TargetSideIdentifier    : 1000
      PSComputerName          :IsHeaderDigest         : False
      TargetPortalAddress     : 10.40.40.42
      TargetPortalPortNumber  : 3260
      PSComputerName          :
      Code block. Disk (target) connection
    • Refresh Storage (target) information.
      Color mode
      PS C:\> Update-IscsiTarget
      PS C:\> Update-IscsiTarget
      Code Block. Storage (target) Information Refresh
    • Register the Multipath I/O DSM and create an MPIO Disk.
      When creating an MPIO disk, a query occurs if a reboot is required. Reboot by entering Y or the Enter Key.
      Color mode
      PS C:\> New-MSDSMSupportedHW -VendorId MSFT2005 -ProductId iSCSIBusType_0x9
      PS C:\> Update-MPIOClaimedHW
      
      Confirm
      Are you sure you want to perform this action?
      The operation may require a system restart.
      [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"):
      False
      PS C:\> New-MSDSMSupportedHW -VendorId MSFT2005 -ProductId iSCSIBusType_0x9
      PS C:\> Update-MPIOClaimedHW
      
      Confirm
      Are you sure you want to perform this action?
      The operation may require a system restart.
      [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"):
      False
      Code block. Multipath I/O DSM registration, MPIO Disk creation
    • Multipath I/O Disk Check the list and path.
      mpclaim.exe can be used to check MPIO disk information. Enter the generated MPIO disk number to check the disk path and status.
      Color mode
      PS C:\> mpclaim.exe -s -d
      For more information about a particular disk, use 'mpclaim -s -d #' where # is the MPIO disk number.
      
      MPIO Disk    System Disk  LB Policy    DSM Name
      -------------------------------------------------------------------------------
      MPIO Disk3   Disk 1       RR           Microsoft DSM
      
      PS C:\> mpclaim.exe -s -d 3
      MPIO Disk3: 02 Paths, Round Robin, Symmetric Access
          Controlling DSM: Microsoft DSM
          SN: 600A098038314853475D543544614131
          Supported Load Balance Policies: FOO RR RRWS LQD WP LB
      
          Path ID          State              SCSI Address      Weight
          ---------------------------------------------------------------------------
          0000000077040001 Active/Optimized   004|000|001|000   0
              TPG_State : Active/Optimized  , TPG_Id: 1000, : 25
      
          0000000077040000 Active/Optimized   004|000|000|000   0
              TPG_State : Active/Optimized  , TPG_Id: 1001, : 26
      PS C:\> mpclaim.exe -s -d
      For more information about a particular disk, use 'mpclaim -s -d #' where # is the MPIO disk number.
      
      MPIO Disk    System Disk  LB Policy    DSM Name
      -------------------------------------------------------------------------------
      MPIO Disk3   Disk 1       RR           Microsoft DSM
      
      PS C:\> mpclaim.exe -s -d 3
      MPIO Disk3: 02 Paths, Round Robin, Symmetric Access
          Controlling DSM: Microsoft DSM
          SN: 600A098038314853475D543544614131
          Supported Load Balance Policies: FOO RR RRWS LQD WP LB
      
          Path ID          State              SCSI Address      Weight
          ---------------------------------------------------------------------------
          0000000077040001 Active/Optimized   004|000|001|000   0
              TPG_State : Active/Optimized  , TPG_Id: 1000, : 25
      
          0000000077040000 Active/Optimized   004|000|000|000   0
              TPG_State : Active/Optimized  , TPG_Id: 1001, : 26
      Code block. Multipath I/O Disk list and path verification
    • Please check in Disk Management.

Block Storage(BM) Check Detailed Information

Block Storage(BM) service can view and edit the full resource list and detailed information. Block Storage(BM) Detail page consists of Detail Information, Snapshot List, Replication, Operation History tabs.

To view detailed information of the Block Storage (BM) service, follow the steps below.

  1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
  2. Click the Block Storage(BM) menu on the Service Home page. You will be taken to the Block Storage(BM) List page.
  3. Click the resource to view detailed information on the Block Storage(BM) List page. You will be taken to the Block Storage(BM) Details page.
    • Block Storage(BM) Details page displays status information and additional feature information, and consists of Details, Snapshot List, Replication, Tags, Operation History tabs.
      CategoryDetailed description
      Volume StatusStatus of the volume
      • Creating: Creating
      • Available: Creation completed, server connection possible
      • Attaching: Connecting to server
      • Detaching: Disconnecting from server
      • In Use: Server connection established
      • Deleting: Service termination in progress
      • Editing: Changing settings
      • Error Deleting: Abnormal state while deleting
      • Error: Abnormal state during creation
      Create ReplicationCreate a replica at another location
      • For detailed information about replication creation, see [Create Replication](/userguide/storage/block_storage_bm/how_to_guides/replication.md/#복제-생성하기)
      | | Snapshot Creation | Create a snapshot at a specific point in time
      • For detailed information on snapshot creation, see [Create Snapshot](/userguide/storage/block_storage_bm/how_to_guides/snapshot.md/#스냅샷-생성하기)
      | |Service termination|Button to cancel the service|
      Table. Status Information and Additional Functions
Reference
In the case of a recovery copy, snapshot list, replication tabs are not displayed.

Detailed Information

Block Storage(BM) List page allows you to view detailed information of the selected resource and, if necessary, edit the information.

CategoryDetailed description
serviceservice name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In the Block Storage (BM) service, it refers to the volume SRN
Resource NameResource Name
  • In Block Storage(BM) service, it refers to the volume name
Resource IDUnique resource ID of the service
CreatorUser who created the service
Creation timeDate/time the service was created
EditorUser who modified the service
Modification Date/TimeDate/Time when the service was modified
Volume NameVolume Name
  • If you need to edit the volume name, click the Edit button
CategoryOriginal status regarding duplication
Storage Volume NameVolume name within storage device
  • Information distinguishing the volume used for analysis when failures and issues occur
capacityvolume capacity
IOPSIOPS value set when creating service
  • HDD type does not provide this metric
ThroughputThroughput speed (MB/s) set when creating the service
  • HDD type does not provide this metric
Disk typeDisk type
EncryptionEncryption status
  • Encryption provided by default regardless of disk type
Volume GroupName of the Volume Group that the volume belongs to
iSCSI informationStorage Target IP information for server connection
Snapshot CapacityCapacity of snapshot storage space
  • Charges incurred according to the set capacity
  • Click the edit button if you need to set snapshot capacity
  • For detailed information on snapshot capacity, refer to [Edit Snapshot Capacity](/userguide/storage/block_storage_bm/how_to_guides/_index.md/#스냅샷-용량-수정하기)
| | Snapshot Schedule | Snapshot automatic creation cycle
  • After setting snapshot capacity, schedule can be registered
  • Click the edit button when snapshot schedule setting is needed
  • For detailed information on snapshot schedule, refer to [Edit Snapshot Schedule](/userguide/storage/block_storage_bm/how_to_guides/_index.md/#스냅샷-스케줄-수정하기)
| | Snapshot | Name of the snapshot
  • Display when a snapshot exists
  • Click the name to go to the snapshot's detail page
  • For details on creating a snapshot, see [Create Snapshot](/userguide/storage/block_storage_bm/how_to_guides/snapshot.md/#복구본-생성하기)
| | Connected Server | Connected Bare Metal Server
  • **Server Name**: Server Name
  • **Image**: Server's OS image
  • **Status**: Server status
  • When adding a Bare Metal Server connection, click the **Add** button
  • When removing a Bare Metal Server connection, click the **Disconnect** button
  • For more details about the connected server, see [Edit Connected Server](/userguide/storage/block_storage_bm/how_to_guides/_index.md/#연결-서버-수정하기)
|
Table. Block Storage(BM) Detailed Information Items
Reference
For volumes created before December 18, 2025, IOPS and Throughput information is not displayed.

Snapshot List

Block Storage(BM) List page allows you to view the snapshot of the selected resource.

CategoryDetailed description
Snapshot UsageTotal Capacity of Stored Snapshots
Snapshot nameSnapshot name
CapacitySnapshot Capacity
Creation TimeSnapshot Creation Time
Additional features > MoreSnapshot management button
  • Restore: Restore volume from snapshot
  • Create restore point: Create restore point from snapshot
  • Delete: Delete snapshot
Table. Snapshot List Tab Detailed Information Items
Caution
  • If the maximum number of snapshots or the snapshot space threshold (around 90%) is exceeded, older snapshots will be deleted.
  • If the snapshot capacity usage rate is high (around 90%), replication may be stopped.
  • Snapshots can be created up to a maximum of 1,023 (the automatic creation count via schedule is up to 128), and if the maximum creation count is exceeded, no more snapshots can be created.
  • Snapshot recovery must be performed while all connected servers are disconnected (Umount, Disk Offline), and the recovered volume can be used after being reconnected (Mount, Disk Online).
  • Only one recovery copy can be created, and it is a separate volume that incurs the same charges as the original.
Reference
  • Snapshot creation date and time is based on Asia/Seoul (GMT +09:00).
  • Snapmirror files cannot be deleted when using replication.
  • When using Volume Group, set the snapshot schedule on the Volume Group (BM) detail information screen. The created snapshots can be viewed in the Block Storage (BM) snapshot list.

Replication

Block Storage(BM) List page you can view the replication information of the selected resource.

CategoryDetailed description
Replication PolicyReplication policy set by the user
Replication CycleReplication cycle of the original set by the user
Replication StatusReplication progress status according to policy settings
Volume InformationVolume information of original and replica
  • Classification: Distinguish whether original related to replication
  • Volume Name: Volume name of original or replica
  • Location: Location where the volume was created
  • Permissions: User permissions of the volume set according to replication policy
Table. Replication Tab Detailed Information Items
Caution
If the snapshot capacity usage rate is high (around 90%), replication may be stopped.
Reference
  • When creating a clone, a replica with the same disk type is created.
  • After setting the snapshot capacity, you can create a replica.
  • If using Volume Group, check the replication information on the Volume Group (BM) list page.
  • A replica can modify the connected server if the replication policy is stopped or deleted.
  • The replica can use the snapshot feature after the replication policy is deleted.
  • If the replication policy is stopped or the replication status is completed, you can modify the policy and schedule in the replica.

Tag

Block Storage(BM) List page allows you to view the tag information of the selected resource, and you can add, modify, or delete it.

CategoryDetailed description
Tag ListTag List
  • You can check the Key and Value information of tags
  • Up to 50 tags can be added per resource
  • When entering tags, search and select from the previously created Key and Value list
Table. Block Storage(BM) Tag Tab Items

Work History

Block Storage(BM) List page allows you to view the operation history of the selected resource.

CategoryDetailed description
Work History ListResource Change History
  • Work date and time, resource type, resource ID, resource name, work details, event topic, work result, verify worker information
  • Click the detailed search button to perform a detailed search
Table. Work History Tab Detailed Information Items

Block Storage(BM) Resource Management

If you need to modify the settings of a created Block Storage (BM) or add or delete a connected server, you can perform the task on the Block Storage (BM) Details page.

Edit Volume Name

You can edit the name of the volume. To edit the volume name, follow these steps.

  1. All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
  2. Click the Block Storage(BM) menu on the Service Home page. You will be taken to the Block Storage(BM) List page.
  3. Block Storage(BM) List Click the resource to edit the volume name. Block Storage(BM) Details page will be opened.
  4. Click the Edit button of Volume Name. Volume Name Edit popup opens.
  5. Enter the volume name and click the Confirm button.
Reference
It must start with an English letter and can be set using English letters, numbers, and the special character (-) within 3 to 28 characters.

Modify Snapshot Capacity

You can modify the capacity of the snapshot storage space. To modify the snapshot capacity, follow the steps below.

  1. All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Block Storage(BM) menu. Navigate to the Block Storage(BM) list page.
  3. Block Storage(BM) List page, click the resource to modify the snapshot capacity. Block Storage(BM) Details page will be opened.
  4. Click the Edit button of the Snapshot Capacity item. The Snapshot Capacity Edit popup window opens.
  5. Set the Usage status and Generation Capacity (%), and click the Confirm button.
    • Generation capacity(%) can be selected in units of 50 between 100 and 500.
Caution
  • The charges change depending on whether snapshots are used and their size. (Example: If the volume size is 10GB and the snapshot creation size is 100%, a total of 20GB charges occur.)
  • If the maximum number of snapshots or the snapshot space threshold (around 90%) is exceeded, older snapshots will be deleted.
  • If the size after modification is smaller than the original, older snapshots will be deleted first.
  • When edited as unused, all snapshots will be deleted.
  • Replication can be created after setting snapshot capacity.
  • After setting the snapshot capacity, it can be added to the Volume Group.
  • If the snapshot capacity usage rate is high (around 90%), replication may be stopped.
  • The replica can use the snapshot feature after the replication policy is deleted.

Edit Snapshot Schedule

You can modify the snapshot auto-creation interval. To modify the snapshot schedule, follow the steps below.

  1. All Services > Storage > Block Storage(BM) menu, click it. Navigate to the Service Home page of Block Storage(BM).
  2. On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
  3. Block Storage(BM) List on the page, click the resource to edit the snapshot schedule. Block Storage(BM) Details page will be opened.
  4. Click the Snapshot Schedule Edit button. The Snapshot Schedule Edit popup opens.
  5. Set the snapshot auto generation status and generation interval, and click the Confirm button.
    • Creation Cycle based, if you want to automatically create snapshots, select Auto Creation as Enabled.
    • Generation cycle can be selected daily, hourly, or weekly, day of week, hourly.
Caution
Snapshots can be created up to a maximum of 1,023 (with up to 128 automatically created via schedule), and if the maximum number is exceeded, no more snapshots can be created.
Note
  • The snapshot schedule is based on Asia/Seoul (GMT +09:00).
  • After setting snapshot capacity, schedule registration is possible.
  • When setting a snapshot schedule, it cannot be added to the Volume Group.

Modify IOPS

You can modify the IOPS value. To modify the IOPS value, follow the steps below.

  1. All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
  2. Click the Block Storage(BM) menu on the Service Home page. Navigate to the Block Storage(BM) list page.
  3. Click the resource to modify the IOPS value on the Block Storage(BM) List page. It moves to the Block Storage(BM) Details page.
  4. Click the Edit button of IOPS. The IOPS Edit popup opens.
  5. After entering the IOPS value to change, click the Confirm button.
    • IOPS value can be entered between 3,000 and 16,000.
Reference
  • The IOPS value can be modified after the initial server attach.
  • In the case of a recovery copy, the IOPS value cannot be modified.

Throughput Edit

You can modify the Throughput speed. To modify the Throughput speed, follow the steps below.

  1. All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
  2. Click the Block Storage(BM) menu on the Service Home page. Navigate to the Block Storage(BM) List page.
  3. Click the resource to modify the Throughput speed on the Block Storage(BM) List page. Block Storage(BM) Details page will be opened.
  4. Click the Edit button of Throughput. Throughput Edit popup window opens.
  5. After entering the Throughput speed to change, click the Confirm button.
    • Throughput speed can be set to a value between 125 and 1,000.
Reference
  • Throughput speed can be modified after the initial server attach.
  • In the case of a recovery copy, the Throughput speed cannot be modified.

Edit Connection Server

Bare Metal Server, you can connect or disconnect the Multi Node GPU Cluster. To modify the connected server, follow the steps below.

  1. All Services > Storage > Block Storage(BM) Click the menu. Go to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Block Storage(BM) menu. Go to the Block Storage(BM) list page.
  3. On the Block Storage(BM) List page, click the resource to edit the connected server. You will be taken to the Block Storage(BM) Details page.
  4. If you want to add a connection server, click the Add button in the Connection Server item. The Add Connection Server popup window will open.
  5. After selecting the server you want to connect to, click the Confirm button.
  6. If you want to disconnect the server, click the Disconnect button in the Connection Server item.
    • Be sure to connect to the server and perform the disconnect operation (Umount, Disk Offline) before disconnecting.
Caution
  • Connect to the server and be sure to perform disconnect operations (Umount, Disk Offline) before releasing the connected server. If you release without OS operations, a status error (Hang) may occur on the connected server. For detailed information on server disconnect, see Disconnect Server.
Reference
  • You can connect up to 8 Bare Metal Servers created in the same location as Block Storage.
  • There is no limit on the number of volume connections for Bare Metal Server.
  • When adding a connected server, you can use it after performing connection tasks (Mount, Disk Online) on the server. For detailed information about server connection, refer to Server Connection.
  • Please connect to the server and be sure to perform disconnect operations (Umount, Disk Offline) before releasing the connected server. If you release without OS operations, a status error (Hang) may occur on the connected server. For detailed information on server disconnect, refer to Disconnect Server.
  • If the replica’s replication policy is stopped or deleted, the connected server can be modified.

Block Storage(BM) Cancel

You can reduce operating costs by terminating unused Block Storage (BM). However, if you terminate the service, the running service may be immediately stopped, so you should consider the impact of service interruption sufficiently before proceeding with the termination.

Caution
  • After termination, you cannot recover data, so be careful.
  • If there is a connected server, you can cancel after removing all connected resources.
  • The volume can be terminated only when it is in Available or Error state.
  • If you are using a replication policy, you can cancel it after deleting the replication policy from the connected replica.
  • If a Volume Group is being used, you can cancel it after disconnecting the connected Volume Group.
  • If there is a backup of the original, you can delete the backup and then cancel.

To cancel Block Storage, follow the steps below.

  1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
  2. Click the Block Storage(BM) menu on the Service Home page. Navigate to the Block Storage(BM) List page.
  3. On the Block Storage(BM) List page, select the resource to terminate, and click the Terminate Service button.
  4. When termination is complete, check whether the resource has been terminated on the Block Storage(BM) List page.

3.1.2.1 - Connecting to a Server

When using a volume on a server, a connection or disconnection operation is required.
When using a volume on a server, you need to perform a connection or disconnection operation. After adding a connection server on the Block Storage(BM) details page, access the server and perform Multi Path settings and connection operations (Mount, Disk Online). After completing the use, perform disconnection operations (Umount, Disk Offline) and remove the connection server.

Configuring Multi Path

Before using a volume on a connection server, you need to configure Multi Path. Follow the procedure below.

Note
If you do not configure Multi Path, it may affect the service due to maintenance, failures, etc.

Linux Operating System

  1. Click the All Services > Storage > Block Storage(BM) menu. The Block Storage(BM) Service Home page will be displayed.

  2. On the Service Home page, click the Block Storage(BM) menu. The Block Storage(BM) list page will be displayed.

  3. On the Block Storage(BM) list page, click the resource you want to set up Multi Path for. The Block Storage(BM) details page will be displayed.

  4. In the Connected Server section, check the server and access it. Follow the guide below to configure Multi Path.

    • Device confirmation

      1. The created volume can be confirmed using the fdisk -l command.
    • DM-Multipath application confirmation

      1. The Linux system automatically applies Multi Path during the volume recognition process, and you can confirm it using the multipath –ll command.
      2. The volume with Multi Path applied uses a Multipath device name in the format /dev/mapper/#####, not /dev/sd#, and can be confirmed using the fdisk –l command.
    • iSCSI replacement timeout value setting

      1. Set the replacement timeout when connecting to iSCSI.
      # vi /etc/iscsi/iscsid.conf
      node.session.timeo.replacement_timeout = 5
      (change the default value of 120 to 5)
      
      1. After changing the above content, restart the iSCSI service
      # systemctl restart iscsid
      

Windows Operating System

  1. Click the All Services > Storage > Block Storage(BM) menu. The Block Storage(BM) Service Home page will be displayed.

  2. On the Service Home page, click the Block Storage(BM) menu. The Block Storage(BM) list page will be displayed.

  3. On the Block Storage(BM) list page, click the resource you want to set up Multi Path for. The Block Storage(BM) details page will be displayed.

  4. In the Connected Server section, check the server and access it. Follow the guide below to configure Multi Path.

    • Device confirmation

      1. Click the Start > Server Manager menu to run Server Manager.
      2. Click Server Manager > File and Storage Services > Volumes > Disks to confirm the iscsi device.
      3. Before setting up Multi Path, one device appears as multiple devices for each path.
    • MPIO installation (Reboot required)

      1. Click Server Manager > Dashboard > Add roles and features.

      2. The Add Roles and Features Wizard popup window will open. Click the Next button.

      3. On the Select installation type page, select Role-based or feature-based installation and click the Next button.

      4. On the Select destination server page, the current server will be automatically searched. Confirm the content and click the Next button.

      5. On the Select features page, select Features on the left menu and check Multipath I/O. Then, click the Next button.

        MultiPath

      6. On the Confirm installation selections page, check Restart the destination server automatically if required. If a popup window opens, click Yes and then click the Install button.

      7. The installation will start, and the server will automatically reboot.

      8. After reconnecting to the server, the installation will be complete. Click the Close button to close the Wizard popup window.

      9. Click Server Manager > Dashboard > Tools > MPIO.

        MultiPath

      10. On the Discover Multi-Paths tab, check Add support for iSCSI devices and click the Add button.

        • If a message is displayed, reboot the server again.
      11. After the reboot is complete, you can confirm NETAPP Devices in MPIO devices.

        MultiPath

      12. Run diskmgmt.msc in the Windows execution window (command prompt) to open the Disk Management popup window.

        • You can confirm that MPIO is applied through the properties of the volume created in the Block Storage(BM) service.
          MultiPath

Connecting to a Server (Mount, Disk Online)

To use a volume added to a connection server, you need to access the server and perform connection operations (Mount, Disk Online). Follow the procedure below.

Linux Operating System

Server Connection Example Configuration
  • Server OS: LINUX
  • Mount location: /data
  • Volume capacity: 24 GB
  • File system: ext3, ext4, xfs, etc.
  • Additional allocated disk: /dev/vdb
  1. Click the All Services > Storage > Block Storage(BM) menu. The Block Storage(BM) Service Home page will be displayed.

  2. On the Service Home page, click the Block Storage(BM) menu. The Block Storage(BM) list page will be displayed.

  3. On the Block Storage(BM) list page, click the resource you want to connect to the server. The Block Storage(BM) details page will be displayed.

  4. In the Connected Server section, check the server and access it. Follow the guide below to connect (Mount) the volume.

    • Switch to root privileges

      $ sudo -i
      
    • Confirm the disk

      # lsblk
      NAME    MAJ:MIN  RM   SIZE RO TYPE MOUNTPOINT
      vda       252:0   0    24G  0 disk
      ├─vda1    252:1   0  23.9G  0 part [SWAP]
      └─vda14   252:14  0     4M  0 part /
      └─vda15   252:15  0   106M  0 part /boot/efi
      vdb       252:16  0    24G  0 disk
      
    • Create a partition

      # fdisk /dev/vdb
      Command (m for help): n
      
      Partition type:
         p   primary (0 primary, 0 extended, 4 free)
         e   extended
      Select (default p): p
      Partition number (1-4, default 1): 1
      First sector (2048-50331646, default 2048):
      Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-50331646, default 50331646):
      
      Created a new partition 1 of type 'Linux' and of size 24 GiB.
      
      Command (m for help): w
      The partition table has been altered!
      Calling ioctl() to re-read partition table.
      Syncing disks.
      
    • Set the partition format (e.g., ext4)

      # lsblk
      NAME    MAJ:MIN  RM   SIZE RO TYPE MOUNTPOINT
      vda       252:0   0    24G  0 disk
      ├─vda1    252:1   0  23.9G  0 part [SWAP]
      └─vda14   252:14  0     4M  0 part /
      └─vda15   252:15  0   106M  0 part /boot/efi
      vdb       252:16  0    24G  0 disk
      └─vdb1    252:17  0    24G  0 part
      
      # mkfs.ext4 /dev/vdb1
      mke2fs 1.46.5 (30-Dec-2021)
      ...
      Writing superblocks and filesystem accounting information: done
      
    • Mount the volume

      # mkdir /data
      
      # mount /dev/vdb1 /data
      
      # lsblk
      NAME    MAJ:MIN  RM   SIZE RO TYPE MOUNTPOINT
      vda       252:0   0    24G  0 disk
      ├─vda1    252:1   0  23.9G  0 part [SWAP]
      └─vda14   252:14  0     4M  0 part /
      └─vda15   252:15  0   106M  0 part /boot/efi
      vdb       252:16  0    24G  0 disk
      └─vdb1    252:17  0    24G  0 part /data
      
      # vi /etc/fstab
      (add) /dev/vdb1     /data       ext4     defaults   0 0
      
ItemDescription
cat /etc/fstabLinux system file containing filesystem information. Used when the server starts.
df -hConfirms the total disk usage of the mounted filesystems in the Linux system.
fdisk -lConfirms partition information.
  • Physical disks are displayed with letters such as a, b, c, etc. (e.g., /dev/sda, /dev/sdb, /dev/sdc)
  • Disk partitions are displayed with numbers such as 1, 2, 3, etc. (e.g., /dev/sda1, /dev/sda2, /dev/sda3)
Table. Mount Command Reference
CommandDescription
mDisplays the usage of the fdisk command.
nCreates a new partition.
pDisplays the changed partition information.
tChanges the system ID of the partition.
wSaves the partition information and exits the fdisk settings.
Table. Partition Creation Command (fdisk) Reference

Windows Operating System

  1. Click the All Services > Storage > Block Storage(BM) menu. The Block Storage(BM) Service Home page will be displayed.

  2. On the Service Home page, click the Block Storage(BM) menu. The Block Storage(BM) list page will be displayed.

  3. On the Block Storage(BM) list page, click the resource you want to connect to the server. The Block Storage(BM) details page will be displayed.

  4. In the Connected Server section, check the server and access it. Follow the guide below to connect (Disk Online) the volume.

    • Right-click the Windows Start icon and run Computer Management.

    • In the Computer Management tree structure, select Storage > Disk Management.

    • Confirm the disk

    Mount
    • Set the disk to Online
    Mount
    • Initialize the disk
    Mount
    Mount
    • Format the partition
    Mount
    Mount
    Mount
    • Confirm the volume
    Mount

Disconnecting from the Server (Umount, Disk Offline)

After disconnecting from the server (Umount, Disk Offline) and performing the disconnection work, you must disconnect the connected server from the Console. Follow the procedure below.

Caution
If you disconnect the connected server from the Console without disconnecting from the server (Umount, Disk Offline), a server status error (Hang) may occur. Be sure to perform the OS task first.

Linux Operating System

  1. Click All Services > Storage > Block Storage (BM) menu. Move to the Service Home page of Block Storage (BM).

  2. Click the Block Storage (BM) menu on the Service Home page. Move to the Block Storage (BM) list page.

  3. Click the resource to be disconnected from the server on the Block Storage (BM) list page. Move to the Block Storage (BM) details page.

  4. Check the server in the Connected Server item and access it. Follow the guide below to disconnect the volume (Umount).

    • Volume Umount
      # umount /dev/vdb1 /data
      
      # lsblk
      NAME    MAJ:MIN  RM   SIZE RO TYPE MOUNTPOINT
      vda       252:0   0    24G  0 disk
      ├─vda1    252:1   0  23.9G  0 part [SWAP]
      └─vda14   252:14  0     4M  0 part /
      └─vda15   252:15  0   106M  0 part /boot/efi
      vdb       252:16  0    24G  0 disk
      └─vdb1    252:17  0    24G  0 part
      
      # vi /etc/fstab
      (delete) /dev/vdb1     /data       ext4     defaults   0 0
      

Windows Operating System

  1. Click All Services > Storage > Block Storage (BM) menu. Move to the Service Home page of Block Storage (BM).

  2. Click the Block Storage (BM) menu on the Service Home page. Move to the Block Storage (BM) list page.

  3. Click the resource to be disconnected from the server on the Block Storage (BM) list page. Move to the Block Storage (BM) details page.

  4. Check the server in the Connected Server item and access it. Follow the guide below to disconnect the volume (Disk Offline).

    • Right-click the Windows Start icon and run Computer Management

    • Select Storage > Disk Management in the Computer Management tree structure

    • Right-click the disk to be removed and run Offline

    Umount
    • Check the disk status
    Umount

3.1.2.2 - Using Snapshots

You can create, delete, or recover snapshots of the generated Block Storage (BM). You can perform actions on the Block Storage (BM) Details page and the Snapshot List page.

Create Snapshot

You can create a snapshot at the point in time you want. To create a snapshot, follow the steps below.

  1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
  2. Click the Block Storage(BM) menu on the Service Home page. You will be taken to the Block Storage(BM) List page.
  3. Block Storage(BM) List page, click the resource to create a snapshot. Navigate to the Block Storage(BM) Details page.
  4. Snapshot Capacity Check the setting status of the item.
    • Snapshots can only be created when storage space is secured by setting the snapshot capacity.
    • For more details, please refer to Modify Snapshot Capacity.
  5. Click the Create Snapshot button. Create Snapshot popup window opens.
  6. Confirm Click the button. Creates a snapshot of the current point in time.
  7. Click the Snapshot List page. Go to the Block Storage(BM) Snapshot list page.
  8. Check the generated snapshot.
Caution
  • If the maximum number of snapshots or the snapshot space threshold (around 90%) is exceeded, older snapshots will be deleted.
  • If the usage rate within snapshot capacity is high (around 90%), replication may be stopped.
  • If there is a volume in the Volume Group with snapshot capacity not set, you cannot create a snapshot. Set the snapshot capacity for all volumes first.
  • Snapshots can be created up to a maximum of 1,023 (the automatic creation count via schedule is up to 128), and if the maximum creation count is exceeded, no more snapshots can be created.
Reference
  • The snapshot creation date and time is based on Asia/Seoul (GMT +09:00).
  • If you want to automatically create snapshots via a schedule, set the snapshot schedule on the Block Storage(BM) Details page.
  • For detailed information about snapshot schedules, see Edit Snapshot Schedule.
  • The replica can use the snapshot feature after the replication policy is deleted.

Recover Snapshot

Block Storage(BM) volumes can be restored from a snapshot. To perform snapshot recovery, follow the steps below.

  1. Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Block Storage(BM) menu. Navigate to the Block Storage(BM) list page.
  3. Block Storage(BM) List On the page, click the resource to restore from the snapshot. Block Storage(BM) Details Navigate to the page.
  4. If there is a server added in the Connection Server item, after connecting to the server, perform the disconnect operation (Umount, Disk Offline).
  5. Snapshot List Click the page. Block Storage(BM) Snapshot List Go to the page.
  6. After checking the Snapshot Name and Creation Date/Time, click the More button of the snapshot you want to restore.
  7. Recovery Click the button. The snapshot recovery popup window opens.
  8. Snapshot Name and Creation Date and Time after checking, click the Confirm button. Recover the Block Storage volume as a snapshot.
  9. Click the Details button. You will be taken to the Block Storage (BM) Details page.
  10. Connection Server If there is a server added in the item, after connecting to the server, perform the connection tasks (Mount, Disk Online).
Caution
  • Snapshot recovery must be performed while disconnected (Umount, Disk Offline) on all connected servers, and the recovered volume can be used after reconnecting (Mount, Disk Online).
  • After the snapshot recovery is completed, all snapshots created after the snapshot used for recovery will be deleted.
  • When restoring a snapshot, the volume is restored to that point.
  • If you are using Volume Group (BM), you can perform snapshot recovery from the detail page of Volume Group (BM).

Create a recovery copy

Block Storage(BM) volume’s snapshot can be used to create a recovery copy. To create a snapshot recovery copy, follow the steps below.

  1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
  2. Click the Block Storage(BM) menu on the Service Home page. Navigate to the Block Storage(BM) List page.
  3. On the Block Storage(BM) List page, click the resource to restore from a snapshot. You will be taken to the Block Storage(BM) Details page.
  4. Connection Server If there is a server added in the item, after connecting to the server, perform the disconnect operation (Umount, Disk Offline).
  5. Snapshot List page, click it. Block Storage(BM) Snapshot List page, go to it.
  6. After confirming the Snapshot name and Creation date/time, click the More button of the snapshot you want to create a recovery copy for.
  7. Click the Create Recovery button. The snapshot recovery creation popup opens.
  8. After entering the Recovery volume name, click the Confirm button. A popup notifying the creation of the recovery copy opens.
  9. Click the Confirm button. The recovery copy creation request is completed.
Caution
  • Only one backup can be created per original.
  • A recovery copy is a separate volume created with the same capacity as the original, and incurs additional costs.
  • If you are using Volume Group (BM), you can create a backup on the detail page of Volume Group (BM).

Delete Snapshot

You can select a snapshot to delete. To delete a snapshot, follow the steps below.

  1. All Services > Storage > Block Storage(BM) Click the menu. Navigate to the Service Home page of Block Storage(BM).
  2. Service Home on the page, click the Block Storage(BM) menu. Go to the Block Storage(BM) list page.
  3. Block Storage(BM) List page, click the resource to delete the snapshot. Block Storage(BM) Details page will be opened.
  4. Click Snapshot List. Go to the Block Storage (BM) Snapshot List page.
  5. After checking the Snapshot Name and Creation Date/Time, click the More button of the snapshot you want to delete.
  6. Click the Delete button. The snapshot will be removed from the Snapshot List page.
Reference
  • Snapshots that contain snapmirror in the snapshot name cannot be deleted. snapmirror is included in the snapshot name when a replication is created.
  • If you are using Volume Group (BM), you can delete snapshots from the detail page of Volume Group (BM).

3.1.2.3 - Using Replication

You can create a replica in a different location of the created Block Storage(BM) and synchronize it periodically, and you can perform tasks on the Block Storage(BM) details page and the replication page.

Reference
  • The kr-south region does not provide Block Storage(BM) replication feature.

Create a copy

You can create a replica volume in a different location. To create a replica volume, follow these steps.

  1. All Services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Block Storage(BM) menu. It moves to the Block Storage(BM) list page.
  3. Block Storage(BM) list page, click on the resource to create a replica. It moves to the Block Storage(BM) details page.
  4. Snapshot capacity item’s setting status should be checked.
  • Replication creation is only possible when storage space is secured through snapshot capacity setting.
  • For more detailed information, please refer to Modifying snapshot capacity.
  1. Replicate Create button will be clicked. Replicate Create popup window will be opened.
  2. Replication location and replication volume name, replication cycle should be entered and the confirm button should be clicked. It creates a replica with the same disk type.
  • Replication location: Select a location different from the original Block Storage(BM) volume.
  • Replica Volume Name: It should start with English and use English, numbers, and special characters(-) to input 3-28 characters.
  • Replication cycle: Choose from 5 minutes, 1 hour, daily, weekly, or monthly. Replication will be performed according to the selected cycle.
  • Daily: every day 23:59:00
  • Every week: every Sunday 23:59:00
  • Every month: every month 1st 23:59:00
  1. Replication page will be clicked. It moves to the Replication page.
  2. Check the replication information.
  • When selecting the volume name of the original or replica, it moves to the Block Storage(BM) details page of the volume.
Note
  • When replicating, a replica with the same disk type is created.
  • After setting the snapshot capacity, a replica can be created, and the disk type of the created replica is the same as the original.
  • In cases where the snapshot capacity usage rate is high (around 90%), replication may be stopped.
  • After setting the snapshot capacity, the volume added to the Volume Group can be replicated in units of Group on the Volume Group page.
  • One replica can be created per volume, and additional data transfer fees apply when replicating across regions.
  • The replicated created volume cannot be added to the Volume Group.
  • If you are using Volume Group, you can check the replication information from Volume Group (BM).

Modify replication policy

You can change the replication status through replication policy modification.

Caution
During replication, you cannot modify the replication cycle and replication policy.

To modify the replication policy, follow the following procedure.

  1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Block Storage(BM) menu. It moves to the Block Storage(BM) list page.
  3. Block Storage(BM) list page, click the resource to modify the replication policy. It moves to the Block Storage(BM) details page.
  4. Replication page is clicked. It moves to the Block Storage(BM) replication page.
  5. Replication Policy’s Edit button should be clicked. Replication Policy Edit popup window will be opened.
  • Usage: performs replication. Paused can be modified to Usage.
  • Temporary suspension: temporarily suspends replication. If in use, it can be modified to temporary suspension.
  • Delete: It deletes the replication. In case of pause, it can be modified to delete, and after deletion, replication cannot be used again.
  1. Block Storage(BM) replication page, check the modified replication policy.
Caution
  • Be aware of the following when deleting a policy.
  • After deleting the policy, the replica is not converted to the original and cannot create a replica.
  • After deleting the policy, you cannot connect to the existing replica, and you can only create a new replica.
  • Data stored only in replicas after temporary suspension will be deleted when replication is used again.
  • When using the replication policy, the replica is in a read-only state and data modification is not possible. Please use replication after unmounting from all connected resources
  • The replication policy can be mounted from the connection server only when it is deleted or in a paused state.

Modify replication cycle

You can change the synchronization cycle between the original and the copy through replication cycle modification.

Caution
During replication, you cannot modify the replication cycle and replication policy.

To modify the replication cycle, follow the following procedure.

  1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Block Storage(BM) menu. It moves to the Block Storage(BM) list page.
  3. Block Storage(BM) list page, click the resource to modify the replication cycle. It moves to the Block Storage(BM) details page.
  4. Replication page will be clicked. It moves to the Block Storage(BM) replication page.
  5. Replication Cycle’s Edit button should be clicked. Replication Cycle Edit popup window will be opened.
  • Replication cycle: Select from 5 minutes, 1 hour, daily, weekly, or monthly. Replication will be performed according to the selected cycle.
  • Daily: every day 23:59:00
  • Every week: every Sunday 23:59:00
  • Every month: every month 1st 23:59:00
  1. Block Storage(BM) replication page where you can check the modified replication cycle.

3.1.2.4 - Using Volume Group

Volume Group(BM) service allows you to create a group of up to 16 Block Storage(BM) volumes to create snapshots and replicas at a consistent point in time.
The user can enter the necessary information of the Volume Group (BM) through the Samsung Cloud Platform Console and select detailed options to create the corresponding service.

Creating Volume Group (BM)

You can create and use the Volume Group(BM) service on the Samsung Cloud Platform Console.

To create Block Storage, follow the next procedure.

  1. All services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
  2. Volume Group(BM) menu should be clicked. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) page, click the Volume Group(BM) creation button. It moves to the Volume Group(BM) creation page.
    Classification
    Mandatory
    Detailed Description
    Volume Group nameRequiredVolume Group name
    • Starts with English and uses English, numbers, and special characters (-) to input 3-28 characters
    • Cannot be modified after service creation
    Target VolumeRequiredAdd target volume to Volume Group
    • Add button is clicked, and then select the target volume in the target add popup
    • Target volume basis
      • Snapshot capacity: Setting
      • Snapshot automatic creation, creation cycle: Not used
      • Replication: Not used
      • Up to 16 can be added
    Table. Volume Group(BM) Service Information Input Items
  4. Complete button을 클릭하세요 -> 4. Complete button should be translated as: 4. Click the Complete button. So the final translation is: 4. Click the Complete button.
  • Once creation is complete, check the created resource from the Volume Group(BM) list page.
Reference
  • When adding the target volume, you can add the volume corresponding to the following to the Volume Group (BM).
  • Snapshot capacity: setting
  • Snapshot automatic creation, creation cycle: not used
  • Replication: Not used
  • The target volume can be added up to a maximum of 16.

Volume Group(BM) detailed information check

Volume Group(BM) service allows you to check and modify the entire resource list and detailed information. The Volume Group(BM) details page consists of detailed information, snapshot list, replication, job history tabs.

Volume Group(BM) service’s detailed information can be checked by following the next procedure.

  1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click on the resource to check the detailed information. It moves to the Volume Group(BM) details page.
  • Volume Group(BM) details page displays status information and additional feature information, and consists of details, snapshot list, replication, tags, job history tabs.
    ClassificationDetailed Description
    Volume Group statusVolume Group’s status
    • Creating: being created
    • Available: creation completed, server connection available
    • Deleting: service termination in progress
    • Editing: settings being changed
    • Error Deleting: abnormal state during deletion
    • Error: abnormal state during creation
    Replication creationCreate a replica in a different location
    Creating a snapshotCreate a snapshot at a specific point in time
    Service CancellationButton to cancel the service
    Table. Status Information and Additional Functions
Reference
For a recovery file, the snapshot list, replication tabs are not displayed.

Detailed Information

Volume Group(BM) list page where you can check the detailed information of the selected resource and modify the information if necessary.

ClassificationDetailed Description
ServiceService Name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In Volume Group(BM), it means Volume Group SRN
Resource NameResource Name
  • In Volume Group(BM), it means Volume Group name
Resource IDService’s unique resource ID
CreatorThe user who created the service
Creation TimeThe time when the service was created
EditorUser who modified the service
Revision TimeThe time when the service was revised
Volume Group nameVolume Group Name
DivisionDivision of original related to replication
Storage Volume Group nameStorage device internal Volume Group name
  • Distinguishing information of the Volume Group used for analysis when failures and issues occur
Snapshot ScheduleSnapshot automatic generation cycle
  • Snapshot capacity setting and schedule registration are possible
  • If snapshot schedule setting is required, click the modify button
BackupVolume Group’s backup name
  • Displayed when a backup exists
  • Clicking the name moves to the detailed page of the backup
Target VolumeVolume Group added Block Storage(BM)
  • Volume Name: Volume name
  • Disk Type: Disk type of the volume
  • Capacity: Capacity of the volume
  • Snapshot Capacity: Capacity of the snapshot storage space set for the volume
Table. Detailed information items of Volume Group(BM)

Snapshot list

Volume Group(BM) Resource List page where you can check the snapshot of the selected resource.

ClassificationDetailed Description
Snapshot NameSnapshot Name
Creation TimeSnapshot Creation Time
Additional Features > MoreSnapshot Management Button
  • Restore: Volume Restore with Snapshot
  • Create Copy: Create Copy from Snapshot
Table. Snapshot list tab detailed information items
Caution
  • When creating a snapshot in the Volume Group, a snapshot is created in the Block Storage (BM).
  • Volume Group snapshot is used when managing the target volume’s snapshot capacity and count.
  • If the maximum number of snapshot creations or the threshold of snapshot space (around 90%) is exceeded, old snapshots will be deleted from oldest.
  • If the snapshot capacity usage rate is high (around 90%), replication may be stopped.
  • Snapshots can be created up to a maximum of 1,023 (the maximum number of automatic creations through scheduling is 128), and if the maximum number of creations is exceeded, no more snapshots can be created.
  • Snapshot recovery must be performed in a state where all connected servers are disconnected (Umount, Disk Offline), and the recovered volume can be used after reconnection (Mount, Disk Online).
Reference
  • The snapshot creation time is based on Asia/Seoul (GMT +09:00) standard.
  • When using replication, the snapmirror file cannot be deleted.
  • When using Volume Group, set the snapshot schedule on the Volume Group (BM) detailed information screen. The created snapshot can be checked in the Block Storage (BM) snapshot list.

Replication

Volume Group(BM) Resource List page where you can check the replication information of the selected resource.

ClassificationDetailed Description
Replication PolicyReplication policy set by the user
Replication CycleThe replication cycle of the original set by the user
Replication StatusReplication progress status according to policy settings
Volume InformationVolume information of the original and replica
  • Classification: Classification of whether it is a replica-related original
  • Volume Group Name: Volume Group name of the original or replica
  • Location: Location where the volume was created
  • Authority: User authority of the volume set according to the replication policy
Table. Replication tab detailed information items
Caution
  • If the snapshot capacity usage rate is high (around 90%), replication may be stopped
Reference
  • When replicating, a replica with the same disk type is created.
  • Snapshot capacity setting and replica creation are possible after setting.
  • If you are using a Volume Group, check the replication information on the Volume Group(BM) resource list page.
  • The replica Block Storage can modify the connected server when the replication policy is paused or deleted.
  • The replica Block Storage can use the snapshot feature after the replication policy is deleted.
  • If the replication policy is paused or the replication status is completed, you can modify the policy and cycle from the replica.

Tag

Volume Group(BM) list page where you can check the tag information of the selected resource, and add, change or delete it.

ClassificationDetailed Description
Tag ListTag List
  • Check Key, Value information of the tag
  • Up to 50 tags can be added per resource
  • When entering a tag, search and select from the existing list of created Key and Value
Fig. Volume Group(BM) Tag Tab Items

Work History

Volume Group(BM) Resource List page where you can check the work history of the selected resource.

ClassificationDetailed Description
Job history listResource change history
  • Check job time, resource type, resource ID, resource name, job details, event topic, job result, and worker information
  • Click the detailed search button to search in detail
Table. Work History Tab Detailed Information Items

Volume Group(BM) Resource Management

If you need to modify the settings of the created Volume Group(BM) or add or remove target volumes, you can perform the task on the Volume Group(BM) details page.

Modifying the Snapshot Schedule

You can modify the snapshot automatic creation cycle. To modify the snapshot schedule, follow the following procedure.

  1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click the resource to modify the snapshot schedule. It moves to the Volume Group(BM) details page.
  4. Snapshot Schedule item’s Edit button should be clicked. Snapshot Schedule Edit popup window will be opened.
  5. Set the snapshot automatic creation and creation cycle, and click the confirm button.
  • Creation Cycle basis to automatically create a snapshot, in the case of Auto Creation select Yes.
  • Creation cycle can be selected as daily, hourly, or weekly, day of the week, hourly.
Caution

Volume Group snapshot is used when managing the target volume’s snapshot capacity and count

  • Snapshots can be created up to a maximum of 1,023 (the maximum number of automatic creations through scheduling is 128), and if the maximum number of creations is exceeded, no more snapshots can be created.
Reference
The snapshot schedule is based on Asia/Seoul (GMT +09:00) standard.

Modifying the target volume

You can add or detach the target volume. To modify the target volume, follow these procedures.

  1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click the resource to modify the target volume. It moves to the Volume Group(BM) detail page.
  4. If you add a target volume, click the Add button in the Target Volume item. The Add Volume popup window opens.
  • If you want to disconnect the volume, click the Disconnect button in the Target Volume section.
  1. Select the volume you want to add and then click the Confirm button.
Caution
  • Volume Group’s replication policy is in use, the target volume cannot be modified.
Reference
  • When adding the target volume, you can add the following volume to the Volume Group (BM).
  • Snapshot capacity: settings
  • Snapshot automatic creation, creation cycle: not used
  • Copy: Not used
  • The target volume can be added up to a maximum of 16.

Volume Group(BM) snapshot usage

You can create, delete a snapshot of the created Volume Group(BM), or restore it using a snapshot. You can perform tasks on the Volume Group(BM) details page and the Snapshot list page.

Creating a snapshot

The user can create a snapshot of the desired point in time. To create a snapshot, follow the following procedure.

  1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click on the resource to create a snapshot. It moves to the Volume Group(BM) details page.
  4. Create Snapshot button is clicked. Create Snapshot popup window is opened.
  5. Confirm button, click. It creates a snapshot of the current point in time.
  6. Snapshot List page, click. It moves to the Volume Group(BM) Snapshot list page.
  7. Check the generated snapshot.
Caution
  • When creating a snapshot in the Volume Group, a snapshot is also created on the connected target volume.
  • Volume Group snapshot usage, manage the snapshot capacity and number of the target volume.
  • If the maximum number of snapshot creations or the threshold of snapshot space (around 90%) is exceeded, old snapshots will be deleted from oldest.
  • If the snapshot capacity usage rate is high (around 90%), replication may be stopped.
  • A snapshot can be created up to 1,023 (the automatic creation number through the schedule is up to 128), and if the maximum creation number is exceeded, no more snapshots can be created.
Reference
  • The snapshot creation time is based on Asia/Seoul (GMT +09:00) standard.
  • Snapshot storage space will be applied according to the settings on the Block Storage(BM) details page of the target volume.
  • If you want to automatically create snapshots through a schedule, set the snapshot schedule on the Volume Group(BM) details page.
  • For more information about the snapshot schedule, please refer to Modifying the Snapshot Schedule.
  • The replica can use the snapshot feature after the replication policy is deleted.

Restoring a snapshot

Volume Group(BM)’s target volumes can all be restored as snapshots. To restore as a snapshot, follow the following procedure.

  1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click the resource to be restored with a snapshot. It moves to the Volume Group(BM) detail page.
  4. Click the Volume Name of the volume added to the Target Volume. It moves to the Block Storage(BM) Detail page.
  5. connected server item has a server added, after server connection, perform disconnect work (Umount, Disk Offline) please.
  1. Volume Group(BM) details page, click the snapshot list page. It moves to the Volume Group(BM) snapshot list page.
  2. Snapshot name and Creation time should be confirmed, then click the More button of the snapshot you want to restore.
  3. Restore button, click. Snapshot restore popup window opens.
  4. Snapshot name and Creation time are confirmed after clicking the Confirm button. The target volumes are restored as snapshots.
  5. Detailed Information button will be clicked. It will move to the Volume Group(BM) Detail page.
  6. Click the Volume Name of the volume added to Target Volume. You will be taken to the Block Storage(BM) Detail page.
  7. connected server items have been added, after server connection, perform connection work (Mount, Disk Online)
Caution
  • Snapshot recovery must be performed with all target volumes disconnected (Umount, Disk Offline) from the connected server, and the recovered volume can be used after reconnection (Mount, Disk Online).
  • After the snapshot restoration is complete, all snapshots created after the snapshot used for restoration will be deleted.

Creating a recovery version

You can create a replica from a snapshot of the target volume. To create a snapshot replica, follow these steps.

  1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click on the resource to create a backup. It moves to the Volume Group(BM) details page.
  4. Volume Group(BM) details page, click the snapshot list page. It moves to the Volume Group(BM) snapshot list page.
  5. Snapshot name and Creation time are confirmed, then click the More button of the snapshot you want to create a restore from.
  6. Restore Point Creation button should be clicked. Snapshot restore point creation popup window will be opened.
  7. Enter the Prefix and then click the Confirm button. A pop-up window announcing the creation of a backup will open.
  • The name of the backup is created with the input prefix value + original Block Storage name entered.
  1. Confirm button will be clicked. The application for creating a backup copy will be completed.
Caution
  • A backup copy can be created only one per original.
  • The recovery volume is a separate volume created with the same capacity as the original, and additional costs are incurred.

Deleting a snapshot

You can select a snapshot to delete it. To delete a snapshot, follow these steps.

  1. All Services > Storage > Block Storage(BM) menu should be clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click the resource to delete the snapshot. It moves to the Volume Group(BM) details page.
  4. Click Snapshot list. You will be taken to the Volume Group (BM) snapshot list page.
  5. Snapshot name and Creation time should be confirmed, then click the More button of the snapshot you want to delete.
  6. Delete button will be clicked. Snapshot list page will remove the snapshot.
Reference
When using replication, the snapmirror file cannot be deleted.

Volume Group(BM) replication usage

The created Volume Group(BM) can be synchronized periodically and consistently after creating replicas in other locations, and work can be done on the Volume Group(BM) details page and the replication page.

Create a copy

You can create a replica of the Volume Group and volume in a different location. To create a copy, follow the following procedure.

  1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click the resource to create a replica. It moves to the Volume Group(BM) details page.
  4. Replicate Create button should be clicked. Replicate Create popup window will be opened.
  5. Replication Location and Replication Volume Group, Replication Block Storage Name Prefix, Replication Cycle should be entered and the Confirm button should be clicked. It creates a replica Volume Group and a replica Block Storage volume with the same disk type.
  • Replication location: Select a location different from the original Volume Group (BM).
  • Replica Volume Group name: It should start with English and use English, numbers, and special characters (-) to input 3-28 characters.
  • Replica Block Storage Name Prefix: It should start with English and use English, numbers, and special characters (-) to input 3-28 characters.
  • The replica Block Storage(BM) is created with a volume name of ‘replica Block Storage name prefix + original Block Storage volume name’.
  • Replication cycle: Choose from 5 minutes, 1 hour, daily, weekly, or monthly. Replication will be performed according to the cycle below.
  • Daily: every day 23:59:00
  • Every week: every Sunday 23:59:00
  • Every month: every month 1st 23:59:00
  1. Replication page will be clicked. It moves to the Replication page.
  2. Check the replication information.
  • When the original or replica Volume Group name is selected, it moves to the Volume Group(BM) details page.
Note
  • When creating a replica in the Volume Group, a replica Volume Group and Block Storage (BM) are created.
  • The replica Block Storage has the same type as the original and disk type.
  • You can create one replica per Volume Group, and additional data transfer fees apply when replicating across regions.

Modify replication policy

You can change the replication status through replication policy modification.

Caution
During replication, you cannot modify the replication cycle and replication policy.

To modify the replication policy, follow the following procedure.

  1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click the resource to modify the replication policy. It moves to the Volume Group(BM) details page.
  4. Replication page will be clicked. It moves to the Volume Group(BM) Replication page.
  5. Replication Policy’s Edit button is clicked. Replication Policy Edit popup window is opened.
  • Usage: performs replication. Pause can be modified to Usage.
  • Temporary Suspension: temporarily suspends replication. If in use, it can be modified to temporary suspension.
  • Delete: It deletes the replication. In case of pause, it can be modified to delete, and after deletion, replication cannot be used again.
  1. Volume Group(BM) replication page where you can check the modified replication policy.
Caution
  • Note the following when deleting a policy.
  • After deleting the policy, the replica cannot be converted to the original and replication cannot be created.
  • After deleting the policy, you cannot connect to the existing replica, and you can only create a new replica.
  • Data stored only in replicas after temporary suspension will be deleted when replication is used again.
  • When using the replication policy, the replica is in a read-only state and data modification is not possible. Please use replication after unmounting all connected resources

Modify Replication Cycle

You can change the synchronization cycle between the original and the replica through replication cycle modification.

Caution
During replication, you cannot modify the replication cycle and replication policy.

To modify the replication cycle, follow the following procedure.

  1. All services > Storage > Block Storage(BM) menu is clicked. It moves to the Service Home page of Block Storage(BM).
  2. Service Home page, click the Volume Group(BM) menu. It moves to the Volume Group(BM) list page.
  3. Volume Group(BM) list page, click the resource to modify the replication cycle. It moves to the Volume Group(BM) details page.
  4. Replication page is clicked. It moves to the Volume Group(BM) replication page.
  5. Replication Cycle’s Edit button should be clicked. Replication Cycle Edit popup window will be opened.
  • Replication cycle: Choose from 5 minutes, 1 hour, daily, weekly, or monthly. Replication will be performed according to the cycle below.
  • Daily: every day 23:59:00
  • Every week: every Sunday 23:59:00
  • Every month: every month 1st 23:59:00
  1. Volume Group(BM) replication page where you can check the modified replication cycle.

Volume Group(BM) cancellation

You can cancel the unused Volume Group(BM).
Volume Group(BM) has no separate cancellation procedure, and it is automatically deleted when all volumes are disconnected from the target volume item.

Caution
After cancellation, it cannot be recovered, so please be careful.

3.1.3 - API Reference

API Reference

3.1.4 - CLI Reference

CLI Reference

3.1.5 - Release Note

Block Storage(BM)

2025.12.16
FEATURE IOPS, Throughput setting feature added
  • You can set the volume performance metrics (IOPS, Throughput) and edit them on the detail page.
    • IOPS: 3,000 ~ 16,000
    • Throughput: 125 ~ 1,000
    • No separate charges during the preview period (billing planned for the first half of 2026).
2025.10.23
FEATURE Add snapshot recovery creation feature
  • The feature to create a recovery (Recovery) using snapshots has been added.
    • A recovery copy is a separate volume created with the same capacity as the original, and additional costs are incurred.
2025.07.01
FEATURE New feature addition and monitoring integration
  • HDD Disk type has been added. When creating Block Storage (BM), HDD disk can be selected.
  • Provides an IaC environment through Terraform.
  • You can use the snapshot feature on a replica volume.
  • Cloud Monitoring has been linked.
    • You can view IOPS, Latency, and Throughput information in Cloud Monitoring.
2025.02.27
FEATURE Add replication and Volume Group feature
  • Block Storage(BM) Feature Change
    • Block Storage(BM) Replication feature that allows volumes to be replicated to another location has been added.
    • The Volume Group feature has been added, allowing you to set up to 16 Block Storage (BM) volumes as a group to create snapshots and replication at a consistent point in time.
    • For detailed information, please refer to Block Storage(BM) Overview.
  • Samsung Cloud Platform Common Feature Change
    • Account, IAM and Service Home, tags etc. reflected the common CX changes.
2024.10.01
NEW Block Storage(BM) Service Official Version Release
  • Launched a high-performance storage service suitable for handling large-scale data and database workloads.

3.2 - File Storage

3.2.1 - Overview

Service Overview

File Storage servers connected via network can easily store and share data can, making it suitable for application environments that use multiple servers.
You can select the disk type according to performance requirements, and it will automatically expand or shrink according to the user’s data size without capacity limits.

Features

  • Free volume usage: The volume capacity is automatically expanded or reduced according to data creation and deletion without user configuration. There is no cost for creating volumes, and only usage fees for stored data capacity are incurred.
  • Various disk types provided: Users can select disk type according to usage purpose. HDD that can store large data cost‑effectively, SSD that provides reduced response time and high IOPS performance, and high‑performance SSD can be used.
  • Snapshot Backup: Through the image snapshot feature, recovery of changed or deleted data is possible, and when performing disk backup, snapshots can be stored in a location different from the original. Users select the snapshot created at the point in time they wish to recover from the list and perform the recovery.
  • Replication: Creates an identical replica volume at a different location, and the user can set the data replication schedule. In case the original volume cannot be used due to failures or disasters, service can be provided through the replica volume.

Configuration Diagram

Diagram
Figure. file Storage diagram

Provided Features

File Storage provides the following features.

  • Volume Name: Users can set or edit names per volume.
  • Disk Type: You can select the disk type according to the user’s performance requirements.
    • HDD: General Volume
    • SSD: High-performance general volume
    • High-performance SSD: Performance-optimized volume that can be connected to a Multi-node GPU Cluster
    • SSD SAP_S, SSD SAP_E: SAP Account dedicated volume
  • Protocol: You can select the protocol according to the user’s OS Image.
    • NFS: Primarily used on Linux operating systems
    • CIFS: Primarily used in Windows operating systems
  • Free volume usage: Provides flexible volume size based on the amount of stored data without user capacity settings.
  • Connection Resources: Virtual Server, Bare Metal Server, Multi-node GPU Cluster can be connected and used.
  • Encryption: Regardless of disk type, all volumes are encrypted with the XTS-AES-256 algorithm.
  • Snapshot: Through the image snapshot feature, you can create snapshots immediately or schedule them.
    • Retention Count: The number of snapshots retained that are automatically created via schedule
    • Schedule: Snapshot automatic creation interval
    • Recovery: Recover the original volume to the latest snapshot, or select a snapshot at a specific point in time to create a recovery volume
  • Replication: Replicates the volume to another location, and the user can set the replication interval.
  • Disk Backup: Stores snapshots on backup-dedicated HDD storage and allows you to select the backup location.
  • VPC Endpoint connection: File Storage can be used via Private Network connection from an external network.
  • Monitoring: You can view usage, IOPS, Throughput, etc., monitoring information through the Cloud Monitoring service.
  • ServiceWatch Service Integration Provided: You can monitor data through the ServiceWatch service.

Components

You can create a volume by selecting the disk type and protocol according to the user’s service environment and performance requirements.
When using the snapshot feature, you can restore data to the point in time you want to recover.

Volume

Volume (Volume) is the basic creation unit of the File Storage service and is used as data storage space. Users select a name, disk type, and protocol (CIFS/NFS) to create a volume, then connect it to one or more servers for use.
The volume name creation rules are as follows.

  • Must start with a lowercase English letter and can be set to 3~21 characters using lowercase letters, numbers, and special character (_).

Snapshot

Snapshot (Snapshot) is an image backup at a specific point in time. Using the image snapshot feature, you can recover changed or deleted data or store the snapshot in a different location from the original when performing disk backup. The user selects the snapshot created at the point in time they want to recover from the snapshot list and performs the recovery.
The notes for using snapshots are as follows.

Reference
  • Snapshot creation time is based on Asia/Seoul (GMT +09:00).
  • Snapshots can be created up to 800, and snapshots generated by schedule are not included. (Automatic creation via schedule is up to 128)
  • By selecting the snapshot recovery button, you can restore the File Storage volume to the latest snapshot.
  • If you select a specific snapshot from the snapshot list, recovery is possible by creating a new volume based on the snapshot.
  • Automatic creation is possible through snapshot schedule settings.
  • Snapshot capacity is included in File Storage usage and incurs charges, so adjust storage capacity by setting the snapshot retention period.

Prior Service

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

Service CategoryServiceDetailed Description
ComputeVirtual ServerVirtual server optimized for cloud computing
ComputeBare Metal ServerHigh-performance physical server used without virtualization
Table. File Storage Preceding Service

3.2.1.1 - Monitoring Metrics

File Storage monitoring metrics

The table below shows the monitoring metrics of File Storage that can be checked through Cloud Monitoring. For detailed usage of Cloud Monitoring, please refer to the Cloud Monitoring guide.

Performance Item NameDescriptionUnit
Instance StatusFile Storage volume statusstatus
Volume UsedVolume Usedbytes
Volume UsageUsage Rate%
Volume TotalTotal Bytesbytes
IOPS [Total]iops(total)iops
IOPS [Read]IOPS (read)iops
IOPS [Write]IOPS (writing)iops
IOPS [Other]IOPS (etc.)iops
Latency Time [Total]Delay Time (Total)usec
Latency Time [Read]Delay time (read)usec
Latency Time [write]Delayed time (writing)usec
Latency Time [Other]Delayed time (etc.)usec
Throughput [Total]Processing amount (total)bytes/s
Throughput [Read]Throughput (Read)bytes/s
Throughput [Write]Throughput (Write)bytes/s
Throughput [Other]Throughput (etc.)bytes/s
Fig. File Storage Monitoring Metrics

3.2.1.2 - ServiceWatch Metrics

File Storage sends metrics to ServiceWatch. The metrics provided by default monitoring are data collected at a 1‑minute interval.

Reference
How to check metrics in ServiceWatch, refer to the ServiceWatch guide.

Basic Indicators

The following are the basic metrics for the File Storage namespace.

Indicator NameDetailed DescriptionUnitMeaningful Statistics
iops_readIOPS (read)-measurement at the time of query
iops_writeIOPS (write)-measurement value at the time of query
latency_readLatency (read)MicrosecondsAverage
latency_writeLatency (write)MicrosecondsAverage
throughput_readThroughput (read)Bytes/SecondMeasurement at query time
throughput_writeThroughput (write)Bytes/SecondMeasured value at query time
Table. File Storage Basic Metrics

3.2.2 - How-to guides

Users can enter the required information for File Storage through the Samsung Cloud Platform Console, select detailed options, and create the service.

Caution
  • Service fees are charged based on usage without capacity constraints.
  • The volume is allocated 100 GB by default. If you want to use more than 100 GB, please inquire about it via Support Center’s Contact Us.
  • If you add or modify company information in Cost Management’s Billing Management, the Mount name (IP information) of File Storage is automatically changed.
    • Before modifying company information, be sure to check the service impact due to changes in Mount name (IP information).
  • When company information is invited to another Organization, the Mount name (IP information) of File Storage is automatically changed.

File Storage Create

You can create and use the File Storage service from the Samsung Cloud Platform Console.

To create a File Storage, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the Create File Storage button on the Service Home page. You will be taken to the Create File Storage page.
  3. File Storage creation On the page, enter the information required to create the service, and select detailed options.
    Category
    Required
    Detailed description
    Volume NameRequiredVolume Name
    • Start with a lowercase English letter and use lowercase letters, numbers, and the special character (_) to enter 3 to 21 characters
    • Generated as ‘user input value + {6-character UUID composed of lowercase English letters and numbers}’
    • Cannot be modified after service creation
    Disk TypeRequiredSelect Disk Type
    • Disk Types
      • HDD: Standard Volume
      • High-Performance SSD: Performance-optimized volume that can be attached to a Multi-node GPU Cluster
      • SSD: High-Performance Standard Volume
      • SSD SAP_S, SSD SAP_E: Volume exclusive to SAP Account (selectable only when created with SAP Account)
    • Cannot be modified after service creation
    • Set to be identical to the original when creating the service via snapshot recovery volume creation, and cannot be modified
    ProtocolRequiredProtocol for sharing volumes over the network from the server
    • NFS: primarily used on Linux operating systems
    • CIFS: primarily used on Windows operating systems
    • Through snapshot recovery volume creation, it is set identical to the original when creating a service and cannot be modified
    Protocol > PasswordRequiredSet account password for volume access when using CIFS protocol
    • Enter 6~20 characters including letters, numbers and special characters ($ % { } [ ] " \)
    Protocol > Password ConfirmationRequiredAccount Password Confirmation
    • Re-enter the password identically
    Recovery Snapshot NameOptionalName of the recovery snapshot used when creating the volume
    • Provide the recovery snapshot name when creating a service through snapshot recovery volume creation
    Table. File Storage Service Information Input Items
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resource on the File Storage List page.
Warning
We recommend storing up to 3.5 million files per directory within the volume. If you exceed 3.5 million, severe performance degradation may occur, so separate directories and manage the number of stored files.
Reference
  • Regardless of disk type, all volumes have server-side encryption based on the XTS-AES-256 algorithm applied by default.
  • SSD SAP When using the SSD SAP disk type, if a failure occurs causing a failover, the LIF (storage mount IP) is automatically transferred. However, you cannot create new volumes on other storage.
  • Snapshot schedule can be set on the detail page.

File Storage View detailed information

File Storage service can view and edit the full resource list and detailed information. File Storage Detail page consists of Detailed Information, Snapshot List, Replication, Disk Backup, Tags, Job History tabs.

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

  1. All Services > Storage > File Storage Click the menu. Go to File Storage’s Service Home page.
  2. Click the File Storage menu on the Service Home page. Go to the File Storage list page.
  3. Click the resource to view detailed information on the File Storage list page. It navigates to the File Storage details page.
  • File Storage Details page displays status information and additional feature information, and consists of Details, Snapshot List, Replication, Disk Backup, Tags, Job History tabs.
    CategoryDetailed description
    Volume StatusRepresents the status of a volume
    • Creating: Creating
    • Creating From Snapshot: Creating a new volume from snapshot
    • Available: Creation complete, server connection possible
    • Deleting: Service termination in progress
    • Error Deleting: Abnormal state during deletion
    • Inactive: Abnormal state
    • Error: Abnormal state during creation
    • Migrating: Temporary maintenance state
    • Migrating To: Temporary maintenance state
    • Reverting: Reverting snapshot
    • Reverting Error: Snapshot revert abnormal
    Create ReplicationCreate a replica at another location
    • Backups and replicas cannot be used
    • For detailed information on creating replication, see [Create Replication](/userguide/storage/file_storage/how_to_guides/replication.md/#복제-생성하기)
    | | Create Disk Backup | Create a backup copy to store snapshots in backup-dedicated HDD Storage
    • **HDD**, **SSD** disk types can be used
    • Up to 2 backup copies can be created
    • Backup copies and replicas cannot be used
    • For more details on creating disk backups, see [Create Disk Backup](/userguide/storage/file_storage/how_to_guides/disk_backup.md/#디스크-백업-생성하기)
    | | Create Snapshot | Immediately create a snapshot at the time of creation
    • For detailed information about creating snapshots, see [Create Snapshot](/userguide/storage/file_storage/how_to_guides/snapshot.md/#스냅샧-생성하기)
    | | More > Snapshot Recovery | Recover volume with the latest snapshot in **Available** state
    • For detailed information on snapshot recovery, see [Snapshot Recovery](/userguide/storage/file_storage/how_to_guides/snapshot.md/#스냅샷-복구하기)
    | | More > File-level Restore | Enable file-level restore function within snapshots
    • For detailed information on file-level restore, see [Using File-level Restore](/userguide/storage/file_storage/how_to_guides/file_restore.md/#파일-단위-복구-사용하기) reference | | More > Disable file-level restore | Disable file-level restore function within snapshots[Disable file-level restore](/userguide/storage/file_storage/how_to_guides/file_restore.md/#파일-단위-복구-해제하기) Reference | |Service Cancellation|Button to cancel the service|
      Table. Status Information and Additional Functions
Note
Disk backup cannot be used with high-performance SSD disk types.

Detailed Information

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

CategoryDetailed description
serviceservice name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In the File Storage service, it refers to a volume SRN
Resource NameResource Name
  • In the File Storage service, it refers to the volume name
Resource IDService’s unique resource ID
CreatorUser who created the service
Creation DateTimeDate and time the service was created
Volume NameVolume Name
CategoryClassification of original status regarding duplication, disk backup
Disk typeDisk type
UsageVolume usage
ProtocolNFS, CIFS protocol for sharing volumes over the network from the server
Mount nameMount name per volume for server connection
  • ‘scp_{6-digit UUID composed of lowercase English letters and numbers}’ is created
  • The replica’s Mount name can be checked after pausing the replication policy once for the first time
EncryptionEncryption status
  • Encryption provided by default regardless of disk type
Snapshot > ScheduleSnapshot automatic creation cycle
  • Automatically create and store snapshots according to the schedule
  • If snapshot settings are needed, click the **Edit** button
  • For detailed information on snapshot settings, see [Edit Snapshot](/userguide/storage/file_storage/how_to_guides/_index.md/#스냅샷-수정하기)
| | Snapshot > Retention Count | Snapshot Retention Count
  • Number of snapshots retained that are automatically created by schedule
  • If retention count is not entered, 10 is applied automatically
  • If snapshot settings are needed, click the **Edit** button
  • For detailed information on snapshot settings, refer to [Edit Snapshot](/userguide/storage/file_storage/how_to_guides/_index.md/#스냅샷-수정하기)
| | Connected Resources | Connected resources (Bare Metal Server, Virtual Server, GPU Server)
  • **Resource Type**: Service type of the connected resource
  • **Resource Name**: Name of the connected resource
  • **IP**: IP information of the connected resource
  • **Status**: Status of the connected resource
  • NFS volumes are recommended to connect to Linux servers, CIFS volumes to Windows servers
  • Up to 300 connected resources can be added
  • When adding or removing connected resources, select the **Edit** button
  • For more details about connected resources, see [Edit Connected Resources](/userguide/storage/file_storage/how_to_guides/_index.md/#연결-자원-수정하기) reference
| | VPC Endpoint | Connected VPC Endpoint Service
  • **VPC Endpoint Name**: Name of the connected VPC Endpoint
  • **IP**: IP information of the connected VPC Endpoint
  • **Status**: Status of the connected VPC Endpoint
  • When adding or removing a VPC Endpoint, select the **Edit** button
  • For details on editing a VPC Endpoint, see [Edit VPC Endpoint](/userguide/storage/file_storage/how_to_guides/_index.md/#vpc-endpoint-수정하기)
|
Table. File Storage Detailed Information Items

Snapshot List

You can view the snapshot of the selected resource on the File Storage list page.

CategoryDetailed description
Snapshot UsageTotal Capacity of Stored Snapshots
Snapshot NameSnapshot Name
CapacitySnapshot Capacity
Creation TimeSnapshot Creation Time
StatusSnapshot status
  • Available: creation completed, can be restored
  • Creating: creating
  • Error: abnormal state
  • Deleting: deleting
  • Error Deleting: abnormal state while deleting
  • Restoring: restoring
Additional Features > MoreSnapshot Management Button
  • Create Recovery Volume: Create a recovery volume based on a snapshot
  • Delete: Delete Snapshot
Table. Snapshot List Item
Reference
  • Snapshot creation date and time is based on Asia/Seoul (GMT +09:00).
  • Snapshots can be created up to 800, and snapshots created by schedule are not included. (Automatic creation via schedule is up to 128)
  • If you are using replication or disk backup, you cannot delete the snapmirror snapshot.
  • When the snapshot recovery button is clicked, the volume will be restored to the latest snapshot in the Available state.
  • When selecting to create a recovery volume on the snapshot list page, a new volume based on the snapshot is created without modifying the existing volume.
  • The snapshot list can be viewed in the original and backup. The replica can be viewed after the policy is deleted.
  • Snapshot creation, recovery, and recovery volume creation can be used on the original.
  • When using replication or disk backup, you cannot recover with a snapshot, and you can only create a recovery volume.

Replication

You can view the replication information of the selected resource on the File Storage list page.

Notice
Only one copy can be created.
CategoryDetailed description
Replication PolicyReplication policy set by the user
Replication CycleReplication cycle of the original set by the user
Replication StatusReplication progress status according to policy settings
Volume InformationOriginal and replica volume information
  • Distinction: Distinguish whether original related to replication
  • Volume Name: Name of the original or replica volume
  • Location: Location where the volume was created
  • Permission: User permissions of the volume set according to replication policy
Table. Clone Tab Detailed Information Items
Caution
When using replication, you cannot recover with a snapshot and can only create a recovery volume. If snapshot recovery is needed, delete the replication policy and recover with a snapshot.
Note
  • When creating a clone, a replica with the same disk type is created.
  • Replication Policy, Replication Cycle can be modified when the replication status in the replica is Completed or Stopped.
  • File-level recovery of the replica can be used when the replication status is Completed or Stopped.
  • The replica’s connection server, VPC Endpoint can be modified when the replication status is stopped.
  • The snapshot-related functions of the replica can be used after the replication policy is deleted.

Disk Backup

You can view the disk backup information of the selected resource on the File Storage List page.

Notice
  • Disk type is HDD or SSD only the original can disk backup. It cannot be used on clones or high-performance SSD.
  • Up to 2 backup copies can be created.
CategoryDetailed description
Backup PolicyBackup policy set by the user
Backup CycleBackup cycle of the original set by the user
  • For detailed information on modifying the backup cycle, see [Modify Backup Cycle](/userguide/storage/file_storage/how_to_guides/dsik_backup.md/#백업-주기-수정하기)
| | Backup status | Backup progress status according to policy settings | | Backup retention count | Number of snapshots retained in the backup | | Volume Information | Original and backup volume information
  • **Classification**: Distinguish whether original related to backup
  • **Volume Name**: Name of the original or backup volume
  • **Location**: Location where the volume was created
  • **Permission**: User permissions of the volume set according to backup policy
|
Table. Disk Backup Tab Detailed Information Items
Caution
When using disk backup, you cannot recover with a snapshot and can only create a recovery volume. If snapshot recovery is needed, cancel the backup and recover with a snapshot.
Reference
  • When creating a backup, it is created as an HDD disk type regardless of the original disk type.
  • Backup Policy, Backup Frequency can be modified when the backup status in the backup set is Completed or Stopped.
  • File-level recovery of the backup can be used when the backup status is Completed or Stopped.
  • The backup copy’s connection server, VPC Endpoint can be modified when the backup status is stopped.
  • Only deletion of backup snapshots is possible.

Tag

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

CategoryDetailed description
Tag ListTag List
  • You can view the Key, Value information of tags
  • Up to 50 tags can be added per resource
  • When entering tags, search and select from the existing list of Keys and Values
Table. File Storage Tag Tab Item

Work History

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

CategoryDetailed description
Work History ListResource Change History
  • Work date and time, resource type, resource ID, resource name, work details, event topic, work result, verify worker information
Table. Work History Tab Detailed Information Items

File Storage Resource Management

If you need to modify settings of the created File Storage or add or delete connected servers, you can perform the task on the File Storage Details page.

Edit Snapshot

You can modify the snapshot schedule and retention count. To modify a snapshot, follow these steps.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. Navigate to the File Storage list page.
  3. File Storage List page, click the resource to modify the snapshot settings. Navigate to the File Storage Details page.
  4. Click the Edit button of the Snapshot item. The Snapshot Edit popup window opens.
  5. Set the Use status and Schedule, Storage Count, and click the Confirm button.
    • Schedule based, if you want to automatically create snapshots, select Use.
  • Schedule can be selected daily, hour-wise, or weekly, day of week, hour-wise.
    • Storage count: Enter a number between 1 and 128. If not entered, it defaults to 10.
Caution
  • If the number of retained items after modification is less than before, older snapshots will be deleted first.
  • If you modify it as unused, the previously created snapshot will be retained.
  • Since snapshot capacity is included in File Storage usage and incurs charges, adjust the storage capacity by setting the number of snapshots to retain.
Reference
  • Snapshot schedule is based on Asia/Seoul (GMT +09:00).

Edit Connected Resources

You can connect or disconnect resources. To modify the connected resources, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. Navigate to the File Storage list page.
  3. On the File Storage List page, click the resource to edit the linked resource. Navigate to the File Storage Details page.
  4. Click the Edit button of the Connection Resource item. The Select Connection Resource popup opens.
  5. After selecting or deselecting the resource, click the Confirm button.
    • You can select multiple resources at the same time.
Caution
Please connect to the server, perform the disconnect operation (Umount, disconnect network drive), and then disconnect the connected server. If you disconnect without OS operations, a status error (Hang) may occur on the connected server. For detailed information on disconnecting the server, refer to Disconnect Server.
Reference
  • You can connect up to 300 resources at the same location. If you need to connect more than 300, use the API.
  • When adding a connected server, you can use it after performing connection tasks (Mount, network drive connection) on the server. For detailed information about server connections, see Connect to Server.
  • The replica’s connection server can be modified when the replication state is stopped.
  • The backup copy’s connected server can be modified when the backup status is stopped.

VPC Endpoint Edit

You can connect or disconnect a VPC Endpoint.

Notice
Disk type is SSD SAP_S, you cannot modify the VPC Endpoint.

To modify the connection resource, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. Navigate to the File Storage list page.
  3. File Storage List page, click the resource to modify the VPC Endpoint connection. Navigate to the File Storage Details page.
  4. Click the Edit button of the VPC Endpoint item. The Select VPC Endpoint popup opens.
  5. After selecting or deselecting the resource, click the Confirm button.
    • You can select multiple resources at the same time.
Caution
  • After connecting to the server, be sure to perform the disconnect operation (Umount, disconnect network drive) before releasing the VPC Endpoint. If you release it without OS operations, a status error (Hang) may occur on the connected server. For detailed information on disconnecting the server, refer to Disconnect Server.
  • High-performance SSD Even with the disk type, data sharing is possible by connecting a VPC Endpoint, but be careful as it does not guarantee sufficient performance of the high-performance SSD for connecting internal VPC resources.
  • high-performance SSD Disk type, after checking the connection IP in the VPC Endpoint section, apply for the VPC Endpoint service. You can add a VPC Endpoint created based on the connection IP.
Reference
  • The VPC Endpoint of the replica can be modified when the replication status is stopped.
  • The VPC Endpoint of the backup can be modified when the backup status is stopped.

File Storage Cancel

You can cancel unused File Storage to reduce operating costs. However, if you cancel the service, the running service may be stopped immediately, so you should consider the impact of service interruption sufficiently before proceeding with the cancellation.

Caution
  • Be careful because data cannot be recovered after termination.
  • Service termination is possible for File Storage volumes without connected resources. Please terminate the service after removing all connected servers.
  • Service termination is possible for File Storage volumes without a VPC Endpoint connection. Remove all VPC Endpoints before terminating the service.
  • If the volume is in Available, Error, Inactive state, it can be terminated.
  • The original using Replication or Disk Backup can be terminated after deleting the relevant policy.
    • Replication policy: Pause > Delete
    • Backup policy: Pause > Service termination
  • The replica can be terminated after the replication policy is deleted.
  • The backup copy can be terminated after stopping the backup policy log.

To cancel File Storage, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. Navigate to the File Storage list page.
  3. File Storage List On the page, select the resource to cancel, and click the Cancel Service button.
  4. When termination is complete, check on the File Storage List page whether the resource has been terminated.

3.2.2.1 - Connecting to the Server

When using a volume on the server, connection or disconnection work is required.
In the File Storage Details page, add the connection server and then connect to the server to perform the connection work (Mount, Network Drive Connection). After use, perform the disconnection work (Umount, Network Drive Disconnection) and then remove the connection server.

Connecting to the Server (Mount, Network Drive Connection)

To use the volume added to the connection server, you must connect to the server and perform the connection work (Mount, Network Drive Connection). Follow the procedure below.

Linux Operating System (NFS)

Server Connection Example Configuration
  • Mount information: 10.10.10.10:/filestorage
  • Mount location: /data
  1. Click the All Services > Storage > File Storage menu. Move to the Service Home page of File Storage.

  2. On the Service Home page, click the File Storage menu. Move to the File Storage List page.

  3. On the File Storage List page, click the resource to be used by the connection server. Move to the File Storage Details page.

  4. Check the server in the Connection Server section and connect to it.

  5. Refer to the procedure below to connect (Mount) the volume.

    • Switch to root privileges

      $ sudo -i
      
    • Install packages (Redhat series)

      # yum install nfs-utils
      
    • Install packages (Debian series)

      # apt-get install nfs-common
      
    • Activate and run NFS-related daemons

      # systemctl enable rpcbind.service
      # systemctl start rpcbind.service
      
    • Mount the volume

      # mkdir /data
      
      # mount -t nfs -o vers=3,noresvport 10.10.10.10:/filestorage /data
      
      # vi /etc/fstab
      (Add) 10.10.10.10:/filestorage /data nfs defaults,vers=3,_netdev,noresvport 0 0
      
Note
  • Supports NFS Version 3.

Windows Operating System (CIFS)

  1. Click the All Services > Storage > File Storage menu. Move to the Service Home page of File Storage.

  2. On the Service Home page, click the File Storage menu. Move to the File Storage List page.

  3. On the File Storage List page, click the resource to be used by the connection server. Move to the File Storage Details page.

  4. Check the server in the Connection Server section and connect to it.

  5. Refer to the procedure below to connect (Network Drive Connection) the volume.

    • Right-click This PC in File Explorer and click Map Network Drive.
    • Enter the drive and folder based on the detailed information of the File Storage volume to be connected, and then click Finish.
    • To set up automatic connection at login, select Reconnect at sign-in.
  6. In the Network Credentials pop-up window, enter the account name (ID) and password, and then click OK.

    • The account name (ID) can be found on the File Storage Details page.
    • The password is the password set when Creating File Storage.
    • If you are connecting two or more volumes with the CIFS protocol set, add the Storage IP and Storage name to the hosts file and then connect.
    * Mount name
    \\10.10.10.10\filestorage1
    \\10.10.10.10\filestorage2
    
    * Hosts file contents added
    10.10.10.10 filestoragename1 #description
    10.10.10.10 filestoragename2 #description
    
    * Use the name written in the hosts file
    When connecting filestorage1: \\ filestoragename1\filestorage1
    When connecting filestorage2: \\ filestoragename2\filestorage2
    

Disconnecting from the Server (Umount, Network Drive Disconnection)

Connect to the server and perform the disconnection work (Umount, Network Drive Disconnection), and then release the connection server from the Console. Follow the procedure below.

Caution
If you release the connection server from the Console without performing the disconnection work (Umount, Network Drive Disconnection) on the server, a server status error (Hang) may occur. Be sure to perform the OS work first.

Linux Operating System (NFS)

  1. Click the All Services > Storage > File Storage menu. Move to the Service Home page of File Storage.

  2. On the Service Home page, click the File Storage menu. Move to the File Storage List page.

  3. On the File Storage List page, click the resource to be released from the connection server. Move to the File Storage Details page.

  4. Check the server information in the Connection Server section and connect to the server.

  5. Refer to the commands listed below to perform the disconnection work (Umount).

    • Umount the volume
      # umount /data
      
      # vi /etc/fstab
      (Delete) 10.10.10.10:/filestorage /data nfs defaults,vers=3,_netdev,noresvport 0 0
      

Windows Operating System (CIFS)

  1. Click the All Services > Storage > File Storage menu. Move to the Service Home page of File Storage.
  2. On the Service Home page, click the File Storage menu. Move to the File Storage List page.
  3. On the File Storage List page, click the resource to be released from the connection server. Move to the File Storage Details page.
  4. Check the server information in the Connection Server section and connect to the server.
  5. Refer to the procedure below to disconnect (Network Drive Disconnection) the volume.
    • Right-click the already connected Network Drive in File Explorer.

    • Select Disconnect Network Drive.

Note: I translated all Korean text to English while maintaining the original Markdown grammar and document format.

3.2.2.2 - Using Snapshots

You can create, delete, or restore snapshots of the created File Storage. You can perform these actions on the File Storage Details page and Snapshot List page.

Create Snapshot

You can create a snapshot of the current point in time immediately. To create a snapshot, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. File Storage List page, click the resource to create a snapshot. File Storage Details page, you will be taken there.
  4. Click the Create Snapshot button. The Create Snapshot popup window opens.
  5. Confirm Click the button. It creates a snapshot.
  6. Click the Snapshot List button. Navigate to the File Storage Snapshot List page.
  7. Check the generated snapshot.
Caution
  • Snapshot charges are included in the File Storage usage fees.
  • When using replication or disk backup, you cannot recover with a snapshot, and you can only create a recovery volume.
Reference
  • Snapshot creation time is based on Asia/Seoul (GMT +09:00).
  • Snapshots can be created up to 800, and snapshots generated by schedule are not included. (Automatic creation via schedule is up to 128)
  • If you want to automatically create snapshots via schedule, set up snapshots on the File Storage Details page.
  • For detailed information about the snapshot schedule, see Edit Snapshot.

Recover Snapshot

File Storage volume can be restored to the latest snapshot in Available state. To restore the snapshot, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. File Storage List On the page, click the resource to restore from snapshot. File Storage Details Navigate to the page.
  4. Click the Snapshot List button. It navigates to the File Storage Snapshot List page.
  5. Check the latest snapshot in Available state. The volume will be restored with that snapshot.
  6. Click the Snapshot Recovery button. The Snapshot Recovery popup opens.
  7. After checking the Snapshot name and creation date/time, click the Confirm button.
    • When recovery starts, it becomes Reverting, and when completed, it becomes Available.
Caution
  • If you want to recover using a snapshot that is not the latest snapshot, recovery is possible by creating a recovery volume.
  • When restoring, it is restored to the latest snapshot in Available state, and restoration is not possible in the following situations.
    • File Storage if the volume is not in Available state
    • If there are no recoverable snapshots
    • If the latest snapshot changes during recovery creation
    • If the latest snapshot is not in Available state

Create snapshot recovery volume

You can create a volume using a snapshot. To create a snapshot recovery volume, follow these steps.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. File Storage List page, click the resource to restore from snapshot. Move to the File Storage Details page.
  4. Click the Snapshot List button. It navigates to the File Storage Snapshot List page.
  5. After checking Snapshot Name and Creation Date/Time, click the More button of the snapshot you want to restore.
  6. Click Create recovery volume. The Create snapshot recovery volume popup opens.
  7. Click the Confirm button. You will be taken to the Create File Storage page.
  8. File Storage Creation page, enter the information required to create the service, and select detailed options.
    • Please enter the volume name and password.
    • The disk type and protocol are set the same as the original and cannot be modified.
      Category
      Required
      Detailed description
      Volume NameRequiredVolume Name
      • Start with a lowercase English letter and use lowercase letters, numbers, and the special character (_) to input 3 to 21 characters
      • Generated as ‘user input value + {6-character UUID composed of lowercase English letters and numbers}’
      • Cannot be modified after service creation
      Disk TypeRequiredSelect Disk Type
      • HDD: Standard Volume
      • SSD: High-performance Standard Volume
      • Cannot be modified after service creation
      • When creating a service via snapshot recovery volume creation, it is set identical to the original and cannot be modified
      ProtocolRequiredProtocol for sharing volumes over the network from the server
      • NFS: primarily used on Linux operating systems
      • CIFS: primarily used on Windows operating systems
      • Through snapshot recovery volume creation, it is set identical to the original when creating a service and cannot be modified
      Protocol > PasswordRequiredSet account password for volume access when using CIFS protocol
      • Enter 6~20 characters including letters, numbers and special characters (excluding $ % { } [ ] " \)
      Protocol > Password ConfirmationRequiredAccount Password Confirmation
      • Re-enter the password identically
      Recovery Snapshot NameOptionalName of the recovery snapshot used when creating a volume
      • Provide the recovery snapshot name when creating a service through snapshot recovery volume creation
      Table. File Storage Service Information Input Items
  9. 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 resource on the File Storage List page.

Delete Snapshot

You can select a snapshot to delete. To delete a snapshot, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. Click the resource to delete the snapshot on the File Storage List page. It moves to the File Storage Details page.
  4. Click the Snapshot List button. It navigates to the File Storage Snapshot List page.
  5. After checking the Snapshot name and Creation date/time, click the More button of the snapshot you want to delete.
  6. Click the Delete button. The snapshot will be removed from the Snapshot List page.
Reference
  • Snapmirror files cannot be deleted when using replication.

3.2.2.3 - Restoring Files

You can restore data at the file level using the created snapshot. This task can be performed on the File Storage Details page.

Using File-Level Restoration

You can activate the file-level restoration feature and use it. After activating the feature, connect to the server and select and restore the data. To restore files, follow these steps:

  1. Click the All Services > Storage > File Storage menu. You will be taken to the Service Home page of File Storage.

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

  3. On the File Storage List page, click the resource you want to restore. You will be taken to the File Storage Details page.

  4. Click the More button at the top right and then click the File-Level Restoration button. The File-Level Restoration popup window will open.

  5. Click the Confirm button. This will activate the file-level restoration feature.

    • While the file-level restoration is being activated, the File-Level Restoration button will be displayed as Deactivate File-Level Restoration.
  6. Check the server information in the Connected Server section and connect to the server.

  7. Refer to the following procedure to restore the data:

    • Connect to the server and check the mount name of File Storage.

    • Move to the snapshot location under the mount name.

    # cd /Mount_name/.snapshot/snapshot_name
    
    • In the snapshot location, check the file to be restored and restore it to the desired path.

Deactivating File-Level Restoration

After using the file-level restoration feature, you can deactivate it. To deactivate file-level restoration, follow these steps:

  1. Click the All Services > Storage > File Storage menu. You will be taken to the Service Home page of File Storage.
  2. On the Service Home page, click the File Storage menu. You will be taken to the File Storage List page.
  3. On the File Storage List page, click the resource you want to deactivate file-level restoration for. You will be taken to the File Storage Details page.
  4. Click the More button at the top right and then click the Deactivate File-Level Restoration button. The Deactivate File-Level Restoration popup window will open.
  5. Click the Confirm button. This will deactivate the file-level restoration feature.

3.2.2.4 - Using Disk Backup

After creating a backup of File Storage on a backup-dedicated HDD Storage, you can periodically store snapshots. You can perform tasks on the File Storage Details page and the Disk Backup page.

Caution
Backup copies created through Disk Backup can be restored using the File-level Restore feature. For detailed information about File-level Restore, see File-level Restore.
Guide
  • disk type is HDD or SSD only on the original disk backup is possible. Clones or high-performance SSD cannot be used.
  • Up to 2 backup copies can be created.

Create Disk Backup

You can create a backup volume on the original or another location’s backup-only HDD storage.

To create a backup volume, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. Go to the File Storage list page.
  3. File Storage List On the page, click the resource to create a backup. File Storage Details Navigate to the page.
  4. Create Disk Backup Click the button. Create Disk Backup The popup window opens.
  5. After entering the backup information, click the Confirm button. It creates a backup copy of the HDD disk type.
    • Backup Location: Select the location where the backup will be created.
    • Backup frequency: Choose from 1 hour, daily, weekly, monthly. Replication will be performed at the next interval.
      • Daily: Daily 23:59:00
      • Weekly: Every Sunday 23:59:00
      • Monthly: 1st of each month 23:59:00
  6. Disk Backup page click. Disk Backup page moves.
  7. Disk Backup Check the information.
  • When selecting the volume name of the original or backup, you will be taken to the File Storage Details page of that volume.
Caution
When using disk backup, you cannot recover with a snapshot and can only create a recovery volume. If snapshot recovery is needed, cancel the backup and recover with a snapshot.
Reference
  • A backup of HDD type is created regardless of the original disk type.
  • You can create 2 backups per volume, and data transfer fees are added when backing up across regions.

Modify Disk Backup Policy

You can change the backup status by modifying the backup policy. To modify the backup policy, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. Navigate to the File Storage list page.
  3. Click the resource to modify the backup policy on the File Storage List page. You will be taken to the File Storage Details page.
  4. Disk Backup tab.
  5. Click the Edit button of the Backup Policy. The Disk Backup Policy Edit popup window opens.
    • Use: Performs backup. If Paused, can be modified to Use.
    • Pause: Temporarily pauses the backup. If use is the case, it can be edited to Pause.
    • Delete: Deletes the backup. If Paused, can be changed to Delete, and after deletion the backup cannot be used again.
  6. Check the modified backup policy on the Disk Backup page of File Storage.
Reference
Backup Policy, Backup Schedule can be modified in the backup copy when the backup status is Completed or Stopped.

Modify disk backup schedule

Through modifying the backup schedule, you can change the synchronization cycle between the original and the backup. To modify the backup schedule, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. On the Service Home page, click the File Storage menu. You will be taken to the File Storage List page.
  3. Click the resource to modify the backup cycle on the File Storage List page. Navigate to the File Storage Details page.
  4. Disk Backup Click the page.
  5. Click the Edit button of Backup Cycle. The Backup Cycle Edit popup window opens.
  6. Backup frequency: select from 1 hour, daily, weekly, monthly. Create snapshots at the next interval. * Daily: Daily 23:59:00 * Every week: Every Sunday 23:59:00 * Monthly: Monthly 1st 23:59:00
  7. Check the modified backup schedule on the Disk Backup page of File Storage.
Reference
Backup Policy, Backup Frequency can be modified in the backup copy when the backup status is Completed or Stopped.

Modify disk backup retention count

You can set the number of snapshots retained in the backup. To modify the backup retention count, follow these steps.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. Click the resource to modify the backup cycle on the File Storage List page. Navigate to the File Storage Details page.
  4. Disk Backup Click the page.
  5. Click the Edit button of Backup retention count. Edit Disk Backup Retention Count popup opens.
  6. Enter the backup retention count. * The number of stored items can be set from 1 to 128.
  7. Check the modified Backup Schedule on the Disk Backup tab of the File Storage Details page.

3.2.2.5 - Using Replication

You can create a replica of File Storage at another location and synchronize it periodically. You can perform tasks on the File Storage Details page and the Replication page.

Reference
  • kr-south region does not provide File Storage replication feature.

Create Clone

You can create a replica volume at a different location. To create a replica volume, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. Click the resource to create a replica on the File Storage List page. You will be taken to the File Storage Details page.
  4. Click the Create Clone button. The Create Clone popup opens.
  5. Enter Replication Location and Replication Volume Name, Password, Replication Interval, and click the Confirm button. It creates a replica with the same disk type.
    • Replication Location: Select a location different from the original File Storage volume.
  • Clone Volume Name: Start with a lowercase English letter and use lowercase letters, numbers, and the special character (_) to enter 3 to 21 characters.
    • Password: This is the account password for accessing CIFS volumes. Enter 6 to 20 characters including letters, numbers, and special characters (excluding $%{}[]"\).
    • Replication cycle: 5 minutes, 1 hour, daily, weekly, monthly. Replication will be performed at the selected interval.
      • Daily: Daily 23:59:00
      • Weekly: Every Sunday 23:59:00
      • Monthly: 1st of each month 23:59:00
  1. Click the Clone page. Navigate to the Clone page.
  2. Check the replication information.
  • When selecting the volume name of the original or replica, you will be taken to the volume’s File Storage Details page.
Caution
When using replication, you cannot recover with a snapshot and can only create a recovery volume. If snapshot recovery is needed, delete the replication policy and recover with a snapshot.
Reference
  • When creating a replica, a replica with the same disk type and protocol is created.
  • One replica can be created per volume, and data transfer fees are added for cross-region replication.

Edit replication policy

Through modifying the replication policy, you can change the replication status. To modify the replication policy, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. On the File Storage List page, click the resource to modify the replication policy. You will be taken to the File Storage Details page.
  4. Click the Replication page. You will be taken to the File Storage Replication page.
  5. Click the Edit button of Replication Policy. The Edit Replication Policy popup window opens.
    • Use: Performs replication. If Pause, can be changed to Use.
    • Pause: Temporarily pauses replication. If use, it can be modified to Pause.
  • Delete: Deletes the replication. If Paused, it can be changed to Delete, and after deletion, replication cannot be used again.
  1. File Storage Replication on the page, please check the modified replication policy.
Caution
  • After deletion, the replica becomes the original, so you cannot replicate to the previous configuration again by modifying the replication policy.
  • Data stored only in the replica after pausing will be deleted if replication is used again.
  • When using replication policy, the replica is read only and data cannot be changed. Use replication after unmounting all connected resources.
Reference
  • If the replication policy is stopped or the replication status is completed, you can modify the policy and schedule in the replica.

Modify replication cycle

Through modifying the replication cycle, you can change the synchronization cycle between the original and the replica. To modify the replication cycle, follow the steps below.

  1. All Services > Storage > File Storage Click the menu. Navigate to the Service Home page of File Storage.
  2. Click the File Storage menu on the Service Home page. You will be taken to the File Storage list page.
  3. File Storage List on the page, click the resource to modify the replication cycle. File Storage Details navigate to the page.
  4. Replication Click the page. File Storage Replication Navigate to the page.
  5. Click the Edit button of Replication Cycle. The Replication Cycle Edit popup opens.
    • Replication Cycle: Choose from 5 minutes, 1 hour, daily, weekly, monthly. Replication will be performed at the selected interval.
      • Daily: Daily 23:59:00
      • Weekly: Every Sunday 23:59:00
      • Monthly: 1st of each month 23:59:00
  6. Check the modified Replication Cycle on the File Storage Replication page.
Reference
  • If the replication policy is stopped or the replication status is completed, you can modify the policy and schedule on the replica.

3.2.3 - API Reference

API Reference

3.2.4 - CLI Reference

CLI Reference

3.2.5 - Release Note

File Storage

2025.10.23
FEATURE Add disk type and provide ServiceWatch integration
  • SAP Account dedicated volume SSD SAP_E, SSD SAP_E disk type has been added.
    • If you use a SAP Account dedicated volume, when a failure occurs causing a failover, the LIF (storage mount IP) is automatically transferred.
    • Can only be used in SAP Account.
  • ServiceWatch service integration provision
    • You can monitor data through the ServiceWatch service.
2025.07.01
FEATURE Add disk type and disk backup feature
  • High-performance SSD disk type has been added, and can be used by connecting to a Multi-node GPU Cluster.
  • Disk Backup Through the function, you can store snapshots in backup-dedicated HDD Storage. You can select a location other than the original location.
2025.02.27
FEATURE Add disk type and replication, VPC Endpoint connection feature
  • File Storage feature change
    • SSD disk type has been added, allowing you to select the disk type according to the purpose.
    • Create the same replica volume at a different location, and you can set the data replication cycle.
    • Through a VPC Endpoint connection, you can use File Storage from an external network.
  • Samsung Cloud Platform Common Feature Change
    • Account, IAM and Service Home, tags, etc. reflected common CX changes.
2024.10.01
NEW File Storage Service Official Version Release
  • Because it automatically expands or shrinks based on usage, users can use the volume without capacity limits.
  • You can select the connection target through the access control function.
2024.07.02
NEW Beta version release
  • We have launched the File Storage service, a storage that allows multiple client servers to share files via network connection.

3.3 - Object Storage

3.3.1 - Overview

Service Overview

Object Storage is an object storage service that allows users to easily store and use their desired data, with URL-based access for very convenient data management. It enables search and retrieval of large-scale data, and provides features such as encryption and version management. It offers both Public and Private URLs, and Public URLs can be accessed even from the internet environment.

Key Features

  • S3 API Utilization: Easy and fast access from applications through Restful API, and compatible with Amazon S3, so it can be easily used in applications integrated with Amazon S3.
  • Secure Usage: Provides encryption (SSE-S3), access control, and Public/Private access features, making it suitable for safely storing user data or backup data for service recovery.
  • Cost Efficiency: Users do not need to pre-set bucket capacity, and storage space is provided with efficient pricing that charges based on actual usage.
  • Replication: Can perform replication to buckets in different locations or the same location. Multiple replication policies can be set, and if the original bucket cannot be used due to failure or disaster, the service can be provided through the replicated bucket.

Architecture Diagram

Architecture Diagram
Fig. Object Storage Architecture Diagram

Provided Features

Object Storage provides the following features.

  • Storage Management: Provides features for creating Object Storage, creating folders, deleting folders, uploading files, downloading files, and deleting files.
  • Version Management: When version management is used, all versions of uploaded files are managed. Previous files can be easily downloaded through the version list.
  • Encryption: When encryption is enabled, encryption is provided via SSE-S3 method.
  • Access Control: When access control is used, you can directly enter Public IPs allowed to access Object Storage, or select resources within the same Account allowed to access (Virtual Server, Bare Metal Server, VPC Endpoint, etc.).
  • Replication: Can perform replication to buckets in different locations or the same location.
    • Multiple replication policies can be set
  • Permission Management: By default, Private permission is provided, and Public permission and permission management features are provided.
    • Private Permission: Allows file sharing and downloading only to users who know the authentication key
    • Public Permission: Allows file sharing and downloading to anyone worldwide by accessing the file’s URL
  • Monitoring: Monitoring information such as total file count, data amount (Bytes), and HTTP Method request count can be checked through the Cloud Monitoring service.
  • ServiceWatch Service Integration: Data can be monitored through the ServiceWatch service.

Components

Authentication Key

The authentication key is an essential element that must be created in advance to use Object Storage.
The purpose of using the authentication key is as follows.

  • An authentication key is required to create and access the Object Storage service from Samsung Cloud Platform Console.
  • The API provided by Object Storage is compatible with Amazon S3, and tools using Amazon S3 can be used in the same way. In this case, authentication key input is required, and it is used as a tool to identify users with permissions. For detailed instructions on creating and checking authentication keys, see How-to guides > Create Authentication Key.

Bucket

A Bucket is the top-level folder, and all folders and files exist under the bucket. When you create Object Storage service in Samsung Cloud Platform Console, a bucket is created, and you can then upload folders or files.
Bucket naming rules are as follows:

  • Bucket names must be at least 3 characters and at most 63 characters.
  • Bucket names can only consist of lowercase letters, numbers, periods ., and hyphens -.
  • Bucket names must start with a lowercase letter or number.
  • Bucket names must not have two periods adjacent to each other.
  • Bucket names must not end with a period or hyphen.
  • Bucket names must not have periods and hyphens adjacent to each other.
  • Bucket names must not use IP address format (e.g., 192.168.x.x).
  • Bucket names cannot use the name admin.
  • Bucket names must be unique within an Account/Region.
  • Previously used bucket names can be reused after 1 hour.
Valid Bucket Name ExamplesInvalid Bucket Name Examples
Can be used with bucket names like
  • cpexamplebucket1
  • scp-example-bucket-01
  • my-scp-object-storage
Cannot be used with bucket names like
  • scp_example_bucket(includes underscore)
  • DocExampleBucket(includes uppercase)
  • -scp-example-bucket(starts with hyphen)

Folder

Folders are used to logically group files.
Folder naming rules are as follows:

  • Folder names can consist of Korean, English, numbers, and special characters.
  • Special characters that cannot be entered are as follows:
Special Characters Not Allowed in Folder Names
  • Percent sign%
  • Ampersand&
  • Question mark?
  • Exclamation mark!
  • Less than sign<, greater than sign>
  • Slash/
  • Equal sign=
  • Plus sign+
  • Dollar sign$
  • Pound sign#
  • Backtick
  • Caret^
  • Vertical bar/pipe|
  • Left curly brace{, right curly brace}
  • Left square bracket[, right square bracket]

File

A File refers to data stored in Object Storage and is the same as a regular file.
File naming rules are as follows:

  • File names can consist of Korean, English, numbers, and special characters.
  • Special characters that cannot be entered are as follows:
Special Characters Not Allowed in File Names
  • Percent sign%
  • Ampersand&
  • Question mark?
  • Exclamation mark!
  • Less than sign<, greater than sign>
  • Slash/
  • Equal sign=
  • Plus sign+
  • Dollar sign$
  • Pound sign#
  • Backslash\
  • Backtick
  • Caret^
  • Vertical bar/pipe|
  • Left curly brace{, right curly brace}
  • Left square bracket[, right square bracket]
  • Plus sign+

Folder names and file names are separated by a slash /. The following are examples of valid folder names and file names:

Examples of Mixed Folder and File Name Usage
  • 3scp-example
  • my.happy_photo-2024/20240101.jpg
  • video/2024/video01.wmv
Note
The path length including folder name, file name, and delimiter (/) is limited to 1,024 Bytes (based on UTF-8 Encoding).

URL

You can access Object Storage buckets through URLs. Public and Private URLs are provided, allowing access not only from the same Samsung Cloud Platform environment but also from external internet environments.
The URL structure is composed as follows:

URL Without Account IDURL With Account ID
https://[Representative URL]/[bucket name]/[folder name]/[file name]https://[Representative URL]/[accountId]:[bucket name]/[folder name]/[file name]
ComponentDescriptionExample
Representative URLThe Representative URL can be checked from the URL in Check Object Storage Detailed Information
  • Representative URL includes the region name.
-
accountIdaccount ID
  • If accessing files with Public Access enabled without authentication key (Access Key, Secret Key), account ID input is required; otherwise, access is possible without account ID.
c2ef8be0481d4094af3c6d046e536d25
bucket nameBucket name created by the userbucketname
folder nameFolder name where the file is locatedfolder/folder01/folder02/
file nameFile nameFilename02
Table. Object Storage URL Components

Complete URL information for files can be found in Check File Information.

Constraints

Constraints of Object Storage are as follows:

ComponentDescription
Number of creatable Object Storage servicesUp to 1,000 per region
File name length (including path)1,024 Bytes or less
File upload capacity
  • Console: 3GB or less per uploaded file
  • Upload API: 5GB for single upload operation, 5TB for Multipart
Number of files in bucketUp to 200 million
Table. Object Storage Constraints
Warning
  • It is recommended to store up to 200 million files in a bucket. If exceeding 200 million, severe performance degradation may occur, so manage the number of files.
  • When using S3 Backend Filesystem solutions (ex. s3fs, objectivefs, etc.), it is recommended not to use version management. Performance degradation may occur when using version management.
Note
When executing Amazon S3 API after changing IAM permissions, it may take up to 30 seconds.
Note
  • Korea South3 (kr-south3) region constraints
    • File upload and download functions through Samsung Cloud Platform Console are limited.
    • S3 API/CLI usage using Public URL is limited.
    • However, Private URL access through resources created in Samsung Cloud Platform Console (Virtual Server, etc.) is possible.
  • Korea South1 (kr-south1), Korea South2 (kr-south2) region constraints

Prerequisite Services

Object Storage has no prerequisite services.

3.3.1.1 - Amazon S3 Utilization Guide

Object Storage provides functions such as service creation, list retrieval, folder list retrieval, folder creation, file upload, download, etc., through the Samsung Cloud Platform Console. Additionally, these functions are also provided via an API compatible with Amazon S3. Therefore, tools that use Amazon S3 can be used in the same way.
To use Amazon S3’s utility, you need to create and verify an authentication key. For details, see Create Authentication Key.

Caution

When using the Amazon S3 utility, you must use the following version. If you use a different version, some features may be limited, so be careful.

  • SDK v2: 2.22.x or lower
  • SDK v1: 1.12.781 or less
  • CLI v2: 2.22.x or lower
  • CLI v1: 1.36.x or lower
  • SDK for JavaScript v3 : 3.728.0 or lower
  • SDK for Python(Boto3) : 1.35.x or lower

Amazon S3 API

The list of Amazon S3 APIs supported by Samsung Cloud Platform Object Storage service is as follows.

Reference
For detailed information about the Amazon S3 API, please refer to Amazon S3 API Guide.
CategoryDetailed description
head-bucketBucket Information Lookup
list-bucketsList bucket
get-bucket-versioningBucket versioning query
put-bucket-versioningModify bucket versioning
get-bucket-encryptionBucket encryption settings query
put-bucket-encryptionApply bucket encryption settings
delete-bucket-encryptionDelete bucket encryption setting
copy-objectObject copy, move, rename
put-objectCreate object
get-objectObject download
list-objectsObject list query
head-objectObject detailed view
get-object-aclObject ACL query
delete-objectDelete Object
  • If versioning is enabled, deleting a file adds a Delete Marker to the file and the Delete Marker becomes the latest version
  • If permanent deletion of a file is required, delete by specifying the version ID
list-object-versionsObject version list query
delete-objectDelete object version
presignPUT object Presigned URL issuance
get-bucket-aclBucket public permission check
create-bucketCreate bucket
delete-bucketDelete bucket
get-bucket-corsBucket CORS (Cross OriginResources) configuration check
put-bucket-corsCreate bucket CORS (PUT)
delete-bucket-corsBucket CORS Delete
put-bucket-taggingBucket tagging creation
get-bucket-taggingBucket tagging query
delete-bucket-taggingDelete bucket tagging
put-bucket-websiteCreate bucket website
get-bucket-websitebucket website view
delete-bucket-websiteDelete bucket website
get-bucket-policy-statusBucket policy status query
put-bucket-aclCreate bucket ACL
create-multipart-uploadMultipart upload creation
upload-partMultipart upload execution
complete-multipart-uploadMultipart upload completed
list-multipart-uploadsMultipart upload list
abort-multipart-uploadDelete incomplete multipart upload
put-object-taggingObject tagging creation
get-object-taggingObject tagging query
delete-object-taggingObject tagging Delete
list-objects-V2Object query (v2)
put-object-aclObject acl creation
list-partsParts lookup
put-public-access-blockPublic access block creation
get-public-access-blockpublic access block lookup
delete-public-access-blockpublic access block delete
put-bucket-lifecycleCreate bucket lifecycle (only Expiration rule can be used)
get-bucket-lifecycleBucket Lifecycle Query
delete-bucket-lifecycleBucket Lifecycle Delete
put-bucket-replicationModify bucket replication policy
  • When using replication-configuration, the following items need to be checked
    • Role: IAM SRN input required
    • Rules > Destination’s Bucket: Bucket SRN input required
    • If Rule ID is not entered, it is automatically generated with a random value
    • Rule Priority is not applied, so any entered value has no effect (can set all to 1)
    • When changing Rule ID, a new policy is created (the existing policy is deleted)
get-bucket-replicationGet bucket replication policy
delete-bucket-replicationDelete bucket replication policy
Table. List of Amazon S3 supported APIs

Amazon S3 CLI

To use Amazon S3 with the AWS CLI, please refer to Amazon S3 CLI Guide.

Amazon S3 SDK for Java

To use the Amazon S3 SDK for Java, please refer to Amazon S3 SDK Guide.

Note
For SDK guides and Rest API guides for other languages, please check the AWS official website.
Note
  • For using the Amazon S3 SDK, refer to the required region parameter below.
    • Korea West (kr-west1) case: kr-west
    • Korea South 1,2,3(kr-south1,2,3) case: kr-south
  • region parameter is for reference only, and the actual region is distinguished based on the URL.
Note
  • South Korea South 3 (kr-south3) region constraints
    • Samsung Cloud Platform Console through file upload and download functionality is limited.
    • Use of S3 API/CLI via Public URL is restricted.
    • However, access to Private URLs through resources (such as Virtual Server) created in the Samsung Cloud Platform Console is possible.
  • South Korea South1 (kr-south1), South Korea South2 (kr-south2) region constraints

3.3.1.2 - Monitoring Metrics

Object Storage Monitoring Metrics

The following table shows the monitoring metrics of Object Storage that can be checked through Cloud Monitoring. For detailed usage of Cloud Monitoring, please refer to the Cloud Monitoring guide.

Metric NameDescriptionUnit
ObjectsNumber of objects stored in a bucketcnt
Bucket UsedAmount of data stored in a bucket (bytes)bytes
Requests [Upload Avg]Average upload usage per bucketbytes
Requests [Download Avg]Average download usage per bucketbytes
Requests [Total]Total number of HTTP requests executed on a bucketcnt
Requests [Get]Number of HTTP GET requests executed on objects in a bucketcnt
Requests [Head]Number of HTTP HEAD requests executed on objects in a bucketcnt
Requests [List]Number of LIST requests executed on objects in a bucketcnt
Requests [Post]Number of HTTP POST requests executed on objects in a bucketcnt
Requests [Put]Number of HTTP PUT requests executed on objects in a bucketcnt
Requests [Delete]Number of HTTP DELETE requests executed on objects in a bucketcnt
Table. Object Storage Monitoring Metrics

3.3.1.3 - ServiceWatch metric

Object Storage sends metrics to ServiceWatch. The metrics provided by basic monitoring are data collected at a 1-minute interval.

Reference
To check metrics in ServiceWatch, refer to the ServiceWatch guide.

Basic Indicators

The following are the basic metrics for the namespace Object Storage.

Performance ItemDetailed DescriptionUnitMeaningful Statistics
Table. Object Storage Basic Metrics

3.3.2 - How-to guides

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

Creating an access key

To create and use the Object Storage service in the Samsung Cloud Platform Console, you need to generate an authentication key in advance.

Authentication key creation can be done from My Menu > My Info. > Authentication Key Management > Create Authentication Key. For more details, see IAM > Create Authentication Key.

Reference
  • The authentication key (Access Key, Secret Key) is used when authenticating Amazon S3 utility.
  • The authentication key is used not only for Object Storage, but also for authentication in OpenAPI and CLI.
  • Up to 2 authentication keys can be generated.
Caution
  • If the authentication key expires, access rights to the Object Storage service will be restricted. To ensure smooth service usage, check the authentication key’s expiration period in advance.
  • If you disable the authentication key, access rights to the Object Storage service will be restricted.

Object Storage Create

You can create and use the Object Storage service in the Samsung Cloud Platform Console.

To create Object Storage, follow the steps below.

  1. All Services > Storage > Object Storage Click the menu. Go to the Service Home page of Object Storage.
  2. Service Home on the page click the Create Object Storage button. Navigate to the Create Object Storage page.
  3. Object Storage creation Enter the information required to create the service on the page.
    Category
    Required
    Detailed description
    Bucket NameRequiredBucket name created by the user
    • Starts with a lowercase English letter or digit, and using lowercase English letters, digits, hyphen-, period., input 3~63 characters
    • Period. cannot appear consecutively two or more times.
    • Period. and hyphen- cannot be adjacent.
    • Cannot end with a period. or hyphen-.
    • IP format not allowed
    • admin name not allowed
    Table. Object Storage Required Information Input Items
Caution
In the Archive Storage service, if you create with the bucket name that is being used as the Archiving target, be careful as the configured Archiving policy will be applied.
  1. 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 Object Storage List page.

Object Storage Check Detailed Information

Object Storage service can view and edit the full resource list and detailed information.
Object Storage Details page consists of Details, Folder List, Tag tabs.

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

  1. All Services > Storage > Object Storage Click the menu. Go to the Service Home page of Object Storage.
  2. Click the Object Storage menu on the Service Home page. Navigate to the Object Storage List page.
  3. Object Storage List page, click the resource to view detailed information. Navigate to the Object Storage Details page.
    • Object Storage Details page displays status information and additional feature information, and consists of Details, Folder List, Replication, Tag tabs.
      CategoryDetailed description
      Bucket statusBucket status
      • Active: Available state
      Service cancellationButton to cancel the service
      Table. Status Information and Additional Functions
Note
Object Storage resources do not support operation history.
If necessary, please check via the Logging&Audit service. For more details, see Logging & Auddit > How-to Guides.

Detailed Information

Object Storage list page, you can view the detailed information of the selected resource and, if necessary, edit the information.

CategoryDetailed description
serviceservice name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In the Object Storage service, it refers to a bucket SRN
Resource NameResource Name
  • In Object Storage service, it refers to the bucket name
Resource IDUnique resource ID in the service
Bucket NameBucket name created by the user
CategoryField that distinguishes original or replica
  • Currently only the original exists, and a replica will be added when the DR feature is introduced later
UsageTotal data usage of the bucket
EncryptionEncryption usage information
  • When encryption is used, SSE‑S3 encryption key method and AES256 encryption algorithm are applied
  • Encryption settings can be configured on the Object Storage Details page after creating Object Storage
Version ManagementVersion Management Usage Information
  • If settings for version management are required, click the Edit button
URLProvides Public and Private addresses so that Object Storage can be accessed via URL
  • Public: Provided to allow access from external networks
  • Private: Provides an address accessible from resources created within the same Account in the Samsung Cloud Platform Console
Access ControlWhen access control is used, you can control it so that only authorized resources can access the bucket
  • After switching to use access control, you must click the Edit button to add resources to be allowed for each access
    • Public IP Allow: Add as a single IP/CIDR
    • Service Resource Allow: Select service resources created in the same Account/Region
    • Cloud Functions Service: Set whether the service is used
Table. Object Storage Detailed Information Tab Items

Folder List

Through the folder list tab, you can view the list of folders and files stored in the bucket.

CategoryDetailed description
NameFile name or folder name
SizeFile size
Modification Date and TimeThe date and time the file was most recently modified
Additional Features > MoreFile, Folder Management Buttons
  • File Information: View additional information of the file
  • File Copy: Copy the selected file
    • For detailed information on copying files, refer to Copy File.
  • Permission Edit: Set Public Access permission for the file
  • Version List: If versioning is enabled, view the version list
  • Download: Download the selected file
    • For detailed information on downloading files, refer to Download File.
  • Create Presigned URL: Allows file download using a Presigned URL for a set period
    • Enter the required time (1~720 minutes) and click the Confirm button to generate.
  • Delete: Delete the selected file or folder
    • For folders, only deletion is possible.
New FolderAdd new folder
File UploadUpload a new file or a file in progress
  • For detailed information about file upload, see Upload File
DeleteDelete file or folder
  • Activate Delete button when multiple files are selected
  • Deletion possible when single/multiple folders are selected
  • Deletion possible when single/multiple files are selected
  • Deletion possible when multiple files and folders are selected
DownloadFile download
  • Download only possible when a single file is selected
  • Button disabled when a folder is selected
  • Button disabled when multiple files are selected
  • Button disabled when multiple files and folders are selected
Table. Folder List Tab Items
Reference
  • Korea South 3 (kr-south3) region constraints
    • The file upload and download functionality via the Samsung Cloud Platform Console is limited.
    • Use of S3 API/CLI via Public URL is restricted.
    • However, accessing Private URLs through resources (such as Virtual Server) created in the Samsung Cloud Platform Console is possible.
  • Korea South 1 (kr-south1), Korea South 2 (kr-south2) region constraints
  • If delete marker is the latest version, it cannot be seen in the folder list.
  • delete marker version cannot be found in the version list.

Replication

Object Storage list You can view and manage the replication information of the selected resource on the page.

CategoryDetailed description
Policy NameName of the replication policy
  • Enter up to 255 characters, including English letters, numbers, and special characters (-,.)
Replication targetReplication target bucket name
Replication locationReplication location (region)
Target fileReplication target file list
StateReplication policy status
  • Active: Active
  • Inactive: Inactive
AddAdd new replication policy
MorePolicy management possible
  • **Disable**: Disable the policy (display as enabled when disabled)
  • **Edit**: Can edit replication target, target files, and options of the replication policy
    • For details on editing replication policies, see [Edit Replication Policy](/userguide/storage/object_storage/how_to_guides/obj_policy.md#복제-정책-수정하기)
  • **Delete**: Delete the policy
    • For details on deleting replication policies, see [Delete Replication Policy](/userguide/storage/object_storage/how_to_guides/obj_policy.md#복제-정책-삭제하기)
Table. Object Storage Replication Information Tab Items

Tag

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

CategoryDetailed description
Tag ListTag List
  • Tag’s Key and Value information can be checked
  • Up to 50 tags can be added per resource
  • When entering a tag, search and select from the existing list of Keys and Values
Table. Object Storage Tag Tab Items

Work History

Reference
Object Storage resources do not support operation history.
If needed, please check via the Logging&Audit service. For more details, see Logging&Auddit > How-to Guides.

Object Storage Encryption Setup

You can set it to encrypt the data stored in the bucket. After setting bucket encryption, the encryption setting is applied to uploaded data. When using encryption, the SSE‑S3 encryption key method and the AES256 encryption algorithm are applied.

Reference
Object Storage bucket encryption can provide two types (SSE‑S3/SSE‑KMS). SSE‑S3 is server‑side encryption (SSE‑S3) using Amazon S3 managed keys. SSE‑KMS is server‑side encryption (SSE‑KMS) using Key Management Service (KMS) keys.
In this service, server‑side encryption (SSE‑S3) using Amazon S3 managed keys is released as the default method, and server‑side encryption (SSE‑KMS) using Key Management Service (KMS) keys will be provided later according to the service roadmap.

Information

If there is data saved before bucket encryption was set, the encryption settings will not be applied.

  • If you re-upload the file, encryption will be applied.
  • To set encryption for existing data, you need to re-upload it.

Object Storage Follow the steps below to use bucket encryption.

  1. All Services > Storage > Object Storage Click the menu. Go to the Service Home page of Object Storage.
  2. Click the Object Storage menu on the Service Home page. Navigate to the Object Storage List page.
  3. Object Storage List page, click the resource (bucket) to use encryption. Object Storage Details page will be opened.
  4. On the Object Storage Detailed page, check if encryption is not used.
  5. If Encryption is Not Used, click the Edit button.Encryption Edit Popup opens.
  6. After checking Encryption Use, click the Confirm button.

Object Storage Cancel

You can cancel unused Object Storage to reduce operating costs. However, if you cancel the service, the running service may be immediately stopped, so you should consider the impact of service interruption sufficiently before proceeding with the cancellation.

Caution
  • Service termination is possible for buckets with no stored data.
  • If a file is being uploaded, the upload will be canceled.
  • Please be careful as data cannot be recovered after deletion.

If you want to cancel Object Storage, follow the steps below.

  1. All Services > Storage > Object Storage Click the menu. Go to the Service Home page of Object Storage.
  2. Click the Object Storage menu on the Service Home page. Navigate to the Object Storage list page.
  3. Object Storage list on the page, select the resource (bucket) to cancel, and click the Cancel Service button.
  4. Please enter bucket name to confirm termination.
  5. If you have entered the Bucket Name correctly, the Confirm button will be activated. Click the Confirm button.
  6. When termination is complete, check whether the resource has been terminated on the Object Storage List page.