No-service management method and device, equipment and storage medium
By dynamically matching the storage address and parameters of the camel-k source code, service images supporting multiple architectures are generated, solving the problem of tedious and labor-intensive manual compilation and realizing automated and visualized serviceless management.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHINA ELECTRONICS CLOUD DIGITAL INTELLIGENCE TECH CO LTD
- Filing Date
- 2023-03-13
- Publication Date
- 2026-06-05
AI Technical Summary
In the existing serviceless management approach, manually compiling service images that support multiple architectures is a cumbersome process that consumes a lot of manpower.
By dynamically matching the private storage address and harbor address in the camel-k source code, as well as related parameters and Maven repository parameters, service images supporting multiple architectures are generated, and service management files are generated based on modification records, achieving automated and visual management.
It simplifies the compilation process, saves manpower costs, and enables dynamic, automatic, and visual serverless management.
Smart Images
Figure CN116450140B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of no-service management technology, and in particular to a no-service management method, apparatus, device and storage medium. Background Technology
[0002] Serverless management is a cloud management approach that provides serverless computing on private or public clouds. Serverless computing, also known as Function as a Service (FaaS), is a new cloud computing paradigm that allows programmers to run event-driven functions in the cloud without managing resource allocation or runtime environment configuration. Serverless computing offers numerous advantages, such as reduced costs and ease of maintenance, making serverless management the foundation of serverless computing.
[0003] In general, serverless management involves compiling service images that support multiple architectures (such as camel-k services). However, serverless management methods in related technologies typically involve manually compiling these service images, a tedious process that consumes significant manpower. Summary of the Invention
[0004] To solve the above-mentioned technical problems, or at least partially solve them, this disclosure provides a serviceless management method, apparatus, device, and storage medium.
[0005] Firstly, this disclosure provides a service-free management method, the method comprising:
[0006] If a pre-created compilation task is obtained, the camel-k source code is downloaded from the intranet remote repository based on the source code download instruction in the pre-created compilation task. The compilation task is a task that supports compiling camel-k services for multiple architectures.
[0007] The private storage address in the camel-k source code is dynamically matched with multiple harbor addresses. Based on multiple first dynamic matching results, the private storage address in the camel-k source code is modified to the matching target harbor address. The relevant parameters in the camel-k source code are dynamically matched with multiple Maven repository parameters. Based on multiple second dynamic matching results, the relevant parameters in the camel-k source code are modified to the matching target Maven repository parameters.
[0008] Based on the camel-k source code containing the target harbor address and the target Maven repository parameters, a camel-k service is generated, wherein the camel-k service refers to a service image that supports multiple architectures;
[0009] Based on the modification records of the camel-k service, a no-service management file is generated and sent to the front end for display. The no-service management file is used to install or update the recorded camel-k service.
[0010] Secondly, this disclosure provides a serviceless management device, the device comprising:
[0011] The download module is used to download the camel-k source code from a remote intranet repository based on the source code download instructions in the pre-created compilation task when a pre-created compilation task is obtained. The compilation task is a task that supports compiling camel-k services for multiple architectures.
[0012] The modification module is used to dynamically match the private storage address in the camel-k source code with multiple harbor addresses, modify the private storage address in the camel-k source code to the matching target harbor address based on multiple first dynamic matching results, and dynamically match the relevant parameters in the camel-k source code with multiple Maven repository parameters, modify the relevant parameters in the camel-k source code to the matching target Maven repository parameters based on multiple second dynamic matching results.
[0013] The first generation module is used to generate a camel-k service based on the camel-k source code containing the target harbor address and the target Maven repository parameters, wherein the camel-k service refers to a service image that supports multiple architectures;
[0014] The second generation module is used to generate a no-service management file based on the dynamic modification records of the camel-k service, and send the no-service management file to the front end for display. The no-service management file is used to install or update the recorded camel-k service.
[0015] Thirdly, this disclosure also provides a serviceless management device, the serviceless management device comprising:
[0016] One or more processors;
[0017] Storage device for storing one or more programs.
[0018] When one or more programs are executed by one or more processors, the one or more processors implement the methods provided in the first aspect.
[0019] Fourthly, embodiments of this disclosure also provide a computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the method provided in the first aspect.
[0020] The technical solution provided in this disclosure has the following advantages compared with the prior art:
[0021] This disclosure discloses a serviceless management method, apparatus, device, and storage medium, comprising: upon obtaining a pre-created compilation task, downloading camel-k source code from an intranet remote repository based on source code download instructions in the pre-created compilation task, wherein the compilation task supports compiling camel-k services for multiple architectures; dynamically matching a private storage address in the camel-k source code with multiple harbor addresses; modifying the private storage address in the camel-k source code to the matched target harbor address based on multiple first dynamic matching results; and configuring relevant parameters in the camel-k source code with... The process involves dynamically matching parameters from multiple Maven repositories. Based on these matching results, relevant parameters in the Camel-K source code are modified to match the parameters of the target Maven repository. A Camel-K service is generated from the Camel-K source code, including the target Harbor address and target Maven repository parameters. This service image supports multiple architectures. Based on the modification history of the Camel-K service, a serviceless management file is generated and displayed on the front end. This file is used to install or update the recorded Camel-K service. Thus, by dynamically matching parameters, Camel-K services can be generated, creating service images that support multiple architectures. The resulting serviceless management file is then displayed on the front end, completing the serviceless management process. This simplifies the compilation process, saves manpower, and achieves dynamic, automatic, and visualized serviceless management. Attached Figure Description
[0022] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.
[0023] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0024] Figure 1 A schematic diagram of the architecture of a serviceless management platform provided in this disclosure embodiment;
[0025] Figure 2 A flowchart illustrating a serviceless management method provided in an embodiment of this disclosure;
[0026] Figure 3 A logical schematic diagram of a serviceless management method provided in an embodiment of this disclosure;
[0027] Figure 4 A logical schematic diagram of another service-free management method provided in this embodiment of the disclosure;
[0028] Figure 5 A logical schematic diagram of yet another service-free management method provided in this disclosure embodiment;
[0029] Figure 6 This is a schematic diagram of the structure of a serviceless management device provided in an embodiment of the present disclosure;
[0030] Figure 7 This is a schematic diagram of the structure of a serviceless management device provided in an embodiment of this disclosure. Detailed Implementation
[0031] To better understand the above-mentioned objectives, features, and advantages of this disclosure, the solutions disclosed herein will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.
[0032] Numerous specific details are set forth in the following description in order to provide a full understanding of this disclosure, but this disclosure may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only some, and not all, of the embodiments of this disclosure.
[0033] To address the aforementioned issues, this disclosure provides a serverless management platform, which can be understood as a backend server. Figure 1 This illustration shows an architecture diagram of a serviceless management platform provided in an embodiment of this disclosure.
[0034] like Figure 1As shown, the serviceless management platform includes: camel-k management module, runtime environment management module, Fax function management module, monitoring management module, and code development module.
[0035] The camel-k management module is used to send compilation commands through a front-end visual interface, compiling service support images that support multiple architectures, thus enabling dynamic compilation of camel-k services and serviceless management.
[0036] The runtime environment management module is used to install and update the runtime support services for Fass functions by sending installation commands through the front-end visual interface.
[0037] The Fass function management module is used to manage Fass functions. Fass functions support various file types, such as Java, JS, and Python. It also compiles and runs Fass functions and displays the compilation and execution results on a visual interface provided on the front end.
[0038] The monitoring and management module is used to monitor the execution results of the Fass function. Specifically, it can include monitoring the execution status of the Fass function at various execution times and generating monitoring logs.
[0039] The code development module provides a web-based integrated development environment (IDE) tool, which compiles and runs FASS functions.
[0040] Based on the architecture of the aforementioned serviceless management platform, this disclosure provides a serviceless management method, apparatus, device, and medium.
[0041] The following is combined Figures 2 to 5 The no-service management method provided in this disclosure embodiment will be described. In this disclosure embodiment, the no-service management method can be executed by a no-service management platform, that is, by a backend server.
[0042] Figure 2 A flowchart illustrating a serviceless management method provided in an embodiment of this disclosure is shown.
[0043] like Figure 2 As shown, the no-service management method may include the following steps.
[0044] S210. If a pre-created compilation task is obtained, download the camel-k source code from the intranet remote repository based on the source code download instruction in the pre-created compilation task. The compilation task is a task that supports compiling camel-k services for multiple architectures.
[0045] In this embodiment, when the serverless management platform performs serverless management to ensure serverless computing capabilities, it can pre-create compilation tasks that support camel-k services across multiple architectures. During serverless management, the platform obtains the compilation tasks, reads the source code download instructions within them, and downloads the camel-k source code from a remote intranet repository, enabling the generation of camel-k services based on the camel-k source code.
[0046] Among them, various architectures can be such as ARM64, x86-64, etc.
[0047] The internal remote repository is specifically a GitLab repository, which contains the camel-k source code used to generate the camel-k service.
[0048] S220. Dynamically match the private storage address in the camel-k source code with multiple harbor addresses. Based on multiple first dynamic matching results, modify the private storage address in the camel-k source code to the matching target harbor address. Also, dynamically match the relevant parameters in the camel-k source code with multiple Maven repository parameters. Based on multiple second dynamic matching results, modify the relevant parameters in the camel-k source code to the matching target Maven repository parameters.
[0049] In this embodiment, the serviceless management platform can pre-obtain multiple harbor addresses and multiple Maven repository parameters. It can then dynamically match the private storage address in the camel-k source code with each of the multiple harbor addresses and the relevant parameters in the camel-k source code with each of the multiple Maven repository parameters. Based on the dynamic matching results, it can modify the private storage address and relevant parameters in the camel-k source code.
[0050] The target harbor address refers to the address of the harbor repository, which can be used to store camel-k services.
[0051] Among them, the target Maven repository parameters refer to the relevant parameters of the Maven repository, which can be used to store the relevant dependencies of FASS functions.
[0052] S230. Generate a camel-k service based on the camel-k source code containing the target harbor address and target Maven repository parameters. Here, a camel-k service refers to a service image that supports multiple architectures.
[0053] In this embodiment, after obtaining the target harbor address and target Maven repository parameters through dynamic modification, the camel-k source code containing the target harbor address and target Maven repository parameters is compiled to generate a camel-k service, that is, to generate a service image that supports multiple architectures.
[0054] Furthermore, after generating the camel-k service, it can be stored in the target harbor repository based on the target harbor address, and the corresponding client service can be stored in the distributed storage node based on the pre-generated distributed storage node identifier. The camel-k service stored in the target harbor repository and the corresponding client service stored in the distributed storage node are used for subsequent installation or updates.
[0055] Among them, the pre-generated distributed storage node identifier is used to represent the address of the distributed storage node.
[0056] Therefore, service images supporting multiple architectures can be generated through dynamic matching, and the camel-k service and its corresponding client service can be stored separately for later use during installation or updates.
[0057] S240. Based on the modification records corresponding to the camel-k service, generate a no-service management file and send the no-service management file to the front end for display. The no-service management file is used to install or update the recorded camel-k service.
[0058] In this embodiment, the no-service management platform can generate a no-service management file based on the modification records corresponding to the camel-k service. This allows the platform to determine whether the camel-k service has been installed or updated when the service is subsequently installed or updated, based on the modification records. At the same time, the no-service management file is sent to the front end so that the front end can display the no-service management file on the visual interface.
[0059] The modification records include the private storage address in the camel-k source code, the target harbor address, related parameter modifications, and the target Maven repository parameters.
[0060] It should be noted that S210 to S240 above can be executed by the camel-k management module. To facilitate understanding of the management logic of the camel-k management module, Figure 3 A logical diagram of a serviceless management method is shown.
[0061] like Figure 3As shown, the method includes the following steps:
[0062] S31. Create a compilation task to obtain a task that supports compiling camel-k services for multiple architectures; S32. Download the camel-k source code from the GitLab repository; S33. Dynamically modify the private storage address and related parameters in the camel-k source code; S34. Based on the modified private storage address and related parameters, generate service images for compiling multiple architectures; S35. Store the camel-k service in the Harbor repository and distribute the client services corresponding to the camel-k service; S36. Based on the modification records corresponding to the camel-k service, generate a service management file.
[0063] Therefore, a no-service management file is generated based on the dynamic matching results to complete the no-service management process. At the same time, a visual interface is provided for users and administrators to view the no-service management results and display the no-service management file on the front end.
[0064] A serviceless management method according to an embodiment of this disclosure includes: upon obtaining a pre-created compilation task, downloading camel-k source code from an intranet remote repository based on the source code download instruction in the pre-created compilation task, wherein the compilation task is a task that supports compiling camel-k services for multiple architectures; dynamically matching the private storage address in the camel-k source code with multiple harbor addresses, modifying the private storage address in the camel-k source code to the matched target harbor address based on multiple first dynamic matching results, and dynamically matching relevant parameters in the camel-k source code with multiple Maven repository parameters, modifying the relevant parameters in the camel-k source code to the matched target Maven repository parameters based on multiple second dynamic matching results; generating a camel-k service based on the camel-k source code containing the target harbor address and target Maven repository parameters, wherein the camel-k service refers to a service image that supports multiple architectures; generating a serviceless management file based on the modification records of the camel-k service, and sending the serviceless management file to the front end for display, wherein the serviceless management file is used to install or update the recorded camel-k service. Therefore, camel-k services can be generated through dynamic matching, i.e., service images supporting multiple architectures can be generated. Based on the dynamic matching results, a serverless management file is generated and displayed on the front end to complete the serverless management process. This simplifies the compilation process and saves labor costs, thereby achieving dynamic, automatic, and visual serverless management.
[0065] In another embodiment of this disclosure, a visual interface can be provided at the front end, and the Fass function's runtime support service can be installed and updated based on the installation instructions received at the front end's visual interface.
[0066] Optionally, in this embodiment of the disclosure, after executing S240, the method further includes:
[0067] S250. Upon detecting the installation command sent by the front end, obtain the client service from the distributed storage node and download the camel-k service corresponding to the client service from the target Harbor repository.
[0068] S260. Determine whether the Fass function's execution support service exists, where the Fass function's execution support service includes camel-k service and client service;
[0069] S270. If the Fass function's runtime support service does not exist, then the client service is used to install the camel-k service into the container cluster management system to obtain the current version's runtime environment. The current version's runtime environment is the environment in which the camel-k service is installed.
[0070] S280. If the Fass function execution support service already exists, the obtained Fass function execution status is completed, and new Fass function execution requests are no longer received, the camel-k service is installed into the container cluster management system using the client service to obtain an updated version of the runtime environment. The obtained Fass function and its corresponding execution result are used to be stored in the distributed storage node.
[0071] The installation instruction refers to the request information generated by the front end based on the administrator's installation operation on the visual interface.
[0072] The container cluster management system is a Kubernetes cluster.
[0073] The Fass functions and their corresponding execution results that have been retrieved and stored in the distributed storage nodes can be restored when the Fass functions are run again, thus avoiding data loss during the upgrade process of the Fass function execution support service.
[0074] Understandably, after obtaining the camel-k service and its corresponding client service, if the serverless platform determines that the runtime support service for the Fass function does not exist, it will determine that the runtime support service for the Fass function has not been installed. It will then use the client service to install the camel-k service into the container cluster management system, thus installing the runtime support service for the Fass function. If the runtime support service for the Fass function is found, it will determine that the runtime support service for the Fass function has been installed, but it is not the latest version. It needs to further determine whether the obtained Fass function is running. If it is running, it will wait for the obtained Fass function to complete its execution and stop receiving new Fass function execution requests. When the running status of the obtained Fass function is "completed," it will update the runtime support service for the Fass function. This means using the client service to install the camel-k service into the container cluster management system to obtain an updated runtime environment, thus completing the update of the runtime support service for the Fass function.
[0075] It should be noted that S250 to S280 described above can be executed by the runtime environment management module. To facilitate understanding of the management logic of the runtime environment management module, Figure 4 A logical diagram of another serviceless management method is shown.
[0076] like Figure 4 As shown, the method includes the following steps:
[0077] S41. Obtain the installation command sent by the front end; S42. Obtain the client service from the distributed storage node and download the camel-k service corresponding to the client service from the target Harbor repository; S43. Determine if the Fass function's runtime support service exists. If the Fass function's runtime support service does not exist, execute S44; otherwise, execute S45; S44. Use the client service to install the camel-k service into the container cluster management system; S45. Determine if the obtained Fass function's runtime status is "completed". If the obtained Fass function's runtime status is not "completed", execute S46 and return to execute S45 until the obtained Fass function's runtime status is "completed", then execute S47; S46. Wait for the obtained Fass function's runtime status to be "completed" and stop receiving new Fass function runtime requests; S47. Install the camel-k service and client service into the container cluster management system to obtain an updated runtime environment.
[0078] Furthermore, the installed runtime environment and the updated runtime environment can be sent to the front end for display.
[0079] Therefore, a visual interface can be provided on the front end, and the installation support service for the Fass function can be installed and updated based on the installation instructions received on the front end visual interface, and the results of the installation and update of the runtime environment can be displayed on the visual interface.
[0080] In yet another embodiment of this disclosure, the FASS function can be compiled and run using a code development module, and the compilation and running results of the FASS function can be displayed on a visual interface provided on the front end.
[0081] Optionally, in this embodiment of the disclosure, after executing S280, the method further includes:
[0082] S290. Upon detecting a Fass function execution command sent by the front end, download the retained Fass function from the distributed storage node;
[0083] S291. Based on the current status of the Fass function's runtime support service, push the retained Fass functions to the container cluster management system;
[0084] S292. Install the runtime environment required by the Fass function;
[0085] S293. Compile and run the Fass function to obtain the result of the Fass function.
[0086] The Fass function execution command is a request message generated by the front end based on the administrator's operation on the visual interface.
[0087] Downloading the retained Fass functions from the distributed storage nodes can include the acquired Fass functions and their corresponding execution results.
[0088] Specifically, S291 may include:
[0089] If the current state of the service supporting the execution of the Fass function is neither updated nor installed, then the retained Fass function will be pushed to the container cluster management system.
[0090] If the current state of the Fass function execution support service is in the update state or in the installation state, and a new Fass function is received from the front end, then the Fass function is stored in the target queue;
[0091] Continuously monitor whether the Fass function's runtime support service has been updated or installed within a preset time period;
[0092] If it is determined at the current detection time that the Fass function's runtime support service has been updated or installed, the new Fass function is retrieved from the target queue, and the new Fass function and the retained Fass function are pushed to the container cluster management system so that the container cluster management system can run the new Fass function and the retained Fass function.
[0093] Among them, the retained Fass functions refer to the Fass functions that were stored before the Fass function's runtime support service was determined to be in an update or installation state.
[0094] The new Fass function is obtained from the front end after determining whether the Fass function's execution support service is in an update or installation state.
[0095] It should be noted that S290 to S293 above can be executed by the Fass function management module. To facilitate understanding of the management logic of the Fass function management module, Figure 5 A logical diagram of yet another serviceless management method is shown.
[0096] like Figure 5 As shown, the method includes the following steps:
[0097] S51. Obtain the Fass function execution command sent by the front end; S52. Download the retained Fass function from the distributed storage node; S53. Determine whether the current status of the Fass function execution support service is in update or installation state. If yes, execute S54; otherwise, execute S58; S54. Store the new Fass function received from the front end into the target queue; S55. Determine whether the Fass function execution support service has been updated or installed within a preset time period. If yes, execute S56; otherwise, continue executing S55; S56. Retrieve the new Fass function from the target queue; S57. Push the new Fass function and the retained Fass function to the container cluster management system; S58. Install the runtime environment that the Fass function depends on; S59. Compile and run the Fass function to obtain the execution result of the Fass function.
[0098] Furthermore, the result of the Fass function can be sent to the front end for display.
[0099] Therefore, the code development module can be used to compile and run FASS functions, and the compilation and running results of FASS functions can be displayed on the visual interface provided on the front end.
[0100] In another embodiment of this disclosure, the execution result of the Fass function is monitored based on the monitoring and management module.
[0101] Optionally, after S293, the method further includes:
[0102] Monitor the execution results of the Fass function; generate monitoring logs based on the execution results of the Fass function, and send the monitoring logs to the front end so that the front end can display the execution results of the Fass function on the visualization interface.
[0103] Therefore, based on the monitoring and management module, the running status of the Fass function at various runtime moments can be monitored, and monitoring logs can be generated and displayed on the visualization interface, making it convenient for administrators to maintain the no-service management process based on the monitoring logs.
[0104] This disclosure also provides a service-free management device for implementing the above-described extraction method, which will be described below in conjunction with... Figure 6 The following explanation is provided. In this embodiment of the disclosure, the serverless management device can be a serverless management platform, that is, a backend server.
[0105] Figure 6 A schematic diagram of the structure of a serviceless management device provided in an embodiment of this disclosure is shown.
[0106] like Figure 6 As shown, the serviceless management device 600 may include:
[0107] Download module 610 is used to download camel-k source code from an intranet remote repository based on the source code download instruction in the pre-created compilation task when a pre-created compilation task is obtained. The compilation task is a task that supports compiling camel-k services for multiple architectures.
[0108] Modification module 620 is used to dynamically match the private storage address in the camel-k source code with multiple harbor addresses, modify the private storage address in the camel-k source code to the matching target harbor address based on multiple first dynamic matching results, and dynamically match the relevant parameters in the camel-k source code with multiple Maven repository parameters, modify the relevant parameters in the camel-k source code to the matching target Maven repository parameters based on multiple second dynamic matching results;
[0109] The first generation module 630 is used to generate a camel-k service based on camel-k source code containing the target harbor address and the target Maven repository parameters, wherein the camel-k service refers to a service image that supports multiple architectures;
[0110] The second generation module 640 is used to generate a no-service management file based on the dynamic modification record of the camel-k service, and send the no-service management file to the front end for display. The no-service management file is used to install or update the recorded camel-k service.
[0111] A serviceless management device according to an embodiment of this disclosure includes: upon obtaining a pre-created compilation task, downloading camel-k source code from an intranet remote repository based on the source code download instruction in the pre-created compilation task, wherein the compilation task is a task that supports compiling camel-k services for multiple architectures; dynamically matching a private storage address in the camel-k source code with multiple harbor addresses, modifying the private storage address in the camel-k source code to a matching target harbor address based on multiple first dynamic matching results, and dynamically matching relevant parameters in the camel-k source code with multiple Maven repository parameters, modifying the relevant parameters in the camel-k source code to matching target Maven repository parameters based on multiple second dynamic matching results; generating a camel-k service based on the camel-k source code containing the target harbor address and target Maven repository parameters, wherein the camel-k service refers to a service image that supports multiple architectures; generating a serviceless management file based on the modification records of the camel-k service, and sending the serviceless management file to the front end for display, wherein the serviceless management file is used to install or update the recorded camel-k service. Therefore, camel-k services can be generated through dynamic matching, i.e., service images supporting multiple architectures can be generated. Based on the dynamic matching results, a serverless management file is generated and displayed on the front end to complete the serverless management process. This simplifies the compilation process and saves labor costs, thereby achieving dynamic, automatic, and visual serverless management.
[0112] In some embodiments of this disclosure, the device further includes:
[0113] The storage module is used to store the camel-k service in the target harbor repository based on the target harbor address, and to store the client service corresponding to the camel-k service in the distributed storage node based on the pre-generated distributed storage node identifier.
[0114] In some embodiments of this disclosure, the device further includes:
[0115] The acquisition module is used to acquire the client service from the distributed storage node and download the camel-k service corresponding to the client service from the target harbor repository when an installation command sent by the front end is detected.
[0116] The judgment module is used to determine whether the execution support service of the Fass function exists, wherein the execution support service of the Fass function includes the camel-k service and the client service;
[0117] The first installation module is used to install the camel-k service into the container cluster management system using the client service when the support service for running the Fass function does not exist, thereby obtaining the current version of the running environment. The current version of the running environment is the usage environment of the camel-k service and the client service.
[0118] In some embodiments of this disclosure, the device further includes:
[0119] The second installation module is used to install the camel-k service into the container cluster management system using the client service when the Fass function's execution support service already exists, the obtained Fass function's execution status is "executed," and the receiving of new Fass function execution requests has stopped, thereby obtaining an updated version of the runtime environment. The obtained Fass function and its corresponding execution result are used to be stored in the distributed storage node.
[0120] In some embodiments of this disclosure, the device further includes:
[0121] The function download module is used to download the retained Fass functions from the distributed storage nodes when a Fass function execution instruction sent by the front end is detected.
[0122] The push module is used to push the retained Fass functions to the container cluster management system based on the current status of the Fass function's runtime support service.
[0123] The third installation module is used to install the runtime environment that the Fass function depends on;
[0124] The execution module is used to compile and run the Fass function to obtain the execution result of the Fass function.
[0125] In some embodiments of this disclosure, the push module is specifically used for:
[0126] If the current status of the Fass function's execution support service is neither an update state nor an installation state, then the retained Fass function will be pushed to the container cluster management system.
[0127] In some embodiments of this disclosure, the push module is specifically used for:
[0128] If the current state of the Fass function's execution support service is in an update state or an installation state, and a new Fass function is received from the front end, then the Fass function is stored in the target queue;
[0129] The system continuously monitors whether the support service for running the Fass function has been updated or installed within a preset time period.
[0130] If it is determined at the current detection time that the support service for running the Fass function has been updated or installed, the new Fass function is retrieved from the target queue, and the new Fass function and the retained Fass function are pushed to the container cluster management system so that the container cluster management system can run the new Fass function and the retained Fass function.
[0131] In some embodiments of this disclosure, the device further includes:
[0132] The monitoring module is used to monitor the execution results of the Fass function;
[0133] The sending module is used to generate monitoring logs based on the execution result of the Fass function and send the monitoring logs to the front end so that the front end can display the execution result of the Fass function on the visualization interface.
[0134] It should be noted that, Figure 6 The serviceless management device 600 shown can perform Figures 2 to 5 The various steps in the method embodiment shown are implemented. Figures 2 to 5 The various processes and effects in the methods or system embodiments shown are not described in detail here.
[0135] Figure 7 A schematic diagram of a serviceless management device according to an embodiment of this disclosure is shown. This serviceless management device can be understood as the serviceless management platform in the foregoing embodiments.
[0136] like Figure 7 As shown, the serviceless management device may include a processor 701 and a memory 702 storing computer program instructions.
[0137] Specifically, the processor 701 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.
[0138] Memory 702 may include a large-capacity storage for information or instructions. For example, and not limitingly, memory 702 may include a hard disk drive (HDD), a floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or a Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 702 may include removable or non-removable (or fixed) media. Where appropriate, memory 702 may be internal or external to the integrated gateway device. In a particular embodiment, memory 702 is a non-volatile solid-state memory. In a particular embodiment, memory 702 includes read-only memory (ROM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (Electrically Programmable ROM, EPROM), an electrically erasable programmable PROM (EEPROM), an electrically alterable ROM (EAROM), or flash memory, or a combination of two or more of these.
[0139] The processor 701 performs the steps of the no-service management method provided in this disclosure by reading and executing computer program instructions stored in the memory 702.
[0140] In one example, the serviceless management device may also include a transceiver 703 and a bus 704. Wherein, as Figure 7 As shown, the processor 701, memory 702 and transceiver 703 are connected via bus 704 and communicate with each other.
[0141] Bus 704 includes hardware, software, or both. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industrial Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a MicroChannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses, or a combination of two or more of these. Where appropriate, bus 704 may include one or more buses. Although specific buses are described and illustrated in the embodiments of this application, this application considers any suitable bus or interconnection.
[0142] The following are embodiments of a computer-readable storage medium provided in this disclosure. This computer-readable storage medium belongs to the same inventive concept as the no-service management method in the above embodiments. For details not described in detail in the embodiments of the computer-readable storage medium, please refer to the embodiments of the no-service management method described above.
[0143] This embodiment provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a serviceless management method.
[0144] Of course, the computer-executable instructions provided in the embodiments of this disclosure are not limited to the above-described method operations, but can also perform related operations in the no-service management method provided in any embodiment of this disclosure.
[0145] Based on the above description of the implementation methods, those skilled in the art can clearly understand that this disclosure can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer cloud platform (which may be a personal computer, a server, or a network cloud platform, etc.) to execute the serverless management methods provided in the various embodiments of this disclosure.
[0146] Note that the above description is merely a preferred embodiment and the technical principles employed in this disclosure. Those skilled in the art will understand that this disclosure is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of this disclosure. Therefore, although this disclosure has been described in detail through the above embodiments, it is not limited to the above embodiments. Many other equivalent embodiments may be included without departing from the concept of this disclosure, and the scope of this disclosure is determined by the scope of the appended claims.
Claims
1. A service-free management method, characterized in that, include: If a pre-created compilation task is obtained, the camel-k source code is downloaded from the intranet remote repository based on the source code download instruction in the pre-created compilation task. The compilation task is a task that supports compiling camel-k services for multiple architectures. The private storage address in the camel-k source code is dynamically matched with multiple harbor addresses. Based on multiple first dynamic matching results, the private storage address in the camel-k source code is modified to the matching target harbor address. The relevant parameters in the camel-k source code are dynamically matched with multiple Maven repository parameters. Based on multiple second dynamic matching results, the relevant parameters in the camel-k source code are modified to the matching target Maven repository parameters. Based on the camel-k source code containing the target harbor address and the target Maven repository parameters, a camel-k service is generated, wherein the camel-k service refers to a service image that supports multiple architectures; Based on the modification records corresponding to the camel-k service, a no-service management file is generated and sent to the front end for display. The no-service management file is used to install or update the recorded camel-k service.
2. The method according to claim 1, characterized in that, Also includes: The camel-k service is stored in the target harbor repository based on the target harbor address, and the client service corresponding to the camel-k service is stored in the distributed storage node based on the pre-generated distributed storage node identifier.
3. The method according to claim 2, characterized in that, Also includes: Upon detecting an installation command sent from the front end, the client service is retrieved from the distributed storage node, and the camel-k service corresponding to the client service is downloaded from the target harbor repository; Determine whether the Fass function's runtime support service exists, wherein the Fass function's runtime support service includes the camel-k service and the client service; If the support service for running the Fass function does not exist, the client service is used to install the camel-k service into the container cluster management system to obtain the current version of the runtime environment, wherein the current version of the runtime environment is the environment in which the camel-k service is installed.
4. The method according to claim 3, characterized in that, Also includes: If the Fass function's execution support service already exists, the obtained Fass function's execution status is "completed," and new Fass function execution requests are no longer being received, then the camel-k service is installed into the container cluster management system using the client service to obtain an updated version of the runtime environment. The obtained Fass function and its corresponding execution result are stored in the distributed storage node.
5. The method according to claim 4, characterized in that, Also includes: Upon detecting a Fass function execution command sent from the front end, the retained Fass function is downloaded from the distributed storage node; Based on the current state of the Fass function's runtime support service, the retained Fass functions are pushed to the container cluster management system; Install the runtime environment that the Fass function depends on; Compile and run the Fass function to obtain the result of its execution.
6. The method according to claim 5, characterized in that, Based on the current state of the runtime support service for the Fass function, pushing the retained Fass function to the container cluster management system includes: If the current status of the Fass function's execution support service is neither an update state nor an installation state, then the retained Fass function will be pushed to the container cluster management system.
7. The method according to claim 5, characterized in that, Based on the current state of the runtime support service for the Fass function, pushing the retained Fass function to the container cluster management system includes: If the current state of the Fass function's execution support service is in an update state or an installation state, and a new Fass function is received from the front end, then the Fass function is stored in the target queue; The system continuously monitors whether the support service for running the Fass function has been updated or installed within a preset time period. If it is determined at the current detection time that the support service for running the Fass function has been updated or installed, the new Fass function is retrieved from the target queue, and the new Fass function and the retained Fass function are pushed to the container cluster management system so that the container cluster management system can run the new Fass function and the retained Fass function.
8. The method according to claim 5, characterized in that, Also includes: Monitor the execution result of the Fass function; Based on the execution result of the Fass function, a monitoring log is generated and sent to the front end so that the front end can display the execution result of the Fass function on a visual interface.
9. A service-free management device, characterized in that, include: The download module is used to download the camel-k source code from a remote intranet repository based on the source code download instructions in the pre-created compilation task when a pre-created compilation task is obtained. The compilation task is a task that supports compiling camel-k services for multiple architectures. The modification module is used to dynamically match the private storage address in the camel-k source code with multiple harbor addresses, modify the private storage address in the camel-k source code to the matching target harbor address based on multiple first dynamic matching results, and dynamically match the relevant parameters in the camel-k source code with multiple Maven repository parameters, modify the relevant parameters in the camel-k source code to the matching target Maven repository parameters based on multiple second dynamic matching results. The first generation module is used to generate a camel-k service based on the camel-k source code containing the target harbor address and the target Maven repository parameters, wherein the camel-k service refers to a service image that supports multiple architectures; The second generation module is used to generate a no-service management file based on the dynamic modification records of the camel-k service, and send the no-service management file to the front end for display. The no-service management file is used to install or update the recorded camel-k service.
10. A service-free management device, characterized in that, include: processor; Memory, used to store executable instructions; The processor is configured to read the executable instructions from the memory and execute the executable instructions to implement the method of any one of claims 1-8.
11. A computer-readable storage medium having a computer program stored thereon, characterized in that, The storage medium stores a computer program that, when executed by a processor, causes the processor to implement the method described in any one of claims 1-8.