The Intigua Blog
In May 2017, the WannaCry vulnerability caught the IT world by surprise. In the blink of an eye, an estimated 200,000 computers worldwide were infected with crippling ransomware. The attack exploited a vulnerability in the antiquated version 1 of Server Message Block (SMB), a critical remote service and file sharing protocol for Windows servers.
We’ve recently started to work with a new cloud services provider - Virtustream, an important and growing member of the Dell Technologies family. Virtustream is a large business, having been acquired by Dell for over $2B. At Intigua we haven’t reached a 10-digit valuation (yet...), but as we started to work with the Virtustream team, we were thrilled to find out how much our two companies have in common. Most importantly, both our companies share a common view of today’s enterprise IT challenges.
The Intigua Packager lets you package any tool agent for use with Intigua. However, we also have an extensive library of tool agents we have already pre-packaged for use with Intigua.
We constantly add new tools and versions to this library. Here are some recent additions:
So you’re setting up a fabulous new cloud-based compute infrastructure. It probably requires some software agents, at least for configuration management and monitoring. In a traditional enterprise on-premise setting, the agents would be identified by their hostname, such as “erpdb01.ca.purplefishfood.com”.
The nice thing about using hostnames is that they are unique and easy to figure out. Enterprises have been working with DNS servers for decades and have taken great care to ensure that hostnames are well-managed.
But what happens when you go to the public cloud? In Amazon EC2, hostnames have an odd-looking format derived from their private IP address, such as ip-172-39-0-172.ec2.internal
Our modern world runs on technology. It takes a team to keep everything working. But, let’s face it, the SysAdmin’s of the world are the heroes who keep everything running smoothly.
DevOps is such a hot topic in the last couple of years. Everybody likes it. What’s not to like about high agility and empowering the guys in the trenches? If you’re starting a new Internet company, there is practically no question: use a small team with a bunch of open-source and cloud technologies, automate your development and deployment cycle for continuous delivery, and voilà - you are practicing DevOps. Granted, discipline and practice are needed - but in a small, single-app environment, it’s relatively easy. But what about most of the real world, where people are working in complex existing environments?
Let’s look at four ways IT Ops and Infrastructure teams currently deploy and maintain software on physical and virtual servers and examine why each approach has diminishing success as scale and complexity increase.
There are three significant problems that plague IT teams as they deploy and maintain agent and agentless server management solutions on 1000s of servers and hybrid infrastructure. Let’s take a look. The Situation: Server Management Processes are too complex, too slow, and too expensive.