Announcing Google Cloud VMware Engine
cloud.google.com
cloud.google.com
When I left in early 2016, soon thereafter VMware ditched that partnership in favor of... IBM. No comment.
And now it's 2020, IBM is far behind everyone else in the cloud, and VMware and Google are cranking along just fine. This partnership makes a ton of sense for both of them. AWS is eventually going to lose its "monopoly" over cloud (disclaimer: I was at AWS 2008-2014).
It gives me a good feeling. Especially for the very talented engineers that I met on both sides. Sometimes they have to put up with a ton of red tape and politics. At least this will make some of them smile.
I don't know that this start as early as 2014. Great work though.
The transition to partnering with IBM is baffling just like what you express.
Oh yes. Very much so.
Disclosure: I work for VMware.
GCP purchased CloudSimple who provides managed VMWare running on bare metal. This isn't a solution co-developed between VMWare and GCP, nor is this a 1st party VMWare solution. I'm not even sure if this is running on GCE, or if its just a re-branding of CloudSimple as GCP VMWare Engine
VMWare Cloud on AWS was built by VMWare to run on AWS ec2 bare-metal instances, and is managed by VMWare themselves.
While similar, they are different.
It might tickle you to learn of Project Pacific, an upcoming rewrite of VMware to run seamlessly on Kubernetes by default, with an upgrade path for existing installations
Is VMware developing it because their installed base shrinks as people are moving to bare metal K8s and they simply need to counter that? Or is is there some other benefit such as retiring some parts of their codebase e.g. replacing VSAN by CSI?
Any idea what VMwares motivation is?
Google theoretically has a similar pitch with Anthos but they’re really not good at sales and GCP has a lot of basic catch-up to do in most areas other than GKE. Say what you will about VMware, they know how to sell effectively and don’t ignore features which aren’t cool CS problems.
You didn't specify what the hardware cost you, nor what it would cost someone else to buy new and how it compares to cloud servers. Add to that lack of redundancy, having to do hardware maintenance yourself, no add-on services unless you run and manage them yourself, no flexibility in scaling up or down, etc.
IT is probably perfect for your use-case, but not for the use case of the people who choose the cloud.
For clarity's sake, my setup cost ~$10k, and includes a 12TB ZFS NAS server, a 10GBe back end, 2 ESXi hosts totaling 16 cores, 256GB. It also took many weekends to set up (and labor isn't cheap).
The uplink is mere Comcast, and, at 30Mbps, does not come close to rivaling a cloud offering. Also, I'm unable to scale as fast as the cloud (think weeks instead of minutes).
On the positive side, for those of us who love infrastructure, there's nothing like running your own, very small, cloud.
Disclosure: I work for VMware.
... to put it delicately, why do corporate VDI management teams always have such terrible ops practices?
I have literally never run into one that even does things like proactive utilization and response time monitoring.
Non tech companies see tech refresh and upkeep as a pool from which to steal people or dollars for other stuff. Until something breaks in a way that it hurts the business.
I eventually switched to RDS to save some money.
I have another 2008R2 server running IIS that was launched at the same time and is still in service on the same hardware.
The question is whether something has changed.
> We have important news about your account (AWS Account ID: 288053528466). EC2 has detected degradation of the underlying hardware hosting your Amazon EC2 instance (instance-ID: i-0480b1eb4617c84f3) in the us-east-1 region. Due to this degradation, your instance could already be unreachable. After 2016-08-16 01:00 UTC your instance, which has an EBS volume as the root device, will be stopped.
> You can use vSphere Fault Tolerance (FT) for most mission critical virtual machines. FT provides continuous availability for such a virtual machine by creating and maintaining another VM that is identical and continuously available to replace it in the event of a failover situation.
> The protected virtual machine is called the Primary VM. The duplicate virtual machine, the Secondary VM, is created and runs on another host. The primary VM is continuously replicated to the secondary VM so that the secondary VM can take over at any point, thereby providing Fault Tolerant protection.
> ...
---
[0]: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsp...
sched: Unexpected reschedule of offline CPU#1!Softlayer clearly needed a change of direction / leadership, and I guess we'll never know, but i feel they (via IBM) took a left turn when they should have gone right. Instead of trying to become cloud, they should have doubled-down on baremetal. What they _really_ needed was a pricing page that didn't force you to go through sales and reflected the price that you'd eventually get (50% less than what they advertised).
Although they filed for Chapter 11 about a month ago.
IBM would spends 100s of thousands of dollars per Q buying the keyword "VMware" and send people to a page that did nothing.
One of the most expensive keywords in the company was VPS, which was a broadmatch term. There wasn't even conversion tracking in place and they spent millions per quarter in PPC with terrible results.
I've seen many instances where they spent more than my annual salary on keywords over 1 week with no results to show for it.
This was despite having about 10 people on the IBM side to "manage" stuff (excluding multiple layers of management) and several people on the ad agency side to "execute", with more focused on "strategy" and others focused on,"analytics".
It doesn’t convert.
I've seen teams that spend most of their (7 figure per Q) ad budgets on branded keywords (vs unbranded) despite having top organic rankings, because no one knew any better.
The agency makes commissions on ad budget spent, so there was no incentive for efficiency.
The inefficiently was incredibly painful and no one gave a damn on either side..those that knew what they were doing didn't last or were pushed out.
(this is not a unique issue, from a PwC study last week 50% of ad spend is taken by middlemen rather than the publisher... the entire ecosystem thrives on inefficiency)
How? I could see it becoming a duopoly with Azure, but Amazon has a huge lead that I don't see being lost. Customers shackled to AWS infra won't move. Development and egress costs are a huge moat.
They lists one possible node at $10/hour ($7200/mo) before contract length discounts:
> CPU: 2.6 GHz (3.9 GHz Turbo) x2, 36 cores/72 hyperthreads
> Memory: 768 GB
> Data: 19.2 TB NVMe
> Cache: 3.2 TB NVMe
I could already import VMDK's to run in GCE. Obviously this is not intended for that, but rather to provide vSphere/vCenter/ESXi in the cloud. Where I've used these in the past (for relatively low-tech IIoT work), I'd often "pull" the VM's off the on-prem server and run 4-12 VM's on my laptop to simulate and configure machines for chemical plants. If I was in the office, I could RDP into the machines running on the on-prem server and would be able to enjoy a high performing desktop environment. Obviously as I was in the same building as the vSphere/ESXi host, latency was very low.
I've had significant issues with latency in the past trying to use RDP/VNC/etc from Houston to any of GCP's datacenters and wonder if that would affect quality of service for this offering. Will a lot of users be remoting into these VM's to use boxes running Windows/GUI/etc? Or is this a very different use case?
> Google Cloud VMware Engine is expected to be generally available to customers this quarter in the North Virginia (us-east4) and Los Angeles (us-west2) regions.
> We plan for the service to be available globally in eight additional regions—London, Frankfurt, Tokyo, Sydney, Montréal, São Paulo, Singapore, and Netherlands—in the second half of the calendar year.
There are a lot of great colo facilities for this type of hardware. Using secure boot, TPM, LUKS and tamper detection, it sure would be hard to break into your server even if not caged. Most of these facilities have video cams and modern security protocols.
However, if you can migrate your workloads to Kubernetes with KubeVirt and others then I'd advise you avoid VMware like the plague.
Not every company has the need to staff all of these specialists.
[1] https://cloud.vmware.com/vmc-aws
[2] https://blogs.vmware.com/performance/2019/02/hybrid-cloud-vm...
If you can't do that already (and I'm fairly certain you can), you shouldn't have to wait much longer -- as this "partnership" and their others e.g., with AWS) illustrate.
I recently posted about installing and trying the VMware ESXi hypervisor to create a homelab here: