Zenoss' Alan Conley: Doing the Dynamic Infrastructure Dance
"There is a trend where a company starts with open source and builds out to follow the commercial model. Certainly all of our large customers want a company behind the platform, so they opt for that notion. A lot of smaller companies start in the open source world and then gradually move towards the commercial as they get bigger or get more dependent on those solutions."
Jun 18, 2013 5:00 AM PT
A thin line between traditional IT monitoring and management services and monitoring real-time operations divides what Zenoss offers its customers and what other vendors provide.
The IT monitoring space is becoming more crowded with proprietary and open source software solutions. Zenoss, according to Chief Technology Officer Alan Conley, offers a uniform platform that extends its reach.
"We are categorized as being in the monitoring space, but I really see us as participating in the real-time operations," Conley told LinuxInsider. "It's not just the monitoring aspect of it. We have a uniform platform, so we have more than a bunch of point products, which is what we typically see from the big four."
Having a unified platform lets the Zenoss software talk to more than one type of end point, whether infrastructure, middleware or application layer. That's where the trend is headed: Everyone is trying to get to the point of service level management, he noted.
Zenoss has a free, general purpose, do-it-yourself version, but to that it adds a full commercial enterprise-class version with more capabilities, support, training and other professional services.
Beyond the open source unified platform that Zenoss developed, the company's structure around a commercial open source business model separates Zenoss from the crowded playing field, added Zenoss Chief Marketing Officer Chris Smith.
"What makes a difference from other companies in the pretty crowded monitoring space is that we were built from the ground up to address the challenges of what we call the modern data center and the heavily virtualized software data center," Smith explained.
Prior to becoming the CTO of Zenoss, Conley was the CTO of the Network Management Group at Cisco Systems, where he worked on Cisco's strategy and architecture for cloud management and next-generation networks.
In this interview, Conley talks about the need for a new breed of IT monitoring software and why traditional do-it-yourself open source solutions fall short.
LinuxInsider: What led Zenoss to develop a new approach to IT management services?
Alan Conley: The dynamic nature of these virtualized data centers makes it kind of hard for the legacies with the static tools that have been used for the last 20 years. The old-school monitoring tools are not as well-fit to monitor the dynamic virtualized environments.
LI: How much interplay or competition do you see between open source and proprietary products or business models available to address this issue?
Conley: There are certainly other players in the monitoring space. Most of what you see is commercial, but there is a trend where a company starts with open source and builds out to follow the commercial model. Certainly all of our large customers want a company behind the platform, so they opt for that notion. A lot of smaller companies start in the open source world and then gradually move towards the commercial as they get bigger or get more dependent on those solutions.
LI: So the competition is skewed in favor of commercial or proprietary software solutions?
Conley: There is competition out there, and there are companies that prefer open source, but I think what you are going to see is a trend where more and more people will gravitate in that particular direction where things will initiate with open source and will move towards the commercial experience.
LI: It seems more and more that open source is dividing between a pure open source model and a commercialized version. Is the crossover to a commercial business model becoming the path you see as more prominent?
Conley: Here is an example that helps answer that question. I recently went to the O'Reilly Strata Conference on Big Data. If you looked at what was there, almost everything started on a set of Apache projects. What you saw at the conference was a whole slew of new companies that were building commercial offerings on top of open source.
They have a distribution of basically open source with no support, and they all have a commercial version with added features and support that enriches what you get with the open source version in terms of better scale, better performance, or what have you. This is where we obviously play.
I think you are going to see that trend continue. There are obviously benefits from the open source side. You get broader adoption much faster and you get crowdsourced. I think you will see more and more businesses move in that direction.
LI: How are the challenges CTOs face today different from five years ago because of the growing use of open source?
Conley: I think the word 'change' is absolutely at the core of this. My experience is that technology continues to change at a very rapid pace. I think the big difference is when you look back to five or 10 years ago -- products did not change the underpinnings of the products they sat on for many, many years. They have used the same sound core technologies.
What has happened is so much innovation is happening in the open source climate I've just described that you have to make sure your software architecture, your product, can evolve the underlying platform at a much faster rate than you have seen historically. That means you have to be more aware of what is going on in the industry today, keep an eye on that, and make sure you can update your core platform maybe once every three to four years as opposed to when people used to live on these things for every five to 10 years.
LI: Is it just a singular challenge focused on navigating technical change?
Conley: Another big thing driving the industry is the SaaS [Software as a Service] cloud model. So one of the things that comes up in a CTO's mind is, 'How do I ensure that I architect my product so it can be deployed as a long-term product or as a SaaS solution without incurring a lot of overhead and having divergent code bases, divergent feature sets?' and things like that. So, being aware of that change in the industry and understanding how to architect your product so it can reduce your overall cost to deliver is pretty important.
LI: Is that the only real headache CTOs face today?
Conley: It is very important for CTOs to understand that the infrastructure, the things that you are managing, are no longer static. They become very dynamic. Virtualization is one thing that came up. From a CTOs perspective, being able to understand how to adapt to those changes in environment is very important.
LI: How much of an impact does what you describe have on system administrators?
Conley: It is definitely changing for sysadmins as well. Earlier in my career as an engineer and sysadmin, one of the challenges we were facing was the notion of converged infrastructure and converged services. Traditional sysadmins now have to become more network-savvy, more storage-savvy, and be aware of virtualization platforms. I saw this first-hand at Cisco IT.
LI: What else are you hoping to see in open source development in order for it to be even more viable as a business model?
Conley: In this bigger picture, we always have people harping on how the cloud is here to stay. There is this overriding opinion that it's all about automation. What a lot of that implies is integration. You have to have your open source components have full sets of stable, public APIs so that you can integrate into adjacent systems.
LI: Regarding this integration, what are the major problems that sysadmins face in monitoring the different open source cloud offerings available like OpenStack, CloudStack and Eucalyptus?
Conley: Those platforms focus very specifically on provisioning and configuration of virtual machines, but they have to have the interfaces that can plug into sort of upstream self-service catalogs or engines. For us in particular, the hook there is important to monitoring.
Look at and compare a few of the offerings such as OpenStack and CloudStack. CloudStack is much more mature in terms of the interfaces available to plug into and build what we call a Zen pack, which is what we call our extension module to CloudStack for monitoring.
OpenStack is still considerably less mature -- the interface is not there. So, if you are deploying an OpenStack solution today, the ability to monitor it is missing some of those public-facing APIs. I think that whole notion in open source is making sure that those interfaces are there and you understand how to apply it.
LI: Given that assessment, how does Zenoss' platform fix those shortcomings?
Conley: Our product is based on an open source core model. That is basically free. We have the commercial version on top of that. It's the resource manager, which is the piece that sits right on top of the core itself, that provides the additional functionality that comes with the commercial version, as well as the ability to scale.
The impact module brings the service-level monitoring. It says that, 'I have a bunch of pieces underneath my service that supports databases and messaging infrastructures and virtualized infrastructure and all of the physical infrastructures.' Understanding all of that infrastructure is really important for the impact of each event on that service.
The final piece is our analytics product. It is largely the reporting engine that takes all of that data, understands the service model itself and provides all of the analytics on questions such as, 'when am I going to run out of capacity,' 'what are my service levels looking like' and 'where are we with the analytics?'
LI: Is this product run locally on a customer's hardware or does Zenoss monitor operations remotely?
Conley: We are also in beta testing for an extension of this product to be delivered as a SaaS. It is being built to populate on Amazon Web Services.
We are starting to take advantage of some of the back-end services on AWS to cater to tenancy and shared infrastructure to reduce some of the cost, but the experience to the end user will be pretty much the same whether it is on premises or in the clouds. It is just a lightweight deployment for them in the SaaS offering, so they can be up and running very quickly.