We recently had a meeting with our new (as in 4th in a year) rep. They let us know ROBO licensing is moving away from the VM Pack method it is now to per socket licensing. Minimum of 16 core per socket purchase, and you can’t stretch a license across multiple cores.

We about blew a gasket when we were told this. It is going to make our ROBO license jump from about $2K up to $30K PER YEAR. We were told changes to Ent+ are coming too, but details were not known. We are in the process of looking at how moving to another option would look like. Either Hyper-V or Nutanix AHV.

I guess we can see how Broadcom is making their money back. By screwing over their customers.

  • @ostsjoe
    link
    English
    81 year ago

    We moved to promox, and never looking back. Thanks Broadcom.

  • @[email protected]
    link
    fedilink
    English
    11 year ago

    Definitely look into Nutanix AHV, but I’d definitely recommend 3 node over two node ROBO. Personally I like NX hardware but it’s all fine.

    The only downside I’ve encountered is VM affinity lacks compared to VMware.

  • KingSlareXIV
    link
    fedilink
    English
    11 year ago

    The is pretty much Broadcom’s MO with purchases like this. Jack up prices to get rid of small customers, milk the huge customers for all they can, don’t spend money on further development.

    We saw the writing on the wall with the purchase, got the ball rolling and now are almost done expunging all VMware from our environment. Just in time it seems.

      • KingSlareXIV
        link
        fedilink
        English
        11 year ago

        It’s a multi stage transition, and we are nearing the end of phase 1, rebuild in AWS using equivalent EC2 instances. This is not cheap by any means, but it gets us out of VMware, and also gets us away from our abysmal capacity management problems. Being able to keep up with business growth on-demand is worth the extra cost over the medium term.

        Phase 2 is rearchitecting and consolidating our major overlapping LOB applications into fewer, more cloud-native designs. This should reap cost savings eventually.

        • @TurnItOff_OnAgainOP
          link
          English
          21 year ago

          Yeah, we’ll never be able to afford a full lift and shift to the cloud. Too much OpEx required.

  • @rehabdoll
    link
    English
    -131 year ago

    It’s like they don’t want anyone to use the product. And just bleed the customers that can’t quickly migrate to something else.

    Insane