System and method for a workload management and scheduling module to manage access to a compute environment according to local and non-local user identity information

• US 10,379,909 B2
• Filed: 05/12/2015
• Issued: 08/13/2019
• Est. Priority Date: 08/20/2004
• Status: Active Grant

• Current Assignee: III Holdings 12, LLC (Intellectual Ventures LLC)
• Original Assignee: III Holdings 12, LLC (Intellectual Ventures LLC)
• Inventors: Jackson, David B.
• Primary Examiner(s): An, Meng Ai T
• Assistant Examiner(s): Huaracha, Willy W
• Application Number:
  US14/709,642
• Publication Number:
  US 20150242244A1
• Time in Patent Office: 1,554 Days
• Field of Search: 718100
• CPC Class Codes: G06F 21/305 by remotely controlling device operation
• CPC Class Codes: G06F 2209/483 Multiproc
• CPC Class Codes: G06F 9/44552 Conflict resolution, i.e. enabling coexistence of conflicting executables
• CPC Class Codes: G06F 9/468 Specific access rights for resources, e.g. using capability register
• CPC Class Codes: G06F 9/4881 Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
• CPC Class Codes: G06F 9/5072 Grid computing

Abstract

A system, method and computer-readable media for managing a compute environment are disclosed. The method includes importing identity information from an identity manager into a module performs workload management and scheduling for a compute environment and, unless a conflict exists, modifying the behavior of the workload management and scheduling module to incorporate the imported identity information such that access to and use of the compute environment occurs according to the imported identity information. The compute environment may be a cluster or a grid wherein multiple compute environments communicate with multiple identity managers.

Claims

1. A method for managing a compute environment, comprising:

periodically exporting locally-obtained identity information to an identity manager of a first compute environment as new identity information is discovered by a management module of the first compute environment;

in the event that workload needs to be transferred from the first compute environment to a second environment, allowing a management module of the second compute environment to access the identity information maintained by the identity manager of the first compute environment to ensure that user constraints are maintained for the workload when consuming resources of the second compute environment;

periodically importing identity information from the identity manager of the first compute environment into the management module that schedules workload that consumes resources in the first compute environment, wherein the identity information comprises exported local utilization of resources and credentials associated with at least one of users, groups of users, accounts, projects, classes, queues, and qualities of service;

resolving a conflict between exported identity information and local configuration information to yield a resolution, wherein the local configuration information comprises information on arrangement of computers and computer types in the first compute environment, and resolving the conflict comprises determining a priority between the exported identity information and the local configuration information of the first compute environment by applying precedent rules that determine whether the exported identity information or the local configuration information has precedence; and

modifying a behavior of the management module of the first compute environment to incorporate the identity information such that a scheduling decision associated with a location of resources in the first compute environment is based at least in part on the exported identity information and the resolution.

2. The method of claim 1, wherein the first compute environment is a different entity than the identity manager.

3. The method of claim 1, wherein the identity manager is at least one of:

a text file, a database, and a service.

4. The method of claim 1, wherein the management module further comprises at least one of a resource manager, a grid manager, a cluster scheduler, and a workload manager.

5. The method of claim 1, wherein importing identity information from the identity manager further comprises importing identity information from a plurality of identity managers.

6. The method of claim 5, wherein each identity manager of the plurality of identity managers has a different type of information.

7. The method of claim 1, wherein the identity manager further comprises information associated with at least one of default credential associations and credential specification constraints.

8. The method of claim 7, wherein the default credential associations define credentials for users where no specified constraints exist and credential specification constraints further comprise constraints related to at least one of:

a service level agreement, priority information, usage limit information, fairshare targets, service guarantees, resource constraints, usage statistics, contact information, and billing information.

9. The method of claim 1, wherein the identity manager is associated with a service that receives identity information from any location including the management module.

10. The method of claim 9, wherein the identity manager receives identity information from at least one of:

the Internet, administrator input, another identity manager, and another management module.

11. The method of claim 1, wherein the management module obtains a global view of users and groups based on the identity information and from locally-obtained identity information.

12. The method of claim 1, wherein the identity information from the identity manager comprises a subset of the identity information in the identity manager that is relevant to the first compute environment managed by the management module.

13. The method of claim 1, wherein a plurality of identity managers and a plurality of management modules import and export the identity information.

14. The method of claim 1, wherein if the conflict is resolved in favor of the local configuration information, then the management module manages access to and use of the first compute environment according to the local configuration information.

15. The method of claim 1, wherein the computer types in the configuration information includes any one of hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, and mainframe computers.

16. A system for managing a compute environment, the system comprising:

a processor; and

a non-transitory computer-readable storage medium storing instructions, which, when executed by the processor, cause the processor to perform operations comprising;

periodically exporting locally-obtained identity information to an identity manager of a first compute environment as new identity information is discovered by a management module of the first compute environment;

in the event that workload needs to be transferred from the first compute environment to a second environment, allowing a management module of the second compute environment to access the identity information maintained by the identity manager of the first compute environment to ensure that user constraints are maintained for the workload when consuming resources of the second compute environment;

periodically importing identity information from the identity manager of the first compute environment into the management module that schedules workload that consumes resources in the first compute environment, wherein the identity information comprises exported local utilization of resources and credentials associated with at least one of users, groups of users, accounts, projects, classes, queues, and qualities of service;

resolving a conflict between exported identity information and local configuration information to yield a resolution, wherein the local configuration information comprises information on arrangement of computers and computer types in the first compute environment, and resolving the conflict comprises determining a priority between the exported identity information and the local configuration information of the first compute environment by applying precedent rules that determine whether the exported identity information or the local configuration information has precedence; and

modifying a behavior of the management module of the first compute environment to incorporate the identity information such that a scheduling decision associated with a location of resources in the first compute environment is based at least in part on the exported identity information and the resolution.

17. A non-transitory computer-readable storage device storing instructions for managing a compute environment, which, when executed by a processor, cause the processor to perform operations comprising:

periodically exporting locally-obtained identity information to an identity manager of a first compute environment as new identity information is discovered by a management module of the first compute environment;

in the event that workload needs to be transferred from the first compute environment to a second environment, allowing a management module of the second compute environment to access the identity information maintained by the identity manager of the first compute environment to ensure that user constraints are maintained for the workload when consuming resources of the second compute environment;

periodically importing identity information from the identity manager of the first compute environment into the management module that schedules workload that consumes resources in the first compute environment, wherein the identity information comprises exported local utilization of resources and credentials associated with at least one of users, groups of users, accounts, projects, classes, queues, and qualities of service;

resolving a conflict between exported identity information and local configuration information to yield a resolution, wherein the local configuration information comprises information on arrangement of computers and computer types in the first compute environment, and resolving the conflict comprises determining a priority between the exported identity information and the local configuration information of the first compute environment by applying precedent rules that determine whether the exported identity information or the local configuration information has precedence; and

modifying a behavior of the management module of the first compute environment to incorporate the identity information such that a scheduling decision associated with a location of resources in the first compute environment is based at least in part on the exported identity information and the resolution.