This week John and I talk about: the state of BSM and ITIL-think in relation to all this cloud hoopla, news from several IT management & cloud startups, BMC’s Remedy OnDemand, and how much pizza Tarus can eat in one sitting.
Download the episode directly right here, subscribe to the feed in iTunes or other podcatcher to have episodes downloaded automatically, or just click play below to listen to it right here:
Show Notes
- Steel vs. Big Iron.
- BSM and ITSM at OpsCamp discussion. What’s the place of BSM, ITIL and friends now-a-days?
- Doug McClure sums up in BSM in 2009 – several startups, but not much from big vendors.
- While Coté was rolling his eyes at a BPM tool earlier this week, it does start to seem like a holy grail when you add in the fully automated provisioning tool chain. We do a lot of dev/ops blue skying.
- Nice clutch of OpenNMS news: OpenNMS user conference, May 6-7 in Frankfort, Papa John’s write-up, helping out in Haiti.
- Cloud Drama – Reuven vs. @samj.
- Tivoli Pulse coming up, trying to do more OpsCamp.
- CloudSwitch – cloud brokers with an isolation technology. Makes me think of CloudCat and going after the “easy kill” of installs.
- CloudShare – virtual labs plus analytics is an interesting, novel play here.
- Quick discussion of Remedy OnDemand.
- Amazon versioning S3 – who don’t like built in version control?
- John will be at the Cloud Connect conference doing Cloud Operations Boot Camp – March 15th. In San Jose.
- WebappVM guys launch and rename to as Makara.
- Nicira – open flow, virtual switch thingy. See Jon Brodkin’s piece as well.
Transcript
Coming soon.
Disclosure: IBM, The OpenNMS Group, and others are clients.
I didn’t want to piss on Johns party over at opscode.com, but didn’t automation replace all the keypunch operators? Didn’t automation replace many of the tape jockeys? Didn’t automation replace the print shop monkeys… didn’t automation eliminate telephone operators and shouldn’t automation replace much of what todays operations do?
Technology moves on if the dynamics and financials make it worth the journey. Ultimately automating a cats hair ball will end up in two things, 1. an automated mess, and 2. more failures as you now get failures in the automation and the hair ball.
The real answer as we move to the cloud etc. is to simplify. That requires gracefully backing out of stuff we did 10/20 years ago and replacing it with forward thinking, not backward automation. Do we really need Vmotion for example? Surely we ought to have application failover and systems these days that have much higher availability, rendering vmotion and much of the complex automation that surrounds it, redundant. If thems your skills… well, just sayin…