Microservices server and storage resource controller

Patent metadata

Field	Value
Publication number	US-12360666-B2
Application number	US-202217585811-A
Country	US
Kind code	B2
Filing date	Jan 27, 2022
Priority date	Jan 27, 2022
Publication date	Jul 15, 2025
Grant date	Jul 15, 2025

Abstract

Aspects of the present disclosure relate to controlling resource consumption of a server and storage array. In embodiments, a request can be received by a server that is communicatively coupled to a storage array. Further, the services required to process the request can be identified. Additionally, services' activation can be controlled based on a mapping of request-related actions and initiated services.

First claim

What is claimed is:

1. A method comprising:
receiving a request by a server communicatively coupled to a storage array;
identifying services required to process the request;
collecting, by a resource monitor, telemetric data from daemons coupled to the services, wherein the daemons record activity levels of their respective resources and services in activity logs;
generating resource activity heatmaps based on the telemetric data by:
analyzing snapshots of the daemon activity logs according to a daemon reporting schedule, and
identifying resources and services having highest and lowest relative activity levels during snapshot windows;

establishing activity level thresholds based on the heatmaps by:
defining an activity level range from the highest and lowest relative activity levels, and
setting thresholds based on the activity level range and identified activity patterns;
wherein the resource monitor manages the daemons using a daemon control signal that defines a daemon reporting schedule based on identified workload patterns;
wherein a workload analyzer includes a machine learning engine that identifies patterns in IO workloads and generates predictive IO workload models; and

controlling the services' activation based on:
comparing service activity levels to the thresholds and a mapping of request-related actions and initiated services,
determining relative importance levels of the services, and
using a mapping of request-related actions and initiated services to selectively activate services having activity levels above a first threshold and deactivate services having activity levels below a second threshold, wherein the mapping includes host-facing API endpoints allocated with IO processing resources and corresponding instruction blocks that define rules for activating and deactivating services.

2. The method of claim 1 , further comprising:
generating a resource mapping, defining relationships between the request-related actions and the services initiated to process the request-related actions; and
monitoring consumption and use of the services using the collected telemetric data.

3. The method of claim 2 , further comprising:
collecting telemetric data from the server and storage array in response to receiving the request; and
analyzing the collected telemetric data.

4. The method of claim 3 , further comprising:
monitoring consumption and use of one or more of the server and storage array resources to process the request using the collected telemetric data.

5. The method of claim 4 , further comprising:
comparing one or more of the server and storage array resource consumptions to a threshold.

6. The method of claim 1 , further comprising:
determining if one or more of the initiated services include grouped services, wherein each service of the grouped services is activated by default if any service of the group services is initiated.

7. The method of claim 6 , further comprising:
determining whether each service of the grouped services is necessary to process the request-related actions.

8. The method of claim 6 , further comprising:
logically decoupling the grouped services.

9. The method of claim 4 , further comprising:
generating one or more service consumption models using the server and storage array resource mappings.

10. The method of claim 1 , further comprising:
controlling service initiation based on one or more of the service consumptions models and the resource mappings, wherein controlling service initiation includes activating or suspending one or more services of one or more grouped services.

11. An apparatus including a memory and processor configured to:
receive a request by a server communicatively coupled to a storage array;
identify services required to process the request;
collect, by a resource monitor, telemetric data from daemons coupled to the services, wherein the daemons record activity levels of their respective resources and services in activity logs;
generate resource activity heatmaps based on the telemetric data by:
analyzing snapshots of the daemon activity logs according to a daemon reporting schedule, and
identifying resources and services having highest and lowest relative activity levels during snapshot windows;

establish activity level thresholds based on the heatmaps by:
defining an activity level range from the highest and lowest relative activity levels, and
setting thresholds based on the activity level range and identified activity patterns;
wherein the resource monitor manages the daemons using a daemon control signal that defines a daemon reporting schedule based on identified workload patterns;
wherein a workload analyzer includes a machine learning engine that identifies patterns in IO workloads and generates predictive IO workload models; and

control the services' activation based on;
comparing service activity levels to the thresholds and a mapping of request-related actions and initiated services,
determining relative importance levels of the services, and
using a mapping of request-related actions and initiated services to selectively activate services having activity levels above a first threshold and deactivate services having activity levels below a second threshold, wherein the mapping includes host-facing API endpoints allocated with IO processing resources and corresponding instruction blocks that define rules for activating and deactivating services.

12. The apparatus of claim 11 , further configured to:
generate a resource mapping, defining relationships between the request-related actions and the services initiated to process the request-related actions; and
monitor consumption and use of the services using the collected telemetric data.

13. The apparatus of claim 12 , further configured to:
collect telemetric data from the server and storage array in response to receiving the request; and
analyze the collected telemetric data.

14. The apparatus of claim 13 , further configured to:
monitor consumption and use of one or more of the server and storage array resources to process the request using the collected telemetric data.

15. The apparatus of claim 14 , further configured to:
compare one or more of the server and storage array resource consumptions to a threshold.

16. The apparatus of claim 11 , further configured to:
determine if one or more of the initiated services include grouped services, wherein each service of the grouped services is activated by default if any service of the group services is initiated.

17. The apparatus of claim 16 , further configured to:
determine whether each service of the grouped services is necessary to process the request-related actions.

18. The apparatus of claim 16 , further configured to:
logically decouple the grouped services.

19. The apparatus of claim 14 , further configured to:
generate one or more service consumption models using the server and storage array resource mappings.

20. The apparatus of claim 11 , further configured to:
control service initiation based on one or more of the service consumptions models and the resource mappings, wherein controlling service initiation includes activating or suspending one or more services of one or more grouped services.

Assignees

• Dell Products Lp

Inventors

• Mcsweeney Paul
• O'Maolcatha Fearghal
• Holland Elaine

Classifications

• G06F2209/5019

  Workload prediction · CPC title

• G06F9/5072 Primary

  Grid computing · CPC title

• G06F9/5011

  the resources being hardware resources other than CPUs, Servers and Terminals · CPC title

• G06F3/0653

  Monitoring storage devices or systems · CPC title

• G06F3/0604 Primary

  Improving or facilitating administration, e.g. storage management · CPC title