After talking about the “grand vision” of the Software Defined Datacenter (SDD) in part 1 of this series and discussing the individual components required to build out the SDD in part 2, this third part will be all about the three core challenges and controversies:
In part 1 of this series of four posts, we examined the grand vision of the software-defined datacenter (SDD). In this second post of the series, we will take a look at the core components of the SDD (see Figure 1) and provide a brief evaluation of how mature these components currently are.
When I picked “The Journey to the Cloud” as the working title for one of my fall research projects, I triggered some immediate reactions from colleagues and customers, whose opinions I value. And while I typically do not place too much importance on selecting a working title and also did not intend to just warm up an earlier research piece on that same topic, these reactions prompted me to take a minute to think about how we can best target our research for maximum customer benefit. As EMA is conducting this research for our customers – vendors and end users – why not talk to exactly these people to find out which specific issues they want to learn more about? And so we did…
During this year's research for the 2012 EMA Workload Automation (WLA) Radar Report, we encountered a number of very interesting core findings. These research results mostly originated from dozens of conversations with end customers, who have been using WLA software for many years and sometimes even for decades. WLA, by definition, is a mature discipline, as it started during the beginning of mainframe times, then became more complex when organizations adopted distributed computing, and today is faced with a new challenge: the cloud. Please take a look at what our research showed as the most important aspects of a modern WLA solution. The following vendors were included in the report: Arcana, ASCI, ASG, BMC, CA Technologies, Cisco, Flux, MVP Systems, Network Automation, ORSYP, Stonebranch, UC4.
Every March, IBM invites customers and analysts to its annual Pulse user conference. This year, Pulse was all about the more efficient delivery of IT services, a concept that is usually referred to as "cloud". Since cloud has developed into a term that, due to its overuse, is often frowned upon, to say the least, it was great to see IBM try hard to demystify this elusive concept, backing it up with numerous case studies and customer testimonials. The fact that many of these case studies were not as polished as you so often see during this type of show, made the experience actually better. It became clear that these were real customers, implementing "cloud" to solve very specific corporate problems and while doing this, running into very specific IT problems. This is something that just happens when breaking new ground and it speaks for IBM's self confidence to not present only squeaky clean projects at its show.
IT as a Service is one of the hottest topics these days. In a nutshell, it entails the radical alignment of all IT disciplines around strategic business requirements. Instead of having to beg IT for resources and services, as many of us are accustomed to, we can now pick all the resources and services from an easy-to-use online catalog. Workload automation features are finally becoming part of this service catalog, allowing business users to trigger, monitor, and even repair essential job flows.
Almost all of today's business processes are supported and complemented by enterprise IT applications. These applications are often business-critical and therefore tied to strict Service Level Agreements (SLAs). Most enterprises utilize sophisticated monitoring tools to track system health on the application, operating system, hypervisor, hardware, network resources, and storage levels. These health monitoring tools send out alerts to the administrator if any of the warning lights turn yellow or red. When all lights are green, there should be no problem.
Welcome to my Blog on the latest trends in systems management. In this Blog, I will look at systems management from a business process perspective. The initial focus will lie on server virtualization management, cloud systems management and workload automation. Within this context, I will analyze and try to quantify the efficiency gains that the organization can realize by implementing systems management tools and processes. However, as systems management does not exist in a vacuum, it is essential to tie these findings together with the latest developments in neighboring disciplines such as configuration management systems, IT service management, process automation, security, networking, applications management etc.
I had originally intended to make this blog about mental health. A supportive article for those of you trying to support change in your own environment wrestling with the stubbornly persistent caricatures and silos still so dominant in many IT organizations. It was inspired by a rather nasty line in a novel my one of [...]