Earlier quoted context omitted.
Dell private cloud lock in would be the death of any company. You don't want to be isolated to one hardware vendor. We've told Dell to kick rocks many times for renewals and would not be able to do that if we were in their Cloud, which requires Dell hardware. Don't do it
It’s not their Cloud, you buy a bunch of PowerEdge R7725 for example and then choose between OpenShift, VCF and one other I can’t remember at the moment. It’s on prem
Leaving VMware just got harder after Broadcom pulled VDDK downloads
151–160 of 161 posts
Re: Leaving VMware just got harder after Broadcom pulled VDDK downloads
#152Earlier quoted context omitted.
It’s not their Cloud, you buy a bunch of PowerEdge R7725 for example and then choose between OpenShift, VCF and one other I can’t remember at the moment. It’s on prem
The problem is you must use Dell hardware. Sure it makes being hypervisor agnostic much easier, but you then become locked into a single hardware vendor that has you by the balls every 3 years when hardware refresh comes along. We've switched between HP and SMC several times when Dell has tried to extort us.
Re: Leaving VMware just got harder after Broadcom pulled VDDK downloads
#153Earlier quoted context omitted.
The problem is you must use Dell hardware. Sure it makes being hypervisor agnostic much easier, but you then become locked into a single hardware vendor that has you by the balls every 3 years when hardware refresh comes along. We've switched between HP and SMC several times when Dell has tried to extort us.
I can’t run HP or Super Micro in my industry.
Re: Leaving VMware just got harder after Broadcom pulled VDDK downloads
#154Earlier quoted context omitted.
You are hallucinating and don't have any clue what you are talking about (VMware employee #10/11 -- I lost count, First Director of PM at VMware). VMwware sure as hell did not invent the hypervisor, and we were damn careful not to ever claim that. The early unique IP was how to enable a hypervisor to use dynamic translation where required to work around non-virtualizable x86 instructions, we also did well with how to…
What he said. I was a VMware workstation user in the late 90s. I worked on the VMware monitor team back in 2007-2008, which probably put my employee number way in the 1000s. Ole Agesen, Carl Waldspurger, and other early folks were still there. Back then "kvm" meant a remote keyboard/video/mouse device. Linux kvm was announced in 2006, and released in 2007, and required hardware virtualization, which was first release…
Re: Leaving VMware just got harder after Broadcom pulled VDDK downloads
#155Earlier quoted context omitted.
Proxmox is amateur hour. No enterprise support
> Proxmox is amateur hour. No enterprise support 24/7 support will be available starting in October: * https://www.proxmox.com/en/about/company-details/press-relea... The other thing perhaps worth noting that the entire stack is open source, even Proxmox's 'special sauce' for management. Depending on your organization, if you can solve a problem with Debian (and Qemu) you can solve a problem with Proxmox.
Re: Leaving VMware just got harder after Broadcom pulled VDDK downloads
#156Earlier quoted context omitted.
Another ex-VMware here (9 years on the Workstation team). It's so very sad to see... I grew up there from a career standpoint and I was proud to be there, loved being there, and I just don't recognize it anymore. I agree with your point about "winning was the default state." I joined during the Diane Greene era and left in the Pat Gelsinger era, spoke to all three CEOs at different points in one-on-ones, and learned…
What do you think was the root cause?
The company began to grow fast in the years after I joined. VMware's early culture was amazing (a template for any company, imho), but it's hard to maintain that with fast growth. Not a unique situation, but I feel it had an impact on how we addressed certain challenges.
ESX was big, and we wanted to figure out the next big thing. There were a few initiatives, some gambles. Reorgs didn't always match and some initiatives got starved, others over-fed.
Let me take the opportunity to say that we did have a lot of freedom in engineering to build and experiment, which I always loved. This was a strength of the company. Personally, I got to figure out and build Unity in our Workstation product (it let you pop windws out of a VM into the host -- SUPER challenging), the whole remote VM infrastructure for Workstation (took 3 years with a major rewrite), WSX (early-days HTML5 client for accessing VMs using just a native browser and a network connection), amongst others.
But the world changed and we didn't really nail this. Case in point, The Cloud. (And later Docker.)
In early Cloud days, we were trying to figure out what that all this really should look like, how we fit in. We had things in the works that didn't get released or got restarted, we had some really useful bits that got spun out. What we should have built was more obvious in retrospect, but not so much at the time.
I think we had a lot of really good people in the management chain, and overall people were trying to do the right things there. But we did have a few high-impact bone-headed decisions (some short-term cost savings at the expense of longer-term strategy in parts of some departments) and some people who shouldn't have had the responsibilities they did (in my opinion). Some of these decisions may have made sense at those levels at the time due to factors they were dealing with that I don't know about, but these did damage.
Bear in mind, it was a big company in a quickly-evolving industry, and it's not always easy to get things right. I would NOT say "corporate greed" or "screwing over customers" or anything like that. Not while I was there. But missteps and hard questions to answer about the future.
All that said, I enjoyed working there. I left to work on Review Board (https://www.reviewboard.org) full time in 2013, and then my old team disbanded in 2016, but much of the team still gets dinner every month, 10 years later. Still sees movies, still hangs out in a Discord. I wouldn't trade working there for anything.
Re: Leaving VMware just got harder after Broadcom pulled VDDK downloads
#157Re: Leaving VMware just got harder after Broadcom pulled VDDK downloads
#158Re: Leaving VMware just got harder after Broadcom pulled VDDK downloads
#159Earlier quoted context omitted.
SCVMM may technically have the thing you're missing from vCenter... but it's no vCenter. It is a grotesque, MMC plug-in-looking application where nothing quite makes sense to someone accustomed to vCenter or Hyper-V / FCM. Maybe if you're into Azure and slap another layer on top w/ Arc you'll have something that... is less icky but still isn't vCenter. But, hey, The Reg says that VMware is now claiming that vSphere S…
Microsoft has done a lot of shitty things, including letting Windows Server and SCVMM languish to push/force their customers to Azure. I've been to a few Ignites and the feeling I got was Server development was starving for resources while the things we've asked for were being deployed to Azure only. I don't think SCVMM is as bad as you portrait. I've used both SCVMM and vCenter. vCenter is so far ahead. And SCVMM wa…
If you think about it, all hyperscalers are hardly any different from old timesharing OSes, the only big difference is the way we get to log into the platform.
Re: Leaving VMware just got harder after Broadcom pulled VDDK downloads
#160Earlier quoted context omitted.
I remember reading some obscure customer doco that "The old fax server is running on the virtual host" And I was like... what virtual host? What I found was Server 2003 running on VMWare Workstation, running on a Windows 7 Dell PC sitting at the bottom of a rack. A lot of people think VMWare Workstation is the pinnacle product of the company and I have NFI how this came to be.
I think you're conflating different requirements/usecases. Sure, a type-1 hypervisor like vSphere is technically better since there's no host OS creating unmanageable contention and if you have guests with higher performance requirements then yeah it's settling for something half-assed. But in reality, we have some similar shit to a "fax server" that has manually set up weird manufacturer printer settings (local admi…
I disagree. protoculture's core statement seems to be:
A lot of people think VMWare Workstation is the pinnacle product of the company and I have NFI how this came to be.
A company's pinnacle product can be completely useless to me, but that doesn't change the fact that the products of theirs that I do use are very simple and unimpressive when compared to it. [0]Having said that, I expect that a lot of people think Vmware Workstation is Vmware's pinnacle product because they've never heard of vSphere, ESXi, or anything else the company has made. "People have no knowledge of like 95% of what most companies do." is always a solid first guess when trying to work out confusion like protoculture's.
[0] Please spare me the "But how can it be a pinnacle product if it's not useful to you?" retort and ones like it. I've deliberately made a distinction between a product's usefulness to me personally and the sophistication of that product.