


CloudCenter provides the same kind of IT systems aggregation that Alexa does for IoT devices. They’ve renamed it to Cisco CloudCenter (unfortunately not as cool a name as CliQr), and it is a key element to Cisco’s cloud strategy. “So uh, Amazon, could we make Alexa work with vCenter and my Nexus 9k?” Wouldn’t that be sweet? An aggregator of all these different architectures and solutions? Man, somebody should get on that…oh snap, they did.Įarlier this year, Cisco completed the acquisition of CliQr Technologies Inc. Now you’ve got yet another interface and way of consuming compute/storage/networking resources. It’s even more harrowing if you are a hybrid shop that has some workloads in the cloud in addition to on-premesis. Well, disparate interfaces and different ways to work with products and solutions within IT is a huge problem when trying to coalesce these things into a SYSTEM that works as one converged experience. What else sounds like having a bunch of different interfaces for managing different ”things?” How about every product and solution within IT? I’ve previously written about automation, and how the day-to-day tasks in IT should be more like the cloud. the Wink app for flipping a light bulb on or off, now I can just say “Alexa, turn on Garage” and two lights from two different manufacturers will simultaneously turn on. Instead of worrying about going into the Phillips Hue app vs. Her ability to control a variety of IoT devices through a common verbal UI greatly simplified the experience of my day to day life in using these devices. Yeah, having three different interfaces is obnoxious.Įnter Alexa. I have three different vendor’s IoT lightbulbs in my house. This can be extremely frustrating, especially for someone who likes to dabble with different brands of devices that all do the same thing. Connected door bells? What color would you like?Īs an IoT customer, there’s one dirty little secret that nobody talks about when you’re starting to get into the device game: all of these little devices are managed by different apps, with different interfaces, and very few of them natively work together. Want connected power outlets? Yep, lots of those. Want connected lightbulbs? Well, there’s about a gajillion different options there. Despite the potential security risks, for me personally, IoT is a step in the direction of the ST:TNG experience. This is not a post about security, and we’ve recently featured an article on the evils of bad IoT security, so buyer of IoT devices beware. Oh yes, I have IoT devices for days scattered throughout my house. With my previous research, I had run across a nifty little feature that the Amazon team had included: the ability to control Internet of Things (IoT) devices on a home network. I ran through the verbal commands I could give, tested where in the room she would hear me from (literally everywhere), and poured over the web UI to see what else I could make her do. When she (yes, the anthropomorphism started early with this one) arrived in June of 2015, I totally geeked out. Lucky ducks, getting their hands-on units early. I read every review that TechCrunch or Engadget or any other tech news site wrote. You can imagine the waves of childish joy that fell over me upon learning of Amazon’s Echo (or Alexa, since I don’t know a single person that calls it “Echo”). If I had to pinpoint anything in my life that drove me to IT, I think it would have to be how much I enjoyed the idea of the helpful computer in ST:TNG that made people’s lives easier. One of the key elements of this show was the ship’s computer, LCARS, which could control and interact with various other systems and sensors of the ship on behalf of the crew. I grew up LOVING Star Trek: The Next Generation.
