CN116800735A

CN116800735A - Cloud application management method and device, storage medium and electronic equipment

Info

Publication number: CN116800735A
Application number: CN202210257975.7A
Authority: CN
Inventors: 李斌
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2022-03-16
Filing date: 2022-03-16
Publication date: 2023-09-22

Abstract

The embodiment of the application discloses a cloud application management method, a device, a storage medium and electronic equipment, wherein the method is applied to a cloud application management server, the cloud application management server comprises an application service manager, an application instance manager and an application access manager, and the application service manager generates a record corresponding to feedback to trigger an application display end to display the application service in response to the condition of acquiring an application service input request, generates an instance trigger request aiming at the application service and transmits the instance trigger request to the application instance manager; the application instance manager generates instance parameters in response to the instance trigger request and sends the instance parameters to the application access manager; the application access manager transmits the instance parameters to the origin server, and triggers the origin server to generate and deploy an instance according to the instance parameters. The application can efficiently, stably and reliably provide the SaaS service.

Description

Cloud application management method and device, storage medium and electronic equipment

Technical Field

The embodiment of the application relates to the technical field of computers, in particular to a cloud application management method, a cloud application management device, a storage medium and electronic equipment.

Background

The software service is a novel service providing mode, and a service provider is responsible for setting up all network infrastructures, software and hardware operation platforms, all early implementation, later maintenance and other series of services required by the informatization, and a user can enjoy the service through the Internet only by purchasing the service without paying attention to the maintenance details of the service, so that the consumption cost is obviously reduced. However, the application management flow of the platform for providing the user with the software-based transaction is complex, the coupling degree is high, and the reliability guarantee scheme is lacking, so that the robustness is not high.

Disclosure of Invention

In order to enable a software service transaction platform to reduce the complexity of an authentication and authorization process, and provide fine-grained cloud application management for users, the embodiment of the application provides a cloud application management method, a cloud application management device, a storage medium and electronic equipment.

In one aspect, an embodiment of the present application provides a cloud application management method, applied to a cloud application management server, where the cloud application management server includes an application service manager, an application instance manager, and an application access manager, and the method includes:

in response to obtaining an application service entry request, the application service manager generates a record corresponding to an application service, wherein the application service entry request comprises an address of a source server for providing the application service;

The application service manager feeds back the record to trigger the application display end to display the application service in response to the situation that the application display request sent by the application display end is acquired;

in response to receiving demand information for the application service from the application presentation end, the application service manager generates an instance trigger request for the application service and transmits the instance trigger request to the application instance manager;

the application instance manager responds to the instance triggering request to generate instance parameters, and the instance parameters are sent to the application access manager;

the application access manager transmits the instance parameters to the address of the origin server to trigger the origin server to generate and deploy an instance according to the instance parameters.

In another aspect, an embodiment of the present application provides a cloud application management apparatus, applied to a cloud application management server, where the apparatus includes: an application service manager, an application instance manager, and an application access manager;

the application service manager is used for responding to the condition of acquiring an application service input request, generating a record corresponding to the application service, wherein the application service input request comprises an address of a source server for providing the application service, and responding to the condition of acquiring an application display request sent by an application display end, feeding back the record to trigger the application display end to display the application service;

The application service manager is further configured to generate an instance trigger request for the application service in response to receiving the requirement information for the application service from the application display end, and transmit the instance trigger request to the application instance manager;

the application instance manager is used for responding to the instance triggering request to generate instance parameters and sending the instance parameters to the application access manager;

the application access manager is used for transmitting the instance parameter to the address of the source server so as to trigger the source server to generate and deploy an instance according to the instance parameter.

In another aspect, an embodiment of the present application provides a computer readable storage medium, where at least one instruction or at least one program is stored, where the at least one instruction or at least one program is loaded and executed by a processor to implement a cloud application management method described above.

In another aspect, an embodiment of the present application provides an electronic device including at least one processor, and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor, and the at least one processor implements the cloud application management method by executing the instructions stored by the memory.

In another aspect, an embodiment of the present application provides a computer program product, including a computer program or an instruction, where the computer program or the instruction implement the cloud application management method described above when executed by a processor.

The cloud application management method provided by the application can automatically input the SaaS services provided by each ISV in various cloud environments, and intensively display the input SaaS services, and automatically trigger and establish a use link of the SaaS services under the condition that the requirement information for a certain SaaS service is acquired, so that a user can directly consume the SaaS services, that is, the cloud application management method in the embodiment of the application essentially provides an application store for the SaaS services in the cloud environment, and provides a unified platform for inquiring, browsing, purchasing, using, ordering and other operations related to the SaaS services.

In addition, in the implementation process of the embodiment of the application, each manager can carry out decoupling communication, and a plurality of reliability guarantee mechanisms are arranged to ensure the reliability of the communication, so that an efficient, rapid and stable SaaS service platform can be presented.

Drawings

In order to more clearly illustrate the technical solutions and advantages of embodiments of the present application or related technologies, the following description will briefly explain the drawings required for the embodiments or related technologies, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to the drawings without inventive effort for those skilled in the art.

Fig. 1 is a schematic view of a cloud service framework provided in an embodiment of the present disclosure;

fig. 2 is a schematic flow chart of a cloud application management method according to an embodiment of the present disclosure;

FIG. 3 is a first schematic diagram of cloud application management provided by an embodiment of the present application;

FIG. 4 is a second schematic diagram of cloud application management provided by an embodiment of the present application;

FIG. 5 is a third schematic diagram of cloud application management provided by an embodiment of the present application;

FIG. 6 is a fourth schematic diagram of cloud application management provided by an embodiment of the present application;

FIG. 7 is a fifth schematic diagram of cloud application management provided by an embodiment of the present application;

fig. 8 is a block diagram of a cloud application management apparatus provided by an embodiment of the present application;

fig. 9 is a schematic hardware structure of an apparatus for implementing the method provided by the embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the embodiments of the present application.

It should be noted that the terms "first," "second," and the like in the description and the claims of the embodiments of the present application and the above-described drawings are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or server that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

In order to make the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings and examples. It should be understood that the detailed description and specific examples, while indicating the embodiment of the application, are intended for purposes of illustration only and are not intended to limit the scope of the application.

The terms "first" and "second" are used below for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present embodiment, unless otherwise specified, the meaning of "plurality" is two or more. In order to facilitate understanding of the technical solutions and the technical effects produced by the embodiments of the present application, the embodiments of the present application first explain related terms:

cloud technology (Cloud technology): the hosting technology is used for integrating hardware, software, network and other series resources in a wide area network or a local area network to realize calculation, storage, processing and sharing of data. The cloud computing business model application-based network technology, information technology, integration technology, management platform technology, application technology and the like can be collectively called to form a resource pool, and the resource pool is flexible and convenient as required. Cloud computing technology will become an important support. Background services of technical networking systems require a large amount of computing, storage resources, such as video websites, picture-like websites, and more portals. Along with the high development and application of the internet industry, each article possibly has an own identification mark in the future, the identification mark needs to be transmitted to a background system for logic processing, data of different degrees can be processed separately, and various industry data need strong system rear shield support and can be realized only through cloud computing.

Software servitization: software as a Service, saaS. The SaaS platform is a platform that manages SaaS software. The SaaS provider builds all network infrastructure, software and hardware operation platforms required by informatization for enterprises and is responsible for a series of services such as implementation in the early stage, maintenance in the later stage and the like, and the enterprises can use the information system through the Internet without purchasing software and hardware, building a machine room and recruiting computer professionals. SaaS is a software layout model whose applications are specifically designed for network delivery, facilitating users' hosting, deployment and access through the internet.

SaaS application is a mode of software provided by a network, a user does not need to purchase the software any more, but instead rents the web-based software to a provider to manage business activities of an enterprise, and the service provider can manage and maintain the software in full right. In the embodiment of the application, the SaaS application sources comprise public cloud, private cloud and mixed cloud, and for the SaaS product, the SaaS application sources can be provided by corresponding service providers, namely service providers ISVs, the service purchased by the user can be self-research application or can come from related service providers, and the service providers need to finish whole delivery docking according to the frame standard of the embodiment of the application, so that the corresponding SaaS service is provided.

In the related art, a transaction platform of a software service with high reliability and low coupling degree is difficult to provide for a user, so that the cloud application management method provided by the embodiment of the application can automatically input the SaaS service provided by each ISV in various cloud environments and intensively display the input SaaS service, and automatically trigger and establish a use link of the SaaS service under the condition that the requirement information of the user for a certain SaaS service is acquired, so that the user can directly consume the SaaS service, that is, the cloud application management method provided by the embodiment of the application essentially provides an application store for the SaaS service in the cloud environment and provides a unified platform for inquiring, browsing, purchasing, using, ordering and other operations related to the SaaS service.

The method provided by the embodiment of the application can relate to a blockchain, namely the method provided by the embodiment of the application can be realized based on the blockchain, or the data related in the method provided by the embodiment of the application can be stored based on the blockchain, or an execution object of the method provided by the embodiment of the application can be positioned in the blockchain. Blockchains are novel application modes of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanisms, encryption algorithms, and the like. The Blockchain (Blockchain), which is essentially a decentralised database, is a string of data blocks that are generated by cryptographic means in association, each data block containing a batch of information of network transactions for verifying the validity of the information (anti-counterfeiting) and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, and an application services layer.

The embodiment of the application can be applied to public cloud, private cloud or mixed cloud scenes. A Private Cloud (Private Cloud) is a Cloud infrastructure created with software and hardware resources within a firewall for organizations or departments within an enterprise to share resources within a data center. A private cloud is created, typically cloud device (IaaS, infrastructure as a Service, infrastructure as a service) software in addition to hardware resources. Private cloud computing also includes three levels of cloud hardware, cloud platform, cloud services. In contrast, cloud hardware is a data center from a user's computer or server, rather than a cloud computing vendor. Cloud computing manufacturers build data centers to provide public cloud services for thousands of millions of users, thus requiring tens of millions of servers. Private cloud computing serves only friends and relatives to individuals, and staff and clients and suppliers to businesses, so that computers or servers of individuals or businesses are sufficient to provide cloud services.

Public clouds (Public clouds) generally refer to clouds that third party providers provide for users to be able to use, public clouds are generally available through the Internet and may be free or low cost, and the core function of Public clouds is to share resource services. There are many examples of such clouds that can provide services throughout the open public network today.

Hybrid clouds (Hybrid clouds) merge Public clouds (Public clouds) and Private clouds (Private clouds), which are the main modes and development directions of Cloud computing in recent years. Private clouds are mainly enterprise-oriented, and enterprises prefer to store data in the private clouds for safety, but at the same time wish to obtain computing resources of public clouds, in which case hybrid clouds are increasingly adopted, and mix and match the public clouds and the private clouds to obtain the best effect.

Public cloud, private cloud or hybrid cloud can deploy various applications, and the applications published, sold or run by the public cloud, private cloud or hybrid cloud are cloud applications. The embodiment of the application is not limited to the field related to cloud application, and for example, the cloud application can relate to cloud internet of things, cloud calling, cloud security, cloud social contact, cloud medical treatment, cloud computing, cloud storage and the like.

In one embodiment, the embodiment of the application can be applied to a cloud service framework, and an architecture diagram of the cloud service framework is shown in fig. 1. The cloud service framework includes support tools, application service manager (application marketplace), application instance manager (instance center), and base service tools.

The basic service tool comprises core contents such as an account center and a charging center, wherein the account center is responsible for basic operations such as account information, login management, registration, activation and the like, the rights center is responsible for rights system management of the hybrid cloud platform, and the charging center comprises a billing center, an order center and a payment management function. The order center is responsible for processing the whole purchasing application flow of the account corresponding to the user, including the links of the account of ordering, paying, notifying instance delivery, refund, docking cloud market and the like, the user corresponding to the account browses the application through the commodity center in the application module, clicks and purchases, and then ordering, paying and successful payment are performed through the order center, and the order notifies the instance center of carrying out delivery logic processing. The billing center is responsible for billing information after the order is paid.

The application market realizes unified management and configuration of commodities of various sources, and the commodities can be SaaS applications. In the embodiment of the application, if the commodities originate from different clouds, the cloud service framework is a hybrid cloud framework. The scenes related to the commodities in the application market comprise importing from the cloud, checking, putting on shelf, putting off shelf, selling and the like, and the application market is related to the scenes. The commodity can be put on shelf through the public cloud and also can be put on shelf through the private cloud, that is to say, the mixed cloud framework can provide a unified commodity put on shelf interface for the private cloud and the public cloud. The application market simultaneously serves the aspects of commodity information display, maintenance and the like, is a key link of whole commodity information maintenance, and realizes unified maintenance of commodity information of public cloud commodities and commodity information of private cloud commodities.

The instance center is responsible for managing application instance information, package block instance management, and related to basic information such as instance information, instance access address, instance expiration time and the like after the user purchases the SaaS application, wherein the user accesses an entry for purchasing the SaaS application. The hybrid cloud is responsible for interfacing with cloud markets and service providers, saaS commodities purchased by users are controlled by the life cycle of the post-service instance purchased by the instance center, the post-service instance comprises operations of instance shipment, renewal, expiration, configuration upgrading, closing and the like, the post-process after the purchase is completed is responsible for processing by the instance center, and the control is a core link of commodity delivery after the purchase of the users.

The access center, namely an application access manager, is responsible for interfacing service providers of public cloud and private cloud, and performs the processes of shipping, interfacing and carding, interface verification, data interfacing and information synchronization. The access center is used as a management center in the mixed cloud scene, realizes function realization level docking, mainly realizes docking of local service providers ISV, comprises service opening, renewal, upgrading, expiration and destroying the whole process docking, and when the instance center delivers local service, service side docking is carried out, the access center is called, the access center notifies a service provider to carry out delivery processing, the service provider returns delivery information, the instance center carries out delivery information judgment, and returns to the instance center, so that the whole delivery process is completed.

The support tool includes related tools for log maintenance, call chain management, transport management, etc. of the entire frame to facilitate efficient operation of the support frame.

In order to support the operation of the tools and managers described above, the framework is also provided with an underlying IaaS layer and an intermediate base component layer. In a specific embodiment, the framework can support automatic access and implementation of the SaaS service in the hybrid cloud mode, and realize the processes of automatic access, service input, service loading, service purchase and automatic service delivery of the third party SaaS application in the hybrid cloud mode. The commodity access side comprises flows of SaaS application creation, renewal, upgrading, destroying, expiration and the like, so that local is realized, and the instance center realizes automatic delivery docking of the SaaS application.

In the following, a cloud application management method according to an embodiment of the present application is described, and fig. 2 shows a flow chart of the cloud application management method provided by the embodiment of the present application, where the method is applied to a cloud application management server, and the cloud application management server includes an application service manager, an application instance manager, and an application access manager.

In one particular embodiment, the application service manager (application marketplace) includes three parts, application entry, application management, and application vending. The application market is responsible for cloud and local SaaS service input in a commodity center, commodity loading is finished, and after the local application loading is finished, the commodity can be purchased and ordered in the commodity center. The application input module is responsible for input butt joint of the local SaaS application, and comprises input debugging, core processes of covering creation of an instance, renewal of charge, expiration, destruction and the like, and commodity input is completed after input and debugging are completed. The application management module is responsible for loading, releasing and unloading commodities in the application management module after the SaaS application is input, and ordering and purchasing can be performed in the application market after the commodities are loaded and released. The application selling module is responsible for the application to be displayed in the application selling center after being released, and a user can check, place an order and purchase the application, so that the application selling module is an entrance for the user to purchase the application.

The application instance manager (instance center) is responsible for instance management work after a user purchases an application, and comprises core processes of instance creation, renewal, expiration and the like, and covers core links of instance information maintenance, life cycle management, instance access and the like.

Embodiments of the present application provide method operational steps as described above in the embodiments or flowcharts, but may include more or fewer operational steps based on conventional or non-inventive labor. The order of steps recited in the embodiments is merely one way of performing the order of steps and does not represent a unique order of execution. When implemented in a system, terminal device or server product in practice, the methods illustrated in the embodiments or figures may be performed sequentially or in parallel (e.g., in a parallel processor or multithreaded environment), and may include:

s101, in response to the situation that an application service input request is acquired, the application service manager generates a record corresponding to the application service, and the application service input request comprises an address of a source server for providing the application service.

The embodiment of the application can support the processes of inputting, putting on shelf, purchasing by order, notifying delivery and delivering results of ISV to the service from the ISV, wherein commodity inputting comprises the related debugging of the SaaS service of the ISV, and the specific processes comprise core operations such as creation, renewal, expiration, destruction and the like, and after inputting is completed, the user can put on shelf and release locally, and can purchase. The application market completes the recording step by receiving an application service recording request from the ISV in cooperation with the ISV, and generates a record corresponding to the service provided by the ISV after the recording is completed, wherein the application service recording request comprises an address of a source server for providing the application service, and the purpose of the application service recording request is that after a user purchases the service, the ISV can be triggered to provide the corresponding service for the user by sending a message to the address.

Referring to fig. 3, a first schematic diagram of cloud application management is shown. There are two kinds of ISV services, which provide a local SaaS service and an ecological SaaS service, respectively, the former is a service homologous to the above-mentioned framework, and the latter is a third party service. Correspondingly, the application service input request further includes an application service type, where the application service type includes a first type of application service type or a second type of application service type, an application service corresponding to the first type of application service type is a homologous service (local SaaS service) of the cloud application management server, and an application service corresponding to the second type of application service type does not belong to the homologous service (ecological SaaS service) of the cloud application management server.

S102, in response to the situation that an application display request sent by an application display end is obtained, the application service manager feeds back the record to trigger the application display end to display the application service.

When the application service manager inputs the application service, the application service can be used as a commodity to be put on shelf, and after the commodity is put on shelf, the application service manager can respond to the condition of acquiring an application display request sent by an application display end, and the application service manager feeds back the record so as to trigger the application display end to display the application service. The application display end is a client held by a user, and the client can check the on-shelf commodity by accessing the application service manager.

S103, in response to receiving the demand information for the application service from the application display end, the application service manager generates an instance trigger request for the application service and transmits the instance trigger request to the application instance manager.

When a user purchases a certain application service, payment can be carried out for the application service, and after the payment operation is successful, the application service manager can generate an instance triggering request for the application service based on the requirement information and transmit the instance triggering request to the application instance manager.

S104, the application instance manager responds to the instance triggering request to generate instance parameters, and the instance parameters are sent to the application access manager.

The application access manager in the embodiment of the application is the access center.

S105, the application access manager transmits the instance parameters to the address of the source server to trigger the source server to generate and deploy the instance according to the instance parameters.

Referring to fig. 3, after the user places an order and purchases, the application instance manager may generate instance parameters for the order, and send a shipment notification to the access center based on the instance parameters, where the access center may trigger the provider (address of origin server) of the ISV service to ship, and the process of shipping is to generate and deploy an instance based on the instance parameters.

In one embodiment, the application service manager generates an instance trigger request for the application service, and transmits the instance trigger request to the application instance manager, including: the application service manager generates an instance trigger request for the application service and sends the instance trigger request to an instance request management queue; the application instance manager accesses the instance request management queue to obtain the instance trigger request.

The access center transmitting the instance parameter to the address of the origin server to trigger the origin server to generate and deploy the instance according to the instance parameter, including: the access center calls an asynchronous communication interface to send the instance parameter to the address of the source server so as to trigger the source server to asynchronously generate and deploy the instance based on the instance parameter; responding to the condition of obtaining a target address fed back by the asynchronous communication interface in preset time, and returning the target address as an example address to the application service manager so as to trigger the application service manager to respond the target address as the requirement information; wherein the target address is a deployment address of the instance generated by the origin server based on the instance parameter.

Referring to fig. 4, a second schematic diagram of cloud application management is shown. After the user finishes the operations of ordering, paying and the like, the application service manager can acquire the requirement information of the user, the requirement information can be understood as an effective order, an instance trigger request obtained based on the requirement information is sent to an instance request management queue, and the application instance manager acquires the instance trigger request by consuming the data form in the instance request management queue. This design decouples the application service manager and the application instance manager from each other, working asynchronously and without affecting each other.

After the application instance manager transmits the instance parameters to the application access manager, the application access manager needs to trigger the origin server to ship, i.e. trigger the origin server to provide the SaaS service purchased by the user. In particular, the interaction of the application instance manager and origin server is also asynchronous, thus decoupling well.

If the target address fed back by the source server is acquired within the preset time, the application instance manager can return the target address, and the target address can be finally transmitted to the client held by the user, so that the user can use the purchased SaaS service by accessing the target address. After feeding back the target address, the source server deploys an instance of SaaS service for the user at the target address for access by the user.

If the target address is not obtained within the preset time, a timeout may be fed back, prompting a purchase failure, a refund may be made, or a request for shipment may be attempted again. Of course, idempotency is ensured by the ISV during shipment from the order information.

In one embodiment, after the application instance manager accesses the instance request management queue to obtain the instance trigger request, please refer to fig. 5, which shows a third schematic diagram of cloud application management. Fig. 5 is a schematic flow chart of a delivery process, that is, a process of finally generating an instance according to an instance trigger request, where the method further includes:

s201, determining a target hash identifier corresponding to the instance triggering request.

The method for acquiring the target hash identifier is not limited, and in one embodiment, the method for generating the message abstract based on the hash can be called according to the commodity content and the commodity identifier in the instance triggering request to acquire the target hash identifier uniquely corresponding to the instance triggering request.

S202, inquiring the target hash identification in a first storage space, wherein the first storage space is used for storing hash identifications corresponding to all the currently processed requests.

In the embodiment of the application, a plurality of threads can process the instance triggering request in parallel, in order to avoid the condition that a plurality of threads process the same instance triggering request, the embodiment of the application uses the first storage space to record the hash mark corresponding to each request being processed, and the hash mark generating method is consistent with the previous and is not repeated herein. The embodiment of the application is not limited to the first storage space, and in one embodiment, redis, redis (Remote Dictionary Server), namely remote dictionary service, can be used, and the remote dictionary service is an open-source log-type Key-Value database which supports a network, can be based on a memory and can also be persistent.

S203, discarding the instance triggering request in response to the condition that the target hash identification is queried.

S204, in response to the fact that the target hash identification is not queried, the target hash identification is written into the first storage space.

And if the target hash mark is not found in the first storage space, and the example triggering request is not processed by other threads at present, starting the processing procedure of the example triggering request.

S205, inquiring a processing record set corresponding to the target hash mark in a second storage space, wherein the second storage space is used for persistently storing processing records for each request.

The embodiment of the application is not limited to the second storage space, in one embodiment MySQL may be used, and MySQL is a relational database management system, which belongs to one of the mainstream relational database management systems.

S206, responding to the condition that the processing record set represents that the request corresponding to the target hash mark is processed for preset times, sending the instance triggering request to the instance request management queue, and deleting the target hash mark in the first storage space.

The embodiment of the present application is not limited to the preset number of times, and for example, may be set to 3 times. If the processing has been performed 3 times, and further processing needs to be continued in this step, it is expected that the processing is difficult to be performed successfully this time, in this case, the instance trigger request may be directly sent to the instance request management queue, and the target hash identifier may be deleted in the first storage space. The instance triggering request is returned to the request management queue, and the instance triggering request can be used as a new instance triggering request to be reprocessed after a period of time passes based on the message interaction framework of the embodiment of the application.

S207, analyzing an instance triggering request pointed by the target hash mark in response to the condition that the number of times of processing the request corresponding to the target hash mark represented by the processing record set does not reach the preset number of times.

S208, performing instance service processing on the analysis result, wherein the instance service processing comprises the steps of generating instance parameters and sending the instance parameters to the access center.

S209, generating a processing record in the second storage space record, and deleting the target hash mark in the first storage space.

S210, responding to the situation that the instance service is successfully processed, and sending a response representing that the instance service is successfully processed to the application service manager.

S211, responding to the situation that the processing of the example service fails, and inquiring a processing record set corresponding to the target hash mark in a second storage space.

S212, responding to the condition that the processing record set represents that the request corresponding to the target hash mark is processed for preset times, sending the instance triggering request to the instance request management queue, and deleting the target hash mark in the first storage space.

S213, responding to the situation that the number of times of processing the request corresponding to the target hash mark represented by the processing record set does not reach the preset number of times, sending a response representing retrying the instance service processing to the application service manager, and returning to the step of carrying out the instance service processing on the analysis result.

Referring to fig. 6, a fourth schematic diagram of cloud application management is shown. Fig. 6 and 5 each represent an information processing flow of the shipping link, where the database and the MQ each represent MySQL as the second storage space, and the preset number of times is defined as 3 times. The delivery reliability guarantee can be achieved by the flow steps in fig. 5 and 6. In particular, instance trigger requests may be managed in a queue and fed back to the queue for processing next after a processing failure, by setting up multiple threads for message processing, and each thread sets up a mechanism to avoid duplicate processing. And in a specific processing link, carrying out hash operation so as to judge whether the current message is being processed, if not, carrying out message persistence operation, judging whether the message is processed for preset times, if not, carrying out service processing, feeding back a processing result after the service processing is finished, carrying out consumption deletion after success, and carrying out retry after failure, and throwing back to a queue again.

In the process of shipping, message interaction between an application access manager and an origin server (ISV service provider) is required, in order to ensure the reliability of the message interaction, in the embodiment of the application, in the process of application service input by the ISV service provider, the address of the origin server, namely a URL (Uniform Resource Locator ), and token information are carried in an application service input request, and the URL and the token information are recorded by a cloud application management server. In the delivery process, the application access manager carries the URL, and the timestamp information, the event identification information, the token information and the signature information required by the request delivery request to the origin server for verification, so that the delivery can be performed under the condition that the verification is successful.

Referring to fig. 7, a fifth schematic diagram of cloud application management is shown. Specifically, in the verification stage, the origin server may detect whether the time-out is performed based on the timestamp information, if not, perform dictionary reverse order ordering based on the token information, the timestamp information and the event identification information, encrypt according to the ordering result, compare with the signature information after encrypting, and pass the verification after comparing. By setting this verification policy, the reliability of the message interaction is ensured.

The embodiment of the application is particularly suitable for being used in a mixed cloud scene, the mixed cloud is fused with public cloud and private cloud, the main development mode and direction of cloud technology are divided from user groups, the public cloud is oriented to individuals and enterprises, the private cloud is mainly oriented to enterprises, particularly large enterprises are biased to the private cloud mode, and meanwhile, public cloud SaaS application resources are hoped to be obtained. The hybrid cloud platform is combined with the public cloud platform, and the characteristics of the public cloud are utilized, so that the enterprise can enjoy abundant public cloud resources including SaaS services, local features can be created, large enterprises can push out the enterprise to get cloud for digitized transformation of the enterprise, the traditional application fully hugs the cloud, and SaaS support is carried out.

Under the hybrid cloud mode, the SaaS application not only sources screening applications of public cloud markets, but also provides application and enterprise self-service application support for service providers in private cloud environments. Under the hybrid cloud mode, a user purchases the SaaS application through the hybrid cloud platform, does not need to perceive whether the commodity application sources public cloud market or private cloud market, only needs to purchase according to a standard purchase flow, and performs docking of different service providers through the hybrid cloud platform so as to realize SaaS shipping processing.

The cloud application management method provided by the embodiment of the application can automatically input the SaaS services provided by each ISV in various cloud environments, and intensively display the input SaaS services, and automatically trigger the establishment of a use link of the SaaS services under the condition that the requirement information for a certain SaaS service is acquired, so that the SaaS services can be directly consumed, that is, the cloud application management method provided by the embodiment of the application essentially provides an application store aiming at the SaaS services in the cloud environment, and provides a unified platform for inquiring, browsing, purchasing, using, ordering and other operations related to the SaaS services.

Referring to fig. 8, a block diagram of a cloud application management apparatus in the present embodiment is applied to a cloud application management server, where the apparatus includes: an application service manager 101, an application instance manager 102, and an application access manager 103;

the application service manager 101 is configured to generate a record corresponding to an application service in response to acquiring an application service entry request, where the application service entry request includes an address of a source server that is used to provide the application service, and feed back the record in response to acquiring an application display request sent by an application display end, so as to trigger the application display end to display the application service;

the application service manager 101 is further configured to generate an instance trigger request for the application service in response to receiving the requirement information for the application service from the application display end, and transmit the instance trigger request to the application instance manager;

the application instance manager 102 is configured to generate an instance parameter in response to the instance trigger request, and send the instance parameter to the application access manager;

the application access manager 103 is configured to transmit the instance parameter to an address of the origin server, so as to trigger the origin server to generate and deploy an instance according to the instance parameter.

In an embodiment, the application service entry request further includes an application service type, where the application service type includes a first type of application service type or a second type of application service type, and an application service corresponding to the first type of application service type is a homologous service of the cloud application management server, and an application service corresponding to the second type of application service type does not belong to the homologous service of the cloud application management server.

In one embodiment, the above apparatus is further configured to perform the following operations:

the application service manager generates an instance trigger request for the application service and sends the instance trigger request to an instance request management queue;

the application instance manager accesses the instance request management queue to obtain the instance trigger request;

the application access manager transmitting the instance parameters to the address of the origin server to trigger the origin server to generate and deploy the instance according to the instance parameters, comprising:

the application access manager invokes an asynchronous communication interface to send the instance parameters to the address of the source server to trigger the source server to asynchronously generate and deploy the instance based on the instance parameters;

Responding to the condition of obtaining a target address fed back by the asynchronous communication interface in preset time, and returning the target address as an example address to the application service manager so as to trigger the application service manager to respond the target address as the requirement information; wherein the target address is a deployment address of the instance generated by the origin server based on the instance parameter.

determining a target hash identifier corresponding to the instance triggering request;

inquiring the target hash identification in a first storage space, wherein the first storage space is used for storing hash identifications corresponding to all the currently processed requests;

and discarding the instance triggering request in response to the condition that the target hash identification is queried.

writing the target hash identification into the first storage space in response to the condition that the target hash identification is not queried;

inquiring a processing record set corresponding to the target hash mark in a second storage space, wherein the second storage space is used for persistently storing processing records for each request;

And responding to the condition that the processing record set characterizes that the request corresponding to the target hash mark is processed for a preset number of times, sending the instance triggering request to the instance request management queue, and deleting the target hash mark in the first storage space.

analyzing an instance triggering request pointed by the target hash mark in response to the condition that the number of times of processing the request corresponding to the target hash mark represented by the processing record set does not reach the preset number of times;

performing instance service processing on the analysis result, wherein the instance service processing comprises generating instance parameters and sending the instance parameters to the application access manager;

and generating a processing record in the second storage space record, and deleting the target hash mark in the first storage space.

responding to the situation that the example service is successfully processed, and sending a response representing that the example service is successfully processed to the application service manager;

responding to the case that the processing of the instance service fails, and inquiring a processing record set corresponding to the target hash mark in a second storage space;

Responding to the condition that the processing record set characterizes that the request corresponding to the target hash mark is processed for preset times, sending the instance triggering request to the instance request management queue, and deleting the target hash mark in the first storage space;

and responding to the situation that the number of times of processing the request corresponding to the target hash mark represented by the processing record set does not reach the preset number of times, sending a response representing retrying the instance business processing to the application service manager, and returning to the step of carrying out the instance business processing on the analysis result.

Further, fig. 9 shows a schematic hardware structure of an apparatus for implementing the method provided by the embodiment of the present application, where the apparatus may participate in forming or including the device or the system provided by the embodiment of the present application. As shown in fig. 9, the apparatus 10 may include one or more processors 102 (shown as 102a, 102b, … …,102 n) that may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, the method may further include: a display, an input/output interface (I/O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of the I/O interface), a network interface, a power supply, and/or a camera. It will be appreciated by those skilled in the art that the configuration shown in fig. 9 is merely illustrative and is not intended to limit the configuration of the electronic device. For example, the device 10 may also include more or fewer components than shown in fig. 9, or have a different configuration than shown in fig. 9.

It should be noted that the one or more processors 102 and/or other data processing circuits described above may be referred to generally herein as "data processing circuits. The data processing circuit may be embodied in whole or in part in software, hardware, firmware, or any other combination. Further, the data processing circuitry may be a single stand-alone processing module, or incorporated in whole or in part into any of the other elements in the device 10 (or mobile device). As referred to in embodiments of the application, the data processing circuit acts as a processor control (e.g., selection of the path of the variable resistor termination connected to the interface).

The memory 104 may be used to store software programs and modules of application software, such as program instructions/data storage devices corresponding to the above-mentioned methods in the embodiments of the present application, and the processor 102 executes the software programs and modules stored in the memory 104, thereby executing various functional applications and data processing, that is, implementing a cloud application management method as described above. Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, memory 104 may further include memory located remotely from processor 102, which may be connected to device 10 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission means 106 is arranged to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communications provider of device 10. In one example, the transmission device 106 includes a network adapter (NetworkInterfaceController, NIC) that can connect to other network devices through a base station to communicate with the internet. In one example, the transmission device 106 may be a radio frequency (RadioFrequency, RF) module for communicating wirelessly with the internet.

The display may be, for example, a touch screen type Liquid Crystal Display (LCD) that may enable a user to interact with the interface of the device 10 (or mobile device).

It should be noted that: the sequence of the embodiments of the present application is only for description, and does not represent the advantages and disadvantages of the embodiments. And the foregoing description has been directed to specific embodiments of this application. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

All the embodiments of the present application are described in a progressive manner, and identical and similar parts of all the embodiments are mutually referred to, and each embodiment mainly describes differences from other embodiments. In particular, for the device and server embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and references to the parts of the description of the method embodiments are only required.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The instructions in the storage medium may execute a cloud application management method applied to a cloud application management server, where the cloud application management server includes an application service manager, an application instance manager, and an application access manager, and the method includes:

in response to acquiring an application service entry request, the application service manager generates a record corresponding to an application service, wherein the application service entry request comprises an address of a source server for providing the application service;

in response to receiving the demand information for the application service from the application display end, the application service manager generates an instance trigger request for the application service and transmits the instance trigger request to the application instance manager;

the application instance manager generates instance parameters in response to the instance trigger request and sends the instance parameters to the application access manager;

In one embodiment, the application service manager generates an instance trigger request for the application service, and transmits the instance trigger request to the application instance manager, including:

In one embodiment, after the application instance manager accesses the instance request management queue to obtain the instance trigger request, the method further includes:

In one embodiment, after the processing of the instance service for the parsing result, the method further includes:

The foregoing description of the preferred embodiments of the present application is not intended to limit the embodiments of the present application, but is intended to cover all modifications, equivalents, improvements and alternatives falling within the spirit and principles of the embodiments of the present application.

Claims

1. A cloud application management method, applied to a cloud application management server, the cloud application management server including an application service manager, an application instance manager, and an application access manager, the method comprising:

2. The method of claim 1, wherein the application service entry request further includes an application service type, the application service type including a first type of application service type or a second type of application service type, the application service corresponding to the first type of application service type being a homologous service of the cloud application management server, the application service corresponding to the second type of application service type not being a homologous service of the cloud application management server.

3. The method of claim 1 or 2, wherein the application service manager generating an instance trigger request for the application service, transmitting the instance trigger request to the application instance manager, comprising:

the application access manager transmitting the instance parameters to an address of the origin server to trigger the origin server to generate and deploy the instance in accordance with the instance parameters, comprising:

the application access manager invokes an asynchronous communication interface to send the instance parameter to the address of the source server to trigger the source server to asynchronously generate and deploy the instance based on the instance parameter;

responding to the condition that a target address fed back by the asynchronous communication interface is acquired within preset time, and returning the target address as an example address to the application service manager so as to trigger the application service manager to respond the target address as the requirement information; wherein the target address is a deployment address of the instance generated by the origin server based on the instance parameter.

4. A method according to claim 3, wherein after the instance triggering request is obtained by the application instance manager accessing the instance request management queue, the method further comprises:

and discarding the instance triggering request in response to querying the target hash identification.

5. The method of claim 4, wherein after the instance triggering request is obtained by the application instance manager accessing the instance request management queue, the method further comprises:

and responding to the condition that the processing record set characterizes that the request corresponding to the target hash mark is processed for preset times, sending the instance triggering request to the instance request management queue, and deleting the target hash mark in the first storage space.

6. The method of claim 5, wherein after the instance triggering request is obtained by the application instance manager accessing the instance request management queue, the method further comprises:

generating a processing record in the second storage space record, and deleting the target hash identification in the first storage space.

7. The method of claim 6, wherein after the instance business processing is performed on the parsing result, the method further comprises:

responding to the situation that the instance service is successfully processed, and sending a response representing that the instance service is successfully processed to the application service manager;

responding to the case that the instance service processing fails, and inquiring a processing record set corresponding to the target hash mark in a second storage space;

8. A cloud application management apparatus, applied to a cloud application management server, the apparatus comprising: an application service manager, an application instance manager, and an application access manager;

9. A computer readable storage medium having stored therein at least one instruction or at least one program loaded and executed by a processor to implement a cloud application management method according to any of claims 1 to 7.

10. An electronic device comprising at least one processor, and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the at least one processor implementing a cloud application management method according to any of claims 1 to 7 by executing the instructions stored by the memory.

11. A computer program product comprising a computer program or instructions which, when executed by a processor, implements a cloud application management method as claimed in any of claims 1 to 7.