IP Library Granted Patent US 11,500,683
Granted Patent B2
US 11,500,683 · App. 17/083,455 · Granted Nov 15, 2022

Workload compliance governor system

Inventors: Mukund P. Khatri (Austin, TX); Gaurav Chawla (Austin, TX); William Price Dawkins (Lakeway, TX); Elie Jreij (Pflugerville, TX); Mark Steven Sanders (Roanoke, VA); Walter A. O'Brien, III (Westborough, MA); Robert W. Hormuth (Cedar Park, TX); Jimmy D. Pike (Georgetown, TX)
Assignee: Dell Products L.P.
G06F9/5044G06F9/505G06F9/5083
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,500,683
App. No.
17/083,455
Granted
Nov 15, 2022
Kind
B2
Abstract

A workload compliance governor system includes a management system coupled to a computing system. A workload compliance governor subsystem in the computing system receives a workload performance request associated with a workload, exchanges hardware compose communications with the management system to compose hardware components for the workload, and receives back an identification of hardware components. The workload compliance governor subsystem then determines that the identified hardware components satisfy hardware compliance requirements for the workload, and configures the identified hardware components in the computing system based on the software compliance requirements for the workload in order to cause those identified hardware components to provide an operating system and at least one application that operate to perform the workload.

Claims (61)

1. A workload compliance governor system, comprising:

a management system;

a computing system that is coupled to the management system via a network; and

a workload compliance governor subsystem that is included in the computing system and that is configured to:

receive a first workload performance request that identifies first hardware compliance requirements and first software compliance requirements for performing a first workload;

exchange, with the management system based on the first hardware compliance requirements in the first workload performance request, first hardware compose communications to compose a plurality of hardware components for the first workload;

receive, from the management system in response to the first hardware compose communications, an identification of a plurality of first hardware components for use in performing the first workload;

determine that the plurality of first hardware components satisfy the first hardware compliance requirements for the first workload; and

configure, in response to determining that the plurality of first hardware components satisfy the first hardware compliance requirements for the first workload, the plurality of first hardware components in the computing system based on the first software compliance requirements for the first workload in order to cause the plurality of first hardware components in the computing system to provide an operating system and at least one application that operate to perform the first workload.

2. The system of claim 1 , wherein the workload compliance governor subsystem is configured to:

receive a second workload performance request that identifies second hardware compliance requirements and second software compliance requirements for performing a second workload;

exchange, with the management system based on the second hardware compliance requirements in the second workload performance request, second hardware compose communications to compose a plurality of hardware components for the second workload;

receive, from the management system in response to the second hardware compose communications, an identification of a plurality of second hardware components for use in performing the second workload;

determine that the plurality of second hardware components do not satisfy the second hardware compliance requirements for the second workload; and

transmit, to the management system in response to determining that the plurality of second hardware components satisfy the second hardware compliance requirements for the second workload, a hardware non-compliance communication that indicates that the computing system cannot satisfy the second hardware compliance requirements for performing the second workload.

3. The system of claim 1 , wherein the first hardware compliance requirements for performing the first workload include at least one of a processor system requirement, a memory system requirement, a storage system requirement, a Federal Information Processing Standard (FIPS) requirement, a Trusted Platform Module (TPM) requirement, a Secure Encrypted Drive (SED) requirement, or a latency requirement.

4. The system of claim 1 , wherein the configuring the plurality of first hardware components in the computing system based on the first software compliance requirements include configuring at least one of firmware, Basic Input/Output System (BIOS) settings, or Baseboard Management Controller (BMC) settings.

5. The system of claim 1 , wherein the configuring the plurality of first hardware components in the computing system based on the first software compliance requirements for the first workload include configuring at least one of a secure boot process, a Trusted Platform Module (TPM), an active directory, or a Federal Information Processing Standard (FIPS) mode.

6. The system of claim 1 , wherein the workload compliance governor subsystem is configured, subsequent to configuring the plurality of first hardware components in the computing system to provide an operating system and at least one application that operate to perform the first workload, to:

perform a runtime compliance check of the first hardware compliance requirements and the first software compliance requirements for performing the first workload.

7. An Information Handling System (IHS), comprising:

a processing system; and

a memory system that is coupled to the processing system and that includes instructions that, when executed by the processing system, cause the processing system to provide a workload compliance governor engine that is configured to:

receive a first workload performance request that identifies first hardware compliance requirements and first software compliance requirements for performing a first workload;

exchange, with a management system based on the first hardware compliance requirements in the first workload performance request, first hardware compose communications to compose a plurality of hardware components for the first workload;

receive, from the management system in response to the first hardware compose communications, an identification of a plurality of first hardware components for use in performing a first workload;

determine that the plurality of first hardware components satisfy the first hardware compliance requirements for the first workload; and

configure, in response to determining that the plurality of first hardware components satisfy the first hardware compliance requirements for the first workload, the plurality of first hardware components in the computing system based on the first software compliance requirements for the first workload in order to cause the plurality of first hardware components to provide an operating system and at least one application that operate to perform the first workload.

8. The IHS of claim 7 , wherein the workload compliance governor engine is configured to:

receive a second workload performance request that identifies second hardware compliance requirements and second software compliance requirements for performing a second workload;

exchange, with the management system based on the second hardware compliance requirements in the second workload performance request, second hardware compose communications to compose a plurality of hardware components for the second workload;

receive, from the management system in response to the second hardware compose communications, an identification of a plurality of second hardware components for use in performing a second workload;

determine that the plurality of second hardware components do not satisfy the second hardware compliance requirements for the second workload; and

transmit, to the management system in response to determining that the plurality of second hardware components do not satisfy the second hardware compliance requirements for the second workload, hardware non-compliance communication that indicates that the second hardware compliance requirements for performing the second workload cannot be satisfied.

9. The IHS of claim 7 , wherein the first hardware compliance requirements for performing the first workload include at least one of a processor system requirement, a memory system requirement, a storage system requirement, a Federal Information Processing Standard (FIPS) requirement, a Trusted Platform Module (TPM) requirement, a Secure Encrypted Drive (SED) requirement, or a latency requirement.

10. The IHS of claim 7 , wherein the configuring the plurality of first hardware components in the computing system based on the first software compliance requirements include configuring at least one of firmware, Basic Input/Output System (BIOS) settings, or Baseboard Management Controller (BMC) settings.

11. The IHS of claim 7 , wherein the configuring the plurality of first hardware components in the computing system based on the first software compliance requirements for the first workload include configuring at least one of a secure boot process, a Trusted Platform Module (TPM), an active directory, or a Federal Information Processing Standard (FIPS) mode.

12. The IHS of claim 7 , wherein the workload compliance governor engine is configured, subsequent to configuring the plurality of first hardware components in the computing system to provide an operating system and at least one application that operate to perform the first workload, to:

perform a runtime compliance check of the first hardware compliance requirements and the first software compliance requirements for performing the first workload.

13. The IHS of claim 7 , wherein the workload compliance governor engine is configured, subsequent to configuring the plurality of first hardware components in the computing system to provide an operating system and at least one application that operate to perform the first workload, to perform a subsequent compliance check in response to at least one of:

a boot operation, a subsequent compliance check request, the detection of a second hardware component, the detection of second software.

14. A method for governing workload compliance in a computing system, comprising:

receiving, by a workload compliance governor subsystem in a computing system, a first workload performance request that identifies first hardware compliance requirements and first software compliance requirements for performing a first workload;

exchanging, by the workload compliance governor subsystem with a management system based on the first hardware compliance requirements in the first workload performance request, first hardware compose communications to compose a plurality of hardware components for the first workload;

receiving, by the workload compliance governor subsystem from the management system in response to the first hardware compose communications, an identification of a plurality of first hardware components for use in performing a first workload;

determining, by the workload compliance governor subsystem, that the plurality of first hardware components satisfy the first hardware compliance requirements for the first workload; and

configuring, by the workload compliance governor subsystem in response to determining that the plurality of first hardware components satisfy the first hardware compliance requirements for the first workload, the plurality of first hardware components in the computing system based on the first software compliance requirements for the first workload in order to cause the plurality of first hardware components to provide an operating system and at least one application that operate to perform the first workload.

15. The method of claim 14 , further comprising:

receiving, by the workload compliance governor subsystem, a second workload performance request that identifies second hardware compliance requirements and second software compliance requirements for performing a second workload;

exchanging, by the workload compliance governor subsystem with the management system based on the second hardware compliance requirements in the second workload performance request, second hardware compose communications to compose a plurality of hardware components for the second workload;

receiving, by the workload compliance governor subsystem from the management system in response to the second hardware compose communications, an identification of a plurality of second hardware components for use in performing a second workload;

determining, by the workload compliance governor subsystem, that the plurality of second hardware components do not satisfy the second hardware compliance requirements for the second workload; and

transmitting, by the workload compliance governor subsystem to the management system in response to determining that the plurality of second hardware components satisfy the second hardware compliance requirements for the second workload, a hardware non-compliance communication that indicates that the second hardware compliance requirements for performing the second workload cannot be satisfied.

16. The method of claim 14 , wherein the first hardware compliance requirements for performing the first workload include at least one of a processor system requirement, a memory system requirement, a storage system requirement, a Federal Information Processing Standard (FIPS) requirement, a Trusted Platform Module (TPM) requirement, a Secure Encrypted Drive (SED) requirement, or a latency requirement.

17. The method of claim 14 , wherein the configuring the plurality of first hardware components in the computing system based on the first software compliance requirements include configuring at least one of firmware, Basic Input/Output System (BIOS) settings, or Baseboard Management Controller (BMC) settings.

18. The method of claim 14 , wherein the configuring the plurality of first hardware components in the computing system based on the first software compliance requirements for the first workload include configuring at least one of a secure boot process, a Trusted Platform Module (TPM), an active directory, or a Federal Information Processing Standard (FIPS) mode.

19. The method of claim 14 , further comprising:

performing, by the workload compliance governor subsystem subsequent to configuring the plurality of first hardware components in the computing system to provide an operating system and at least one application that operate to perform the first workload, a runtime compliance check of the first hardware compliance requirements and the first software requirements for performing the first workload.

20. The method of claim 14 , further comprising:

performing, by the workload compliance governor subsystem subsequent to configuring the plurality of first hardware components in the computing system to provide an operating system and at least one application that operate to perform the first workload, a subsequent compliance check in response to at least one of:

a boot operation for the computing system, a subsequent compliance check request, the detection of a second hardware component, the detection of second software.

Assignments (9)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (054475/0523) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
Reel/Frame 060332/0664 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (054475/0434) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
Reel/Frame 060332/0740 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (054475/0609) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
Reel/Frame 062021/0570 →
RELEASE OF SECURITY INTEREST AT REEL 054591 FRAME 0471 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 058001/0463 →
SECURITY INTEREST Recorded Nov 18, 2020
From: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 054475/0609 →
SECURITY INTEREST Recorded Nov 18, 2020
From: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 054475/0434 →
SECURITY INTEREST Recorded Nov 18, 2020
From: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 054475/0523 →
SECURITY AGREEMENT Recorded Nov 13, 2020
From: EMC IP HOLDING COMPANY LLC; DELL PRODUCTS L.P.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 054591/0471 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 29, 2020
From: KHATRI, MUKUND P.; CHAWLA, GAURAV; DAWKINS, WILLIAM PRICE; JREIJ, ELIE; SANDERS, MARK STEVEN; O'BRIEN, WALTER A., III; HORMUTH, ROBERT W.; PIKE, JIMMY D.
To: DELL PRODUCTS L.P.
Reel/Frame 054249/0392 →