3 Replies Latest reply on Oct 18, 2018 9:35 AM by daphnissov

    vCenter 6.7 Update 1 got a unique API Version ... Why?

    IamTHEvilONE Champion

      I think the subject says it all.

       

      For the first time ever, that I can recall, vCenter had an update release that has a unique API version ... 6.7.1.

       

      Over all the updates of 5.1 to 6.5 ... doing an update 1/2/3 didn't change the API version from 6.5.1 to 6.5.2.  And I've been using VMware since vCenter 2.5 ... so this is pretty new to me.

       

      I guess I'm just curious to know why this was done?

        • 1. Re: vCenter 6.7 Update 1 got a unique API Version ... Why?
          msripada Expert
          vExpert

          Probably there are lot of new features introduced in the 6.7 U1 which needs those new API calls.. As you are aware that now VMware has lot of partners integrating with multiple products which might require new api's, rather than delaying they introduced the same in new release with update 1.. It is most awaited updated as far as i can say..

           

          - MS

          • 2. Re: vCenter 6.7 Update 1 got a unique API Version ... Why?
            IamTHEvilONE Champion

            I know this happens with vCloud Director, but at least there was guidance provided for that since there are multiple strains of it.

             

            For vCenter, this is a departure.

             

            It's also not in the release notes.  VMware vCenter Server 6.7 Update 1 Release Notes

             

            If this was going to happen, announce it at 6.7.0 and at least give partners time to prepare.

             

            It's also entirely possible I can't find this sort of guidance in a public forum.

             

            But when you have multiple vendors complaining about this (see Veeam and other backup vendors) ... it makes me thing this wasn't planned very well.

            • 3. Re: vCenter 6.7 Update 1 got a unique API Version ... Why?
              daphnissov Guru
              vExpertCommunity Warriors

              Totally agree. The real problem here is that VMware isn't providing partners the pre-release GA code. It's just dumped in their lap as a "surprise" moment same as it is with all customers. This is especially egregious for the data protection partners considering VMware has bowed out of the data protection business altogether after their abomination VDP product (an Avamar pig in lipstick)  failed miserably. By them not working with those DP vendors all the way from beta through GA, these types of breaking changes cripple more and more customers until the vendor has a chance to catch up.