CaaS Repository Failover for Container Platform Connectivity Loss
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Containerized applications in telecommunications systems experience failures due to network disruptions, leading to service outages when pods or containers restart and cannot fetch required files.
Innovation Solution
Implementing a container as a service (CaaS) platform that replicates CI/CD server contents in real time to a geo-redundant server or proxy cache, enabling access during network failures and ensuring service continuity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If containerized solutions are used for efficient software management, then automation and efficiency are improved, but service reliability deteriorates due to pod or container restarts causing failures
Solution Approach 1:
The system performs preliminary actions by replicating CI/CD tool server contents to alternative repositories before failures occur. This ensures that when the primary CI/CD server becomes unavailable due to network failures or container restarts, the CaaS server can immediately access replicated contents from alternative repositories, maintaining service continuity without interruption.
Solution Approach 2:
The patent implements copying by creating alternative repositories that contain replicated copies of CI/CD tool server contents. When the primary server fails, the system switches to using these copied versions, allowing service continuation even when the original source is unavailable. This resolves the reliability issue while preserving the automated containerized management approach.
2Reliability
If real-time replication is implemented to prevent service disruptions, then service reliability is improved, but system complexity increases
Solution Approach 1:
The patent introduces alternative repositories as intermediary components between the CaaS server and the primary CI/CD tool server. These intermediaries hold replicated contents and serve as backup access points when the primary server is unavailable. This intermediary layer adds minimal complexity while significantly improving reliability by providing a straightforward failover mechanism.
Solution Approach 2:
The system extracts critical CI/CD tool server contents and separates them into alternative repositories that can function independently. This extraction allows the CaaS server to access essential contents from alternative repositories when the primary server fails, reducing the impact of system complexity while maintaining service continuity.
3Reliability
If alternative repositories with real-time replication are created, then service disruption prevention is improved, but resource consumption increases
Solution Approach 1:
The patent applies local quality by replicating only the specific CI/CD tool server contents that are necessary for CaaS server operation, rather than duplicating entire systems. This selective replication minimizes storage resource consumption while ensuring that critical contents are available in alternative repositories for failure remediation.
Solution Approach 2:
The system implements partial action by replicating only the essential portions of CI/CD tool server contents to alternative repositories. This partial replication is sufficient to maintain service continuity during failures while avoiding the excessive resource consumption that would result from complete system duplication.
Data Source
AI summary
Systems, methods and non-transitory computer-readable mediums are provided for remediating failures in container-based telecommunications systems. A method includes accessing by a container as a service (CaaS) server a continuous integration (CI)/continuous delivery (CD) tool server. The method additionally includes experiencing a connectivity failure with the CI/CD tool server and accessing by the CaaS server an alternative repository created through real time replication of the CI/CD tool server contents.