From the Blogosphere
Automated Orchestration | @CloudExpo #SDN #DevOps #Microservices
In light of rapid changes to hardware and software, the standard way of managing configurations is no longer feasible
Jan. 2, 2017 12:00 PM
Creating a Customized Automated Orchestration Strategy
Large enterprises today are juggling an enormous variety of network equipment. Business users are asking for specific network throughput guarantees when it comes to their critical applications, legal departments require compliance with mandated regulatory frameworks, and operations are asked to do more with shrinking budgets. All these requirements do not easily align with existing network architectures; hence, network operators are continuously faced with a slew of granular parameter change requests, trying to meet ongoing network requirement changes without having the proper tools in place.
In light of rapid changes to hardware and software, the standard way of managing configurations through hop-by-hop or router-to-router management is no longer feasible. Network complexity today requires control of the entire environment from end to end, and the ability to apply policy changes with the utmost precision across a whole network. Let's consider the path to making these changes:
The change requests then must be fulfilled in line with the user's request and satisfy the network performance requirement of the application while having minimal effect on the other services running on the network.
The next problem is that, though it isn't unusual for teams to fall behind as the changes roll in, when operations is given a complex request, only to realize there is no current network documentation, the results can be disastrous. Often senior network architects, designers and engineers must collaborate to minimize potential side effects, which slows the process even more.
Trying to Make Changes on the Fly
Complicating factors include, as an example, the lack of highly skilled "full-stack engineers," professionals who can program software and make configuration changes with networking on the fly, regardless of the application or the equipment. Operations personnel tend to be generalists, and without a detailed skillset, they must rely upon subject-matter experts who are well versed in various subsets of technology. Alternatively, they must wait on configuration changes to be released by the hardware or software vendor, or engage a contractor from a third party, a slow and painful process at best.
The majority of network projects incrementally evolve and enhance an existing network in the common "brownfield" approach. This is in contrast to the less-common "greenfield" scenario, where the engineers can pick the newest router or product with the most up-to-date feature set. The average replacement cycle is usually dictated by the manufacturer's support cycle, typically five to 10 years. Such a long cycle can create a significant mismatch of feature sets supported, since new firmware is issued every six to 12 months on average, and existing devices are only updated when necessary. Today, engineers can't think of each router or device as being the same but instead must consider what version of the firmware was installed, what hardware plug-in extensions have come and gone, and then mix and match configurations that work from end to end.
Today's multi-faceted cybersecurity landscape has made the security policy of a "vanilla" access list on a router a thing of the past. Simple firewalling and access control lists are no longer sufficient; they must be extended with more sophisticated intrusion detection and prevention systems. And using public internet transport for low-cost bandwidth requires additional layers of secured virtual networks.
Another significant challenge is capacity planning. Many companies are now leveraging Software as a Service (SaaS) and Infrastructure as a Service (IaaS) such as AWS and Azure. Network bandwidth usage and flow patterns have significantly changed, and are evolving rapidly with the introduction of additional services such as rollouts of Salesforce or Office 365, creating unique demands on networks that were originally designed for "internal use only" usage and security concepts. The reality is that adding new equipment to today's complex networks can't be done overnight.
Streamlining the Transition to Automation
This is a good idea that doesn't quite fit the bill. IT helpdesk ticketing systems were designed to assign incoming change requests to the proper engineer, but even still, requests that are handled manually can take three to five days to implement if there is no new equipment. When equipment like a new circuit or router is involved, turnaround time can take 30 to 60 days or more and may require senior architects and networking engineers to implement.
Rome was not built in a day, and neither is a sound orchestration and automation plan.
However, here are a few tips on easing the transition:
No two networks are alike; whether brownfield or greenfield, each one has its own complexities and challenges. Each team will explore their options and find what best serves their particular circumstances. Using the best practices above will help teams create a customized solution that aligns with the approved network model and serves all stakeholders.
Reader Feedback: Page 1 of 1
Latest Cloud Developer Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week