October 2016

So during the keynote at VMworld in Barcelona on Tuesday morning, 18 October 2016, VMware showed a demo of how a VMware Cloud infrastructure is stood up in AWS and following that, showed how a virtual machine was migrated with vMotion into the AWS hosted VMware Cloud. This seemed impressive. However, something’s been bothering me and I’ve been to the VMware booth to get an answer but came up short.

The question I have is around processor architecture. If I’m running Intel in my local vSphere environment and AWS/VMware decided to run AMD in the VMware Cloud on AWS, how would you get that vMotion migration to work? It can’t right?

Is there an option to select the processor vendor for the newly deployed VMware Cloud on AWS?


Answers on o postcard or comment section below! Go!


And we have an answer!! Thank you Alex Jauch (@ajauch)!


Published in VMware vSphere

Container technology has been around for quite a while now. Most people would by now have heard about Docker, and a lot of people are using Docker. What about VMware Photon? What’s that? Well again, I’d say that it’s been around for a while, however while people have been raving on about Docker and the container revolution, VMware has been working on their own implementation of container technologies as well as products that utilise and integrate with existing container technologies, such as Docker. At VMworld Europe 2016, VMware announced vSphere 6.5 and one feature that has caught my attention in this release (apart from the long overdue vSphere HTML5 Client) is vSphere Integrated Containers, or simply, VIC. At the moment I’m trying to make sense of all these technologies, how (and if) they fit together and where you would want to use each one. 

RT @elonmusk: The Twitter Files on free speech suppression soon to be published on Twitter itself. The public deserves to know what really…
Follow Rynardt Spies on Twitter