(I cross post my week-daily newsletter here, but also feel free to subscribe to it directly if you’d don’t want to follow CoteIndustries.com regularly.) Meta-data Hello again, welcome to #29. Today we have 36 subscribers, so we’re +3 - good job, subscribers! I’d love to hear what you like, dislike, your feedback, etc.: memo@cote.io. (If you’re reading this on the web, you should subscribe to get the daily email.) See past newsletters in the archives, and, as always, see things as they come at Cote.

WTH: How do you see the path towards the software-defined Data centre? AB: What I believe is driving this trend is that developers and organisations are looking to move extremely fast. Developers are getting used to the paradigm of going on AWS (Amazon Web Services) and getting resources immediately instead of weeks/months of provisioning time. That is the benchmark against which they are now holding their internal IT organisations.

(I’ve had a little email newsletter for sometime. It’s fun! People like it and write to me! Rather than rely on the archiving at TinyLetter, I thought I’d post the archives here. However, feel free to subscribe to the newsletter in its proper format, email…or just read it here, whatever you like.) Meta-data Hello again, welcome to #28. Today we have 33 subscribers, so we’re +/-0. I’d love to hear what you like, dislike, your feedback, etc.

With EVO, VMware is pitting the hardware vendors against each other for deals that will likely involve hundreds to thousands of nodes in large enterprises, and the competition will drive down hardware prices and therefore the overall price of the EVO solution. If hardware costs less than it might otherwise without such pressure, that extra margin can come from the software and support in the EVO stack. It’s rough being a hardware vendor.

Good, thorough piece from TPM on VMware’s OpenStack and Docker stuff this week, inc.: The lesson to be learned from this is that OpenStack is just a framework for how the components of a cloud are controlled, but it does not prescribe any particular component for compute, networking, storage, or management. Treating OpenStack like a spec, not a stack at #vmworld

As you may recall, I write about virtual desktop stuff from time-to-time. Teradici recently launched a new workstation remote access package for engineers and CAD/CAM types. My 451 report on the topic is out, co-authored with Scott Ottaway. Teradici is an interesting company in this space as they get most of their revenue (70-75%) from OEM’ing their PCoIP technology to the likes of VMware, Amazon, HP, and many others for embedded use in those OEM’ers products and services.

Gartner’s @cloudpundit has a great way of summing up VMware’s future-proofing problems when it comes to their strategy. tl;dr: they need to straddle two worlds, pre-cloud and post-cloud infrastructure. When VMware says “hybrid cloud,” that straddling of “legacy” IT and “real cloud” seems to be what they mean: That brings us to VMware (and many of the other traditional IT vendors who are trying to figure out what to do in an increasingly cloud-y world).

I am going to sound incredibly churlish here but why on earth Lionel Messi could possibly like our stuff is well beyond my imagination. Flattering though it might be. The same goes for the 20 year career short order cook who posts cat pictures, the retired person who joined Facebook last week, the nurse with a heavy religious bent. On and on it went. Long ago I tried some ads for RedMonk on Facebook.

Early on, vendors who wanted to compete with AWS would speak to the idea of an “enterprise cloud.” All the US Federal activity that AWS had been up to - including that $600m private cloud for the CIA - seems to nullify most of that. I think what will be more important is targeting the type of application supported: old school, three tier app that are statefull everywhere, or cloud native, microservices apps that are stateless (shoving statefullness of to caches and databases).