On today’s Heavy Networking, we peer behind the curtain of Intent-Based Networking (IBN) with guest Phil Gervasi, who wrote a pair of white papers for the Packet Pushers' Ignition membership site. We discuss core concepts of IBN, including network abstraction, continuous validation, and automated remediation.
The post Heavy Networking 461: Key Concepts Of Intent-Based Networking appeared first on Packet Pushers.
The serverless platform was initially developed by IBM but now enters an increasingly complex...
The first phase of CenturyLink’s fiber network expansion traverses more than 3.5 million miles...
One of the new products combines Arrcus’ hardware-agnostic operating system with Broadcom’s...
The service pairs FatPipe’s multi-path WAN transmission security technology with Mode’s SD-Core...
The milestone comes as governments continue to struggle with 5G security concerns.
By Bruce Davie, CTO, Asia Pacific & Japan
As I’m currently preparing my breakout session for VMworld 2019, I’ve been spending plenty of time looking into what’s new in the world of networking. A lot of what’s currently happening in networking is driven by the requirements of modern applications, and in that context it’s hard to miss the rise of service mesh. I see service mesh as a novel approach to meeting the networking needs of applications, although there is rather more to it than just networking.
There are about a dozen talks at VMworld this year that either focus on service mesh or at least touch on it – including mine – so I thought it would be timely to comment on why I think this technology has appeared and what it means for networking.
To be clear, there are a lot of different ways to implement a service mesh today, of which Istio – an open-source project started at Google – is probably the most well-known. Indeed some people use Istio as a synonym for service mesh, but the broader use of the term rather than a particular implementation is my Continue reading

Enterprise IT is a mehtopian paradise
The post Dictionary: mehtopian appeared first on EtherealMind.
Here’s a simple scenario: you have some Virtual Machines (VMs) in your on-premises environment, likely in VMware vSphere or Microsoft Hyper-V. You want to either fully migrate some or all of those VMs to the AWS Cloud or you want to copy a gold image to the AWS Cloud so you can launch compute instances from that image. Simple enough.
Now, how do you do it?
Can you just export an OVA of the VM, copy it up, and then boot it? Can you somehow import the VMDK files that hold the VM’s virtual drive contents? Regardless the eventual method, how do you do it at scale for dozens or hundreds of VMs? And lastly, how do you orchestrate the process so that VMs belonging to an application stack are brought over together, as a unit?
This post will answer these questions and more by providing an introduction to the services available on the AWS Cloud to discover, plan, migrate, and track VMs from on-prem to AWS.
This post assumes good working knowledge of technologies such as VMware vCenter and only basic knowledge of AWS.
Remembering that this post is tailored for those that Continue reading