Welcome!

Containers Expo Blog Authors: Liz McMillan, Pat Romanski, Yeshim Deniz, Elizabeth White, Zakia Bouachraoui

Related Topics: Containers Expo Blog, @CloudExpo, SDN Journal

Containers Expo Blog: Blog Post

The Network as a Complex Distributed System By @MartenT1999 | @CloudExpo

Yes, we have gotten better at protecting this distributed animal that is the network

Through http://blog.ipspace.net I landed on this article on acm.org discussing the complexity of distributed systems. Through some good examples, George Neville-Neil makes it clear that creating and scaling distributed systems is very complex and “any one that tells you it is easy is either drunk or lying, and possibly both”.

Networks are of course inherently distributed systems. Most everyone that has managed a good sized network before knows that like the example in the article, minor changes in traffic or connectivity can have huge implications on the overall performance of a network. In my time supporting some very large networks I have seen huge chain reactions of events based on what appear to be some minor issues.

Very few networks are extensively modeled before they are implemented. Manufacturers of machines, cars and many other things go through extensive modeling to understand the behaviors of what they created and their design choices. Using modeling they will look at all possible inputs and outputs, conditions, failure scenarios and anything else we can think of to see how their product behaves.

There are few if any true modeling tools for networks. We build networks with extensive distributed protocols to control connectivity and reachability. The protocols and their behaviors are fairly well understood and we design our networks based on our knowledge of how these protocols will react to failures. There is very little modeling of actual traffic or expected traffic patterns. We have all seen networks melt down because of forwarding loops, excessive multicast or broadcast that affect portions of the networks we had not expected it would affect. And a chain reaction of failures follows. I have seen single transceivers go through soft failures (lots of errors and intermittent link state) and bring large networks to their knees.

Of course we learn from our mistakes (mostly) and created protection mechanisms for the things we know can go wrong. We created “hello” based protocols to guard against those soft transceiver failures. We create rate limiting and overload protection mechanisms to guard against those broadcast and multicast storms. We have implemented dampening mechanisms in many of our protocols to ensure state transitions can be managed more gracefully.

But in the end, like the example in the article, we have created artificial limits and protection mechanisms. And they are based on the things we know, because they have hurt us in the past. Less protective but more pro-active, we have implemented hashing mechanisms in our networks to distribute the traffic. As explained, these are generic mechanisms that are designed for uniform best case scenarios. Provide it with less uniform traffic, and the expected distribution is not what we want it to be. The 2014 favorite example of “elephant flow” is perfect in how a single change in a network can drastically change its behavior and performance.

Yes, we have gotten better at protecting this distributed animal that is the network. We have stubbed our toes, bashed our heads and figured out how to protect against it. But we have not taken it to that next level of engineering. The network is a product. It is a highly distributed system where we know way too little about the inputs. We do not model the network and its behavior. We do not test its resiliency. I have asked this question before in this forum and to customers. Every customer has maintenance windows to do proactive maintenance on servers, OSs and the like. Every school and company has fire drills. I have yet to meet a single customer that actually schedules network failure drills to ensure that the resiliency designed into the distributed system actually performs as expected.

We have to start treating the network like the complex distributed system it is. That means that complex algorithms that manage the distribution of traffic and take failure scenarios into account need to be in charge of our networks. Local decision making based on partially complete information can never be enough to truly create a network that pushes the boundaries of what it is capable of. It is not easy, but we have to recognize what the network is. And then approach it with the right tools and methods to model and manage it.

The post The Network as a Complex Distributed System appeared first on Plexxi.

Read the original blog entry...

More Stories By Marten Terpstra

Marten Terpstra is a Product Management Director at Plexxi Inc. Marten has extensive knowledge of the architecture, design, deployment and management of enterprise and carrier networks.

IoT & Smart Cities Stories
The deluge of IoT sensor data collected from connected devices and the powerful AI required to make that data actionable are giving rise to a hybrid ecosystem in which cloud, on-prem and edge processes become interweaved. Attendees will learn how emerging composable infrastructure solutions deliver the adaptive architecture needed to manage this new data reality. Machine learning algorithms can better anticipate data storms and automate resources to support surges, including fully scalable GPU-c...
Machine learning has taken residence at our cities' cores and now we can finally have "smart cities." Cities are a collection of buildings made to provide the structure and safety necessary for people to function, create and survive. Buildings are a pool of ever-changing performance data from large automated systems such as heating and cooling to the people that live and work within them. Through machine learning, buildings can optimize performance, reduce costs, and improve occupant comfort by ...
The explosion of new web/cloud/IoT-based applications and the data they generate are transforming our world right before our eyes. In this rush to adopt these new technologies, organizations are often ignoring fundamental questions concerning who owns the data and failing to ask for permission to conduct invasive surveillance of their customers. Organizations that are not transparent about how their systems gather data telemetry without offering shared data ownership risk product rejection, regu...
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Poor data quality and analytics drive down business value. In fact, Gartner estimated that the average financial impact of poor data quality on organizations is $9.7 million per year. But bad data is much more than a cost center. By eroding trust in information, analytics and the business decisions based on these, it is a serious impediment to digital transformation.
Digital Transformation: Preparing Cloud & IoT Security for the Age of Artificial Intelligence. As automation and artificial intelligence (AI) power solution development and delivery, many businesses need to build backend cloud capabilities. Well-poised organizations, marketing smart devices with AI and BlockChain capabilities prepare to refine compliance and regulatory capabilities in 2018. Volumes of health, financial, technical and privacy data, along with tightening compliance requirements by...
Predicting the future has never been more challenging - not because of the lack of data but because of the flood of ungoverned and risk laden information. Microsoft states that 2.5 exabytes of data are created every day. Expectations and reliance on data are being pushed to the limits, as demands around hybrid options continue to grow.
Digital Transformation and Disruption, Amazon Style - What You Can Learn. Chris Kocher is a co-founder of Grey Heron, a management and strategic marketing consulting firm. He has 25+ years in both strategic and hands-on operating experience helping executives and investors build revenues and shareholder value. He has consulted with over 130 companies on innovating with new business models, product strategies and monetization. Chris has held management positions at HP and Symantec in addition to ...
Enterprises have taken advantage of IoT to achieve important revenue and cost advantages. What is less apparent is how incumbent enterprises operating at scale have, following success with IoT, built analytic, operations management and software development capabilities - ranging from autonomous vehicles to manageable robotics installations. They have embraced these capabilities as if they were Silicon Valley startups.
As IoT continues to increase momentum, so does the associated risk. Secure Device Lifecycle Management (DLM) is ranked as one of the most important technology areas of IoT. Driving this trend is the realization that secure support for IoT devices provides companies the ability to deliver high-quality, reliable, secure offerings faster, create new revenue streams, and reduce support costs, all while building a competitive advantage in their markets. In this session, we will use customer use cases...