Ingress Engine for Data Center Message Reordering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional mechanisms for monitoring data center resources in virtualized environments are inadequate, particularly due to limitations in handling out-of-order messages and varying protocol types, which disrupt network infrastructure management and performance visibility.
Innovation Solution
The implementation of a policy enforcement system that ensures compliance with protocol-specific requirements for message ordering, using an ingress engine to identify and communicate messages to appropriate collector applications, ensuring data viability and integrity for dynamic optimization and orchestration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If traditional monitoring mechanisms are used to gather data center performance statistics, then data collection is possible, but network element scale is limited and additional periodic processing is required
Solution Approach 1:
The patent introduces an intermediary component that sits between network elements and the monitoring system, acting as a proxy to collect and forward metrics. This intermediary handles the complexity of data collection, allowing the monitoring system to scale to more network elements without increasing its own complexity proportionally.
Solution Approach 2:
The monitoring mechanism enables network elements to self-report their metrics through standardized interfaces, eliminating the need for periodic polling by the central monitoring system. This self-service approach reduces the processing burden on the monitoring system and allows for scalable data collection from a large number of network elements.
2Reliability
If messages are processed without protocol-specific ordering enforcement, then processing speed is faster, but data viability is compromised when messages arrive out-of-order
Solution Approach 1:
The system performs preliminary actions by establishing protocol-specific ordering requirements before message processing begins. The ingress engine is pre-configured with knowledge of which protocols require ordering enforcement, allowing it to make immediate routing decisions without compromising data viability while minimizing unnecessary processing delays.
Solution Approach 2:
The patent applies different quality requirements to different message streams based on their protocol type. Rather than enforcing ordering on all messages uniformly, the system applies ordering enforcement only where specifically required by the protocol, maintaining data viability for sensitive protocols while preserving high throughput for protocols that tolerate out-of-order delivery.
3Reliability
If protocol-specific policies are enforced for message ordering, then data integrity is maintained, but system complexity increases due to multiple collector applications
Solution Approach 1:
The ingress engine is designed as a universal component that handles multiple protocol types and determines appropriate routing to different collector applications based on protocol-specific requirements. This multi-functional design consolidates the complexity management in a single intelligent component rather than requiring separate specialized components for each protocol.
Solution Approach 2:
The system changes the parameter of message routing based on protocol type detection. The ingress engine dynamically adjusts routing parameters by examining message headers and determining the appropriate collector application for each protocol type, allowing the system to maintain reliability through protocol-specific handling while managing complexity through adaptive routing logic.
Data Source
AI summary
Techniques for resource monitoring and managed message reordering in a data center are described. In one example, a computing system comprises an ingress engine to receive a message from a network device in a data center comprising a plurality of network devices and the computing system; and in response to receiving the message from a network device in the data center, communicate the message to an appropriate collector application corresponding to the message's protocol type in compliance with at least one requirement for data stored in a message flow communicated from one or more network devices to the computing system.