Plug-in management method and system for cloud application and electronic equipment

Abstract

The embodiment of the invention provides a plug-in management method and system of a cloud application and electronic equipment. The plug-in management method for the cloud application comprises the following steps: receiving a cloud application starting instruction sent by a first client, wherein the cloud application starting instruction comprises an identifier of a target user; in response to the cloud application starting instruction, mounting a virtual disk file of a target plug-in for a cloud application session of a target user based on plug-in information of the target user, the plug-in information being used for indicating the target user to select to start the target plug-in, the cloud application session of the target user runs based on the virtual disk file of the cloud application mounted on the cloud server instance and the virtual disk file of the target plug-in. And the flexibility of cloud application plug-in management is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of cloud applications, and more particularly, to a plug-in management method, system and electronic device of cloud applications. BACKGROUND

[0002] Currently, many software supports plug-ins (Plug-in), which can optimize the use of software, supplement the functions of software, and improve the user experience. For example, the programming integrated development environment (Integrated Development Environment, IDE) software in the IT industry almost inevitably requires plug-ins, and the richness of plug-ins determines the user's choice.

[0003] Currently, most cloud providers provide cloud applications mainly in the form of pre-installed application and plug-in virtual machine image management. The commonly used plug-ins are downloaded and installed in advance in the image, which lacks flexibility. SUMMARY

[0004] The present application provides a plug-in management method, system and electronic device of cloud applications, which improves the flexibility of cloud application plug-in management.

[0005] In a first aspect, the present application provides a plug-in management method of cloud applications applied to the cloud, which comprises:

[0006] receiving a cloud application start instruction sent by a first client, wherein the cloud application start instruction comprises an identifier of a target user;

[0007] in response to the cloud application start instruction, mounting a virtual disk file of a target plug-in for a cloud application session of the target user based on plug-in information of the target user, wherein the plug-in information is used to indicate that the target user selects to enable the target plug-in, and the cloud application session of the target user is run based on a virtual disk file of the cloud application mounted by a cloud server instance and the virtual disk file of the target plug-in.

[0008] In a second aspect, the present application provides a plug-in management method of cloud applications applied to a first client, which comprises:

[0009] in response to an operation of starting a cloud application by a target user, sending a cloud application start instruction to the cloud;

[0010] receiving a user interface of the cloud application returned by the cloud, wherein a cloud application session of the target user is run based on a virtual disk file of the cloud application mounted by a cloud server instance and a virtual disk file of a target plug-in indicated in plug-in information of the target user, and the plug-in information is used to indicate that the target user selects to enable the target plug-in.

[0011] In a third aspect, the application provides a plug-in management method of a cloud application, applied to a second client, the method comprising:

[0012] In response to an operation of creating an image for the cloud application, sending a creation image instruction for the cloud application to a cloud end, the creation image instruction being used to trigger creation of an application image based on a virtual disk file of the cloud application;

[0013] In response to an operation of creating a delivery group for the application image, sending a creation delivery group instruction to the cloud end, the creation delivery group instruction being used to trigger creation of a cloud server instance based on the application image and mounting the virtual disk file of the cloud application, the creation delivery group instruction comprising authorization user information of the cloud application, in a case where a target user in the authorization users starts the cloud application, a cloud application session of the target user being run based on the virtual disk file of the cloud application mounted by the cloud server instance and a virtual disk file of a target plug-in indicated in plug-in information of the target user, the plug-in information being used to indicate that the target user selects to enable the target plug-in.

[0014] In a fourth aspect, the application provides a plug-in management device of a cloud application, comprising:

[0015] A receiving module is configured to receive a cloud application start instruction sent by a first client, the cloud application start instruction comprising an identifier of a target user;

[0016] A processing module is configured to, in response to the cloud application start instruction, mount a virtual disk file of a target plug-in for a cloud application session of the target user based on plug-in information of the target user, the plug-in information being used to indicate that the target user selects to enable the target plug-in, the cloud application session of the target user being run based on a virtual disk file of the cloud application mounted by a cloud server instance and the virtual disk file of the target plug-in.

[0017] In a fifth aspect, the application provides a plug-in management device of a cloud application, comprising:

[0018] A sending module is configured to, in response to an operation of starting a cloud application by a target user, send a cloud application start instruction to a cloud end;

[0019] A receiving module is configured to receive a user interface of the cloud application returned by the cloud end, wherein a cloud application session of the target user is run based on a virtual disk file of the cloud application mounted by a cloud server instance and a virtual disk file of a target plug-in indicated in plug-in information of the target user, the plug-in information being used to indicate that the target user selects to enable the target plug-in.

[0020] In a sixth aspect, the application provides a plug-in management device of a cloud application, comprising:

[0021] a first sending module, configured to, in response to an operation of creating an image for a cloud application, send a creating image instruction for the cloud application to a cloud end, the creating image instruction being used to trigger creation of an application image based on a virtual disk file of the cloud application;

[0022] a second sending module, configured to, in response to an operation of creating a delivery group for the application image, send a creating delivery group instruction to the cloud end, the creating delivery group instruction being used to trigger creation of a cloud server instance based on the application image and mounting of the virtual disk file of the cloud application, the creating delivery group instruction including authorization user information of the cloud application, in a case where a target user in the authorization users starts the cloud application, a cloud application session of the target user being run based on the virtual disk file of the cloud application mounted by the cloud server instance and a virtual disk file of a target plug-in indicated in plug-in information of the target user, the plug-in information being used to indicate that the target user selects to enable the target plug-in.

[0023] In a seventh aspect, the present application provides an electronic device, comprising a memory and a processor;

[0024] The memory is configured to store a computer program;

[0025] The processor is configured to execute the computer program stored in the memory, and the computer program, when running, causes the processor to execute the method in the first aspect, the second aspect or the third aspect.

[0026] In an eighth aspect, the present application provides a computer readable storage medium, the computer readable storage medium storing a computer program, and the computer program, when executed by a processor, causes the processor to execute the method in the first aspect, the second aspect or the third aspect.

[0027] In a ninth aspect, the present application provides a computer program product, comprising a computer program, and the computer program, when executed by a processor, implements the method in the first aspect, the second aspect or the third aspect.

[0028] In the cloud application plug-in management method, system and electronic device provided by the present application, the cloud application and each plug-in of the cloud application are respectively stored as independent virtual hard disk (VHD) files, a target user can select a required plug-in when using the cloud application, and the selection of the target user on the plug-in is recorded in plug-in information, in addition to mounting the VHD file of the cloud application, the cloud server also mounts the VHD file of a target plug-in for a cloud application session of the user based on the plug-in information of the user, thereby realizing flexible plug-in management for the user. BRIEF DESCRIPTION OF DRAWINGS

[0029] In order to more clearly illustrate the technical solutions of the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced as follows. Obviously, the accompanying drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor under the premise of the accompanying drawings.

[0030] Figure 1 is a schematic diagram of the principle of a plug-in management method of a cloud application provided by an embodiment of the present application;

[0031] Figure 2 is a flowchart of a plug-in management method of a cloud application provided by an embodiment of the present application Figure 1 ;

[0032] Figure 3 is a flowchart of a plug-in management method of a cloud application provided by an embodiment of the present application Figure 2 ;

[0033] Figure 4 is a flowchart of a plug-in management method of a cloud application provided by an embodiment of the present application Figure 3 ;

[0034] Figure 4 is a flowchart of a plug-in management method of a cloud application provided by an embodiment of the present application Figure 5 ;

[0035] Figure 1 is a structural diagram of a plug-in management device of a cloud application provided by an embodiment of the present application Figure 7 ;

[0036] Figure 2 is a structural diagram of a plug-in management device of a cloud application provided by an embodiment of the present application Figure 8 ;

[0037] Figure 3 is a structural diagram of a plug-in management device of a cloud application provided by an embodiment of the present application Figure 9 ;

[0038] Figure 1 is a schematic block diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.

[0040] The terms involved in the embodiments of the present application are introduced.

[0041] Cloud application: Application virtualization based on cloud resources, running traditional software using cloud resources, and providing applications running in cloud resources to users for local use.

[0042] Plug-in: A program written according to a certain specification of application program interface. Plug-ins can only run on the system platform specified by the program (may support multiple platforms at the same time), and cannot run independently of the specified platform. Different plug-ins can provide different auxiliary functions, for example, after installing the GitToolBox plug-in in IntelliJ IDEA, the Git commit record of the code can be displayed more conveniently.

[0043] Plug-in store: A space on the cloud application client for managing plug-ins that users have access to, such as enabling, disabling, upgrading, etc.

[0044] VHD file: A virtual disk format file, a VHD format file can be virtually a hard disk, VHD files support remote mounting, VHD files stored on shared storage can be ported and remotely mounted locally.

[0045] Application package: Each application package is an independent VHD format file, which contains application files, registry files and some auxiliary files, and is directly mounted to the system at runtime in the form of a volume (Volume).

[0046] Plug-in package: Each plug-in package is an independent VHD format file, which contains plug-in files and directories, and is directly mounted to the application directory in the system at runtime in the form of a Volume. The management system maintains the application to which the plug-in belongs.

[0047] Application image: refers to a logical image containing a series of applications, which can be located to the VHD file on the shared storage according to the application information.

[0048] Application instance: refers to mounting a VHD file made from an application to a cloud server (Elastic Compute Service, ECS), and running the application on the cloud to provide users with use.

[0049] Delivery group: a logical grouping of delivering cloud applications to end users, including underlying dependent cloud application resources, images of cloud applications, resource management policies, elasticity policies, and user allocation settings, etc.

[0050] Currently, most cloud applications provided by cloud vendors mainly use the virtual machine image management mode of pre-installed applications and plug-ins. The administrator downloads and installs common plug-ins in advance in the image. If it is necessary to add, upgrade, or remove plug-ins, or users have the use demand for other plug-ins, the administrator needs to re-produce the image. If users install or upgrade plug-ins in the cloud application, the resource instances that have undergone elasticity or reset need to be re-installed with plug-ins. Therefore, in the embodiments of the present application, a scheme of dynamically loading cloud application plug-ins based on VHD is proposed. The cloud application and each plug-in of the cloud application are respectively made into an independent VHD file. When a user uses the cloud application, the user can select the plug-in to be enabled, disabled, or upgraded. The selection of the plug-in by the user can be recorded in the plug-in information of the user. In addition to mounting the VHD file of the cloud application, the cloud server also mounts the VHD file of the corresponding plug-in for the session of the user based on the plug-in information of the user. The plug-in information of the user is not affected by time, space, client type, and elasticity, reset, etc. of the application instance, so that the cloud application is closer to the PC experience.

[0051] Figure 1 is a principle diagram of a plug-in management method of a cloud application provided by the embodiments of the present application. As shown in Figure 1 , the cloud application runs in the cloud. The cloud includes a cloud application management and control platform, a cloud server, and shared storage. The shared storage is used to store application packages and plug-in packages, that is, VHD files of the cloud application and VHD files of the plug-in. Each cloud application and each plug-in is an independent VHD file. The VHD files of the cloud application in the shared storage are stored in directories according to tenants. For example, Figure 1 the tenant 1 directory and the tenant 2 directory in are respectively used to store the VHD files of the cloud applications and the corresponding plug-ins of tenant 1 and tenant 2. Each cloud application of each tenant corresponds to a plug-in directory, which is used to store the VHD files of the plug-ins of the cloud application. For example, Figure 2 the cloud application 1 and the cloud application 2 of tenant 1 in have corresponding cloud application 1 plug-in directories and cloud application 2 plug-in directories, respectively. The cloud application 1 plug-in directory is used to store the VHD files of the plug-ins of the cloud application 1, and the cloud application 2 plug-in directory is used to store the VHD files of the plug-ins of the cloud application 2. Optionally, the shared storage in the embodiments of the present application can be a network attached storage (NAS) file system.

[0052] The tenant administrator requests the cloud application management and control platform to create a cloud application through a second client, and associates one or more plug-ins with the cloud application, including making installation files of the cloud application and installation files of the corresponding plug-ins into VHD files and storing them in a shared storage, making an application image and creating a delivery group to authorize the cloud application to a user. The tenant administrator can perform user authorization management on the cloud application. The user accesses the cloud application through a cloud application client in the first client. The cloud application client can provide a plug-in store. The user can enter the plug-in store through the cloud application client. The plug-in store displays optional plug-ins of the cloud application authorized by the user. The user can adjust the plug-ins to be used by himself. The cloud server instance can mount the VHD file of the corresponding plug-in for the cloud application instance of the user based on the selection of the user in addition to mounting the VHD file of the cloud application. The cloud application instances of different users can correspond to the VHD files of the same or different plug-ins. The cloud application instance of the user corresponds to the cloud application session of the user. The tenant administrator is also called an administrator. The plug-in management method of the cloud application provided in the application will be described below in combination with embodiments.

[0053] Figure 1 is a flowchart of a plug-in management method of a cloud application provided in an embodiment of the application Figure 2 . The execution subject of the method is a second client of a tenant administrator. As shown in Figure 3 , the method comprises the following steps.

[0054] S201, in response to an operation of creating an image for a cloud application, sending a creation image instruction for the cloud application to a cloud end, the creation image instruction being used to trigger the creation of an application image based on a VHD file of the cloud application.

[0055] The application image is triggered to be created by an operation of an administrator. For example, the administrator logs in a cloud application console through a browser. The cloud application console can be a management page provided by a cloud application management and control platform. The administrator selects a cloud application that needs to create an image from the created cloud applications, and triggers the creation of an application image for the cloud application. The created cloud applications that can be selected by the administrator in the cloud application console are cloud applications whose VHD files have been generated. The creation image instruction can include a running environment of the image, a region to which the image belongs, a name of the image, and an identifier of the cloud application that needs to make the image. The cloud application management and control platform of the cloud end can save the image information in response to the creation image instruction, and store the information of the VHD file of the cloud application into a database of the cloud end.

[0056] Before the image is created, the operation of creating the cloud application can also be triggered by the administrator, and the administrator creating the cloud application refers to that the administrator uploads the installation file of the cloud application to the cloud through the second client, so that the cloud converts the installation file of the cloud application into a VHD file. That is, before step S201, the method of the embodiment of the application can also include: obtaining the installation file of the cloud application, and sending the installation file of the cloud application to the cloud to convert the installation file of the cloud application into a VHD file of the cloud application. Wherein, the cloud can use the existing file conversion tool or file making tool to convert the installation file of the cloud application into a VHD file. In addition, the cloud can store the generated VHD file of the cloud application in the directory of the corresponding tenant in the shared storage.

[0057] Optionally, after the cloud application is created, the administrator can further select the cloud application through the cloud application console to trigger adding or upgrading the plug-in of the cloud application, that is, the method of the embodiment of the application can also include: obtaining the installation file of any plug-in of the cloud application, and sending the installation file of any plug-in to the cloud to convert the installation file of any plug-in into a VHD file of any plug-in, any plug-in being a new version of an existing plug-in of the cloud application or a new plug-in of the cloud application. Similar to the foregoing, the cloud can use the existing file conversion tool or file making tool to convert the installation file of any plug-in into a VHD file. In addition, the cloud can store the generated VHD file of any plug-in in the plug-in directory of the corresponding cloud application in the shared storage. It should be noted that, for the case of upgrading the plug-in, the cloud will not delete the VHD file of the old version of the plug-in after generating and storing the VHD file of the new version of the plug-in, so that the user can choose whether to upgrade the plug-in of his own, that is, the user can choose to use the new version of the plug-in or continue to use the old version of the plug-in.

[0058] S202, in response to the operation of creating a delivery group for the application image, a create delivery group instruction is sent to the cloud, the create delivery group instruction is used to trigger the creation of a cloud server instance based on the application image and the mounting of the VHD file of the cloud application, the create delivery group instruction includes authorized user information of the cloud application, in the case that a target user in the authorized users starts the cloud application, the cloud application session of the target user is run based on the VHD file of the cloud application mounted by the cloud server instance and the VHD file of the target plug-in indicated in the plug-in information of the target user, and the plug-in information is used to indicate that the target user selects to enable the target plug-in.

[0059] After the application image is created, the cloud application is provided to the user by creating a delivery group, and the tenant administrator can create the delivery group through the cloud application console. When operating to create the delivery group, the tenant administrator can select the application image and make relevant configurations, such as configuring the information of the resources and authorized users of the delivery group, and the creation instruction of the delivery group can include the resources of the delivery group, the application image, the authorized user information, and the like. The cloud application management and control platform in the cloud responds to the application image indicated by the creation instruction of the delivery group, creates a cloud server instance using the basic operating system image, and mounts the VHD file of the cloud application on the cloud server instance, so that the cloud application can be displayed in the cloud application client of the authorized user, and the authorized user can operate and use the cloud application.

[0060] When the target user uses the cloud application, the target user can select to enable the plug-in of the cloud application according to the own demand, the cloud end mounts the VHD file of the target plug-in according to the selection of the user for the cloud application session of the user, so that the cloud application session of the target application runs based on the VHD file of the cloud application and the VHD file of the target plug-in, and the personalized plug-in management for the user is realized.

[0061] The related information of the target plug-in selected to be enabled by the target user is stored in the plug-in information of the target user, and the plug-in information is stored in the cloud end. When the target user uses the cloud application, the cloud end can automatically mount the VHD file of the target plug-in for the application session of the target user according to the plug-in information, and the persistence of the plug-in management is realized.

[0062] In the method of the embodiment of the application, the cloud application and each plug-in of the cloud application are stored as independent VHD files, the administrator creates the image and the delivery group based on the VHD file of the cloud application, the target user can select the plug-in needed by the target user when using the cloud application, and the selection of the plug-in by the target user can be recorded in the plug-in information. In addition to mounting the VHD file of the cloud application, the cloud server also mounts the VHD file of the target plug-in for the cloud application session of the user based on the plug-in information of the user, and the flexible plug-in management for the user is realized. The administrator no longer needs to maintain the plug-in in the image, but only needs to configure the plug-in for the cloud application and configure the permission for the user, and the user can conveniently manage the plug-in range used by the user through the plug-in store, so that the experience of the cloud application is closer to the PC experience.

[0063] Figure 2 is a flowchart of a plug-in management method of a cloud application provided by the embodiment of the application Figure 3 . The execution subject of the method is a first client of a target user. As shown in Figure 4 , the method comprises the following steps.

[0064] S301, in response to an operation of starting the cloud application by the target user, a cloud application start instruction is sent to the cloud end.

[0065] After the administrator authorizes the cloud application for the user to use by creating a delivery group, the authorized user can see the authorized cloud application through the cloud application client in the first client. The target user starts the cloud application through the cloud application client, for example, the target user selects the icon of a certain cloud application in the cloud application client, clicks the "connect" option, triggers a cloud application starting instruction, and the cloud application starting instruction includes the identity of the target user, so that the cloud end mounts the corresponding VHD file for the cloud application session of the target user. Alternatively, the target user can select the plug-in to be started when starting the cloud application through the cloud application client, that is, the cloud application starting instruction can carry plug-in information.

[0066] S302, receiving the user interface of the cloud application returned by the cloud end, wherein the cloud application session of the target user is run based on the VHD file of the cloud application mounted by the cloud server instance and the VHD file of the target plug-in indicated in the plug-in information of the target user, and the plug-in information is used to indicate that the target user selects to enable the target plug-in.

[0067] After the target user starts the cloud application, the cloud server instance of the cloud end mounts the VHD file of the target plug-in selected by the target user to be enabled in addition to the VHD file of the cloud application based on the plug-in information of the target user. The plug-in information of the target user can be the plug-in information carried in the cloud application starting instruction, or can also be the plug-in information of the target user stored by the cloud end. The cloud application instance of the target user runs in the cloud end, and the cloud end returns the user interface of the cloud application to the client of the target user, so that the target user operates and uses the cloud application through the cloud application client in the first client.

[0068] In the embodiment of the application, the target user starts the cloud application through the first client, and the cloud end can automatically mount the VHD file of the corresponding plug-in based on the plug-in information of the target user, thereby realizing flexible plug-in management.

[0069] When the target user uses the cloud application, the target user can operate and manage the plug-in of the cloud application. The first client sends a plug-in operation instruction to the cloud end in response to the operation of the target user on the plug-in of the cloud application. The plug-in operation instruction is used to enable, disable or upgrade the plug-in and is used to update the plug-in information.

[0070] For example, the administrator adds multiple plug-ins to the cloud application according to the method in the foregoing embodiment, and the target user can view the multiple plug-ins of the cloud application through the cloud application client in the first client, for example, the target user can view the plug-ins of the cloud application in the plug-in store and further perform enabling, disabling or upgrading operations. Optionally, the target user can select one or more plug-ins from the multiple plug-ins to start, so that the cloud end mounts the VHD file of the corresponding plug-in for the cloud application session of the target user, and the target user can use the function of the corresponding plug-in. Optionally, after enabling a plug-in, if the target user selects to disable the plug-in, the cloud end unmounts the VHD file of the corresponding plug-in for the cloud application session of the target user. Optionally, after the target user enables a plug-in, if the tenant administrator adds a new version of the plug-in, the target user can receive a prompt of the new version of the plug-in through the first client, and the target user can select whether to upgrade. If the target user selects to upgrade, the cloud end mounts the VHD file of the new version of the plug-in for the cloud application session of the target user and unmounts the VHD file of the old version of the plug-in. Thus, flexible plug-in management at the user level is implemented.

[0071] Figure 3 is a flowchart of a plug-in management method of a cloud application provided in an embodiment of the present application Figure 4 . The execution subject of the method is the cloud end. As shown in Figure 5 , the method comprises the following steps.

[0072] S401, receiving a cloud application starting instruction sent by a first client, the cloud application starting instruction comprising an identifier of a target user.

[0073] S402, in response to the cloud application starting instruction, mounting a VHD file of a target plug-in in plug-in information for a cloud application session of the target user based on the plug-in information of the target user, the plug-in information being used to indicate that the target user selects to enable the target plug-in, and the cloud application session of the target user being run based on a VHD file of a cloud application mounted by a cloud server instance and the VHD file of the target plug-in.

[0074] In the embodiment of the present application, the cloud application instance of the target user is run in the cloud end, the administrator creates a delivery group for the authorized user, and the cloud end mounts the VHD file of the target plug-in for the cloud application session of the target user in response to the cloud application starting instruction triggered by the operation of the target user through the first client according to the target plug-in indicated in the plug-in information of the target user selected by the target user to be enabled. The plug-in information of the target user can be the plug-in information carried in the cloud application starting instruction, and the cloud end can save the plug-in information carried in the cloud application starting instruction. Alternatively, the plug-in information of the target user can be the plug-in information already saved in the cloud end, for example, the plug-in information saved based on the cloud application starting instruction or the plug-in operation instruction of the target user.

[0075] When the target user uses the cloud application, the target user performs an operation management on the plug-in of the cloud application, for example, the target user performs an enabling, disabling or deleting operation on the plug-in of the cloud application through the plug-in store of the cloud application client in the first client, the operation of the target user triggers a plug-in operation instruction, the cloud end receives the plug-in operation instruction of the target user for the cloud application, and based on the plug-in operation instruction, the cloud end mounts a virtual disk file of a first plug-in and / or unmounts a virtual disk file of a second plug-in for the cloud application session of the target user, and updates the plug-in information of the target user.

[0076] In one case, the first plug-in is a plug-in that the target user has not selected to enable, and the plug-in operation instruction is used to enable the first plug-in; based on the plug-in operation instruction, the cloud end mounts the VHD file of the first plug-in for the cloud application session of the target user, and adds the information of the first plug-in in the plug-in information of the target user. In the case where the target user selects to enable the first plug-in, the cloud end adds the VHD file of the first plug-in, so that the target user can use the first plug-in on the basis of the currently used cloud application or the cloud application and the plug-in. Moreover, the cloud end records the information of the first plug-in, for example, the identifier of the first plug-in, in the plug-in information of the target user, so that the cloud end automatically mounts the VHD file of the first plug-in for the cloud application session of the target user when the target user uses the cloud application again subsequently.

[0077] In another case, the second plug-in is a plug-in that the target user has selected to enable, and the plug-in operation instruction is used to disable the second plug-in; based on the plug-in operation instruction, the cloud end unmounts the VHD file of the second plug-in for the cloud application session of the target user, and deletes the information of the second plug-in in the plug-in information of the target user. In the case where the second plug-in has been enabled, the target user can select to disable the second plug-in again, and then the cloud end unmounts the mounted VHD file of the second plug-in, so that the target user cannot use the second plug-in. Moreover, the cloud end deletes the recorded information of enabling the second plug-in, for example, deletes the identifier of the second plug-in, so that the cloud end does not automatically mount the VHD file of the second plug-in for the cloud application session of the target user when the target user uses the cloud application again subsequently.

[0078] In another case, the first plug-in is an upgraded version of a second plug-in that the target user has selected to enable, and the plug-in operation instruction is used to upgrade the enabled second plug-in to the first plug-in; the cloud side mounts the VHD file of the first plug-in and unmounts the VHD file of the second plug-in for the cloud application session of the target user based on the plug-in operation instruction, and adds the information of the first plug-in to the plug-in information of the target user and deletes the information of the second plug-in. In the case where the target user selects to enable the second plug-in, if the administrator upgrades the second plug-in, the target user can select to upgrade the second plug-in, that is, to enable the first plug-in, or can select to continue to use the second plug-in. In the case where the target user selects to upgrade, the cloud side will mount the VHD file of the first plug-in and unmount the mounted VHD file of the second plug-in, so that the target user can use the new version of the plug-in, that is, the first plug-in. Moreover, the cloud side deletes the recorded information of enabling the second plug-in and adds the information of enabling the first plug-in, so that when the target user uses the cloud application again later, the cloud side will automatically mount the VHD file of the first plug-in for the cloud application session of the target user, instead of mounting the VHD file of the second plug-in.

[0079] In the method of the embodiment of the application, the cloud application and each plug-in of the cloud application are stored as independent VHD files in the shared storage, the administrator creates the image and the delivery group based on the VHD file of the cloud application, the target user can select the required plug-in when using the cloud application, the selection of the plug-in by the target user can be recorded in the plug-in information, and the cloud server mounts the VHD file of the target plug-in for the cloud application session of the user based on the plug-in information of the user in addition to mounting the VHD file of the cloud application, thereby realizing flexible plug-in management for the user.

[0080] The method executed by the cloud side in the process of creating the cloud application, the application image and the delivery group by the administrator is described below.

[0081] The administrator uploads the installation file of the cloud application through the second client, the cloud side obtains the installation file of the cloud application, converts the installation file of the cloud application into a virtual disk file of the cloud application, and stores the virtual disk file of the cloud application under the directory of the cloud application in the shared storage. In the process of VHDing the installation file of the cloud application to obtain the VHD file, the cloud side can use an existing file conversion tool or a file making tool, and the cloud side stores the generated VHD file of the cloud application under the directory of the corresponding tenant in the shared storage, so that the administrator can view on the second client that the cloud application has been successfully created.

[0082] Optionally, after the cloud application is created, the administrator can add or upgrade a plug-in for the cloud application. The administrator uploads an installation file of any plug-in of the cloud application through the second client. The cloud end obtains the installation file of the any plug-in, converts the installation file of the any plug-in into a virtual disk file of the any plug-in, and stores the virtual disk file of the any plug-in in a plug-in directory of the cloud application in the shared storage. The any plug-in can be a new version of an existing plug-in of the cloud application, that is, the administrator upgrades the existing plug-in. Alternatively, the any plug-in is a new plug-in of the cloud application, that is, the administrator adds a new plug-in for the cloud application.

[0083] After the cloud application is created, the administrator can create an application image for the cloud application. The cloud end receives a creation image instruction for the cloud application, and creates an application image based on a virtual disk file of the cloud application. The creation image instruction can include a running environment of the image, a region to which the image belongs, an image name, and an identifier of the cloud application for which the image is to be created. The cloud application management and control platform of the cloud end can save image information and store information of the VHD file of the cloud application in a database of the cloud end in response to the creation image instruction.

[0084] After the administrator creates the application image, the administrator can further create a delivery group to provide the cloud application to a user. The cloud end receives a creation delivery group instruction for the application image, creates a cloud server instance based on the application image, and mounts the virtual disk file of the cloud application. The creation delivery group instruction includes authorized users of the cloud application, and the target user is any one of the authorized users. The creation delivery group instruction can include information such as resources of the delivery group, the application image, and the authorized users. The cloud application management and control platform of the cloud end creates a cloud server instance using a basic operating system image in response to the application image indicated by the creation delivery group instruction, and mounts the VHD file of the cloud application on the cloud server instance. Thus, the cloud application client in the client of the authorized user can display the cloud application, and the authorized user can operate and use the cloud application.

[0085] Optionally, in the embodiment of the present application, after the cloud application is provided to the authorized user through the delivery group, if the administrator adds or upgrades a plug-in for the cloud application, the cloud end converts the installation file of the plug-in into a VHD file and stores the VHD file in the shared storage, and further sends prompt information to the client of the authorized user. The prompt information is used to prompt that there is a new plug-in or that there is a new version of an existing plug-in. In this way, the authorized user can view the prompt information through the client of the authorized user, and further select whether to enable the new plug-in or to upgrade the existing plug-in. If the authorized user operates to enable the new plug-in or to upgrade the existing plug-in, a plug-in operation instruction is triggered, and the corresponding process is described in the foregoing embodiment, which will not be described here.

[0086] Figure 4 is a flowchart of a plug-in management method of a cloud application provided in an embodiment of the present application Figure 5 .Figure 6 The flowchart includes the flow of administrator creating application image and delivery group, administrator uploading plug-in and user operating plug-in, which are described as follows. Steps 1 and 2 show that the administrator triggers the creation of application image through the second client, and the cloud application management and control platform stores the image information and VHD file information of the cloud application into a database (DB). Steps 3-5 show that the administrator triggers the creation of the delivery group for the application image through the second client, and the cloud application management and control platform starts the creation of the delivery group workflow, and the workflow automatically creates ECS using the basic OS image, the basic OS image contains an agent (Agent) adapted to a guest operating system (GuestOS), and the Agent mounts the VHD file of the cloud application. Optionally, after the creation of the delivery group succeeds, the cloud application management and control platform can also attempt to start an application instance. Steps 6-9 show that the administrator uploads the plug-in through the second client, which can be a new plug-in or an upgraded version of an existing plug-in, and the cloud application management and control platform updates the plug-in information of the user, starts the modification of the delivery group workflow, and the workflow automatically notifies the Agent to mount the VHD file of the new plug-in and / or uninstall the VHD file of the unnecessary plug-in. Steps 10-14 show that the user starts, disables or upgrades the plug-in, the cloud application management and control platform updates the plug-in information of the user, mounts the new plug-in and / or uninstalls the unnecessary plug-in for the cloud application session of the user, and attempts to start the application instance to ensure that the cloud application can run normally.

[0087] In the embodiment of the application, the user uses the cloud application through the first client, for example, uses the shadowless cloud application based on the shadowless cloud application protocol, and the computing resource is in the cloud. When the user finishes using the cloud application, the user directly closes the application, and the cloud resource automatically uninstalls the VHD file.

[0088] Figure 1 Fig. 6 is a structural schematic of a plug-in management device of a cloud application provided by the embodiment of the application. Figure 6 As shown in Fig. 6, the plug-in management device 600 of the cloud application includes: Figure 7 The receiving module 601 is configured to receive a cloud application starting instruction sent by the first client, and the cloud application starting instruction includes the identification of the target user.

[0089] The processing module 602 is configured to, in response to the cloud application starting instruction, mount the virtual disk file of the target plug-in for the cloud application session of the target user based on the plug-in information of the target user, the plug-in information is used to indicate that the target user selects to enable the target plug-in, and the cloud application session of the target user is run based on the virtual disk file of the cloud application mounted by the cloud server instance and the virtual disk file of the target plug-in.

[0090]

[0091] ​In an implementation manner, the receiving module is further configured to receive a plug-in operation instruction of the target user for the cloud application;

[0092] The processing module is further configured to mount a virtual disk file of the first plug-in and / or unmount a virtual disk file of the second plug-in for the cloud application session of the target user based on the plug-in operation instruction, and update the plug-in information of the target user.

[0093] In an implementation manner, the plug-in operation instruction is used to enable the first plug-in;

[0094] The processing module is configured to:

[0095] The processing module is configured to mount a virtual disk file of the first plug-in for the cloud application session of the target user based on the plug-in operation instruction, and add information of the first plug-in in the plug-in information of the target user.

[0096] In an implementation manner, the plug-in operation instruction is used to disable the second plug-in;

[0097] The processing module is configured to:

[0098] The processing module is configured to unmount a virtual disk file of the second plug-in for the cloud application session of the target user based on the plug-in operation instruction, and delete information of the second plug-in in the plug-in information of the target user.

[0099] In an implementation manner, the plug-in operation instruction is used to upgrade the enabled second plug-in to the first plug-in;

[0100] The processing module is configured to:

[0101] The processing module is configured to mount a virtual disk file of the first plug-in and unmount a virtual disk file of the second plug-in for the cloud application session of the target user based on the plug-in operation instruction, and add information of the first plug-in and delete information of the second plug-in in the plug-in information of the target user.

[0102] In an implementation manner, the receiving module is further configured to receive a creation image instruction for the cloud application, and the processing module is further configured to create an application image based on a virtual disk file of the cloud application;

[0103] The receiving module is further configured to receive a creation delivery group instruction for the application image, and the processing module is further configured to create a cloud server instance based on the application image and mount a virtual disk file of the cloud application, the creation delivery group instruction including authorized user information of the cloud application, and the target user being any one of the authorized users.

[0104] In an implementation manner, the receiving module is further configured to receive a creation image instruction for the cloud application, and the processing module is further configured to create an application image based on a virtual disk file of the cloud application;

[0105] The conversion module is configured to acquire an installation file of the cloud application, convert the installation file of the cloud application into a virtual disk file of the cloud application, and store the virtual disk file of the cloud application under a directory of the cloud application in the shared storage.

[0106] In an implementation manner, the conversion module is further configured to acquire an installation file of any plug-in of the cloud application, convert the installation file of the any plug-in into a virtual disk file of the any plug-in, and store the virtual disk file of the any plug-in under a plug-in directory of the cloud application in the shared storage, the any plug-in being a new version of an existing plug-in of the cloud application or a new plug-in of the cloud application.

[0107] In an implementation manner, the apparatus further comprises:

[0108] The sending module is configured to send prompt information to the client of the authorized user, the prompt information being used to prompt that there is a new plug-in or an existing plug-in has a new version.

[0109] The apparatus provided in the embodiments of the present application can be used to execute the plug-in management method of the cloud application in the foregoing embodiments, and has similar implementation principles and technical effects, which will not be repeated here.

[0110] Figure 2 is a structural diagram of a plug-in management apparatus of a cloud application provided in the embodiments of the present application Figure 7 . As shown in Figure 8 , the plug-in management apparatus 700 of the cloud application comprises:

[0111] The sending module 701 is configured to send a cloud application starting instruction to the cloud end in response to an operation of starting the cloud application by a target user.

[0112] The receiving module 702 is configured to receive a user interface of the cloud application returned by the cloud end, wherein a cloud application session of the target user is run based on a virtual disk file of the cloud application mounted by a cloud server instance and a virtual disk file of a target plug-in indicated in plug-in information of the target user, the plug-in information being used to indicate that the target user selects to enable the cloud target plug-in.

[0113] In an implementation manner, the sending module is further configured to:

[0114] In response to an operation of the target user on the plug-in of the cloud application, the sending module is further configured to send a plug-in operation instruction to the cloud end, the plug-in operation instruction being used to enable, disable or upgrade the plug-in and to update the plug-in information.

[0115] The apparatus provided in the embodiments of the present application can be used to execute the plug-in management method of the cloud application in the foregoing embodiments, and has similar implementation principles and technical effects, which will not be repeated here.

[0116] Figure 3 is a structural diagram of a plug-in management apparatus of a cloud application provided in the embodiments of the present applicationFigure 8 As shown in Figure 9 , the plug-in management apparatus 800 of the cloud application comprises:

[0117] a first sending module 801, configured to, in response to an operation of creating an image for the cloud application, send a creation image instruction for the cloud application to the cloud end, the creation image instruction being used to trigger the creation of an application image based on a virtual disk file of the cloud application;

[0118] a second sending module 802, configured to, in response to an operation of creating a delivery group for the application image, send a creation delivery group instruction to the cloud end, the creation delivery group instruction being used to trigger the creation of a cloud server instance based on the application image and the mounting of the virtual disk file of the cloud application, the creation delivery group instruction comprising authorized user information of the cloud application, in a case where a target user in the authorized user starts the cloud application, a cloud application session of the target user is run based on the virtual disk file of the cloud application mounted by the cloud server instance and a virtual disk file of a target plug-in indicated in plug-in information of the target user, the plug-in information being used to indicate that the target user selects to enable the target plug-in.

[0119] In an implementation manner, the apparatus further comprises a third sending module, configured to:

[0120] obtain an installation file of the cloud application, and send the installation file of the cloud application to the cloud end to convert the installation file of the cloud application into a virtual disk file of the cloud application;

[0121] obtain an installation file of any plug-in of the cloud application, and send the installation file of the any plug-in to the cloud end to convert the installation file of the any plug-in into a virtual disk file of the any plug-in, the any plug-in being a new version of an existing plug-in of the cloud application or a new plug-in of the cloud application.

[0122] The apparatus of the embodiment of the application can be used to execute the plug-in management method of the cloud application in the foregoing embodiments, and has similar implementation principles and technical effects, which will not be described herein again.

[0123] The embodiment of the application provides a cloud application system, comprising a cloud end and a first client. The cloud end and the first client are used to implement the method of any of the foregoing embodiments.

[0124] In an implementation manner, the cloud application system further comprises a second client. The second client is used to implement the method of any of the foregoing embodiments.

[0125] Figure 9 is a schematic block diagram of an electronic device provided by the embodiment of the application. As shown in Figure 9 , the electronic device 900 can comprise at least one processor 901, which is used to implement the plug-in management method of the cloud application provided by the embodiment of the application.

[0126] Optionally, the electronic device 900 further comprises at least one memory 902 for storing program instructions and / or data. The memory 902 is coupled with the processor 901. The coupling in the embodiments of the present application is indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, for information interaction between devices, units or modules. The processor 901 can operate in cooperation with the memory 902. The processor 901 can execute program instructions stored in the memory 902. At least one of the at least one memory can be included in the processor.

[0127] Optionally, the electronic device 900 further comprises a communication interface 903 for communicating with other devices through a transmission medium, so that the electronic device 900 can communicate with other devices. The communication interface 903 can be, for example, a transceiver, an interface, a bus, a circuit or a device capable of realizing the transceiving function. The processor 901 can utilize the communication interface 903 to transceive data and / or information, and is used to implement the method provided by the embodiments of the present application. For details, refer to the detailed description in the foregoing embodiments, which will not be repeated here.

[0128] The specific connection medium between the processor 901, the memory 902 and the communication interface 903 is not limited in the embodiments of the present application. In the embodiments of the present application, the processor 901, the memory 902 and the communication interface 903 are connected through a bus 904. Figure 9 The bus 904 is represented by a thick line in the embodiments of the present application, and the connection mode between other components is only schematically illustrated and is not limited. The bus can be divided into an address bus, a data bus, a control bus, etc. For convenience of representation, only one thick line is used to represent the bus in the embodiments of the present application, but it does not mean that there is only one bus or only one type of bus. Figure 9 ​

[0129] ​​It should be understood that the processor in the embodiments of the present application can be an integrated circuit chip with a signal processing capability. In the implementation process, each step of the method embodiments described above can be completed by an integrated logic circuit or an instruction in the form of software in the processor. The processor described above can be a general processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, a discrete gate or transistor logic device, a discrete hardware component. Each method, step and logic block diagram disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as a hardware code processor for execution, or a combination of hardware and software modules in the code processor for execution. The software module can be located in a random access memory, a flash memory, a read only memory, a programmable read only memory or an electrically erasable programmable memory, a register or other mature storage medium in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and combines the hardware to complete the steps of the above method.

[0130] It should also be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically EPROM (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM) used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM) and direct memory bus random access memory (DRAM) (DRAM). It should be noted that the memory of the system and method described herein is intended to include, but not limited to, these and any other suitable types of memory.

[0131] The present application also provides a computer readable storage medium, which stores a computer program (also referred to as code or instructions) that implements the method in any of the preceding embodiments when executed by a processor.

[0132] The present application also provides a computer program product comprising a computer program, which, when executed by a processor, implements the method in any of the preceding embodiments.

[0133] The terms "unit", "module" and the like used in the present specification can be used to represent computer-related entities, hardware, combinations of hardware and software, software, or software in execution.

[0134] Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. The choice of hardware or software, or combinations of both, would be dependent on the specific application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application. In several embodiments provided in the present application, it will be apparent that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the division of the units described above is merely illustrative, and for example, the division of the units is merely a logical function division, and actual implementation can have another division, for example, a plurality of units or components can be combined or integrated into another system, or some features can be omitted or not implemented. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0135] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, i.e. can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiments.

[0136] In addition, the functional units in each of the embodiments of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit.

[0137] In the above embodiments, the functions of the various functional units can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, the software can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, the whole or part of the flow or function according to the embodiments of the present application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transferred from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL) or wireless (such as infrared, wireless, microwave, etc.)) way. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media sets. The available medium can be a magnetic medium (for example, floppy disk, hard disk, magnetic tape), optical medium (for example, digital video disc (DVD)), or semiconductor medium (for example, solid state disk (SSD)) and the like.

[0138] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the part that contributes to the prior art or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk, and various media that can store program codes.

[0139] The user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation portal for user to choose authorization or refusal.

[0140] The above merely provides the specific implementation of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of the changes or replacements within the technical range disclosed by the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A plugin management method for cloud applications, characterized in that, Applied to the cloud, the method includes: Receive a cloud application launch command sent by a first client, wherein the cloud application launch command includes the identifier of the target user; In response to the cloud application launch command, based on the target user's plugin information, the target user's cloud application session is mounted with the virtual disk file of the target plugin. The plugin information is used to instruct the target user to select to enable the target plugin. The target user's cloud application session runs based on the virtual disk file of the cloud application mounted on the cloud server instance and the virtual disk file of the target plugin.

2. The method according to claim 1, characterized in that, The method further includes: Receive the plugin operation instructions from the target user for the cloud application; Based on the plugin operation instructions, mount the virtual disk file of the first plugin and / or unmount the virtual disk file of the second plugin for the target user's cloud application session, and update the plugin information of the target user.

3. The method according to claim 2, characterized in that, The plugin operation command is used to enable the first plugin; The step of mounting the virtual disk file of the first plugin and / or unmounting the virtual disk file of the second plugin for the target user's cloud application session based on the plugin operation instructions, and updating the target user's plugin information, includes: Based on the plugin operation instructions, the virtual disk file of the first plugin is mounted for the target user's cloud application session, and the information of the first plugin is added to the target user's plugin information.

4. The method according to claim 2, characterized in that, The plugin operation command is used to disable the second plugin; The step of mounting the virtual disk file of the first plugin and / or unmounting the virtual disk file of the second plugin for the target user's cloud application session based on the plugin operation instructions, and updating the target user's plugin information, includes: Based on the plugin operation instructions, the virtual disk file of the second plugin is uninstalled for the target user's cloud application session, and the information of the second plugin is deleted from the target user's plugin information.

5. The method according to claim 2, characterized in that, The plugin operation command is used to upgrade the enabled second plugin to the first plugin; The step of mounting the virtual disk file of the first plugin and / or unmounting the virtual disk file of the second plugin for the target user's cloud application session based on the plugin operation instructions, and updating the target user's plugin information, includes: Based on the plugin operation instructions, the virtual disk file of the first plugin is mounted for the cloud application session of the target user, and the virtual disk file of the second plugin is unmounted. The information of the first plugin is added to the plugin information of the target user, and the information of the second plugin is deleted.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Receive a create image instruction for the cloud application, and create an application image based on the virtual disk file of the cloud application; The system receives a create delivery group instruction for the application image, creates a cloud server instance based on the application image, and mounts the virtual disk file of the cloud application. The create delivery group instruction includes the authorized user information of the cloud application, and the target user is any one of the authorized users.

7. The method according to claim 6, characterized in that, Before receiving the image creation instruction for the cloud application, the method further includes: Obtain the installation file of the cloud application, convert the installation file of the cloud application into a virtual disk file of the cloud application, and store the virtual disk file of the cloud application in the directory of the cloud application in shared storage.

8. The method according to claim 7, characterized in that, The method further includes: Obtain the installation file of any plugin of the cloud application, convert the installation file of the arbitrary plugin into a virtual disk file of the arbitrary plugin, and store the virtual disk file of the arbitrary plugin in the plugin directory of the cloud application in the shared storage. The arbitrary plugin is a new version of an existing plugin of the cloud application, or the arbitrary plugin is a new plugin of the cloud application.

9. The method according to claim 8, characterized in that, A notification message is sent to the authorized user's client, indicating the existence of a new plugin or a new version of an existing plugin.

10. A plugin management method for cloud applications, characterized in that, Applied to a first client, the method includes: In response to a target user's action to launch a cloud application, a cloud application launch command is sent to the cloud. The user interface of the cloud application returned by the cloud is received, wherein the cloud application session of the target user runs based on the virtual disk file of the cloud application mounted on the cloud server instance and the virtual disk file of the target plugin indicated in the plugin information of the target user, and the plugin information is used to instruct the target user to select to enable the target plugin.

11. The method according to claim 10, characterized in that, The method further includes: In response to the target user's operation on the plugin of the cloud application, a plugin operation instruction is sent to the cloud. The plugin operation instruction is used to enable, disable or upgrade the plugin and to update the plugin information.

12. A plugin management method for cloud applications, characterized in that, Applied to a second client, the method includes: In response to the operation of creating an image for a cloud application, a creation image instruction for the cloud application is sent to the cloud, the creation image instruction being used to trigger the creation of an application image based on the virtual disk file of the cloud application; In response to the operation of creating a delivery group for the application image, a create delivery group instruction is sent to the cloud. The create delivery group instruction is used to trigger the creation of a cloud server instance based on the application image and mount the virtual disk file of the cloud application. The create delivery group instruction includes the authorized user information of the cloud application. When a target user among the authorized users starts the cloud application, the cloud application session of the target user runs based on the virtual disk file of the cloud application mounted on the cloud server instance and the virtual disk file of the target plugin indicated in the plugin information of the target user. The plugin information is used to instruct the target user to select to enable the target plugin.

13. The method according to claim 12, characterized in that, The method further includes: Obtain the installation file of the cloud application, send the installation file of the cloud application to the cloud, and convert the installation file of the cloud application into a virtual disk file of the cloud application; Obtain the installation file of any plugin of the cloud application, send the installation file of the arbitrary plugin to the cloud, so as to convert the installation file of the arbitrary plugin into a virtual disk file of the arbitrary plugin. The arbitrary plugin is a new version of an existing plugin of the cloud application, or the arbitrary plugin is a new plugin of the cloud application.

14. A cloud application system, characterized in that, include: Cloud and primary client; The cloud is used to implement the method as described in any one of claims 1-9; The first client is used to implement the method as described in claim 10 or 11.

15. The system according to claim 14, characterized in that, Also includes: Second client; The second client is used to implement the method as described in claim 12 or 13.

16. An electronic device, characterized in that, include: Memory and processor; The memory is used to store computer programs; The processor is configured to execute a computer program stored in the memory, wherein the computer program, when executed, causes the processor to perform the method according to any one of claims 1-13.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, causes the processor to perform the method as described in any one of claims 1-13.

18. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method as described in any one of claims 1-13.

Images