Stateful Endpoint Mobility in Federated Cloud Systems

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing federated container orchestration tools cause service interruptions and lose state when moving workloads between clusters, as they terminate the old instance and start a new one without retaining the state.

Innovation Solution

Implement a 'make-before-break' approach where a replica endpoint and database are deployed in the target cluster, synchronized with the original, and then used by clients, allowing seamless state transfer and minimizing service disruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the old instance is terminated and a new instance is started in the new cluster, then the workload can be moved between clusters, but service interruptions occur and state is lost

Engineering Contradiction:

Improveworkload mobilityVSAvoidservice continuity

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent creates a replica endpoint and replica database in the target cluster before terminating the original endpoint. The replica database is synchronized with the original database, and the replica endpoint is configured to use the replica database. This preliminary setup ensures that when the switch occurs, service continuity is maintained without interruption or state loss.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent creates a copy (replica) of the endpoint and a copy (replica) of the database in the target cluster. The replica endpoint is initially configured to use the replica database, and after synchronization, clients are switched to use the replica endpoint. This copying approach allows seamless migration while preserving state.

Inventive Principle:

Principle #26Copying

2Adaptability or versatility

If the old instance is terminated and a new instance is started in the new cluster, then the workload can be moved between clusters, but state maintained by the old instance is lost

Engineering Contradiction:

Improveworkload mobilityVSAvoidstate loss

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent synchronizes the replica database with the original database before the endpoint migration is completed. This preliminary synchronization ensures that all state information is copied to the target cluster before the original endpoint is terminated, preventing any state loss during the migration process.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent creates a replica database that is synchronized with the original database. The replica endpoint is configured to use the replica database, ensuring that state information is preserved and transferred to the new cluster. When clients switch to the replica endpoint, they continue to access the same state information without loss.

Inventive Principle:

Principle #26Copying

3Reliability

If a replica endpoint and database are deployed and synchronized before switching, then service continuity is maintained, but the migration process becomes more complex

Engineering Contradiction:

Improveservice continuityVSAvoidmigration process complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the migration process into distinct phases: (1) creating the replica endpoint and replica database in the target cluster, (2) synchronizing the replica database with the original database, (3) configuring the replica endpoint to use the replica database, and (4) switching clients to use the replica endpoint. This segmentation makes the complex migration process more manageable and systematic.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a replica endpoint and replica database as intermediaries during the migration process. The replica endpoint acts as a temporary mediator that can receive client requests while the underlying database is being synchronized. This intermediary approach simplifies the migration by providing a buffer that decouples the client switching from the data synchronization process.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS20240311181A1Stateful endpoint mobility in a federated cloud computing system

Publication Date: 2024.09.19 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

A method by a master orchestrator in a federated cloud computing system to move an endpoint between clusters. The method includes receiving a request to move a first endpoint implemented in a first cluster to another cluster, wherein the first endpoint provides a service and uses a first database to store state associated with the service, responsive to receiving the request, causing a second endpoint and a second database to be deployed in a second cluster, wherein the second endpoint is a replica of the first endpoint, the second database is a replica of the first database, and the second endpoint is to use the second database to store state, causing synchronization between the first database and the second database to begin, causing the first endpoint to use the second database instead of the first database, and causing clients to use the second endpoint instead of the first endpoint.