Method, device and computer program product for performing applications in hybrid cloud

Patent metadata

Field	Value
Publication number	US-10877776-B2
Application number	US-201916244937-A
Country	US
Kind code	B2
Filing date	Jan 10, 2019
Priority date	Jan 18, 2018
Publication date	Dec 29, 2020
Grant date	Dec 29, 2020

Abstract

Embodiments of the present disclosure provide a method, device and computer program product for executing applications in a hybrid cloud. The method comprises in response to receiving a request for executing the application from a user, obtaining an application identifier for the application from the request. The method also comprises determining, based on the application identifier and a scheduling strategy associated with the application, an executable file identifier corresponding to the application. The method further comprises obtaining, from a repository associated with the hybrid cloud, an executable file of the application corresponding to the executable file identifier, the executable file being associated with a type of a heterogeneous device in a hybrid cloud. By utilizing the above method, users can rapidly execute the application without considering the type of the heterogeneous device in the hybrid cloud.

First claim

What is claimed is:

1. A method of executing an application in a hybrid cloud, comprising:
in response to receiving a request for executing the application from a user, obtaining an application identifier for the application from the request;
determining, based on the application identifier and a scheduling strategy associated with the application, an executable file identifier corresponding to the application; and
obtaining, from a repository associated with the hybrid cloud, an executable file of the application corresponding to the executable file identifier, the executable file being associated with a type of a heterogeneous device in the hybrid cloud;
wherein determining the executable file identifier comprises:
determining, based on the application identifier and the scheduling strategy, a cloud identifier and a device identifier from metadata, the metadata comprising the application identifier, the cloud identifier, the device identifier and information related to at least one of device performance, a usage cost, and security; and
determining the executable file identifier from the repository based on the application identifier, the cloud identifier and the device identifier.

2. The method of claim 1 , further comprising:
deploying the executable file into a heterogeneous device in the hybrid cloud to obtain an execution result snapshot of the application; and
determining an output of the application based on an initial snapshot of the application and the execution result snapshot of the application.

3. The method of claim 2 , wherein the execution result snapshot of the application comprises a snapshot of a file list associated with the application after the application execution is completed.

4. The method of claim 3 , wherein determining the output of the application based on the initial snapshot of the application and the execution result snapshot of the application comprises identifying at least one of files and data altered in operation of the application based on the file list associated with the application after the application execution is completed.

5. The method of claim 1 , further comprising:
in response to an application installation request from the user, obtaining source code of the application;
obtaining a type of the heterogeneous device in the hybrid cloud from configuration information of the hybrid cloud;
generating, based on the type of the heterogeneous device and from the source code, the executable file corresponding to the type of the heterogeneous device; and
storing the executable file in the repository.

6. The method of claim 5 , wherein storing the executable file in the repository comprises:
storing the executable file in the repository in association with at least one of the application identifier, the executable file identifier, the cloud identifier and the device identifier.

7. The method of claim 5 , further comprising:
in response to the generation of the executable file, storing the metadata of the application in metadata storage of a hybrid cloud tool, the metadata comprising the application identifier, the cloud identifier, the device identifier and the information related to at least one of device performance, a usage cost, and security.

8. The method of claim 1 , further comprising:
verifying the user based on account information of the user and the application identifier.

9. The method of claim 1 , further comprising:
determining a current scheduling strategy based on at least one of a scheduling strategy previously used for the application by the user and a scheduling strategy used for the application by a further user.

10. The method of claim 1 , wherein the executable file of the application corresponding to the executable file identifier comprises one of a plurality of executable files stored in the repository for the application, each of the plurality of executable files being associated with a different type of heterogeneous device available in the hybrid cloud.

11. An electronic device for executing an application in a hybrid cloud, the electronic device comprising:
a processor; and
a memory having computer program instructions stored thereon, the processor executing the computer program instructions in the memory to control the electronic device to perform actions comprising:
in response to receiving a request for executing the application from a user, obtaining an application identifier for the application from the request;
determining, based on the application identifier and a scheduling strategy associated with the application, an executable file identifier corresponding to the application; and
obtaining, from a repository associated with the hybrid cloud, an executable file of the application corresponding to the executable file identifier, the executable file being associated with a type of a heterogeneous device in the hybrid cloud;
wherein determining the executable file identifier comprises:
determining, based on the application identifier and the scheduling strategy, a cloud identifier and a device identifier from metadata, the metadata comprising the application identifier, the cloud identifier, the device identifier and information related to at least one of device performance, a usage cost, and security; and
determining the executable file identifier from the repository based on the application identifier, the cloud identifier and the device identifier.

12. The electronic device of claim 11 , wherein the actions further comprise:
deploying the executable file into a heterogeneous device in the hybrid cloud to obtain an execution result snapshot of the application; and
determining an output of the application based on an initial snapshot of the application and the execution result snapshot of the application.

13. The electronic device of claim 11 , wherein the actions further comprise:
in response to an application installation request from a user, obtaining source code of the application;
obtaining a type of the heterogeneous device in the hybrid cloud from configuration information of the hybrid cloud;
generating, based on the type of the heterogeneous device and from the source code, the executable file corresponding to the type of the heterogeneous device; and
storing the executable file in the repository.

14. The electronic device of claim 13 , wherein storing the executable file in the repository comprises:
storing the executable file in the repository in association with at least one of the application identifier, the executable file identifier, the cloud identifier and the device identifier.

15. The electronic device of claim 13 , wherein the actions further comprise:
in response to the generation of the executable file, storing the metadata of the application in a metadata storage of a hybrid cloud tool, the metadata comprising the application identifier, the cloud identifier, the device identifier and the information related to at least one of device performance, a usage cost, and security.

16. The electronic device of claim 11 , wherein the actions further comprise:
verifying the user based on account information of the user and the application identifier.

17. The electronic device of claim 11 , wherein the actions further comprise:
determining a current scheduling strategy based on at least one of a scheduling strategy previously used for the application by the user and a scheduling strategy used for the application by a further user.

18. A computer program product being tangibly stored on a non-volatile computer readable me

Assignees

• Dell Products Lp

Inventors

• Chen Fei
• Liu Fucai
• Wang Kun

Classifications

• G06F9/44542

  Retargetable · CPC title

• G06F9/44568

  Immediately runnable code · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• G06F9/44547 Primary

  Fat binaries · CPC title

• G06F9/4881

  Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues · CPC title