How-to guides
Users can create the service by entering the required GPU Server information and selecting detailed options through the Samsung Cloud Platform Console.
Creating a GPU Server
You can create and use a GPU Server service from the Samsung Cloud Platform Console.
To create a GPU server, follow the steps below.
Click the All Services > Compute > GPU Server menu. You will be taken to the Service Home page of GPU Server.
On the Service Home page, click the GPU Server Creation button. You will be taken to the GPU Server Creation page.
On the GPU Server Creation page, enter the information required to create the service and select detailed options.
- Select the required information in the Image and Version Selection area.
Category Required statusDetailed description Image Required Select the type of Image provided - Standard: Samsung Cloud Platform standard provided Image
- RHEL, Ubuntu
- Custom: User-created Image
- Kubernetes: Image for Kubernetes
- Ubuntu
Image version Required Select the version of the chosen Image - Provides a list of versions for the offered server Image
- For detailed information about the provided server image, see OS and GPU driver versions
Table. GPU Server image and version selection input fields - Standard: Samsung Cloud Platform standard provided Image
- Service Information Input area, enter or select the required information.
Category Required statusDetailed description Number of servers Required Number of GPU Server servers to create concurrently - Only numeric input is allowed, enter a value between 1 and 100
Service Type > Server Type Required GPU Server server type - Indicates the specifications of a GPU-type server, allowing selection of servers with 1, 2, 4, or 8 GPUs
- For detailed information about the server types provided by GPU Server, refer to GPU Server Server Types
Service Type > Planned Compute Selection Resource status with Planned Compute configured - In Use: Number of resources with Planned Compute that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Apply for Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, refer to Apply for Planned Compute
Block Storage Required Configure the Block Storage used by the GPU Server according to its purpose - Basic: The area where the OS is installed and used
- Capacity can be entered in units (the 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 keys
- Encryption can be applied only at initial creation (cannot be changed after creation)
- Performance degradation occurs when using the SSD_KMS disk type
- SSD_Provisioned: SSD volume with configurable IOPS and throughput
- Capacity can be entered in units (the minimum capacity varies depending on the OS image type)
- Additional: Used when the user needs extra space beyond 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, with values between 1 and 1,536
- Since 1 Unit equals 8 GB, this creates 8 GB to 12,288 GB
- SSD: High‑performance general volume
- HDD: General volume
- SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption keys
- Encryption can be applied only at initial creation (cannot be changed after creation)
- Performance degradation may occur when using the SSD_KMS disk type
- HDD/SSD_MultiAttach: Volume that can be attached to two or more servers
- SSD_Provisioned: SSD volume with configurable IOPS and throughput
- For details on each Block Storage type, refer to Create Block Storage
- Delete on termination: If Delete on Termination is set to Enabled, the volume is terminated together with the server
- Volumes with existing snapshots are not deleted even if Delete on termination is set to Enabled
- A multi‑attach volume can be deleted only when the server being removed is the last remaining server attached to the volume
Max IOPS Required Enter a maximum IOPS value between 5,000~20,000 - Can be set only when disk type is SSD_Provisioned
Max Throughput Required Enter the maximum Throughput value between 250~1,000 - Disk type can be set only when it is SSD_Provisioned
Table. GPU Server Service Configuration Items - In the Required Information Input area, enter or select the necessary information.
Category required or notDetailed description Server name Required Enter a name to distinguish the server when the selected number of servers is 1 - Set the hostname using the entered server name
- Enter within 63 characters using letters, numbers, spaces, and special characters (
-_)
Server name Prefix Required Enter a Prefix to distinguish each server generated when the selected number of servers is 2 or more - Automatically generated in the form of user input value (prefix) + ‘
-#’
- Enter within 59 characters using letters, numbers, spaces, and special characters (
-,_)
Network Settings > Create New Network Port Required Configure 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 manual entry; if manual is chosen, the user can directly input the IP
- NAT: Available only when there is a single server and the VPC is attached to an Internet Gateway. Checking Use enables selection of a NAT IP
- NAT IP: Select a NAT IP
- If no NAT IP is available, 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 Use for a local Subnet
- It is not a required element for creating the service
- A pre‑created local Subnet must be selected
- IP can be set to auto‑generate or manual entry; selecting Manual allows the user to input the IP directly
- Security Group: Settings required to access the server
- Select: Choose a pre‑created Security Group
- Create New: If no applicable Security Group exists, you can create one separately in the Security Group service
- Up to 5 can be selected
- If no Security Group is set, all connections are blocked by default
- You must configure a Security Group to allow required connections
Network Settings > Existing Network Port Assignment Required Set 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: Available only when there is a single server and the VPC is connected to an Internet Gateway. When you check to use it, you can select a NAT IP.
- 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
- Local Subnet (optional): Select Use for the local Subnet
- Select a pre-created local Subnet and Port
Keypair Required User authentication methods to use when connecting to the server - New creation: Create a new keypair if one is needed
- Refer to Keypair 생성하기 for how to create a new keypair
- Default login accounts by OS
- RHEL: cloud-user
- Ubuntu: ubuntu
Table. Required input fields for GPU Server - Enter or select the required information in the Additional Information Input area.
Category RequiredDetailed description Lock Selection Lock usage setting - When Lock is enabled, it prevents actions such as server termination, start, and stop from being executed, thereby avoiding malfunctions caused by mistakes
Init script Selection Script executed when the server starts - The init script must be written as a Batch script for Windows, a Shell script for Linux, or cloud‑init, depending on the image type.
- Up to 45,000 bytes can be entered
tag Selection Add Tag - Up to 50 can be added per resource
- After clicking the Add Tag button, enter or select Key, Value values
Table. GPU Server additional information input fields
- Select the required information in the Image and Version Selection area.
Summary Check the detailed information and estimated billing amount generated in the panel, and click the Create button.
- Once creation is complete, check the created resources on the GPU Server List page.
Check GPU Server detailed information
GPU Server service allows you to view and edit the full resource list and detailed information. GPU Server Details page consists of Details, Tags, Job History tabs.
To view detailed information about the GPU Server service, follow these steps.
- Click the All Services > Compute > GPU Server menu. You will be taken to the Service Home page of GPU Server.
- On the Service Home page, click the GPU Server menu. You will be taken to the GPU Server List page.
- On the GPU Server List page, click the resource you want to view details for. You will be taken to the GPU Server Details page.
- GPU Server Details page displays status information and additional feature information, and is composed of Details, Tags, Activity History tabs.
- GPU Server Additional Features for detailed information, please refer to GPU Server Management Additional Features.
Category Detailed description GPU Server status Status of user-created GPU Server - Build: State where the Build command has been received
- Building: Build in progress
- Networking: Server creation networking process
- Scheduling: Server creation scheduling process
- Block_Device_Mapping: Connecting Block Storage during server creation
- Spawning: Server creation process is ongoing
- Active: Available state
- Powering_off: State when a stop request is made
- Deleting: Server deletion in progress
- Reboot_Started: Reboot in progress
- Error: Error state
- Migrating: Server migrating to another host
- Reboot: State where the Reboot command has been received
- Rebooting: Rebooting
- Rebuild: State where the Rebuild command has been received
- Rebuilding: State during Rebuild request
- Rebuild_Spawning: Rebuild process is ongoing
- Resize: State where the Resize command has been received
- Resizing: Resizing in progress
- Resize_Prep: State when a server type change is requested
- Resize_Migrating: Server is migrating to another host while resizing
- Resize_Migrated: Server has completed migration to another host during resizing
- Resize_Finish: Resize completed
- Revert_Resize: Resize or migration of the server failed for some reason. The target server is cleaned up and the original server is restarted
- Shutoff: State when powering off is completed
- Verity_Resize: After Resize_Prep following a server type change request, the server type is confirmed or can be reverted
- Resize_Reverting: State when a server type revert is requested
- Resize_Confirming: State confirming the server’s Resize request
Server control Buttons to change server status - Start: start a stopped server
- Stop: stop a running server
- Restart: restart a running server
Image generation Create a custom user image from the current server image Console log View console logs of the current server - You can view the console logs output by the current server. For more details, see Check console logs.
Create dump Generate a dump of the current server - The dump file is created inside the GPU Server
- For detailed dump creation instructions, refer to Create Dump
Rebuild All data and settings of the existing server are deleted, and a new server is configured - For detailed information, see Execute Rebuild.
Service termination Cancel service button Table. GPU Server status information and additional features
Detailed Information
GPU Server List page lets you view detailed information of the selected resource and edit it if needed.
| Category | Detailed description |
|---|---|
| service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource name | Resource Name
|
| Resource ID | Unique resource ID in the service |
| constructor | User who created the service |
| Creation date and time | Service creation date and time |
| editor | User who edited the service information |
| Modification date | Date and time the service information was modified |
| Server name | Server name |
| Server type | vCPU, memory, GPU information display
|
| image name | Service OS image and version |
| Lock | Indicates whether Lock is used or not
|
| Keypair name | Server authentication information set by the user |
| Planned Compute | Resource status with Planned Compute configured
|
| LLM Endpoint | URL for using LLM
|
| ServiceWatch Detailed Monitoring | When enabled, data monitoring is possible in the ServiceWatch service
|
| Network | Network information of the GPU Server
|
| Local Subnet | Local Subnet information of the GPU Server
|
| Block Storage | Information of Block Storage attached to the server
|
tag
GPU Server List page allows you to view the tag information of the selected resource, and you can add, modify, or delete it.
| Category | Detailed description |
|---|---|
| Tag list | Tag list
|
Job History
You can view the job history of the selected resource on the GPU Server List page.
| Category | Detailed description |
|---|---|
| Task History List | Resource Change History
|
Control GPU Server Operation
If you need to control the operation of a created GPU Server resource, you can perform the task on the GPU Server List or GPU Server Details page. You can start, stop, and restart a running server.
Getting Started with GPU Server
You can start a shutoff GPU Server. To start a GPU Server, follow the steps below.
- Click the All Services > Compute > GPU Server menu. You will be taken to the Service Home page of the GPU Server.
- On the Service Home page, click the GPU Server menu. You will be taken to the GPU Server List page.
- On the GPU Server List page, click the resource you want to start among the shutoff servers, and navigate to the GPU Server Details page.
- GPU Server List page allows you to Start each resource via the right More button.
- After selecting multiple servers with checkboxes, you can control multiple servers simultaneously using the Start button at the top.
- GPU Server Details page, click the Start button at the top to start the server. In the Status Display section, verify the updated server status.
- When the GPU Server startup is complete, the server status changes from Shutoff to Active.
- For detailed information about the GPU Server status, refer to GPU Server detailed information.
Stopping the GPU Server
You can stop a running (Active) GPU Server. To stop the GPU Server, follow the steps below.
- Click the All Services > Compute > GPU Server menu. You will be taken to the Service Home page of GPU Server.
- On the Service Home page, click the GPU Server menu. You will be taken to the GPU Server List page.
- On the GPU Server List page, click the resource to stop among the servers that are running (Active), and navigate to the GPU Server Details page.
- On the GPU Server List page, you can Stop each resource via the right More button.
- After selecting multiple servers with checkboxes, you can control multiple servers simultaneously using the Stop button at the top.
- GPU Server Details page, click the Stop button at the top to start the server. Check the changed server status in the Status Display item.
- When the GPU server shutdown is complete, the server status changes from Active to Shutoff.
- For detailed information about the GPU Server status, please refer to GPU Server Detailed Information.
Restart GPU Server
You can restart the created GPU Server. To restart the GPU Server, follow the steps below.
- Click the All Services > Compute > GPU Server menu. You will be taken to the Service Home page of GPU Server.
- On the Service Home page, click the GPU Server menu. You will be taken to the GPU Server List page.
- On the GPU Server List page, click the resource to restart and go to the GPU Server Details page.
- On the GPU Server list page, you can restart each resource using the right More button.
- After selecting multiple servers with checkboxes, you can control multiple servers simultaneously using the Restart button at the top.
- GPU Server Details on the page, click the Restart button at the top to start the server. Check the updated server status in the Status Display field.
- During a GPU Server restart, the server status goes through Rebooting and finally changes to Active.
- For detailed information about the GPU Server status, refer to GPU Server detailed information.
GPU Server resource management
If you need server control and management functions for the created GPU Server resources, you can perform the tasks on the GPU Server Resource List or GPU Server Details page.
Create Image
You can create an image of a running GPU server.
This guide explains how to create a custom user image from the image of a running GPU server.
- On the 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 these steps.
Click the All Services > Compute > GPU Server menu. Navigate to the Service Home page of the GPU Server.
On the Service Home page, click the GPU Server menu. You will be taken to the GPU Server List page.
On the GPU Server List page, click the resource to create an Image. You will be taken to the GPU Server Details page.
Click the Create Image button on the GPU Server Details page. You will be taken to the Image Creation page.
- Enter the required information in the Service Information Input area.
Category Required statusDetailed description image name Required Enter the name of the image to be created - using English letters, numbers, spaces, and special characters (
-_) within 200 characters
Table. Image service information input fields - using English letters, numbers, spaces, and special characters (
- Enter the required information in the Service Information Input area.
Check the input information and click the Create button.
- When creation is complete, check the created resources on the All Services > Compute > GPU Server > Image List page.
- When you create an Image, the generated Image is stored in the Object Storage used as internal storage. Therefore, Object Storage usage fees are applied.
- Since the file system of an image created from an active GPU server cannot be guaranteed to be intact, it is recommended to stop the server before creating the image.
Enabling detailed monitoring for ServiceWatch
By default, the GPU Server is linked to the basic monitoring of the ServiceWatch and Virtual Server namespaces. You can enable detailed monitoring as needed to identify operational issues more quickly and take action. For detailed information about ServiceWatch, see ServiceWatch Overview.
To enable detailed ServiceWatch monitoring on the GPU Server, follow these steps.
- Click the All Services > Compute > GPU Server menu. You will be taken to the Service Home page of GPU Server.
- On the Service Home page, click the GPU Server menu. You will be taken to the GPU Server List page.
- On the GPU Server List page, click the resource to enable ServiceWatch detailed monitoring. You will be taken to the GPU Server Details page.
- On the GPU Server Details page, click the ServiceWatch detailed monitoring Edit button. You will be taken to the ServiceWatch Detailed Monitoring Edit popup.
- ServiceWatch Detailed Monitoring Edit In the popup window, select Enable, review the instructions, and click the Confirm button.
- On the GPU Server Details page, check the ServiceWatch detailed monitoring items.
Disable detailed monitoring of ServiceWatch
To disable detailed monitoring of ServiceWatch on the GPU Server, follow these steps.
- Click the All Services > Compute > GPU Server menu. You will be taken to the Service Home page of GPU Server.
- On the Service Home page, click the GPU Server menu. You will be taken to the GPU Server List page.
- GPU Server List page, click the resource to disable ServiceWatch detailed monitoring. Navigate to the GPU Server Details page.
- GPU Server Details page, click the ServiceWatch detailed monitoring Edit button. You will be taken to the ServiceWatch detailed monitoring Edit popup.
- ServiceWatch Detailed Monitoring Edit In the popup window, after deselecting Enabled, review the guidance message and click the Confirm button.
- On the GPU Server Details page, view the ServiceWatch detailed monitoring items.
GPU Server Management Additional Features
GPU Server can view Console logs, generate Dumps, and perform Rebuilds for server management. To view Console logs, generate Dumps, or Rebuild a GPU Server, follow the steps below.
Check console log
You can view the current console log of the GPU Server.
To view the console logs of the GPU server, follow these steps.
- Click the All Services > Compute > GPU Server menu. You will be taken to the GPU Server’s Service Home page.
- On the Service Home page, click the GPU Server menu. You will be taken to the GPU Server List page.
- On the GPU Server List page, click the resource to view the console log. You will be taken to the GPU Server Details page.
- On the GPU Server Details page, click the Console Log button. You will be taken to the Console Log popup.
- Console Log Verify the console log displayed in the popup window.
Create Dump
To create a dump file on the GPU Server, follow these steps.
- Click the All Services > Compute > GPU Server menu. You will be taken to the Service Home page of GPU Server.
- On the Service Home page, click the GPU Server menu. You will be taken to the GPU Server List page.
- GPU Server List page, click the resource to view detailed information. You will be taken to the GPU Server Details page.
- On the GPU Server Details page, click the Create Dump button.
- The dump file is created inside the GPU server.
Perform Rebuild
You can delete all data and settings of the existing GPU Server and rebuild it on a new server.
Follow these steps to perform a Rebuild of the GPU Server.
- Click the All Services > Compute > GPU Server menu. You will be taken to the Service Home page of GPU Server.
- On the Service Home page, click the GPU Server menu. You will be taken to the GPU Server List page.
- GPU Server List page, click the resource to perform Rebuild. GPU Server Details page will be displayed.
- On the GPU Server Details page, click the Rebuild button.
- During a GPU Server Rebuild, the server status changes to Rebuilding, and when the Rebuild is complete, it returns to its state before the Rebuild.
- For detailed information about the GPU Server status, refer to Check GPU Server details.
Terminate GPU Server
If you terminate an unused GPU Server, you can reduce operating costs. However, terminating a GPU Server may cause the running service to stop immediately, so you should carefully consider the impact of service interruption before proceeding with the termination.
To cancel the GPU Server, follow the steps below.
- Click the All Services > Compute > GPU Server menu. Go to the GPU Server’s Service Home page.
- On the Service Home page, click the GPU Server menu. You will be taken to the GPU Server List page.
- On the GPU Server List page, select the resource to cancel and click the Cancel Service button.
- The termination of attached storage depends on the Delete on termination setting, so refer to Termination constraints.
- After termination is complete, check on the GPU Server List page whether the resources have been terminated.
Cancellation constraints
When a GPU Server termination request cannot be processed, a popup will provide guidance. Please refer to the cases below.
- If File Storage is connected please disconnect the File Storage connection first.
- When the LB Pool is connected, please disconnect the LB Pool connection first.
- If Lock is set please change the Lock setting to disabled and try again.
Termination of attached storage depends on the Delete on termination setting.
- Whether the volume is deleted also depends on the Delete on termination setting.
- Delete on termination If not set: Even if you terminate the GPU Server, the volume will not be deleted.
- When Delete on termination is set: If you terminate the GPU Server, the associated volume will be deleted.
- Volumes that have snapshots will not be deleted even if Delete on termination is set.
- A Multi‑attach volume can be deleted only when the server being deleted is the last remaining server attached to the volume.