TWI884729B - Terraform management system and method of the same - Google Patents

Abstract

A Terraform management system may include a processor, and a memory storing instructions, wherein when the instructions are executed by the processor, the instructions may cause the processor to perform an operation of receiving first information related to a provider of a cloud service, second information related to a virtual private cloud (VPC) of a resource of the cloud service, and third information related to a subnet of the resource, an operation of individually creating Terraform modules corresponding to each of the first information, the second information, and the third information, the Terraform modules including a plurality of Terraform codes, and an operation of executing the created Terraform modules.

Description

Infrastructure automation tool management system and method

The present disclosure relates to an infrastructure automation tool (TERRAFORM) management system and method thereof, and more specifically, to a working method of a no-code infrastructure automation tool platform for creating, importing, and editing cloud service resources.

Since existing infrastructure automation tools consist of a single code, when separating resources or editing resource information, the code must be changed as a whole. In this process, errors such as human errors may occur, and it takes a long time to change the code. In addition, the infrastructure automation tool code has the trouble of being created directly by users who manage resources. Therefore, the need for an infrastructure automation tool platform that makes resource editing easy, user-friendly, and minimizes human errors has become prominent.

[Prior art literature]

[Patent Literature]

(Patent Document 0001) US Patent No. US 11470040 B2 (Announcement Date 2022.10.11)

Technical problems to be solved by the invention

The technical problem to be solved by the embodiments of the present disclosure is to provide an infrastructure automation tool management system and an infrastructure automation tool management method that can create cloud service resources or import resources from cloud services and edit resources without directly creating infrastructure automation tool codes.

Furthermore, the technical problem to be solved by the embodiments of the present disclosure is to provide a method for managing different types of information, such as information related to a cloud service provider's account, information related to a resource's VPC, and information related to a resource's subnet, by using an additional infrastructure automation tool module.

Furthermore, the technical problem to be solved by the embodiment disclosed herein is to provide a method for determining whether the cloud service console and the infrastructure automation tool management system are synchronized. The technical solution of the present invention is

According to the embodiment of the present disclosure, the infrastructure automation tool management system includes: a processor and a memory storing instructions. When the processor executes the instructions, the processor can perform the following tasks: input first information related to the provider of the cloud service, second information related to the VPC of the resources of the cloud service, and third information related to the subnet of the resources; separately create an infrastructure automation tool module corresponding to the first information, the second information, and the third information, respectively, and the infrastructure automation tool module includes multiple infrastructure automation tool codes; and run the created infrastructure automation tool module.

In one embodiment, it is characterized in that the second information and the third information are the second information and the third information of new resources that do not exist in the cloud service.

In one embodiment, the second information and the third information are the second information and the third information already existing in the resources of the cloud service.

In one embodiment, the first information may include the account information and region information of the cloud service provider, the second information may include the VPC name information, ticketing information and VPC address information of the resource, and the third information may include the subnet name information, corresponding VPC information and subnet address information of the resource.

In one embodiment, the inputting work may also include the inputting of fourth information related to the tag assigned to the resource, and the creating work may also include the creating of an infrastructure automation tool module corresponding to the fourth information.

In one embodiment, when the processor executes the instructions, the processor can also perform the following tasks: editing the created infrastructure automation tool module, the editing may include: inputting new information that needs to be modified among the first information, the second information and the third information; and modifying the infrastructure automation tool code of the corresponding infrastructure automation tool module according to the modified information.

In one embodiment, the work of modifying the above-mentioned infrastructure automation tool code may include the work of displaying the modified portion of the above-mentioned code.

In one embodiment, when the processor executes the instructions, the processor may further perform the following tasks: determining the synchronization status of the second information and the third information of the resource stored in the control console of the cloud service and the second information and the third information of the resource inputted, wherein the determination may include: when the information of the resource stored in the control console changes, displaying the status of the resource as out of sync; importing the information of the resource stored in the control console, replacing the input information of the resource with the imported information; and modifying the infrastructure automation tool code of the corresponding infrastructure automation tool module according to the replaced information.

In one embodiment, the operation of displaying the resource status as being out of sync may include: displaying inconsistent information between the resource information stored in the control console and the input resource information.

According to another embodiment of the present disclosure, an infrastructure automation tool management method is performed by a computing device and may include: a step of inputting first information related to a cloud service provider, second information related to a VPC of resources of the cloud service, and third information related to a subnet of the resources; a step of separately creating an infrastructure automation tool module corresponding to the first information, the second information, and the third information, respectively, the infrastructure automation tool module including a plurality of infrastructure automation tool codes; and a step of running the created infrastructure automation tool module.

In one embodiment, it is characterized in that the second information and the third information are the second information and the third information of new resources that do not exist in the cloud service.

In one embodiment, the second information and the third information are the second information and the third information already existing in the resources of the cloud service.

In one embodiment, the method may further include: a step of editing the infrastructure automation tool module created above, and the editing step may include: a step of inputting new information that needs to be modified among the first information, the second information and the third information; and a step of modifying the infrastructure automation tool code of the corresponding infrastructure automation tool module according to the modified information.

In one embodiment, it may also include: a step of determining the synchronization status of the second information and the third information of the above-mentioned resource stored in the control console of the above-mentioned cloud service and the second information and the third information of the above-mentioned resource inputted, and the above-mentioned determination step may include: when the information of the above-mentioned resource stored in the above-mentioned control console changes, the step of displaying the status of the above-mentioned resource as out of sync; the step of importing the information of the above-mentioned resource stored in the above-mentioned control console, and replacing the above-mentioned input information of the above-mentioned resource with the above-mentioned imported information; and the step of modifying the infrastructure automation tool code of the corresponding infrastructure automation tool module according to the replaced information.

Hereinafter, various embodiments of the present disclosure are described in detail with reference to the attached drawings. The advantages and features of the present disclosure and the methods for realizing the same will become clear if the attached drawings and the embodiments described in detail below are referred to. However, the present disclosure is not limited to the embodiments described below, but can be implemented in a variety of different ways. The embodiments are only provided to make the present disclosure complete and to fully inform the ordinary technicians in the technical field to which the present disclosure belongs of the scope of the present disclosure. The present disclosure is only defined according to the scope of the invention application.

When adding reference numerals to the structural elements of each drawing, it should be noted that for the same structural elements, even if they are shown in other drawings, they should have the same reference numerals as much as possible. When explaining the present disclosure, if it is determined that the specific description of the relevant known structure or function may confuse the main purpose of the present disclosure, its detailed description will be omitted.

If there is no other definition, all terms (including technical and scientific terms) used in this specification can be used with the meaning commonly understood by ordinary technicians in the technical field to which this disclosure belongs, and the terms defined in commonly used dictionaries shall not be ideally or over-interpreted unless they are clearly and specifically defined. The terms used in this specification are used to illustrate the embodiments, and the present invention is not limited thereto. In this specification, the singular form also includes the plural form unless it is not specifically mentioned in the context.

Furthermore, when describing the structural elements of the present disclosure, terms such as first, second, A, B, (a), (b), etc. may be used. Such terms are used only to distinguish the structural elements from other structural elements, rather than to limit the nature, order, or sequence of the structural elements to the terms. When it is recorded that certain structural elements are "connected", "combined" or "connected" to other structural elements, it should be understood that the structural elements may be directly connected or connected to other structural elements, but each structural element may also be "connected", "combined" or "connected" to another structural element.

The use of “comprises” and/or “comprising” in the specification does not exclude the existence or addition of the mentioned structural elements, steps, tasks and/or devices and one or more other structural elements, steps, tasks and/or devices.

In this manual, cloud services refer to subscription-based outsourcing services that provide users with a variety of IT resources such as servers, storage devices, and SW. For example, cloud services that provide storage devices store various data in the storage devices of service provider servers connected to the Internet, and can be downloaded via the Internet when necessary.

In this manual, terraform (TF) refers to an open source Infrastructure as Code (IaC) tool that manages cloud infrastructure through code. Terraform code refers to files used to create cloud resources, import resources from cloud services, edit resources, or delete resources. Terraform modules refer to related Terraform code packages.

FIG1 is a block diagram exemplarily showing the structure of an overall system 10 including an infrastructure automation tool management system 12 according to an embodiment of the present disclosure. Referring to FIG1 , the overall system 10 may include a user terminal 11, an infrastructure automation tool management system 12, and a cloud service server 13. The infrastructure automation tool management system 12 according to an embodiment of the present disclosure does not need to directly create an infrastructure automation tool code, but provides the cloud service server 13 and a user interface for inputting information related to resources to the user terminal 11, thereby enabling the resource manager to create the infrastructure automation tool code.

The user terminal 11 may be a computing device available to a user of the infrastructure automation tool management system 12. That is, the user may access the infrastructure automation tool management system 12 through the user terminal 11, and may manage the resources of the cloud service server 13 through a user interface provided by the infrastructure automation tool management system 12. For example, the user terminal 11 may include a smart phone, a desktop, a laptop, etc. However, the present disclosure is not limited thereto, and the user terminal 11 may be any device.

The infrastructure automation tool management system 12 may input information related to the cloud service provider and information related to the cloud service resources. More specifically, the information related to the resources may include information related to the VPC of the resources, information related to the subnet of the resources, and information related to the tags assigned to the resources.

For example, information related to the cloud service provider may include account information and region information. Furthermore, information related to the VPC may include VPC name information, ticket information, and VPC address information in CIDR format. Furthermore, information related to the subnet may include subnet name information, corresponding VPC information, and subnet address information in CIDR format. However, the present disclosure is not limited to this, and other information besides the above may be additionally input.

In the present disclosure, the resources that become the management objects of the infrastructure automation tool can also be resources that already exist in the cloud service server 13, or they can be new resources that do not exist in the cloud service server 13. When the resources to be managed are existing resources, the infrastructure automation tool management system 12 allows users to input information related to the existing resources. The process of inputting information related to the existing resources is equivalent to importing. On the contrary, when the resources to be managed are new resources that do not exist, the infrastructure automation tool management system 12 allows users to input information related to the new resources. The process of inputting information related to the new resources is equivalent to creating.

After the information is input, the infrastructure automation tool management system 12 can create an infrastructure automation tool module corresponding to each piece of information. For example, the infrastructure automation tool management system 12 can create an infrastructure automation tool module for managing information related to cloud service providers, an infrastructure automation tool module for managing information related to VPCs, an infrastructure automation tool module for managing information related to subnets, and an infrastructure automation tool module for managing information related to tags. At this time, each infrastructure automation tool module may include multiple infrastructure automation tool codes required for operation. As such, the infrastructure automation tool management system 12 according to the embodiment of the present disclosure adopts an additive structure managed by additional infrastructure automation tool modules according to different types of information.

With the adoption of a layered structure, the editing of the infrastructure automation tool module created according to the embodiment of the present disclosure can be performed according to different types of information. The editing of the infrastructure automation tool module can be performed by modifying the infrastructure automation tool code that constitutes the infrastructure automation tool module, which is equivalent to editing (modifying) the resource information that becomes the management object. In order to edit the infrastructure automation tool module, the infrastructure automation tool management system 12 can input new information that needs to be modified, and the infrastructure automation tool code of the corresponding infrastructure automation tool module can be modified according to the modified information.

Generally speaking, modification of infrastructure automation tool codes includes a process of scanning the infrastructure automation tool codes from beginning to end before and after the modification to confirm which item is modified on the code. When all information is managed by one infrastructure automation tool module, the entire infrastructure automation tool code needs to be scanned regardless of which information is modified, but when a layered structure is used as described above, only the infrastructure automation tool code corresponding to the modified information needs to be scanned, thereby shortening the time required for editing the infrastructure automation tool module (i.e., modification of the infrastructure automation tool code and editing of resource information). Furthermore, when modifying the infrastructure automation tool code, the modified portion can be additionally displayed to the user.

On the other hand, depending on the situation, some users can also directly access the control console of the cloud service server 13 (hereinafter referred to as the cloud service control console) to manage resources instead of managing the cloud service resources through the infrastructure automation tool management system 12. At this time, the results of managing resources in the cloud service control console should be delivered to the infrastructure automation tool management system 12. Otherwise, the resource management results (for example, resource editing results) executed in the infrastructure automation tool management system 12 and the resource management results executed in the cloud service control console will be inconsistent. In particular, when the VPC information or subnet information is inconsistent, the infrastructure automation tool may have difficulty managing resources.

To this end, the infrastructure automation tool management system 12 according to the embodiment of the present disclosure can determine the synchronization status of the VPC information or subnet information of the resources stored on the infrastructure automation tool management system 12 and the VPC information or subnet information of the same resources stored on the control console of the cloud service in response to the user's access. When there is inconsistency between the information on the infrastructure automation tool management system 12 and the information on the control console of the cloud service, the infrastructure automation tool management system 12 can display the status of the resource as out of sync. On the contrary, when no inconsistency occurs, the infrastructure automation tool management system 12 can display the status of the resource as in sync.

When an inconsistency occurs and the resource status is displayed as out of sync, the infrastructure automation tool management system 12 can import resource information from the cloud service console and replace the resource information on the infrastructure automation tool management system 12 with the resource information imported from the console. Then, the infrastructure automation tool management system 12 can modify the infrastructure automation tool code of the corresponding infrastructure automation tool module according to the replaced resource information. In addition, the infrastructure automation tool management system 12 can additionally display the type of inconsistent information on the user terminal 11.

Finally, the infrastructure automation tool management system 12 can run the created infrastructure automation tool module. The operation of the infrastructure automation tool module may include the operation of the infrastructure automation tool code that constitutes the infrastructure automation tool module, and may include an infrastructure automation tool plan (terraform plan) and an apply (apply) step. The infrastructure automation tool plan displays the predicted operation results before the infrastructure automation tool module is finally run. Users can use the infrastructure automation tool plan to confirm whether the infrastructure automation tool module is accurately created, and confirm the parts that need to be modified to perform the above editing work. After confirming the forecast results through the infrastructure automation tool plan, the infrastructure automation tool module is finally run.

The infrastructure automation tool management system 12 can be implemented by at least one computing device. For example, all functions of the infrastructure automation tool management system 12 can also be implemented by one computing device, the first function of the infrastructure automation tool management system 12 can be implemented on the first computing device, and the second function can also be implemented on the second computing device. Alternatively, specific functions of the infrastructure automation tool management system 12 can also be implemented on multiple computing devices. For example, the computing device may include all types of devices having a computing unit and a communication unit. Alternatively, the infrastructure automation tool management system 12 is based on cloud technologies such as virtual machines and can be constructed using one or more physical servers included in a server farm.

The cloud service server 13 can provide cloud services including resources managed by the infrastructure automation tool management system 12. Like the infrastructure automation tool management system 12, the cloud service server 13 can be implemented as a computing device, and the computing device implemented by the cloud service server 13 can be equivalent to a control console for the cloud service. The cloud service including resources that become management objects of the user can be identified by information related to the provider of the cloud service (account information and regional information).

The structural elements shown in Figure 1 can communicate via a network. For example, the network can be implemented as any type of wired/wireless network such as a local area network (LAN), a wide area network (WAN), a mobile radio communication network, or a wireless broadband Internet (Wibro).

2 to 7, the user interface for determining whether the creation, import, and editing of resources and synchronization with the cloud service console is checked by the infrastructure automation tool management system 12. For example, the user interface shown in FIG. 2 to 7 can be displayed on the user terminal 11 by the infrastructure automation tool management system 12.

FIG. 2 exemplarily shows a user interface 20 for creating a new VPC according to an embodiment of the present disclosure. Referring to FIG. 2 , a user may input information 21 related to a cloud service provider, VPC information 22, and tag information 23. As described with reference to FIG. 1 , the information 21 related to a cloud service provider may include account information and region information, and the VPC information 22 may include VPC name information, ticket information, and VPC address information. Tag information 23 may be added by using a tag append button, and the added tag may be assigned to a resource as a tag. A user may interrupt the VPC creation process by using a cancel button 24, and may terminate the VPC creation process by using a create button 25.

FIG. 3 exemplarily shows a user interface 30 for creating a new subnet according to an embodiment of the present disclosure. As in FIG. 2 , a user may input information 31 related to a cloud service provider, subnet information 32, and tag information 33. Subnet information 32 may include corresponding VPC information, subnet address information, and available region information. A user may interrupt the subnet creation process by pressing a cancel button 34, and may terminate the subnet creation process by pressing a create button 35.

Through the VPC creation and subnet creation process shown in FIG. 2 and FIG. 3 , new resources that do not exist can be created, and an infrastructure automation tool module for managing the created resources can be created.

FIG. 4 exemplarily shows a user interface 40 for importing an existing VPC according to an embodiment of the present disclosure. As in FIG. 2 , a user can input information 41 related to a cloud service provider, VPC information 42, and tag information 43. Unlike the VPC information 22 of FIG. 2 , which is VPC information of a non-existent new resource, the VPC information 42 of FIG. 4 is VPC information of an existing resource, and the infrastructure automation tool management system 12 can import resources corresponding to the input VPC information 42. The user can interrupt the VPC import process by pressing the cancel button 44, and can terminate the VPC import process by pressing the import button 45.

Through the VPC import process shown in Figure 4, existing resources in the cloud service server 13 can be imported, and an infrastructure automation tool module for managing the imported resources can be created. On the other hand, according to an embodiment, in addition to the information shown in Figures 2 to 4, other various information can also be input.

Fig. 5 exemplarily shows the editing result of the infrastructure automation tool module according to the embodiment of the present disclosure. Referring to Fig. 5 , Table 50 shows the infrastructure automation tool code before and after the editing of the infrastructure automation tool module, and Table 50 is equivalent to the infrastructure automation tool module corresponding to the subnet information. In more detail, the first line 51 may correspond to the infrastructure automation tool code corresponding to the subnet VPC in the infrastructure automation tool module corresponding to the subnet information, the second line 52 may correspond to the infrastructure automation tool code corresponding to the subnet available area, and the third line 53 may correspond to the infrastructure automation tool code corresponding to the remaining subnet information except the subnet VPC and available area such as the subnet name information, ticket information, type information, etc. Although the first line 51 and the second line 52 are the same before and after editing, the third line 53 is different before and after editing, and the different parts will be additionally indicated (highlighted).

As described with reference to FIG1 , since the infrastructure automation tool management system 12 according to the embodiment of the present disclosure adopts a layered structure, editing of subnet information only includes modification of the code shown in Table 50, and does not require modification of the code corresponding to the remaining information. Thus, the time required for editing the infrastructure automation tool module (i.e., modification of resource information) can be shortened.

6 and 7 exemplarily show the synchronization status judgment results according to the embodiments of the present disclosure. Table 60 records the VPC address, subnet ID and available area, and the recorded information represents the information stored on the infrastructure automation tool management system 12. In addition, referring to FIG6 , the synchronization column of Table 60 shows whether it is synchronized with the cloud service console. When the information recorded in Table 60 is consistent with the resource information stored in the cloud service console, the synchronization is displayed as synchronization (in sync), and when it is inconsistent, the synchronization is displayed as out of sync.

For example, when the user terminal 11 is a PC, if the cursor is placed in "out of sync", the type of inconsistent information can be displayed in a pop-up window 61 as shown in Fig. 7. Referring to Fig. 7, a pop-up window 61 indicating inconsistent subnet IDs is exemplarily shown.

Below, referring to Figures 8 to 13, the steps/work related to the creation and operation of the infrastructure automation tool module, the editing of the infrastructure automation tool module, and the judgment of synchronization between the cloud service console and the infrastructure automation tool management system are examined. For reference, the following description shows the steps/work of the infrastructure automation tool management method executed in the infrastructure automation tool management system 12 of Figure 1. Therefore, in the following description, when the subject of a specific step/work is omitted, it can be understood that it is executed in the infrastructure automation tool management system 12.

FIG8 is a flow chart illustratively showing an infrastructure automation tool management method according to an embodiment of the present disclosure. Referring to FIG8 , in step S100, first information related to the provider of the cloud service, second information related to the VPC of the resources of the cloud service, and third information related to the subnet of the resources can be input. Then, in step S200, infrastructure automation tool modules corresponding to the first information, the second information, and the third information can be created separately. Among them, each infrastructure automation tool module includes a plurality of infrastructure automation tool codes, and each infrastructure automation tool module can work separately. That is, according to step S200, the infrastructure automation tool module can be created in a manner having a layered structure. In step S300, the created infrastructure automation tool module may be run, and the running of the infrastructure automation tool module may include infrastructure automation tool planning and applicable work.

FIG9 is a flowchart illustratively showing an infrastructure automation tool management method according to another embodiment of the present disclosure. Referring to FIG9 , before the operation ( S300 ) of the infrastructure automation tool module, the infrastructure automation tool module created in step S210 can be edited. Referring to FIG10 , the following step S210 is explained.

FIG10 is a flowchart specifically showing step S210 of editing the infrastructure automation tool module created in FIG9. Referring to FIG10, in step S211, new information to be modified may be input, and in step S212, the infrastructure automation tool code of the corresponding infrastructure automation tool module may be modified according to the modified information. At this time, the modified part may be additionally displayed to the user.

FIG11 is a flowchart illustratively showing an infrastructure automation tool management method according to another embodiment of the present disclosure. Referring to FIG11 , before the operation (S300) of the infrastructure automation tool module, in step S220, the synchronization status of the resource information stored in the cloud service control console and the resource information input from the infrastructure automation tool management system 12 can be determined. The following describes step S220 with reference to FIG12 .

FIG12 is a flowchart specifically showing step S220 for determining the synchronization state of FIG11. Referring to FIG12, in step S221, it can be determined whether the resource information stored in the cloud service console has changed. For example, when a user different from the user of the infrastructure automation tool management system 12 directly manages resources through the cloud service console, the resource information stored in the console will change. Specifically, step S221 can be executed each time a user accesses the infrastructure automation tool management system 12.

When a change occurs (YES), it may be displayed in step S222 that the resource status is out of sync. At this time, the type of inconsistent information may be displayed together. Then, in step S223, the input resource information may be replaced with the information imported from the control console, and in step S224, the infrastructure automation tool code of the corresponding infrastructure automation tool module may be modified according to the replaced information.

Fig. 13 is a flowchart illustratively showing an infrastructure automation tool management method according to another embodiment of the present disclosure. Referring to Fig. 13, in step S105, in addition to the first information, the second information, and the third information, fourth information related to the tag may be input, and in step S205, an infrastructure automation tool module corresponding to the fourth information may be created.

Figure 14 is a block diagram showing the hardware structure of a computing device 500 used to manage an infrastructure automation tool according to an embodiment of the present disclosure.

The computing device 500 may include one or more processors 510, a bus 530, a communication interface 540, a memory 520 for loading a computer program executed by the processor 510, and a storage device 550 for storing a computer program 560. However, FIG. 14 only shows the structural elements related to the embodiment of the present disclosure. Therefore, any person skilled in the art in the technical field to which the present disclosure belongs will know that in addition to the structural elements shown in FIG. 14, other general structural elements may also be included. That is, the computing device 500 may include a variety of structural elements in addition to the structural elements shown in FIG. 14. Moreover, depending on the circumstances, the computing device 500 may be configured in a form in which a part of the structural elements shown in FIG. 14 is omitted. Below, the structural elements of the computing device 500 are described.

The processor 510 can control the overall operation of each structure of the computing device 500. The processor 510 may include at least one of a central processing unit (CPU), a microprocessor unit (MPU), a microcontroller unit (MCU), a graphics processing unit (GPU), or any form of processor known in the technical field of the present disclosure. In addition, the processor 510 can perform operations on at least one application or program for executing the work/method according to the embodiment of the present disclosure. The computing device 500 may have more than one processor.

Then, the memory 520 can store various data, commands and/or information. The memory 520 can load the computer program 560 from the storage device 550 to execute the work/method according to the embodiment of the present disclosure. The memory 520 can be implemented as a volatile memory such as RAM, but the technical scope of the present disclosure is not limited thereto.

Next, the bus 530 can provide a communication function between the structural elements of the computing device 500. The bus 530 can be implemented as a bus in various forms such as an address bus, a data bus, and a control bus.

Next, the communication interface 540 can support the wired or wireless Internet communication of the computing device 500. Furthermore, the communication interface 540 can also support a variety of communication methods other than Internet communication. To this end, the communication interface 540 can include a communication module known in the technical field of the present disclosure.

Next, the storage device 550 temporarily stores one or more computer programs 560. The storage device 550 may include a non-volatile memory such as a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a hard disk, a removable disk, or any form of computer-readable recording medium known in the art to which the present disclosure belongs.

Then, the computer program 560 may include one or more instructions that cause the processor 510 to execute the work/method according to various embodiments of the present disclosure when loaded into the memory 520. That is, the processor 510 runs the one or more loaded instructions, thereby executing the work/method according to various embodiments of the present disclosure.

For example, the computer program 560 may include instructions for further executing the following operations: inputting first information related to the provider of the cloud service, second information related to the VPC of the resources of the cloud service, and third information related to the subnet of the resources; separately creating infrastructure automation tool modules corresponding to the first information, the second information, and the third information, respectively; and running the created infrastructure automation tool modules. Furthermore, the computer program 560 may include instructions for further executing the following operations: editing the created infrastructure automation tool module; determining the synchronization status of the second information and the third information of the resources stored in the control console of the cloud service and the second information and the third information of the input resources.

According to the embodiments of the present disclosure, the inconvenience of users having to directly create infrastructure automation tool codes in order to manage resources can be eliminated, and the time required for editing infrastructure automation tool modules can be shortened through the layered structure. In addition, according to the embodiments of the present disclosure, the results of directly managing resources through the cloud service console due to the inability to access the infrastructure automation tool management system are transmitted to the infrastructure automation tool management system, thereby achieving unified resource management.

So far, various embodiments of the present disclosure and the effects of the embodiments have been mentioned with reference to Figures 1 to 14. The effects of the technical ideas of the present disclosure are not limited to the effects mentioned above, and ordinary technical personnel can clearly understand other effects not mentioned through the following description.

Although it is described above that a plurality of structural elements constituting the embodiments of the present disclosure are combined into one or work in combination, the present disclosure is not necessarily limited to these embodiments. That is, as long as it is within the scope of the purpose of the present disclosure, all structural elements can also be selectively combined into one or more to work.

Although the drawings illustrate the tasks in a specific order, it should not be understood that the tasks need to be performed in the specific order shown or in sequence, or that all the tasks shown must be performed to obtain the desired results. In certain circumstances, multitasking and parallel processing are more advantageous. Moreover, in the embodiments described above, the separation of various structures should not be understood as necessarily requiring such separation, but it should be understood that the program components and systems described are generally integrated together by a single software product or can be packaged as multiple software products.

Although various embodiments of the present disclosure are described above with reference to the attached drawings, a person skilled in the art to which the present disclosure belongs can understand that the technical ideas of the present disclosure can also be implemented in other specific ways without changing the technical ideas or essential features. Therefore, it is necessary to understand that the embodiments described above are exemplary in all aspects, rather than restrictive. The protection scope of the present disclosure needs to be interpreted according to the scope of the attached invention application, and all technical ideas within the equivalent scope thereof should be interpreted as included in the scope of the present disclosure.

11: User terminal 12: Infrastructure automation tool management system 13: Cloud service server 20, 30, 40: User interface 500: Computing device 510: Processor 520: Memory 530: Bus 540: Communication interface 550: Storage device 560: Computer program S100, S105, S200, S205, S210, S211, S212, S220, S221, S222, S223, S224, S300: Steps

FIG1 is a block diagram schematically showing the structure of an overall system including an infrastructure automation tool management system according to an embodiment of the present disclosure.

FIG. 2 illustratively shows a user interface for creating a new VPC according to an embodiment of the present disclosure.

FIG. 3 schematically shows a user interface for creating a new subnet according to an embodiment of the present disclosure.

FIG. 4 exemplarily shows a user interface for importing an existing VPC according to an embodiment of the present disclosure.

FIG5 exemplarily shows the editing result of the infrastructure automation tool module according to an embodiment of the present disclosure.

6 and 7 exemplarily show the synchronization status determination results according to the embodiments of the present disclosure.

FIG8 is a flow chart that exemplarily shows an infrastructure automation tool management method according to an embodiment of the present disclosure.

FIG9 is a flow chart that exemplarily shows an infrastructure automation tool management method according to another embodiment of the present disclosure.

FIG10 is a flow chart specifically showing the steps for editing the infrastructure automation tool module created in FIG9.

FIG11 is a flow chart that exemplarily shows an infrastructure automation tool management method according to another embodiment of the present disclosure.

FIG. 12 is a flowchart specifically showing the steps for determining the synchronization state of FIG. 11 .

FIG13 is a flow chart that exemplarily shows an infrastructure automation tool management method according to another embodiment of the present disclosure.

Figure 14 is a block diagram showing the hardware structure of a computing device used to manage an infrastructure automation tool according to an embodiment of the present disclosure.

S100, S200, S300: Steps

Claims (14)

An infrastructure automation tool management system is characterized in that it includes: a processor; and a memory storing instructions, when the processor executes the instructions, the processor performs the following operations: inputting first information related to a cloud service provider, second information related to a VPC of a resource of the cloud service, and third information related to a subnet of the resource; separately creating an infrastructure automation tool module corresponding to the first information, the second information, and the third information, respectively, the infrastructure automation tool module including a plurality of infrastructure automation tool codes; and running the created infrastructure automation tool module. According to the infrastructure automation tool management system described in claim 1, the second information and the third information are the second information and the third information of new resources that do not exist in the cloud service. According to the infrastructure automation tool management system described in claim 1, the second information and the third information are the second information and the third information of the resources already existing in the cloud service. According to the infrastructure automation tool management system described in claim 1, the first information includes the account information and region information of the cloud service provider, the second information includes the VPC name information, ticket information and VPC address information of the resource, and the third information includes the subnet name information, corresponding VPC information and subnet address information of the resource. According to the infrastructure automation tool management system described in claim 1, the feature is that, the inputting work also includes the work of inputting fourth information related to the tag assigned to the resource, the creating work also includes the work of creating an infrastructure automation tool module corresponding to the fourth information. According to the infrastructure automation tool management system described in claim 1, it is characterized in that, when the processor executes the instruction, the processor also performs the following work: Editing the created infrastructure automation tool module, the editing work includes: Inputting new information that needs to be modified in the first information, the second information and the third information; and Modifying the infrastructure automation tool code of the corresponding infrastructure automation tool module according to the modified information. According to the infrastructure automation tool management system described in claim 6, the feature is that the work of modifying the infrastructure automation tool code includes the work of displaying the modified part of the code. According to the infrastructure automation tool management system described in claim 1, it is characterized in that, when the processor executes the instruction, the processor also performs the following work: Determine the synchronization status of the second information and the third information of the resource stored in the control console of the cloud service and the second information and the third information of the input resource, The determination work includes: When the information of the resource stored in the control console changes, the status of the resource is displayed as out of sync; Import the information of the resource stored in the control console, and replace the input information of the resource with the imported information; and According to the replaced information, modify the infrastructure automation tool code work of the corresponding infrastructure automation tool module. According to the infrastructure automation tool management system described in claim 8, the feature is that the work of displaying the status of the resource as being out of sync includes: the work of displaying inconsistent information between the information of the resource stored in the control console and the information of the resource input. An infrastructure automation tool management method is an infrastructure automation tool management method executed according to a computing device, and is characterized in that it includes: A step of inputting first information related to a cloud service provider, second information related to a VPC of a resource of the cloud service, and third information related to a subnet of the resource; A step of separately creating an infrastructure automation tool module corresponding to the first information, the second information, and the third information, respectively, the infrastructure automation tool module including a plurality of infrastructure automation tool codes; and A step of running the created infrastructure automation tool module. According to the infrastructure automation tool management method described in claim 10, the second information and the third information are the second information and the third information of new resources that do not exist in the cloud service. According to the infrastructure automation tool management method described in claim 10, the second information and the third information are the second information and the third information of the resources already existing in the cloud service. According to the infrastructure automation tool management method described in claim 10, it is characterized in that, it also includes: a step of editing the created infrastructure automation tool module, the editing step includes: a step of inputting new information to be modified in the first information, the second information and the third information; and a step of modifying the infrastructure automation tool code of the corresponding infrastructure automation tool module according to the modified information. The infrastructure automation tool management method according to claim 10 is characterized in that it also includes: a step of determining the synchronization status of the second information and the third information of the resource stored in the control console of the cloud service and the second information and the third information of the input resource, the determination step includes: a step of displaying the status of the resource as out of sync when the information of the resource stored in the control console changes; a step of importing the information of the resource stored in the control console and replacing the input information of the resource with the imported information; and a step of modifying the infrastructure automation tool code of the corresponding infrastructure automation tool module according to the replaced information.

Images