Device for managing distribution of cloud infrastructure and method thereof

Abstract

The present invention relates to a cloud infrastructure deployment management device and method, and the problem to be solved is to enable continuous configuration management of cloud infrastructure resources by managing the deployment and updates of resources actually deployed on the cloud and resources to be deployed using a state management file based on Infrastructure as Code (IaC). For example, a cloud infrastructure deployment management device is disclosed, comprising: a resource deployment management decision unit that determines whether to redeploy or proceed with deployment of a said resource depending on whether the import of a cloud infrastructure resource is in progress; a resource deployment progress unit that deploys the resource after importing it from a CSP when the resource import is in progress; and a resource redeployment progress unit that redeploys the resource so that the said resource is updated through synchronization between the already deployed resource and the resource of the CSP when the resource import is not in progress.

Description

Technology Field

[0001] An embodiment of the present invention relates to a cloud infrastructure deployment management device and method. Background Technology

[0002] With the advent of the digital era and the rapid changes in the business environment, there is an increasing need for IT infrastructure capable of corporate flexibility and agility, and the cloud is being utilized across various fields to meet these corporate needs.

[0003] In particular, as remote work and non-face-to-face services increase, cases of developing and adopting cloud solutions are on the rise, and cloud environments that provide flexible resources to support the activation of AI are emerging as an attractive option.

[0004] Cloud refers to "service provider servers" based on the convention of representing computing service provider servers as a cloud shape. It involves storing software and data on a central computer connected to the Internet, allowing users to access data anytime and anywhere simply by connecting to the Internet.

[0005] With the advent of the cloud environment, Cloud Service Providers (CSPs) have become able to easily access cloud resources through consoles.

[0006] However, conventional cloud service platforms have limitations in that they can manage updates for cloud infrastructure deployed on the portal, but cannot manage infrastructure that is not deployed.

[0007] Meanwhile, Infrastructure as Code (IaC) involves managing and provisioning infrastructure through code rather than manual processes, and currently, the de facto industry standard services representing Infrastructure as Code (IaC) include Terraform and Ansible.

[0008] Utilizing IaC generates configuration files containing cloud infrastructure specifications, making it easy to edit and deploy configurations. It also ensures that the same environment is provisioned every time and offers the advantage of version control because the infrastructure is managed in the form of code, so continued utility is expected for the construction and management of cloud infrastructure in the future. Prior art literature

[0009] Published Patent Application No. 10-2015-0137530 (Publication Date: December 09, 2015) Registered Patent Application No. 10-1826498 (Registration Date: February 01, 2018) Registered Patent Application No. 10-2196894 (Registration Date: December 23, 2020) Registered Patent Application No. 10-2625121 (Registration Date: January 10, 2024) The problem to be solved

[0010] An embodiment of the present invention provides a cloud infrastructure deployment management device and method capable of continuous configuration management of cloud infrastructure resources by managing the deployment and updates of resources deployed on an actual cloud and resources being deployed based on Infrastructure as Code (IaC) using a state management file. means of solving the problem

[0011] A cloud infrastructure deployment management device according to one embodiment of the present invention includes: a resource deployment management decision unit that determines whether to redeploy or proceed with deployment of a said resource depending on whether the import of a cloud infrastructure resource is in progress; a resource deployment progress unit that deploys a resource after importing it from a CSP when the resource import is in progress; and a resource redeployment progress unit that redeploys a resource so that the said resource is updated through synchronization between an already deployed resource and a resource of a CSP when the resource import is not in progress.

[0012] In addition, the resource distribution progress unit can convert the resources configured by the user into architecture and IaC code having visual objects, respectively, and display them on the canvas.

[0013] In addition, the resource distribution progress unit generates a state management file for the resource converted into IaC code, and the resource redistribution progress unit can manage updates to already distributed resources by comparing the resource of the CSP with the state of the resource through the state management file when redistributing the resource.

[0014] In addition, the resource redistribution process unit compares the already distributed resources with the resources of the CSP to provide update items for the user to verify, and receives a selection as to whether to proceed with synchronization for the provided update items; if resource synchronization is not performed, the resource configured by the user is distributed from the CSP, and if resource synchronization is performed, the resource corresponding to the update item is imported, and the process returns to the step of verifying the update item for the imported resource, and the subsequent process can be repeated until resource synchronization is not performed.

[0015] A cloud infrastructure deployment management method according to another embodiment of the present invention comprises: a resource deployment management decision unit, which determines whether to redeploy or proceed with the deployment of a cloud infrastructure resource based on whether the import of the resource proceeds; a resource deployment progress unit, which, if the resource import proceeds in the resource deployment management decision unit, distributes the resource after importing it from a CSP; and a resource redeployment progress unit, which, if the resource import does not proceed in the resource deployment management decision unit, redeploys the resource so that the resource is updated through synchronization between the already deployed resource and the resource of the CSP.

[0016] In addition, during the resource distribution process step, the resources configured by the user can be converted into architecture and IaC code having visual objects, respectively, and displayed on the canvas.

[0017] In addition, during the resource distribution process step, a state management file is created for the resources converted into IaC code, and during the resource redeployment process step, updates to already distributed resources can be managed by comparing the resources of the CSP with the status of the resources through the state management file when redeploying the resources.

[0018] In addition, during the resource redistribution step, the update items are provided to the user for verification by comparing the already distributed resources with the resources of the CSP, and the user is asked to select whether to proceed with synchronization for the provided update items. If resource synchronization is not performed, the resources configured by the user are distributed from the CSP; if resource synchronization is performed, the resources corresponding to the update items are imported, and the process returns to the step of verifying the update items for the imported resources, and the subsequent process can be repeated until resource synchronization is not performed. Effects of the invention

[0019] According to the present invention, by managing the distribution and updates of resources deployed on an actual cloud and resources being deployed based on Infrastructure as Code (IaC) using a state management file, a cloud infrastructure deployment management device and method capable of continuous configuration management of cloud infrastructure resources can be provided. Brief explanation of the drawing

[0020] FIG. 1 is a schematic diagram showing the hardware configuration of the overall configuration of a cloud infrastructure deployment management device according to one embodiment of the present invention. FIG. 2 is a block diagram showing the detailed configuration of a cloud infrastructure distribution management device according to one embodiment of the present invention. FIG. 3 is a flowchart illustrating a redistribution process according to an embodiment of the present invention. FIG. 4 is a flowchart illustrating the process of creating a state management file according to one embodiment of the present invention. FIG. 5 is a flowchart showing the detailed configuration of a cloud infrastructure deployment management method according to another embodiment of the present invention. Specific details for implementing the invention

[0021] The terms used in this specification will be briefly explained, and the invention will be described in detail.

[0022] The terms used in this invention have been selected based on currently widely used general terms, taking into account their functions within the invention; however, these terms may vary depending on the intent of those skilled in the art, case law, the emergence of new technologies, etc. Additionally, in specific cases, terms have been arbitrarily selected by the applicant, and in such cases, their meanings will be described in detail in the relevant description of the invention. Therefore, the terms used in this invention should be defined not merely by their names, but based on their meanings and the overall content of the invention.

[0023] When a part of a specification is described as "comprising" a certain component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components. Furthermore, terms such as "...part" or "module" as used in the specification refer to a unit that processes at least one function or operation, and this may be implemented in hardware or software, or as a combination of hardware and software.

[0024] Embodiments of the present invention are described below with reference to the attached drawings so that those skilled in the art can easily implement them. However, the present invention may be embodied in various different forms and is not limited to the embodiments described herein. Furthermore, in order to clearly explain the present invention in the drawings, parts unrelated to the explanation have been omitted, and similar parts throughout the specification are denoted by similar reference numerals.

[0025] FIG. 1 is a schematic diagram showing the hardware configuration of the overall configuration of a cloud infrastructure deployment management device according to one embodiment of the present invention.

[0026] Referring to FIG. 1, a cloud infrastructure deployment management device (1000) according to one embodiment of the present invention may include at least one of a user terminal (10) and a cloud infrastructure deployment management server (20).

[0027] The above user terminal (10) is a terminal possessed by the user to receive update management services through the creation of a new cloud infrastructure, and can receive continuous configuration management for the cloud infrastructure, such as distribution services through importing resources of various cloud infrastructures configured by the user from a CSP (Cloud Service Provider) and update management services for the distributed resources.

[0028] The user terminal (10) according to the present embodiment can be implemented in a form that applies the hardware configuration of computing devices such as a smartphone, smartpad, tablet PC, PCS (Personal Communication System), GSM (Global System for Mobile communications), PDC (Personal Digital Cellular), PHS (Personal Handyphone System), PDA (Personal Digital Assistant), IMT (International Mobile Telecommunication)-2000, CDMA (Code Division Multiple Access)-2000, W-CDMA (W-Code Division Multiple Access), and Wibro (Wireless Broadband Internet) terminal.

[0029] The cloud infrastructure deployment management server (20) can perform resource deployment and update management by determining whether to redeploy or proceed with deployment of the cloud infrastructure resources configured by the user based on whether the resources are being imported, and if the resources are being imported, deploying the resources after importing them from the CSP, and if the resources are not being imported, redeploying the resources so that the resources configured by the user are updated through synchronization between the resources configured by the user and the resources of the CSP.

[0030] The cloud infrastructure distribution management server (20) according to the present embodiment may include program modules that perform various functions by being implemented in software using various forms of languages ​​such as C, C++, Java, Visual Basic, Visual C, etc., and may be implemented using web server programs provided in various ways according to operating systems such as DOS, Windows, Linux, Unix, Macintosh, Android, iOS, etc. on general server hardware.

[0031] According to the present embodiment, a user terminal (10) and a cloud infrastructure distribution management server (20) can be connected via a network communication network, wherein the network communication network refers to a connection structure capable of exchanging information between each node, and examples include, but are not limited to, a 3GPP (3rd Generation Partnership Project) network, an LTE (Long Term Evolution) network, a WIMAX (World Interoperability for Microwave Access) network, the Internet, a LAN (Local Area Network), a Wireless LAN (Wireless Local Area Network), a WAN (Wide Area Network), a PAN (Personal Area Network), a Bluetooth network, a satellite broadcasting network, an analog broadcasting network, a DMB (Digital Multimedia Broadcasting) network, etc.

[0032] The configuration of the cloud infrastructure distribution management device (1000) according to the present embodiment will be described in more detail below with reference to the attached drawings.

[0033] FIG. 2 is a block diagram showing the detailed configuration of a cloud infrastructure distribution management device according to an embodiment of the present invention, FIG. 3 is a flowchart showing a redistribution process according to an embodiment of the present invention, and FIG. 4 is a flowchart showing a state management file creation process according to an embodiment of the present invention.

[0034] Referring to FIG. 2, a cloud infrastructure distribution management device (1000) according to one embodiment of the present invention may include at least one of a resource distribution management decision unit (100), a resource distribution progress unit (200), and a resource redistribution progress unit (300).

[0035] The above resource distribution management decision unit (100) can determine whether to redeploy or proceed with distribution of the said resource depending on whether the import of the cloud infrastructure resource is proceeding. That is, if the resource has been imported, the process of redeploying the resource (a process of redeploying after importing the distributed resource) is carried out by performing the resource import, and if the resource has not been imported, the direction of the distribution process can be determined so that the process of redeploying the resource (a process of redeploying after the resource has been first deployed on the platform (portal)) is carried out.

[0036] The above resource distribution progress unit (200) can perform a process of distributing resources after importing them from the CSP when performing resource importing (a process of redistributing resources after retrieving distributed resources).

[0037] The resource distribution progress unit (200) above can convert the resources configured by the user into an architecture having visual objects and an IaC code, respectively, and display them on a canvas. The architecture may include physical resource and virtual resource images (icons) and block and line shapes for diagramming the correlation between each image (icon), and the IaC code for the resources may be displayed on the canvas screen together with the architecture.

[0038] The above resource distribution progress unit (200) can generate a state management file for the resource converted into IaC code. For example, the state management file can generate a 'tfstate' file for managing the state of an existing infrastructure resource using the 'terraform import' command in Terraform. That is, the resource is loaded in the form of a 'state' through the command to generate a 'tfstate' file, and the state of the distributed resource can be loaded.

[0039] More specifically, when a user selects the Import button (or the Synchronize button after importing), the cloud infrastructure resources actually deployed in the cloud can be visualized and displayed on the canvas via the import function. At this point, internal synchronization can be performed by generating a 'tfstate' file for the environment deployed in the cloud; until the synchronization is complete, user functions such as pre-deployment checks and deployment may be restricted, but immediately after importing, the user can proceed with deployment without needing to perform a separate synchronization process.

[0040] The process of distributing these resources after importing them (the process of redeploying the distributed resources after importing them) can be executed as an asynchronous process after a synchronization operation when the resource import status is 'Yes' as shown in FIG. 3. The process after the synchronization operation is the same as the process of redeploying the resources after the first distribution described above.

[0041] The above resource redistribution process unit (300) can redistribute resources (a process of redistributing resources after the first distribution on the platform (portal)) so that resources that have already been distributed are updated through synchronization between resources configured by the user and resources of the CSP when resource importing has not been performed.

[0042] The above resource redistribution progress unit (300) can manage updates to already distributed resources by comparing the status of resources distributed on the CSP console and resources already distributed by the user through a status management file when redistributing resources.

[0043] The above resource redistribution progress unit (300) compares the already distributed resources and the resources of the CSP to provide an update item that the user can check, and receives a selection as to whether to proceed with synchronization for the provided update item. If resource synchronization is not performed, the resource configured by the user is distributed from the CSP, and if resource synchronization is performed, the resource corresponding to the update item is imported, and then the process of checking the update item for the imported resource is returned to the process of not performing resource synchronization, and the subsequent process can be repeated until resource synchronization is not performed.

[0044] For example, as shown in FIG. 3, if the user selects the 'Canvas resource update (add / delete / change)' button and the 'Deploy' button (variables comparison modal), and then selects the 'Deploy without synchronization' menu (No), the resource can be deployed as is on the canvas screen, and at this time, it may affect existing cloud resources.

[0045] Next, as shown in Fig. 3, the 'Canvas Resource Update (Add / Delete / Change)' button is selected, and the 'Deploy' button (variables comparison modal) is selected. Then, if the user selects the 'Synchronize' menu (Yes), a 'synchronization' operation is performed between the already deployed resources and the resources deployed on the portal connected to the CSP console, and the synchronized resources can be deployed. At this time, even if the portal environment is deployed by overwriting the canvas screen as is, the state of the cloud resources is not changed.

[0046] In this way, during the redeployment process following the initial deployment of resources, users can synchronize the infrastructure environment deployed in the actual cloud environment and display it on the canvas screen by clicking the synchronize button. If there are no instances where resource updates have been performed directly on the portal, users do not need to perform synchronization manually. However, if comparing variables (Canvas ↔ Portal) before deployment reveals that a resource on the portal is scheduled to be deleted, users can use the synchronization function to check update information for the resource in advance to prevent damage caused by unnecessary updates.

[0047] Accordingly, the cloud infrastructure distribution management device (1000) according to the present embodiment provides a user's cloud infrastructure resource version saving function to save the state of the canvas, and can perform version management by retrieving the saved canvas through a version history management function, and can check the detailed items of the resource that require updating, thereby enabling continuous configuration management of the cloud infrastructure by performing update management for each resource item.

[0048] After the process of redeploying the aforementioned resource after the first deployment and the process of redeploying the deployed resource after retrieving it, the 'tfstate' file creation process (A) illustrated in FIG. 4 is carried out.

[0049] As illustrated in Fig. 4, the process is divided into a 'tfstate' creation request and a 'websoket' request process, and these processes are executed asynchronously. The 'tfstate' creation request process can proceed through the steps of 'creating Terraform files', 'creating Terraform State', 'executing Celery-based Terraform import', and 'recording completed tasks in Celery Tasks'. Additionally, the 'websoket' request process involves 'checking Celery Task results', 'checking if the task is completed', 'checking the status of Celery Task results', and 'checking if the task is successful'. Subsequently, if the task is successful, a synchronization completion message is sent, and if the task is not successful, an error message is sent.

[0050] FIG. 5 is a flowchart showing the detailed configuration of a cloud infrastructure deployment management method according to another embodiment of the present invention.

[0051] Referring to FIG. 5, a cloud infrastructure deployment management method (S1000) according to one embodiment of the present invention may include at least one of a resource deployment management decision step (S100), a resource deployment progress step (S200), and a resource redeployment progress step (S300).

[0052] In the above resource distribution management decision step (S100), the redeployment or distribution of the corresponding resource can be determined based on whether the import of the cloud infrastructure resource is in progress. That is, if the resource has been imported, the process of distributing the resource by performing the import (a process of redeploying after retrieving the distributed resource) can be carried out, and if the resource has not been imported, the direction of the distribution process can be determined so that the process of redeploying the resource (a process of redeploying after the resource has been initially distributed on the platform (portal)) can be carried out.

[0053] In the above resource distribution process step (S200), when resource importing is performed, a process of distributing resources after importing them from the CSP (a process of redeploying resources after retrieving them) can be performed.

[0054] In the resource distribution process step (S200) described above, the resources configured by the user can be converted into an architecture having visual objects and an IaC code, respectively, and displayed on the canvas. The architecture may include physical and virtual resource images (icons) and block and line shapes for diagramming the correlation between each image (icon), and the IaC code for the resources can be displayed on the canvas screen along with the architecture.

[0055] In the above resource deployment process step (S200), a state management file can be created for the resource converted into IaC code. For example, the state management file can be created as 'tfstate', which is a file for managing the state of existing infrastructure resources, using the 'terraform import' command in Terraform. That is, the resource is loaded in the form of 'state' through the command to create a 'tfstate' file, and the state of the deployed resource can be loaded.

[0056] More specifically, when a user selects the Import button (or the Synchronize button after importing), the cloud infrastructure resources actually deployed in the cloud can be visualized and displayed on the canvas via the import function. At this point, internal synchronization can be performed by generating a 'tfstate' file for the environment deployed in the cloud; until the synchronization is complete, user functions such as pre-deployment checks and deployment may be restricted, but immediately after importing, the user can proceed with deployment without needing to perform a separate synchronization process.

[0057] The process of distributing these resources after importing them (the process of redeploying the distributed resources after importing them) can be executed as an asynchronous process after a synchronization operation when the resource import status is 'Yes' as shown in FIG. 3. The process after the synchronization operation is the same as the process of redeploying the resources after the first distribution described above.

[0058] In the above resource redistribution step (S300), if resource importing has not been performed, resources can be redistributed (a process of redistributing resources after the initial deployment on the platform (portal)) so that already deployed resources are updated through synchronization between the resources configured by the user and the resources of the CSP.

[0059] In the above resource redistribution process step (S300), when redistributing resources, the status of resources distributed on the CSP console and resources already distributed by the user can be compared through the status management file of the resources to manage updates to already distributed resources.

[0060] In the above resource redistribution step (S300), an update item is provided to the user for verification by comparing the already distributed resource and the resource of the CSP, and the user is asked whether to proceed with synchronization for the provided update item. If resource synchronization is not performed, the resource configured by the user is distributed from the CSP, and if resource synchronization is performed, the resource corresponding to the update item is imported, and the process returns to the step of verifying the update item for the imported resource, and the subsequent process can be repeated until resource synchronization is not performed.

[0061] For example, as shown in FIG. 3, if the user selects the 'Canvas resource update (add / delete / change)' button and the 'Deploy' button (variables comparison modal), and then selects the 'Deploy without synchronization' menu (No), the resource can be deployed as is on the canvas screen, and at this time, it may affect existing cloud resources.

[0062] Next, as shown in Fig. 3, the 'Canvas Resource Update (Add / Delete / Change)' button is selected, and the 'Deploy' button (variables comparison modal) is selected. Then, if the user selects the 'Synchronize' menu (Yes), a 'synchronization' operation is performed between the already deployed resources and the resources deployed on the portal connected to the CSP console, and the synchronized resources can be deployed. At this time, even if the portal environment is deployed by overwriting the canvas screen as is, the state of the cloud resources is not changed.

[0063] In this way, during the redeployment process following the initial deployment of resources, users can synchronize the infrastructure environment deployed in the actual cloud environment and display it on the canvas screen by clicking the synchronize button. If there are no instances where resource updates have been performed directly on the portal, users do not need to perform synchronization manually. However, if comparing variables (Canvas ↔ Portal) before deployment reveals that a resource on the portal is scheduled to be deleted, users can use the synchronization function to check update information for the resource in advance to prevent damage caused by unnecessary updates.

[0064] Accordingly, the cloud infrastructure deployment management method (S1000) according to the present embodiment provides a user's cloud infrastructure resource version saving function to save the state of the canvas, and can perform version management by retrieving the saved canvas through a version history management function, and can check the detailed items of the resource requiring update, thereby enabling continuous configuration management of the cloud infrastructure by performing update management for each resource item.

[0065] After the process of redeploying the aforementioned resource after the first deployment and the process of redeploying the deployed resource after retrieving it, the 'tfstate' file creation process (A) illustrated in FIG. 4 is carried out.

[0066] As illustrated in Fig. 4, the process is divided into a 'tfstate' creation request and a 'websoket' request process, and these processes are executed asynchronously. The 'tfstate' creation request process can proceed through the steps of 'creating Terraform files', 'creating Terraform State', 'executing Celery-based Terraform import', and 'recording completed tasks in Celery Tasks'. Additionally, the 'websoket' request process involves 'checking Celery Task results', 'checking if the task is completed', 'checking the status of Celery Task results', and 'checking if the task is successful'. Subsequently, if the task is successful, a synchronization completion message is sent, and if the task is not successful, an error message is sent.

[0067] The cloud infrastructure deployment management device described above may be implemented as a hardware component, a software component, and / or a combination of a hardware component and a software component. For example, the device and components described in the embodiments may be implemented using one or more general-purpose or special-purpose computers, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable array (FPA), a programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions.

[0068] A cloud infrastructure deployment management device may execute an operating system (OS) and one or more software applications executed on said operating system. Additionally, the cloud infrastructure deployment management device may access, store, manipulate, process, and generate data in response to the execution of the software. For convenience of understanding, the cloud infrastructure deployment management device may be described as being used as a single unit, but a person of ordinary skill in the art will know that the cloud infrastructure deployment management device may include multiple processing elements and / or multiple types of processing elements.

[0069] For example, a cloud infrastructure deployment management device may include multiple processors or one processor and one controller. Additionally, other processing configurations, such as parallel processors, are possible. Software may include computer programs, code, instructions, or a combination of one or more of these, and may configure the processing device to operate as desired or command the processing device independently or collectively. Software and / or data may be permanently or temporarily embodied in any type of machine, component, physical device, virtual equipment, computer storage medium or device, or transmitted signal wave to be interpreted by the processing device or to provide instructions or data to the processing device. Software may be distributed over networked computer systems, stored or executed in a distributed manner, or stored on one or more computer-readable recording media.

[0070] The above description is merely one embodiment for implementing the cloud infrastructure distribution management device and method according to the present invention. The present invention is not limited to the above embodiment, and the technical spirit of the present invention extends to the scope in which various modifications can be made by anyone with ordinary knowledge in the field to which the invention belongs, without departing from the gist of the invention as claimed in the following patent claims. Explanation of the symbols

[0071] 1000: Cloud infrastructure deployment management device 100: Resource Distribution Management Decision Department 200: Resource Distribution Progress 300: Resource Redistribution Progress S1000: Cloud Infrastructure Deployment Management Method S100: Resource Distribution Management Decision Phase S200: Resource deployment progress stage S300: Resource redeployment progress stage

Claims

Claim 1 A cloud infrastructure deployment management device comprising: a resource deployment management decision unit that determines whether to redeploy or proceed with distribution of a said resource depending on whether the import of a cloud infrastructure resource is in progress; a resource deployment progress unit that, if resource import is in progress, imports the resource from the CSP and then distributes it; and a resource redeployment progress unit that, if resource import is not in progress, redeploys the resource so that the said resource is updated through synchronization between the already distributed resource and the CSP's resource, wherein the resource redeployment progress unit compares the already distributed resource and the CSP's resource to provide an update item for the user to verify, and receives a selection regarding whether to proceed with synchronization for the provided update item, wherein if resource synchronization is not in progress, the resource configured by the user is distributed from the CSP, and if resource synchronization is in progress, the subsequent process is repeated until the resource synchronization is not in progress, by importing the resource corresponding to the update item and returning to the process of verifying the update item for the imported resource. Claim 2 A cloud infrastructure deployment management device according to claim 1, wherein the resource deployment progress unit converts the resources configured by the user into an architecture having visual objects and IaC code, respectively, and displays them on a canvas, respectively. Claim 3 A cloud infrastructure deployment management device according to claim 2, wherein the resource deployment progress unit generates a state management file for a resource converted into IaC code, and the resource redeployment progress unit manages updates of already deployed resources by comparing the resource of the CSP with the state of the resource through the state management file during resource redeployment. Claim 4 delete Claim 5 A cloud infrastructure distribution management method comprising: a resource distribution management decision unit, a resource distribution management decision step, which determines whether to redeploy or proceed with distribution of a said resource based on whether to proceed with importing a cloud infrastructure resource; a resource distribution progress unit, a resource distribution progress step, which distributes a resource after importing it from a CSP if resource importing is performed in the resource distribution management decision step; and a resource redeployment progress unit, which redeploys a resource so that the said resource is updated through synchronization between an already distributed resource and a CSP resource if resource importing is not performed in the resource distribution management decision step, wherein in the resource redeployment progress step, an update item is provided to a user for verification by comparing an already distributed resource and a CSP resource, and a selection is received regarding whether to proceed with synchronization for the provided update item; wherein if resource synchronization is not performed, the resource configured by the user is distributed from the CSP, and if resource synchronization is performed, the process returns to the step of importing the resource corresponding to the update item and verifying the update item for the imported resource, and repeats the subsequent process until resource synchronization is not performed. Claim 6 A cloud infrastructure deployment management method according to claim 5, characterized in that, in the resource deployment progress step, the resources configured by the user are respectively converted into an architecture having visual objects and an IaC code and displayed on a canvas. Claim 7 A cloud infrastructure deployment management method according to claim 6, characterized in that, in the resource deployment progress step, a state management file is created for the resource converted into IaC code, and in the resource redeployment progress step, when redeploying the resource, the update of the already deployed resource is managed by comparing the resource of the CSP with the state of the resource through the state management file. Claim 8 delete Claim 9 A computer-readable recording medium having a program for executing a cloud infrastructure deployment management method according to any one of claims 5 to 7.

Images