Multi-cluster provisioning and managing method on cloud platform

Multi-cluster provisioning and managing method on cloud platform}

The present invention relates to a multi-cluster provisioning and management method in a cloud platform, and more particularly, it is possible to automatically create a multi-cluster environment in which container-based applications can operate in various infrastructures, and remotely manage the cluster version upgrade. It relates to a multi-cluster provisioning and management method on a cloud platform that can improve operational efficiency.

Cloud is referred to as 'service provider's server' according to the practice of displaying computing service provider servers in a cloud shape. Software and data are stored in a central computer connected to the Internet, and data can be accessed anytime, anywhere as long as the Internet is connected.

Depending on the type of service provision, such cloud is an application service that is provided on-demand to multiple users such as Salesforce.com·Google e-mail, etc., such as Software as a Service (SaaS), AWS RDS·Google AppEngine, etc. It can be divided into Platform as a Service (PaaS), which is a software stack required to run a development platform or application, and Infrastructure as a Service (IaaS), which provides servers or storage as a service to users, such as AWS EC2.

In addition, depending on the type of introduction and deployment, the cloud is a private cloud that operates only for one organization, a public cloud that is rendered through a network open for public use, and two that maintain a distinct entity but are tied together. It can be divided into hybrid cloud, which is a combination of the above clouds.

On the other hand, in the case of Enterprise Cloud, it is the cloud that implements the company's business and IT strategy. It is most important to customize and optimize technology and infrastructure centering on application services, and it is also easy to configure or deploy applications to various infrastructures. shall.

<p><patcit num="0001"><text>Republic of Korea Patent Publication No. 10-2015-0142871 (published on December 23, 2015)</text></patcit></p>

<p>Accordingly, the present invention was created to solve the above problems, and it is possible to automatically create a multi-cluster environment in which container-based applications can operate in various infrastructures, and to remotely manage the version upgrade of the cluster to improve operational efficiency. Its purpose is to provide a multi-cluster provisioning and management method on a cloud platform. </p><p>However, the technical problems of the present invention are not limited to the above-mentioned problems, and other technical problems not mentioned will be clearly understood by those skilled in the art from the following description.</p>

<p>In the multi-cluster provisioning and management method in a cloud platform according to an embodiment of the present invention, when provisioning of a plurality of clusters in which a container-based application can operate in a multi-cloud environment is requested, the cloud platform system collects type information of each of the clusters allowing input; generating, by the cloud platform system, configuration information of each of the clusters when the type information of the cluster is input; when the public cloud or system access information is registered, confirming whether the cloud platform system creates or changes each of the clusters; if the cluster is created, the cloud platform system requests and configures instances, networks, and storage creation, installs container runtime software, sets configuration information of the cluster, and performs remote simultaneous provisioning of the cluster; and if the cluster is to be changed, the cloud platform system checks configuration history information of the cluster and updates the configuration of the cluster to remotely change the cluster; adding, by the cloud platform system, a node in the cluster or replacing a failed node, and backing up a node in the cluster; and performing, by the cloud platform system, automatic scaling of the cluster, wherein the cluster configuration information includes at least one of the number of instances, instance specifications (GPU, memory type), network configuration information, and storage configuration information. .</p>

<p>The multi-cluster provisioning and management method in the cloud platform according to the present invention can automatically create a multi-cluster environment in which container-based applications can operate on various infrastructures, and can remotely manage cluster version upgrades to improve operational efficiency. have an effect </p>

1 shows a configuration diagram of a cloud platform system according to an embodiment of the present invention. FIG. 2 schematically illustrates the function of the cloud integrator of FIG. 1 . FIG. 3 is a diagram schematically illustrating a function of the service management unit of FIG. 1 . FIG. 4 schematically illustrates the function of the application orchestration unit of FIG. 1 . 5 shows a framework of application containerization according to an embodiment of the present invention. 6 to 11 are schematic views of the functions of the development/operation unit of FIG. 1 . 12 shows an architecture of a cloud platform system according to an embodiment of the present invention. 13 shows the configuration of a cocktail server and its surrounding architecture. 14 to 16 are diagrams for explaining a multi-cluster provisioning and management function of a cloud platform system according to an embodiment of the present invention. 17 is a flowchart illustrating a multi-cluster provisioning and management method of a cloud platform system according to an embodiment of the present invention.

Advantages and features of the present invention and methods of achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in other various forms, and only these embodiments allow the disclosure of the present invention to be complete and common knowledge in the technical field to which the present invention pertains. It is provided to fully inform the possessor of the scope of the invention, and the present invention is only defined by the claims.

Like reference numerals refer to like elements throughout.

Hereinafter, a cloud platform system according to an embodiment of the present invention will be described with reference to the accompanying drawings.

1 shows a configuration diagram of a cloud platform system according to an embodiment of the present invention, FIG. 2 briefly shows the function of the cloud integrator of FIG. 1, and FIG. 3 briefly shows the function of the service management unit of FIG. and FIG. 4 briefly illustrates the function of the application orchestration unit of FIG. 1 .

5 shows a framework of application containerization according to an embodiment of the present invention, and FIGS. 6 to 11 briefly illustrate the functions of the development/operation unit of FIG. 1 .

The cloud platform system of FIG. 1 guarantees application availability and scalability based on multi/hybrid cloud integrated management and provides views and tools for efficient development and operation. Hereinafter, the cloud platform system of the present invention is "<b>Cocktail Cloud</b>" to be called.

Referring to FIG. 1 , the cocktail cloud includes a cloud integration unit (Cloud Integration, 100), a service management unit (Service Management, 110), an application orchestration unit (Orchestration, 120), a development/operation unit (DevOps View, 140), and a DB/repository. (150).

The cloud integration unit (Cloud Integration, 100) automatically configures the infrastructure of the multi/hybrid cloud, provides it to the application, and synchronizes the configuration information for management.

The cloud integrator 100 performs functions of cloud provisioning and cloud synchronization.

Referring to FIG. 2 , the cloud provisioning function is a function of configuring and providing a cloud network infrastructure to an application cluster (cocktail cluster), and configuring and providing a cloud computing infrastructure to an application. And in the case of physical infrastructure (bare metal), a cluster configuration tool is provided. Supported clouds are AWS·Azure·Aliyun·Google Computing Engine for public, Openstack·VMWear for private, and On-premise·Datacenter BareMetal Infra can be in addition.

The cloud synchronization function is a function of storing and managing cloud infrastructure configuration information in the integrated configuration DB 160 , and synchronizing the infrastructure change information with the integrated configuration DB 160 during operation.

The service management unit (Service Management, 110) is a logical group that manages the application cluster, and performs a role of allocating and managing cloud accounts, users, and network resources. That is, the service management unit 110 performs an integrated account management function, a network management function, and a user management function.

Referring to FIG. 3 , the integrated account management (Cloud Provider) function is a function that integrates management of multi-cloud accounts and access information, and is used to configure network and cloud provisioning.

The network management function is the function of configuring cloud networks and assigning them to services. For example, it may be a VPC/Subnet of AWS. One service configures and operates an application by creating a cluster using the network of a multi-cloud provider.

The user management function is a function to manage the team members who manage the service and the rights required for development/operation. Here, the authority may include enterprise service management authority (Admin), enterprise service inquiry authority (Manager), service management authority assigned to a member (DevOps), and the like. Users can participate in various services as members.

The application orchestration unit (Orchestration, 120) is a function that guarantees application distribution, availability, and scalability, and is responsible for the core function of the cocktail cluster.

The application orchestration unit 120 performs an application deployment function, a replication control function, a rolling update function, a scaling function, and a monitoring function.

Referring to FIG. 4 , the application distribution function is a container image-based distribution, which provides ease of not requiring separate settings and configuration, and is a function of automatically provisioning cloud infrastructure when distributing applications.

Here, the application is containerized and distributed, and the application container (hereinafter referred to as "<b>container</b>") refers to an independent system on the OS virtualized by allocating and isolating host resources to application processes.

The core technologies used in containers are cgroups (control groups) and namespaces of Linux. cgroup creates a process group to allocate host resources to processes on the OS, and allocates and manages resources. A namespace is a technology that isolates processes, networks, and mounts into a specific name space. Accordingly, a container refers to an independent system virtualized on the OS that allocates resources to application processes through cgroups and is isolated by namespace.

Container is a lightweight OS virtualization method that does not use a hardware emulator and guest OS. It consumes little host resources and takes very little time to start up, so it is a suitable technology for application virtualization. In addition, with virtualization on the OS, it is possible to configure and deploy independent of infrastructure such as existing physical servers (bare metal) and virtual machines (virtual machines).

In order to convert an existing or new application configuration into a container in this way, a containerization process must be accompanied. In addition, the conversion of development, test, and operation methods and the optimization of operation infrastructure configuration (cocktail cloud platform) should be carried out in parallel.

In order to convert an existing application to a container, it is necessary to change the configuration of the application rather than the setting and source of the application. Considering the distribution and operational efficiency, the independent configuration for each role centered on the workload is common, and multiplexing and scaling through replication A configuration considering the should be designed and applied.

In order to change the application development, test, and operation method, image-based application build, test, and distribution and application configuration through a base image should be standardized.

In order to optimize the application container operation infrastructure configuration, a cluster-oriented infrastructure for container orchestration should be configured, and the computing capacity should be calculated (minimizing spare capacity, easy to expand if necessary) considering replication and scaling, and related storage, security, network, etc. You will need to configure the infrastructure.

Referring to FIG. 5 , containerization is largely divided into analysis and configuration design (S100), container conversion (S200), and operation transfer (S300).

For analysis and configuration design (S100), a container conversion target is selected among existing applications in consideration of the container/cloud introduction purpose and strategy (S110).

When the target application is selected, the target application is analyzed (S120). At this time, the application status and data such as application, infrastructure, data, and linkage structure are investigated, and the needs of development, operation, and manager are collected. And the container configuration direction, issues, and solutions are derived.

Then, the container configuration for each target application is designed in consideration of separation/integration, connection, availability, scalability, security, and the like (S130). At this time, image build templates such as base image, environment variable, included item, and command can be defined.

Thereafter, the infrastructure configuration is designed (S140). Select a transition infrastructure (cloud/bare metal) provider and calculate the capacity for each application container. In addition, the number of container cluster nodes and infrastructure capacity are calculated, and storage, network, and security configurations are designed.

When the infrastructure configuration is designed, a container conversion plan is established (S150). At this time, a detailed conversion plan for each application is established, the transition task and organization/role are defined, and the transition schedule is established. and reflect reports and feedback.

For container switching (S200), iterative/incremental switching (S210) is required. Iterative and incremental transitions, such as pre-test (PoC) and application-specific phased transitions.

In order to configure the cocktail cluster (S220), the cocktail cloud platform is installed and configured, and the infrastructure such as network, shared storage, and security is configured (provisioning in cocktail in the case of cloud). Create cocktail services and clusters through allocation of infrastructure infrastructure and user registration, and verify cluster configuration.

In addition, an application container is configured for application switching ( S230 ), and application settings and sources are changed if necessary. Verifies the functions and settings of the conversion container, builds the container deployment image and registers it in the registry. Then create and test the cocktail server.

The target application container is switched for data conversion (S240), the cocktail server is set through persistence volume setting, etc., data is extracted and transmitted to the cocktail server. In case of applying a heterogeneous DB solution, data conversion is performed and data consistency is checked. For production applications, a data synchronization solution is applied to minimize downtime.

After that, the verified container is distributed to the cocktail server, application function and performance tests are performed, and the test results are reflected in the container and infrastructure (S250, S260).

Operation distribution/opening (S310) is performed for operation transfer (S300). Specifically, an operation cocktail cluster is created, and a cocktail server is created based on the converted image and configured in connection. Then, the operation data is transferred and the application is opened. The technology for deploying, operating, and managing such application containers is called container orchestration.

Container orchestration is a technology that deploys, operates, and manages application containers by configuring a managed cluster in physical/virtual infrastructure. and private/public cloud application management platforms.

Application and infrastructure operation monitoring is performed through the cocktail cloud monitoring view and performance issues and errors are reflected (S320).

For the transfer and application of the development and operating system (S330), the result of the container transfer is reported, the development and operation organization in charge is trained on the container-based development/operating system, and the cocktail cloud platform is used.

Accordingly, the container has the following advantages.

First, containers are independent.

It is an isolated application execution environment, independent resources are allocated (CPU, Memory, Disk, Network, etc.), and multiple applications are operated on the same host.

Second, containers implement lightweight virtualization.

OS-level virtualization (Non Hypervisor) is possible, quick operation is possible (creation, execution, restart, etc.), and deployment and update are efficient with a small container image.

Third, containers have mobility.

It has an infrastructure-independent image, can be moved anywhere, including bare metal, virtual machine, and cloud, and online deployment and version management are possible through the image registry, and the main host OS (Linux) series, Windows). This container mobility increases the productivity and efficiency of application operation/development under multi/hybrid cloud environments. In particular, standardized container images solve the difficulties of application deployment and transfer to heterogeneous infrastructures, and lock-in dependent on a specific cloud. ) solves the problem.

The replication function is faster and more efficient than the OS reboot method by maintaining the initially designated number of copies (multiplexing) for application stability and availability and restarting in case of an abnormality through the application container health check. Replicated applications are serviced through load balancing.

The rolling update function performs update tasks such as distribution and infrastructure changes without interruption of application service, and when there is a dependency between multiple applications, it configures automation through the job management function of DevOps View.

The scaling function in (In)/Out (Out) the scaling of the instance through the monitoring of the application, in the case of the application infrastructure, the scale of the resource capacity up (Up) / down (Down) function. And configure scaling automation through monitoring information.

The monitoring function monitors application instances (container + infrastructure) and generates and manages alarms through threshold settings.

The development/operation department (DevOps View, 140) includes a service status function, a cluster map function, a monitoring view function, a resource management function, a metering function, a job management function, and a company-wide status management/analysis function. Each function will be described with reference to FIGS. 6 to 11 as follows.

The service status function provides a view (refer to FIG. 6) that can identify the status of the entire application cluster of Cocktail Cloud based on the service. In this way, items such as service status, cluster status, monitoring alarm, etc. may be displayed.

In the service status, the overall service status of Cocktail Cloud can be inquired, and the cloud provider, cluster, server, cloud component, current monthly usage cost, etc. can be identified by synthesizing the configuration status of the cluster within the service. Here, the cluster means the constituent unit of the application, and the service means a logical grouping of the cluster.

In the cluster status, it is possible to inquire the provider, region, server, cloud component, and monthly usage cost of the cluster in the form of a card, and in the case of a physical (bare metal) cluster, the usage cost can be excluded.

In the monitoring alarm display function, when an alarm occurs in an application or infrastructure within the cluster, it can be checked on the cluster card.

The cluster map function provides a view to visualize and manage the configuration and status information of the cocktail server (application) in the form of a map (see FIG. 7).

The cluster map enhances visibility of configuration information by inquiring/managing the configuration of the server and cloud components of the cluster in the form of a map. The cluster map can include items such as cocktail servers, cloud components, and server groups.

Cocktail Server is the basic unit of application orchestration and consists of load balancing, application container, and infrastructure, and provides a standardized interface for multi/hybrid cloud management. The cocktail server checks the application status, replication, and resource usage within the server, and manages scaling and rolling updates. Cocktail server is divided into multi-instance type and single-instance type according to the presence or absence of replication function. AWS supports a multi-zone option.

The cloud component manages the PaaS service provided by the provider. For example, it may be RDS, a DB service of AWS.

Server groups provide management convenience for logical groups of server configurations.

The monitoring view function provides information to check the resource capacity and status of applications and infrastructure in the cluster and to check the status of cloud resources (see FIG. 8 ).

Monitoring view visualizes monitoring information for applications and infrastructure in the cluster, and provides CPU, memory, disk average and TOP information to check resource usage and respond in operation.

The monitoring view may include a view conversion (trend/data) item, a target conversion (server/resource) item, and the like.

In the view conversion item, the trend view provides hourly monitoring information for the server and replicated instance/application container, and the data view provides the average and TOP monitoring figures for the current time.

In the target conversion item, the monitoring target is divided into the server in the cluster and the resource of the cloud infrastructure. Cloud resources use information provided by providers.

The resource management function allows you to check the resources of the cloud infrastructure constituting the application and adjust detailed settings if necessary<b>resource management view</b>") is provided (see FIG. 9).

In the resource management view, you can check the cloud infrastructure resources that make up the cocktail server and change the settings in detail. Here, the cocktail server automatically performs basic configuration for application orchestration, but is used when you need to manually orchestrate cloud resources if necessary.

The resource management view includes resource information/action items. Among the resource information, the application manages container settings and deployment information. Cloud resource information consists of load balancer, instance (VM), and security, and the instance manages capacity and volume. Resource information that needs adjustment is performed through actions.

The metering function is a view that can check the cost information of the cloud infrastructure resources used by the application (hereinafter referred to as "<b>metering view</b>") is provided (refer to FIG. 10). The metering view may include cluster infrastructure usage cost items, server/resource cost items, and the like.

In the cluster infrastructure usage cost item, you can check the cost status of cloud resources used by the cluster and cocktail server, and it provides cost information for the previous month and the current month and estimated cost for the next month. It also provides a graph of the cost increase and decrease by month.

The cost of each server/resource item provides the cost of cloud resources used by cocktail server based on TOP, and the cost of each type of cloud resource is provided based on the TOP.

The task management function is a management view (hereinafter referred to as "the<b>work management view</b>") is provided (see FIG. 11).

The job management view provides scheduling and batch processing functions for the operation of applications and infrastructure. Such a job management view may include a job status item, a job management item, and the like.

In the job management view, the job status items are divided into distribution, remote command, and resource management tasks, and each task is combined to form it. Here, deployment means application deployment, remote command means remote execution of OS commands, and resource management means scaling and status/configuration change.

In the task management view, the task management item can set the execution method according to immediate execution, scheduling, and alarm occurrence. Execution according to the occurrence of an alarm is used for automatic scaling according to the standard value of capacity monitoring. In the task management item, the execution status of the task and the log check are provided.

The company-wide status management/analysis function provides a cocktail dashboard that can identify and analyze company-wide application, cloud, and cost status.

The cocktail dashboard is a view that inquires the status of applications and cloud infrastructure at the enterprise level, and provides cost/budget management, cost optimization analysis, and statistical reports. This cocktail dashboard may include application status items, cloud status items, cost/budget management, cost optimization analysis items, and statistics/report items.

Through the application status item, the status of applications and infrastructure can be identified and inquired company-wide based on standardized elements of cocktail server, cluster, and cloud components, and a service-oriented status view is provided.

Through the cloud status item, it is possible to grasp the status of the cloud used by the company by provider, region, and resource, and provides an infrastructure-oriented status view.

Through cost/budget management and cost optimization analysis items, company-wide cloud cost status is identified, and cloud resource cost efficiency is provided through budget allocation/control and optimization analysis for each service.

Statistics/Report provides statistical information and report view necessary for analysis and reporting.

In the DB/repository 150, the image storage (registry) 180 manages registration, sharing, download, search, and versioning of application containers, and the monitoring DB 170 manages monitoring information of applications and infrastructure, and integrated configuration DB (Configuration Management DB, CMDB, 160) manages configuration information of provider, network, service, cluster, server, component, and cloud resources.

Figure 12 shows the architecture of the cloud platform according to an embodiment of the present invention, Figure 13 shows the configuration of the cocktail server and its surrounding architecture.

12 , the cocktail cloud includes cocktail cluster 200, provider plug-in 210, server manager 220, DevOps manager, CMDB 160, monitoring DB 170, image registry 180, API server ( 290 ), and a user console 300 .

The cocktail cluster 200 provides an orchestration-based architecture and the provider plug-in 210 is used as a basic module for integrated management through the cloud provider API 280 .

The cluster 200 is composed of a node and a master, and in the case of a node, it has a structure that processes commands of the master through a worker 310 . The worker 310 is in charge of communication with the master, and an executor is supported according to an execution command. The Monitoring Executor 320 collects node and container monitoring information, and the Command Executor 330 executes OS and container commands. In addition, there is Container Engine (Docker, 340).

The provider plug-in 210 is an API Rapper for Kubernetes API support for multi-cloud and bare metal, and consists of a plug-in module for provider extension. The cocktail server is a basic unit of application orchestration and performs replication, scaling, and rolling updates of containers and cloud infrastructure through the cluster master 200 and the provider plug-in 210 .

As shown in Figure 13, the cocktail server is composed of a container and cloud infrastructure, and is composed of a load balancer, instance (node), container, volume, security, etc. It may be ESB. Cocktail Server provides cloud components for cloud providers' PaaS. For example, it may be RDS of AWS.

The server manager 220 is a control module that orchestrates application containers and infrastructure within the server, and performs replication control to restart/restore an abnormally terminated container, scale in/out, and scaling to perform up/down through instance type and volume expansion. , provides a rolling update function that sequentially and non-disruptively deploys application containers.

DevOps Manager is configuration management for multi-cloud infrastructure provisioning (Configuration Manager, 230), metering management for multi-cloud resource usage and cost management (Metering Manager, 240), and resource management for multi-cloud resource status and configuration management (Resource). Manager, 250), monitoring management for collecting and managing container/infrastructure monitoring information (Monitoring Manager, 260), combining and performing multiple task tasks in batches, immediate execution, execution time, and event occurrence are the execution conditions, and deployment and server actions · It is a manager module for DevOps that provides job management (Job Manager, 270) for tasks of remote commands.

Cocktail Cloud provides a DB for application and infrastructure configuration information management/monitoring information management/application container image management, and an interface for users and programming.

The CMDB 160 manages configuration information of a provider, a network, a service, a cluster, a server, a component, and a cloud resource.

The monitoring DB 170 manages monitoring information of applications and infrastructure.

The image registry 180 manages registration/share/download/search/version of the application container.

The API server 290 provides all the functions of the cocktail cloud as the API 280, and supports customization according to corporate strategy and linkage with other solutions.

The user console 300 is provided in the form of a Web GUI.

This cocktail cloud can be utilized as follows.

First, it can be utilized as a multi-cloud.

Cocktail Cloud is a platform for integrated management of heterogeneous and complex multi-cloud environments through standardized components, and also implements the entire application-oriented enterprise cloud. Specifically, Cocktail Cloud is a standardized management component that standardizes management targets through provider, network, service, cluster, server, and cloud components and integrates management of heterogeneous and complex multi-cloud resources (integrated accounts, resources, and costs). In addition, applications are a core business resource, and application availability and scalability are enhanced through cocktail cluster, and application-oriented enterprise cloud can be implemented through development/operational efficiency through cocktail DevOps View.

Second, Cocktail Cloud provides the basis for building/operating a hybrid cloud through cloudization of in-house and data center bare metal infrastructure. It also provides integrated management and development/operational efficiency of complex hybrid infrastructure.

Specifically, by configuring an application cluster in the bare metal infrastructure of in-house and data centers to build a container-based cloud environment, a separate platform for virtualization is unnecessary, providing scalability such as availability and scaling, and integrating the existing private and public clouds Cloudization of manageable physical infrastructure can be implemented.

In addition, it is managed through standard components of Cocktail Cloud and provides development/operational efficiency through Cocktail Cloud DevOps view.

Third, Cocktail Cloud provides an efficient management of applications on the cloud and a platform for building and operating microservices through automation for containers and CI/CD.

Cocktail Cluster provides a container-based application deployment and management environment in cloud infrastructure (cloud native applications). Here, the cocktail cluster is the basic unit for building and managing microservices.

Task management in the cocktail DevOps view provides an automated foundation for building and deploying applications, and containers are a lighter and easier technology to do CI/CD. Cocktail Cloud provides a platform to deploy/operate applications on multi/hybrid clouds.

Fourth, Cocktail Cloud can also be used as a platform for resale of infrastructure and service provision of cloud service brokers.

It integrates management of public cloud and data center infrastructure and builds and operates a platform for CSB that provides resale and cloud management platforms as a service to users as a cocktail cloud, provides multi-tenancy and billing systems for SaaS, and provides large-scale of companies, it can be used as a cloud provision and management platform for affiliates.

In addition, the infrastructure of existing data center operators is clouded and provided, and services (cocktail cloud component (PaaS)) specialized for public cloud providers are provided.

14 to 16 are diagrams for explaining a multi-cluster provisioning and management function of a cloud platform system according to an embodiment of the present invention.

The cocktail cloud, which is a cloud platform system according to the present invention, provides a multi-cluster provisioning and management function that automatically creates a cluster environment in which container-based applications can operate in various infrastructures such as bare metal, cloud platform, and public cloud. This function creates a container application operating environment by remote simultaneous provisioning of multiple clusters from the central (cocktail cloud) in a multi-cloud environment, and improves operational efficiency by remotely managing cluster version upgrades (see Fig. 14).

Referring to FIG. 15 , when upgrading the version of the cluster, the latest functions of the Orchestration engine and add-on are reflected, and a cluster node can be easily added and a faulty node can be replaced by using a CLI tool. In addition, cluster node backup is possible, and cluster auto-scaling is also possible.

FIG. 16 is an exemplary screen for registering account information of a public cloud in which a cluster is configured and remotely controlling the cluster to perform application distribution, operation management, and cluster monitoring functions.

17 is a flowchart illustrating a multi-cluster provisioning and management method of a cloud platform system according to an embodiment of the present invention.

A user-inputable provisioning and management tool is provided for multi-cluster provisioning and management.

When a user's cluster provisioning is requested by the provisioning and management tool (S400), the cloud platform system allows to input cluster type information (eg, bare-metal, public cloud, cloud platform, etc.) (S410). When cluster type information is input by the user, cluster configuration information is generated ( S420 ). Specifically, the cluster configuration information includes at least one of the number of instances, instance specifications (GPU, memory type), network configuration information, and storage configuration information.

Next, when public cloud or system access information (access account information, authentication information) is registered (S430), the cloud platform system checks whether to create or change a cluster (S440, S490).

When creating a cluster, the cloud platform system requests and configures instances, networks, and storage creation (S450). Thereafter, the container runtime software is installed (S460). And the cluster configuration information is set (S470). Then, cluster provisioning is completed (S480).

If the cluster is to be changed, the cloud platform system checks the cluster configuration history information and updates the cluster configuration (S500, S510). Then, the cluster change is completed (S520).

Meanwhile, the above-described embodiments of the present invention can be written as a program that can be executed on a computer, and can be implemented in a general-purpose digital computer that operates the program using a computer-readable recording medium. The computer-readable recording medium includes a magnetic storage medium (eg, a ROM, a floppy disk, a hard disk, etc.), an optically readable medium (eg, a CD-ROM, a DVD, etc.) and a carrier wave (eg, through the Internet). storage media such as transmission).

As described above, according to the method of containerizing an application in the cloud platform according to the present invention, an isolated application execution environment is provided, independent resource allocation is possible, multiple applications can be operated on the same host, and operation is quick with OS-level virtualization. This is possible, and deployment and update are efficient with a small size container image, and it can be moved anywhere.

In addition, according to the multi-cluster provisioning and management method in the cloud platform according to the present invention, it is possible to automatically create a multi-cluster environment in which container-based applications can operate on various infrastructures, and to remotely manage cluster version upgrades to improve operational efficiency. can do it

So far, with respect to the present invention, the preferred embodiments have been looked at. Those of ordinary skill in the art to which the present invention pertains will understand that the present invention can be implemented in a modified form without departing from the essential characteristics of the present invention. Therefore, the disclosed embodiments are to be considered in an illustrative rather than a restrictive sense. The scope of the present invention is indicated in the claims rather than the foregoing description, and all differences within the scope equivalent thereto should be construed as being included in the present invention.

100: cloud integration unit 110: service management unit 120: application orchestration unit 140: development / operation unit 150: DB/repository 160: Integration configuration DB 170: monitoring DB 180: image storage 200: cluster 210: provider plugin 220: server manager 230: configuration management 240: metering management 250: resource management 260: monitoring management 270: task management 280: API 290: API server 300: console 310: walker 320: Monitoring Executor 330: Command Executor 340: Container Engine