CN116302174A

CN116302174A - Plug-in management method and device based on cloud application

Info

Publication number: CN116302174A
Application number: CN202310130168.3A
Authority: CN
Inventors: 陈坚; 付志超
Original assignee: Alibaba China Co Ltd
Current assignee: Alibaba China Co Ltd
Priority date: 2023-02-03
Filing date: 2023-02-03
Publication date: 2023-06-23

Abstract

The embodiment of the application provides a plug-in management method and device based on cloud application, wherein the method comprises the following steps: and creating an application image file according to the image creation request, wherein the application image file comprises an application identifier of at least one target application and a plug-in identifier of at least one target plug-in. And creating a virtual machine instance according to a delivery request aiming at the application image file, wherein the delivery request is used for requesting to allocate the target application and the target plugin to at least one target object, and the virtual machine instance is used for running the target application and the target plugin. And according to the application image file, mounting an application file corresponding to the target application stored in the storage unit and a plug-in file corresponding to the target plug-in the virtual machine instance. According to the technical scheme, the complexity of adjusting the cloud application and the plug-in thereof can be effectively reduced.

Description

Plug-in management method and device based on cloud application

Technical Field

The embodiment of the application relates to computer technology, in particular to a plug-in management method and device based on cloud application.

Background

The cloud application changes the use mode of the original traditional software which is required to be installed and operated locally into the service of 'taking and using immediately', and can connect and control a remote server cluster through the Internet or a local area network to complete business logic or operation tasks.

Many applications are served by adding plug-ins to the base software, where plug-ins can optimize the operation of the application and improve efficiency, and cloud applications are no exception. Currently, when providing a cloud application to a user, basic software and plug-ins of the application are usually downloaded and installed in advance in a virtual machine, and then the installed virtual mechanism is used as an image file for the user to use the cloud application.

However, when the plug-in or the application needs to be adjusted, the implementation described above often needs to be mirrored again, which results in a complicated operation of adjusting the plug-in and the application.

Disclosure of Invention

The embodiment of the application provides a plug-in management method and device based on cloud application, which are used for solving the problem that plug-ins are adjusted in the cloud application and the operation of the application is complex.

In a first aspect, an embodiment of the present application provides a plug-in management method based on cloud application, including:

creating an application image file according to an image creation request, wherein the application image file comprises an application identifier of at least one target application and a plug-in identifier of at least one target plug-in;

creating a virtual machine instance according to a delivery request for the application image file, wherein the delivery request is used for requesting to allocate the target application and the target plugin to at least one target object, and the virtual machine instance is used for running the target application and the target plugin;

And according to the application image file, mounting an application file corresponding to the target application and a plug-in file corresponding to the target plug-in the storage unit in the virtual machine instance.

In a second aspect, an embodiment of the present application provides a plug-in management device based on a cloud application, including:

the system comprises a creation module, a storage module and a storage module, wherein the creation module is used for creating an application image file according to an image creation request, and the application image file comprises an application identifier of at least one target application and a plug-in identifier of at least one target plug-in;

the creation module is further configured to create a virtual machine instance according to a delivery request for the application image file, where the delivery request is used to request allocation of the target application and the target plugin to at least one target object, and the virtual machine instance is used to run the target application and the target plugin;

and the receiving and transmitting module is used for mounting the application file corresponding to the target application and the plug-in file corresponding to the target plug-in the virtual machine instance, which are stored in the storage unit, according to the application image file.

In a third aspect, an embodiment of the present application provides an electronic device, including:

A memory for storing a program;

a processor for executing the program stored by the memory, the processor being adapted to perform the method of the first aspect and any of the various possible designs of the first aspect as described above when the program is executed.

In a fourth aspect, embodiments of the present application provide a computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform the method of the first aspect above and any of the various possible designs of the first aspect.

In a fifth aspect, embodiments of the present application provide a computer program product comprising a computer program which, when executed by a processor, implements a method as described in the first aspect and any of the various possible designs of the first aspect.

The embodiment of the application provides a plug-in management method and device based on cloud application, wherein the method comprises the following steps: and creating an application image file according to the image creation request, wherein the application image file comprises an application identifier of at least one target application and a plug-in identifier of at least one target plug-in. And creating a virtual machine instance according to a delivery request aiming at the application image file, wherein the delivery request is used for requesting to allocate the target application and the target plugin to at least one target object, and the virtual machine instance is used for running the target application and the target plugin. And according to the application image file, mounting an application file corresponding to the target application stored in the storage unit and a plug-in file corresponding to the target plug-in the virtual machine instance. When receiving the image creation request, only creating an application image file comprising an application identifier and a plug-in identifier, and then mounting an application file corresponding to a target application and a plug-in file corresponding to a target plug-in a virtual machine instance according to the application image file, so that when the basic software and plug-in of the cloud application are adjusted, the file mounting relationship can be simply changed, and a series of complex operations such as downloading, installing, and re-manufacturing the image file are not required, and the complexity of adjusting the cloud application and the plug-in thereof can be effectively reduced.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief description will be given below of the drawings that are needed in the embodiments or the prior art descriptions, it being obvious that the drawings in the following description are some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art.

Fig. 1 is a schematic view of a scenario of a cloud application and a plug-in management method provided in an embodiment of the present application;

FIG. 2 is a schematic diagram of an implementation of reproducing an image file according to an embodiment of the present application;

fig. 3 is a flowchart of a cloud application-based plug-in management method according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a configuration interface of an application and a plug-in provided in an embodiment of the present application;

fig. 5 is a second flowchart of a cloud application-based plug-in management method provided in an embodiment of the present application;

fig. 6 is a system schematic diagram of a file cloud service platform provided in an example of the present application;

FIG. 7 is a processing timing diagram of a configuration plug-in and an application provided in an embodiment of the present application;

FIG. 8 is a process timing diagram of an adjustment plug-in and application provided in an embodiment of the present application;

Fig. 9 is a flowchart III of a cloud application-based plug-in management method provided in an embodiment of the present application;

fig. 10 is a schematic structural diagram of a plug-in management device based on cloud application according to an embodiment of the present application;

fig. 11 is a schematic hardware structure of an electronic device according to an embodiment of the present application.

Detailed Description

For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are 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 based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

For a better understanding of the technical solutions of the present application, the related concepts and terms referred to in the present application are explained first below.

Application mirroring: refers to a logical image containing a series of applications and plug-ins that can be located to vhd files on NAS (Network Attached Storage ) storage based on application and plug-in information.

Application example: in particular, after a certain software is manufactured into a vhd file, the vhd file is mounted on an instance in a cloud server, and the software runs on the cloud and is provided for a user to use.

Delivery group: delivering logical groupings of cloud applications to end users, including underlying dependent cloud application resources, images containing cloud applications, resource management policies, and user allocation settings, among others.

The application package comprises: each application package is a separate vhd file, which contains the application files, registry files and auxiliary files, and is directly installed to the system during running.

For better understanding of the technical solutions of the present application, the related art related to the present application is described in further detail below.

The cloud application changes the use mode of the original traditional software which is required to be installed and operated locally into the service of 'instant use', and the remote server cluster can be connected and controlled through the Internet or a local area network to complete business logic or operation tasks, thereby helping enterprises to greatly reduce the use cost and improving the working efficiency.

For example, the cloud application may be understood with reference to fig. 1, and fig. 1 is a schematic view of a scenario of the cloud application and a plug-in management method provided in an embodiment of the present application.

As shown in fig. 1, a user may access a cloud end through a terminal device, and the cloud end may provide relevant services of a cloud application for the terminal device, where a desktop of the terminal device may be understood as a cloud desktop.

In the example shown in fig. 1, there are an application a, an application B and an application C on the desktop of the terminal device, for example, the three applications are all cloud applications, so that the user does not need to install the applications in the terminal device, but accesses the cloud through the network, and the cloud provides the terminal device with corresponding processes of the applications, so as to implement the cloud application service that is ready to use in the terminal device.

Many popular applications are currently served by adding plug-ins to the base software, which can provide the base services of the application, and plug-ins can support additional services and operations on top of the base services of the application. Wherein Plug-in is a program written by an application program interface conforming to a certain specification. It can only run under the system platform specified by the program (possibly supporting multiple platforms at the same time), but can not run independently from the specified platform, many software have plug-ins, and the types of plug-ins are very large.

The plug-in can be understood as auxiliary software of the application program to optimize the operation of the application program and improve the operation efficiency, and if only the basic software of the application program is used, the plug-in is not installed, the experience of many application programs is greatly reduced.

In the related art, when plug-in management is performed, required applications and plug-ins are usually downloaded and installed in advance in virtual machine instances created in a cloud, and the virtual machine instances with the applications and plug-ins installed are manufactured as image files so as to provide cloud application services for users.

The virtual machine instance is briefly described herein, and the instance herein may be understood as a cloud server instance, where a cloud server instance may be equivalent to a virtual machine. Examples can include vCPU (virtual central processing unit, virtual processor), memory, operating system, network, disk, etc., and virtual machine examples can be understood as a complete and available computer (virtual) which can be conveniently customized and changed in configuration. Virtual machine instances are the smallest units that can provide computing servers for a service, and different instance specifications can provide different computing power.

The above-described process of installing base software and plug-ins in a virtual machine instance and making the installed virtual machine instance into an image file to provide a cloud application, where it is very difficult to add plug-ins or upgrade plug-ins, for example, as can be understood with reference to fig. 2, and fig. 2 is a schematic diagram of an implementation of reproducing the image file provided in the embodiment of the present application.

As shown in fig. 2, assuming that the current user needs to use application a and 1.0 version of plugin α corresponding to application a in the terminal device, the cloud end creates a cloud server instance for the requirement, for example, and installs application a and 1.0 version of plugin α in the virtual machine instance. The cloud end can then make an instance of the plugin α including the application a and version 1.0 as an image file, and issue the application to the terminal device, thereby providing the terminal device with a corresponding service.

But then, say that the user no longer needs the 1.0 version of the plugin α, but needs the 2.0 version of the plugin α, the cloud needs to install the 2.0 version of the plugin α in the virtual machine instance, and make the virtual machine instance including the plugin α of the application a and the 2.0 version into an image file again, and then issue the application to the terminal device, so as to provide corresponding services for the terminal device.

It can be determined based on the above description that in the current implementation, any update to the plugin, such as updating the plugin version, or requiring a new plugin, etc., needs to recreate the image file and reissue the application, which results in a very complex implementation process for adjusting the plugin.

Aiming at the problems in the prior art, the application provides the following technical conception: the current adjustment for the plug-in and the application is complicated because the implementation manner of installing the plug-in and the application in the virtual machine instance and then manufacturing the image file is adopted, so that the plug-in and the application are included in the image file, and the adjustment is required for the plug-in and the application, so that the image file is naturally required to be manufactured again. If the plug-in and the application files can be placed in a storage unit, and then the corresponding functions are provided by mounting the related application files and the plug-in files in the storage unit, the application and the plug-in can be prevented from being directly included in the mirror image files, and after the plug-in and the application are required to be adjusted, only the mounting relation is required to be adjusted, so that dynamic update and real-time adjustment of the plug-in can be realized, mirror images and cloud applications do not need to be manufactured again, and further the management complexity of the plug-in and the application is effectively reduced.

Based on the above description, the plug-in management method based on cloud application provided in the present application is described in detail below with reference to specific embodiments. The embodiments in the application can be applied to a cloud service platform, wherein a hardware execution body corresponding to the cloud service platform can be, for example, a cloud server, a processor, a chip and other devices, and the embodiment does not limit a specific execution body as long as the hardware execution body is a cloud device with a data processing function.

The following description will be first made with reference to fig. 3 and fig. 4, where fig. 3 is a flowchart of a cloud application-based plug-in management method provided in an embodiment of the present application, and fig. 4 is a schematic configuration interface of an application and a plug-in provided in an embodiment of the present application. As shown in fig. 3, the method includes:

s301, creating an application image file according to an image creation request, wherein the application image file comprises an application identifier of at least one target application and a plug-in identifier of at least one target plug-in.

For example, the cloud service platform may receive a request for creating an image from the terminal device, and in one possible implementation manner, when the cloud service platform is required to provide a service of the cloud application, for example, a tenant administrator may perform configuration of the cloud application through the terminal device, and then directly push the configured cloud application related data to a cloud desktop of the target user. Where the tenant administrator may be, for example, a network administrator within the enterprise, and the target user to which the cloud application is pushed may be an employee within the enterprise. Or the tenant administrator may also be an individual user, and the target user of the pushed cloud application may also be the individual user himself.

Therefore, the image creation request in this embodiment may be sent by any person needing to configure the cloud application through any terminal device, or in an alternative implementation manner, the generation manner and the source of the image creation request may be selected and set according to the actual requirement, so long as the image creation request is used for requesting to generate the application image file. The image creation request may include an application identifier of an application to be configured and a plug-in identifier of a plug-in.

For example, as can be appreciated with reference to fig. 4, a currently configurable application and a configurable plug-in may be presented at the configuration interface as shown in fig. 4. For example, in the example of FIG. 4, it is shown that the current configurable applications include application A and application B, and that the configurable plug-ins include a 1.0 version of plug-in α for application A, a 2.0 version of plug-in α for application A, plug-in β for application A, and so on.

The configurator may then select from the configuration interface, for example, to determine the target application and the target plug-in. After determining the selection, for example, the submit control of the configuration interface may be operated to generate the image creation request. For example, when the current configurator needs to configure application a and version 1.0 of plugin α of application a for certain objects, the configurator may operate through the interface to generate an image creation request, and the image creation request may include an identification of application a and an identification of version 1.0 of plugin α. In the actual implementation process, the specific implementation mode of the configuration interface can be selected and set according to actual requirements.

The cloud end can then create an application image file according to the image creation request, and the application image file can include the application identifier of the at least one application and the plug-in identifier of the at least one target plug-in. The image file described in this embodiment is a logical concept existing in the database, and there is no entity file, so the application image file may also be directly referred to as an application image.

For example, continuing the example introduced above, the cloud creates an application image file in response to the image creation request, and may include an identification of application a and an identification of version 1.0 of plug-in α in the application image file.

It should be noted here that some applications are plug-in-presence, while some applications are plug-in-absence. For applications where no plug-ins exist, the tenant administrator may configure only this single application, and thus may also include only the application identification of the at least one target application in the application image file. For applications where plug-ins exist, the tenant administrator may configure the applications and plug-ins according to the implementation described above, or may configure only individual applications (i.e. where plug-ins exist but not configured), so that the application image file may also only include the application identifier of at least one target application.

It will be appreciated that the application identity of the target application will necessarily be included in the application image file, but whether or not the plug-in identity of the target plug-in will be included depends on the actual needs of the user. Thus there are two cases of application image files: the application image file may include an application identifier of at least one target application and a plug-in identifier of at least one target plug-in, or the application image file may also include only an application identifier of at least one target application.

In the actual implementation process, the specific implementation of the application identifier and the plug-in identifier included in the application image file can be selected and set according to actual requirements, which depend on which cloud applications and corresponding plug-ins are specifically required to be configured for the corresponding objects by an operation configurator.

S302, creating a virtual machine instance according to a delivery request aiming at an application image file, wherein the delivery request is used for requesting to distribute a target application and a target plug-in to at least one target object, and the virtual machine instance is used for running the target application and the target plug-in.

After the cloud creates the application image file, the cloud may obtain a delivery request for the application image file, where the delivery request may be sent by a configurator through a terminal device, and the delivery request is used to request to allocate the target application and the target plug-in described above to at least one target object.

In one possible implementation, the target object may be, for example, a user account, that is, when the configurator configures the cloud application, the configurator allocates the target object to the user account, and then the terminal device logged in with the user account may run the corresponding application and plug-in. Or, the target object may also be a user device, that is, a configurator may allocate the target object to the device when configuring the cloud application, and then the allocated user device may run the corresponding application and plug-in. In the actual implementation process, the specific implementation manner of the target object can be selected and set according to actual requirements, which depends on the manner in which the cloud application is delivered and configured.

In one possible implementation manner, the running of the target application and the target plugin in the terminal device is required to be completed by means of the virtual machine instance in the cloud, so after the cloud in the embodiment receives the delivery request, the virtual machine instance can be created, so that after the target application and the target plugin are allocated to the target object, the device corresponding to the target object can run the corresponding target application and the target plugin through the virtual machine instance.

S303, according to the application image file, an application file corresponding to the target application and a plug-in file corresponding to the target plug-in are mounted in the virtual machine instance.

Based on the above description, it can be determined that the created application image file only includes the application identifier of the target application and the plug-in identifier of the target plug-in, but no actual application file and plug-in file are involved, and when the target application and the target plug-in are run through the virtual machine instance, the actual file is required to be used for data support.

In one possible implementation manner, the storage unit in this embodiment stores application files of each configurable application and plug-in files of each configurable plug-in, and the cloud may mount, according to the application image file, an application file corresponding to a target application stored in the storage unit and a plug-in file corresponding to the target plug-in the virtual machine instance.

Where mount (mount) refers to a process by which computer files and directories on a storage unit are made available to users for access through the computer's file system by the operating system. In this embodiment, the application file corresponding to the target application is installed in the virtual machine instance, which is equivalent to the application file in the remote access storage unit, and the plug-in file of the target plug-in is similar.

It can be understood that after the application file corresponding to the target application and the plug-in file corresponding to the target plug-in are installed in the virtual machine instance, the terminal device needing to run the cloud application can access the application file corresponding to the target application and the plug-in file corresponding to the target plug-in through the virtual machine instance, so that the target application and the target plug-in are run in the terminal device needing to run the cloud application, and service provision of basic software and plug-in of the cloud application is realized.

Meanwhile, because the image file in the embodiment only includes the application identifier and the plugin identifier, the data support of the specific application and plugin is provided by the file mounted by the virtual machine instance, so that when the plugin or the application needs to be updated, only the mounting relationship between the virtual machine instance and the corresponding file in the storage unit needs to be updated, and the complex operation of re-downloading and mounting and then re-making the image file is not required.

The cloud application-based plug-in management method comprises the steps of creating an application image file according to an image creation request sent by first terminal equipment and the image creation request, wherein the application image file comprises an application identifier of at least one target application and a plug-in identifier of at least one target plug-in. And creating a virtual machine instance according to a delivery request aiming at the application image file, wherein the delivery request is used for requesting to allocate the target application and the target plugin to at least one target object, and the virtual machine instance is used for running the target application and the target plugin. And according to the application image file, mounting an application file corresponding to the target application stored in the storage unit and a plug-in file corresponding to the target plug-in the virtual machine instance. When receiving the image creation request, only creating an application image file comprising an application identifier and a plug-in identifier, and then mounting an application file corresponding to a target application and a plug-in file corresponding to a target plug-in a virtual machine instance according to the application image file, so that when the basic software and plug-in of the cloud application are adjusted, the file mounting relationship can be simply changed, and a series of complex operations such as downloading, installing, and re-manufacturing the image file are not required, and the complexity of adjusting the cloud application and the plug-in thereof can be effectively reduced.

Based on the above description, a plurality of processing units may be included in the cloud service platform, where each processing unit performs a different function, and the plug-in management method based on cloud application provided in the present application is further described below with reference to fig. 5 to 6, starting from the respective function of each unit. Fig. 5 is a second flowchart of a cloud application-based plug-in management method provided in an embodiment of the present application, and fig. 6 is a system schematic diagram of a file cloud service platform provided in an example of the present application.

As shown in fig. 5, the method includes:

s501, the management and control unit creates an application image file according to the image creation request, wherein the application image file comprises an application identifier of at least one target application and a plug-in identifier of at least one target plug-in.

The cloud service platform comprises a management and control unit, wherein the management and control unit can complete a series of cloud application management and control works, for example, an image file is created according to corresponding configuration information, and a specific delivery mode is determined according to delivery information configured by configuration personnel, wherein the delivery mode is configured by the management and control unit, for example, the cloud application and plug-in configuration which are specifically indicated to which objects, the specific configuration duration and the like can be processed by the management and control unit.

In this embodiment, the management and control unit may receive the image creation request, and the management and control unit may create the application image file according to the image creation request, and the specific implementation may refer to the description of the foregoing embodiment, which is not repeated herein.

S502, the management and control unit receives the delivery request.

After the administration unit creates the application image file, the administration unit may further receive a delivery request, which may be sent, for example, by a terminal device operated by a configuration person.

S503, the management and control unit responds to the delivery request and sends an instance processing request to the instance unit.

In response to the delivery request, the cloud needs to allocate the target application and the target plug-in to the at least one target object, which needs to be completed by the virtual machine instance, so that the management control unit may send an instance processing request to the instance unit in response to the delivery request, where the instance processing request is used to request the instance unit to create a corresponding virtual machine instance.

The instance unit in this embodiment is used to perform processing operations of the instance, such as creation of the instance, destruction of the instance, management of the instance, and so on.

S504, the instance unit responds to the instance processing request to create a virtual machine instance.

The instance unit may be configured to create virtual machine instances in response to the instance processing request sent by the management and control unit, where the number of virtual machine instances may be one or multiple, depending on the specific situation where the cloud application and the target object of the plug-in are configured.

S505, the instance unit sends notification information indicating that instance creation is successful to the management and control unit.

After the instance unit creates the target instance, notification information may be sent to the management and control unit, the notification information indicating that the virtual machine instance creation was successful.

S506, the management and control unit sends mounting information to the proxy unit of the virtual machine instance according to the application image file, wherein the mounting information comprises an application identifier of the target application and a plug-in identifier of the target plug-in.

In the virtual machine instance, there is a proxy unit for implementing processing work of mounting a file, and the proxy unit may be, for example, a proxy unit (agent) running in an operating system (gueastos) of the virtual machine.

Therefore, after the management and control unit determines that the virtual machine instance is successfully created, the management and control unit can send mounting information to the proxy unit of the virtual machine instance according to the application image file, wherein the mounting information comprises the application identifier of the target application and the plug-in identifier of the target plug-in.

S507, the agent unit mounts application files corresponding to the target application and plug-in files corresponding to the target plug-in the virtual machine instance according to the application identifier and the plug-in identifier in the mounting information.

After receiving the mounting information, the proxy unit in the virtual machine instance can perform corresponding file mounting processing according to the application identifier and the plug-in identifier in the mounting information, that is to say, the application file corresponding to the target application and the plug-in file corresponding to the target plug-in are mounted in the virtual machine instance.

In one possible implementation, after the cloud processing completes the mount request, the cloud may also create an application instance, for example, to determine whether the current file mount may be operating normally. For example, the management and control unit may send a creation instruction to the proxy unit, and the proxy unit may create the application instance corresponding to the target application and the target plug-in described above according to the creation instruction. Wherein creating the application instance may be performed by the proxy unit creating a session in the virtual machine instance, one session corresponding to the virtual machine instance connected to one terminal device to use the cloud application, and one session may include a plurality of application instances, for example, one session opens the application a and the application b at the same time, it may be understood that the session includes two application instances.

It will be appreciated that if the creation of the application instance is successful, it may be determined that the session can be successfully created, meaning that the file mount may be operating normally, or may be considered to be successful in launching the application instance. Therefore, when the application instance is successfully created, the management and control unit can update the delivery state corresponding to the delivery request to complete the delivery processing. At this time, the target object is pushed with the corresponding cloud application and the corresponding plug-in, and then the target object can run the target application and the target plug-in through the virtual machine instance.

For example, the implementation procedure described in the current embodiment may be further understood with reference to fig. 6, where, as shown in fig. 6, a file directory is stored in the storage unit for each tenant, and relevant files uploaded by the tenant are included in the file directory.

It can be understood that the cloud service platform is only a platform for implementing cloud application service, specific application data is still uploaded by configuration personnel, so that each tenant (i.e. configuration personnel) can upload application files and plug-in files required by itself to the cloud service platform, and then the cloud service platform can store the files uploaded by the tenants in the storage unit, and the files uploaded by each tenant are separately and correspondingly stored, so that relevant services of cloud application can be provided for the corresponding tenants later.

In one possible implementation manner, the application file and the add-on file directly uploaded by the tenant may not support remote mounting, so further format conversion is required for the file uploaded by the tenant in this embodiment, so as to ensure that the converted file can support remote mounting, and then store the file in the storage unit,

for example, before sending a mounting request to the storage unit according to the application image file, the cloud service platform may receive a first initial file of the target application through the management and control unit, convert the first initial file into an application file in the target format, and store the application file in the storage unit; and the cloud service platform can receive the second initial file of the target plug-in through the management and control unit, convert the second initial file into the plug-in file in the target format, and store the plug-in file in the storage unit.

The target format may be vhd (Virtual Hard Disk ) format, wherein the file in vhd is a virtual disk format file, and the file in vhd format may be virtualized to a hard disk. vhd files support remote mount, vhd files on Nas can be portable and remotely mounted to the local. Or in the actual implementation process, the specific implementation of the target format can be selected and set according to the actual requirement, so long as the file of the target format can support remote mounting.

For example, as will be understood with reference to fig. 6, in the file directory of tenant 1, there are stored an application file of application 1, a plug-in file of plug-in 1 of application 1, a plug-in file of plug-in 2 of application 1, a plug-in file of plug-in 3 of application 1, a plug-in file of plug-in 4 of application 1, an application file of application 2, a plug-in file of plug-in 1 of application 2, a plug-in file of plug-in 2 of application 2, and a plug-in file of plug-in 3 of application 2, which are all uploaded by tenant 1 by itself and are subjected to format conversion, and are stored under the file directory of tenant 1 in the storage unit.

And referring to fig. 6, there is also a file directory of tenant 2 in the storage unit, and in the file directory of tenant 2, there are stored an application file of application 3, a plug-in file of plug-in 1 of application 3, a plug-in file of plug-in 2 of application 3, and a plug-in file of plug-in 3 of application 3, which are uploaded by tenant 2 by itself and are subjected to format conversion, and are stored under the file directory of tenant 2 in the storage unit.

In the embodiment, the corresponding relation between the application and the plug-in is maintained in the cloud service platform, and the application and the plug-in are converted into a mountable format, so that the application and the plug-in can be accessed in a mounting mode, and a large number of mirror image files are not required to be maintained.

Assuming later that tenant 1 is to provision a plurality of target objects (say user 1, user 2, user 3, and user 4 shown in fig. 6) with related cloud applications, tenant 1 may first query the currently configurable applications and plug-ins, i.e., applications and plug-ins that tenant 1 has previously uploaded itself, and assuming that tenant 1 is to provision application 1, plug-in 1 of application 1, plug-in 2 of application 1, and plug-in 4 of application 1, and plug-in 2 of application 2, plug-in 1 of application 2, and plug-in 2 of application 1, tenant 1 may initiate a mirror creation request via a terminal device.

With reference to the description of the above embodiment, the cloud service platform may create an application image file, and create a virtual machine instance according to a delivery request initiated by the first terminal device. In fig. 6, for example, it can be appreciated that a virtual machine instance is created in the instance unit.

The management and control unit may then send the mount information to the proxy unit of the virtual machine instance according to the application image file, where the proxy unit of the virtual machine instance runs on the operating system of the unit, and then the proxy unit may send the mount request to the storage unit, and then the file mount may be understood with reference to fig. 6, where the virtual machine instance may be mounted with the application file of the application 1, the plug-in file of the plug-in 2 of the application 1, the plug-in file of the plug-in 4 of the application 1, the application file of the application 2, the plug-in file of the plug-in 1 of the application 2, and the plug-in file of the plug-in 2 of the application 2. After the corresponding files are mounted in the virtual machine instance, the user 1 and the user 2 can run the appointed application and plugins on the terminal equipment of the user through the corresponding virtual machine instance.

As shown in fig. 6, assuming that the current user 1 needs to start the application 1 on its own terminal device, the proxy unit of the virtual machine instance may create a corresponding session according to the user request, where the session may include, for example, the application instance of the user 1 shown in fig. 6 corresponding to the application 1. For another example, assuming that the current user 2 needs to start the application 1 on its own terminal device, the proxy unit of the virtual machine instance may create a corresponding session according to the user request, where the session may include, for example, the application instance of the user 2 corresponding to the application 1 shown in fig. 6. User 3 shown in fig. 6 corresponds to an application instance of application 2 and user 4 corresponds to an application instance of application 2, in a similar manner.

Based on the above description, in the cloud application-based plug-in management method provided by the embodiment of the present application, a tenant may upload an initial file of an application and a plug-in to a cloud service platform in advance, and the cloud service platform may convert the initial file into an application file and a plug-in file in a target format and store the application file and the plug-in file in a storage unit, so as to ensure that a virtual machine instance may mount a file from the storage unit later, thereby providing a data base for the mounting. The management and control unit, the instance unit and the storage unit in the cloud service unit can interact with each other, so that target applications and target plugins indicated by application image files are mounted through the created virtual machine instance, the target applications and target plugins can be normally operated through the virtual machine instance, and meanwhile, only application identifiers and plugin identifiers are stored in the application image files, so that when the plugins and the application are updated, only the file mounting relationship is required to be adjusted, the image files do not need to be manufactured again, and the adjustment complexity of the cloud applications and the plugins can be effectively reduced.

Based on the above description, for example, the above description of the timing procedure may be further described with reference to fig. 7, in which fig. 7 further describes operations on the user side and related detailed information, and fig. 7 is a processing timing diagram of the configuration plug-in and the application provided in the embodiment of the present application.

As shown in fig. 7, the specific processing procedure includes:

1. the tenant operates a foreground interface through the first terminal equipment, and sends a query request for calling a query list to the browser, wherein the query request is used for querying the current configurable application and the plug-in;

2. the browser sends a query request to the management and control unit of the cloud service platform, and the query request has the same function.

3. And the control unit returns the configurable application information and the plug-in information to the browser.

The application information may include, for example, an identification of the application, a version of the application, a developer of the application, a size of the application, and the like, and the plug-in information is similar, and specific application information and a specific implementation of the plug-in information may be determined according to actual situations.

4. And the browser returns an application information page to the tenant foreground, wherein the application information page comprises the current configurable application information and plug-in information.

5. The tenant foreground selects the application and plug-in to be configured in the application information page, so as to send the image creation information to the browser, and the image creation information can include the application identifier and the plug-in identifier to be configured.

6. The browser sends a mirror creation request to the management and control unit.

7. And the management and control unit creates an application image file according to the image creation request.

8. The control unit returns information of successful creation to the browser.

9. The browser displays relevant information of successful image creation to the tenant foreground.

10. The tenant operates in the foreground interface, creates a delivery group, and selects a previously created image for distribution to the corresponding user.

The delivery group created by the tenant indicates which image file to assign to which user's devices, how long to assign, etc., so the tenant may send delivery information to the browser via the foreground interface, which may include the image file, user device, duration, etc. described above.

11. And the browser sends a delivery request to the management and control unit, wherein the delivery request requests the cloud service platform to execute corresponding delivery actions according to the delivery information.

12. The administration unit saves the delivery information and may initiate a workflow to create the delivery group.

13. And the control unit returns information to the browser to indicate the workflow to start.

14. The browser returns information to the tenant foreground indicating that the workflow is started, at which point the tenant can see that the delivery group is being created.

15. The management and control unit responds to the delivery information and sends an instance creation request to the instance unit.

16. The instance unit may first return an Identification (ID) of the virtual machine instance.

17. The control unit waits for the instance unit to successfully create the virtual machine instance.

18. The instance unit returns information of successful creation to the management and control unit.

19. The management and control unit sends the mounting information to the proxy unit.

20. The agent unit sends a mounting request to the storage unit, and corresponding application files and plug-in files are mounted in the virtual machine instance.

21. The agent unit returns the information of the completion of the mounting process to the management and control unit.

22. The management and control unit instructs the proxy unit to start the application instance.

23. The proxy unit indicates that the virtual machine instance is started successfully.

24. The management and control unit updates the state of the delivery group to be successful in creation, and feeds back the successful creation of the delivery group to the tenant platform through a browser.

The embodiment of the application describes the operations of each party and the interactions among each unit in the plug-in management method in detail.

Based on the above description, the implementation manner of the case where an application update or a plug-in update occurs after the delivery request processing is completed will be described in further detail. Fig. 8 is a process timing diagram of an adjustment plug-in and an application according to an embodiment of the present application.

As shown in fig. 8, the specific processing procedure includes:

1. the tenant operates the foreground interface, thereby editing the image file.

For example, the tenant may operate in a foreground interface, thereby indicating the newly added applications and plug-ins in the application image file, and the applications and plug-ins that need to be deleted in the application image file.

2. The browser sends a mirror modification request to the management and control unit, wherein the mirror modification request is used for requesting updating of the application mirror file.

Wherein the mirrored modification request may include at least one of:

the first case, the image modification request is used to request deletion of the plug-in identifier of the first plug-in the application image file.

The second case, the image modification request is used to request to add the plug-in identifier of the second plug-in to the application image file.

And in the third case, the mirror image modification request is used for requesting to delete the application identifier of the first application and the plug-in identifier under the first application in the application mirror image file.

And in the fourth case, the image modification request is used for requesting to add the application identifier of the second application in the application image file.

3. The management and control unit responds to the mirror image modification request to update the application mirror image file.

Because only simple updating identification information is in the application image file, which is a modification operation of the database class, and complicated downloading and installing operations are not needed, the application image file can be directly updated without being re-manufactured.

4. And the control unit returns the indication information of successful updating to the browser.

5. And the browser displays successful updating of the image file on the interface of the tenant foreground.

6. The management and control unit sends updated mounting information to the proxy unit, wherein the updated mounting information (may also be referred to as update information) corresponds to different implementations for the four cases described above.

For case one (uninstall the first plug-in) described above, the update information may include a plug-in identification of the first plug-in. For case two (newly added second plugin) described above, the update information may include the plugin identification of the second plugin. For case three (uninstall the first application) described above, the update information may include an application identification of the first application. For case four (newly added second application) described above, the update information may include an application identifier of the first application.

7. The agent unit processes file mounting or file unloading according to the mounting information.

Similarly, for the four cases described above, the proxy unit corresponds to a different implementation. For the first case described above (unloading the first plugin), the proxy unit may unload, according to the plugin identifier of the first plugin, the mount of the plugin file of the virtual machine instance for the first plugin.

For the second case (the second plugin is newly added), the proxy unit may mount the plugin file of the second plugin in the virtual machine instance according to the plugin identifier of the second plugin.

For the third case (first application is unloaded) described above, when the first application is unloaded, in addition to the need of unloading the mounting relationship of the first application itself, the plug-in file having the mounting relationship under the first application needs to be unloaded, so the proxy unit may unload, according to the application identifier of the first application, the mounting of the application file of the virtual machine instance for the first application, and the mounting of the plug-in file for the virtual machine instance for the first application, where "the plug-in file for the first application" refers to the plug-in file having the mounting relationship with the virtual machine instance in the corresponding at least one plug-in file of the first application.

For the fourth case (newly adding the second application) described above, the proxy unit may mount, in the virtual machine instance, an application file of the second application according to an application identifier of the second application.

8. And the agent unit returns the information of the completion of the update of the mounting relationship to the management and control unit.

9. The management and control unit instructs the proxy unit to start the application instance.

10. The proxy element indicates that the application instance started successfully. So far, the corresponding updating of the application and the plug-in can be realized.

In one possible implementation manner, when the user finishes using the cloud application, the cloud application can be directly closed, related files can be directly unloaded from the cloud resource, and the related files are distributed again when the related files are required next time, and the operations described above are repeatedly executed.

According to the plug-in management method provided by the embodiment of the application, when a user needs to update an allocated application or plug-in, a tenant administrator can indicate the application and plug-in to be updated by editing the image file, then each unit in the cloud service platform can process the image file, the image file is updated first, and the mounting relation of the virtual machine instance and the files in the storage unit is updated, so that the updated mounting relation meets the configuration requirements of the current new application and plug-in, the image file does not need to be manufactured by a center, and the delivery group does not need to be updated, so that the dynamic management of the application and the plug-in can be realized simply and efficiently.

Based on the description of the above embodiment, it may be determined that, in the implementation process of the plug-in management method based on the cloud application, the cloud service platform may perform subsequent operations in response to a request of a tenant administrator, or may perform subsequent operations in response to a request of an individual user, and related implementation manners between the client and the cloud service platform are described in further detail below for different application scenarios. Fig. 9 is a flowchart III of a cloud application-based plug-in management method according to an embodiment of the present application.

As shown in fig. 9, the method includes:

s901, receiving a mirror image creation request sent by a first client, and creating an application mirror image file in response to the mirror image creation request, wherein the application mirror image file comprises an application identifier of at least one target application and a plug-in identifier of at least one target plug-in, and the first client is a client for cloud application configuration.

In this embodiment, the first client may be a client that performs cloud application configuration. For example, in a scenario where a tenant administrator configures a cloud application to a general user, the first client may be a client operated by the tenant administrator, and the second client is a client of the general user, such as an enterprise employee. For example, in a scenario where the personal user configures a cloud application for his own device, the first client and the second client may be the same client, which are both clients owned by the personal user. In any application scenario, the first client is a client for cloud application configuration, and the second client is a client for running a cloud application.

Therefore, in this embodiment, the first client may send an image creation request to the first client according to an actual configuration requirement, and then the cloud service platform may create an application image file according to the image creation request, where an implementation manner is similar to that described above and will not be repeated herein.

And S902, creating a virtual machine instance according to a delivery request aiming at the application image file, wherein the delivery request is used for requesting to distribute the target application and the target plugin to at least one target object, the virtual machine instance is used for running the target application and the target plugin, and the second client is used for using the target application and the target plugin through a streaming transmission protocol with the virtual machine instance.

The delivery request and the virtual machine instance in this embodiment are similar to those described in the above embodiments, and will not be described here again. It should be noted that, in this embodiment, the target object and the second client have a corresponding relationship, for example, when the target object is a user account, the second client is the client logged in with the user account. Or the target object is the terminal device, then the second client is the target object.

Therefore, in this embodiment, in order to implement delivering the corresponding application and plug-in to the target object, a virtual machine instance is created, where the virtual machine instance may run the target application and the target plug-in to perform corresponding data processing, and then the virtual machine instance may provide the output data of the target application and the target plug-in for the second client, where the output data may include image data, sound data, character data, and so on, so that the second client may use the target application and the target plug-in through a streaming transmission protocol with the virtual machine instance.

S903, according to the application image file, an application file corresponding to the target application stored in the storage unit and a plug-in file corresponding to the target plug-in are mounted in the virtual machine instance.

The implementation manner of the cloud service platform for processing the file mount is similar to that described in the above embodiment, and will not be repeated here.

After the file mounting process is completed, the client corresponding to the target object can run a corresponding cloud application, and in a specific process, the second client can respond to the starting operation of the first application aiming at the desktop and send a session creation request to the cloud service platform, wherein the session creation request comprises object information corresponding to the second client, and the object information can be, for example, the equipment identifier of the second client or the account identifier of the user account logged in the second client. And also including in the session creation request an application identification of the first application to be run in the second client.

After receiving the session creation request sent by the second client, the cloud service platform can verify the second client according to the object information first, and when the verification passes, it can be determined that the second client has the authority to run the first application.

The cloud service platform may then create a target session in the virtual machine instance in response to the session creation request, wherein one session may be considered as a connection of the client, the connection being used to obtain data related to running the first application in the cloud, and thus may include an application instance of the first application in the target session, where the application instance is a process running the first application on the virtual machine instance. Therefore, after the session is successfully created, from the perspective of the user, the first application can be run on the desktop in the second client, and the related plug-in installed under the first application can also be run, however, the real application data processing is completed in the cloud.

In summary, according to the cloud application-based plug-in management method provided by the embodiment of the application, the application files and the plug-in files can be stored in the storage unit of the cloud service platform in the target format, so that the plug-in is free from installation, only simple configuration and mounting are needed, the effect of instant use is achieved, and the plug-in does not need to be downloaded and installed again after the instance is destroyed. Meanwhile, the image file only comprises the application identifier and the plug-in identifier, so that when the application and the plug-in need to be adjusted, the identification information in the image file can be edited, the purpose of adjusting the application and the plug-in can be achieved, and the image file does not need to be manufactured again. And in the application, the plug-in files are stored in the cloud service platform, so that the trouble that a user needs to search and install the plug-ins by himself is avoided, the user can be rapidly put into production after opening the cloud application, and the convenience and the comprehensiveness of the cloud application are improved.

Fig. 10 is a schematic structural diagram of a plug-in management device based on cloud application according to an embodiment of the present application. As shown in fig. 10, the apparatus 100 includes: a creation module 1001, a transceiver module 1002, and a processing module 1003.

A creating module 1001, configured to create an application image file according to an image creation request, where the application image file includes an application identifier of at least one target application and a plug-in identifier of at least one target plug-in;

the creating module 1001 is further configured to create a virtual machine instance according to a delivery request for the application image file, where the delivery request is used to request allocation of the target application and the target plugin to at least one target object, and the virtual machine instance is used to run the target application and the target plugin;

and a transceiver module 1002, configured to mount, in the virtual machine instance, an application file corresponding to the target application and a plug-in file corresponding to the target plug-in, where the application file corresponds to the target application and the plug-in are stored in the storage unit.

In one possible design, the cloud service platform further comprises a management and control unit and an instance unit;

the creation module 1001 is specifically configured to:

The control unit receives a delivery request;

the control unit responds to the delivery request and sends an instance processing request to the instance unit;

the instance unit responds to the instance processing request, creates the virtual machine instance, and sends notification information indicating that the instance creation is successful to the management and control unit.

In one possible design, the virtual machine instance includes a proxy unit therein;

the transceiver module 1002 is specifically configured to:

the control unit sends mounting information to the proxy unit of the virtual machine instance according to the application image file, wherein the mounting information comprises an application identifier of the target application and a plug-in identifier of the target plug-in;

and the proxy unit mounts the application file corresponding to the target application and the plug-in file corresponding to the target plug-in the virtual machine instance according to the application identifier and the plug-in identifier in the mounting information.

In one possible design, the transceiver module 1002 is further configured to:

before the application file corresponding to the target application and the plug-in file corresponding to the target plug-in are mounted in the virtual machine instance according to the application image file,

The control unit receives a first initial file of the target application, converts the first initial file into an application file in a target format, and stores the application file in the storage unit; the method comprises the steps of,

and the control unit receives a second initial file of the target plug-in, converts the second initial file into a plug-in file in a target format, and stores the plug-in file in the storage unit.

In one possible design, the apparatus further comprises a processing module 1003, the processing module 1003 being configured to:

after the application file corresponding to the target application and the plug-in file corresponding to the target plug-in are mounted in the virtual machine instance according to the application image file, updating the application image file according to an image modification request;

and updating the application files and plug-in files mounted by the virtual machine instance according to the updated application image files.

In one possible design, the image modification request is used to request deletion of a plug-in identifier of a first plug-in the application image file;

the processing module 1003 is specifically configured to:

The control unit determines a plug-in identification of the first plug-in according to the updated application image file;

the control unit sends update information to an agent unit of the virtual machine instance, wherein the update information comprises a plug-in identifier of the first plug-in;

and the proxy unit unloads the mount of the plug-in file of the virtual machine instance for the first plug-in according to the plug-in identification of the first plug-in.

In one possible design, the image modification request is used to request adding a plug-in identifier of a second plug-in to the application image file;

the processing module 1003 is specifically configured to:

the control unit determines the plug-in identification of the second plug-in according to the updated application image file;

the control unit sends update information to the proxy unit of the virtual machine instance, wherein the update information comprises a plug-in identifier of the second plug-in;

and the proxy unit mounts the plug-in file of the second plug-in the virtual machine instance according to the plug-in identification of the second plug-in.

In one possible design, the image modification request is used for requesting deletion of an application identifier of the first application in the application image file;

The processing module 1003 is specifically configured to:

the control unit determines an application identifier of the first application according to the updated application image file;

the control unit sends update information to an agent unit of the virtual machine instance, wherein the update information comprises an application identifier of the first application;

and the proxy unit uninstalls the application file of the virtual machine instance aiming at the first application and the mount of the plug-in file under the first application according to the application identifier of the first application.

In one possible design, the image modification request is used to request an application identifier of a second application to be added to the application image file;

the processing module 1003 is specifically configured to:

the control unit determines an application identifier of the second application according to the updated application image file;

the control unit sends update information to an agent unit of the virtual machine instance, wherein the update information comprises an application identifier of the second application;

and the proxy unit mounts the application file of the second application in the virtual machine instance according to the application identifier of the second application.

The device provided in this embodiment may be used to implement the technical solution of the foregoing method embodiment, and its implementation principle and technical effects are similar, and this embodiment will not be described herein again.

Fig. 11 is a schematic hardware structure of an electronic device provided in the embodiment of the present application, as shown in fig. 11, an electronic device 110 in the embodiment includes: a processor 1101 and a memory 1102; wherein the method comprises the steps of

Memory 1102 for storing computer-executable instructions;

the processor 1101 is configured to execute computer-executable instructions stored in the memory to implement the steps performed by the cloud application-based plug-in management method in the above embodiment. Reference may be made in particular to the relevant description of the embodiments of the method described above.

Alternatively, the memory 1102 may be separate or integrated with the processor 1101.

When the memory 1102 is provided separately, the electronic device further comprises a bus 1103 for connecting said memory 1102 with the processor 1101.

The embodiment of the application also provides a computer readable storage medium, wherein computer execution instructions are stored in the computer readable storage medium, and when a processor executes the computer execution instructions, the plug-in management method based on cloud application, which is executed by the electronic equipment, is realized.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards, and provide corresponding operation entries for the user to select authorization or rejection.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple modules may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.

The integrated modules, which are implemented in the form of software functional modules, may be stored in a computer readable storage medium. The software functional module is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (english: processor) to perform some of the steps of the methods described in the embodiments of the present application.

It should be understood that the above processor may be a central processing unit (english: central Processing Unit, abbreviated as CPU), or may be other general purpose processors, digital signal processors (english: digital Signal Processor, abbreviated as DSP), application specific integrated circuits (english: application Specific Integrated Circuit, abbreviated as ASIC), or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present invention may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in a processor for execution.

The memory may comprise a high-speed RAM memory, and may further comprise a non-volatile memory NVM, such as at least one magnetic disk memory, and may also be a U-disk, a removable hard disk, a read-only memory, a magnetic disk or optical disk, etc.

The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (Peripheral Component, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, the buses in the drawings of the present application are not limited to only one bus or one type of bus.

The storage medium may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer readable storage medium. The program, when executed, performs steps including the method embodiments described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. The plug-in management method based on the cloud application is characterized by being applied to a cloud service platform, wherein the cloud service platform comprises a storage unit, and application files of at least one application and plug-in files of at least one plug-in are stored in the storage unit, and the method comprises the following steps:

2. The method of claim 1, wherein the cloud service platform further comprises a management and control unit and an instance unit;

the creating a virtual machine instance according to the delivery request for the application image file comprises the following steps:

the control unit receives a delivery request;

3. The method according to claim 2, wherein the virtual machine instance comprises a proxy unit;

and according to the application image file, mounting an application file corresponding to the target application and a plug-in file corresponding to the target plug-in the storage unit in the virtual machine instance, including:

4. A method according to any one of claims 2-3, wherein, before the application file corresponding to the target application and the plug-in file corresponding to the target plug-in stored in the storage unit are installed in the virtual machine instance according to the application image file, the method further includes:

5. The method according to any one of claims 2-4, wherein after the application file corresponding to the target application and the plug-in file corresponding to the target plug-in stored in the storage unit are installed in the virtual machine instance according to the application image file, the method further includes:

Updating the application image file according to the image modification request;

6. The method of claim 5, wherein the image modification request is for requesting deletion of a plug-in identifier of a first plug-in the application image file;

and updating the application file and the plug-in file mounted by the virtual machine instance according to the updated application image file, wherein the updating comprises the following steps:

7. The method of claim 5, wherein the image modification request is for requesting an addition of a plug-in identification of a second plug-in the application image file;

8. The method of claim 5, wherein the image modification request is for requesting deletion of an application identifier of a first application in the application image file;

9. The method of claim 5, wherein the image modification request is for requesting an addition of an application identifier of a second application in the application image file;

10. The method according to any one of claims 2-9, wherein after the application file corresponding to the target application and the plug-in file corresponding to the target plug-in stored in the storage unit are installed in the virtual machine instance according to the application image file, the method further includes:

the control unit sends a creation instruction to the proxy unit;

the agent unit creates the target application and the application instance corresponding to the target plugin according to the creation instruction;

And if the application instance is successfully created, the management and control unit updates the delivery state corresponding to the delivery request to be the delivery processing completion.

11. The plug-in management method based on the cloud application is characterized by being applied to a cloud service platform, wherein the cloud service platform comprises a storage unit, and application files of at least one application and plug-in files of at least one plug-in are stored in the storage unit, and the method comprises the following steps:

receiving an image creation request sent by a first client, and responding to the image creation request to create an application image file, wherein the application image file comprises an application identifier of at least one target application and a plug-in identifier of at least one target plug-in, and the first client is a client for cloud application configuration;

creating a virtual machine instance according to a delivery request for the application image file, wherein the delivery request is used for requesting to allocate the target application and the target plugin to at least one target object, the virtual machine instance is used for running the target application and the target plugin, and a second client is used for using the target application and the target plugin through a streaming transmission protocol with the virtual machine instance;

12. The method of claim 11, wherein the target object is the second client; or if the target object is a user account, the second client is a client logged in to the user account.

13. The method according to claim 11 or 12, wherein after the application file corresponding to the target application and the plug-in file corresponding to the target plug-in stored in the storage unit are installed in the virtual machine instance according to the application image file, the method further comprises:

receiving a session creation request sent by a second client, wherein the session creation request comprises object information corresponding to the second client and an application identifier of a first application to be run by the second client;

and verifying the object information, and when the verification is passed, responding to the session creation request, and creating a target session in the virtual machine instance, wherein the target session comprises an application instance of the first application, and the application instance is a process running the first application on the virtual machine instance.

14. A cloud application-based plug-in management apparatus, comprising:

15. An electronic device, comprising:

a memory for storing a program;

a processor for executing the program stored by the memory, the processor being for performing the method of any one of claims 1 to 13 when the program is executed.

16. A computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 13.

17. A computer program product comprising a computer program, characterized in that the computer program, when executed by a processor, implements the method of any of claims 1 to 13.