Data Analytics

• 1: Event Streams
• 1.1: Overview
• 1.1.1: Server Type
• 1.1.2: Monitoring Metrics
• 1.2: How-to guides
• 1.3: API Reference
• 1.4: CLI Reference
• 1.5: Release Note
• 2: Search Engine
• 2.1: Overview
• 2.1.1: Server Type
• 2.1.2: Monitoring Metrics
• 2.2: How-to guides
• 2.3: API Reference
• 2.4: CLI Reference
• 2.5: Release Note
• 3: Vertica(DBaaS)
• 3.1: Overview
• 3.1.1: Server Type
• 3.1.2: Monitoring Metrics
• 3.2: How-to guides
• 3.2.1: Vertica Backup and Recovery
• 3.3: API Reference
• 3.4: CLI Reference
• 3.5: Release Note
• 4: Data Flow
• 4.1: Overview
• 4.2: How-to guides
• 4.2.1: Data Flow Services
• 4.2.2: Installing Ingress Controller
• 4.3: API Reference
• 4.4: CLI Reference
• 4.5: Release Note
• 5: Data Ops
• 5.1: Overview
• 5.2: How-to guides
• 5.2.1: Data Ops Services
• 5.2.2: Installing Ingress Controller
• 5.3: API Reference
• 5.4: CLI Reference
• 5.5: Release Note
• 6: Quick Query
• 6.1: Overview
• 6.2: How-to guides
• 6.3: API Reference
• 6.4: CLI Reference
• 6.5: Release Note

1 - Event Streams

1.1 - Overview

Service Overview

Event Streams provides fully managed creation and configuration of the open source Apache Kafka for large-scale, massive message data processing. Samsung Cloud Platform automates the creation and configuration of Apache Kafka through a web-based console, and users can configure the main components of Apache Kafka—Broker, Zookeeper, and AKHQ—in a single or clustered form.

Event Streams cluster is composed of multiple Broker nodes, and Brokers can be installed from a minimum of 1 to a maximum of 10, typically installed with 3 or more. Zookeeper can be installed separately to manage the distributed Brokers, and if not installed separately, it is installed together on the Broker node. Additionally, a tool for managing Kafka called AKHQ (Apache Kafka HQ) is provided, allowing users to manage cluster operations through it.

Provided Features

Event Streams provides the following features.

• Auto Provisioning (Auto Provisioning): You can configure and set up an Apache Kafka cluster via the UI.
• Operation Control Management: Provides a function to control the status of running servers. Restart is possible to apply configuration values, along with starting and stopping the cluster.
• Providing AKHQ: By providing AKHQ, a tool that can manage Kafka, users can manage and monitor clusters through it.
• Broker node addition: If expansion is needed to improve cluster performance and stability, you can add nodes with the same specifications as the Broker nodes in use.
• Parameter Management: Performance improvement and security-related configuration parameters can be set and modified.
• Monitoring: CPU, memory, and cluster performance monitoring information can be viewed through the Cloud Monitoring service.

Components

Event Streams provides pre-validated engine versions and various server types in accordance with the open source support policy. Users can select and use them according to the scale of the service they wish to configure.

Engine Version

The engine versions supported by Event Streams are as follows.

Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped is set to six months before the EoTS date.

According to the supplier’s policy, the EOS and EoTS dates may change, so please refer to the supplier’s license management policy page for details.

• Apache Kafka: https://docs.confluent.io/platform/current/installation/versions-interoperability.html

Server Type

The server types supported by Event Streams are as follows.

For detailed information about the server types provided by Event Streams, please refer to Event Streams Server Types.

Standard ess1v2m4

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.

1.1.1 - Server Type

Event Streams server type

Event Streams provides a server type composed of various combinations such as CPU, Memory, Network Bandwidth, etc. When creating Event Streams, Apache Kafka is installed according to the selected server type suitable for the purpose of use.

The server types supported in Event Streams are as follows.

Standard ess1v2m4

ess1 server type

The ess1 server type of Event Streams is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

• Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor Supports up to 16 vCPUs and 64 GB of memory
• Up to 12.5 Gbps networking speed

ess2 server type

The ess2 server type of Event Streams is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

• Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
• Supports up to 16 vCPUs and 64 GB of memory
• Up to 12.5 Gbps networking speed

esh2 server type

The esh2 server type of Event Streams is provided with high-capacity server specifications and is suitable for database workloads for large-scale data processing.

• Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
• Supports up to 32 vCPUs and 128 GB of memory
• Up to 25Gbps networking speed

1.1.2 - Monitoring Metrics

Event Streams Monitoring Metrics

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

For server monitoring metrics of Event Streams, please refer to the Virtual Server Monitoring Metrics guide.

1.2 - How-to guides

The user can enter the necessary information of Event Streams through the Samsung Cloud Platform Console and create the service by selecting detailed options.

Creating Event Streams

You can create and use the Event Streams service in the Samsung Cloud Platform Console.

To create Event Streams, follow these procedures.

1. Click All services > Data Analytics > Event Streams menu. It moves to the Service Home page of Event Streams.

2. On the Service Home page, click the Create Event Streams button. It moves to the Create Event Streams page.

3. Event Streams Creation page, enter the information required for service creation and select detailed options.

   • Image and Version Selection area, please select the necessary information.

     Classification	Necessity	Detailed Description
     Image Version	Required	Provides a list of Event Streams versions

     Table. Event Streams service information input items

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

     Classification	Necessity	Detailed Description
     Server Name Prefix	Required	The server name where Apache Kafka will be installed Starts with lowercase English letters, and uses lowercase letters, numbers, and special characters(-) to input 3 ~ 13 characters A postfix such as 001, 002 is attached based on the server name to create the actual server name
     Cluster Name	Required	Name of the cluster that the servers are configured in Enter in English, 3-20 characters A cluster is a unit that bundles multiple servers
     Broker > Broker Node count	required	Broker Node count
     Broker > Server Type	Required	The type of server on which the Broker will be installed Standard: Standard specification commonly used High Capacity: High-capacity server with 24vCore or more For more information about the server types provided by Event Streams, see Event Streams server types
     Broker > Planned Compute	Selection	Current status of resources with Planned Compute set In use: Number of resources with Planned Compute set that are currently in use Settings: Number of resources with Planned Compute set Coverage preview: Amount applied by resource-based Planned Compute Apply for Planned Compute service: Move to the Planned Compute service application page For more information, see How to apply for Planned Compute
     Broker > Block Storage	Required	Block Storage type to be used for Broker node Base OS: Area where the engine is installed DATA: Area for storing data files Please select the storage type and enter the capacity. (For more information on each Block Storage type, see Creating Block Storage) SSD: High-performance general volume HDD: General volume SSD_KMS/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption key Capacity should be entered in multiples of 8 within the range of 16 to 5,120
     Zookeeper separate installation > use	selection	Whether to install Zookeeper node separately Use is selected, Zookeeper nodes are installed separately. If Zookeeper nodes are not installed separately, Broker nodes also perform the Zookeeper role.
     Zookeeper separate installation > Server type	Selection	The server type where Zookeeper will be installed Zookeeper node provides vCPU 1, Memory 2G or vCPU 2, Memory 4G
     Zookeeper separate installation > Planned Compute	selection	Current status of resources with Planned Compute set In use: Number of resources in use among those with Planned Compute set Settings: Number of resources with Planned Compute set Coverage preview: Amount applied by resource-based Planned Compute Apply for Planned Compute service: Move to the Planned Compute service application page For more details, refer to Apply for Planned Compute
     Zookeeper separate installation > Block Storage	required	Block Storage type to be used for Zookeeper node Basic OS: area where the engine is installed DATA: area for storing data files After selecting the storage type, enter the capacity. (For more information on each Block Storage type, see Creating Block Storage) SSD: high-performance general volume HDD: general volume SSD_KMS/HDD_KMS: additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption key Capacity should be entered in multiples of 8 within the range of 16 to 5,120
     AKHQ > Use	Required	Whether AKHQ is installed Use is selected, AKHQ will be installed.
     AKHQ > Server Type	Required	The type of server where AKHQ will be installed AKHQ only provides vCPU 2, Memory 4G type
     AKHQ > Planned Compute	Selection	Current status of resources with Planned Compute set In use: Number of resources with Planned Compute set that are in use Settings: Number of resources with Planned Compute set Coverage preview: Amount applied by resource-based Planned Compute Apply for Planned Compute service: Move to the Planned Compute service application page For more information, see Apply for Planned Compute
     AKHQ > Block Storage	required	The type of Block Storage to be used on the server where AKHQ will be installed Basic OS: The area where the engine is installed
     AKHQ > AKHQ account	required	AKHQ account Use lowercase English letters to enter 2-20 characters
     AKHQ > AKHQ password	required	AKHQ account password Enter 8-30 characters, including English, numbers, and special characters (excluding " ’)
     AKHQ > AKHQ password confirmation	required	AKHQ account password confirmation Re-enter the AKHQ account password identically
     AKHQ > AKHQ Port number	required	AKHQ connection port number The port number is automatically set to 8080 and cannot be modified
     Network > Common Settings	Required	Network settings for servers created by the service Select if you want to apply the same settings to all servers being installed Select pre-created VPC and Subnet IP: Only automatic creation is possible Public NAT settings are only possible in server-specific settings.
     Network > Server-specific settings	Required	Network settings for installing servers created by the service Select to apply different settings for each server being installed Select pre-created VPC and Subnet IP: Enter the IP for each server Public NAT feature is available only when the VPC is connected to the Internet Gateway, checking Use allows selection from the reserved IP in the VPC product’s Public IP. For more information, see Creating Public IP
     IP Access Control	Select	Set service access policy Set access policy for IP entered on the page, so you don’t need to set Security Group policy separately. Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32), and click the Add button To delete the entered IP, click the x button next to the entered IP
     Maintenance period	Select	Event Streams maintenance period Use Select the day, start time, and duration It is recommended to set the maintenance period for stable management of the service. Patch work will be carried out at the set time and service interruption may occur Issues caused by not applying patches (setting to not in use) are not the responsibility of our company

     Table. Event Streams Service Configuration Items

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

     Classification	Necessity	Detailed Description
     Zookeeper SASL account	required	Zookeeper account Use lowercase English letters, 2-20 characters
     Zookeeper SASL password	required	Zookeeper account password Enter 8-30 characters including English, numbers, and special characters (excluding " ’)
     Zookeeper SASL password confirmation	required	Confirm Zookeeper account password Re-enter the Zookeeper SASL account password identically
     Zookeeper Port number	required	Zookeeper port number 1,024 ~ 65,535 can be entered as one of them, and Broker port or 2888, 3888 cannot be used
     Broker SASL account	required	Kafka connection account Enter within 2-20 characters using lowercase English letters
     Broker SASL password	required	Kafka connection account password Enter 8-30 characters, including English, numbers, and special characters (excluding " ’)
     Broker SASL password confirmation	required	Kafka connection account password confirmation Re-enter the Broker SASL account password identically
     Broker Port number	required	Kafka port number 1,024 ~ 65,435 can be entered as one of them, and Broker port or 2888, 3888 cannot be used
     Parameter	Required	Event Streams configuration parameters Inquiry button can be clicked to check detailed information of parameters Parameter modification is possible after service creation is completed, and restart is required when modified
     Time Zone	Selection	Standard Time Zone where the service will be used

     Table. Essential information input items for Event Streams Database configuration

   • Enter Additional Information Enter or select the required information in the area.

     Classification	Necessity	Detailed Description
     Tag	Selection	Tag addition Tag addition button to create and add tags or add existing tags Up to 50 tags can be added Newly added tags are applied after service creation is completed

     Table. Event Streams service additional information input items

4. In the Summary panel, review the detailed information and estimated charges, and click the Complete button.

   • Once creation is complete, check the created resource on the Resource List page.

Event Streams detailed information check

The Event Streams service allows you to view and modify the list of all resources and detailed information. The Event Streams details page consists of Details, Tags, Activity tabs.

To view detailed information about the Event Streams service, follow these steps.

1. Click All services > Data Analytics > Event Streams menu. It moves to the Service Home page of Event Streams.
2. On the Service Home page, click the Event Streams menu. It moves to the Event Streams list page.
3. Event Streams list page, click on the resource to check the detailed information. Move to the Event Streams details page.
   • Event Streams details page top shows status information and additional function information.

Detailed Information

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

Tag

On the Event Streams list page, you can check the tag information of the selected resource, and add, change, or delete it.

Work History

You can check the operation history of the selected resource on the Event Streams list page.

Managing Event Streams Resources

If you need to change the existing setup options for the generated Event Streams resource or manage Parameters, or configure additional Broker Nodes, you can perform the task from the Event Streams details page.

Operating Control

If changes occur to the Event Streams resource while it is running, you can start, stop, or restart it.

To control the operation of Event Streams, follow these procedures.

1. Click All services > Data Analytics > Event Streams menu. It moves to the Service Home page of Event Streams.
2. On the Service Home page, click the Event Streams menu. It moves to the Event Streams list page.
3. Event Streams list page, click the resource to control the operation. Move to the Event Streams details page.
4. Check the status of Event Streams and complete the change through the control buttons below.
   • Start: The server where the Event Streams service is installed and the Event Streams service is running.
   • 중지: Event Streams service installed server and Event Streams service will be stopped.
   • Restart: Only the Event Streams service will be restarted.

Synchronizing Service Status

You can query the current server status and synchronize it to the Console.

To synchronize the service status of Event Streams, follow these procedures.

1. Click All services > Data Analytics > Event Streams menu. It moves to the Service Home page of Event Streams.
2. On the Service Home page, click the Event Streams menu. It moves to the Event Streams list page.
3. On the Event Streams list page, click the resource to query the service status. It moves to the Event Streams details page.
4. Service Status Synchronization button should be clicked. It takes a little time to retrieve, and during retrieval, the cluster changes to Synchronizing status.
5. Once the inquiry is completed, the status of the server information item is updated, and the cluster is changed to the Running state.

Managing Parameters

It provides parameter inquiry and modification functions.

To view or modify the configuration parameters, follow these steps.

1. 모든 서비스 > Data Analytics > Event Streams menu should be clicked. It moves to the Service Home page of Event Streams.
2. Service Home page, click the Event Streams menu. It moves to the Event Streams list page.
3. Event Streams list page, click the resource you want to query and modify parameters. It moves to the Event Streams detail page.
4. Click the Parameter Management button. It moves to the Parameter Management page.
5. On the Parameter Management page, click the Search button. The Database Search popup window opens.
6. To inquire about parameter information, click the Confirm button. It may take some time to retrieve.
   • You can modify the Parameter information after performing the inquiry.
7. To modify the Parameter information, click the Modify button and enter the modification details in the Custom Value area of the Parameter to be modified.
   • If the application type is dynamic, it is reflected immediately, and if it is static, a service restart is required, so the service is stopped.
8. When the input is complete, click the Save button.

Changing the Server Type

You can change the configured server type.

To change the server type, follow these steps.

1. Click All services > Data Analytics > Event Streams menu. It moves to the Service Home page of Event Streams.
2. On the Service Home page, click the Event Streams menu. It moves to the Event Streams list page.
3. On the Event Streams list page, click the resource for which you want to change the server type. It moves to the Event Streams detail page.
4. Click the Edit button of the server type you want to change at the bottom of the detailed information. The Server Type Edit popup window opens.
5. Server Type Modification In the server type modification popup window, select the server type and click the OK button.

Expanding Storage

The storage added to the data area can be expanded up to a maximum of 5TB based on the initially allocated capacity. Storage can be expanded without interrupting Event Streams, and if configured as a cluster, all nodes are expanded simultaneously.

To increase the storage capacity, follow the next procedure.

1. Click All services > Data Analytics > Event Streams menu. It moves to the Service Home page of Event Streams.
2. Service Home page, click the Event Streams menu. It moves to the Event Streams list page.
3. On the Event Streams list page, click the resource for which you want to change the server type. It moves to the Event Streams details page.
4. Click the Edit button of the additional Disk you want to add at the bottom of the detailed information. The Disk Edit popup window opens.
5. In the Disk Modification popup window, enter the expansion capacity and click the Confirm button.

Add Broker Node

If Event Streams cluster expansion is needed, nodes can be added with the same specifications as the Broker Node in use. The added nodes are added to the existing cluster without server downtime, and the existing data is automatically distributed.

To add a Broker node, follow these steps.

1. Click All services > Data Analytics > Event Streams menu. It moves to the Service Home page of Event Streams.
2. On the Service Home page, click the Event Streams menu. It moves to the Event Streams list page.
3. Event Streams Resource Click the resource you want to recover from the list page of Event Streams Resources. It moves to the Event Streams Details page.
4. Click the Add Broker Node button. It moves to the Add Broker Node page.
5. Required Information Input area, enter the corresponding information, and then click the Complete button.

Cancel Event Streams

You can cancel unused Event Streams to reduce operating costs. However, when canceling the service, the operating service may be stopped immediately, so you should consider the impact of stopping the service sufficiently before proceeding with the cancellation work.

To cancel Event Streams, follow these procedures.

1. Click All services > Data Analytics > Event Streams menu. It moves to the Service Home page of Event Streams.
2. Service Home page, click the Event Streams menu. It moves to the Event Streams list page.
3. Event Streams list page, select the resource to be canceled and click the Service Cancellation button.
4. Once the cancellation is complete, check if the resource has been cancelled on the Event Streams listing page.

1.3 - API Reference

1.4 - CLI Reference

1.5 - Release Note

Event Streams

2 - Search Engine

2.1 - Overview

Service Overview

Search Engine provides automated creation and configuration of the distributed search and analytics engines Elasticsearch and OpenSearch through a web-based console. Users can select a server type that fits the system configuration to set up a cluster, and it supports the data analysis and visualization tools Kibana and the OpenSearch dashboard.

Search Engine Cluster consists of multiple master nodes and data nodes. Data nodes can be installed from a minimum of 1 up to a maximum of 10, and are usually installed with three or more. If a separate master node is not installed, the data node also performs the role of the master node, and up to 10 can be installed. When a separate master node is installed, data nodes can be up to 50.

Provided Features

Search Engine provides the following functions.

• Auto Provisioning (Auto Provisioning): You can configure and set up Elasticsearch and OpenSearch clusters via the UI.
• Operation Control Management: Provides a function to control the status of running servers. It allows restarting to apply configuration values, in addition to starting and stopping the cluster.
• Backup and Recovery: Backup is possible using the built-in backup function, and recovery is possible to the point in time of the backup file.
• Data Node Addition: If cluster expansion is needed, you can add nodes with the same specifications as the data nodes in use. Up to 10 nodes can be added within the cluster.
• Visualization tool support: Provides data analysis and visualization tools, and supports Elasticsearch Kibana or OpenSearch dashboards.
• Monitoring: CPU, Memory, cluster performance monitoring information can be checked through the Cloud Monitoring service.

Components

Search Engine provides pre-validated engine versions and various server types according to the open source support policy. Users can select and use them according to the scale of the service they want to configure.

Engine Version

Search Engine the supported engine versions are as follows.

Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped is set to six months before the EoTS date.

According to the supplier’s policy, the EOS and EoTS dates may change, so please refer to the supplier’s license management policy page for details.

• Elasticsearch: https://www.enterprisedb.com/resources/platform-compatibility

• OpenSearch: https://opensearch.org/releases/

Server Type

The server types supported by Search Engine are as follows.

For detailed information about the server types provided by Search Engine, please refer to Search Engine Server Type.

Standard se1v2m4

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.

2.1.1 - Server Type

Search Engine server type

Search Engine provides a server type composed of various combinations such as CPU, Memory, Network Bandwidth, etc. When creating a Search Engine, Elastic Search is installed according to the server type selected to match the purpose of use.

The server types supported by the Search Engine are as follows.

Standard ses1v2m4

ses1 server type

The ses1 server type of Search Engine is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

• 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

ses2 server type

The ses1 server type of Search Engine is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

• 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

SEH2 server type

The seh2 server type of Search Engine is provided with large-capacity server specifications and is suitable for database workloads for large-scale data processing.

• Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
• Supports up to 72 vCPUs and 288 GB of memory
• Up to 25Gbps networking speed

2.1.2 - Monitoring Metrics

Search Engine Monitoring Metrics

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

For server monitoring metrics of the Search Engine, please refer to the Virtual Server Monitoring Metrics guide.

2.2 - How-to guides

The user can enter the necessary information of the Search Engine through the Samsung Cloud Platform Console and create the service by selecting detailed options.

Creating Search Engine

You can create and use the Search Engine service in the Samsung Cloud Platform Console.

To create a Search Engine, follow the next procedure.

1. All Services > Database > Search Engine menu, click. It moves to the Service Home page of Search Engine.

2. On the Service Home page, click the Create Search Engine button. It moves to the Create Search Engine page.

3. Search Engine Creation page where you enter the information needed to create a service and select detailed options.

   • Image and Version Selection area, please select the necessary information.

     Classification	Necessity	Detailed Description
     Image	Required	Select the type of image provided Elasticsearch Enterprise, OpenSearch
     Image Version	Required	Select the version of the selected image Provide a list of versions of the server image provided

     Fig. Search Engine image and version selection items

   • Enter Service Information area, please enter or select the necessary information.

     Classification	Necessity	Detailed Description
     Server Name Prefix	Required	The name of the server where Elasticsearch will be installed Starts with a lowercase letter, using lowercase letters, numbers, and special characters (-) to input 3 ~ 13 characters A postfix such as 001, 002 is attached based on the server name to create the actual server name
     Cluster Name	Required	Name of the cluster that the servers are configured in Enter in English, 3-20 characters The cluster is a unit that bundles multiple servers
     MasterNode separate installation > use	essential	Whether to install the Master node separately Use is selected, the Master node is installed separately. If the Master node is not installed separately, the data node also performs the master role.
     MasterNode separate installation > MasterNode count	required	Number of Master nodes The master node is installed with a fixed 3 units for failover recovery.
     MasterNode separate installation > Server type	Required	Master node server type Standard: Standard specification commonly used High Capacity: High-capacity server with 24vCore or more For more information on the server type provided by Search Engine, refer to Search Engine server type
     MasterNode separate installation > Planned Compute	selection	Current status of resources with Planned Compute set In use: Number of resources in use among those with Planned Compute set Settings: Number of resources with Planned Compute set Coverage preview: Amount applied by resource-based Planned Compute Apply for Planned Compute service: Move to the Planned Compute service application page For more information, see Apply for Planned Compute
     MasterNode separate installation > Block Storage	required	Master node block storage type Basic OS: area where the engine is installed DATA: data file storage area After selecting the storage type, enter the capacity. (For more information on each block storage type, see Creating Block Storage) SSD: high-performance general volume HDD: general volume SSD_KMS/HDD_KMS: additional encrypted volume using KMS (Key Management System) encryption key Capacity can be entered in multiples of 8 in the range of 16 to 5,120 Add Disk: data storage area After selecting Use, enter the Capacity of the storage To add storage, click the + button, and to delete, click the x button. Up to 9 can be added. Capacity can be entered in multiples of 8 in the range of 16 to 5,120, and up to 9 can be created
     Number of Nodes	Required	Number of Data Nodes In cases where the Master node is installed separately, 2 or more nodes are required, and in other cases, 1 or more nodes must be selected.
     Service Type > Server Type	Required	Data Node Server Type Standard: generally used standard specification High Capacity: high-capacity server with 24vCore or more
     Service Type > Planned Compute	Selection	Current status of resources with Planned Compute set In Use: Number of resources with Planned Compute set that are in use Settings: Number of resources with Planned Compute set Coverage Preview: Amount applied by Planned Compute for each resource Apply for Planned Compute Service: Move to the Planned Compute service application page For more information, see How to Apply for Planned Compute
     Service Type > Block Storage	Required	Type of Block Storage to be used for data node Basic OS: Area where the engine is installed DATA: Data file storage area Please select the storage type and enter the capacity. (For more information on each Block Storage type, refer to Creating Block Storage) SSD: High-performance general volume HDD: General volume SSD_KMS/HDD_KMS: Additional encrypted volume using KMS (Key Management System) encryption key Capacity can be entered in multiples of 8 within the range of 16 to 5,120 Disk Add: Additional storage area for data, backup Select Use and enter the Purpose and Capacity of the storage To add storage, click the + button, and to delete, click the x button. Up to 9 can be added. Capacity can be entered in multiples of 8 within the range of 16 to 5,120, and up to 9 can be created
     Kibana > Server Type	Required	The type of server where Kibana will be installed Standard: Standard specification commonly used
     Kibana > Planned Compute	Selection	Current status of resources with Planned Compute set In use: Number of resources with Planned Compute set that are in use Settings: Number of resources with Planned Compute set Coverage preview: Amount applied by resource-based Planned Compute Apply for Planned Compute service: Move to the Planned Compute service application page For more information, see How to apply for Planned Compute
     Kibana > Block Storage	required	The type of Block Storage to be used on the server where Kibana will be installed Basic OS: The area where the engine is installed
     Network > Common Settings	Required	Network settings for servers created by the service Select if you want to apply the same settings to all servers being installed Select pre-created VPC and Subnet IP: Only automatic creation is possible Public NAT settings are only possible in server-specific settings.
     Network > Server Settings	Required	Network settings for installing servers created by the service Select to apply different settings for each server being installed Select pre-created VPC and Subnet IP: Enter the IP for each server The Public NAT function is available only when the VPC is connected to the Internet Gateway, and if Use is checked, you can select from the reserved IP in the VPC product’s Public IP. For more information, see Creating Public IP
     IP Access Control	Select	Set service access policy Set access policy for IPs entered on the page, so you don’t need to set Security Group policy separately. Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32), and click the Add button To delete the entered IP, click the x button next to the entered IP
     Maintenance period	Select	Search Engine maintenance period Use Selecting the day of the week, start time, and duration It is recommended to set the maintenance period for stable management of the service. Patch work is performed at the set time and service interruption occurs If set to unused, problems that occur due to non-application of patches are not the responsibility of our company.

     Table. Search Engine service information input items

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

     Classification	Necessity	Detailed Description
     Backup > Use	Selection	Whether to use node backup If node backup is selected, select the storage period and backup start time
     Backup > Retention Period	Select	Backup Retention Period Please select the backup retention period. The file retention period can be set from 7 to 35 days Backup files may incur additional charges depending on capacity.
     Backup > Backup start time	Select	Backup start time Select the backup start time The minutes when the backup is performed are set randomly, and the backup end time cannot be set
     Cluster Port number	Required	Elasticsearch connection port number 1,024 ~ 65,535 can be entered as one of them, and Elasticsearch internal port 9300 and Kibana port 5301 are not available
     Elastic username	required	Elasticsearch username Enter within 2-20 characters using lowercase English letters The following usernames cannot be used. apm_system, beats_system, elastic, kibana, kibana_system, logstash_system, remote_monitoring_user, scp_kibana_system, scp_manager, maxigent_cl
     Elastic password	required	Elasticsearch connection password Enter 8-30 characters, including English, numbers, and special characters (excluding " ’ </code>)
     Elastic password confirmation	required	Confirm Elasticsearch connection password Re-enter the Elasticsearch connection password identically
     License Key	required	Elasticsearch License Key Enter the entire contents of the issued license file (.json) If the entered license key is not valid, service creation may not be possible. OpenSearch does not require a License Key.
     Time Zone	Selection	Standard Time Zone where the service will be used

     Fig. Search Engine Database Configuration Required Information Input Items

   • Enter Additional Information Enter or select the required information in the area.

     Classification	Necessity	Detailed Description
     Tag	Select	Add Tag Add Tag button to create and add a tag or add an existing tag Up to 50 tags can be added Newly added tags will be applied after service creation is complete

     Fig. Search Engine service additional information input items

4. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.

   • Once creation is complete, check the created resource on the Resource List page.

Search Engine detailed information check

The Search Engine service can check and modify the entire resource list and detailed information. The Search Engine details page consists of detailed information, tags, and work history tabs.

To check the detailed information of the Search Engine service, follow the next procedure.

1. All services > Data Analytics > Search Engine menu, click. It moves to the Service Home page of Search Engine.
2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
3. Search Engine list page, click on the resource to check the detailed information. Move to the Search Engine details page.
   • Search Engine Details The top of the page displays status information and additional features.

Detailed Information

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

Tag

On the Search Engine list page, you can check the tag information of the selected resource, and add, change, or delete it.

Work History

You can check the operation history of the resource selected on the Search Engine list page.

Search Engine Resource Management

If you need to change the existing setting options of the generated Search Engine resource or manage Parameters, or configure additional Nodes, you can perform the task on the Search Engine details page.

Operating Control

If there are changes to the Search Engine resources in operation, you can start, stop, and restart them.

To control the operation of the Search Engine, follow the next procedure.

1. Click on the menu of all services > Data Analytics > Search Engine. It moves to the Service Home page of Search Engine.
2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
3. Search Engine list page, click the resource to control the operation. Move to the Search Engine details page.
4. Check the Search Engine status and complete the change through the control button below.
   • Start: The Search Engine service is installed on the server and the Search Engine service is running.
   • Stop: The Search Engine service installed on the server and the Search Engine service will be stopped.
   • Restart: Only the Search Engine service will be restarted.

Synchronizing Service Status

You can query the current server status and synchronize it to the Console.

To synchronize the service status of the Search Engine, follow the next procedure.

1. Click All Services > Data Analytics > Search Engine menu. It moves to the Service Home page of Search Engine.
2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
3. Search Engine list page, click on the resource to check the service status. Move to the Search Engine details page.
4. Service Status Synchronization button should be clicked. It takes some time to retrieve, and during retrieval, the cluster changes to Synchronizing status.
5. When the query is complete, the status in the server information item is updated, and the cluster changes to Running status.

Changing Server Type

You can change the configured server type.

To change the server type, follow these steps.

1. All services > Data Analytics > Search Engine menu is clicked. It moves to the Service Home page of Search Engine.
2. Service Home page, click the Search Engine menu. Move to the Search Engine list page.
3. Search Engine list page, click the resource to change the server type. Move to the Search Engine details page.
4. Click the Edit button of the Server Type you want to change at the bottom of the detailed information. The Edit Server Type popup window opens.
5. In the Server Type Modification popup window, select the server type and click the Confirm button.

Expanding Storage

The storage added to the data area can be expanded up to a maximum of 5TB based on the initially allocated capacity. Storage can be expanded without stopping the Search Engine, and if configured in a cluster, all nodes are expanded simultaneously.

To increase the storage capacity, follow the procedure below.

1. All services > Data Analytics > Search Engine menu is clicked. It moves to the Service Home page of Search Engine.
2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
3. Search Engine list page, click the resource to change the server type. It moves to the Search Engine details page.
4. Click the Modify button of the additional Disk you want to add at the bottom of the detailed information. The Disk Modification popup window opens.
5. In the Disk Modification popup window, enter the expansion capacity and click the Confirm button.

Adding Storage

If you need more than 5TB of data storage space, you can add storage.

To add storage capacity, follow these steps.

1. All services > Data Analytics > Search Engine menu is clicked. It moves to the Service Home page of Search Engine.
2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
3. Search Engine list page, click the resource to add storage. Move to the Search Engine details page.
4. Click the Add Disk button at the bottom of the detailed information. The Add Disk popup window opens.
5. In the Add Disk popup window, enter the purpose and capacity, then click the OK button.

Search Engine Backup

Through the backup settings function, users can set the data retention period and start cycle, and perform backup history inquiry and deletion through the backup history function.

Setting up backup

While creating the Search Engine, the procedure for setting up the backup is to refer to the Search Engine creation guide, and to modify the backup settings of the created resource, follow the following procedure.

1. All Services > Data Analytics > Search Engine menu is clicked. It moves to the Service Home page of Search Engine.
2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
3. Search Engine list page, click the resource to set the backup. Move to the Search Engine details page.
4. Click the Edit button of the backup item. The Backup Edit popup window opens.
5. If you set up a backup, click Use in the Backup Modification popup window, select the storage period, backup start time, and Archive backup cycle, and then click the Confirm button.
   • If you want to stop the backup settings, uncheck Use in the Backup Modification popup window and click the OK button.

Check Backup History

To view the backup history, follow these steps.

1. All Services > Data Analytics > Search Engine menu is clicked. It moves to the Service Home page of Search Engine.
2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
3. Search Engine list page, click the resource to check the backup history. Move to the Search Engine details page.
4. Click the Backup History button. The Backup History popup window opens.
5. Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.

Deleting backup files

To delete the backup history, follow these steps.

1. Click on the menu for all services > Data Analytics > Search Engine. It moves to the Service Home page of the Search Engine.
2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
3. Search Engine list page, click the resource to check the backup history. Move to the Search Engine details page.
4. Click the Backup History button. The Backup History popup window opens.
5. In the backup history popup window, check the file you want to delete and click the Delete button.

Search Engine recovery

In the event of a failure or data loss that requires restoration from a backup file, cluster recovery allows recovery based on a specific point in time.

To restore the Search Engine, follow the following procedure.

1. All Servives > Data Analytics > Search Engine menu should be clicked. It moves to the Service Home page of Search Engine.
2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
3. Search Engine Resource Click on the resource you want to restore from the list page. It moves to the Search Engine Details page.
4. Click the Cluster Recovery button. It moves to the Cluster Recovery page.
5. Enter the corresponding information in the Cluster Recovery Configuration area, and then click the Complete button.

Add Node

If Search Engine cluster expansion is needed, you can add nodes with the same specifications as the data node in use.

To add a node, follow these steps.

1. All Services > Data Analytics > Search Engine menu should be clicked. It moves to the Service Home page of Search Engine.
2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
3. Search Engines Resource menu should be clicked. It moves to the Search Engine Detail page.
4. Click the Add Broker Node button. It moves to the Add Broker Node page.
5. Required Information Input area, enter the corresponding information, and then click the Complete button.

Search Engine cancellation

You can cancel the unused Search Engine to reduce operating costs. However, if you cancel the service, the operating service may be stopped immediately, so you should consider the impact of stopping the service sufficiently before proceeding with the cancellation work.

To cancel the Search Engine, follow the next procedure.

1. All services > Data Analytics > Search Engine menu is clicked. It moves to the Service Home page of Search Engine.
2. On the Service Home page, click the Search Engine menu. It moves to the Search Engine list page.
3. Search Engine list page, select the resource to be canceled and click the Service Cancellation button.
4. Once the cancellation is complete, please check if the resource has been cancelled on the Search Engine list page.

2.3 - API Reference

2.4 - CLI Reference

2.5 - Release Note

Search Engine

3 - Vertica(DBaaS)

3.1 - Overview

Service Overview

Vertica(DBaaS) is a high-availability enterprise database based on Data Warehouse for large-scale data analysis/processing. It is a data analysis platform that, through a single engine, can perform basic analyses such as queries on data coming from various sources without moving them, as well as AI analyses like machine learning. In Samsung Cloud Platform, DB management functions such as high‑availability configuration, backup/recovery, patching, parameter management, and monitoring are added to ensure stable management of single instances or critical data, enabling automation of tasks throughout the database lifecycle. Additionally, to prepare for issues with DB servers or data, it provides an automatic backup function at user‑specified times, supporting data recovery at the desired point in time.

Service Architecture Diagram

Provided Features

Vertica (DBaaS) provides the following features.

• Auto Provisioning: Automatically installs the DB of the standard version of Samsung Cloud Platform based on Virtual Servers of various specifications.
• Cluster configuration: Provides its own high-availability architecture in a Masterless form.
• Operation Control Management: Provides a function to control the status of running servers. Servers can be started and stopped, and can be restarted if there is a problem with the DB or to apply configuration values.
• Backup and Recovery: Provides a data backup function based on its own backup commands. The backup retention period and backup start time can be set by the user, and additional charges apply based on backup size. It also provides a recovery function for backed-up data; when the user performs a recovery, a separate DB is created and recovery proceeds to the point selected by the user (backup save point, user-specified point). When recovering a Database, you can choose to install the Management Console for use.
• Service status query: You can view the final status of the current DB service.
• Monitoring: CPU, memory, DB performance monitoring information can be checked through the Cloud Monitoring service.
• High-performance processing of large-scale data: Guarantees stable performance in environments with massive parallel processing (MPP, Massively Parallel Processing) and SQL query Mixed Workload. Vertica processes queries through distributed processing and has a structure that allows queries to be started from any node, so there is no Single Point of Failure where queries would not be executed in case of a specific node failure.

Components

Vertica(DBaaS) provides pre-validated engine versions and various server types. Users can select and use them according to the scale of the service they want to configure.

Engine Version

The engine versions supported by Vertica(DBaaS) are as follows.

Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped is set to six months before the EoTS date.

According to the supplier’s policy, the EOS and EoTS dates may change, so please refer to the supplier’s license management policy page for details.

Server Type

The server types supported by Vertica (DBaaS) are as follows.

For detailed information about the server types provided by Vertica (DBaaS), please refer to Vertica server types.

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.

3.1.1 - Server Type

Vertica(DBaaS) server type

Vertica(DBaaS) provides a server type composed of various combinations such as CPU, Memory, Network Bandwidth, etc. When creating Vertica(DBaaS), the Database Engine is installed according to the server type selected for the purpose of use.

The server types supported by Vertica(DBaaS) are as follows.

Standard db1v2m4

db1 server type

The db1 server type of Vertica(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

• 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

DB2 server type

The db2 server type of Vertica(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

• 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

DBH2 Server Type

The dbh2 server type of Vertica(DBaaS) is provided with large-capacity server specifications and is suitable for database workloads for large-scale data processing.

• 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

3.1.2 - Monitoring Metrics

Vertica(DBaaS) monitoring metrics

The following table shows the performance monitoring metrics of Vertica (DBaaS) that can be checked through Cloud Monitoring. For detailed instructions on how to use Cloud Monitoring, please refer to the Cloud Monitoring guide.

The server monitoring metrics of Vertica(DBaaS) refer to the Virtual Server monitoring metrics guide.

3.2 - How-to guides

The user can enter the required information of Vertica(DBaaS) through the Samsung Cloud Platform Console and create the service by selecting detailed options.

Creating Vertica(DBaaS)

You can create and use the Vertica (DBaaS) service in the Samsung Cloud Platform Console.

To create a Vertica(DBaaS), follow these steps.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).

2. Service Home page, click the Vertica(DBaaS) creation button. Move to the creation page.

3. Create Vertica(DBaaS) page, enter the information required for service creation, and select detailed options.

   • Image and Version Selection area, please select the necessary information.

     Classification	Necessity	Detailed Description
     Image Version	Required	Provides a list of Vertica (DBaaS) versions

     Table. Vertica(DBaaS) image and version input items

   • Enter Service Information Enter or select the necessary information in the area.

     Classification	Necessity	Detailed Description
     Server Name Prefix	Required	The name of the server where Vertica will be installed Starts with a lowercase letter, and consists of 3 to 13 characters using lowercase letters, numbers, and special characters (-) A postfix such as 001, 002 is attached based on the server name to create the actual server name
     Cluster Name	Required	The name of the cluster that the servers are configured in Enter in English, 3-20 characters A cluster is a unit that bundles multiple servers
     Number of Nodes	Required	Number of Data Nodes The number of nodes must be entered within the range of 1-10 Entering the number of nodes as 2 or more to form a cluster ensures high availability
     Service Type > Server Type	Required	Data Node Server Type Standard: Standard specification commonly used High Capacity: High-capacity server with 24vCore or more For more information on the server types provided by Vertica(DBaaS), see Vertica(DBaaS) Server Type
     Service Type > Planned Compute	Selection	Current status of resources with Planned Compute set In Use: Number of resources with Planned Compute set that are currently in use Settings: Number of resources with Planned Compute set Coverage Preview: Amount applied by Planned Compute for each resource Apply for Planned Compute Service: Move to the Planned Compute service application page For more details, refer to How to Apply for Planned Compute
     Service Type > Block Storage	Required	Type of Block Storage to be used for data node Base OS: Area where the engine is installed DATA: Area for storing data files Select storage type and enter capacity (For more information on Block Storage type, refer to Creating Block Storage) SSD: General Block Storage SSD_KMS: Additional encryption volume using KMS (Key Management System) encryption key The set storage type will be applied equally to additional storage Capacity can be entered in multiples of 8 in the range of 16 to 5,120 Additional: DATA, Backup data storage area Select Use and enter Purpose and Capacity of storage To add storage, click the + button, and to delete, click the x button, up to 9 can be added Capacity can be entered in multiples of 8 in the range of 16 to 5,120, and up to 9 can be created
     Management Console	Selection	Use selection, then select the server type of Node for cluster management and monitoring, and Block Storage settings
     Management Console > Server Type	Required	Select server type for data node for cluster management and monitoring
     Management Console > Block Storage	Essential	Select the type of Block Storage to be used for data nodes for cluster management and monitoring
     Network > Common Settings	Required	Network settings for servers created by the service Select if you want to apply the same settings to all servers being installed Select pre-created VPC and Subnet IP: Enter the IP for each server Public NAT settings are only possible in server-specific settings
     Network > Server Settings	Required	Network settings for installing servers created by the service Select to apply different settings for each server being installed Select pre-created VPC and Subnet IP: Enter the IP for each server Public NAT feature is available only when the VPC is connected to the Internet Gateway, checking Use allows selection from the reserved IP in the VPC product’s Public IP. For more information, see Creating Public IP
     IP Access Control	Select	Set service access policy Set access policy for the IP entered on the page, so you don’t need to set Security Group policy separately Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32), and click the Add button To delete the entered IP, click the x button next to the entered IP
     Maintenance period	Select	DB maintenance period Use Select the day of the week, start time, and duration It is recommended to set the maintenance period for stable DB management. Patch work is performed at the set time and service interruption occurs If set to not used, SamsungSDS is not responsible for any problems that occur due to non-application of patches.

     Table. Vertica(DBaaS) Service Configuration Items

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

     Classification	Necessity	Detailed Description
     Database name	Mandatory	Server name applied when installing DB Starts with English and enters 3 to 20 characters using English and numbers
     Database username	required	DB username An account with the same name is also created in the OS Enter 2-20 characters using lowercase English letters Restricted Database usernames can be checked in the Console
     Database password	required	Password to use when accessing the DB Enter 8-30 characters including English, numbers, and special characters (excluding " ’)
     Database password confirmation	required	Re-enter the password to be used when accessing the DB
     Database Port number	required	port number required for DB connection DB port should be entered within the range of 1,024 ~ 65,535
     Backup > Use	Selection	Whether to use node backup Use is selected to select the node backup storage period and backup start time
     Backup > Retention Period	Select	Backup Retention Period Select the backup retention period. The file retention period can be set from 7 days to 35 days Backup files are charged separately depending on the capacity
     Backup > Backup start time	Select	Backup start time Select the backup start time The minutes when the backup is performed are set randomly, and the backup end time cannot be set
     License Key	Required	Enter the Vertica License Key owned by the customer If the entered license key is not valid, service creation is not possible
     DB Locale	required	Settings related to string handling, number/currency/date/time display formats, etc. to be used in Vertica(DBaaS) DB is created with the selected Locale as the default setting
     Time Zone	Required	Standard time zone to use for Vertica (DBaaS)

     Fig. Essential configuration items for Vertica(DBaaS)

   • Enter Additional Information Please enter or select the required information in the area.

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

     Fig. Vertica(DBaaS) additional information input items

4. In the Summary panel, check the detailed information generated and the estimated billing amount, and click the Complete button.

   • Once creation is complete, check the created resource on the Resource List page.

Check detailed information about Vertica(DBaaS)

The Vertica(DBaaS) service allows you to check and modify the entire resource list and detailed information. The Vertica(DBaaS) details page consists of details, tags, and operation history tabs.

To check the detailed information of the Vertica(DBaaS) service, follow the next procedure.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. Service Home page, click the Vertica(DBaaS) menu. It moves to the Vertica(DBaaS) list page.
3. Vertica(DBaaS) list page, click on the resource to check the detailed information. Move to the Vertica(DBaaS) details page.
   • Vertica(DBaaS) Details page top shows status information and additional features.

Detailed Information

On the Vertica(DBaaS) list page, you can check the detailed information of the selected resource and modify the information if necessary.

Tag

On the Vertica(DBaaS) list page, you can check the tag information of the selected resource, and add, change, or delete it.

Work History

You can check the operation history of the selected resource on the Vertica(DBaaS) list page.

Managing Vertica (DBaaS) Resources

If you need to change the existing setting options of the generated Vertica(DBaaS) resource or add storage configuration, you can perform the task on the Vertica(DBaaS) details page.

Operating Control

If there are changes to the running Vertica (DBaaS) resource, you can start, stop, and restart it.

To control the operation of Vertica(DBaaS), follow the next procedure.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. Service Home page, click the Vertica(DBaaS) menu. It moves to the Vertica(DBaaS) list page.
3. Click the resource to control operation on the Vertica(DBaaS) list page. It moves to the Vertica(DBaaS) detail page.
4. Check the status of Vertica(DBaaS) and complete the change through the control button below.
   • Start: The server where the Vertica(DBaaS) service is installed and the Vertica(DBaaS) service is running.
   • 중지: Vertica(DBaaS) service installed server and Vertica(DBaaS) service will be stopped.
   • Restart: Only the Vertica (DBaaS) service will be restarted.

Synchronizing Service Status

You can synchronize the real-time service status of Vertica(DBaaS).

To check the service status of Vertica(DBaaS), follow the next procedure.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. Service Home page, click the Vertica(DBaaS) menu. It moves to the Vertica(DBaaS) list page.
3. Click the resource to check the service status on the Vertica(DBaaS) list page. It moves to the Vertica(DBaaS) details page.
4. Service Status Synchronization button should be clicked. During the inquiry, the cluster changes to Synchronizing status.
5. Once the query is complete, the status in the server information item is updated, and the cluster changes to Running status.

Changing the Server Type

You can change the configured server type.

To change the server type, follow these steps.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. Service Home page, click the Vertica(DBaaS) menu. Move to the Vertica(DBaaS) list page.
3. On the Vertica(DBaaS) list page, click the resource you want to change the server type for. It moves to the Vertica(DBaaS) details page.
4. Click the Edit icon of the server type you want to change at the bottom of the detailed information. The Server Type Edit popup window opens.
5. Modify Server Type In the modify server type popup window, select the server type and click the OK button.

Adding Storage

If you need more than 5 TB of data storage space, you can add storage. If it is a high-availability configuration (HA cluster), adding or expanding storage capacity will be applied to all DBs simultaneously.

To add storage, follow these steps.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. Service Home page, click the Vertica(DBaaS) menu. It moves to the Vertica(DBaaS) list page.
3. On the Vertica(DBaaS) list page, click the resource to add storage. It moves to the Vertica(DBaaS) details page.
4. Click the Disk 추가 button at the bottom of the detailed information. The 추가 스토리지 요청 popup window will open.
5. In the Additional Storage Request popup window, enter the purpose and capacity, then click the Confirm button.

Expanding Storage

The storage added to the data area can be expanded up to a maximum of 5TB based on the initially allocated capacity. Storage can be expanded without stopping Vertica (DBaaS), and if configured in a cluster, all nodes are expanded simultaneously.

To increase the storage capacity, follow the procedure below.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. On the Service Home page, click the Vertica(DBaaS) menu. It moves to the Vertica(DBaaS) list page.
3. On the Vertica(DBaaS) list page, click the resource you want to change the server type for. It moves to the Vertica(DBaaS) details page.
4. Click the Modify button of the additional Disk you want to add at the bottom of the detailed information. The Modify Additional Storage popup window will open.
5. Modify Additional Storage popup window, enter the expansion capacity, then click the Confirm button.

Change Recovery DB instance type

After DB recovery is complete, you can change the instance type from the Recovery detailed information screen.

To change the Recovery DB instance type, follow these steps.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. On the Service Home page, click the Vertica(DBaaS) menu. It moves to the Vertica(DBaaS) list page.
3. Vertica(DBaaS) list page, click the resource to change the Recovery DB instance type. It moves to the Vertica(DBaaS) details page.
4. Click the Change Instance Type button. The Change Instance Type confirmation window will be displayed.

• The DB instance type is changed from Recovery to Active to perform the same function as a single DB.

Canceling Vertica(DBaaS)

You can cancel unused Vertica(DBaaS) to reduce operating costs. However, when canceling the service, the operating service may be stopped immediately, so you should consider the impact of stopping the service sufficiently before proceeding with the cancellation work.

To cancel Vertica(DBaaS), follow these steps.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. Service Home page, click the Vertica(DBaaS) menu. Move to the Vertica(DBaaS) list page.
3. Vertica(DBaaS) list page, select the resource to be canceled and click the Service Cancellation button.
4. Once the cancellation is complete, check if the resource has been cancelled on the Vertica(DBaaS) list page.

3.2.1 - Vertica Backup and Recovery

Users can set up backups of Vertica (DBaaS) through the Samsung Cloud Platform Console and restore from the backed-up files.

Vertica(DBaaS) Backup

You can set up a backup function so that the user’s data can be stored safely. Also, through the backup history function, you can verify whether the backup was performed correctly and you can also delete backed-up files.

Set up backup

For backup configuration of Vertica(DBaaS), see Create Vertica(DBaaS).

To modify the backup settings of Vertica (DBaaS), follow the steps below.

1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. Navigate to the Service Home page of Vertica(DBaaS).
2. Click the Vertica(DBaaS) menu on the Service Home page. Navigate to the Vertica(DBaaS) List page.
3. Click the resource to set backup on the Vertica(DBaaS) List page. You will be taken to the Vertica(DBaaS) Details page.
4. Click the Edit button of the backup item. Backup Settings popup window opens.
5. When setting up a backup, click Use in the Backup Settings popup, select the retention period and backup start time, and click the Confirm button.
   • If you want to stop the backup setting, uncheck Use in the Backup Setting popup window and click the Confirm button.

Check backup history

To view the backup history, follow these steps.

1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. Go to the Service Home page of Vertica(DBaaS).
2. Click the Vertica(DBaaS) menu on the Service Home page. Navigate to the Vertica(DBaaS) list page.
3. Click the resource to view the backup history on the Vertica(DBaaS) 목록 page. Go to the Vertica(DBaaS) 상세 page.
4. Click the Backup History button. Backup History popup opens.
5. Backup History In the popup window, you can check the backup status, version, backup start date and time, backup completion date and time, and size.

Delete backup file

To delete the backup history, follow the steps below.

1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. Navigate to the Service Home page of Vertica(DBaaS).
2. Service Home page, click the Vertica(DBaaS) menu. Go to the Vertica(DBaaS) list page.
3. Vertica(DBaaS) List On the page, click the resource to view the backup history. Vertica(DBaaS) Details You will be taken to the page.
4. Click the Backup History button. The Backup History popup window opens.
5. Backup History In the popup window, check the file you want to delete, then click the Delete button.

Vertica(DBaaS) Recover

If restoration from a backup file is required due to a failure or data loss, you can use the cluster recovery feature to recover based on a specific point in time.

Vertica (DBaaS)를 복구하려면 다음 절차를 따르세요.

1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. Navigate to the Service Home page of Vertica(DBaaS).
2. Click the Vertica(DBaaS) menu on the Service Home page. Go to the Vertica(DBaaS) List page.
3. Vertica(DBaaS) Resource On the list page, click the resource you want to recover. You will be taken to the Vertica(DBaaS) Detail page.
4. Click the Database Recovery button. Go to the Database(DBaaS) Recovery page.
5. Database Recovery area, after entering the relevant information, click the Complete button.

   Category	Required or not	Detailed description
   Recovery Type	Required	Set the point in time the user wants to recover Backup point (recommended): Recover based on backup file. Select from the list of backup file timestamps displayed in the list Recovery point: Choose the date and time to recover. Can be selected from the start time of the backup history
   Server Name Prefix	Required	Recovery DB Server Name Enter 3~16 characters starting with a lowercase English letter, using lowercase letters, numbers, and the special character (-) A postfix such as 001, 002 is appended based on the server name to create the actual server name
   Cluster Name	Required	Recovery DB Cluster Name Enter using English, 3 to 20 characters A cluster is a unit that groups multiple servers
   Number of nodes	Select	Number of data nodes Set to be the same as the number of nodes configured in the original cluster.
   Service Type > Server Type	Required	Recovery DB Server Type Standard: Standard specifications commonly used High Capacity: Large-capacity server of 24 vCore or more
   Service Type > Planned Compute	Select	Status 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 For details, refer to Planned Compute Apply
   Service Type > Block Storage	Required	Block Storage settings used by the recovery DB Base OS: Area where the DB engine is installed DATA: Storage area for table data, archive files, etc. Apply the same Storage type as set in the source cluster After selecting Use, enter the storage purpose and capacity Click the + button to add storage, and the x button to delete Capacity can be entered in multiples of 8 within the range 16 to 5,120, and up to 9 can be created
   Management Console > Server Type	Required	Management Console Server Type After selecting Use, choose the storage purpose and capacity Standard: Standard specifications commonly used High Capacity: Large-capacity server with 24 vCore or more
   Management Console > Block Storage	Required	Block Storage settings used by Management Console Select Use and then select Base OS
   Database username	Required	Database username Apply the same username set in the original cluster
   Database Password	Required	Database Password Apply the same password set in the original cluster
   Database Port Number	Required	Database Port Number Apply the same Port number as set in the original cluster
   IP Access Control	Select	Service Access Policy Settings Since the access policy is set for the IP entered on the page, you do not need to separately configure Security Group policies. Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32) and click the Add button To delete an entered IP, click the x button next to the entered IP
   Maintenance period	Select	DB maintenance period If Use is selected, set day of week, start time, and duration It is recommended to set a maintenance period for stable DB management. Patch work will be performed at the set time, causing service interruption If set to not use, Samsung SDS is not responsible for issues arising from unapplied patches.
   License Key	Required	Enter the Vertica License Key to recover If the entered license key is not valid, service creation is not possible
   Tag	Select	Add Tag Add Tag button click after entering or selecting Key, Value values

   Table. Vertica(DBaaS) Recovery Configuration Items

3.3 - API Reference

3.4 - CLI Reference

3.5 - Release Note

Vertica(DBaaS)

4 - Data Flow

4.1 - Overview

Service Overview

Data Flow is a data processing flow tool that extracts large amounts of data from various data sources and visually creates a processing flow for transformation/transmission of stream/batch data, providing open-source Apache NiFi. Data Flow can be used independently in the Kubernetes Engine cluster environment of the Samsung Cloud Platform or with other application software.

Provided Features

Data Flow provides the following functions.

• Easy installation and management: Data Flow can be easily installed through the web-based Samsung Cloud Platform Console in a standard Kubernetes cluster environment. Based on open-source Apache NiFi, it automatically configures the architecture required for extensible clustering, and automatically installs ZooKeeper, Registry, and management modules. Through Data Flow, you can set up and deploy the setting files, NiFi templates, etc. required for service connection.
• Easy Data Flow Management: The processing flow of stream/batch data can be easily written in a GUI-based manner tailored to the user environment, and efficient data extraction/transmission/processing between systems is possible with GUI-based data flow writing.
• NiFi Template Gallery: You can share/distribute reference NiFi templates. Data Flow provides a gallery of work files for data processing flows frequently used in the field, and users can share their own data processing flow tasks.

Component

Data Flow is composed of Manager and Service modules, and provides Apache NiFi as a package.

Data Flow Manager

Data Flow Manager provides various managing functions to utilize NiFi more efficiently.

• Through Data Flow Manager, customers can upload the Nar File they created and use it in the Processor, and upload setting files to share them.
• Among NiFi templates, high-frequency templates are assetized and provided as a gallery, and can be used immediately with just one click.
• Provides real-time monitoring and resource status monitoring for multiple services configured for Native NiFi Service.
• You can easily provision setting information for NiFi configuration components within the cluster.

Data Flow Service

• It provides a data flow management service based on Apache NiFi.
• It automatically configures the architecture required for extensible clustering based on Apache NiFi, and Nifi, ZooKeeper, Nifi Registry modules are automatically installed.
• When providing Nifi, you can set Description, resource size, access ID/PW, and Host Alias.
• After creating the service, you can modify the Description, necessary resource size, access password, Host Alias, etc. and reflect them in the service.

Server spec type

When creating a Data Flow service, please check the following contents.

• Recommended Service Installation Specifications: CPU 21 core, Memory 57 GB, storage 100 GB or more

Regional Provision Status

Data Flow is available in the following environments.

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.

4.2 - How-to guides

The user can enter the essential information of Data Flow through the Samsung Cloud Platform Console and create the service by selecting detailed options.

Creating Data Flow

You can create and use the Data Flow service in the Samsung Cloud Platform Console.

To create a Data Flow, follow the next procedure.

1. Click on the menu for all services > Data Analytics > Data Flow. It moves to the Service Home page of Data Flow.

2. On the Service Home page, click the Create Data Flow button. It moves to the Create Data Flow page.

3. Data Flow Creation page where you enter the information needed to create a service and select detailed options.

   • Version Selection area, please select the necessary information.

     Division	Necessity	Detailed Description
     Data Flow version	required	Select version of the selected image Provide a list of versions of the server image provided

     Fig. Data Flow version selection items

   • Cluster Selection area, please enter or select the required information. To install Data Flow, creating nodes for the Kubernetes cluster and a workspace is required first.

     Classification	Necessity	Detailed Description
     Cluster Name	Required	Select Cluster to Use
     Ingress Controller	Required	Select the Ingress Controller installed in the cluster In the Details tab of the installed Ingress Controller, add the following information to the ConfigMap item: Key: allow-snippet-annotations Value: true
     Fig. Data Flow cluster selection items

   • Service Information Input area, please enter or select the necessary information.

     Classification	Necessity	Detailed Description
     Data Flow name	required	Enter Data Flow name Start with lowercase English letters and do not end with a special character (-), using lowercase English letters, numbers, and special characters (-) to input 3 ~ 30 characters
     Storage Class	Required	Select the storage class used by the chosen cluster
     Description	Select	Enter additional information or description about the Data Flow within 150 characters
     Domain setting	Mandatory	Enter Data Flow domain Start with lowercase English letters and do not end with a special character (-), using lowercase letters, numbers, and special characters (-) to input 3 to 50 characters {Data Flow name}.{set domain} will be the Data Flow access address.
     Node Selector	Required	To install on a specific node, enter a distinguishable label from the node’s labels If the node label is entered incorrectly, an installation error may occur, so check the node label in advance The node label can be checked in the yaml file of the corresponding node
     Account	Required	Enter Data Flow Manager account ID: Starts with lowercase English letters and uses lowercase letters and numbers to enter a value between 6 and 30 Password: Includes uppercase (English), lowercase (English), numbers, and special characters (!@#$%^&*) and enter 8 to 50 characters Password Confirmation: Enter the password exactly once more
     Host Alias	Selection	Add host information to be connected to Data Flow (up to 20 can be created, including default) Select “Use”, then click the + button Hostname: Enter in hostname or domain format, using lowercase, numbers, and special characters (-) with 3-63 characters IP: Enter in IP format To delete, click the X button The firewall between the cluster and the server must be open to use the added host information
     Fig. Data Flow service information input items

   • Enter Additional Information area, please enter or select the necessary information.

     Division	Necessity	Detailed Description
     Tag	Selection	Tag addition Tag addition button to create and add tags or add existing tags possible Up to 50 tags can be added Newly added tags are applied after service creation is complete

     Fig. Data Flow Additional Information Input Items

4. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.

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

Check Data Flow Detailed Information

You can check and modify the list of all resources and detailed information of Data Flow. The Data Flow details page consists of detailed information, tags, and work history tabs.

To check the detailed information of Data Flow, follow the next procedure.

1. Click on the menu for all services > Data Analytics > Data Flow. It moves to the Service Home page of Data Flow.
2. On the Service Home page, click the Data Flow menu. It moves to the Data Flow list page.
3. Data Flow list page, click on the resource to check the detailed information. It moves to the Data Flow details page.
   • Data Flow Details page top shows status information and additional function information.

Detailed Information

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

Tag

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

Work History

You can check the work history of the selected resource on the Data Flow list page.

Data Flow cancellation

You can cancel unused Data Flow to reduce operating costs. However, if you cancel the service, the operating service may be stopped immediately, so you should consider the impact of stopping the service sufficiently before proceeding with the cancellation work.

To cancel Data Flow, follow the next procedure.

1. Click on the menu for all services > Data Analytics > Data Flow. It moves to the Service Home page of Data Flow.
2. Service Home page, click the Data Flow menu. It moves to the Data Flow list page.
3. Data Flow list page, select the resource to be canceled and click the Service Cancellation button.
4. Once the cancellation is complete, check the Data Flow list page to see if the resource has been cancelled.

4.2.1 - Data Flow Services

The user can enter the essential information of Data Flow Services in the Data Flow service through the Samsung Cloud Platform Console and create the service by selecting detailed options.

Create Data Flow Services

The user can add a service by selecting the detailed options of the Data Flow service or entering the setting value.

To create Data Flow Services, follow these steps.

1. Click all services > Data Analytics > Data Flow menu. It moves to Data Flow Service Home page.

2. On the Service Home page, click Data Flow Services. It moves to the Data Flow Services list page.

3. On the Data Flow Services list page, click the Create Data Flow Services button. It moves to the Create Data Flow Services page.

4. Data Flow Services Creation page, enter the information required for service creation and select detailed options.

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

     Classification	Necessity	Detailed Description
     Data Flow name	required	Data Flow selection
     Flow Service name	Required	Enter Data Flow Services name Start with lowercase English letters and do not end with a special character (-), use lowercase letters, numbers, and special characters (-) to enter 3 to 30 characters
     Storage Class	Required	Select the storage class used by the selected cluster
     Description	Select	Enter additional information or description about Data Flow Services within 150 characters
     Domain Setting	Mandatory	Enter the Data Flow Services domain Start with lowercase English letters and do not end with a special character (-), use lowercase letters, numbers, and special characters (-) to input 3 ~ 50 characters {Data Flow Services name}.{set domain} will be the Data Flow Services access address.
     Node Selector	Required	To install on a specific node, enter a distinguishable Label from the node’s Labels If the node Label is entered incorrectly, an installation error may occur, so check the node Label in advance The node Label can be checked in the yaml file of the corresponding node
     Service Workload	Required	Nifi: A module that provides Apache Nifi services and UI Nifi Registry: A module for setting and deploying Nifi templates Zookeeper: A module that supports distributed processing of Nifi in multiple nodes
     Account	Required	Enter Nifi account ID: Enter a value between 6 and 30 characters, starting with a lowercase letter and using lowercase letters and numbers Password: Enter a value of 8 to 50 characters, including uppercase letters (English), lowercase letters (English), numbers, and special characters (!@#$%^&*) Password Confirmation: Enter the password again, identical to the previous entry

     Fig. Data Flow Services Service Information Input Items

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

     Classification	Necessity	Detailed Description
     Host Alias	Selection	Add host information to be connected to Data Flow (up to 20 can be created, including default) Use is selected and then + button is clicked Hostname: in the form of hostname or domain, using lowercase letters, numbers, and special characters (-) to enter 3 ~ 63 characters IP: enter in IP format click the X button to delete the firewall between the cluster and the corresponding server must be open to use the added host information
     Tag	Selection	Add tag Add tag button to create and add tags or add existing tags Up to 50 tags can be added Newly added tags are applied after service creation is completed

     Fig. Data Flow Additional Information Input Items

5. In the Summary panel, review the detailed information and estimated charges, and click the Complete button.

   • Once creation is complete, check the created resource on the Data Flow Services list page.

Data Flow Services detailed information check

You can check and modify the list of all resources and detailed information of Data Flow Services. The Data Flow Services details page consists of details, tags, and operation history tabs.

To check the detailed information of Data Flow Services, follow the next procedure.

1. 모든 서비스 > Data Analytics > Data Flow menu should be clicked. It moves to the Service Home page of Data Flow.
2. Service Home page, click the Data Flow Services menu. It moves to the Data Flow Services list page.
3. Data Flow Services list page, click on the resource to check the detailed information. Move to the Data Flow Services details page.
   • Data Flow Services Details page displays status information and additional features at the top.

Detailed Information

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

Tag

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

Work History

You can check the operation history of the selected resource on the Data Flow Services list page.

Cancel Data Flow Services

You can cancel unused Data Flow Services to reduce operating costs. However, when canceling a service, the operating service may be stopped immediately, so you should consider the impact of stopping the service sufficiently before proceeding with the cancellation work.

To cancel Data Flow or Data Flow Services, follow the procedure below.

1. Click All Services > Data Analytics > Data Flow menu. It moves to the Service Home page of Data Flow.
2. Service Home page, click the Data Flow Services menu. Move to the Data Flow Services list page.
3. Data Flow Services list page, select the resource to be canceled and click the Data Flow Services delete button.
4. Once the cancellation is complete, please check if the resource has been cancelled on the Data Flow Services list page.

4.2.2 - Installing Ingress Controller

The user must install the Ingress Controller before creating the Data Flow service. Only one Ingress Controller must be installed in a Kubernetes cluster.

Install Ingress Controller using Container Registry

To install Ingress Controller using Container Registry, follow the procedure below.

1. Prepare the SCR (Samsung Container Registry) to store the Ingress Controller image.
2. Push the Ingress Controller image to SCR(Samsung Container Registry).
3. Download the YAML file used for installation from Ingress GitHub and modify the following items.

kind: Deployment
...
spec:
  template:
    spec:
      containers:
        image: {SCR private endpoint}.{repository name}.{image name}:{tag}

kind: Deployment
...
spec:
  template:
    spec:
      containers:
        image: {SCR private endpoint}.{repository name}.{image name}:{tag}

kind: ConfigMap
...
metadata:
  labels:
    app: ingress-controller

kind: Service
...
metadata:
  labels:
    app: ingress-controller

kind: Deployment
...
metadata:
  labels:
    app: ingress-controller

kind: IngressClass
...
metadata:
  labels:
    app: ingress-controller

kind: ConfigMap
...
metadata:
  labels:
    app: ingress-controller

kind: Service
...
metadata:
  labels:
    app: ingress-controller

kind: Deployment
...
metadata:
  labels:
    app: ingress-controller

kind: IngressClass
...
metadata:
  labels:
    app: ingress-controller

4. You can install the Ingress Controller using the Create Object button in the Workloads > Deployments list in Kubernetes Engine using the modified YAML file.

4.3 - API Reference

4.4 - CLI Reference

4.5 - Release Note

Data Flow

5 - Data Ops

5.1 - Overview

Service Overview

Data Ops is a managed workflow orchestration service based on Apache Airflow that writes workflows for periodic or repetitive data processing tasks and automates task scheduling. Users can automate the process of bringing useful data to the right place at the right time, and monitor the configuration and progress of data pipelines.

Provided Features

Data Ops provides the following functions.

• Easy installation and management: Data Ops can be easily installed through a web-based Console in a standard Kubernetes cluster environment. Apache Airflow and management modules are automatically installed, and integrated monitoring of the execution status of web servers and schedulers is possible through an integrated dashboard.
• Dynamic Pipeline Composition: Pipeline composition for data tasks is possible based on Python code. Since it dynamically generates tasks in conjunction with data task scheduling, you can freely compose the desired workflow form and scheduling.
• Convenient workflow management: DAG (Direct Acyclic Graph: directed acyclic graph) configuration is visualized and managed through a web-based UI, making it easy to understand the data flow’s preceding and parallel relationships. Additionally, each task’s timeout, retry count, priority definition, etc. can be easily managed.

Component

Data Ops consists of Manager and Service modules, and provides Apache Airflow by packaging it.

Data Ops Manager

Data Ops Manager provides various managing functions to use Airflow more efficiently.

• You can upload Plugin File, Shared File, Python Library File to be used in Ops Service through Ops Manager.
• You can easily provision setting information for Airflow configuration components within the cluster.
• You can manage and easily provision different service settings within the Airflow cluster.

Data Ops Service

• Provides a managed workflow orchestration service based on Apache Airflow.
• When Airflow is provided, you can set Description, necessary resource size, DAGs GitSync, and Host Alias.
• After creating a service, you can modify Description, resource usage, DAGs GitSync, and Host Alias to reflect the service.

Server Spec Type

When creating a Data Ops service, please check the following contents.

• Recommended Service Installation Specifications: CPU KubernetesExecutor 43 core, CPU CeleryExecutor 25 core, Memory 50 GB, storage 100 GB or more

Regional Provision Status

Data Ops is available in the following environments.

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.

5.2 - How-to guides

The user can enter the essential information of Data Ops through the Samsung Cloud Platform Console and create the service by selecting detailed options.

Create Data Ops

You can create and use the Data Ops service on the Samsung Cloud Platform Console.

To create Data Ops, follow the following procedure.

1. Click on the menu for all services > Data Analytics > Data Ops. It moves to the Service Home page of Data Ops.

2. On the Service Home page, click the Create Data Ops button. It moves to the Create Data Ops page.

3. Data Ops Creation page, enter the information required for service creation and select detailed options.

   • Version Selection area, please select the necessary information.

     Classification	Necessity	Detailed Description
     Data Ops version	required	Select version of the selected image Provide a list of versions of the provided server image

     Table. Data Ops version selection items

   • Cluster Selection area, please enter or select the required information. To install Data Ops, it is necessary to create nodes for the Kubernetes cluster and the working environment first.

     Classification	Mandatory	Detailed Description
     Cluster Name	Required	Select Cluster to Use
     Ingress Controller	required	Select the Ingress Controller installed in the cluster

     Fig. Data Ops Cluster Selection Items

   • Enter Service Information area, please enter or select the necessary information.

     Classification	Necessity	Detailed Description
     Data Ops name	required	Enter Data Ops name Start with lowercase English letters and do not end with special characters (-), use lowercase letters, numbers, and special characters (-) to enter 3 ~ 30 characters
     Storage Class	Required	Select the storage class used by the selected cluster
     Description	Optional	Enter additional information or description about Data Ops within 150 characters
     Domain Setting	Mandatory	Enter Data Ops domain Start with lowercase English letters and do not end with a special character (-), use lowercase letters, numbers, and special characters (-) to enter 3 to 50 characters {Data Ops name}.{set domain} will be the Data Ops access address.
     Node Selector	Required	To install on a specific node, enter a distinguishable Label from the node’s Labels If the node Label is entered incorrectly, an installation error may occur, so check the node Label in advance The node Label can be checked in the yaml file of the corresponding node
     Account	Required	Enter Data Ops Manager account ID: Enter a value between 6 and 30 characters, starting with a lowercase English letter and using only lowercase letters and numbers Password: Enter a value between 8 and 50 characters, including uppercase letters (English), lowercase letters (English), numbers, and special characters (!@#$%^&*) Password Confirmation: Enter the password again, identical to the previous entry
     Host Alias	Selection	Add host information to be connected to Data Ops (up to 20 can be created, including default) Select “Use” and click the + button Hostname: Enter in hostname or domain format, using lowercase letters, numbers, and special characters (-) in 3-63 characters IP: Enter in IP format To delete, click the X button The firewall between the cluster and the corresponding server must be open to use the added host information

     Fig. Data Ops Service Information Input Items

   • Enter Additional Information Enter or select the required information in the area.

     Classification	Necessity	Detailed Description
     Tag	Select	Add Tag Add Tag button to create and add tags or add existing tags Up to 50 tags can be added Newly added tags will be applied after service creation is complete

     Fig. Data Ops Additional Information Input Items

4. In the Summary panel, review the detailed information and estimated charges, and then click the Complete button.

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

Data Ops detailed information check

You can check and modify the full list of Data Ops resources and detailed information. The Data Ops details page consists of detailed information, tags, and work history tabs.

To check the detailed information of Data Ops, follow the next procedure.

1. 모든 서비스 > Data Analytics > Data Ops menu should be clicked. It moves to the Service Home page of Data Ops.
2. Service Home page, click the Data Ops menu. It moves to the Data Ops list page.
3. Data Ops list page, click on the resource to check the detailed information. It moves to the Data Ops details page.
   • Data Ops Details page top shows status information and additional function information.

Detailed Information

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

Tag

On the Data Ops list page, you can check the tag information of the selected resource, and add, change, or delete it.

Work History

You can check the work history of the selected resource on the Data Ops list page.

Cancel Data Ops

You can cancel unused Data Ops to reduce operating costs. However, if you cancel the service, the operating service may be stopped immediately, so you should consider the impact of stopping the service sufficiently before proceeding with the cancellation work.

To cancel Data Ops, follow the procedure below.

1. Click All Services > Data Analytics > Data Ops menu. It moves to the Service Home page of Data Ops.
2. On the Service Home page, click the Data Ops menu. It moves to the Data Ops list page.
3. Data Ops list page, select the resource to be canceled and click the Service Cancellation button.
4. Once the cancellation is complete, please check if the resource has been cancelled on the Data Ops list page.

5.2.1 - Data Ops Services

Users can enter essential information for Data Ops Services within the Data Ops service and create the service by selecting detailed options through the Samsung Cloud Platform Console.

Create Data Ops Services

The user can add a service by selecting detailed options for Data Ops or entering setting values.

To create Data Ops Services, follow the procedure below.

1. Click on the menu for all services > Data Analytics > Data Ops. It moves to the Service Home page of Data Ops.

2. On the Service Home page, click Data Ops Services. It moves to the Data Ops Services list page.

3. On the Data Ops Services list page, click the Create Data Ops Services button. It moves to the Create Data Ops Services page.

4. Data Ops Services Creation page, enter the information required for service creation and select detailed options.

   • Enter Service Information area, enter or select the required information.

     Division	Necessity	Detailed Description
     Data Ops Name	Required	Data Ops Selection
     Ops Service Name	Required	Enter Data Ops Services name Start with lowercase English letters and do not end with a special character (-), use lowercase letters, numbers, and special characters (-) to input 3 ~ 30 characters
     Storage Class	Required	Select the storage class used by the chosen cluster
     Description	Optional	Enter additional information or description about Data Ops Services within 150 characters
     Domain setting	Mandatory	Enter Data Ops Services domain Start with lowercase English letters and do not end with a special character (-), use lowercase letters, numbers, and special characters (-) to input 3 ~ 50 characters {Data Ops Services name}.{set domain} will be the Data Ops Services access address.
     Node Selector	Required	To install on a specific node, enter a distinguishable label from the node’s labels If the node label is entered incorrectly, an installation error may occur, so check the node label in advance Node labels can be checked in the yaml file of the corresponding node
     Service Workload	Required	Web Server: Provides visualization of DAG components and status, and Airflow configuration management module Scheduler: Manages scheduling and execution of various DAGs and tasks for orchestration Worker: Performs actual orchestration and data processing tasks Worker(Kubernetes): Dynamically creates and runs pods when worker conditions are met, allowing for efficient resource usage. The Replica text box is disabled when Kubernetes is selected. Worker(Celery): Creates and maintains static pods when worker conditions are met, allowing for faster performance with large requests. The Replica text box is enabled and user input is allowed when Celery is selected. The type of executor chosen cannot be changed once selected
     Account	Required	Enter Airflow account ID: Starts with lowercase English letters and uses lowercase letters and numbers to enter a value between 6 and 30 characters Password: Includes uppercase (English), lowercase (English), numbers, and special characters (!@#$%^&*) and enters 8 to 50 characters Password Confirmation: Enter the password again
     Table. Data Ops Services service information input items

   • Enter Additional Information area, enter or select the required information.

     Classification	Necessity	Detailed Description
     Host Alias	Selection	Add host information to be connected to Data Ops (up to 20 can be created, including default) Select “Use” and click the + button Hostname: Enter in hostname or domain format, using lowercase letters, numbers, and special characters (-) with 3 ~ 63 characters IP: Enter in IP format To delete, click the X button The firewall between the cluster and the server must be open to use the added host information
     Tag	Selection	Tag addition Tag addition button to create and add tags or add existing tags possible Up to 50 tags can be added Newly added tags are applied after service creation is complete

     Fig. Additional Data Ops information input items

5. In the Summary panel, review the detailed information and estimated charges, then click the Complete button.

   • Once creation is complete, check the created resource on the Data Ops Services list page.

Data Ops Services detailed information check

You can check and modify the full list of Data Ops Services resources and detailed information. The Data Ops Services details page consists of details, tags, and work history tabs.

To check the details of Data Ops Services, follow the next procedure.

1. Click on the menu for all services > Data Analytics > Data Ops. It moves to the Service Home page of Data Ops.
2. On the Service Home page, click the Data Ops Services menu. It moves to the Data Ops Services list page.
3. Data Ops Services list page, click on the resource to check the detailed information. It moves to the Data Ops Services details page.
   • Data Ops Services Details page top shows status information and additional features.

Detailed Information

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

Tag

On the Data Ops Services list page, you can check the tag information of the selected resource and add, change, or delete it.

Work History

You can check the operation history of the selected resource on the Data Ops Services list page.