Particularly bad timing since just today the San Francisco Chronicle is reporting that foreign airlines are now asked to use GPS for landings at SFO. What could possibly go wrong?

The whole idea of SDDC and Cloud Computing is to basically end up with "IT as a Service". The rest are just marketing words. The goal is to have a service pretty much like electricity: you don't necessarily care where it comes from or how it's delivered to your premises. All you care is that it's there, it's reliable, it's consistent and you know exactly how much you are paying for.

The problem I've seen in the 10 years I've been in this particular industry, is that very few large companies are doing chargeback from IT to their internal customers or business units. IT has been historically seen as a shared cost for the company which adds tremendous pressure every year to cut more and more and try to leverage economies of scale whenever possible. Once you implement chargeback (even if it starts as a showback only) you can effectively pass that cost to the internal customer so you end up shaping their behavior depending on their own funds allocation, not IT's.

The next step is to have accurate forecasting so you know exactly how much infrastructure to have available, particularly if you implement service tiering. This doesn't mean that IT will have a free ride, and it will still be expected to be competitive with external cloud providers, but at least is something more manageable than the status quo.

It will explode with poisonous gas as soon as the sensor detects Duke Leto nearby!

OpenStack has the potential to become the ultimate IaaS multi-vendor glue API, and now that the Foundation is established and a number of large players are committing resources and actual code (VMware, HP, IBM, Rackspace, etc, etc), things are taking shape at an amazing rate.

I'd say yes, embrace the AWS API as a baseline, just to make sure developers can port their applications as seamlessly as possible from AWS to OpenStack and viceversa. Just don't think this has to be all or nothing. Since not every use case can be fulfilled by AWS, I see absolutely nothing wrong with creating brand new APIs and operational models to address the needs of whomever is implementing OpenStack out there, as long as it's clear that using them would make your application incompatible with AWS. For many use cases, that's irrelevant.

Kudos to AWS to having come out with that model, but innovation cannot stop for fear of incompatibilities.

Come on dude! It's so easy to be dismissive when you don't have a clue what are you talking about. Let me break your bubble: there are geeks that are hipsters, foodies and that just love the hedonistic pleasures of life. We all converge in this site at some point and share things that matter to all of us, but this is by no means all we are in life.

I've had to learn to appreciate our differences with fellow geeks and nerds that have completely opposite political views for example without demonizing them, and in the process I've learned a thing or two. Don't fall in the "us" and "them" rhetoric and learn to respect people that care about different things.

We are at the very beginning of this technology. You can't possibly say there is no legitimate uses only because you haven't thought of any. Besides, the image you have in your mind of a drone can change radically in the next few years (think insect-sized drones for example).

No, Whonix is a system. The key part of the system is the Gateway which is indeed Linux, but the Workstation portion can be easily swapped by Windows or anything else. Read a bit more before you comment.

You can achieve the same result today with Whonix which allows you to "torify" basically any network I/O traffic from the workstation VM. Heck, you can even have a Windows VM go through the Tor gateway for that matter.