Browse Prior Art Database

Method and System for Utilizing a Distributed Resource Scheduler with Enhanced anti-affinity Rule set based on Server Naming Conventions and Application Identification

IP.com Disclosure Number: IPCOM000233594D
Publication Date: 2013-Dec-17
Document File: 3 page(s) / 115K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system is disclosed for utilizing a Distributed Resource Scheduler (DRS) with enhanced anti-affinity rule set based on server naming conventions and application identification. The method and system considers affinity, anti-affinity rules based on applications running on a virtual system as well as the identified server function, database system and webserver for the DRS.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 61% of the total text.

Page 01 of 3

Method and System for Utilizing a Distributed Resource Scheduler with Enhanced anti-affinity Rule set based on Server Naming Conventions and Application Identification

Disclosed is a method and system for utilizing a Distributed Resource Scheduler (DRS) with enhanced anti-affinity rule set based on server naming conventions and application identification.

The method and system utilizes a rule generator which pulls data from several sources. Thereafter, information such as Application Identification Number (AIM) ID is gathered and a server naming convention is used to build anti-affinity rules. After this, data is used to ensure that applications having more than a single virtual system in a physical node cluster monitor a physical host. The physical node cluster ensures that no physical host executes more than one virtual machine (VM) with the same server function. Here, server function is defined as one of a database server and a web server.

Figure 1 illustrates the overall architecture of the system, wherein the AIM provides its ID to the configuration management database (CMDB). The CMDB transfers CMBD data to the Datamart. The Datamart forwards AIM ID and hostname data to the DRS rule builder and thereafter it is forwarded to mobility boundaries.

1


Page 02 of 3

Figure 1

Figure 2 illustrates the flow chart of performing the method. As shown in Figure 2, the DRS monitors in an interval of 300 seconds. The method then identifies if there is a temporary spike or...