& cplSiteName &

Making Things Simpler

Jeff Finkelstein
6/16/2014
100%
0%

    “The way to build a complex system that works is to build it from very simple systems that work.” – Kevin Kelly, founding editor of Wired Magazine

In many ways, we are most comfortable with complexity. As engineers, we enjoy the process of creating, modifying, re-creating, and maybe at some point in time actually producing something that works. We find that more often than not we enjoy the process more than the creation itself. So we undertake the analysis, re-analysis, re-re-analysis, of solving a given problem and often find the most complex, sometimes most costly, often difficult, solution as it appeals to the problem solver in us all.

I often remember the following cartoon when I am faced with solving a technology problem…

Back in the good old days when I was involved in developing UNIX kernels, we often played games with code trying intentionally to make it as obfuscated as possible. We even gave prizes out for whoever could write the most unreadable code. We considered it a fun way to solve problems and also impress our peers with our programming skills.

What we lost in the process was that there were people actually using our software and that others in the future would have to maintain it. As I look back at code I wrote in the 80s, I have no idea what I was trying to do unless there were some semblance of comments scattered haphazardly throughout the code. It was fun back then, but today I would not be happy having to need to make a code change.

As engineers, we need to maintain the balance between simple solutions and complex answers. Occam's Razor has proven true all too many times for us to ignore it and yet at times we do. We become so enamored of our favorite shiny object that we develop an amazingly transparent blindness to others' blind spots, to anything other than what has become the new toy in our toy box. However, we do know we cannot completely depend on it. We may build large, complex, and even unwieldy, solutions to posed problems, but very often we are solving for things that have never even been presented as a concern.

For my architecture team, we maintain five simple rules:

1. Simple, modular architectures always win
2. Centralize what you can, distribute what you must
3. Silicon matters for scale, availability, and resilience
4. Automate anything that can be automated
5. Support open standards

The more complexity we introduce into an already complex ecosystem creates a difficult road to navigate over time. Each change creates a ping-pong effect that often touches remote pieces of the design in our minds, never to be impacted. But in some small way they are changed enough to cause havoc that we end up spending much time troubleshooting.

Back in my last column, I spent time discussing the delineation between network layers in the cable modem termination system (CMTS) functional block diagram that I've been using for a few articles to show how this simplification may help. Putting the physical layer components (and possibly MAC) into a remote device helps with the scale issues at hand while also simplifying the architecture. (See Embracing Technological Change and Learning From Mistakes.)

There are many ways to solve the same problems using monolithic architectures that are completely sound both technically and financially. But do they get us where we want in the long run? How do we simplify even more? What can we do to not only break the functional blocks and layers apart further, but also provide a communication path between them?

Enter SDN and NFV…

While they are our industry's current shiny objects, if we treat them as another tool in our toolbox they do provide a framework for achieving this goal. I am often involved in discussions about how they can be used to solve almost every imaginable issue simply by decomposing functions or using OpenFlow (or other protocols) as a standard communication mechanism. Realistically, both SDN and NFV are finding their way through the complex organism we call our network. But, in order for them to flourish in our technological world, we need some quick wins to show how they may help.

So what are they? I like to look for ways to reduce the complexity both in design and configuration. As we add more devices, paths, circuits, flows, routes, etc, we make things more complex. As we are required to configure more equipment with device-specific configurations using unique command line interfaces, we simply increase the complexity.

So how can we simplify things? One way is to use an abstraction that allows us to define things in such a way that it is applicable to multiple physical manifestations. Rather than force us to integrate device and service-level provisioning, is there a way to focus on the services and let the devices provision themselves? To me, it is a holy grail in network design and management; but through standardization we are getting much closer.

In the excellent work done at CableLabs, with MSO and vendor support, on Converged Cable Access Platform (CCAP) and DOCSIS 3.1, we are seeing a real-world impact through the use of YANG models for device and service abstraction, and NETCONF for configuring devices. In many ways, this is the beginning of a whole new way to view the cable ecosystem. We are no longer encumbered with doing things as we have always done them; it is a completely new way to envision how we may be able to manage our networks.

Stay tuned for future blog posts and ruminations on ways to think about N2GCable, i.e. the next-next generation of cable we are now entering…

— Jeff Finkelstein, Executive Director of Strategic Architecture, Cox Communications

(8)  | 
Comment  | 
Print  | 
Newest First  |  Oldest First  |  Threaded View        ADD A COMMENT
brookseven
50%
50%
brookseven,
User Rank: Light Sabre
6/18/2014 | 12:26:41 PM
Re: Abstraction as a language
I think the biggest challenge here is age.  I don't mean the age of people, but instead the age of products and services.

My experience with this is that things become difficult once a product or service exists for a period of time.  There becomes dependency on what I will call quirks in behavior.  This kind of kruft creeps in over time.

Why do I bring this up.  The kind of systems architecture discussion here is most valid about brand new things.  Do we have that in a network service?  FiOS was about as brand new as a service as I have been involved with.  Even there we had TIRKS.

So my question is...Can you define the entire current network as a single abstraction?  If not, I think that you will end up with issues around interconnecting the old and new.  I have had success in encapsulating the old and treating it as a block.  But old products are grumpy and have personalities.  They get mad when you try to get them to do things that they were never intended to do.

seven
nasimson
50%
50%
nasimson,
User Rank: Light Sabre
6/17/2014 | 11:29:17 PM
Re: Abstraction as a language
Thanks Mike. Now that I get it, I think it's an area where industry associations should play a greater and active role in defining and standardizing these abstractions and specifications.
@mbushong
50%
50%
@mbushong,
User Rank: Moderator
6/17/2014 | 10:10:02 PM
Re: Abstraction as a language
We tend to think of edge policy in very networking-centric terms: VLANs, ACLs, QOS, whatever. These are all constructs that help us specify how traffic traverses (or does not) the network. 

If the future is about converged infrastructure (including applications), the most meaningful abstractions are probably not networking constructs. What you might want is a set of abstractions relevant across all infrastructure. 

If the abstractions are in support of applications, the abstractions themselves could be expressed in application terms. For example, it might be interesting to label an application as HIPAA-compliant. Individual infrastructure elements would then translate this policy into behavior (isolating traffic on the network, for instance). You could specify things like application response times, loss thresholds, compliance requirements (like PCI), access restrictions, auditability requirements, etc.

Note that this would all need to be done in a way that is somewhat higher-level than the underlying compute, storage, and networking, and obviously in a way that is at least open access (like open source) if not standard.

Mike Bushong (@mbushong)

Plexxi
nasimson
50%
50%
nasimson,
User Rank: Light Sabre
6/17/2014 | 9:49:22 PM
Re: Abstraction as a language
> Maybe we need to be presenting policy as a derivative of applications SLAs? @Mike: Can you please elaborate the above a little? Thanks in advance.
nasimson
50%
50%
nasimson,
User Rank: Light Sabre
6/17/2014 | 9:41:00 PM
lot of insights
A great wow article! Only the other day, I was thinking of this image to put it in my work space so that we don't repeat these mistakes. To learn from the insights there in, and not to let these slip over from over time, I think I need to read it every once in a while.
Duh!
50%
50%
Duh!,
User Rank: Light Sabre
6/17/2014 | 10:16:30 AM
One more rule
Excellent points.

As a network architect, I have adapted a rule from software engineering.  Since it is complementary to the five rules that Jeff writes about, I'd simply add it to his list.

6. Strong cohesion within subsystems, loose coupling between subsystems.

Which means that subsystems should be kept small and simple by insisting that all their functions be the set of operations on a single, self-contained object.  And that interfaces between subsystems be kept simple.  When a subsystem gets too complex to understand, or has too many moving parts... you're doing it wrong.   When an interface gets too chatty or has a state explosion... you're doing it wrong.  Redraw your subsystem boundaries and start again.

 
danielcawrey
50%
50%
danielcawrey,
User Rank: Light Sabre
6/16/2014 | 5:28:19 PM
Re: Abstraction as a language
I can see a future where many systems will need multiple networks, not just one or two. Being able to rethink VLAN architecture with a more software-defined component I think is a step towards this. 

Ultimately, I think that network engineering is more going to be able compartmentalizing certain aspects of a system. Does anyone else see that type of architecture coming?
@mbushong
50%
50%
@mbushong,
User Rank: Moderator
6/16/2014 | 10:13:48 AM
Abstraction as a language
The needfor abstraction is absolutely a great way to siplify things going forward. We should be aware that these abstractions will eventually serve as the lingua france between infrastructure that current exists in separate silos. This begs for some real thought to be put into anything that resembles a policy abstraction. Should things be expressed in terms of networking constructs? Or in terms of storage or compute requirements? Maybe we need to be presenting policy as a derivative of applications SLAs? 

The point is not to advocate one or the other here, but rather to suggest that even abstraction needs to be thought about. Because it is being done within the context of networking today, we could very well end up with a reimagining of VLANs and ACLs, a good step for sure but certainly not a long-lasting evolutionary step.

Mike Bushong (@mbushong)

Plexxi
Educational Resources
sponsor supplied content
Educational Resources Archive
More Blogs from Column
In this final blog of a three-part series, Jeff Gordon examines what operators hope to gain from going down the converged service layer route.
SDN and NFV are more than just networking acquaintances, believes Open Networking Foundation (ONF) Executive Director Dan Pitt.
As niche OTT services abound, they could shatter the business model for the pay-TV industry's traditional fat bundles.
In the second of a three-part series, OpenCloud's Jeff Gordon delves deeper into the driving forces for adopting a converged service layer.
Edge computing is a compelling option for telcos looking to balance tightening finances with increasing demands for bandwidth and processing speed. 
From The Founder
The more things change, the more they stay the same for Juniper's next-gen comms solutions, and that's a good thing.
Flash Poll
Live Streaming Video
Charting the CSP's Future
Six different communications service providers join to debate their visions of the future CSP, following a landmark presentation from AT&T on its massive virtualization efforts and a look back on where the telecom industry has been and where it's going from two industry veterans.
LRTV Interviews
Rogers: Millennials Prefer Mobile Video

7|1|16   |     |   (0) comments


Rogers' Upinder Saini explains how millennial viewers favor mobile devices over big TVs and non-conventional TV content over broadcast and cable networks.
LRTV Custom TV
ZTE Pre5G & 5G Solutions

6|30|16   |   02:23   |   (0) comments


At 5G World London, ZTE demonstrated two types of equipment, including 128 antenna Pre5G Massive MIMO and 15GHz high-frequency base stations.
LRTV Custom TV
Energy 2020: Technology Innovation to Fuel Power Efficiency

6|30|16   |   07:21   |   (0) comments


Managing energy costs and consumption as cable operators deploy new services requires new levels of innovation from technology partners. In this video, Dave Fellows, co-founder and CTO of Layer3 TV and chief scientist of the SCTE/ISBE Energy 2020 program, discusses such ambitious objectives as achieving a second 500% increase in efficiency in outside plant ...
LRTV Custom TV
Transitioning to Service Agile Networks

6|30|16   |     |   (0) comments


Packet optical networks are transitioning from proprietary converged systems to open disaggregated platforms. This video will describe the Fujitsu 1FINITY disaggregated platform, explore how 1FINITY interoperates with the Fujitsu FLASHWAVE platform and explain how 1FINITY is designed for software control, like with Fujitsu Virtuora NC.
Women in Comms Introduction Videos
Nokia's Advancement Plan: Bring Old Skills to New Roles

6|29|16   |   7:57   |   (1) comment


Nokia's Sandy Motley advises women to change their mindsets; get aggressive about advancing their careers; develop strong, diverse support networks; and always bring forth learned skills to take on new challenges and different roles.
Between the CEOs
CEO Chat: Cisco's Yvette Kanouff

6|28|16   |     |   (0) comments


In Silicon Valley, Steve Saunders sits down with Cisco's Yvette Kanouff for an exclusive in-depth interview.
LRTV Interviews
Comcast: Prepping Next-Gen Video Services

6|28|16   |     |   (0) comments


In this LRTV interview, Comcast's Elad Nafshi outlines where MSO stands with cloud DVR, OTT video, college and gigabit services.
LRTV Custom TV
Energy 2020: Creating Unique Standards for Cable's Unique Networks

6|28|16   |   09:30   |   (0) comments


Cable's unique network requirements require a specific set of standards for operators to increase power efficiency, according to Dan Cooper, vice president of critical infrastructure for Charter Communications and chair of the SCTE/ISBE Standards Program's Energy Management Subcommittee, and Ian Oliver, managing director of the Trenchant Group and a member of the ...
LRTV Custom TV
Masergy: 'Now Is the Time for NFV'

6|28|16   |     |   (0) comments


Hear Ray Watson, VP of Global Technology at Masergy, talk about the advantages that enterprises can leverage using Network Function Virtualization (NFV), and how Masergy takes a unique approach to solving customers' problems. For more information on Masergy, please visit www.masergy.com.
LRTV Custom TV
Masergy Leads the Charge With NFV Capabilities

6|28|16   |     |   (0) comments


Hear Tim Naramore, CTO at Masergy, talk about how focusing on solving specific customer challenges, providing self-service automation tools and being laser focused on the customer experience has enabled Masergy to be a leader in the NFV space. For more information on Masergy, please visit www.masergy.com.
LRTV Custom TV
Private Company of the Year - Affirmed Networks

6|27|16   |     |   (0) comments


At BCE 2016, Steve Saunders speaks to Hassan Ahmed about Affirmed's success.
LRTV Custom TV
Energy 2020: Growing Services, Not Consumption

6|24|16   |   07:18   |   (0) comments


Management of power requirements needs to be a key consideration as cable operators deploy new services, says Dan Cooper, vice president of critical infrastructure for Charter Communications and chair of the SCTE/ISBE Standards Program's Energy Management Subcommittee. In this video, Cooper discusses the importance of cable operators and technology partners ...
Upcoming Live Events
September 13-14, 2016, The Curtis Hotel, Denver, CO
November 3, 2016, The Montcalm Marble Arch, London
November 30, 2016, The Westin Times Square, New York City
December 6-8, 2016,
May 16-17, 2017, Austin Convention Center, Austin, TX
All Upcoming Live Events
Infographics
A new survey conducted by Heavy Reading and TM Forum shows that CSPs around the world see the move to digital operations as a necessary part of their overall virtualization strategies.
Hot Topics
Brexit: It's Hard to See an Upside
Ray Le Maistre, Editor-in-chief, 6/29/2016
Qualcomm Readies Lower-Band 5G Testbed
Dan Jones, Mobile Editor, 6/27/2016
DT Eyes FTTH Solution to German Opex Issue
Iain Morris, News Editor, 6/29/2016
Sigfox Said to Face Customer Backlash
Iain Morris, News Editor, 6/27/2016
Disney Deals $3.5B for MLBAM Stake – Report
Mari Silbey, Senior Editor, Cable/Video, 7/1/2016
Like Us on Facebook
Twitter Feed
BETWEEN THE CEOs - Executive Interviews
In Silicon Valley, Steve Saunders sits down with Cisco's Yvette Kanouff for an exclusive in-depth interview.
At the BCE 2016 show in Austin, ECI Telecom CEO Darryl Edwards tells Light Reading founder and CEO about the Elastic Network concept and the company's NFV and cybersecurity developments.
Animals with Phones
Live Digital Audio

Our world has evolved through innovation from the Industrial Revolution of the 1740s to the information age, and it is now entering the Fourth Industrial Revolution, driven by technology. Technology is driving a paradigm shift in the way digital solutions deliver a connected world, changing the way we live, communicate and provide solutions. It can have a powerful impact on how we tackle some of the world’s most pressing problems. In this radio show, Caroline Dowling, President of Communications Infrastructure & Enterprise Computing at Flex, will join Women in Comms Director Sarah Thomas to discuss the impact technology has on society and how it can be a game-changer across the globe; improving lives and creating a smarter world. Dowling, a Cork, Ireland, native and graduate of Harvard Business School's Advanced Management Program, will also discuss her experience managing an international team focused on innovation in an age of high-speed change.