& 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
IEEE's Nita Patel outlines the specific overlapping and critical elements that you must possess to successfully and simultaneously be a leader, mentor and mentee.
As companies virtualize, too many fail to bring anywhere near the same rigor to monitoring their cloud services that they'd applied to their physical networks -- and that's playing with fire.
How cable operators can use advanced customer-aware data analytics to improve the customer experience, reduce service disruptions and cut both tuck rolls and call center costs.
Spectrum sharing is becoming a bigger issue as the 5G radio specification evolves.
Addressing current and future app demands while laying the foundation for mobile's next big network transition.
From The Founder
Cisco's Conrad Clemson, recently promoted to head up the company's Service Provider Apps & Platforms developments, talks to Light Reading's Founder and CEO Steve Saunders about how he's bringing cloud video, mobile and virtualization together to empower network operators.
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
Heavy Reading: The Web-Scale View

1|18|17   |     |   (0) comments


At Light Reading's 2020 Vision Executive Summit in Rome, Heavy Reading's former chief analyst Patrick Donegan shared insight from the recent web-scale operators report, which featured research on how web-scale operators view the market, the best web-scale companies to ...
LRTV Custom TV
Cisco's Cloud Scale Networking: Automation, Virtualization & Simplification

1|18|17   |     |   (0) comments


Cisco's Sanjeev Mervana outlines the latest innovations in networking technology at CES 2017 in Las Vegas.
LRTV Custom TV
ADVA Talks Innovation & the Future of Networking

1|17|17   |     |   (0) comments


Ray Le Maistre and Christoph Glingener, CTO of ADVA Optical Networking, discuss the current state of the industry, cooperation and collaboration, open innovation and the future of networking.
LRTV Custom TV
Cisco's Infinite Video Platform

1|17|17   |     |   (0) comments


Cisco's Infinite Video Platform allows service providers to deliver broadcast-quality video over IP networks. Infinite video supports many devices, from 4K TVs to tablets to game consoles. Join Cisco's Rajeev Raman for a brief tour and live demo.
LRTV Interviews
Masergy: Ability to Adapt Key for NFV

1|16|17   |   6:40   |   (0) comments


Speaking at Light Reading's 2020 Vision in Rome, Masergy's VP, Global Technology, Ray Watson, said agility is key to providing the mix and match NFV-based services that are driving business for the managed service provider today.
LRTV Interviews
Equinix: The Data Explosion

1|13|17   |   4:16   |   (0) comments


At Light Reading's 2020 Vision in Rome, Eric Schwartz, president of EMEA, Equinix, talked about how Equinix is helping its customers manage the influx of data today, and how it's preparing for a future filled with millions of connected IoT devices.
LRTV Interviews
Heavy Reading: The Changing Data Center Landscape

1|12|17   |   6:05   |   (1) comment


At Light Reading's 2020 Vision event in Rome, Heavy Reading's Senior Analyst Roz Roseboro talks about how virtualization is impacting data center evolution and how that evolution is affecting the relationship between service providers, data center operators and public cloud providers.
LRTV Interviews
Boingo: Prepping for Millions of Devices

1|12|17   |   5:07   |   (2) comments


At Light Reading's 2020 Vision in Rome, Boingo's CTO Derek Peterson discusses how wireless operators will address the needs of low-bandwidth and high-bandwidth apps at the same time, the need for more MHz, the impact of IoT and more.
LRTV Interviews
Comcast Shows Off Gig Gateway at CES

1|11|17   |     |   (1) comment


With its largest presence at CES in years, Comcast took the wraps off its long-awaited gigabit gateway and a new platform for managing the home WiFi network. Light Reading Senior Editor Mari Silbey sat down with EVP Chris Satchell to discuss the latest Comcast advance, and met with VP of Product Strategy and Development Andrea Peiro to walk through a demo of the ...
LRTV Interviews
Colt: End-to-End Key for 2017

1|10|17   |   6:21   |   (0) comments


At Light Reading's 2020 Vision Executive Summit in Rome, Nico Fischbach of Colt said having a multi-carrier, end-to-end service proposition is going to be key for 2017 -- and SD-WAN is instrumental in making it happen.
From the Founder
Cisco's Clemson on Mobile Cloud Video

1|9|17   |     |   (2) comments


Cisco's Conrad Clemson, recently promoted to head up the company's Service Provider Apps & Platforms developments, talks to Light Reading's Founder and CEO Steve Saunders about how he's bringing cloud video, mobile and virtualization together to empower network operators. "If you think about where we're going… whether it's a mobile application, or a video ...
LRTV Custom TV
VMware Telco NFV Solutions – Preparing for 5G & IOT

1|9|17   |     |   (0) comments


Shekar Ayyar, EVP & Corporate Strategy/General Manager of Telco for VMware, discusses VMware's Telco NFV solutions role and foundation for the Imminent Arrival of 5G & IOT.
Upcoming Live Events
March 21-22, 2017, The Curtis Hotel, Denver, CO
May 15-17, 2017, Austin Convention Center, Austin, TX
All Upcoming Live Events
Infographics
Hot Topics
A Women in Comms Glossary
Sarah Thomas, Director, Women in Comms, 1/18/2017
Is Cable One Beefing Up for Slaughter?
Alan Breznick, Cable/Video Practice Leader, Light Reading, 1/20/2017
Nokia CTO: 2017 Is the Year 5G Gets in the Field
Dan Jones, Mobile Editor, 1/19/2017
TV's Paradox: No HDR Without 4K
Mari Silbey, Senior Editor, Cable/Video, 1/17/2017
Qualcomm Study Predicts 5G Will Create 22M Jobs by 2035
Dan Jones, Mobile Editor, 1/17/2017
Like Us on Facebook
Twitter Feed
BETWEEN THE CEOs - Executive Interviews
Light Reading founder and CEO Steve Saunders chats with Sportlogiq CEO Craig Buntin about sports data analysis.
Eyal Waldman, CEO of Mellanox Technologies, speaks to Steve Saunders, CEO of Light Reading, for an exclusive interview about the 100 GB cable challenge, cybersecurity and much more.
Animals with Phones
Live Digital Audio

Playing it safe can only get you so far. Sometimes the biggest bets have the biggest payouts, and that is true in your career as well. For this radio show, Caroline Chan, general manager of the 5G Infrastructure Division of the Network Platform Group at Intel, will share her own personal story of how she successfully took big bets to build a successful career, as well as offer advice on how you can do the same. We’ll cover everything from how to overcome fear and manage risk, how to be prepared for where technology is going in the future and how to structure your career in a way to ensure you keep progressing. Chan, a seasoned telecom veteran and effective risk taker herself, will also leave plenty of time to answer all your questions live on the air.