Light Reading

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
More Blogs from Column
Dan Pitt of the Open Networking Foundation (ONF) lays down a challenge to OpenFlow's naysayers.
Telecom carriers need to build, buy or partner for many of the technology enhancements they put into the networks or customer solutions each year.
The future of communications depends on technology licensing, according to Ericsson's Monica Magnusson.
Reflecting on the pivotal role this technology played in the history of computing on its 10th birthday.
This is what industry leadership looks like.
From The Founder
Against the odds, Huawei is growing its telecoms networking equipment business in the US -- that should be ringing some alarm bells for domestic vendors.
Flash Poll
Live Streaming Video
CLOUD / MANAGED SERVICES: Prepping Ethernet for the Cloud
Moderator: Ray LeMaistre Panelists: Jeremy Bye, Leonard Sheahan
Between the CEOs
CEO Chat With Jeff Miller, ActiveVideo

8|28|15   |   19:05   |   (0) comments


Jeff Miller, President and CEO of ActiveVideo, talks to Light Reading founder and CEO Steve Saunders about the impact of virtualization on the TV and video distribution market.
LRTV Huawei Video Resource Center
Vodafone: Mobile Money Is About Customer Trust

8|27|15   |   06.36   |   (0) comments


Light Reading spoke with Vodafone's Ian Ravenscroft about the unique responsibilities and opportunities facing operators handling customers' financial transactions over the network.
Telecom Innovators Video Showcase
Palo Alto Networks on Expanding in the Carrier/Service Provider Market

8|26|15   |   07:54   |   (0) comments


Alfred Lee from Palo Alto Networks tells Steve Saunders about their new chassis-based system, the PA-7080, and how it can benefit service providers compared to legacy firewalls.
LRTV Custom TV
Global Services Forum Preview

8|25|15   |   02:36   |   (0) comments


Light Reading's CEO and Founder Steve Saunders talks about Huawei's upcoming Global Services Forum with the help of Heavy Reading's Patrick Donegan and Teresa Mastrangelo.
Telecom Innovators Video Showcase
Infoblox on DNS Threat Index

8|19|15   |   04:39   |   (0) comments


Dilip Pillaipakam from Infoblox talks to Steve Saunders about his company's core network services.
Between the CEOs
CEO Chat With Ihab Tarazi, Equinix

8|14|15   |   20:18   |   (1) comment


Equinix CTO Ihab Tarazi talks to Light Reading founder and CEO Steve Saunders about the dramatic changes in the data center, cloud and interconnect markets and discusses the impact of SDN and NFV in the coming years.
Telecom Innovators Video Showcase
The Netformx Ecosystem

8|14|15   |   09:39   |   (1) comment


Ittai Bareket, CEO of Netformx, talks with Steve Saunders about the Netformx Ecosystem, which employs cutting-edge prescriptive analytics to help solution providers maximize profits.
Telecom Innovators Video Showcase
Versa Networks on Leveraging VNFs

8|12|15   |   07:37   |   (0) comments


Kumar Mehta, founder and CEO of stealth mode startup Versa Networks, talks with Steve Saunders about how providers can best leverage virtualized network functions (VNFs).
LRTV Custom TV
Transforming the Network Through OPNFV

8|5|15   |   7:09   |   (0) comments


Sandra Rivera, VP Data Center Group; GM Network Platforms Group, Intel Corporation, on OPNFV Arno and how the industry is coming together to accelerate the deployment of NFV and transform the network.
LRTV Huawei Video Resource Center
Huawei ONS Product Demo

8|3|15   |   6:01   |   (0) comments


Huawei shows at Open Networking Summit 2015 in Santa Clara how its SDN and NFV solutions embrace openness.
LRTV Custom TV
End-User or Enterprise Benefits to the New IP

7|30|15   |   04:27   |   (1) comment


Andrew Coward discusses what the New IP means to end users or enterprise customers. He explains compelling reasons, including how every customer can get their own network, from the transformation to the New IP.
LRTV Custom TV
Network Visibility & the New IP

7|30|15   |   02:23   |   (0) comments


Mukund Srigopal provides an explanation of what network visibility is and how it is essential as service providers transition to the New IP. In addition, the importance of the network packet broker is discussed.
Upcoming Live Events
September 16-17, 2015, The Westin Galleria Dallas, Dallas, TX
September 16, 2015, The Westin Galleria Dallas, Dallas, TX
September 16, 2015, The Westin Galleria Dallas, Dallas, TX
September 29-30, 2015, The Westin Grand Müchen, Munich, Germany
October 14-15, 2015, New Orleans Ernest N. Morial Convention Center, New Orleans, LA
November 5, 2015, Hilton Santa Clara, Santa Clara, CA
November 17, 2015, Santa Clara, California
December 1, 2015, The Westin Times Square, New York City
December 2, 2015, The Westin Times Square, New York City
All Upcoming Live Events
Infographics
Cisco's cloud and virtualization portfolio can increase business agility and innovation by building a more flexible network architecture.
Hot Topics
Verizon Hums a Driving Tune
Sarah Thomas, Editorial Operations Director, 8/26/2015
Gogo Approved to Speed Up In-Flight WiFi
Sarah Thomas, Editorial Operations Director, 8/24/2015
Could Market Volatility Hurt Tech IPOs?
Dan Jones, Mobile Editor, 8/24/2015
Sprint's Claure: '3 to 5 Years' to Turnaround
Dan Jones, Mobile Editor, 8/25/2015
Like Us on Facebook
Twitter Feed
September 22, 2015
Media Begins With “Me”
Webinar Archive
BETWEEN THE CEOs - Executive Interviews
Jeff Miller, President and CEO of ActiveVideo, talks to Light Reading founder and CEO Steve Saunders about the impact of virtualization on the TV and video distribution market.
Equinix CTO Ihab Tarazi talks to Light Reading founder and CEO Steve Saunders about data center, cloud and the impact of virtualization in the coming years.
Cats with Phones
Cats Are a Smartphone's Best Friend Click Here
Whoever said cats didn't live to please their humans?