Network automation might be the next big “Ops”.
Gluware is a company dedicated to the art of Intelligent Network Automation and helping companies make the shift to security, agility, and business continuity. The Gluware Intelligent Network Automation platform leverages powerful intelligence to automate and orchestrate large multi-vendor, mission-control networks at scale and without code.
Gluware is also focused on NetOps, which brings DevOps concepts (such as automation, orchestration, and virtualization) into network operations and makes it a part of the development process. The company is currently automating networks for companies like MasterCard, Merck, Ernst & Young, and Global 2000 customers, such as Terracon and Acuity Insurance. According to Jeff Gray, CEO, and co-founder of Gluware, “Gluware has created a layer of automation that is able to go down and crawl along any existing enterprise traditional network and create a layer of automation across both traditional, API-driven, and cloud-driven networking, and create a digital twin of that network.” He adds that this newly-created layer, “not only shares where those issues lie, but also provides the ability to cleanse the network and bring it back to gold standard.”
To digitally transform and create better IT outcomes, what most enterprises are looking for is “to have one layer of automation, where first they can automate what they have extended to modern architectures,” explains Gray. To do this, he indicates it’s important that the companies they work for must affect the changes they suggest internally. Gluware provides the best practices and guidelines, but the enterprise companies must implement them in a certain timescale to make a difference. Gray adds, “But when you start taking away the ability to make changes via a command-line interface (CLI), it forces the organization to adopt automation. And so absolutely, it’s this cultural change that needs to happen. And that is the critical part. Technology is one piece, but the company does need to change the way it’s doing business.”
One thing Gray hits on is the idea that companies should avoid “tribal knowledge” within DevOps and NetOps. “It’s a matter of breaking down silos, getting them to communicate. And it hasn’t been a simple process culturally. But over time, as they start to understand and work together, then it has actually gone quite well,” avers Gray.