• SGG@lemmy.world
    cake
    link
    fedilink
    English
    arrow-up
    69
    ·
    6 months ago

    It’s simple. Either you are one of the few enterprise customers they want to keep (of which there are only a handful), or you need to have started a transition away from VMware the moment the purchase was announced.

    Which completely sucks for the industry.

    • bluGill@kbin.social
      link
      fedilink
      arrow-up
      9
      ·
      6 months ago

      Who are the customers they want? I know of companies in the fortune 100 moving away. They don’t want me to name then so I won’t.

        • test113@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          6 months ago

          I mean, if I were an investor looking at this, I would also get excited about making this change - much less risk, less cost, less customer support, etc., all for basically the same output in revenue. In other words, if I cut the small business (6% of value but over 100k accounts to handle) out of the model, I can make more money because the cost reduction is higher than the loss of revenue. And in the long run, when “big game customers” jump ship, I just downsize some more. I also don’t need to invest but can be sure it will generate a certain amount of revenue, as long as I do not squeeze the relevant customer groups too hard. This strategy is very feasible and relatively risk-free. I am not a fan of it, but I think a lot of software companies will go this way after they establish themselves in a market.

  • linearchaos@lemmy.world
    link
    fedilink
    English
    arrow-up
    29
    ·
    edit-2
    6 months ago

    DYAM I dodged a bullet. My VMWare renewal came due in December but we pulled the rip cord and went to Proxmox because the renewal was more than the price of the VMHost machine and the licenses for all the VMs running on it.

    • flatpandisk@lemm.ee
      link
      fedilink
      English
      arrow-up
      11
      ·
      6 months ago

      We did the same thing. Been VMWare customer for over 12yr and slowly migrating to Proxmox. So far pretty happy with it.

    • CurbsTickle@lemmy.world
      cake
      link
      fedilink
      English
      arrow-up
      6
      ·
      6 months ago

      We had VMware, new office I told them we are shifting to Proxmox. The licensing just wasn’t worth it compared, especially with the features we use as a small enterprise client.

      This just confirms the decision was the right one for us too.

      I have to wonder how many are out there doing the same and now getting a support license, hopefully a good amount to give the team some revenue to keep things moving well on their end.

      • linearchaos@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        6 months ago

        At my last place we had a decked out vmware. SAN, HA, hot migration. When I came to he new place I brought the mindset with me, but you have to need it to make it worth it.

        Yeah that support license is solid, especially since most of us don’t actually call them with any questions :)

        Sooner or later they’ll probably make it a pay / community duality like everything else, but for the moment, it’s the absolute best

    • Saik0@lemmy.saik0.com
      link
      fedilink
      English
      arrow-up
      4
      ·
      6 months ago

      Proxmox is awesome. Debian underneath means you can do whatever you want. And the tools in proxmox are pretty damn good especially with automation scripts.

  • Bizarroland@kbin.social
    link
    fedilink
    arrow-up
    18
    ·
    6 months ago

    I’ve already dumped my esxi servers and am using proxmox and hyper-vm instead.

    That’s one less customer for them.

  • Shadow@lemmy.ca
    link
    fedilink
    English
    arrow-up
    16
    ·
    6 months ago

    We’re trialing migrating windows workload to hyperv. We pay for windows licenses anyways so hyperv is free, and it’s come a long way. Veeam supports it, so keeps the change minimal.

    • ikidd@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      6 months ago

      Well, it could only get better because when I tried to deploy it widely about a decade ago it was an utter steaming pile of shit. I went and got my VCP instead.

      • WordBox@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 months ago

        2008 was pretty shit. 2012 was pretty good. And now 2016+ has a lot more features.

        The best and worst part about it is that it’s Windows.

  • AutoTL;DR@lemmings.worldB
    link
    fedilink
    English
    arrow-up
    6
    ·
    6 months ago

    This is the best summary I could come up with:


    It’s unclear who or how many current partners will be able to sell VMware-related offerings after April 2024, leaving potential for tens of thousands of businesses to be disrupted.

    But today’s news reportedly reveals a final closure date for the cloud services provider partner program, which debuted in 2019.

    The Register noted “unconfirmed fears” that only 10 percent of the biggest VMware cloud service providers would be invited into Broadcom’s partner program.

    VMware has about 4,000 service provider partners, according to a January 4 report from CRN, which claimed that only 10–15 percent of them are expected to get invites into the Broadcom program, citing an unnamed source.

    By altering how VMware tech is purchased, long-term customers may be forced to change critical infrastructure or work with a new, potentially much bigger, provider than they’re used to.

    There’s a deeper concern that Broadcom’s VMware won’t prioritize smaller customers during this evolution.


    The original article contains 544 words, the summary contains 151 words. Saved 72%. I’m a bot and I’m open source!

  • deafboy@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    6 months ago

    Just finishing the migration from cloudstack to vcloud director.

    I’m not angry, just disapointed.