Search BMC.com
Search

Optimize IT

2 Posts authored by: Richard Voninski
Richard Voninski

Tool Evolution

Posted by Richard Voninski Jan 31, 2011
Share: |


Friends know I am passionate about my photography. I am always trying to hone my craft and looking for the latest and best techniques to produce the best results. HDR (high dynamic range imaging) is the ability to take multiple photographs of the same image with different exposures and then to combine them in order to get better shadow details and highlights. Without blending images it is sometimes very hard to achieve an image with a good balance of shadows and highlights. The idea for HDR has been around since the early 2000’s and with some images people have achieved some great results but it has been very hit or miss. In the mid 2005’s some companies started to write some tools that allowed us to combine images but again the results were hit or miss and the tools had controls that were difficult to use and understand. Recently companies are just starting to put together tools that are both easy to use, repeatable results and controls that make sense to use. The image here is an example of HDR and is a blend of 5 images taken in 1/3 stop intervals.

 

_MG_2034_HDR.jpg

 

I started to think about how BMC’s tools are very much like the HDR example I illustrate above. We have a vast collection of software with varying capabilities (and ease of use) and strive to refine, enhance and integrate these solutions so that we can solve problems our customers give us. When I 1st came to BMC 4 years ago the idea of being able to choose a specific type of computer and service from a browser and have all of the components (server, software, configurations, monitoring, network containers, CMDB etc) all get kicked off was definitely a seed in our minds but a lot of work needed to be done in order to make it work. So we went through a variety of stages to develop the solution (which we call CLM – Cloud Lifecycle Management) which required customer input, engineer input and a hell of a lot of brain (I mean sweat) equity to develop our initial solutions. Much like the HDR example this solution is evolving over time and requires the attention of engineers, developers and customers ideas in order to grow.

 

One last point I would like to make. Recently I have been working with a customer who is beta testing our 8.1 Bladelogic for Servers solution. I ran a week long seminar where we went through all aspects of server lifecycle managed through Bladelogic. This customer is a large Solaris customer and needed to provision virtual zones. Since they were running on our beta version I engaged our development team directly to have some detailed discussions. The developers not only provided the information required to teach the customer but they actively solicited from them ideas on how to improve the product and wanted to clearly understand how the customer would be using the functionality within their organization. I have been on other POC’s (proof of concepts) where specific use cases that customers have asked for have become ‘out of the box’ functionality in the next release of the software. We need your help to understand your organizations functions and how you would like our software to work in order to enhance (and improve) the functionality.

Richard Voninski

How we got here.

Posted by Richard Voninski Sep 21, 2010
Share: |


Today I am just thinking about where we have come from in our industry over the past 20 years.  When I started out I was lucky enough to work with (shhhhh) top secret hardware from IBM.  Something called an IBM RS6000.  I remember my 1st machine running the max 32MB of memory and (gulp) I had the bad boy hard drive.  A whopping 857MB drive that cost as much as my car at the time.  Nowadays I regularly work with single photographic files larger than 857MB and I think my wristwatch has more beef than the memory on that 1st system.

 

I mention these since we also need to look back at the industry over the past 20 years to understand how we have grown with respect to managing our infrastructures.  Back in those days we were starting to think of incorporating MIBs and creating SNMP traps related to not only networking events but also systems.  We used to think about how cool it would be to somehow relate these events to business systems.  Being able to automatically find and fix problems detected was not even on our radar.  We quickly discovered that we had far more events than we could handle and ‘boy who cried wolf’ syndrome was prevalent in our NOC.

 

Today our industry has really moved forward.  We have thought about the lifecycle of enterprise management and have come up with innovative ways to not only collect events but to also parse out events that are not relevant.  We have integrated our systems to relate when mission critical systems are not optimal or not working.  More importantly we can relate this information directly back to how it is impacting our business.  And last but not least when problems are detected we can fix our systems (application, systems, networking components) in an automated fashion and maintain a constant record and audit trail for all changes that have occurred.

 

The future of enterprise systems management is constantly evolving and changing.  Advances in detecting, fixing and reporting on events are most definitely part of it.  But I wonder what other changes will be happening with not only technology but specifically Enterprise Service Management (ESM) over the next coming years.  It will be an adventure for sure!

Filter Blog

By date:
By tag:
It's amazing what I.T. was meant to be.