network automation | The Blog Pros

June 30, 2020

JMeter Netconf Plug-in and Network Service Automation

Network service automation-related requirements are usually realized by means of commercial or open-source network orchestrator or controller software system. However, for some temporary or urgent needs, software patch or version development, upgrade, and change are often involved, which sometimes makes network engineer feel like "to break a fly upon a wheel". In fact, it can be realized through a light-weight way, JMeter Netconf plug-in implementation and network service automation process customization without compiled code based on JMeter framework.

JMeter Netconf plug-in implementation includes two modules.

February 14, 2020February 18, 2020

Beam-Up Load Balancing: The Portable Next Generation App Experience

We’ve seen many of the technological advances described in the Star Trek milieu become reality over the last 50 years, from personal communication devices and instant translators to GMOs, medical robots, 3D printing and weapons that stun.

But, ah yes, the matter transporter. By far, the invention that captivates us most.

November 15, 2019

The Mindset Required to Treat the Network as Code

Changing the way you network requires you to change the way you think.

In order to accelerate automation, network operators need to change the way they think about managing the network and incorporate DevOps practices. By adopting modern agile processes, the benefits of treating Network Infrastructure as Code becomes more attainable. That being said, network as code initiatives require a mindset shift to enable success. Below are five essential concepts that serve as building blocks.

You may also enjoy: How You Should Treat the Network as Software

Remove Humans From Network Device CLI

Transformational thinking is required when discussing network and software principles in conjunction. Questions such as, “What does each line or block of configuration mean to a network device?” and “How does it get managed and applied to the network device?” arise and require answers. However, if network engineers are still leveraging CLI to manage device configurations, there's no easy migration to the network being treated as code. Software code is stored in repositories (not template files) which allows developers to apply robust pipelines and processes in order to solidify deployment and reduce errors while increasing frequency. As a result, to move towards Network Infrastructure as Code, device configurations cannot be managed via templates, but rather in source code repositories.

February 8, 2019

Don’t Confuse Business Process Management with Network Automation

It is not uncommon for enterprises to confuse the role of a Business Process Management (BPM) system with that of a network automation solution. Because there are a lot of similarities between the two, we often see organizations attempt to leverage BPM systems to automate network activities in an effort to leverage their existing investments in these tools. Additionally, the allure of open source BPM options is often mistakenly seen as low-cost alternatives to network automation solutions. While the differences between the two are vast at their core, they are often overlooked or discounted in the planning process due to their common traits and similarities at the surface. Inevitably, their differences always present themselves as major problems during implementation when operators discover they can’t force a network focused automation process into a system not designed with that in mind; it’s just not the right tool for the job and as a result, falls short in automating critical network operations.

When looking at the capabilities of a BPM system as compared to a network automation solution, they both share similar features such as: