Application issuing method and device, computer device and storage medium

Abstract

The application relates to an application issuing method and device, computer equipment and a storage medium. The method comprises the following steps: when an application issuing request is received, reading stored application configuration information corresponding to an application product, the application issuing request carrying a to-be-issued application identifier and a to-be-issued node identifier, the stored application configuration information being application configuration information stored when the application product is accessed; performing application issuing auditing according to the to-be-issued application identifier and the to-be-issued node identifier; when the application issuing auditing is passed, obtaining target application configuration information from the stored application configuration information according to the to-be-issued application identifier; and issuing the target application configuration information to a target issuing node corresponding to the to-be-issued node identifier. The method can realize flexible application deployment and improve application deployment efficiency.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computers, in particular to an application issuing method and device, computer equipment and storage medium. BACKGROUND

[0002] With the development of computer technology, cloud technology has emerged. Cloud technology refers to a hosting technology that unifies a series of resources such as hardware, software and network in a wide area network or local area network to realize data calculation, storage, processing and sharing.

[0003] In the prior art, a cloud application market based on cloud technology can provide cloud application products. The cloud application market corresponds to a cloud node. When providing cloud application products, the cloud application products need to be first accessed to the cloud application market by a service provider, and then imported and put on the market in the cloud application market.

[0004] However, in the prior art, since there are multiple different cloud application markets, when providing cloud application products, the service provider needs to separately connect and put on the multiple different cloud application markets, which causes the problem of complicated application deployment operation and low deployment efficiency. SUMMARY

[0005] Therefore, it is necessary to provide an application issuing method and device, computer equipment and storage medium capable of realizing flexible application deployment and improving application deployment efficiency in view of the above technical problems.

[0006] An application issuing method, the method comprising:

[0007] When an application issuing request is received, read the stored application configuration information corresponding to the application product, the application issuing request carrying a to-be-issued application identifier and a to-be-issued node identifier, the stored application configuration information being the application configuration information stored when the application product is accessed;

[0008] According to the to-be-issued application identifier and the to-be-issued node identifier, perform application issuing auditing;

[0009] When the application issuing auditing is passed, according to the to-be-issued application identifier, obtain target application configuration information from the stored application configuration information;

[0010] Issue the target application configuration information to a target issuing node corresponding to the to-be-issued node identifier.

[0011] An application issuing device, the device comprising:

[0012] A first processing module configured to, when an application issuing request is received, read the stored application configuration information corresponding to the application product, the application issuing request carrying a to-be-issued application identifier and a to-be-issued node identifier, the stored application configuration information being the application configuration information stored when the application product is accessed;

[0013] The auditing module is configured to perform application delivery auditing according to the application identifier to be delivered and the node identifier to be delivered.

[0014] The second processing module is configured to acquire target application configuration information from the stored application configuration information according to the application identifier to be delivered when the application delivery auditing is passed.

[0015] The synchronizing module is configured to deliver the target application configuration information to a target delivery node corresponding to the node identifier to be delivered.

[0016] A computer device comprises a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0017] When receiving an application delivery request, read the stored application configuration information corresponding to an application product, the application delivery request carries an application identifier to be delivered and a node identifier to be delivered, and the stored application configuration information is the application configuration information stored when the application product is accessed;

[0018] Perform application delivery auditing according to the application identifier to be delivered and the node identifier to be delivered;

[0019] When the application delivery auditing is passed, acquire target application configuration information from the stored application configuration information according to the application identifier to be delivered;

[0020] Deliver the target application configuration information to a target delivery node corresponding to the node identifier to be delivered.

[0021] A computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement the following steps:

[0022] When receiving an application delivery request, read the stored application configuration information corresponding to an application product, the application delivery request carries an application identifier to be delivered and a node identifier to be delivered, and the stored application configuration information is the application configuration information stored when the application product is accessed;

[0023] Perform application delivery auditing according to the application identifier to be delivered and the node identifier to be delivered;

[0024] When the application delivery auditing is passed, acquire target application configuration information from the stored application configuration information according to the application identifier to be delivered;

[0025] Deliver the target application configuration information to a target delivery node corresponding to the node identifier to be delivered.

[0026] The application distribution method, device, computer device and storage medium described above only need to complete the docking of the application product once to obtain the stored application configuration information corresponding to the application product, and can read the stored application configuration information when receiving the application distribution request, obtain target application configuration information from the stored application configuration information according to the to-be-distributed application identifier, and distribute the target application configuration information to a target distribution node corresponding to the to-be-distributed node identifier when the application distribution audit is passed according to the to-be-distributed application identifier and the to-be-distributed node identifier, so that the target distribution node distributes the application according to the target application configuration information. Without the need to dock the application product to multiple cloud application markets at the same time, the application access process is separated from the application deployment process, flexible application deployment can be realized, and the application deployment efficiency is improved. BRIEF DESCRIPTION OF DRAWINGS

[0027] Figure 1 An application environment diagram of the application distribution method in one embodiment;

[0028] Figure 2 A flowchart of the application distribution method in one embodiment;

[0029] Figure 3 A schematic diagram of cross-node message notification in one embodiment;

[0030] Figure 4 A schematic diagram of account creation and account permission management in one embodiment;

[0031] Figure 5 An application architecture diagram of the application distribution method in another embodiment;

[0032] Figure 6 A schematic diagram of access standards and delivery standards in one embodiment;

[0033] Figure 7 A schematic diagram of the application distribution method in yet another embodiment;

[0034] Figure 8 A schematic diagram of distributing target application configuration information in one embodiment;

[0035] Figure 9 A flowchart of the application distribution method in another embodiment;

[0036] Figure 10 A structural block diagram of the application distribution device in one embodiment;

[0037] Figure 11 An internal structure diagram of the computer device in one embodiment. DETAILED DESCRIPTION

[0038] The present application relates to cloud technology, cloud technology (Cloud technology) based on cloud computing business model application network technology, information technology, integration technology, management platform technology, application technology, etc. It can form a resource pool, and can be used on demand, flexible and convenient. Cloud computing technology will become an important support. The background service of the technical network system needs a large amount of computing and storage resources, such as video websites, picture websites and more portals. With the high development and application of the Internet industry, every item may have its own identification mark in the future, and it needs to be transmitted to the background system for logical processing. Different levels of data will be processed separately, and various industry data will need strong system support, which can only be realized through cloud computing.

[0039] In order to make the purpose, technical scheme and advantages of the present application clearer, the present application will be further described in detail below in combination with the drawings and examples. It should be understood that the specific examples described herein are only used to explain the present application and do not limit the present application.

[0040] The application issuing method provided by the present application can be applied to the application environment as shown in Figure 1 . Among them, the terminal 102 communicates with the management control end 104 through the network. When application issuing is needed, the user will send an application issuing request to the management control end 104 through the terminal 102. When receiving the application issuing request, the management control end 104 will read the stored application configuration information corresponding to the application product. The application issuing request carries the to-be-issued application identifier and the to-be-issued node identifier, and the application issuing audit is performed according to the to-be-issued application identifier and the to-be-issued node identifier. When the application issuing audit is passed, the target application configuration information is obtained from the stored application configuration information according to the to-be-issued application identifier, and the target application configuration information is issued to the target issuing node corresponding to the to-be-issued node identifier. Among them, the management control end can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, and big data and artificial intelligence platforms. Basic cloud computing services such as platform. The terminal can be a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, etc., but is not limited thereto. The terminal and the server can be directly or indirectly connected through wired or wireless communication, which is not limited in the present application. Among them, the management control end can be a node in the block chain.

[0041] In one embodiment, as shown in Figure 2 , an application issuing method is provided. Taking the management control end in Figure 1 as an example, the method comprises the following steps:

[0042] Step 202: When an application delivery request is received, the stored application configuration information corresponding to the application product is read. The application delivery request carries the application identifier to be delivered and the node identifier to be delivered. The stored application configuration information is the application configuration information stored when the application product is accessed.

[0043] In this context, "application delivery request" refers to the request to deliver an application product to a cloud node. A cloud node is an edge node corresponding to the cloud platform. For example, a cloud node could specifically refer to an industrial cloud node located in an administrative region such as a prefecture-level city. Here, "cloud" refers to the management and control terminal that manages and controls the edge node. "Application product" refers to a cloud computing application product that can provide product services based on cloud computing. "Stored application configuration information" refers to the application configuration information corresponding to the application product stored when it is accessed. For example, stored application configuration information could specifically refer to the version configuration information and product attribute information corresponding to the application product. Version configuration information could specifically refer to version code, and product attribute information could specifically refer to product specifications, documents, images, product origin, etc.

[0044] In this context, "application product access" refers to the product service provider connecting the application product to the public cloud marketplace in the management and control terminal. Access here means allowing the public cloud marketplace to acquire and store the application product's configuration information. "Application identifier to be distributed" refers to the identifier of the application product to be distributed, used to identify the application product that needs to be distributed. For example, the application identifier to be distributed could specifically be the ID (Identity Document) of the application product to be distributed. "Node identifier to be distributed" refers to the identifier of the cloud node to which the application product needs to be distributed, used to identify the cloud node to which the application product needs to be distributed. For example, the node identifier to be distributed could specifically be the ID of the cloud node to which the application product needs to be distributed.

[0045] Specifically, when application deployment to cloud nodes is required, the product service provider sends an application deployment request, carrying the identifier of the application to be deployed and the identifier of the node to be deployed, to the management control terminal via the terminal. Upon receiving the application deployment request, the management control terminal reads the stored application configuration information corresponding to the application product, and then deploys the application based on this information. It should be noted that the stored application configuration information for the application product here refers to the application configuration information corresponding to all application products connected to the management control terminal.

[0046] Step 204: Review the application distribution based on the application identifier to be distributed and the node identifier to be distributed.

[0047] Specifically, upon receiving an application distribution request, the management control terminal needs to review whether the application distribution can proceed based on the application identifier and the node identifier. During the review, the management control terminal generates and pushes a review prompt based on the application identifier and node identifier to remind the application distribution reviewers to review whether the application distribution can proceed. The application distribution reviewers will then provide feedback on the review result based on the prompt. When the review result is "approved," it means that the application distribution review has been passed.

[0048] Step 206: When the application is approved for distribution, retrieve the target application configuration information from the stored application configuration information based on the application identifier to be distributed.

[0049] Specifically, when the application distribution review is approved, it means that the application can be distributed. The management control terminal will retrieve the corresponding target application configuration information from the stored application configuration information based on the application identifier to be distributed.

[0050] Step 208: Send the target application configuration information to the target distribution node corresponding to the node identifier to be distributed.

[0051] Specifically, after obtaining the target application configuration information, the management control terminal needs to determine the application to be distributed based on the application identifier to be distributed, and determine the target distribution node based on the node identifier to be distributed, so as to obtain the application version information corresponding to the application to be distributed from the target distribution node, and then use the application version information to distribute the target application configuration information to the target distribution node.

[0052] The above application delivery method only requires the application product to be integrated once to obtain the stored application configuration information corresponding to the application product. When an application delivery request is received, the stored application configuration information can be read. After the application delivery is approved based on the application identifier and the node identifier, the target application configuration information is obtained from the stored application configuration information based on the application identifier. The target application configuration information is then delivered to the target delivery node corresponding to the node identifier, so that the target delivery node can deploy the application based on the target application configuration information. This eliminates the need to connect the application product to multiple cloud application marketplaces simultaneously, decoupling the application access process from the application deployment process, enabling flexible application deployment and improving application deployment efficiency.

[0053] In one embodiment, before reading the stored application configuration information corresponding to the application product when an application delivery request is received, the method further includes:

[0054] Receive application product access requests. The application product access requests carry the application identifier, application configuration information, and access party identifier.

[0055] After successful authentication based on the access party identifier, the application configuration information is stored based on the application identifier, thus obtaining the stored application configuration information corresponding to the application product.

[0056] In this context, "Application Product Access Request" refers to a request to access an application product. "Application Identifier" is the identifier of the application product that needs to be accessed, used to distinguish different application products. For example, the application identifier could specifically be the application product's ID. "Access Provider Identifier" is the identifier of the product service provider providing the application product access, used to distinguish different product service providers. For example, the access provider identifier could specifically be the access provider's account.

[0057] Specifically, when a product service provider needs to connect its application product to the public cloud marketplace in the management control terminal, it sends an application product access request to the access address provided by the public cloud marketplace via its terminal. The application product access request carries the application identifier, application configuration information, and access party identifier. Upon receiving the application product access request, the public cloud in the management control terminal first authenticates the access party based on the access party identifier. If the authentication based on the access party identifier is successful, it indicates that the access party has permission to access the application product. The public cloud in the management control terminal then stores the application configuration information based on the application identifier, thus obtaining the stored application configuration information corresponding to the application product. The authentication method based on the access party identifier can be by comparing the access party identifier with preset access permission information. If the access permission information contains access party information corresponding to the access party identifier, the authentication is considered successful.

[0058] In this embodiment, by receiving an application product access request and verifying the identity based on the access party's identifier, the application configuration information is stored according to the application identifier to obtain the stored application configuration information corresponding to the application product, thereby enabling access to the application product.

[0059] In one embodiment, application delivery review based on the application identifier to be delivered and the node identifier to be delivered includes:

[0060] Based on the application identifier and node identifier to be distributed, generate and push review prompts;

[0061] Receive the review results corresponding to the review prompts;

[0062] When the review result is "approved", the application is confirmed to have passed the review and distribution process.

[0063] The review prompt refers to the review of whether the application to be distributed can be distributed to the target distribution node. The target distribution node corresponds to the distribution node identifier, and the application to be distributed corresponds to the application to be distributed identifier. The review result refers to the feedback from the reviewer, which determines whether the application can be distributed.

[0064] Specifically, after the product service provider connects the application product to the management control terminal, it needs to further specify the target distribution nodes that can be distributed. At this time, the product service provider will send an application distribution request to the management control terminal through the terminal. After receiving the application distribution request, the management control terminal will generate and push a review prompt based on the application identifier and distribution node identifier to be distributed, so as to prompt the reviewers to review the application distribution. The reviewers will conduct the application distribution review based on the distribution nodes of the application products agreed upon with the product service provider in advance, and provide feedback on the review results. After receiving the review results, the management control terminal can determine whether the application can be distributed based on the review results. When the review result is approved, it means that the application distribution can be distributed, that is, the application distribution review is approved.

[0065] In this context, the pre-agreed deployment nodes for application products refer to the cloud nodes pre-selected by the product service provider for selling application products. It should be noted that in this embodiment, the number of deployment node identifiers can be more than one; that is, when deploying an application, the product service provider can simultaneously specify multiple deployment nodes for application deployment.

[0066] In this embodiment, by generating and pushing a review prompt based on the application identifier to be distributed and the node identifier to be distributed, and receiving the review result corresponding to the review prompt, the application distribution is confirmed to be approved when the review result is approved, thus enabling the review of application distribution.

[0067] In one embodiment, sending the target application configuration information to the target distribution node corresponding to the node identifier to be distributed includes:

[0068] The application to be distributed is determined based on the application identifier, and the target distribution node is determined based on the node identifier.

[0069] Obtain the application version information corresponding to the application to be distributed from the target distribution node;

[0070] Based on the application version information and the target application configuration information, determine the version difference data to be synchronized;

[0071] Send the version difference data to be synchronized to the target distribution node.

[0072] Here, "Applications to be Deployed" refers to applications that need to be deployed to cloud nodes. "Target Deployment Node" refers to the cloud node where the application needs to be deployed. "Application Version Information" refers to the version information of the applications to be deployed on the target deployment node. "Version Difference Data to be Synchronized" refers to the version difference data that needs to be deployed. This version difference refers to the difference between the newly added version and the application version. The newly added version corresponds to the target application configuration information, and the application version corresponds to the application version information.

[0073] Specifically, after determining that an application needs to be deployed, the management control terminal will identify the application to be deployed based on the application identifier and the target deployment node based on the node identifier. It will then generate and send an application version retrieval request to the target deployment node, so that the target deployment node can provide the application version information corresponding to the application to be deployed. After receiving the application version information, the management control terminal will determine the corresponding application version data based on the application version information and obtain the new version data based on the target application configuration information. By comparing the application version data and the new version data, it will obtain the version difference data to be synchronized and send the version difference data to be synchronized to the target deployment node.

[0074] In this embodiment, by obtaining the application version information corresponding to the application to be distributed from the target distribution node, determining the version difference data to be synchronized based on the application version information and the target application configuration information, and distributing the version difference data to be synchronized to the target distribution node, the target application configuration information can be distributed to the target distribution node.

[0075] In one embodiment, the version difference data to be synchronized, determined based on application version information and target application configuration information, includes:

[0076] Parse the target application configuration information to determine the new version data corresponding to the target application configuration information;

[0077] Determine the application version data corresponding to the application version information, and determine the version difference data to be synchronized based on the application version data and the newly added version data.

[0078] Specifically, the version data corresponding to each version information is pre-stored in the database. When determining the version difference data to be synchronized, the management control terminal parses the target application configuration information to obtain the new version data corresponding to the target application configuration information, and retrieves the corresponding application version data based on the application version information. By comparing the application version data and the new version data, the version difference data to be synchronized is obtained. The target application configuration information can specifically be a binary log file, which can be parsed to obtain the new version data.

[0079] In this embodiment, by determining the new version data corresponding to the target application configuration information and the application version data corresponding to the application version information, the difference data between the versions to be synchronized can be obtained based on the application version data and the new version data.

[0080] In one embodiment, it also includes:

[0081] Receive a message notification request, which carries the message to be notified and the identifier of the node to be notified;

[0082] The node to be notified is determined based on the node identifier, and the notification message is pushed to the node to be notified.

[0083] In this context, a message notification request refers to a request sent by a cloud node to receive a message notification, and a message notification refers to pushing the message to be notified to the receiving node. The message to be notified is the message that needs to be notified, the receiving node is the cloud node that receives the message, and the receiving node identifier is the identifier of the cloud node receiving the message. For example, the receiving node identifier could specifically be the ID of the receiving node.

[0084] Specifically, the management control terminal can communicate with at least two cloud nodes. However, the networks between the two cloud nodes communicating with the management control terminal may not be directly connected. When two cloud nodes want to communicate, they need to use the management control terminal as an intermediary. The cloud node that wants to communicate will send a message notification request to the management control terminal. After receiving the message notification request, the management control terminal will determine the node to be notified based on the node identifier carried in the message and push the notification message to the node to be notified.

[0085] For example, such as Figure 3 As shown, the management and control terminal can utilize its own public cloud message queue to provide cross-node messaging services. When node A generates a business service production message and wants to notify node B of it, node A writes the message to the public cloud message queue. The public cloud message queue then retrieves the message and forwards it to node B's message queue. Similarly, upon receiving a business service subscription message from node A, the public cloud message queue also retrieves the subscription message and forwards it to node A's message queue. Node B's message queue communicates with node B, and node A's message queue communicates with node A.

[0086] In this embodiment, by determining the node to be notified based on the node identifier when receiving a message notification request, and pushing the notification message to the node to be notified, message communication between cloud nodes can be achieved.

[0087] In one embodiment, it also includes:

[0088] Receive a node account creation request, which carries node account information.

[0089] Create a cloud account corresponding to the node based on the node account information, and set the account permissions for the cloud account.

[0090] Among these, a node account creation request refers to a request to create a cloud account corresponding to a node in the cloud. A cloud account is an account that can be used in the cloud. Node account information refers to the information of the account that can be used on the cloud node. Account permissions refer to the permissions that an account has to perform operations in the cloud. For example, operations performed in the cloud include application product access and application product management. Application product management includes the management of information related to application products such as categories, protection agreements, tags, and service providers, as well as the management of operations such as entry, sale, listing, deletion, and approval.

[0091] Specifically, when it's necessary to grant operational permissions to a cloud node, the user sends a node account creation request to the management control terminal via the cloud node. This request includes the node account information. Upon receiving the node account information, the management control terminal creates a corresponding cloud account for the node and acquires the operational permissions for the cloud node. It then sets the account permissions for the cloud account based on these permissions. The operational permissions for each cloud node are pre-set and stored. This method enables unified permission management for cloud nodes, ensuring that cloud node accounts originating from the same cloud node have the same permissions.

[0092] For example, such as Figure 4 As shown, users first create a local account (i.e., a node account) on the local end (i.e., a cloud node). After the local account is created, the local end will send the account information (or node account creation request when creating a cloud account for the first time) to the public cloud in the management control terminal. After receiving the account information, the public cloud will attempt to obtain the primary account certificate (i.e., check if a cloud account corresponding to the node account exists). If the primary account certificate does not exist, it means that a guest account (i.e., a cloud account) corresponding to the local account needs to be created. The public cloud will create the corresponding guest account and re-obtain the primary account certificate. After obtaining the guest account certificate, it will send the guest account certificate to Idaas (Identity asa Service) in the management control terminal, so that Idaas can enable the application identity service and synchronize the account (i.e., set the account permissions of the cloud account).

[0093] In this embodiment, after receiving an account creation request, a cloud account is created based on the node account information, and account permissions corresponding to the cloud account are set, thereby enabling unified permission management of cloud nodes.

[0094] This application also provides an application architecture, such as Figure 5As shown, this application architecture utilizes the aforementioned application deployment method. In this architecture, the management and control end is a hybrid cloud architecture, consisting of a public cloud communicating via a cloud API (Application Programming Interface) and a management and control end. The nodes are local city-level terminals. Specifically, the application deployment method is applied in this architecture as follows:

[0095] When a product service provider wants to integrate an application product, it sends an application product integration request to the cloud marketplace in the public cloud via its terminal. The application product integration request carries the application identifier, application configuration information, and the integrating party identifier. Upon receiving the application product integration request, the cloud marketplace verifies the product service provider's identity based on the integrating party identifier. Once identity verification is successful, the cloud marketplace stores the application configuration information based on the application identifier, thus obtaining the stored application configuration information corresponding to the application product. Furthermore, the management control terminal pre-configures access standards, such as... Figure 6 As shown, taking the integration of SaaS (Software-as-a-Service) application products as an example, the integration standards include signature verification, passwordless login standards, delivery notification interface, renewal notification interface, configuration change notification interface, instance destruction notification interface, etc.

[0096] After the application product integration is completed, the product service provider will further send an application delivery request to the management terminal through the terminal. The application delivery request carries the application identifier to be delivered and the node identifier to be delivered. When the management terminal receives the application delivery request, it will read the stored application configuration information corresponding to the application product in the cloud market through the cloud API. Based on the application identifier to be delivered and the node identifier to be delivered, it will generate and push the review prompt, and receive the review result corresponding to the review prompt. When the review result is approved, the application delivery is confirmed to be approved. When the application delivery is approved, the target application configuration information is obtained from the stored application configuration information based on the application identifier to be delivered, and the target application configuration information is delivered to the target delivery node corresponding to the node identifier to be delivered.

[0097] For example, such as Figure 7 As shown, the "city-level terminal" specifically refers to the industrial cloud located at the city level. The management and control platform, or control terminal, can distribute applications to the industrial cloud, allowing platform users to purchase application products. After the platform user makes the purchase, the industrial cloud and management and control platform deliver the application product, which the user can then use. Furthermore, the management and control terminal has pre-set delivery standards. For example... Figure 6 As shown, the delivery process may include delivery standards such as image standards, deployment standards, component standards, and configuration standards.

[0098] Furthermore, the control end primarily distributes the target application configuration information to the target distribution node corresponding to the node identifier to be distributed, through the synchronization center. The specific distribution process can be as follows: Figure 8 As shown, the cloud refers to the control end, and the edge refers to the target distribution node. After confirming the need for application distribution, the cloud writes the target application configuration information into the target master database and creates a synchronization task to the Master server in the cloud. The Master server can communicate with the Slave servers in the edge. After receiving the synchronization task, the Master server uses updateAt to retrieve the target application configuration information from the target master database, parses the target application configuration information (i.e., parses the binlog), obtains the new version data and offset, stores the new version data and offset in the target master database, determines the application to be distributed based on the application identifier, retrieves the node version (i.e., application version information) from the edge, determines the application version data corresponding to the node version, and determines the version difference data based on the application version data and the new version data. The version difference data is then synchronized to the Slave server in the edge. After receiving the version difference data, the Slave server sets a transaction row lock, uses the version difference data to update the application, queries the backup of the data to be updated, replays the data when the application update fails, and unlocks the transaction when the application update is complete.

[0099] Furthermore, such as Figure 5 As shown, in addition to application delivery, the management and control terminal also includes a message center and a message queue (i.e., CMQ (Cloud Message Queue)) to enable cross-cloud message notification. The message queue includes node message queues corresponding to each city. When city A needs to send a notification message to city B, it will send a message notification request to the message center in the management and control terminal. The message notification request will carry the message to be notified and the node identifier of city B. After receiving the message notification request, the message center will push the message to be notified to the B node message queue in the message queue according to the node identifier of city B, so that the B node message queue can push the message to be notified to city B.

[0100] Furthermore, such as Figure 5 As shown, public cloud accounts can also be linked. This refers to using a unified cloud account for a single city / region, thereby enabling unified access control for users corresponding to that city / region. Specifically, during public cloud account linking, the city / region sends an account creation request to the public cloud, which includes node account information. Upon receiving the request, the public cloud creates a cloud account based on the node account information and sets the corresponding account permissions.

[0101] Furthermore, such asFigure 5 As shown, the management and control system also includes a product center, order center, access center, and instance center. The product center provides management functions for information such as products, categories, protection agreements, tags, and service providers. It offers capabilities for application selection, listing, deletion, and approval, as well as for local applications at the city / prefecture level, including listing, custom billing items, and deletion. It ensures consistency of product information across the management and control system, city / prefecture level, and cloud / prefecture level through proactive push notifications and periodic polling from the cloud marketplace. Selected applications refer to those that can be distributed to city / prefecture levels, while local applications refer to applications self-operated by city / prefecture levels. The order center is responsible for the entire purchase process in a hybrid cloud scenario, including order placement, payment, instance delivery notification, refunds, and cloud marketplace integration. It is the main initiator of the SaaS service purchase process. Users browse through the product center, click to purchase, place an order through the order center, pay, and upon successful payment, the order notification is sent to the instance center for delivery processing. The access center is responsible for defining unified access standards for SaaS applications at the city / prefecture level and for platform access, ensuring compatibility with the access standards of cloud marketplace service providers for SaaS applications. This includes the integration of service activation, renewal, upgrade, conversion, destruction, and expiration capabilities. The Instance Center is responsible for connecting with the cloud marketplace and product service providers. For SaaS products purchased by users, the Instance Center is responsible for the lifecycle control of the service instances after purchase, including instance delivery, renewal, expiration, configuration upgrades, and shutdown. The Instance Center is responsible for handling the subsequent processes after the purchase, which is the core link in the delivery of products after the user purchases.

[0102] Furthermore, such as Figure 5 As shown, public clouds also include CAM (Cloud Access Management) and Idaas (Application Identity Service). Access Management primarily helps customers securely manage access permissions to resources under their cloud accounts. Users can create, manage, and destroy users (groups) through CAM, and use identity management and policy management to control other users' permissions to use cloud resources. Idaas provides enterprises with unified and efficient identity management services. Unlike the traditional model of multiple systems maintaining different user information and distributed identity authentication, it supports centralized management of enterprise user identities and authentication methods, enabling a single account to access all application services. Users only need to authenticate once to log in to all applications and systems within their authorized scope without a password. User login and access behavior can also be monitored uniformly, greatly improving enterprise IT management efficiency and reducing maintenance costs.

[0103] like Figure 9 As shown, this application also provides a flowchart to illustrate the above application delivery method, which specifically includes the following steps:

[0104] Step 902: Receive the application product access request. The application product access request carries the application identifier, application configuration information, and access party identifier.

[0105] Step 904: After the identity verification is successful based on the access party identifier, the application configuration information is stored based on the application identifier to obtain the stored application configuration information corresponding to the application product.

[0106] Step 906: When an application delivery request is received, read the stored application configuration information corresponding to the application product. The application delivery request carries the application identifier to be delivered and the node identifier to be delivered.

[0107] Step 908: Generate and push an approval prompt based on the application identifier to be distributed and the node identifier to be distributed;

[0108] Step 910: Receive the review result corresponding to the review prompt;

[0109] Step 912: When the review result is "approved", confirm that the application has been approved for distribution.

[0110] Step 914: When the application is approved for distribution, retrieve the target application configuration information from the stored application configuration information based on the application identifier to be distributed.

[0111] Step 916: Determine the application to be distributed based on the application identifier to be distributed, and determine the target distribution node based on the node identifier to be distributed;

[0112] Step 918: Obtain the application version information corresponding to the application to be distributed from the target distribution node;

[0113] Step 920: Parse the target application configuration information to determine the new version data corresponding to the target application configuration information;

[0114] Step 922: Determine the application version data corresponding to the application version information, and determine the version difference data to be synchronized based on the application version data and the newly added version data;

[0115] Step 924: Send the version difference data to be synchronized to the target distribution node.

[0116] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps.

[0117] In one embodiment, such as Figure 10 As shown, an application distribution device is provided. This device can be a software module, a hardware module, or a combination of both as part of a computer device. Specifically, the device includes: a first processing module 1002, an auditing module 1004, a second processing module 1006, and a synchronization module 1008, wherein:

[0118] The first processing module 1002 is used to read the stored application configuration information corresponding to the application product when it receives an application delivery request. The application delivery request carries the application identifier to be delivered and the node identifier to be delivered. The stored application configuration information is the application configuration information stored when accessing the application product.

[0119] The review module 1004 is used to review the application distribution based on the application identifier to be distributed and the node identifier to be distributed.

[0120] The second processing module 1006 is used to obtain the target application configuration information from the stored application configuration information according to the application identifier to be issued when the application is approved.

[0121] The synchronization module 1008 is used to send the target application configuration information to the target distribution node corresponding to the node identifier to be distributed.

[0122] The aforementioned application delivery device only needs to complete the connection of the application product once to obtain the stored application configuration information corresponding to the application product. When it receives an application delivery request, it can read the stored application configuration information. After the application delivery is approved based on the application identifier and the node identifier, it can retrieve the target application configuration information from the stored application configuration information based on the application identifier and deliver the target application configuration information to the target delivery node corresponding to the node identifier. This allows the target delivery node to deploy the application based on the target application configuration information, without having to connect the application product to multiple cloud application marketplaces simultaneously. By separating the application access process from the application deployment process, it enables flexible application deployment and improves application deployment efficiency.

[0123] In one embodiment, the application delivery device further includes an access module, which is used to receive an application product access request. The application product access request carries an application identifier, application configuration information, and access party identifier. After the identity verification is passed based on the access party identifier, the application configuration information is stored based on the application identifier to obtain the stored application configuration information corresponding to the application product.

[0124] In one embodiment, the review module is further configured to generate and push review prompts based on the application identifier to be distributed and the node identifier to be distributed, receive the review result corresponding to the review prompt, and determine that the application distribution review is approved when the review result is approved.

[0125] In one embodiment, the synchronization module is further configured to determine the application to be distributed based on the application identifier to be distributed, determine the target distribution node based on the node identifier to be distributed, obtain the application version information corresponding to the application to be distributed from the target distribution node, determine the version difference data to be synchronized based on the application version information and the target application configuration information, and distribute the version difference data to be synchronized to the target distribution node.

[0126] In one embodiment, the synchronization module is further configured to parse the target application configuration information, determine the new version data corresponding to the target application configuration information, determine the application version data corresponding to the application version information, and determine the version difference data to be synchronized based on the application version data and the new version data.

[0127] In one embodiment, the application delivery device further includes a message processing module, which is used to receive a message notification request, the message notification request carrying a message to be notified and a node identifier to be notified, determine the node to be notified based on the node identifier to be notified, and push the message to be notified to the node to be notified.

[0128] In one embodiment, the application delivery device further includes an account management module, which is used to receive a node account creation request, the node account creation request carries node account information, create a cloud account corresponding to the node based on the node account information, and set the account permissions of the cloud account.

[0129] Specific limitations regarding the application delivery device can be found in the limitations of the application delivery method described above, and will not be repeated here. Each module in the aforementioned application delivery device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0130] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 11 As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores data such as application configuration information. The network interface communicates with external terminals via a network connection. When the computer program is executed by the processor, it implements an application delivery method.

[0131] Those skilled in the art will understand that Figure 11 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0132] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0133] In one embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0134] In one embodiment, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and executes the computer instructions, causing the computer device to perform the steps in the above method embodiments.

[0135] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0136] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0137] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. An application distribution method, characterized in that, Applied to the management and control terminal, the method includes: When an application delivery request is received from a product service provider, the stored application configuration information corresponding to the application product is read. The application delivery request carries the application identifier to be delivered and the node identifier to be delivered. The stored application configuration information is the application configuration information stored when the application product is accessed. The application delivery request refers to a request to deliver the application product to a cloud node. The node identifier to be delivered refers to the identifier of the cloud node to which the application product needs to be delivered, used to determine the cloud node to which the application product needs to be delivered. Accessing the application product refers to the product service provider accessing the application product to the public cloud marketplace in the management and control terminal. Based on the application identifier to be distributed and the node identifier to be distributed, a review prompt is generated and pushed to instruct the application distribution review to be carried out according to the cloud node for selling application products pre-selected by the product service provider. Receive the audit result corresponding to the audit prompt; When the review result is "approved", the application is confirmed to have passed the review. When the application is approved for distribution, the target application configuration information is obtained from the stored application configuration information based on the application identifier to be distributed; The target application configuration information is sent to the target distribution node corresponding to the node identifier to be distributed.

2. The method according to claim 1, characterized in that, Before reading the stored application configuration information corresponding to the application product when receiving an application delivery request, the process also includes: Receive an application product access request, the application product access request carrying the application identifier, application configuration information and access party identifier; After successful authentication based on the access party identifier, the application configuration information is stored based on the application identifier to obtain the stored application configuration information corresponding to the application product.

3. The method according to claim 1, characterized in that, The step of sending the target application configuration information to the target distribution node corresponding to the node identifier to be distributed includes: The application to be delivered is determined based on the application identifier to be delivered, and the target delivery node is determined based on the node identifier to be delivered. Obtain the application version information corresponding to the application to be distributed from the target distribution node; Based on the application version information and the target application configuration information, determine the version difference data to be synchronized; The version difference data to be synchronized is sent to the target sending node.

4. The method according to claim 3, characterized in that, The step of determining the version difference data to be synchronized based on the application version information and the target application configuration information includes: The target application configuration information is parsed to determine the new version data corresponding to the target application configuration information; Determine the application version data corresponding to the application version information, and determine the version difference data to be synchronized based on the application version data and the newly added version data.

5. The method according to claim 1, characterized in that, Also includes: Receive a message notification request, the message notification request carrying a message to be notified and an identifier of the node to be notified; The node to be notified is determined based on the node identifier, and the notification message is pushed to the node to be notified.

6. The method according to claim 1, characterized in that, Also includes: Receive a node account creation request, the node account creation request carrying node account information; Create a cloud account corresponding to the node based on the node account information, and set the account permissions for the cloud account.

7. An application distribution device, characterized in that, The device, used in management and control systems, includes: The first processing module is used to read the stored application configuration information corresponding to the application product when it receives an application delivery request from the product service provider. The application delivery request carries the application identifier to be delivered and the node identifier to be delivered. The stored application configuration information is the application configuration information stored when the application product is accessed. The application delivery request refers to a request to deliver the application product to a cloud node. The node identifier to be delivered refers to the identifier of the cloud node to which the application product needs to be delivered, used to determine the cloud node to which the application product needs to be delivered. Accessing the application product refers to the product service provider accessing the application product to the public cloud marketplace in the management and control terminal. The review module is used to generate and push review prompts based on the application identifier to be distributed and the node identifier to be distributed, so as to instruct the cloud node for application distribution review according to the application product pre-selected by the product service provider, receive the review result corresponding to the review prompt, and determine that the application distribution review is passed when the review result is approved. The second processing module is used to obtain the target application configuration information from the stored application configuration information according to the application identifier to be issued when the application is approved. The synchronization module is used to send the target application configuration information to the target distribution node corresponding to the node identifier to be distributed.

8. The apparatus according to claim 7, characterized in that, The device further includes an access module, which is used to receive an application product access request. The application product access request carries an application identifier, application configuration information, and an access party identifier. After the identity verification is passed according to the access party identifier, the application configuration information is stored according to the application identifier to obtain the stored application configuration information corresponding to the application product.

9. The apparatus according to claim 7, characterized in that, The synchronization module is further configured to determine the application to be distributed based on the application identifier to be distributed, determine the target distribution node based on the node identifier to be distributed, obtain the application version information corresponding to the application to be distributed from the target distribution node, determine the version difference data to be synchronized based on the application version information and the target application configuration information, and distribute the version difference data to be synchronized to the target distribution node.

10. The apparatus according to claim 9, characterized in that, The synchronization module is also used to parse the target application configuration information, determine the new version data corresponding to the target application configuration information, determine the application version data corresponding to the application version information, and determine the version difference data to be synchronized based on the application version data and the new version data.

11. The apparatus according to claim 7, characterized in that, The device further includes a message processing module, which is used to receive a message notification request, the message notification request carrying a message to be notified and a node identifier to be notified, determine the node to be notified based on the node identifier to be notified, and push the message to be notified to the node to be notified.

12. The apparatus according to claim 7, characterized in that, The device also includes an account management module, which is used to receive a node account creation request, the node account creation request carrying node account information, create a cloud account corresponding to the node based on the node account information, and set the account permissions of the cloud account.

13. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

14. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images