Central Namespace Controller for Multi-Tenant Cloud Address Allocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In hybrid cloud computing systems, the integration of virtual machines from private data centers into public cloud environments often leads to MAC address collisions due to overlapping MAC addresses, causing undesirable behavior such as destination host unreachable errors.
Innovation Solution
A method is implemented to configure private networks between tenants and cloud computing systems, using tenant-facing cloud gateways to preserve source addresses and multi-tenant cloud gateways to translate source addresses to unique addresses within the public network, ensuring seamless integration without addressing conflicts. This involves a central namespace controller for allocating unique addresses in a distributed cloud infrastructure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If MAC addresses are preserved during VM migration to maintain seamless integration, then integration continuity is improved, but MAC address collisions occur between tenants
Solution Approach 1:
The patent introduces a cloud gateway as an intermediary component between the virtual machine and the public network. The cloud gateway performs MAC address translation, replacing the original MAC address with a unique cloud-assigned MAC address. This mediator resolves the conflict by allowing VMs to maintain their original MAC addresses internally while presenting unique MAC addresses externally, thus preventing collisions without breaking integration continuity.
Solution Approach 2:
The patent changes the MAC address parameter during VM migration by introducing a translation mechanism. Instead of preserving the original MAC address directly, the system transforms it into a cloud-unique MAC address through the cloud gateway. This parameter transformation maintains the functional identity of the VM while ensuring address uniqueness in the multi-tenant environment.
2Adaptability or versatility
If multiple tenants use independent MAC address allocation, then tenant autonomy is improved, but addressing conflicts arise in the public cloud environment
Solution Approach 1:
The patent segments the addressing space by introducing tenant-specific VLANs and cloud-wide unique MAC address ranges. Each tenant operates within their own segmented namespace where they can autonomously allocate addresses, while the cloud gateway ensures that when these addresses are exposed to the public network, they are translated into globally unique addresses. This segmentation allows tenant autonomy without causing conflicts.
Solution Approach 2:
The cloud gateway acts as a mediator that reconciles independent tenant address allocation with global address uniqueness. It receives packets from tenants with their locally allocated MAC addresses, translates them to cloud-unique MAC addresses, and forwards them to the public network. This intermediary function preserves tenant autonomy while preventing addressing conflicts.
3Reliability
If MAC address translation is implemented to prevent collisions, then address uniqueness is improved, but network complexity increases
Solution Approach 1:
The patent implements automated MAC address allocation and translation management through the cloud gateway. The system automatically assigns unique MAC address ranges to different tenants, dynamically translates MAC addresses during packet forwarding, and manages the translation tables without requiring manual configuration. This self-service approach reduces the operational complexity despite the added functional complexity of translation.
Data Source
AI summary
A centralized namespace controller allocates addresses in a distributed cloud infrastructure on-demand. Upon receiving a request to allocate addresses for a network to be provisioned by a cloud computing system included in the distributed cloud infrastructure, the centralized namespace controller allocates a network address that is unique within the distributed cloud infrastructure. Further, the centralized namespace controller allocates a range of virtual network interface cards (NIC) addresses that are unique within the network. The centralized namespace controller then allocates addresses from the range of virtual NIC addresses on an as-requested basis—when a virtual NIC is being created by the first cloud computing system on the network. Advantageously, by centralizing the allocation of addresses and dedicating independent NIC address ranges to different cloud computing systems, the centralized namespace controller enables stretched L2 networks between cloud computing systems while preventing duplicated addresses on the stretched networks.