CenturionStudio.it - Fotolia

News Stay informed about the latest enterprise technology news and product updates.

The mistake that could make NFV MANO irrelevant

In this week's round-up of blog posts from around the Web, an analyst takes a closer look at NFV management and orchestration (MANO), explaining why it could play second-fiddle to OpenStack.

According to networking analyst Tom Nolle, recent discussion at Light Reading's NFV Everywhere event suggests that NFV MANO may have "lost its luster."

Nolle believes that MANO is the most innovative feature of NFV, but that it faces a range of challenges. Above all, he writes, MANO has failed to incorporate elements of OSS/BSS, network management systems and network operations centers, as the industry specification group declared these areas out of scope. Nolle calls this a mistake that could be fatal for MANO, preventing NFV from achieving the operational efficiency and service agility it needs to build a compelling business case. 

Nolle raises concerns that unless NFV MANO is able to work with operations and legacy equipment, it may simply fade away as a minor alternative to OpenStack.

For NFV proponents, some good news: Overture Networks is integrating its Ensemble Service Orchestrator with Wind River's Titanium Server, combining what Nolle views as the, "best platform available for NFV hosting" with "one of the very few NFV implementations that can actually make a business case."

See more of what Nolle has to say about NFV MANO and why the Overture Networks announcement is big news.

DevOps buyers shake up Application Delivery Controller market

Radical changes are underway in the application delivery controller (ADC) market, says Gartner Inc. research director Andrew Lerner, who details the firm's new Magic Quadrant report in a blog post. The latest shift has sped up the process of change in a sector where, previously, load balancers slowly transitioned into more multifaceted application delivery roles.

According to Lerner, the recent changes have been spurred on by a new legion of DevOps buyers, focused on apps, automation, APIs and a more software-defined approach that stands in contrast to the hardware-centric technology that large network purchasers traditionally buy.

Lerner says the Magic Quadrant report evaluated 10 ADC vendors, with nearly half of those focusing on niche approaches. Brocade has reemerged in the market, while Amazon Web Services has entered the game for the first time. Significantly, neither Brocade nor Amazon are pursuing hardware-based products, underscoring the rise of software-centrism in the market.

See more of Lerner's thoughts on the new Gartner report.

Using SDN to build carrier-grade infrastructure in the cloud

Networking expert Ivan Pepelnjak delved into cloud infrastructure during a recent webinar, expanding on his thoughts on his blog. According to Pepelnjak, it is extremely difficult to achieve carrier-grade levels of reliability in an infrastructure as a service (IaaS) cloud environment, given the variability of IaaS servers.

He recommends setting realistic, business-driven goals, building relatively simple infrastructure and identifying the handful of applications that really need 99.999% availability.

Pepelnjak also notes that carriers who have historically struggled with high costs and complexities may be rushing to adopt NFV too quickly, without considering how to manage the process.

"[Carriers] want to repeat the same mistake, and want cloud architects to build carrier-grade infrastructure on which they'll run unreliable workloads," he adds.

See more of what Pepelnjak has to say about NFV and cloud infrastructure.

Next Steps

Comparing NFV MANO and OpenStack

Discover the differences between NFV and VNF

Learn more about the reliability of Magic Quadrant data

Explore NFV diagrams

 

Dig Deeper on Network virtualization technology

Join the conversation

2 comments

Send me notifications when other members comment.

Please create a username to comment.

Are you more likely to use NFV MANO or OpenStack?
Cancel
To say that OpenStack will push MANO out of the picture as a minor alternative is a little confusing. OpenStack at its core is a Virtual Infrastructure Manager (VIM), one of the core components of the MANO stack. Even if OpenStack projects fill the other two layers of the MANO stack (VNF Manager and Orchestrator) with things like Murano, among others, then OpenStack is not replacing MANO it IS MANO.

This sounds like an analyst that doesn't understand what MANO is.

The OPNFV effort is indeed leaving out of scope those items mentioned, but is not saying those items aren't part of the MANO stack. It is saying that at this current time they are not in scope of current projects. That is a huge difference from what is being implied here.

Before anyone freak out and start saying that OpenStack versus MANO is a valid comparison and that OpenStack is going to supersede MANO, they need to be better educated on what MANO is and the role OpenStack plays WITHIN that stack.
Cancel

-ADS BY GOOGLE

SearchUnifiedCommunications

SearchMobileComputing

SearchDataCenter

SearchITChannel

Close