EDGE CLOUD BUILDING SYSTEM AND METHOD FOR PARALLEL INSTALLATION OF EDGE CLOUD

Abstract

The present invention relates to an edge cloud infrastructure building technology, and particularly, to a system and a method for building an edge cloud, which can simultaneously a large-scale edge cloud in parallel. To this end, the edge cloud building system according to the present invention as an edge cloud building system for parallel installation of an edge cloud include, when a cloud infrastructure provisioning automation platform on a central cloud transmits a multiple cluster installation request to each of a plurality of edge clouds which is scheduled to be built, generating, by a cluster controller on the plurality of edge clouds, a custom resource (CR) based on a custom resource definition (CRD) for cluster provisioning included in the multiple cluster installation request to generate a cluster-specific worker controller; and building, by each cluster-specific worker controller, a cluster constituted by a master node and a worker node, and multiple clusters are simultaneously generated on each of the plurality of edge clouds.

Claims

1. An edge cloud building system for parallel installation of an edge cloud, the system comprising: when a cloud infrastructure provisioning automation platform on a central cloud transmits a multiple cluster installation request to each of a plurality of edge clouds which is scheduled to be built, generating, by a cluster controller on the plurality of edge clouds, a custom resource (CR) based on a custom resource definition (CRD) for cluster provisioning included in the multiple cluster installation request to generate a cluster-specific worker controller; and building, by each cluster-specific worker controller, a cluster constituted by a master node and a worker node to simultaneously generate multiple clusters on each of the plurality of edge clouds.

2. The edge cloud building system of claim 1, wherein the cluster controller receives a cluster task log from the cluster-specific worker controller and transmits the received cluster task log to the cloud infrastructure provisioning automation platform.

3. The edge cloud building system of claim 2, wherein an administrator inputs the multiple cluster installation request and inputs a real-time cluster task log by using a dashboard or a command-line interface of the cloud infrastructure provisioning automation platform.

4. A edge cloud building method for parallel installation of an edge cloud, the method comprising: transmitting, by a cloud infrastructure provisioning automation platform on a central cloud, a multiple cluster installation request to each of a plurality of edge clouds which is scheduled to be built; generating, by a cluster controller on the plurality of edge clouds, a custom resource (CR) based on a custom resource definition (CRD) for cluster provisioning included in the multiple cluster installation request to generate a cluster-specific worker controller; and building, by each cluster-specific worker controller, a cluster constituted by a master node and a worker node, wherein multiple clusters are simultaneously generated on each of the plurality of edge clouds.

5. The edge cloud building method of claim 4, further comprising: receiving, by the cluster controller, a cluster task log from the cluster-specific worker controller and transmitting the received cluster task log to the cloud infrastructure provisioning automation platform.

6. The edge cloud building method of claim 4, wherein in the building of the cluster, the cluster-specific worker controller generates the cluster by using an automation script.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0020] FIG. 1 is a diagram illustrating an overall configuration of an edge cloud building system for parallel installation of an edge cloud according to the present invention.

[0021] FIG. 2 is a diagram illustrating an internal configuration of the edge cloud building system for parallel installation of an edge cloud according to the present invention.

[0022] FIG. 3 is a flowchart illustrating a parallel installation process of an edge cloud according to the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

[0023] Hereinafter, an exemplary embodiment of the present invention will be described in detail with reference to the accompanying drawings. A configuration of the present invention and the resulting operation effect will be described apparently appreciated through the following detailed description.

[0024] Prior to the detailed description of the present invention, the same component is denoted by the same reference numeral even though the same component is illustrated in another drawing, and when it is judged that a known configuration can make the gist of the present invention be ambiguous, it is noted that a detailed description will be omitted.

[0025] FIG. 1 is a diagram illustrating an overall configuration of an edge cloud building system for parallel installation of an edge cloud according to the present invention.

[0026] Referring to FIG. 1, the edge cloud building system is configured by an edge device 100, an edge cloud 200, a central cloud 300, and a cloud infra provisioning automation platform 400 on the central cloud 300.

[0027] The edge cloud 200 is connected to multiple edge devices 100 including an IoT sensor (not illustrated) and an actuator (not illustrated) to receive various data from the edge device 100, and perform edge computing for transmitting a control signal to the edge device 100.

[0028] The central cloud 300 receives data from multiple edge clouds 100 to execute cloud computing and deliver an execution result to the edge cloud 100.

[0029] Multiple edge devices 100 produce a lot of data (e.g., big data), and the edge cloud 200 basically performs preprocessing such as data collection from the edge device 100, data refinement for utilizing the big data, cleaning for main processing of the big data, sampling, combination, etc., and delivers the result to the central cloud 300.

[0030] A function of the edge cloud 200 may be variously designed, and for example, may also be designed to autonomously process big data without sending the big data to the central cloud 300, and also designed to perform only a basic function, and hand over all core tasks to the central cloud 300.

[0031] The central cloud 300 primarily performs deep learning, and analysis, inference, etc., related thereto, and comprehensively performs the task handed over from the edge cloud 200 or distributes some of the tasks to a specific edge cloud 200.

[0032] The result processed in the central cloud 300 or the result autonomously processed in the edge cloud 200 is applied to the edge device 100 to control an operation of the edge device 100.

[0033] The cloud infrastructure provisioning automation platform 400 (hereinafter, referred to as a provisioning automation platform) according to the present invention is provided on the central cloud 300.

[0034] The cloud infra provisioning automation platform 400 may perform tasks such as verification and backup during design, installation (new, update, and restoration), verification (before/after installation), and an operation for a plurality of edge clouds.

[0035] The provisioning automation platform 400 may perform a parallel task for a plurality of edge cloud infrastructures. That is, the automation platform 400 may perform a parallel task for a plurality of clusters within the edge cloud while simultaneously building the edge cloud by parallel arranging and operating a dedicated controller for each task target, and in this case, may perform each task without mutual influence between individual tasks.

[0036] FIG. 2 illustrates an internal configuration of each subject constituting an edge cloud building system according to the present invention.

[0037] The edge cloud building system according to the present invention may be implemented by multiple edge controller and multiple cluster controller schemes in order to build the large-scale edge cloud in parallel, and cluster certification generation, cluster connection, platform component installation, etc., may be processed in one step by an automation script (Ansible script).

[0038] Referring to FIG. 2, the provisioning automation platform 400 includes a dashboard 401, a command-line interface (CLI) 402, a master controller 403, an edge cloud-specific edge controller 404, a message queue 405, etc.

[0039] An administrator may request installation of multiple clusters by using the dashboard 401 or the command line interface 402, while the administrator may identify a task state such as installation of multiple clusters, update of multiple clusters, and extension/deletion of a node.

[0040] When the master controller 403 receives a multiple cluster installation request from the administrator, the master controller 403 delivers the multiple cluster installation request to the edge controller 404 which interlocks with the edge cloud 200.

[0041] The edge controller 404 performs real-time data processing with an edge agent 201 within the edge cloud 200. The edge controller 404 may deliver a request for cluster installation and upgrade, node extension and deletion, etc., to the edge agent 201. In this case, the edge controller 404 delivers custom resource definition for cluster provisioning to the edge agent 201.

[0042] The custom resource definition (CRD) is to define a customer resource of a specific object by a user in addition to a basic workload provided in kubernetes. Equipment information (OS, system specification, CPU, a memory capacity, a disk capacity, etc.), cluster information (version, master/worker node, etc.), auto-scale information, and add-on application information are constituted by the CRD.

[0043] The edge agent 201 delivers a multiple cluster installation request and the CRD of the cluster to the cluster controller 202. The edge agent 201 performs the real-time data processing with the edge controller 404, and installs OpenStack. The edge agent 201 delivers state values related to OpenStack installation, cluster provisioning, and health check to the cluster controller 202.

[0044] The cluster controller 202 generates a customer resource (CR) based on the CRD to generate a worker controller 203 that takes charges of actual processing of the cluster.

[0045] The work controller 203 generates an instance (vm, network, load-balancer, etc.) related to the infrastructure inside the OpenStack through a cluster API, and builds the cluster with a component installer. That is, the work controller 203 may process the task such as the cluster installation and upgrade, and node extension/deletion in one step by using the automation script (Ansible script).

[0046] The work controller 203 generates a cluster task log while installing the cluster, and delivers the generated cluster task log to the edge agent 201. The edge agent 201 delivers the cluster task log to the cluster controller 202, and the cluster controller 202 transmits cluster task log information to the message queue 405 of the provisioning automation platform 400.

[0047] FIG. 3 illustrates a processing process for parallel installation of an edge cloud according to the present invention.

[0048] Referring to FIG. 3, first, the administrator inputs the multiple cluster installation request by using the dashboard 401 or the command-line interface 402 of the cloud infrastructure provisioning automation platform.

[0049] Then, the master controller 403 of the provisioning automation platform 400 delivers the multiple cluster installation request to the edge cloud-specific edge controller 404, and transmits the multiple cluster installation request to each of a plurality of edge clouds 200 which is scheduled to be built (S10).

[0050] The multiple cluster installation request is received by the edge agent 201 of each edge cloud 200, and the edge agent 201 delivers the multiple cluster installation request to the cluster controller 202.

[0051] Next, when each cluster controller 202 on the plurality of edge clouds 200 receives the multiple cluster installation request from the edge agent 201, the CR is generated based on the CRD for the cluster provisioning included in the multiple cluster installation request to generate the cluster-specific worker controller 203 (S20).

[0052] Thereafter, each cluster-specific worker controller 203 builds a cluster constituted by a master node and a worker node (S30). In this case, the cluster-specific worker controller 203 may generate the cluster by using the automation script. As a result, multiple clusters may be simultaneously generated on each of the plurality of edge clouds in parallel.

[0053] When multiple clusters are generated by the cluster-specific worker controller 203, the cluster task log is generated and delivered to the edge agent 201, and the edge agent 201 delivers the cluster task log to the cluster controller 202. Then, the cluster controller 202 transmits the cluster task log to the message queue 405 of the cloud infrastructure provisioning automation platform 400 (S40).

[0054] As a result, the administrator may identify the cluster task log delivered to the message queue 405 in real time by using the dashboard or the command-line interface.

[0055] The above description is just exemplarily describing the present invention, and various modifications can be made by those skilled in the art within the scope without departing from the technical spirit of the present invention. Therefore, the exemplary embodiments disclosed in the present invention do not intend to limit the present invention. The scope of the present invention should be construed based on the following claims, and all the techniques in the equivalent scope thereof should be construed as falling within the scope of the present invention.