EMA Blog: Business Intelligence and IT Management

IT administrators love to write scripts – at least, the most talented ones do. Scripting provides a powerful platform to automate simple and repeatable tasks. However, like with most powerful tools, there is an overwhelming temptation for scripting to be overused. When faced with a project deadline, a high-pressure failure event, or even just the need to simplify day-to-day events, administrators can unintentionally create scripts that are so complex they actually put the business at risk. I must confess that during my 2 decades-long tenure as an IT administrator and engineer, I’ve written a lot of scripts…a LOT of scripts…and learned a lot of important lessons. Scripting was never intended to replace application programming. Its purpose is to provide a quick and easy resource for performing simple and repeatable tasks. It is not uncommon, however, for scripts to start simple but balloon over time into complex code that is virtually unintelligible even to its author.

Have you ever tried to create a major slide presentation on a tablet? Or edit a large spreadsheet? Or write a long document? Probably not. While it’s certainly possible to perform more substantial business tasks on a tablet, the small screen real estate and limited system resources (e.g., processing speed, memory, graphic support, etc.) are typically insufficient in current tablet form factors. However, carrying a laptop around with you everywhere you go just so you can access email is not very practical either. The reality is that we live in a multi-device world where the average worker employs 3 – 5 different computing devices in the regular performance of their job function. . . . and I would argue that’s exactly how it should be. Each user employs the device they prefer to optimally perform tasks at any particular time or place.

The Havana release of OpenStack was launched on October 17, about three weeks prior to the OpenStack Summit in Hong Kong.  As always, there are many new features -high availability, load balancing, easier upgrades, plugins for development tools, improved SDN support, fiber channel SAN support, improved bare metal capabilities- and even two new core components, Ceilometer -metering and monitoring- and Heat -orchestration of the creation of entire application environments- to admire. Without any doubt, OpenStack is becoming more enterprise ready with each new release .

The Havana release of OpenStack was launched on October 17, about three weeks prior to the OpenStack Summit in Hong Kong.  As always, there are many new features -high availability, load balancing, easier upgrades, plugins for development tools, improved SDN support, fiber channel SAN support, improved bare metal capabilities- and even two new core components, Ceilometer -metering and monitoring- and Heat -orchestration of the creation of entire application environments- to admire. Without any doubt, OpenStack is becoming more enterprise ready with each new release .

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.