Adventures of a Technical MasterMind

Surface computing in depth demo      http://www.popularmechanics.com/technology/industry/4217348.html Microsoft Milan site             http://www.microsoft.com/surface/ Really cool stuff from Microsoft. The video is very impressive. I saw the beginnings of this back in the day. There are a couple of cool older projects which remind me of much of the stuff that I see in the video: Bumptop      http://youtube.com/watch?v=M0ODskdEPnQ http://www.bumptop.com MIT Media Lab AudioPad     http://youtube.com/watch?v=lxAD1QIv_dw http://www.jamespatten.com/audiopad/index.php Enjoy these cool new pieces of technology.        

I will be attending HP Software Universe in mid June. I am particularly interested in this show for many reasons: Mercury integration, specifically BAC/BPM and SiteScope into the old OV product line. Evolution of NNM. Migration of the 2 Helpdesks and Asset systems to a single HP software system. ITIL v3 changes and what HP is doing to support it. MPLS capabilities across other HP tools. UDDI (Systinet) progress.

I was privileged to speak at the Interop show in Las Vegas. My discussion was on Datacenter Modeling. Specifically around using Dependency Mapping and the CMDB to effect monitoring. The discussion went well, and I was given quite a few interesting questions to answer. Overall I got very good feedback on the session. The rest of the show was decent. The educational content was a bit too high level. I would have liked to have seen some kind of ranking that you typically see in other shows. A good range of rankings would be introductory, executive, intermediate, advanced, expert. The show floor was huge and excellent. I met quite a few interesting vendors, which I am interested in perusing. Overall the show was useful but not amazing. Some of the all day workshops would be more useful and in depth. I would have liked to have attended one of them, but I didn't have the time to do so.

I seem to be working on several configuration management projects at once. Everyone uses a different set of scripts, or tools. No one has any documented information about what they are solving with the systems, and what they want to do. They seem to have started with the "backup the configuration of x" requirement, and evolved into: Monitoring (Error detection, service outages, checking for known problematic conditions) Capacity management Reporting The issue without having any documentation of what the systems intended uses are, as well as current uses would make standardizing on software much easier. I'm battling trying to accomplish this, and it's very slow and painful. I think authority will help force changes, which should start to happen here.