IT 2.0

In the last few years we collectively spent an outrageous amount of time talking and arguing about the “per VM” cost of running workloads on-prem Vs. running workloads in a public cloud.

You try to convey a concept but it’s only when something (else) happens that people have their “Aha moment”.

A few days ago we had a great friend of mine over for dinner.

Last year I wrote a blog post whose title was "Cloud Native Applications for Dummies" that was apparently well received.

Two years ago I joined the VMware Cloud Services Business Unit working on vCloud Air because I sensed there was a shift going on in the industry.

In the last few weeks I have seen some discussions and requests around using fog.io ("The Ruby cloud services library") in the context of vCloud Air.

In the last year or so I have focused primarily on vCloud Air API and Automation.

I have just heard of a massive outage that a localized IaaS Cloud Service Provider is experiencing: they have been down (at the time I am drafting this short blog post) 4 days and counting.

A few weeks ago I wrote a post whose title was Cloud Native Applications (for Dummies).

There have been attempts lately to describe "modern applications" or "modern workloads".

As I draft this blog post on my way back from VMworld 2014, I have mixed sentiments to share.

In this article I am going to show how you can start using Docker on top of the VMware vCloud Hybrid Service.

As I was taking notes with some vCHS workload deployment experiments I thought I'd turn them in a blog post.

I was surfing the web (as usual) a few days ago and an AWS presentation I spotted on SlideShare got my attention.

In the previous blog post I provided a high level (101) theoretical overview of how resource monitoring and capacity management work in vCHS.

This is blog one of a series of two.

Probably my shortest blog post ever.

There are so many things I'd like to show and talk about here that I wanted to dumb down the title as much as possible.

Last week Alessandro Perilli of Gartner posted one of his controversial takes on cloud.

Warning: yes it is one of those highly philosophical posts.

In this blog post I am going to describe the capabilities of the Load Balancing service in vCHS.

In the vCHS API 101 blog post I have walked you through how to find out your vCHS API end-point(s) as well as how to navigate the structure with the RESTClient browser plug-in.

When people think about vCHS they think about the vCHS portal.

In the last few weeks I had lots of discussions with customers and partners regarding the concept of T-Shirt Size instances as well as the nuances of storage management in both AWS and vCHS.

Last week at VMworld 2013 in San Francisco, among various other sessions, I presented "a Parallel between vCloud Hybrid Service and Amazon Web Services" (session #PHC5123).

I have just got back from VMworld 2013 where, for some reasons, I ended up in many "how did you get this blog thing started" and "when did you start speaking at VMworld?"

When I see my proposals being accepted at VMworld... my ego typically gives way to fear and anxiety.

Today (technically it's still 11:59 PM Pacific Time) VMware announced the vCloud Hybrid Service (aka vCHS).

Having worked for about 3 years with vCloud Director I have to admit that the networking subsystem is the one that takes more time to digest.

Yesterday morning I woke up and found myself being mentioned in one of Randy Bias' blog posts on the Amazon Vs VMware battle.

Last week I posted an article on the VMware vCloud corporate blog (re-posted here).

This article was originally posted on the VMware vCloud corporate blog.

Backup and restore (of consumer workloads) in a vCloud Director environment is a hot topic.

I apologize for the catchy title (I need to drive clicks, somehow).

I keep bumping into discussions where people try to compare vCloud (Director) and OpenStack.

There has been some turmoil lately in the industry when VMware announced that wanted to join the OpenStack community.

vCloud Director 5.1 has introduced a fair amount of new functionalities.

In the last 3 years I spent most of my time advocating that the cloud world is marching at a (very) different pace based on where you are and who you are.

At VMworld 2012 VMware showed something dubbed Distributed Storage.

I spent a good 10 years of my IT career looking closely to hardware platforms (at IBM STG - Systems and Technology Group).

So far I have only missed a single VMworld in the last 8 years.

A few weeks ago, at TechEd, Microsoft announced Azure Virtual Machines.

One of the problems VXLAN is supposed to solve is the possibility to decouple (and abstract) the compute capacity from the underling network configuration.

There have been a lot of discussions lately about SDN (Software Defined Networking).

In the last few months, among other things, I have been working on the document in subject.

Very often VMware gets compared to the Ferrari of cloud computing whereas AWS gets compared to the Ford.

For a change, last week on twitter there was a discussion about multi hypervisor deployments.

This isn't the counter argument to Gartner's Magic Quadrant (I think).

This morning I was on the phone with Ivan Pepelnjak (@ioshints) to decipher some of the paragraphs in one of his latest posts on Nicira Open vSwitch inside vSphere.

There have been a lot of discussions lately about a topic I find extremely interesting: vendor lock-in.