Releasing the Application hounds

The show begins, the suits stand up and, like the great marketers of old, spout key technology verbiage like Cloud, Virtualisation and Orchestration, terms meaning different things to different people, but making the speaker appear tech savvy and at one with the Internet.

Emerging from the first wave of market-speak, calmer water appear ahead as the audience drifts into As-a-Service land and it’s closely aligned relative software-defined-everything. In the corner, guru’s debate when and if IaaS will mind meld with PaaS, whilst software-defined-mainframe academics and the Apache DC/OS communes swap battle stories with an ancient Greek helmsman.

From the outside it is pure gibberish, yet inside this arena hype, spin and commercial interests sit side by side with genuine open communities and the god of wikinomics.

The application is king, declares an agile young man. The audience applauds, yet under the polished virtualised veneer they know the application is no such thing.

Be it Docker or VM, bare metal or traditional server the application is a networking afterthought, an irritant whose demands intrude on the closeted world of Routing Protocols, Leaf and Spine architectures and hyper convergence fairy tales.

To be king you must rule, dictate the way of things. After all today’s business revolves around the success of key applications?

Then it appears at the entrance, a knight on shinning optics. The networks offer bottlenecks, yet Devops pounces, crafting a single tiered path for our hero into the heart of the problem.

‘Where there are optics let me harvest its fruits’, the knight declares, the audience gasps

‘Where there is Orchestration and Workload I shall do likewise.’

Then turning to Devops, ‘Dear friend, let Ruby, Ansible and your comrades will join as well.’

More gasps

‘My king demands success. Bandwidth and latency, workload and orchestration, all must be his to command.’

Welcome to the new kingdom of Application Defined Networking @Anothertrail.


Overlapping Multi-tenant Networks

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

Continue reading “Overlapping Multi-tenant Networks”

Security : From Silo to Overlay

To fight a war you need a range of military options and when combined with great direction and leadership, victory can be achieved. Security is a war, a daily battle whose ground rules and potential impact is morphing from data breach to ransomware, from coporates to nation states.

On CNBC Avi Chelsi CEO of  Empow provides an insight to the alleged Russian involvement in the US Presidential election. Empow is a security overlay, abstracting data from live client security implementations, crafting a common langauage, and through that language empowering a coordinated business level approach to security.

Learn more about Empow : Contact Anothertrail