Network Orchestrator Service-to-Service Scheduling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Container orchestrators lack support for guaranteed bandwidth between services, and existing techniques do not account for network reservation requirements, leading to inefficiencies in replica and request scheduling, especially in container-based deployments with dynamic and short-lived containers.

Innovation Solution

Implementing a network resource-aware container orchestrator that schedules new replicas and incoming requests collaboratively, using service-to-service network resource descriptors and resource utilization monitoring to optimize network resource utilization, auto-scaling, and dynamic network policy adjustments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If container orchestrators use traditional scheduling methods without network resource awareness, then scheduling simplicity is maintained, but network resource utilization efficiency deteriorates

Engineering Contradiction:
Improvenetwork resource utilization efficiencyVSAvoidscheduling system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The network orchestrator implements continuous monitoring of network resource utilization and uses this feedback to dynamically adjust scheduling decisions. The system monitors actual network usage patterns and feeds this information back to the scheduling algorithm, enabling it to optimize replica and request placement based on real-time network conditions, thereby improving resource utilization without manual intervention.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

A network orchestrator is introduced as an intermediary component between the container orchestrator and the network infrastructure. This mediator translates scheduling decisions into network resource allocations and policies, coordinating between compute and network resources to achieve efficient utilization while maintaining the independence of existing orchestrator systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If collaborative scheduling of replicas and requests is implemented, then network performance characteristics improve, but scheduling computation time increases

Engineering Contradiction:
Improvenetwork performance predictabilityVSAvoidscheduling decision time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system pre-calculates and pre-allocates network resources for anticipated replica deployments and request patterns. By performing preliminary network resource reservation and scheduling planning before actual workloads arrive, the system reduces the computational burden during runtime scheduling decisions, enabling faster response times while maintaining reliable network performance guarantees.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The scheduling system dynamically adjusts its complexity based on workload conditions. During periods of low activity, it performs comprehensive collaborative optimization of replicas and requests. During high-demand periods, it relies on pre-computed schedules and simpler allocation rules, thereby maintaining network performance reliability while adapting scheduling computation time to actual system needs.

Inventive Principle:
Principle #15Dynamics

3Reliability

If network resource reservation is enforced for service-to-service communication, then quality of service guarantees improve, but network flexibility deteriorates

Engineering Contradiction:
Improvequality of service guaranteeVSAvoidnetwork configuration flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system applies network resource reservations selectively at the service-to-service communication level rather than globally across the entire network. Each service pair can have customized bandwidth and latency guarantees tailored to its specific requirements, while other parts of the network remain flexible and available for dynamic allocation. This localized approach maintains QoS guarantees for critical communications without sacrificing overall network adaptability.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The network orchestrator dynamically adjusts network resource allocation parameters based on changing workload demands and service requirements. Reservation parameters such as bandwidth limits and priority levels can be modified in response to monitoring data, allowing the system to maintain QoS guarantees when needed while transitioning to more flexible allocation when service requirements change, thus balancing reliability and adaptability.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11997022B2Service-to-service scheduling in container orchestrators
Publication Date: 2024.05.28 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11997022B2 patent drawing
  • US11997022B2 patent drawing
  • US11997022B2 patent drawing

AI summary

Methods, systems, and computer program products for service-to-service scheduling in container orchestrators are provided herein. A computer-implemented method includes reserving, by a network orchestrator, network resources requested between a plurality of services, wherein each of the services is implemented as one or more replicas running on a set of nodes of a cluster, managed by the network orchestrator, that use the network resources to serve incoming requests to the plurality services; monitoring utilization of the network resources; and scheduling, by the network orchestrator based on the monitoring, one or more new replicas of the plurality of services and the incoming requests to the plurality of services in a collaborative manner to increase at least one network performance characteristic.