But all of these moves have been with the goals of innovating faster
Fail.
meeting our customers’ needs more effectively,
Fail.
and making it easier to do business with us.
Fail.
If the goal is milking your customers for more money then it all makes sense. At least until they start migrating away from VMware and your new client stream completely dries up.
Yes, the only thing that Broadcom gives a shit about here:
Broadcom expects VMware revenue to grow double-digits quarter over quarter for the rest of the fiscal year.
The ‘ol late-stage capitalism adage “growth above all else”
“Short-term growth above all else, then lay everyone off and find the next business to buy out and ruin”
Executives care only about their bonuses, and the best way to boost them is to milk companies on the short term even if it ruins them on the long term. There is no incentive to care about long term.
Investors reward this behavior. The system is designed to destroy good things.
Translation: We are gonna gouge the ever living fuck out of every single customer.
I am so fuckdamn tired of having products taken away ‘to meet customers needs more effectively’.
Companies that make shittastic public statements like this should be subject to legal punishment.
And illegal punishment!
At least until they start migrating away from VMware and your new client stream completely dries up.
This is a feature. They take a product that you can’t easily move off of, like VMware or Symantec. They jack up the prices. A few people leave, but some people struggle to leave and pay lots of money. Demand drops, they cut most of the staff and put the product on life support, and eventually they kill it. By that time they’ve bought another company to do the same.
They’re basically just milking old cows to death.
Totally unrelated, but that’s actually what we’re doing with cows. Killing them of at age 3 bc they don’t give enough milk anymore
It’s what we always did with cows. To have a dairy cow you need to repeatedly get it pregnant. Why keep feeding an older less productive cow that has already calved 4 or 5 times when you’ve already got yourself a few new heifers.
fyi most dairy cows are kept beyond the age of 3. You can see on the World Dairy Expo YouTube channel that there are cows producing up to the age of 6.
Heifers reach puberty at about 12 months old, but some delay until up to 20 months old. After breeding they gestate for 283 days (almost 9 1/2 months), give birth to their calf and give milk for about 10 months. “Culling” a cow at the age of three would mean only getting 2 full lactation cycles of milk from them, which isn’t super economical.
You’re not too far off the mark, though: once any individual animal becomes less profitable than a new one could be, they get culled.
Yeah, im not that big on the details, since I don’t support those industries at all.
Said it before, they’re dumping low value customers for high value customers. This can be a legit strategy!
But not in this case. As you said, they’re going to milk the cow dead. We wouldn’t touch VMware with a ten-foot frog. Leaning into Proxmox ATM, working great so far.
A lot of people talk about Proxmox but I wouldn’t be surprised if redhat open shift decided to throw its hat into the ring as an HP or Dell partner.
While open shift can somewhat accommodate VM workloads, it feels like an afterthought. Really the goal is to charge how your applications are run.
However, VMware presides over staunchly “old fashioned” ships that think in terms of “machines”. So ProxMox is a bit more similar.
RedHat did have ovirt which would have been a closer platform, but they ditched that in favor of openstack, which was also VM centered but “cloudy”, which also isn’t the target model of on premise virtualization (openstack had other problems too), and now it’s openshift, which is largely a “kubernetes is a buzz word, let’s go, also as an afterthought some VM hosting to give some semblance of continuity for users we yanked through RHEV, openstack, and for now openshift”
It might play a role, but ProxMox may be better situated to be like for like. Microsoft is of course pushing their azure stack for those wiling to get tied up into azure a bit. I suspect openshift will continue to mainly focus on cloud hosted VMs rather than retool they’re go to market to better capture those abandoning VMware. After all, since the story is “reduce costs”, that’s not an appealing scenario to red hat/IBM, since it inherently puts an obvious upper bound on revenue and the customers will be those that demonstrated they are the most ready to migrate when unhappy.
I think this is very interesting. I’ve been investigating the solutions and found that a lot of other platforms like scale hci, virtuozzo, and oracle VM are all based on the oVirt/Openstack platforms but have been customized.
Openshift and Suse Harvester both have a very similar Kubernetes first approach which I think is interesting. Harvester seems to rely on KubeVirt to deploy “legacy workloads” (probably windows).
The reason I mention openshift though is because I’ve been paying attention to Wendell, level1techs, and the level1 forums and Wendell keeps hinting that Redhat/IBM openshift + intel is being used as a VDI platform featuring Intel flexGPUs for a secret customer (I wouldn’t be surprised if it was a government facility like the national laboratory near Knoxville). I’m just trying to envision how that deployment looks.
I find it peculiar that everybody in this discussion is ignoring Hashicorp’s stuff??
https://en.wikipedia.org/wiki/HashiCorp
I glanced at Proxmox vs Hashicorp’s stuff, after seeing some discussions on here about 'em, & Hashicorp’s stuff is oriented to clarity & simplicity.
Sorta Japanese take on it.
To me clarity is worth a significant amount of value.
Anyways, I’m just noting this, for anyone who’s actually considering such things: I’m only a nobody who has avoided geeking for some years.
( :
I never thought of hashicorps products as a replacement for VMware but more of an add on to it.
In his blog post, Tan defended the subscription-only licensing model, calling it “the industry standard.”
“Industry standard” my ass.
If Adobe hadn’t started the trend by lusting after Blizzard’s subscription model and ultimately emulating it, we’d all be a lot better off.
Not to mention our wallets being eternally thankful.
It is the industry standard now, it never had to be but they all got greedy and Adobe kickstarted the slide
Free and open source software is the industry standard
My job estimated our VMware cost will be 10 times more expensive. We’re moving to the cloud as soon as possible.
A panicky move to the cloud might be extremely expensive too. Especially if you don’t have cloud ready applications (old on prem apps, full fledged VMs, etc. )
It’s not panic. We already have direct connects to AWS and Azure. It’s something we’ve been working on for five years now.
That’s interesting, because hosting anything in the cloud is usually way more expensive than on prem. We just pulled a large number of our systems back out of gcp because of it.
Well that was my point, moving to the cloud requires drastic changes in the way your infra works. You cannot have full fledged VMs running at 10% of capacity 95% of the time like you do on prem. You need to be able to scale up and down on a whim with containers/micro services/whatever you call it. I’ve worked with a lot of companies that never understood that and bitterly regretted moving to the cloud.
Yup. I’ve seen companies that wanted to “get to the cloud” and didn’t want to spend any money on redeveloping their systems so it turned into a lift-and-shift which just drove their costs up.
Hey hey my company is doing exactly this right now
“Get EVERYTHING OFF PREM. SEND ALL OF IT TO GCP NOW”
My company just came to their senses on this.
We demonstrated one product worked well in the cloud by completely re-architecting it. It was a two year project. However then management was all gung ho, and set an extremely aggressive deadline, meaning lift and shift was the only possibility. However just before the new year, management finally realized just how expensive it was going to be, and changed their mind.
The thing is, our products are internet services, so we have to maintain data centers and networking at many locations around the world, and need to have the people to support that. However datacenters are not our core business and there’s a good argument that we should get out of it. Just not that way
O absolutely, but most of these companies don’t want to spend money to actually get to that point since they’re going to have to redev their applications and design, so they just tell the engineers to put everything one to one in the cloud.
Haha, so you move from one bad decision to another? Being stuck at a lousy cloud company? Oh my!
We sell hardware built for and bundled with VMware. Customers are returning it. This isn’t a good look.
Not sure why they’d think cloud will be cheaper. If anything, costs are way more unpredictable from the research I’ve done.
Generally that is true only if you don’t know your workloads.
My workloads are open to students doing things on an LMS. Chaotic doesn’t begin to describe it. 🙃
Lol, THEY have no idea about workloads
Man I wish we could do this, but our customers won’t agree to processing their data in the cloud. We’re going to get milked so hard.
Pure damage control lingo. Anyone in the game for a while knows exactly how Broadcom operates. Theyre not hanging around while they squeeze the juice out until it becomes another SAP or Oracle. If he thinks a subscription model isn’t going to cause a mass exodus, he is a fool.
So I may be biased but what is vmwares USP? From my limited experience it was a slightly more polished GUI for creating VMs and the ability to run on older pre-virt hardware. Is the experience still objectively better than the alternatives?
If you’re running a lab or a small shop any hypervisor can likely do the job. Anything above that VMware’s overall ecosystem is the most robust and well-supported.
At this point virtualization is a legacy technology. It’s not going to disappear tomorrow but its clock is ticking the same way the clock was ticking for mainframes thirty years ago. Plenty of mainframes still out there but nobody is implementing new. Same can be said for virtualization. It’s a limited market with significantly slowed growth over where it was a decade ago.
The move to a subscription model will let them squeeze every last dollar out of the technology while they still can.
Wait what
virtualization is a legacy technology
AWS, GCP, and Azure run on virtualization. Do you think all these cloud providers are providing everyone bare metal? This doesn’t include containerization which is a subset of virtualization. Your average shop might not run virtualization directly unless of course your team touches VirtualBox or Vagrant or qemu or (probably shouldn’t) HyperV.
Either your understanding of virtualization is very lacking or you didn’t explain your point very well. I am really curious what you meant.
Yeah, virtualization is definitely not “legacy technology” 😂
Virtualization, as a commercial product pointed at businesses, is a legacy product.
Of course large providers are utilizing virtualization, containerization and an abundance of similar technologies. However, they’re not generally using VMware to do it.
I spoke in the context of OPs question.
Maybe a better term is “commodity” technology. Rather than a thing by itself where one company is much better, now it’s everywhere, mostly good enough. It’s not going anywhere but I wouldn’t run a business on it alone
I think that’s a fair point. Trying to build a new virtualization company today would have huge initial investment and a steep path to the companies that run their data centers.
Yes commodity is a much better term here. It is a mature and fairly ubiquitous technology at this point.
(probably shouldn’t) HyperV
What makes you say “probably shouldn’t”? WSL use is widespread at this point
WSL is also shit for any kind of containerization and HyperV fucks up everything else. If you’re not doing any DevOps/SRE stuff WSL 2.0 is fine provided you don’t mix the filesystems. I have been so frustrated with their claims on release for 1.0 and 2.0 that I haven’t evaluated the recent systemd release for WSL. I provision WSL for people that don’t know why they should care and Linux VMs for people that need to work with CI tooling.
In general if you use a Microsoft tool you have to use the Microsoft ecosystem. Sometimes that’s not a huge deal, eg VS Code just adds a ton of telemetry and GitHub reads all your public code. Sometimes it’s a huge deal, eg you want to do literally anything beyond Docker Desktop defaults in the container world.
At this point virtualization is legacy technology.
Man, I’d love to believe that - and please Lemmy, prove me wrong, but virtualization, especially commercial products like VMware have one huge advantage over things like kubernetes - it’s effectively plug and play and has full support available.
- Boot off this esxi iso
- Deploy this VCSA OVA
- Have vCenter auto config VSAN
- Deploy fully ha/Drs managed VMs
I would kill for a similar experience with kubes - something that I cannot for the life of me get to work in my homelab given the myriad of walkthrough in various states of accuracy.
Yeah the above is someone who can either greenfield because they work for a new shop or is deep in the kube-aid.
Most buisnesses just need your stated features. Some stand alone VMs with HA that makes them server independent and let you snapshot/back them up with ease. Slot commodity servers in a room somewhere, wander off to do more important things.
The good news is that proxmox is already there, if a bit more crunchy to deploy. It’s got integrated ceph to work as a backend for HA/VSAN, built in snapshots and a separate backup appliance that sports Veeam style features. It has a simple config language that could compete with powercli if that is a current vmware use case. Looks like it even supports VDI with Intel’s enterprise gpus, although that is early days.
Certainly any cloud kubernetes will be much quicker and simpler. To the extent you can use minikube, I’d call it about the same as a vm.
For large on-prem clusters, you may have a point. I did an eval and came to a similar conclusion, but that was about five years ago. Also the question was “Can we ask customers to do this or already have this for installing our product?”. That idea was a bit before its time
Please forgive a wildly uninformed question: What is it that VMware does today that isn’t covered by Docker?
Different OSes. Windows and Linux for example. No way to run a full fledged domain controller in a container. Just to name a example.
VDI environments is one place. Also Windows heavy environments (exchange, SharePoint, teams, DCs, etc) are probably better suited for VMs.
Storage, software defined networking, performance metrics, VDIs, endpoint security, virtualization on the desktop.
Not to mention, a lot of workloads aren’t suited to containers. The vast majority of business software isn’t containerized, and it would be wildly cost-prohibitive for me to shoehorn that square peg into the round hole of virtualization.
Uhh, docker is containers, VMware is a virtualization hypervisor?
Ultimately, in terms of what they can do, well technically you can do anything without any container or virtualization strategy, so from that angle, they are all the same.
It reallyboils down to what the humans are comfortable with, and that’s where there’s some divergence.
Sure, one could make technical arguments about one can be multi kennel, one has arguably somewhat stronger likelihood of isolation, and one has a bit more efficiency than the other, but it’s really down to human factors and familiarity.
Developers tend to like container based approach because the “image” is transparent and usually provides nice cheap options to somewhat track history and “fork” from common points with some flexibility. VMs kind of have some of that, but practically speaking it’s far more awkward.
Conversely some operators find managing container based solutions too “developery” and find comfort with virtual machines. It’s also more straightforward to just carve out a vm, hand it over, and give them the keys and let them deal with it. Then you commonly have VMs at one layer, and at least some of your tenants self managing some container management layer on top of their slice of the world.
While there is some overlap, general comparison of VMware vs Docker is a bit apples and oranges.
This is the best summary I could come up with:
In a blog post Thursday, Tan noted that Broadcom spent 18 months evaluating and buying VMware.
But all of these moves have been with the goals of innovating faster, meeting our customers’ needs more effectively, and making it easier to do business with us.
Tan believes that the changes will ultimately “provide greater profitability and improved market opportunities” for channel partners.
Additionally, Broadcom killing VMware perpetual licensing has reportedly upended financials for numerous businesses.
In a March “User Group Town Hall,” attendees complained about “price rises of 500 and 600 percent,” The Register reported.
In his blog post, Tan defended the subscription-only licensing model, calling it “the industry standard.”
The original article contains 499 words, the summary contains 109 words. Saved 78%. I’m a bot and I’m open source!
