QUALITY OF SERVICE SETTING

• US 20160197794A1
• Filed: 12/16/2015
• Published: 07/07/2016
• Est. Priority Date: 01/04/2015
• Status: Abandoned Application

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Wang, Grissom Tianqing, Peng, Layne Lin, Zhang, Vivian Yun, Chen, Roby Qiyan, Yan, Kay Kai
• Application Number:
  US14/971,006
• Publication Number:
  US 20160197794A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 41/5058 Service discovery by the service manager
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• CPC Class Codes: H04L 45/02 Topology update or discovery

Abstract

Embodiments of the disclosure relate to a method and apparatus for improving quality of service setting. According to an embodiment of the disclosure, the method comprises: obtaining an abstract QoS from a converged QoS profile, wherein the converged QoS profile indicates a mapping relationship between a converged QoS and the abstract QoS; mapping the abstract QoS to a vendor specific QoS; and implementing QoS setting on the obtained component related to the given application, based on the mapped vendor specific QoS. By introducing a centralized and converged QoS controller, the method simplifies QoS setting and improves the efficiency of QoS setting along the virtual application stack.

Claims

1. A method of setting quality of service (QoS), comprising:

obtaining a component related to a given application;

obtaining an abstract QoS from a converged QoS profile, wherein the converged QoS profile indicates a mapping relationship between a converged QoS and the abstract QoS;

mapping the abstract QoS to a vendor specific QoS; and

implementing QoS setting on the obtained component related to the given application, based on the mapped vendor specific QoS.

2. A method according to claim 1, wherein:

the component comprises at least one of a compute related component, a storage related component and a network related component;

the abstract QoS comprises at least one of an abstract compute QoS, an abstract storage QoS and an abstract network QoS; and

the vendor specific QoS comprises at least one of a vendor specific compute QoS, a vendor specific storage QoS and a vendor specific network QoS.

3. The method according to claim 1, wherein obtaining a component related to a given application comprises:

obtaining the component by interacting with a management module of each layer in a layered architecture of a data center.

4. The method according to claim 1, further comprises:

obtaining component information related to an application instance by interacting with a management module of each layer in a layered architecture of a data center, and

storing the obtained component information related to the application instance in a topology repository, and

wherein obtaining a component related to a given application instance includes;

obtaining the component by querying the topology repository.

5. The method according to claim 4, wherein obtaining component information related to an application instance by interacting with a management module of each layer in a layered architecture of a data center comprises:

obtaining the component information related to an application by interacting with at least one of the followings;

a management module for Software-as-a-service (SaaS);

a management module for Platform-as-a-service (PaaS);

a management module for Infrastructure-as-a-service (IaaS); and

a management module for Infrastructure.

6. The method according to claim 1, wherein mapping the abstract QoS to a vendor specific QoS comprises:

mapping the abstract QoS to a vendor specific QoS by loading a corresponding QoS driver.

7. The method according to any of claims 1-6, further comprises at least one of the followings:

defining the converged QoS profile;

storing the converged QoS profile; and

defining a key performance indicator (KPI) for at least one of an abstract compute QoS, an abstract storage QoS and an abstract network QoS.

8. A system, comprising:

a data center, including data storage systems; and

computer-executable program logic encoded in memory of one or more computers enabled to set quality of service (QoS) within the data center, wherein the computer-executable program logic is configured for the execution of;

obtaining a component related to a given application;

obtaining an abstract QoS from a converged QoS profile, wherein the converged QoS profile indicates a mapping relationship between a converged QoS and the abstract QoS;

mapping the abstract QoS to a vendor specific QoS; and

implementing QoS setting on the obtained component related to the given application, based on the mapped vendor specific QoS.

9. The system of claim 8, wherein:

the component comprises at least one of a compute related component, a storage related component and a network related component;

the abstract QoS comprises at least one of an abstract compute QoS, an abstract storage QoS and an abstract network QoS; and

the vendor specific QoS comprises at least one of a vendor specific compute QoS, a vendor specific storage QoS and a vendor specific network QoS.

10. The system of claim 8, wherein obtaining a component related to a given application comprises:

obtaining the component by interacting with a management module of each layer in a layered architecture of a data center.

11. The system of claim 8, wherein the computer-executable program logic is further configured for the execution of:

obtaining component information related to an application instance by interacting with a management module of each layer in a layered architecture of a data center, and

storing the obtained component information related to the application instance in a topology repository, and

wherein obtaining a component related to a given application instance includes;

obtaining the component by querying the topology repository.

12. The system of claim 11, wherein obtaining component information related to an application instance by interacting with a management module of each layer in a layered architecture of a data center comprises:

obtaining the component information related to an application by interacting with at least one of the followings;

a management module for Software-as-a-service (SaaS);

a management module for Platform-as-a-service (PaaS);

a management module for Infrastructure-as-a-service (IaaS); and

a management module for Infrastructure.

13. The system of claim 8, wherein mapping the abstract QoS to a vendor specific QoS comprises:

mapping the abstract QoS to a vendor specific QoS by loading a corresponding QoS driver.

14. The system of claim 8, wherein the computer-executable program logic is further configured for the execution of at least one of the followings:

defining the converged QoS profile;

storing the converged QoS profile; and

defining a key performance indicator (KPI) for at least one of an abstract compute QoS, an abstract storage QoS and an abstract network QoS.

15. A computer program product of setting quality of service (QoS), the computer program product comprising:

a non-transitory computer readable medium encoded with computer-executable code, the code configured to enable the execution of;

obtaining a component related to a given application;

obtaining an abstract QoS from a converged QoS profile, wherein the converged QoS profile indicates a mapping relationship between a converged QoS and the abstract QoS;

mapping the abstract QoS to a vendor specific QoS; and

implementing QoS setting on the obtained component related to the given application, based on the mapped vendor specific QoS.

16. The computer program product of claim 15, wherein:

the component comprises at least one of a compute related component, a storage related component and a network related component;

the abstract QoS comprises at least one of an abstract compute QoS, an abstract storage QoS and an abstract network QoS; and

the vendor specific QoS comprises at least one of a vendor specific compute QoS, a vendor specific storage QoS and a vendor specific network QoS.

17. The computer program product of claim 15, wherein obtaining a component related to a given application comprises:

obtaining the component by interacting with a management module of each layer in a layered architecture of a data center.

18. The computer program product of claim 15, wherein the code is further configured to enable the execution of:

obtaining component information related to an application instance by interacting with a management module of each layer in a layered architecture of a data center, and

storing the obtained component information related to the application instance in a topology repository, and

wherein obtaining a component related to a given application instance includes;

obtaining the component by querying the topology repository.

19. The computer program product of claim 18, wherein obtaining component information related to an application instance by interacting with a management module of each layer in a layered architecture of a data center comprises:

obtaining the component information related to an application by interacting with at least one of the followings;

a management module for Software-as-a-service (SaaS);

a management module for Platform-as-a-service (PaaS);

a management module for Infrastructure-as-a-service (IaaS); and

a management module for Infrastructure.

20. The computer program product of claim 15, wherein mapping the abstract QoS to a vendor specific QoS comprises:

mapping the abstract QoS to a vendor specific QoS by loading a corresponding QoS driver.