Eric Wright of VMTurbo wrote about the death of root cause analysis (RCA) with the rise of microservices. I take exception to this, as microservices aren’t really all that new. Even what’s being called “serverless computing” isn’t particularly new. However, that’s a discussion for another time. The point of RCA is to find the real reasons for failures. I don’t see how using microservices changes this. All we’ve done is add more layers to delve through to find the true root cause of a problem.
Articles Tagged with VMTurbo
Any part of any infrastructure, application, or cloud is data. Data is used by applications, and myriad data is presented to IT organizations for their use, edification, insights, and more. But what really is this data? Can we classify the types of data in some way? Data classifications should not be just “structured” and “unstructured”; they must go deeper than that. To understand how IT operations analytics (ITOA) can act on data, we first need to classify data into something we can comprehend. ITOA leads to insights that can be used to predict capacity, track applications, and tell us when we have security events.
Building a private cloud was a high priority for a number of organizations in 2014. This priority carried over into 2015 because it is hard to execute. For many organizations, it has carried over again into 2016. Of course, the definition of a private cloud has changed in that time, too. Some organizations are happy simply to have consistent VMs deployed in response to a helpdesk ticket. Other organizations aspire to have the AWS in their own datacenter. One significant trend is the use of public cloud services to manage on-premises private clouds. The other trend is OpenStack in the enterprise, rather than only in academia and hyperscale where it started.
IT as a Service (ITaaS) is changing nearly every day. In the past, it was mainly about automating deployment through the contents of a service catalog. Today, it has grown to include IT operations analytics (ITOA). What matters isn’t whether we can select an application from a service catalog, but rather how we monitor and react to issues during the lifetime of the application. With containers, which are all about automation, ITaaS has to change not only to include ITOA, but also to react to the results of the analytics.
We all try to do it, we sometimes succeed, but the increased density of workloads escapes many folks, whether they are in a cloud or using an on-premises virtual environment. Are there ways to help us gain more density within our environments? Is it still fear that keeps us from doing so? Are there real issues we still need to solve? Why are most environments running with CPU to spare? Is there still a fear of running too many things on any one system?
Welcome to The Virtualization Practice’s week-long coverage of VMworld US 2015. Tune in all week for our daily recap of the major announcements and highlights from the world’s premier virtualization and cloud conference.
With all the forward-looking business out of the way (see the Day 1, Day 2, and Day 3 recaps), VMworld took a breath yesterday and focused on other parts of the ecosystem. The first annual Developer Day was held as part of the VMworld DevOps program track, and it included a Hackathon where coders and non-coders could compete for prizes. Non-coders had a series of increasingly difficult challenges to complete. Coders worked to create the most useful, creative, and complex tools and services on vCloud Air, judged at the end of the day, and were awarded prizes like a guitar signed by Alabama Shakes and the Neon Trees, the VMworld Party bands.