Welcome!

Eclipse Authors: Pat Romanski, Elizabeth White, Liz McMillan, David H Deans, JP Morgenthal

Related Topics: Containers Expo Blog

Containers Expo Blog: Blog Post

Types of Network Automation

In networking, workflows are awfully complicated

In networking, workflows are awfully complicated.  There are many workflows, and the exact nature of each depends on a number of variables.  What task comes next is often dependent on the outcome of the previous task, and there is a large amount of data to navigate sometimes to complete a workflow.  Nevertheless, there plenty of opportunity to identify and automate common tasks and segments of workflows.  Once we’ve identified these, we need to ask ourselves, how exactly should we automate them?

Encapsulation
“Encapsulation” means a vendor (possibly a third party vendor) has written software that accomplishes the same thing the workflow does, but usually not the in the same linear way a customer would do it.  Sub-components within an encapsulation have well-designed interfaces for the purpose of accomplishing the goal.  The encapsulation would likely be written in Java or C.  In networking, encapsulated workflows are usually specific to a vendor’s product and often lack flexibility and features.  Encapsulated workflows will manifest as products or product features.

Consider the following workflow:

Untitled Drawing

Figure 1 shows a simplified packet walkthrough for a device.  Here, in the course of evaluating what is happening to a packet passing through this device, we have discovered a filter policy applied to the ingress interface.  This policy has two terms, and each of these terms references an access-list.  A network engineer would need to evaluate this filter policy to determine if it is doing something to the packets of interest.  The thing is, policy languages have a great deal of expressiveness and grammar.  They are also proprietary.  After the filter policy is evaluated, this workflow follows the forwarding pipeline to the egress interface.  If you are an expereinced network engineer, you will know that there are other elements in the pipeline that should be checked for any given network device.  However, there is enormous variation in the structure of the pipeline from one platform to the next.  Therefore, this is a great candidate for discrete encapsulation.* There are more effective ways of achieving the goal of a packet walkthrough than the way a network engineer must do it now (particularly for SDN products), and vendors know their platforms and policy idioms best.

*Discrete means it’s a workflow with a beginning and an end.  It can be manually invoked by a user, and runs for a finite amount of time, reaching some conclusion.

Automation
A workflow automation, on the other hand, consists of sub-components that are “glued together.”  These components were not built especially for automation, and the interfaces between these components were not designed for any particular workflow.  Automations can be developed by the customer, and very frequently discrete automations are employed by network engineers.  A great example here would be a script to configure the login banner on some number of devices.  These automations are written in “softer” languages like Python or Perl.

There is a clear need for Continuous Automation in networking.  Plexxi’s own DSE, now an integral part of the OpenStack Congress project, attempts to address this need.  As the name implies, Continuous means it’s an on-going process.  In the case of the Congress, it is a modular, event/data driven system.  In an environment where there are a plethora of protocols and APIs, each with their own idiosyncracies, this kind of automation makes sense.  Particularly in the context of an open-source community.

Hybrid
Curiously, some workflows may best be addressed by a combination of automation types.  For instance, if a customer wanted to know what was going on in the network relative to a particular application, that workflow automation could use the packet walkthrough encapsulation of a vendor combined with an automation tool like the DSE to harvest network meta-data from external systems about application endpoints.  This could yield a network map of the application’s endpoints along with visual indicators of issues in the network that could be impacting to the application.  In this way, the network engineer could quickly and accurately gauge the health of the network in the context of an application versus engaging in a tedious and error-prone search “by hand.”

Conclusion
Customers, vendors, and open source communities should work togethor to make networking better.  Identifying common workflows and determing the best way to automate them is a good first step.  This will require vendors to think differently about how they develop their products, with their user’s needs in mind first.  Traditionally, just getting a network feature to work and interoperate was the goal, but now we must consider how this feature fits into common workflows performed by network engineers.

[Fun fact:  Broccoli is a member of the cabbage family.  In spite of this, Broccoli tastes good.  When someone offers you cabbage, they are insulting you.]

The post Types of Network Automation appeared first on Plexxi.

Read the original blog entry...

More Stories By Derick Winkworth

Derick Winkworth has been a developer, network engineer, and IT architect in various verticals throughout his career.He is currently a Product Manager at Plexxi, Inc where he focuses on workflow automation and product UX.

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...