Application configuration method based on container cloud, electronic equipment and readable storage medium

Abstract

The invention discloses an application configuration method based on container cloud, electronic equipment and a readable storage medium, and the method comprises the steps: responding to a received application fingerprint request instruction sent by an equipment end, determining target application fingerprint information according to a target application program in the application fingerprint request instruction, and sending the target application fingerprint information to the equipment end, the device end determines a current authorization file of the target application program based on the target application fingerprint information; and in response to the received current authorization file of the target application sent by the device end, performing configuration processing on the target application according to the current authorization file to obtain the configured target application. Therefore, the method can be suitable for application configuration in a containerized deployment scene.

Description

Technical Field

[0001] This invention relates to the field of container cloud technology, and in particular to an application configuration method, electronic device, and computer-readable storage medium based on container cloud. Background Technology

[0002] Current software licensing information is mostly based on hardware fingerprints, which construct a unique identifier for a device using a unique hardware identifier and a set of device characteristics. This method ensures the device uniqueness of software licensing, meaning only authorized devices can use the software.

[0003] However, with the development of containerization technology, software deployed through containerization may be deployed on different servers. Hardware fingerprints cannot accurately identify the software's running status in the containerized environment, resulting in invalid or inaccurate authorization control, which cannot meet the needs of containerized deployment scenarios. Summary of the Invention

[0004] The main technical problem addressed in this application is to provide an application configuration method, electronic device, and computer-readable storage medium based on container cloud, which can adapt to the needs of containerized deployment scenarios.

[0005] To address the aforementioned technical problems, this application provides a technical solution: an application configuration method based on container cloud, the method comprising: responding to receiving an application fingerprint request instruction sent by the device, determining target application fingerprint information according to the target application in the application fingerprint request instruction, and sending the target application fingerprint information to the device, so that the device determines the current license file of the target application based on the target application fingerprint information; responding to receiving the current license file of the target application sent by the device, performing configuration processing on the target application according to the current license file to obtain the configured target application.

[0006] To solve the above-mentioned technical problems, another technical solution adopted in this application is: to provide an electronic device, including a memory and a processor, wherein the memory stores program instructions, and the processor retrieves the program instructions from the memory to execute the above-mentioned application configuration method based on container cloud.

[0007] To address the aforementioned technical problems, another technical solution adopted in this application is to provide a computer-readable storage medium that stores program data, which, when executed by a processor, is used to implement the aforementioned application configuration method based on container cloud.

[0008] The application configuration method based on container cloud in this application responds to receiving an application fingerprint request instruction sent by the device, determines the target application fingerprint information according to the target application in the application fingerprint request instruction, and sends the target application fingerprint information to the device so that the device can determine the current license file of the target application based on the target application fingerprint information; responding to receiving the current license file of the target application sent by the device, the method performs configuration processing on the target application according to the current license file to obtain the configured target application. Therefore, by determining the current license file through the target application fingerprint information of the target application in the container cloud, the license information of the target application in the containerized environment can be accurately identified, making it suitable for application configuration in containerized deployment scenarios. Attached Figure Description

[0009] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly described below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort, wherein: Figure 1 This is a flowchart illustrating an exemplary embodiment of the application configuration method shown in this application; Figure 2 yes Figure 1 A flowchart illustrating an exemplary embodiment of the application configuration method prior to step S110 is shown. Figure 3 yes Figure 1 A flowchart illustrating an exemplary embodiment of the application configuration method prior to step S120 is shown. Figure 4 This is a schematic flowchart of an exemplary embodiment of the license document detection shown in this application; Figure 5 This is a flowchart illustrating another exemplary embodiment of the license document detection shown in this application; Figure 6 yes Figure 1 A flowchart illustrating an exemplary embodiment of step S120 in the application configuration method is shown. Figure 7 This is a schematic flowchart of an exemplary embodiment of the computing node control process shown in this application; Figure 8 This is a detailed flowchart illustrating an exemplary embodiment of the application configuration method shown in this application; Figure 9 This is a schematic diagram of an exemplary embodiment of the application configuration device shown in this application; Figure 10This is a schematic diagram of the structure of an embodiment of the electronic device provided in this application; Figure 11 This is a schematic diagram of an embodiment of the computer-readable storage medium provided in this application. Detailed Implementation

[0010] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It is understood that the specific embodiments described herein are only for explaining this application and not for limiting it. Furthermore, it should be noted that, for ease of description, only the parts related to this application are shown in the accompanying drawings, not all structures. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0011] First, it's important to clarify that an authorization document, also known as a license, is a legal contract between the application developer and the user. It clearly defines the scope of application use and the authorization method. The scope of use includes, but is not limited to, the number of users, the number of devices installed, and geographical restrictions. Authorization methods include, but are not limited to, perpetual licenses and subscription models. Current authorization documents typically incorporate hardware bindings, such as MAC addresses and device serial numbers, to ensure that only authorized users can use the application within the authorized scope. However, in containerized deployment scenarios, applications are often flexibly deployed on different servers. Hardware fingerprints cannot accurately identify the application's running status in a containerized deployment environment, leading to ineffective or inaccurate authorization documents that fail to meet the needs of containerized deployment scenarios.

[0012] Based on this, embodiments of this application propose an application configuration method, electronic device, and computer-readable storage medium based on container cloud. The application configuration method based on container cloud, hereinafter referred to as the application configuration method, ensures the validity of the current authorization file by using the target application fingerprint information of the target application in the container cloud. For details, please refer to... Figure 1 , Figure 1 This is a flowchart illustrating an exemplary embodiment of the application configuration method shown in this application.

[0013] The execution entity of the application configuration method can be a terminal device, a server, or other processing device. The terminal device can be a user equipment (UE), computer, mobile device, user terminal, terminal, cellular phone, cordless phone, personal digital assistant (PDA), handheld device, computing device, in-vehicle device, wearable device, etc. The execution entity of the application configuration method can also be an application configuration device. For example, the application configuration device can be a container cloud, which communicates with the device. In some possible implementations, the application configuration method can be implemented by the processor calling computer-readable instructions stored in memory.

[0014] Specifically, the application configuration method in this embodiment includes the following steps: S110: In response to receiving an application fingerprint request instruction sent by the device, determine the target application fingerprint information according to the target application in the application fingerprint request instruction, and send the target application fingerprint information to the device so that the device can determine the current license file of the target application based on the target application fingerprint information.

[0015] Container cloud refers to a cloud computing service platform built on container technologies (such as Docker) and container orchestration platforms (such as Kubernetes). It provides an environment for deploying, managing, and scaling container-based applications, offering development teams more efficient and flexible deployment and operation solutions. The container cloud platform is the management platform for the target application in this embodiment.

[0016] The device side refers to the terminal operated by the user. In this embodiment, when the device side uses the target application, if it finds that the target application has not yet been configured, it needs to send an application fingerprint request command to the container cloud to request the target application fingerprint information related to the target application. In order to generate the current authorization file of the target application through the target application fingerprint information, the device side can configure the target application so that the user can use the target application normally.

[0017] The application fingerprint request instruction is used to instruct the application configuration device to send the target application fingerprint information requested by the device to the device. For example, the application fingerprint request instruction can be determined based on information such as that of the target application. For instance, the application fingerprint request instruction may include a program identifier of the target application, which is used to identify a unique application.

[0018] A target application can refer to a computer software program used to complete a specific task or function. In some application scenarios, applications require authorization to function properly, and the usage permissions of applications differ under different authorization types. A target application can be any one of a set of applications. In this embodiment, the target application is deployed on a container cloud platform. Application containerization refers to packaging an application and all its dependencies, configurations, and runtime environments into an independent container so that it can be easily deployed and run in different computing environments. It can be seen that the target application in a containerized deployment environment does not specify hardware; if the current authorization file of the target application is built using a hardware fingerprint, authorization control will fail. The target application can also be a data platform system, which refers to a system that uses big data technology to uniformly collect, compute, and store massive amounts of data and provides data services to external parties.

[0019] The target application fingerprint is a unique identifier for the target application, allowing the user to locate the unique target application. The target application fingerprint is stored in an encrypted file. For example, the target application fingerprint includes, but is not limited to, the target application's runtime status information on the container cloud, such as application authorization details, authorization type, authorization expiration time, service ID, etc.

[0020] The current license file is used to clearly define the usage permissions and responsibilities of the target application. For example, the application configuration device can generate the current license file for the target application using the target application's fingerprint information through an authorization website. The application configuration device can also obtain the current license file for the target application from the internal storage of the container cloud platform. For instance, during the build process, the target application initializes a temporary license file within the image of any service of the target application. When the container is launched, the container cloud moves this temporary license file as the current license file to the host machine's file system and maps it to a fixed path inside the container for application configuration processing, resulting in the configured target application.

[0021] S120: In response to receiving the current license file of the target application sent by the device, perform configuration processing on the target application according to the current license file to obtain the configured target application.

[0022] After determining the current license file of the target application based on the target application fingerprint information, the device sends the current license file of the target application to the container cloud platform. The container cloud platform receives the current license file sent by the device and configures the target application according to the current license file to obtain the configured target application. The configured target application can then provide services to users according to the corresponding usage permissions.

[0023] As can be seen, the application configuration method based on container cloud in this embodiment responds to receiving an application fingerprint request instruction sent by the device, determines the target application fingerprint information according to the target application in the application fingerprint request instruction, and sends the target application fingerprint information to the device so that the device can determine the current license file of the target application based on the target application fingerprint information; responding to receiving the current license file of the target application sent by the device, the method performs configuration processing on the target application according to the current license file to obtain the configured target application. Therefore, by determining the current license file through the target application fingerprint information of the target application in the container cloud, the license information of the target application in the containerized environment can be accurately identified, making it suitable for application configuration in containerized deployment scenarios.

[0024] Based on the above embodiments, the embodiments of this application adopt... Figure 2 The flowchart details how to obtain the target application fingerprint information of the target application. Please refer to [link / reference]. Figure 2 , Figure 2 yes Figure 1 The illustrated flowchart shows an exemplary embodiment of the application configuration method prior to step S110. Specifically, prior to step S110, the method further includes the following steps: S210: Obtain the current authorization information of the target application.

[0025] The current authorization information includes the usage permissions of the target application. This information includes, but is not limited to, the expiration date of the target application's license, the license type, and the module authorization information for each functional module. For example, the current authorization information of the target application can be determined based on the user's purchase or application information. For instance, if a user purchases a temporary license, the current authorization information of the target application is determined based on the temporary license's permissions; if a user purchases a permanent license, the current authorization information of the target application is determined based on the permanent license's permissions.

[0026] After determining the user's purchase or application information, the application configuration device determines the target application's current authorization information in the container cloud based on the user's purchase or application information.

[0027] S220: Generate the target application fingerprint information of the target application based on the current authorization information of the target application.

[0028] After obtaining the current authorization information of the target application in the container cloud, the application configuration device generates corresponding target application fingerprint information from the current authorization information. For example, the application configuration device stores and processes the current authorization information according to a certain data structure to obtain the target application fingerprint information.

[0029] In some embodiments, the current authorization information includes module authorization information for at least one functional module. The application configuration device determines the module fingerprint information of each functional module based on the module authorization information of each functional module in the target application; and determines the target application fingerprint information of the target application based on the module fingerprint information of each functional module. This enables precise control over each functional module and also facilitates users to purchase the required functional modules as needed.

[0030] A functional module is a module within a target application that performs a specific function. A target application includes one or more functional modules. In some application scenarios, certain functional modules of the target application may require separate authorization. The module authorization information for a functional module includes its usage permissions. For example, whether the functional module can be used and the scope of its use.

[0031] After the application configuration device obtains the module authorization information of each functional module in the target application, it generates module fingerprint information of each functional module from the module authorization information, and then combines the module fingerprint information of each functional module to obtain the target application fingerprint information of the target application.

[0032] As an example, the plaintext data structure of the target application fingerprint information may include the version of the target application fingerprint information; relevant time, such as the current time and the authorization expiration time, which can be the most recent expiration time among the authorization items; the authorization type of the target application, such as commercial, trial, or temporary; a list of authorization items, including the module authorization information of each functional module; the functional module name and functional module material identifier; the authorization information value and key value; the expiration time of the functional module and the authorization type of the functional module, such as commercial, trial, or temporary.

[0033] In other embodiments, after obtaining the current authorization information of the target application, the application configuration device performs unified authorization on the target application based on the current authorization information to obtain the target application fingerprint information. This enables rapid generation of fingerprint information.

[0034] Based on the above embodiments, the embodiments of this application adopt... Figure 3 The flowchart details how to determine whether the current authorization file has been received from the device. Please refer to [link / reference]. Figure 3 , Figure 3 yes Figure 1 The illustrated flowchart shows an exemplary embodiment of the application configuration method prior to step S120. Specifically, prior to step S120, the method further includes the following steps: S310: In response to detecting a change in the license directory of the target application, obtain the difference between the historical license files and the current license files of the target application. The license directory is used to store the license files of the target application.

[0035] The target application's license files are stored in the license directory. When a user imports a new license file, the license directory is updated with the latest imported license file. Therefore, the application configuration device needs to be aware of changes to the license directory and record the details of each license file import. As an example, the license directory can be stored within the target application's central management service container. The central management service is aware of changes to the license files and updates them when a user imports a new license file.

[0036] For example, the application configuration device can use a tool to detect whether the licensed directory of the target application has changed. The tool can be the WatchService utility included in the JDK. Introduced in JDK 7, WatchService is a native file system detector for the operating system. Wrapped in Java, it can directly detect changes to all files on the operating system within a Java program. It's a signal-based detection method, requiring no traversal or comparison, making it highly efficient. The WatchService utility is initialized, and in the background, it uses the JDK's FileSystem utility to obtain signals indicating file changes. The WatchService utility is then registered with a specified file node. During registration, the type of file change to be detected can be specified, such as creation, deletion, or modification. The file node being detected is the licensed directory, and the scope of the detection includes changes to licensed files and subdirectories within that directory.

[0037] When a change to the authorized directory is detected, the WatchService tool sends a change event to the event list. The business logic then retrieves the event information from the event list to monitor changes to the authorized files. For details, please refer to [link to relevant documentation]. Figure 4 The flowchart shows that the application configuration device traverses the event list and obtains each event; it determines whether the changed item in the event is an authorization file. If so, it parses the authorization file, saves the import record and authorization content to the database (which can be MySQL); otherwise, the process ends.

[0038] A change in the license directory may be due to the import of a new license file. In this case, the application configuration device can further compare the imported current license file with the target application's historical license file to determine whether there are any changes to the current license file relative to the historical license file. If there are changes, it means that application configuration needs to be performed based on the new current license file. If there are no changes, it means that there may be problems such as duplicate import. In this case, there is no need to perform application configuration again, thus reducing resource waste.

[0039] In some embodiments, the difference between the current license file and the historical license file can be calculated using hash values. The application configuration device obtains the hash values ​​of the historical license files and the current license file; and calculates the difference between the historical license files and the current license file based on the hash values ​​of the historical license files and the current license file.

[0040] In this context, the historical license file can be the previous license file of the target application, which can be considered as the license file used before the current license file is imported. For example, when a user wants to elevate the license permissions of the target application, the historical license file is the license file before the permission was elevated, while the current license file is the license file after the permission was elevated; there is a distinction between the two.

[0041] The result of compressing an authorization file into a fixed-length data set using a hash algorithm is called a hash value. Examples of hash algorithms include MD5 (Message-Digest Algorithm 5) and SHA (Secure Hash Algorithm). Since the hash value changes significantly with changes to the authorization file, it's crucial to accurately determine the differences between historical and current authorization files using the hash value.

[0042] In other embodiments, the application configuration device may also determine the difference between the current license file and historical license files based on the metadata of the license files. In still other embodiments, the application configuration device may also compare historical license files and the current license file byte by byte to determine the difference between the current license file and the historical license files.

[0043] S320: Determine whether to receive the current license file of the target application sent by the device based on the relationship between the difference value and the preset difference value.

[0044] After obtaining the difference between the historical license file and the current license file, if the difference is greater than a preset difference value, it is determined that the current license file of the target application sent by the device has been received; if the difference is less than or equal to the preset difference value, it is determined that the current license file of the target application sent by the device has not been received. It should be noted that "not receiving the current license file" here means not using the current license file for application configuration.

[0045] In other embodiments, the application configuration device can detect whether the license directory of the target application has changed using a detection tool. If it has changed, it confirms that it has received the current license file of the target application sent by the device. If it has not changed, it confirms that it has not received the current license file of the target application sent by the device.

[0046] In other embodiments, see [reference needed]. Figure 5 To address the issue of the detection tool failing to detect changes to the licensed directory upon process exit, the application configuration unit calculates the MD5 value of the current licensed file when the service process starts. It then checks if this MD5 value exists in the database for historical licensed files. If it does, the detection tool is registered to detect file change events in the licensed directory. If not, the current licensed file is parsed, import records and the current licensed file are saved to the database, and the detection tool is registered to detect file change events in the licensed directory. The licensed directory can be / etc / license.

[0047] Based on the above embodiments, the embodiments of this application adopt... Figure 6 The flowchart details how to configure the target application using the current license file; please refer to [link / reference]. Figure 6 , Figure 6 yes Figure 1 The illustrated flowchart shows an exemplary embodiment of step S120 in the application configuration method. Specifically, step S120, which involves configuring the target application based on the current license file to obtain the configured target application, includes the following steps: S610: Parse and process the current license file to obtain the module license policy for each functional module in the target application.

[0048] Module authorization strategy refers to the configuration strategy for functional modules. For example, the application configuration device obtains the authorization permissions of each functional module in the current authorization file and determines the corresponding module authorization strategy based on the authorization permissions of each functional module. It is understood that the module authorization strategies for each functional module in the target application differ under different authorization permissions. As an example, Table 1 shows:

[0049] Table 1 S620: Configure the corresponding functional modules according to the module authorization policy of each functional module to obtain the configured target application.

[0050] After obtaining the module authorization policies for each functional module, the application configuration device performs application configuration according to the module authorization policies of each functional module to obtain the configured target application. For example, as shown in Table 1 above, the platform basic module is not allowed to log in to the platform without authorization. A judgment can be added to the login interface. If the platform basic module is not authorized, the login will fail and the user will be prompted. The prompt message can be that the license authorization of the platform basic module has expired. The lineage analysis module and the resource diagnosis module are not allowed to enter the module without authorization. The judgment can be enhanced in the function entry interface. If the lineage analysis module or the resource diagnosis module is not authorized, the functional module will not be displayed. The multi-tenant management module cannot create new project spaces without authorization. Therefore, a judgment can be added to the project space creation interface. If the multi-tenant management module is not authorized, the creation of new project spaces will not be allowed. Other modules in Table 1 are grayed out and cannot be operated without authorization. Therefore, a mark is added to the user menu list interface to indicate whether the menu is grayed out. The front end grays out the modules without authorization based on the mark.

[0051] It should be noted that Table 1 is only an example, and the specific module authorization strategy needs to be determined according to the actual application scenario. This embodiment does not limit it.

[0052] In other embodiments, the application configuration device may further parse the current license file to obtain the number of licensed nodes of the target application; and physically deploy the target application according to the number of licensed nodes of the target application to obtain the configured target application.

[0053] The number of authorized nodes refers to the maximum number of physical nodes that can be deployed on the target application. Once the application configuration device obtains the number of authorized nodes for the target application, it determines the physical nodes for the target application according to that number and deploys the target application to those physical nodes, resulting in the configured target application. For example, when the number of authorized nodes is 3, the target application can be deployed on 3 servers simultaneously, but not more than 3 servers. In other words, the number of physical nodes required for the target application deployment environment corresponds to the number of node licenses that need to be purchased. This node can be referred to as the computing task scheduling engine.

[0054] After deploying the target application based on the number of authorized nodes, when a user creates a new data task, it is necessary to determine whether creation is possible based on the number of authorized nodes and the actual number of computing nodes for the target application. Specifically, in response to receiving a data processing task creation instruction, the application configuration device determines whether the number of authorized nodes in the current authorization file is less than the actual number of computing nodes for the target application; if not, it creates the data processing task according to the creation instruction.

[0055] In this context, the number of authorized nodes refers to the number of data processing tasks that the target application can submit to the Yarn queue of the Hadoop big data platform for execution. These data processing tasks include data development tasks and data access tasks. This links the number of authorized nodes to Yarn computing resources, precisely controlling the amount of resources available for each task.

[0056] The actual number of compute nodes for the target application refers to the number of physical nodes deployed with the target application. When the authorized number of nodes is less than the actual number of compute nodes, users are not allowed to create new data processing tasks. For example, see [link to relevant documentation]. Figure 7 The user issues a command to create a data access task via the web interface. The data access service then calls the task creation interface. The management center service calls an RPC interface to verify the number of authorized nodes in the management center service and queries the actual number of compute nodes for the target application in the container cloud. The container cloud returns the actual number of compute nodes to the management center service, which then determines whether the number of authorized nodes is less than the actual number of nodes and returns the result to the data access service. If the result indicates that the number of authorized nodes is less than the actual number of nodes, the creation of the data access task is not allowed, and a failure message is returned to the web interface informing the user of the creation failure. This completes the authorization control of the number of compute tasks, enabling more granular permission division and meeting diverse user needs.

[0057] In other embodiments, the application configuration device may further parse the current authorization file to obtain the number of authorized nodes of the target application and the module authorization policy of each functional module; physically deploy the target application according to the number of authorized nodes of the target application, and configure the corresponding functional modules according to the module authorization policy of each functional module to obtain the configured target application.

[0058] To elaborate on the application configuration method of this application, Figure 8 The flowchart shown below provides further explanation, as detailed below: First, it should be noted that the target application in this application embodiment can be deployed in a private cloud environment. In a private cloud environment, the server is deployed in the user's local area network and lacks a public account system. The traditional public cloud access control method cannot be adapted to the private cloud environment and it is difficult to achieve effective access control.

[0059] Based on this, this application proposes an application configuration method for containerized deployment in a private cloud scenario, which can effectively control the authorization permissions of the target application through the current authorization file. The installation process of the target application's product package may include parsing the installation file, converting the installation file into a business object, and saving the business object to a database.

[0060] Step 1: The device (user) issues an application fingerprint request command on the interactive page. The container cloud matches the target application fingerprint information from the container cloud according to the target application in the application fingerprint request command and sends the target application fingerprint information to the device. The target application fingerprint information includes a list of authorized items, functional module names, and functional module material identifiers, etc., thereby realizing access control in the private cloud scenario through a specific design format. Step 2: After obtaining the target application fingerprint information, the device sends the target application fingerprint information to the authorization website through the authorization gateway to create the authorization file; Step 3: After obtaining the target application's fingerprint information, the authorized website processes the fingerprint information using a corresponding creation tool. This creation tool is provided by the target application and can be a JAR file or a shell script. Step 4: The tool generates the current license file corresponding to the fingerprint information of the target application. The parameters passed in the current license file include the fingerprint information of the target application and the license items purchased by the user. Step 5: After the device is created, download the current license file of the target application from the authorized website; Step 6: The device imports the downloaded current license file into the container cloud via an interactive page; Step 7: After the container cloud detects the import action of the current license file, the controller verifies the current license file to determine whether the current license file is complete and whether the current license file has changed compared to the historical license file. If it is complete and has changed, the controller parses the current license file to obtain the license policy of the target application. Step 8: At the computing platform business level, the target application is configured according to the parsed authorization policy to obtain the configured application. The authorization policy includes module authorization policies for different functional modules and the deployment of computing nodes. By combining the authorization of functional modules and resource usage, the fineness of authorization control and the efficiency of system resource utilization are improved.

[0061] Step 9: When a user operates the configured application, control is performed using the corresponding authorization policy.

[0062] Please see Figure 9 , Figure 9This is a schematic diagram of an exemplary embodiment of the application configuration apparatus shown in this application. The application configuration apparatus 900 includes a matching module 910 and a configuration module 920. The matching module 910 is used to, in response to receiving an application fingerprint request instruction sent by the device, determine the target application fingerprint information according to the target application in the application fingerprint request instruction, and send the target application fingerprint information to the device, so that the device determines the current license file of the target application based on the target application fingerprint information. The configuration module 920 is used to, in response to receiving the current license file of the target application sent by the device, perform configuration processing on the target application according to the current license file to obtain the configured target application.

[0063] In the above scheme, the application configuration device, upon receiving an application fingerprint request instruction from the device, determines the target application fingerprint information based on the target application in the instruction and sends the target application fingerprint information to the device, enabling the device to determine the current license file of the target application based on the fingerprint information. Upon receiving the current license file of the target application from the device, the device performs configuration processing on the target application based on the current license file to obtain the configured target application. Therefore, by determining the current license file using the target application fingerprint information in the container cloud, the license information of the target application in the containerized environment can be accurately identified, making it suitable for application configuration in containerized deployment scenarios.

[0064] The functions of each module can be found in the application configuration method implementation example, and will not be repeated here.

[0065] To implement the application configuration method of the above embodiments, this application proposes another electronic device, please refer to [link / reference needed]. Figure 10 , Figure 10 This is a schematic diagram of the structure of an embodiment of the electronic device provided in this application.

[0066] Electronic device 1000 includes memory 1010 and processor 1020, wherein memory 1010 and processor 1020 are coupled together.

[0067] The memory 1010 is used to store program data, and the processor 1020 is used to execute the program data to implement the application configuration method of the above embodiment.

[0068] In this embodiment, processor 1020 can also be referred to as CPU (Central Processing Unit). Processor 1020 may be an integrated circuit chip with signal processing capabilities. Processor 1020 may also be a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. The general-purpose processor may be a microprocessor, or processor 1020 may be any conventional processor.

[0069] This application also provides a computer-readable storage medium, such as Figure 11 As shown, the computer-readable storage medium 1100 is used to store program data 1110, which, when executed by a processor, is used to implement the application configuration method as described in the method embodiments of this application.

[0070] The methods involved in the application configuration method embodiments of this application, when implemented as software functional units and sold or used as independent products, can be stored in a device, such as a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0071] The above description is merely an embodiment of this application and does not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A method for configuring applications based on container cloud, characterized in that, The container cloud-based application configuration method is applied to a container cloud, wherein the container cloud communicates with the device. The method includes: In response to receiving an application fingerprint request instruction sent by the device, the device determines the target application fingerprint information according to the target application in the application fingerprint request instruction, and sends the target application fingerprint information to the device so that the device can determine the current license file of the target application based on the target application fingerprint information; In response to receiving the current license file of the target application sent by the device, the target application is configured according to the current license file to obtain the configured target application.

2. The application configuration method based on container cloud according to claim 1, characterized in that, Prior to the step of determining the target application fingerprint information based on the target application in the application fingerprint request instruction, the method further includes: Obtain the current authorization information of the target application; The target application fingerprint information of the target application is generated based on the current authorization information of the target application.

3. The application configuration method based on container cloud according to claim 2, characterized in that, The current authorization information includes module authorization information for at least one functional module. The step of generating the target application fingerprint information of the target application based on the current authorization information of the target application includes: The module fingerprint information of each functional module is determined based on the module authorization information of each functional module in the target application; The target application fingerprint information of the target application is determined based on the module fingerprint information of each functional module.

4. The application configuration method based on container cloud according to claim 1, characterized in that, Before the step of responding to receiving the current license file of the target application sent by the device, and performing configuration processing of the target application according to the current license file to obtain the configured target application, the method further includes: In response to detecting a change in the license directory of the target application, the difference between the historical license files and the current license files of the target application is obtained, wherein the license directory is used to store the license files of the target application; Whether the current authorization file of the target application sent by the device is received is determined based on the relationship between the difference value and the preset difference value.

5. The application configuration method based on container cloud according to claim 4, characterized in that, The step of obtaining the difference between the historical license file and the current license file of the target application includes: Obtain the hash value of the historical licensed file and the hash value of the current licensed file; The difference between the historical license file and the current license file is calculated based on the hash value of the historical license file and the hash value of the current license file.

6. The application configuration method based on container cloud according to claim 1, characterized in that, The step of configuring the target application according to the current authorization file to obtain the configured target application includes: The current authorization file is parsed to obtain the module authorization policy for each functional module in the target application; The corresponding functional modules are configured according to the module authorization policy of each functional module to obtain the configured target application.

7. The application configuration method based on container cloud according to claim 1, characterized in that, The step of configuring the target application according to the current authorization file to obtain the configured target application includes: The current authorization file is parsed to obtain the number of authorized nodes for the target application; The target application is physically deployed based on the number of authorized nodes to obtain the configured target application.

8. The application configuration method based on container cloud according to claim 7, characterized in that, After the step of physically deploying the target application according to the number of authorized nodes of the target application to obtain the configured target application, the method further includes: In response to receiving a data processing task creation instruction, it is determined whether the number of authorized nodes in the current authorization file is less than the actual number of computing nodes of the target application; If not, then create the data processing task according to the creation instructions.

9. An electronic device, characterized in that, include: A memory and a processor, wherein the memory stores program instructions, and the processor retrieves the program instructions from the memory to perform the method as claimed in any one of claims 1-8.

10. A computer-readable storage medium, characterized in that, include: The system stores program data, which, when executed by a processor, is used to implement the method as described in any one of claims 1-8.

Images