Method, apparatus, and program for providing cluster management service that automatically builds ci / cd pipeline in a cluster
The automated CI/CD pipeline service addresses the complexity of cloud environment setup by automating DevOps tool installations and configurations, facilitating rapid development and deployment with error handling capabilities.
Patent Information
- Application Number
- KR1020240154999
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-11-05
- Publication Date
- 2026-11-06
- Estimated Expiration
- 2044-11-05
AI Technical Summary
Building and managing CI/CD pipelines in a cloud environment is complex and requires significant manual configuration, consuming substantial time and resources, and there is a need for an automated solution.
A computer program and service that automatically builds a CI/CD pipeline in a cluster by performing node joins, creating job pods for automation tasks, and managing DevOps tool installations and configurations, with features like automated retries for failed installations.
Enables rapid development and deployment by minimizing manual work, allowing developers to quickly deploy applications to production environments and enhancing user convenience through automated error detection and resolution.
Smart Images

Figure R1020240154999_ABST
Abstract
Description
Technology Field
[0001] The present disclosure relates to a cluster management service, and specifically, to a cluster management service that automatically builds a CI / CD pipeline in a cluster. Background Technology
[0003] With the recent rapid advancement of cloud computing technology alongside the development of IT infrastructure, there is an increasing demand among companies to migrate existing physical servers or data centers to the cloud or to leverage them to efficiently develop, deploy, and operate applications. Cloud computing enables the flexible use of computing resources (servers, storage, networks, databases, etc.) over the Internet as needed, allowing users to access an advanced service environment without the need to directly manage physical hardware.
[0004] Along with this, the emergence of container technology has brought about significant changes in software development and deployment environments. Containers are lightweight virtualization technologies that isolate applications from their execution environments, enabling the rapid and stable deployment and management of applications. In particular, containers allow for the efficient utilization of system resources and offer the advantage of maintaining consistency between development and production environments. Thanks to these characteristics, container technologies such as Docker have spread rapidly and are widely used in various applications.
[0005] Meanwhile, the automated construction and operation of CI / CD (Continuous Integration / Continuous Deployment) pipelines has become an essential element in cloud environments. CI / CD refers to a series of processes that automatically build, test, and deploy code changes within the software development cycle through Continuous Integration (CI) and Continuous Deployment (CD). By adopting CI / CD pipelines, developers can merge code changes more frequently, deploy them rapidly to production environments, and quickly detect and fix bugs or issues. This significantly reduces application deployment times and contributes greatly to delivering high-quality software more reliably.
[0006] However, building and managing CI / CD pipelines in a cloud environment remains complex and involves a significant amount of manual configuration. Developers consume a substantial amount of time and resources manually installing various open-source tools and connecting and configuring them to the cluster. Furthermore, managing nodes within the cluster, executing automated tasks, and monitoring the status of deployed applications in real time require considerable effort.
[0007] Therefore, to address these issues, there is a need for a service that automatically builds and manages CI / CD pipelines in a cluster. In this regard, Korean Registered Patent Publication No. 10-1998564 discloses a method for multi-cluster provisioning and management on a cloud platform. The problem to be solved
[0009] The present disclosure is conceived based on the aforementioned background technology and aims to provide a method, apparatus, and program for providing a cluster management service that automatically builds a CI / CD pipeline in a cluster. means of solving the problem
[0011] In order to solve the aforementioned problem, a computer program stored on a computer-readable storage medium is disclosed according to one embodiment of the present disclosure. The computer program performs the following methods for providing a cluster management service that automatically builds a CI / CD pipeline in a cluster, wherein the method may include: receiving a Container DevOps installation request from a cloud web upon creating a new cluster at a user terminal; performing a node join for the new cluster at the user terminal and, when the node join is completed, creating a job pod for an automation task; and obtaining an automation job execution result from the job pod for the automation task and returning the success or failure of the Container DevOps installation to the cloud web.
[0012] Alternatively, when the above Container DevOps installation request is received, the step of calling OpenStack to create a virtual machine may be further included.
[0013] Alternatively, the step of creating the virtual machine may include: a step of recognizing the resource requirements of the new cluster; and a step of creating the virtual machine by allocating resources corresponding to the resource requirements.
[0014] Alternatively, the step of performing a node join for a new cluster of the user terminal and creating a job pod for automation work when the node join is completed may include: requesting a connection to a node corresponding to the new cluster from a customer cluster; querying whether the node corresponding to the new cluster is connected to the customer cluster; and creating the job pod for automation work when the node is connected to the customer cluster.
[0015] Alternatively, the job pod for the automation task may execute an automation script for the Container DevOps installation, and the automation script may include the action of installing and configuring a DevOps tool including at least one of Jenkins, Gitlab, and Nexus.
[0016] Alternatively, the customer cluster may query the status of the DevOps tool installed in the new cluster and return the query result to the job pod for the automation task, and the job pod for the automation task may transmit the result of the automation job execution to the cluster management service based on the query result.
[0017] Alternatively, the above-mentioned job pod for automation tasks may execute an automation script for configuration actions for the above-mentioned DevOps tools to request configuration changes for at least one of the above-mentioned Jenkins, the above-mentioned Gitlab, and the above-mentioned Nexus to the above-mentioned customer cluster, and the above-mentioned customer cluster may return the processing result for the configuration changes to the above-mentioned job pod for automation tasks.
[0018] Alternatively, the step of obtaining the result of performing an automation job from the above-mentioned job pod for the automation task and returning the success or failure of the above-mentioned Container DevOps installation to the above-mentioned cloud web may include the step of returning the result that the Container DevOps installation was successful to the above-mentioned cloud web when it is recognized that the above-mentioned Container DevOps installation was successful based on the result of performing the above-mentioned automation job.
[0019] Alternatively, the step of obtaining the result of performing an automation job from the above-mentioned job pod for the automation task and returning the success or failure of the Container DevOps installation to the above-mentioned cloud web may include: a step of returning the result that the Container DevOps installation failed to the above-mentioned cloud web when it is recognized that the Container DevOps installation failed based on the result of performing the above-mentioned automation job; a step of recognizing the failure section when a retry request for the Container DevOps installation is received from the above-mentioned cloud web; and a step of retrying the installation for the failure section.
[0020] Alternatively, when a retry request for the Container DevOps installation is received from the cloud web, the step of recognizing the failure section may include: a step of obtaining a log corresponding to the result of the automation job execution; and a step of recognizing a specific tool that failed to install based on the log.
[0021] Alternatively, the step of retrying the installation for the failure section may include: a step of recognizing a script portion corresponding to the specific tool that failed to install in the automation script of the automation job pod; and a step of sending a re-execution command to the automation job pod to re-execute the script portion.
[0022] Alternatively, it may further include the step of obtaining a re-execution result according to the re-execution command from the job pod for the automation task and returning the success or failure of the Container DevOps installation to the cloud web.
[0023] Alternatively, the cloud web may, upon receiving the Container DevOps installation request from the user terminal as it creates a new cluster at the user terminal, forward the Container DevOps installation request to a cluster management service, and upon receiving the success or failure of the Container DevOps installation from the cluster management service, forward the success or failure of the Container DevOps installation to the user terminal.
[0024] Alternatively, a computer device is disclosed. The computer device comprises one or more processors; a memory for storing instructions executable on the one or more processors; and a network unit capable of communicating with at least one of a cloud web and a customer cluster. The one or more processors can receive a Container DevOps installation request from the cloud web as a new cluster is created at a user terminal, perform a node join for the new cluster at the user terminal, create a job pod for automation tasks when the node join is completed, obtain an automation job execution result from the job pod for automation tasks, and return to the cloud web whether the Container DevOps installation was successful.
[0025] Alternatively, a method for providing a cluster management service that automatically builds a CI / CD pipeline in a cluster is disclosed. The method may include: receiving a Container DevOps installation request from a cloud web as a new cluster is created on a user terminal; performing a node join for the new cluster on the user terminal and, when the node join is completed, creating a job pod for an automation task; and obtaining an automation job execution result from the job pod for the automation task and returning the success or failure of the Container DevOps installation to the cloud web. Effects of the invention
[0027] The present disclosure enables rapid development and deployment tasks by automatically building CI / CD pipelines in a cluster, and allows developers to deploy applications to a production environment more quickly by minimizing manual work. Brief explanation of the drawing
[0029] FIG. 1 is an overall flowchart of a cluster management service according to one embodiment of the present disclosure. FIGS. 2 to 6 are flowcharts illustrating a method for providing a cluster management service that automatically builds a CI / CD pipeline in a cluster according to one embodiment of the present disclosure. FIG. 7 illustrates a brief and general schematic diagram of an exemplary computing environment in which embodiments of the present disclosure may be implemented. Specific details for implementing the invention
[0030] Various embodiments are now described with reference to the drawings. In this specification, various descriptions are provided to provide an understanding of the present disclosure. However, it is evident that these embodiments can be practiced without such specific descriptions.
[0031] As used herein, terms such as “component,” “module,” “system,” etc. refer to computer-related entities, hardware, firmware, software, combinations of software and hardware, or executions of software. For example, a component may be, but is not limited to, a procedure executed on a processor, a processor, an object, an execution thread, a program, and / or a computer. For example, both an application executed on a computer device and the computer device itself may be a component. One or more components may reside within a processor and / or an execution thread. A component may be localized within a single computer. A component may be distributed among two or more computers. Additionally, these components may be executed from various computer-readable media having various data structures stored therein. Components may communicate through local and / or remote processes, for example, according to signals having one or more data packets (e.g., data from a component interacting with another component in a local system or distributed system, and / or data transmitted through signals to other systems and networks such as the Internet).
[0032] Furthermore, the term "or" is intended to mean an implicit "or" rather than an exclusive "or." That is, unless otherwise specified or evident from the context, "X uses A or B" is intended to mean one of the natural implicit substitutions. In other words, if X uses A; if X uses B; or if X uses both A and B, "X uses A or B" may apply to any of these cases. Additionally, the term "and / or" as used herein should be understood to refer to and include all possible combinations of one or more of the enumerated related items.
[0033] Additionally, the terms “comprising” and / or “comprising” should be understood to mean that such features and / or components are present. However, the terms “comprising” and / or “comprising” should be understood not to exclude the presence or addition of one or more other features, components and / or groups thereof. Furthermore, unless otherwise specified or clearly evident from the context to indicate a singular form, the singular in this specification and claims should generally be interpreted to mean “one or more.”
[0034] And, the term “at least one of A or B” should be interpreted to mean “a case including only A,” “a case including only B,” or “a combination of A and B.”
[0035] Those skilled in the art should recognize that the various exemplary logical blocks, configurations, modules, circuits, means, logics, and algorithmic steps described in connection with the embodiments disclosed herein may be implemented in electronic hardware, computer software, or a combination of both. To clearly exemplify the interchangeability of hardware and software, various exemplary components, blocks, configurations, means, logics, modules, circuits, and steps have been generally described above in terms of their functionality. Whether such functionality is implemented in hardware or software depends on the specific application and design constraints imposed on the overall system. Skilled technicians may implement the described functionality in various ways for each specific application. However, such decisions regarding implementation should not be construed as going beyond the scope of this disclosure.
[0036] The description of the presented embodiments is provided to enable those skilled in the art to use or practice the present invention. Various modifications to these embodiments will be apparent to those skilled in the art. The general principles defined herein may be applied to other embodiments without departing from the scope of the present disclosure. Thus, the present invention is not limited to the embodiments presented herein. The present invention should be interpreted in the broadest possible scope consistent with the principles and novel features presented herein.
[0038] FIG. 1 is an overall flowchart of a cluster management service according to one embodiment of the present disclosure.
[0039] Referring to FIG. 1, the service (10) of the present disclosure can be performed through a user terminal (11), a cloud web (12), a cluster management service (13), a customer cluster (14), and a job pod (15) for automation work.
[0040] The user terminal (11) can be connected to the cloud web (12) via a network and may be a user terminal that uses the function of automatically building a CI / CD pipeline in a cluster provided by the cluster management service (13). For example, the user terminal (11) may include a terminal of a developer who develops software in a cloud environment. Here, the user terminal may include, for example, various types of computer devices. Specifically, for example, the user terminal may refer to various terminal devices such as smartphones, tablet PCs, desktops, and laptops. However, it is not limited thereto.
[0041] In one embodiment, the user terminal (11) can transmit a request to install Container DevOps to the cloud web (12) when the user clicks the Container DevOps install button at the time of cluster creation or after cluster creation (S1). Here, Container DevOps is a platform that automates and manages the development, deployment, and operation of container-based applications, and may be a software module for optimizing the security and performance of the cluster by integrating DevOps tools such as Private Git, Jenkins, Helm, and Istio. For example, Container DevOps may provide automatic image building, monitoring, scaling, and rollback functions.
[0042] The cloud web (12) may be driven by a computing device that provides a server or cluster management service configured separately to drive the cloud web. The cloud web server may include various computer systems such as a microprocessor, a mainframe computer, and a digital processor.
[0043] In one embodiment, the cloud web (12) serves to connect the user terminal (11) and the cluster management service (13), and can perform the function of receiving user requests, such as a request to install Container DevOps, and processing or forwarding them. To perform this function, the cloud web (12) can be provided to the user in the form of an intuitive and easily accessible web UI, thereby allowing the user to easily perform various tasks such as cluster configuration, monitoring, and DevOps environment installation.
[0044] In one embodiment, the cloud web (12) connects a user terminal (11) and a cluster management service (13) and may provide a function to receive a request from the user terminal (11) and process or forward the request. Here, the cloud web server operating the cloud web (12) may include any type of computer system or computer device, such as, for example, a microprocessor, a mainframe computer, a digital processor, a portable device, and a device controller. However, it is not limited thereto.
[0045] In one embodiment, the cloud web (12) can forward a Container DevOps installation request received from a user terminal (11) to a cluster management service (13) (S2). The Container DevOps installation request may include information for installing a DevOps environment.
[0046] The cluster management service (13) can provide various cluster management tasks such as creating, configuring, monitoring, and maintaining the cluster. This cluster management service (13) can be processed by a computing device. That is, various operations related to the cluster management service (13) can be performed by a computing device. Here, the computing device may include one or more processors, a memory that stores instructions executable on one or more processors, and a network unit capable of communicating with at least one of the cloud web (12) and the customer cluster (14). However, it is not limited thereto.
[0047] In one embodiment, a cluster management service (13) that receives a Container DevOps installation request may call OpenStack (internal) as needed to create a virtual machine (VM) (S3). At this time, the cluster management service (13) allocates appropriate resources so that the cluster can operate normally.
[0048] Additionally, the cluster management service (13) can perform a node join operation (S4-1) to connect a node to the customer cluster (14) and check the status of whether the node has been successfully connected (S4-2). In this case, the cluster management service (13) can receive a result corresponding to the node status inquiry from the customer cluster (14) (S4-3). Once the node join is completed, the cluster management service (13) can proceed with the task of building a DevOps environment by creating a job pod (15) for automation work within the customer cluster (14) (S5).
[0049] In this way, the cluster management service (13) can process a Container DevOps installation request from a user and build the DevOps environment required by the user in the customer cluster (14) in an automated manner.
[0050] The customer cluster (14) is a cluster based on a container orchestration platform such as Kubernetes and can be composed of nodes for running various applications.
[0051] In one embodiment, the customer cluster (14) can receive a node join request from the cluster management service (13), add a new node to the cluster, and manage the state of the node. Additionally, the customer cluster (14) can provide an execution environment for job pods (15) for automation tasks.
[0052] The job pod (15) for automation tasks may be a container-based unit of work that automates the installation and configuration of DevOps tools created within a customer cluster (14). The job pod (15) for automation tasks executes scripts or commands required when installing or configuring specific DevOps tools and can perform the role of processing tasks in an automated manner within the cluster.
[0053] In one embodiment, the job pod (15) for automation tasks can execute an automation script to install and configure DevOps tools. Additionally, when the installation and configuration of the DevOps tools are completed, the job pod (15) for automation tasks can query the status of each tool and return the result to the customer cluster (14). Additionally, the job pod (15) for automation tasks can query the entire information of the cluster to perform configuration changes or optimizations required by the user.
[0054] Specifically, the job pod (15) for automation tasks can create DevOps tools such as Jenkins, GitLab, and Nexus in the cluster (S6-1), query the status of the tools (S6-2), and receive a result regarding the creation status of the tools from the customer cluster (14) (S6-3). Additionally, the job pod (15) for automation tasks can query cluster information (e.g., node status, resource usage, network configuration, etc.) (S6-4) and receive a result regarding cluster information from the customer cluster (14) (S6-5). Additionally, the job pod (15) for automation tasks can change the settings for DevOps tools such as Jenkins, GitLab, and Nexus (S6-6) and receive a result regarding whether the setting change has been reflected from the customer cluster (14) (6-7).
[0055] The job pod (15) for automation tasks can check whether the installation was successful when the installation process for the DevOps tools is completed. Then, if the installation of the DevOps tools is successfully completed, the job pod (15) for automation tasks can transmit an installation success signal to the cluster management service (13) (S7). The cluster management service (13) transmits this to the user terminal (11) via the cloud web (12) (S8-1).
[0056] Meanwhile, the job pod (15) for automation tasks can transmit an installation failure signal to the cluster management service (13) if the installation of DevOps tools fails (S7). In this case, a retry option may be provided to the user via the cloud web (12).
[0057] If the installation of DevOps tools fails, the cluster management service (13) transmits an installation failure signal to the cloud web (12) (S8-2), and the user can retry the installation (S9) by clicking the 'Container DevOps' retry button provided by the cloud web (12). When the retry request is transmitted, the cloud web (12) can process the failure section and send a signal to the cluster management service (13). The cluster management service (13) resumes the installation from the previously failed section, and the job pod (15) for automation tasks can retry the installation of the specific tool that failed.
[0058] Accordingly, the present disclosure provides a method for automatically building a CI / CD pipeline in a cluster, thereby enabling the rapid establishment of a development environment by automatically installing and configuring key processes and related tools required for development. Furthermore, the present disclosure provides an automated retry function in the event of installation failure, which can enhance user convenience and improve installation efficiency.
[0059] The service (10) illustrated in FIG. 1 is according to one embodiment, and the components related to the service (10) are not limited to the embodiment illustrated in FIG. 1 and may be added, changed, or deleted as needed.
[0060] In the following description, various operations for providing a cluster management service that automatically builds a CI / CD pipeline in the cluster of the present disclosure may be performed by a computing device.
[0061] FIGS. 2 to 6 are flowcharts illustrating a method for providing a cluster management service that automatically builds a CI / CD pipeline in a cluster according to one embodiment of the present disclosure.
[0062] Referring to FIG. 2, as the computing device creates a new cluster at the user terminal (11), it can receive a Container DevOps installation request from the cloud web (12) (S110).
[0063] For example, when the cloud web (12) creates a new cluster on a user terminal (11), if the user selects the 'Container DevOps' installation option, the installation request can be forwarded to the cluster management service (13). Accordingly, the computing device can receive the Container DevOps installation request from the cloud web (12).
[0064] Specifically, the computing device can analyze the installation request received from the cloud web (12) and extract various parameters required for installation.
[0065] More specifically, the computing device can parse installation request data delivered in a data format such as JSON or XML, and then identify and extract essential parameters such as the cluster identifier, a list of DevOps tools, resource requirements, and network configuration information. During the parsing process, the computing device interprets the data based on key values such as "cluster_id", "tools", and "resource_requirements", thereby obtaining information related to the cluster to be installed.
[0066] Subsequently, the computing device can perform validation on the extracted parameters. For example, the computing device (100) can check whether a cluster identifier exists, whether the list of DevOps tools is valid, whether resource requirements are sufficient, etc. Additionally, configuration parameters may be created to reflect the installation of plugins for DevOps tools requested by the user or special settings. That is, the parameters may include the identifier (ID) of the cluster to be installed, a list of DevOps tools to be installed (e.g., Jenkins, GitLab, Nexus), custom settings, resource requirements, etc. Based on the parameters, the computing device can establish an installation plan and determine the necessary resources.
[0067] For example, an installation request may include a cluster identifier, a list of DevOps tools to be installed, configuration information for each tool, and specifications of required resources (e.g., number of CPU cores, memory capacity, storage size). This allows the computing device to obtain all the information necessary for the installation process and efficiently perform subsequent steps.
[0068] In various embodiments, referring to FIG. 3, when a computing device receives a Container DevOps installation request, it can call OpenStack to create a virtual machine (S140).
[0069] Specifically, the computing device can recognize the resource requirements of a new cluster. In addition, the computing device can create virtual machines by allocating resources corresponding to the resource requirements.
[0070] More specifically, the computing device can create virtual machines using OpenStack’s Compute Service (Nova) based on resource requirements extracted from the installation request. For example, the computing device selects an appropriate operating system image (e.g., Ubuntu 20.04 LTS) and configures network settings and security groups to ensure the virtual machine operates smoothly in a cluster environment. Additionally, the computing device can create virtual machines by specifying the number of CPU cores, memory capacity, and storage size according to resource requirements. Furthermore, the computing device can connect an appropriate virtual network interface to the virtual machine for network connectivity and configure security groups to control access from the outside.
[0071] Referring again to FIG. 2, the computing device performs a node join for a new cluster of user terminals (11), and when the node join is completed, it can create a job pod (15) for automation work (S120).
[0072] Specifically, referring to FIG. 4, the computing device may request a connection to a node corresponding to a new cluster from the customer cluster (14) (S121).
[0073] More specifically, the computing device can install a Kubernetes node agent on the created virtual machine and apply authentication information and settings to join the node to the customer cluster (14).
[0074] Authentication information for joining a node to a customer cluster (14) may refer to a certificate for securely joining a node to a cluster according to the security settings of the cluster. This authentication information is generated by a cluster manager and may include a TLS certificate and a token.
[0075] The settings for joining a node to a customer cluster (14) may include network settings for the node to communicate with the cluster, the address of the API server, and pod network configuration, and other settings for seamless interaction with the cluster.
[0076] For example, a computing device can execute a node join command using a cluster management tool (kubeadm). Here, the cluster management tool uses the provided token and the address of the API server to ensure that the node is securely joined to the cluster. Through this, the new node communicates with the API server of the customer cluster (14) and can be successfully added to the cluster.
[0077] The computing device can check whether a node corresponding to a new cluster is connected to the customer cluster (14) (S122).
[0078] Specifically, the computing device can check the status information of the customer cluster (14) to determine whether the new node is successfully registered and operating in a 'Ready' state (e.g., a state in which the node has successfully joined the cluster in Kubernetes and is ready to perform tasks). Through this, the computing device can determine whether the node join operation has been successfully completed.
[0079] For example, a compute device can call the Kubernetes API server to query the list of nodes in the cluster and check the status of each node. In this case, if a node is not displayed as "Ready" or is displayed as "NotReady" or "Unknown," the compute device can resolve the issue by performing additional actions (e.g., troubleshooting network connectivity problems, resolving resource shortages, restarting nodes, analyzing logs and events, etc.).
[0080] When a computing device is connected to a customer cluster (14), it can create a job pod (15) for automation tasks (S123). Here, the job pod (15) for automation tasks is a pod created to automatically handle specific tasks in a Kubernetes environment and can perform automated tasks such as the installation and configuration of DevOps tools. Additionally, the job pod (15) for automation tasks can be composed of one or more containers and can provide an environment that can automatically execute DevOps-related tasks, including installation scripts or configuration files.
[0081] Specifically, the computing device can create a job or deployment resource in Kubernetes to deploy a job pod (15) for automation tasks. Here, the job pod (15) for automation tasks includes a script that automates the installation and configuration of DevOps tools and can perform necessary tasks within the cluster.
[0082] For example, a computing device can configure an automation script based on a list of DevOps tools to be installed and configuration information, and run a job pod (15) for automation tasks using a container image containing the script.
[0083] In one embodiment, a job pod (15) for automation tasks can execute an automation script for installing Container DevOps. Here, the automation script may include the action of installing and configuring a DevOps tool including at least one of Jenkins, Gitlab, and Nexus.
[0084] For example, the job pod (15) for automation tasks can be deployed to Kubernetes using Jenkins container images. Additionally, the job pod (15) for automation tasks can set up a Persistent Volume for Jenkins data retention. Furthermore, the job pod (15) for automation tasks can automate the creation of an initial administrator account and the installation of necessary plugins. As another example, the job pod (15) for automation tasks can install GitLab using the Helm package manager in Kubernetes. Additionally, the job pod (15) for automation tasks can initialize user accounts and projects and set up a code repository. Furthermore, the job pod (15) for automation tasks can configure SSH keys and access permissions to enable seamless use by developers. As yet another example, the job pod (15) for automation tasks can deploy Nexus Repository Manager to Kubernetes. In addition, the job pod (15) for automation tasks can create various types of repositories (Maven, npm, etc.) and set access control. Also, the job pod (15) for automation tasks can set the storage and management policy for artifacts to build an efficient build environment.
[0085] Meanwhile, the customer cluster (14) can query the status of the DevOps tools installed in the new cluster and return the query result to the job pod (15) for automation tasks. In this case, the job pod (15) for automation tasks can transmit the result of performing the automation job to the cluster management service (13) based on the query result.
[0086] Specifically, the customer cluster (14) can monitor the deployment status, pod status, service status, etc. of each DevOps tool. For example, the customer cluster (14) can check whether the pods of each tool are running normally and whether the service is being exposed correctly. In addition, the customer cluster (14) can transmit various status information to the job pods (15) for automation tasks to determine whether the installation and configuration tasks are successful.
[0087] In various embodiments, the job pod (15) for automation tasks may execute an automation script for configuration actions for DevOps tools to request a configuration change for at least one of Jenkins, Gitlab, and Nexus from the customer cluster (14). In this case, the customer cluster (14) may return the processing result for the configuration change to the job pod (15) for automation tasks.
[0088] Specifically, the job pod (15) for automation tasks can perform configuration change tasks by utilizing the API or command-line interface (CLI) of each DevOps tool.
[0089] For example, the job pod (15) for automation tasks can create new pipelines or install plugins via the Jenkins CLI in the case of Jenkins. Additionally, the job pod (15) for automation tasks can manage project and user permissions using the REST API in the case of GitLab. As another example, the job pod (15) for automation tasks can automatically perform tasks such as creating a new build job in Jenkins, creating a new code repository in GitLab, and setting up a new repository in Nexus.
[0090] Referring again to FIG. 2, the computing device can obtain the result of performing an automation job from a job pod (15) for automation work and return the success or failure of the Container DevOps installation to the cloud web (12) (S130). Here, when the cloud web (12) receives the success or failure of the Container DevOps installation from the cluster management service (13), it can transmit the success or failure of the Container DevOps installation to the user terminal (11).
[0091] Specifically, referring to FIG. 5, the computing device can obtain the results of an automated job execution from a job pod for an automated task (S131). Here, the results of the job execution may include the success or failure of the installation and configuration process of each DevOps tool, information on errors that occurred, warning messages, etc.
[0092] Specifically, the computing device can determine whether the installation work was successful by analyzing the installation logs and status information collected by the job pod (15) for the automation work. For example, the computing device can determine whether all DevOps tools have been successfully installed and configured and whether each service is operating normally based on the logs and status information.
[0093] When the computing device recognizes that the Container DevOps installation was successful based on the results of the automation job execution, it can return the result that the Container DevOps installation was successful to the cloud web (12) (S132).
[0094] Specifically, the computing device can generate URLs to access each DevOps tool, initial login information, etc., along with the installation success result, and transmit them to the cloud web (12). Through this, the user can immediately use the installed DevOps tool.
[0095] For example, the computing device can send an installation completion message to the cloud web (12) including Jenkins administrator URL and login information, GitLab web interface address and Nexus repository access information.
[0096] Meanwhile, if the computing device recognizes that the Container DevOps installation failed based on the results of the automation job execution, it can return the result that the Container DevOps installation failed to the cloud web (12) (S133).
[0097] Specifically, the computing device can generate a failure result including error messages and information about the cause of failure that occurred during the installation process.
[0098] For example, the computing device can transmit to the cloud web (12) that a network error occurred during the installation of a specific DevOps tool or that the installation failed due to a lack of resources.
[0099] After the computing device returns the result that the Container DevOps installation failed to the cloud web (12), if it receives a request to retry the Container DevOps installation from the cloud web (12), it can recognize the failure section (S134).
[0100] Specifically, the computing device can obtain logs corresponding to the results of the automation job execution. Additionally, the computing device can identify specific tools that failed to install based on the logs. Here, the logs may include information and error messages generated during the installation and configuration process of each DevOps tool. Furthermore, based on the log data, the computing device can identify which DevOps tool installation had a problem and at which stage the failure occurred.
[0101] More specifically, the computing device identifies the section where the problem occurred by analyzing the time of failure and the cause of failure in the logs of the automation job execution results. In this process, the computing device can specifically filter the log data to extract and analyze error or warning messages that occurred during the installation phase of a specific tool.
[0102] For example, the computing device can track the installation order and status of each DevOps tool by analyzing log files in the order in which automation tasks were performed. This allows the computing device to verify accurate time information and detailed status regarding the stage where a problem occurred.
[0103] As another example, a computing device can accurately identify the cause of failure by filtering error messages in log files based on specific keywords (e.g., "Error", "Failed", "Timeout"). This allows the computing device to identify which DevOps tool installation process caused the error.
[0104] As another example, computing devices can analyze detailed error messages included in logs, such as HTTP status codes, file path errors, or resource shortage warnings, to identify the specific reason for the problem. For instance, if a 404 Not Found error occurs during Nexus installation, it can recognize the possibility that the path to the Nexus installation file is incorrect or that the file has been deleted from the repository.
[0105] As another example, computing devices can analyze warning messages in logs related to resource shortages or network errors. Specifically, for instance, if a "Jenkins installation failed due to insufficient memory" message is found in the logs, it can be recognized that there are insufficient resources required for the installation task, indicating that the Jenkins installation failed as a result.
[0106] If the computing device recognizes a failure section, it can retry the installation for the failure section (S135).
[0107] Specifically, the computing device can recognize the part of the script corresponding to a specific tool that failed to install in the automation script of the automation job pod (15). Additionally, the computing device can send a re-execute command to the automation job pod (15) to re-execute the part of the script. Here, the re-execute command may include new parameters or options that can resolve the cause of the error by reflecting specific modifications related to the log analysis results of the failed step.
[0108] And, the computing device can obtain the result of a re-execution according to a re-execution command from the job pod (15) for automation work and return the success or failure of the Container DevOps installation to the cloud web (12).
[0109] That is, the computing device can be configured to re-execute the part of the script corresponding to a specific tool that failed in the automation script of the job pod (15) for automation tasks. To do this, the computing device may adjust necessary parameters or take additional measures to resolve the cause of the error (e.g., reconfiguring network settings or increasing resource allocation). Additionally, the computing device may update related packages or dependencies to reflect changes in the installation environment or attempt to roll back to a previous version of the tool. Furthermore, the computing device (100) may attempt the installation again by sending a retry command to the job pod (15) for automation tasks.
[0110] For example, if the network issue was temporary, the computing device may wait for a certain period of time and then retry, or if the cause was a lack of resources, it may allocate additional resources and then retry the installation. Additionally, if the installation fails due to an overload on a specific node within the cluster, the computing device may adjust the load on that node or redeploy the task to another node.
[0111] Then, if the installation is successful after a retry, the computing device returns the successful installation result to the cloud web (12), and the user can use the DevOps tool normally. If the installation fails even after a retry, the computing device can return the failure result including detailed error information and guide additional measures (e.g., a second retry function). In this process, to prevent repeated failures, the computing device can provide an alternative installation path (e.g., downloading an image from another repository, changing the network path) or new setting values (e.g., increasing resource limits, increasing timeout values) for the problematic section.
[0112] Therefore, computing devices can provide cluster management services that automatically build CI / CD pipelines within the cluster through the aforementioned steps. This minimizes complex manual tasks in a cloud environment and enables the rapid installation and configuration of DevOps tools in an automated manner. Furthermore, by detecting errors during the installation process in real time and efficiently resolving issues through retries, the stability and consistency of development and deployment operations can be enhanced. Through this process, users can prepare the development environment more quickly and maximize operational efficiency by optimizing system resources.
[0114] FIG. 7 illustrates a brief and general schematic diagram of an exemplary computing environment in which embodiments of the present disclosure may be implemented.
[0115] Although the present disclosure has been described as generally being implementable by a computer device, those skilled in the art will understand that the present disclosure may be implemented in combination with computer-executable instructions and / or other program modules that can be executed on one or more computers and / or as a combination of hardware and software.
[0116] Generally, a program module includes routines, programs, components, data structures, etc., that perform a specific task or implement a specific abstract data type. Furthermore, those skilled in the art will be well aware that the method of the present disclosure may be implemented in other computer system configurations, including single-processor or multi-processor computer systems, minicomputers, mainframe computers, as well as personal computers, handheld computer devices, microprocessor-based or programmable consumer electronics, etc. (each of which may be connected to and operated with one or more associated devices).
[0117] The embodiments described in this disclosure may also be implemented in a distributed computing environment in which tasks are performed by remote processing devices connected via a communication network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
[0118] Computers typically include various computer-readable media. Any medium accessible by a computer may be a computer-readable medium, and such computer-readable media include volatile and non-volatile media, transitory and non-transitory media, and removable and non-removable media. By example, but not limiting, computer-readable media may include computer-readable storage media and computer-readable transmission media. Computer-readable storage media include volatile and non-volatile media, transitory and non-transitory media, and removable and non-removable media implemented by any method or technique for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, DVD (digital video disk) or other optical disk storage devices, magnetic cassettes, magnetic tapes, magnetic disk storage devices or other magnetic storage devices, or any other media that can be accessed by a computer and used to store desired information.
[0119] Computer-readable transmission media typically include all information transmission media that implement computer-readable instructions, data structures, program modules, or other data, etc., on a modulated data signal, such as a carrier wave or other transport mechanism. The term modulated data signal means a signal in which one or more of the characteristics of the signal are set or modified to encode information within the signal. By example, not limiting, computer-readable transmission media include wired media, such as wired networks or direct-wired connections, and wireless media, such as acoustic, RF, infrared, and other wireless media. Any combination of the media described above is also considered to be within the scope of computer-readable transmission media.
[0120] An exemplary environment (1100) for implementing various aspects of the present disclosure, including a computer (1102), is shown, wherein the computer (1102) includes a processing unit (1104), system memory (1106), and a system bus (1108). The system bus (1108) connects system components, including system memory (1106) (but not limited thereto), to the processing unit (1104). The processing unit (1104) may be any processor among various commercial processors. Dual processor and other multiprocessor architectures may also be used as the processing unit (1104).
[0121] The system bus (1108) may be any of several types of bus structures that can be additionally interconnected to a local bus using any of the memory bus, peripheral bus, and various commercial bus architectures. System memory (1106) includes read-only memory (ROM) (1110) and random access memory (RAM) (1112). The basic input / output system (BIOS) is stored in non-volatile memory (1110), such as ROM, EPROM, EEPROM, etc., and this BIOS includes basic routines that help transfer information between components within the computer (1102) at times such as during startup. The RAM (1112) may also include high-speed RAM, such as static RAM, for caching data.
[0122] The computer (1102) also includes an internal hard disk drive (HDD) (1114) (e.g., EIDE, SATA)—this internal hard disk drive (1114) may also be configured for external use within a suitable chassis (not shown)—a magnetic floppy disk drive (FDD) (1116) (e.g., for reading from or writing to a removable diskette (1118)), and an optical disk drive (1120) (e.g., for reading from a CD-ROM disk (1122) or reading from or writing to other high-capacity optical media such as a DVD). The hard disk drive (1114), the magnetic disk drive (1116), and the optical disk drive (1120) may each be connected to the system bus (1108) by a hard disk drive interface (1124), a magnetic disk drive interface (1126), and an optical drive interface (1128). The interface (1124) for implementing an external drive includes at least one or both of USB (Universal Serial Bus) and IEEE 1394 interface technologies.
[0123] These drives and associated computer-readable media provide non-volatile storage of data, data structures, computer-executable instructions, etc. In the case of a computer (1102), the drives and media correspond to storing any data in a suitable digital format. Although the description of computer-readable media above refers to HDDs, removable magnetic disks, and removable optical media such as CDs or DVDs, those skilled in the art will know that other types of computer-readable media, such as zip drives, magnetic cassettes, flash memory cards, cartridges, etc., may also be used in exemplary operating environments and that any of these media may contain computer-executable instructions for performing the methods of the present disclosure.
[0124] A number of program modules, including an operating system (1130), one or more application programs (1132), other program modules (1134), and program data (1136), may be stored in the drive and RAM (1112). All or part of the operating system, application, module and / or data may also be cached in RAM (1112). It will be well known that the present disclosure may be implemented in various commercially available operating systems or combinations of operating systems.
[0125] The user can input commands and information into the computer (1102) through one or more wired / wireless input devices, such as a pointing device like a keyboard (1138) and a mouse (1140). Other input devices (not shown) may include a microphone, an IR remote control, a joystick, a game pad, a stylus pen, a touch screen, etc. These and other input devices are often connected to the processing unit (1104) via an input device interface (1142) connected to the system bus (1108), but may also be connected via other interfaces such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, etc.
[0126] A monitor (1144) or other type of display device is also connected to the system bus (1108) via an interface such as a video adapter (1146). In addition to the monitor (1144), the computer generally includes other peripheral output devices (not shown), such as speakers, a printer, and so on.
[0127] The computer (1102) may operate in a networked environment using a logical connection to one or more remote computers, such as remote computer(s) (1148), via wired and / or wireless communication. The remote computer(s) (1148) may be a workstation, a computing device computer, a router, a personal computer, a portable computer, a microprocessor-based entertainment device, a peer device, or other conventional network node, and generally include many or all of the components described for the computer (1102), but for brevity, only the memory storage device (1150) is illustrated. The illustrated logical connection includes a wired / wireless connection to a local area network (LAN) (1152) and / or a larger network, e.g., a wide area network (WAN) (1154). Such LAN and WAN networking environments are common in offices and companies and facilitate enterprise-wide computer networks, such as intranets, all of which can be connected to a global computer network, e.g., the Internet.
[0128] When used in a LAN networking environment, the computer (1102) is connected to a local network (1152) via a wired and / or wireless communication network interface or adapter (1156). The adapter (1156) may facilitate wired or wireless communication to the LAN (1152), and the LAN (1152) may also include a wireless access point installed therein to communicate with the wireless adapter (1156). When used in a WAN networking environment, the computer (1102) may include a modem (1158), be connected to a communication computing device on the WAN (1154), or have other means to establish communication through the WAN (1154), such as through the Internet. The modem (1158), which may be an internal or external and a wired or wireless device, is connected to the system bus (1108) via a serial port interface (1142). In a networked environment, the program modules described for the computer (1102) or parts thereof may be stored in a remote memory / storage device (1150). It will be well known that the illustrated network connection is exemplary and that other means of establishing a communication link between computers may be used.
[0129] The computer (1102) operates to communicate with any wireless device or object that is deployed and operated by wireless communication, for example, a printer, scanner, desktop and / or portable computer, PDA (portable data assistant), communication satellite, any equipment or place associated with a wireless detectable tag, and a telephone. This includes at least Wi-Fi and Bluetooth wireless technologies. Accordingly, the communication may be a predefined structure as in a conventional network, or simply ad hoc communication between at least two devices.
[0130] Wi-Fi (Wireless Fidelity) enables connectivity to the Internet and other sources without wires. Wi-Fi is a wireless technology, similar to a cell phone, that allows devices, such as computers, to transmit and receive data indoors and outdoors—that is, anywhere within the coverage area of a base station. Wi-Fi networks use a wireless technology called IEEE 802.11 (a, b, g, etc.) to provide secure, reliable, and high-speed wireless connections. Wi-Fi can be used to connect computers to each other, to the Internet, and to wired networks (using IEEE 802.3 or Ethernet). Wi-Fi networks can operate in unlicensed 2.4 and 5 GHz wireless bands, for example, at data rates of 11 Mbps (802.11a) or 54 Mbps (802.11b), or in products that include both bands (dual band).
[0131] Those skilled in the art of the present disclosure will understand that information and signals may be represented using any various different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0132] Those skilled in the art will understand that the various exemplary logic blocks, modules, processors, means, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented by electronic hardware, various forms of programs or design code (referred to herein as software for convenience), or a combination of all such. To clearly illustrate this interoperability between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been generally described above in relation to their functions. Whether such functions are implemented as hardware or software depends on the design constraints imposed on the specific application and the overall system. Those skilled in the art may implement the functions described in various ways for each specific application, but such implementation decisions should not be interpreted as being outside the scope of this disclosure.
[0133] The various embodiments presented herein may be implemented as methods, devices, or articles manufactured using standard programming and / or engineering techniques. The term "article manufactured" includes a computer program, a carrier, or a medium accessible from any computer-readable storage device. For example, computer-readable storage media include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips, etc.), optical discs (e.g., CDs, DVDs, etc.), smart cards, and flash memory devices (e.g., EEPROMs, cards, sticks, key drives, etc.). Additionally, the various storage media presented herein include one or more devices and / or other machine-readable media for storing information.
[0134] It should be understood that the specific order or hierarchy of steps in the presented processes is an example of exemplary approaches. It should be understood that the specific order or hierarchy of steps in the processes may be rearranged within the scope of this disclosure based on design priorities. The appended method claims provide elements of various steps in a sample order, but do not imply being limited to the specific order or hierarchy presented.
[0135] Description of the presented embodiments is provided so that a person skilled in the art may use or practice the present disclosure. Various modifications to these embodiments will be apparent to a person skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the embodiments presented herein, but should be interpreted in the broadest possible scope consistent with the principles and novel features presented herein.
Claims
Claim 1 A computer program stored on a computer-readable storage medium for executing the following methods for providing a cluster management service that automatically builds a CI / CD pipeline in a cluster on a computer, wherein the method comprises: a step of receiving a Container DevOps installation request from a cloud web upon creating a new cluster at a user terminal; a step of performing a node join for the new cluster at the user terminal and creating a job pod for automation work when the node join is completed; and a step of obtaining an automation job execution result from the job pod for automation work and returning the success or failure of the Container DevOps installation to the cloud web; wherein the step of obtaining an automation job execution result from the job pod for automation work and returning the success or failure of the Container DevOps installation to the cloud web comprises: a step of returning a result indicating that the Container DevOps installation failed to the cloud web when the Container DevOps installation is recognized as having failed based on the automation job execution result; a step of recognizing a failure section when a retry request for the Container DevOps installation is received from the cloud web; and a step of retrying the installation for the failure section. Claim 2 A computer program stored on a computer-readable storage medium, further comprising the step of calling OpenStack to create a virtual machine when receiving the Container DevOps installation request in claim 1. Claim 3 A computer program stored on a computer-readable storage medium, wherein, in claim 2, the step of creating the virtual machine comprises: a step of recognizing the resource requirements of the new cluster; and a step of creating the virtual machine by allocating resources corresponding to the resource requirements. Claim 4 A computer program stored on a computer-readable storage medium, wherein, in claim 1, the step of performing a node join for a new cluster of the user terminal and, when the node join is completed, creating a job pod for an automation task comprises: a step of requesting a connection to a node corresponding to the new cluster to a customer cluster; a step of querying whether the node corresponding to the new cluster is connected to the customer cluster; and a step of creating the job pod for an automation task if the node is connected to the customer cluster. Claim 5 A computer program stored on a computer-readable storage medium, wherein the job pod for the automation task executes an automation script for the installation of the Container DevOps, and the automation script includes the operation of installing and configuring a DevOps tool including at least one of Jenkins, Gitlab, and Nexus. Claim 6 A computer program stored on a computer-readable storage medium, wherein, in claim 5, the customer cluster queries the status of the DevOps tool installed in the new cluster, returns the query result to the job pod for automation tasks, and the job pod for automation tasks transmits the result of performing the automation job to the cluster management service based on the query result. Claim 7 A computer program stored on a computer-readable storage medium, wherein the automation job pod executes an automation script for configuration actions for the DevOps tool to request a configuration change for at least one of the Jenkins, Gitlab, and Nexus to the customer cluster, and the customer cluster returns the processing result for the configuration change to the automation job pod. Claim 8 A computer program stored on a computer-readable storage medium, wherein, in claim 1, the step of obtaining an automation job execution result from the automation job pod and returning the success or failure of the Container DevOps installation to the cloud web includes: a step of returning a result indicating that the Container DevOps installation was successful to the cloud web when it is recognized that the Container DevOps installation was successful based on the automation job execution result. Claim 9 delete Claim 10 A computer program stored on a computer-readable storage medium, wherein, in the first aspect, when a retry request for the Container DevOps installation is received from the cloud web, the step of recognizing the failure section comprises: a step of obtaining a log corresponding to the result of the automation job execution; and a step of recognizing a specific tool that failed to install based on the log. Claim 11 A computer program stored on a computer-readable storage medium, wherein, in claim 10, the step of retrying the installation for the failure section comprises: a step of recognizing a script portion corresponding to the specific tool that failed to install in the automation script of the automation job pod; and a step of transmitting a re-execution command to the automation job pod to re-execute the script portion. Claim 12 A computer program stored on a computer-readable storage medium, further comprising the step of, in claim 11, obtaining a re-execution result according to the re-execution command from the job pod for the automation task and returning the success or failure of the Container DevOps installation to the cloud web. Claim 13 A computer program stored on a computer-readable storage medium according to claim 1, wherein the cloud web, upon receiving a Container DevOps installation request from the user terminal as it creates a new cluster at the user terminal, transmits the Container DevOps installation request to a cluster management service, and upon receiving a success or failure of the Container DevOps installation from the cluster management service, transmits the success or failure of the Container DevOps installation to the user terminal. Claim 14 A computer device comprising: one or more processors; a memory storing instructions executable on the one or more processors; and a network unit capable of communicating with at least one of a cloud web and a customer cluster; wherein the one or more processors receive a Container DevOps installation request from the cloud web upon creating a new cluster at a user terminal, perform a node join for the new cluster of the user terminal, create a job pod for an automation task when the node join is completed, obtain an automation job execution result from the automation job pod, return the success or failure of the Container DevOps installation to the cloud web, and if the Container DevOps installation is recognized as having failed based on the automation job execution result, return a result indicating that the Container DevOps installation has failed to the cloud web, and if a retry request for the Container DevOps installation is received from the cloud web, recognize the failure section and retry the installation for the failure section. Claim 15 A method for providing a cluster management service that automatically builds a CI / CD pipeline in a cluster, performed on a computing device, comprising: a step in which the computing device receives a Container DevOps installation request from a cloud web as the user terminal creates a new cluster; a step in which the computing device performs a node join for the new cluster of the user terminal and, when the node join is completed, creates a job pod for an automation task; and a step in which the computing device obtains an automation job execution result from the job pod for the automation task and returns the success or failure of the Container DevOps installation to the cloud web; wherein the step of obtaining an automation job execution result from the job pod for the automation task and returning the success or failure of the Container DevOps installation to the cloud web comprises: a step in which, if the computing device recognizes that the Container DevOps installation has failed based on the automation job execution result, the computing device returns a result indicating that the Container DevOps installation has failed to the cloud web; and a step in which, if the computing device receives a retry request for the Container DevOps installation from the cloud web, the computing device recognizes a failure section. A method comprising the step of the computing device retrying the installation for the failure section.
Citation Information
Patent Citations
DevOps Toolchain Automation
US20220091854A1
Cloud platform system
KR101826498B1
Apparatus for automating cloud building
KR1020240138948A
