Imagine for a second that you’re operating an industrial plant. Giant machinery enveloped by metal pipes and thickets of wire that hums along while steam billows from above. All of a sudden, it all comes to a screetching halt.
What’s the problem? How long until it’s fixed? Without visibility into the status of each critical component of your operation, it’s going to be a very long process tyring to get everything back online. Wouldn’t it be great if you had an all-seeing eye and an automatic way of resolving these issues, many before they ever happen?
While many organisations and service providers understand the benefits of NFV, the requirements to set up such an infrastructure are often seen as a major hurdle to adoption. A multi-vendor alliance led by Atos has the specific goal of showing how NFV can help optimise network and business performance based on known and measured performance.
At the root of John Boyd’s “OODA loop” methodology, there is the notion that we need to acknowledge and work with levels of “uncertainty”—gaps that result when applying established models to new and changing contexts[i]. Unfortunately, the networking community—desperate for operational stability—largely ignores these mismatches, designing network and security architectures as if they can dictate how applications are deployed.