Overlapping Multi-tenant Networks

Overlapping Multi-tenant Networks
January 4, 2017 Etienne Coulon

Compute, Storage and Network are the 3 basic IaaS element of Cloud computing, administrated by orchestrators like Openstack, Cloudstack, VMware and delivered as an elastic service to public or private clients.

Over this IaaS your clients require a rich set of application services be they local or via 3rd party SaaS providers.

What we have seen

As Cloud services expand, you see more and more overlapping multi-tenant networks, with the possibility of multiple orchestrators, be that multiple instances of say Openstack, or combinations of different ones.

Fold into this problem the dynamic nature of the service, the compute platform, and the application delivery and you see a major network administration headache. The primary reason is that traditional IP address management platforms are silo/orchestrator based, so managing the whole IP Address range becomes a time consuming task.


In the last 6 months AnotherTrail has seen significant cost implications for Cloud Service Providers caused by:

  1. Overlapping Multi-tenant networks
  2. Service expansion/acquisition
  3. 3rd Party SaaS service access
  4. Multiple orchestrators
  5. Need to accommodate virtual user-id naming conventions
  6. Lack of associated CMDB

Resulting in ever more complex management/administration of CSP IP address space and potentially a compliance and/or security risk.


Authoritative Network Management via Fusion Layer, offering a single(redundant) repository aggregated from various orchestrators supporting UID naming conventions and a CMDB.

Keep you existing systems and let Fusion Layer manage the overall IP address space.

For more information contact Anothertrail



Leave a reply

Your email address will not be published. Required fields are marked *


Social media & sharing icons powered by UltimatelySocial