In this ever-changing world of IT, the legacy of today was once the future of yesterday: namely, hypervisors. Hypervisors are now considered legacy, even though they are seriously underutilized due to issues with fear, uncertainty, and doubt around using these resources to their fullest. The new technology is containers. However, where are the operational tools to support containers? Where are the procedures? Where are the developers who understand distributed systems? We are moving toward containers at lightning speed without answers to those questions and many more. To move to containers today, we need a strategy.
IT as a Service
IT as a Service (ITaaS) covers private clouds, hybrid clouds, and on-premises clouds, as well as cloud management, including performance management offerings used to create and manage these entities. Consider this IT consumption as a utility. (Read More)
This topic explores Infrastructure as a Service (IaaS) private and hybrid cloud offerings, Platform as a Service (PaaS) private and hybrid cloud offerings, and Software as a Service (SaaS). It also investigates emerging areas such as Desktop as a Service (DaaS), Storage as a Service, and Applications as a Service.
The key areas covered include enterprise applications and use cases that are appropriate for private and hybrid clouds, and how consumers and vendors should select cloud management offerings they will use to manage the various types of cloud services and the journey to the cloud: from A to Z and all points between.
I’ve been speaking a lot lately about the importance of IT governance, especially as it relates to driving cloud (public, private, hybrid) adoption in the enterprise. Although IT governance is critical to the success of having a flexible and agile enterprise, having an overarching enterprise architecture to show how all the components of the enterprise are related and to guide the decisions that affect IT is just as important.
Forrester recently completed an in-depth study entitled The Forrester Wave™: Server-Hosted Virtual Desktops (VDI), Q3 2015, which offers a complete analysis of significant providers in this space, including Citrix, Dell, Microsoft, and VMware. Overall, Citrix XenDesktop was rated high in most categories; however, one area, management tools, showed a significant deficit.
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?
Strategy for cloud automation: there are a lot of articles about the cloud and cloud computing, but I have not seen too many that discuss different strategies to consider when it comes to the automation in your environment. I did come across a nice post called “Legacy Job Schedulers: 3 Effective Exit Strategies to Consider,”1 by Jim Manias from Advanced Systems Concepts, Inc., that had some interesting points and thought it would be a great topic for discussion.
Containers and other technologies are moving administrators, developers, and even operational folks up the stack. In other words, we have abstracted out the hardware and abstracted out the operating system; next, we will abstract out middleware and eventually everything but the code to run. However, when we do that, we no longer train people to be systems engineers; we no longer have the ability to do root cause analysis. We have seen this many times in recent years, and it may just get worse. Root cause analysis is part knowledge and part tools, but most of all an understanding of the system underneath the code. We are fast approaching a time when this skill may become a lost art.