Dynamic Job Delegation in Datacenter Management Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Datacenter management solutions face challenges in scaling and re-configuring management services as network topology changes, particularly when additional routers are added, requiring re-configuration and re-deployment of management services.
Innovation Solution
A method and system for job delegation using management objects, where a first management object receives a job, identifies a target system, determines a next hop, places the job on a queue, and executes it using a driver corresponding to the target system, allowing for dynamic management and adaptation to changing network topologies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If management services are located in static locations within the deployment network topology, then management services can be easily deployed and controlled, but the management services must be re-configured and re-deployed when the network topology changes
Solution Approach 1:
The patent implements dynamic management services where management objects are no longer fixed in static locations but can dynamically adapt to changing network topologies. Management objects move with network changes and automatically update their relationships, eliminating the need for manual re-configuration while maintaining ease of deployment.
Solution Approach 2:
The system incorporates feedback mechanisms where management objects continuously monitor network topology changes and automatically adjust their configuration. This feedback loop enables the management services to adapt to topology changes without requiring manual re-deployment, resolving the contradiction between ease of deployment and adaptability.
2Reliability
If the data center is divided into subnets requiring additional routers, then network segmentation and control are improved, but the management service must be re-configured to function in the new topology
Solution Approach 1:
The management objects perform self-configuration when network topology changes occur. They automatically discover new network segments, establish appropriate relationships, and update their routing information without requiring manual intervention. This self-service capability maintains network segmentation reliability while eliminating management re-configuration complexity.
Solution Approach 2:
The system prepares management objects in advance with the capability to automatically adapt to topology changes. When subnet division occurs, the pre-configured management objects immediately begin self-configuration processes, eliminating the need for post-deployment re-configuration and reducing overall system complexity.
3Adaptability or versatility
If management services are re-deployed to accommodate network changes, then the management services can function in the new topology, but the process is time-consuming and disruptive
Solution Approach 1:
Management objects are pre-configured with the necessary capabilities and relationships before network topology changes occur. When changes happen, these pre-prepared objects can immediately adapt without requiring time-consuming re-deployment processes, thus maintaining topology adaptability while minimizing time loss.
Solution Approach 2:
The system transitions from static management service deployment to dynamic adaptation where management objects automatically adjust their configuration in real-time as topology changes occur. This dynamic behavior eliminates the need for manual re-deployment cycles, significantly reducing the time required to accommodate network changes while maintaining full adaptability.
Data Source
AI summary
A method for job delegation including receiving a job from a user by a first management object, identifying a target system for the job using a data model in the first management object and a job delegation policy, where the data model comprises an object representing the target system, and determining a first nexthop for the target system, where the first nexthop is a second management object. The method also includes placing the job on a queue corresponding to the second management object, where the queue is located in the first management object, receiving the job by the second management object, locating the target system and a driver corresponding to the target system using the second management object, and executing the job using the driver corresponding to the target system.