Edge Cloud Anchoring via Automated VPN Service Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for anchoring edge clouds to central clouds are static and manual, leading to limited connectivity and synchronization issues, particularly in decentralized environments, and fail to support dynamic service exposure and multitenancy requirements.
Innovation Solution
A method involving a connectivity controller that obtains an anchoring registry address, sends networking configuration information, sets up a virtual private network (VPN) service, and establishes a VPN connection between edge and central clouds using DNS service discovery, enabling automated and dynamic anchoring.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If static/manual anchoring procedures are used, then configuration simplicity is maintained, but connectivity and synchronization capabilities are limited
Solution Approach 1:
The anchoring system performs self-configuration through automated service discovery and registration. Edge clouds automatically register with the anchoring registry and establish VPN connections without manual intervention, while the system autonomously manages configuration propagation and connection establishment between edge and central clouds
Solution Approach 2:
The system implements feedback mechanisms where the anchoring registry receives registration information from edge clouds, automatically processes anchoring requests, and propagates configuration information back to both edge and central clouds. This closed-loop feedback enables dynamic adaptation and maintains synchronization
2Extent of automation
If automated anchoring is implemented, then connectivity and synchronization are improved, but system complexity increases
Solution Approach 1:
The anchoring registry serves as an intermediary component that mediates between edge clouds and central clouds. It receives registration information from edge clouds, manages anchoring requests, and coordinates with VPN services to establish connections, thereby simplifying the overall system architecture while enabling automated anchoring
Solution Approach 2:
The anchoring registry performs multiple functions including service discovery, registration management, configuration propagation, and coordination of VPN connection establishment. This multi-functionality reduces the need for separate dedicated components, managing system complexity
3Adaptability or versatility
If centralized service exposure is used, then service management is simplified, but dynamicity and flexibility are reduced
Solution Approach 1:
The service exposure mechanism transitions from static centralized management to dynamic edge-initiated exposure. Edge clouds can dynamically register services with the anchoring registry and expose them to central clouds on-demand, enabling flexible and adaptive service exposure while maintaining manageable complexity through the registry's coordination
Data Source
AI summary
The present disclosure relates to a method for anchoring an edge cloud to a central cloud, the method being performed in a cloud environment comprising a central cloud and an edge cloud, the method comprising obtaining (S238, S310), by a connectivity controller of an edge cloud, an address of an anchoring registry of a central cloud; sending (S240, S312), by the connectivity controller, to the anchoring registry, information about networking configuration of the edge cloud; setting up (S246, S314), by an orchestrator of the central cloud, a virtual private network, VPN, service in the central cloud; requesting (S248, S316), by the orchestrator of the central cloud, edge VPN configuration information from the central VPN service, based on the information about networking configuration of the edge cloud; sending (S252, S318), by the anchoring registry, the edge VPN configuration information, to an orchestrator of the edge cloud; creating (S258, S320), by an orchestrator of the edge cloud, an edge VPN service, based on the edge VPN configuration information; and establishing (S260, S322) a VPN connection between the edge VPN service and the central VPN service, whereby services from either one of the edge cloud or the central cloud are exposed in the edge cloud and the central cloud.