{"id":4637,"date":"2014-08-25T15:00:27","date_gmt":"2014-08-25T14:00:27","guid":{"rendered":"http:\/\/vmdamentals.com\/?p=4637"},"modified":"2014-08-25T15:00:27","modified_gmt":"2014-08-25T14:00:27","slug":"vmware-vrealize-really","status":"publish","type":"post","link":"https:\/\/www.vmdamentals.com\/?p=4637","title":{"rendered":"VMware\u00ae vRealize\u2122…. Really??"},"content":{"rendered":"


<\/p>\n

Oh no. VMware just announced a huge change in names. I know “vCAC” wasn’t the best as in many languages CAC means… well you look it up. But vRealize… Really???<\/em>\n<\/p><\/blockquote>\n



\nThe new names convention: Everything vRealize\u2122<\/strong><\/p>\n

Someone at VMware probably thought this was pretty neat. “Let’s change everything to vRealize\u2122, yeah!!”. I’m not a fan. Well, let’s look at some old and new names:
\n

\n

<\/p>\n\n\n\n\n\n\n
ORIGINAL NAME<\/th>\nNEW NAME<\/th>\n<\/tr>\n
VMware vCenter Operations Management Suite<\/td>\nVMware vRealize\u2122 Operations\u2122<\/td>\n<\/tr>\n
VMware vCenter Operations Manager<\/td>\nVMware vRealize\u2122 Operations Manager\u2122<\/td>\n<\/tr>\n
VMware vCloud Automation Center<\/td>\nVMware vRealize\u2122 Automation\u2122<\/td>\n<\/tr>\n
VMware IT Business Management Suite<\/td>\nVMware vRealize\u2122 Business\u2122<\/td>\n<\/tr>\n<\/table>\n

Some Examples of the new VMware naming convention<\/em>
\n<\/center>
\nMaybe it is me. I just don’t like the “vRealize” part. Looking through Google (on August 21st 2014), I found some nice pre-VMworld-leak too:
\n

\n

\"If<\/a>

If you know the name… You could find this draft post that was withdrawn again. Google knows ALL…!<\/p><\/div><\/p>\n

However, when I clicked that link, it seemed VMware did know what to respond:<\/p>\n

\"VMware<\/a>

VMware DID know the right response: Yes it is somewhat embarrassing.<\/p><\/div>
\n

\nNow to mix this with AIR<\/strong><\/p>\n

In addition to the vRealize\u2122 stuff, we also have “Air” that saw the light of day a few days ago to basically rename everything that is “As A Service”. This adds to the naming convention. Now at least I know why I should make my slide decks 16:9 widescreen. I’ll just give some examples and you can guess the original products:
\n
<\/p>\n

    \n
  • VMware vRealize\u2122 Air\u2122 Automation<\/li>\n
  • VMware vRealize\u2122 Air\u2122 Business Enterprise<\/li>\n
  • VMware vCloud\u00ae Air\u2122 Virtual Private Cloud OnDemand<\/li>\n
  • VMware vRealize\u2122 Automation Advanced Public Cloud Extension\u2122<\/li>\n
  • VMware vCloud\u00ae Air\u2122 Virtual Private Cloud<\/li>\n<\/ul>\n

    Yikes.
    \n

    \nMy 2 cents<\/strong><\/p>\n

    Put simply, I don’t like the new naming convention. The words are in my opinion just not right, pronunciation is not fluent.<\/p>\n

    It looks like VMware is trying to get rid of all the abbreviations. While that is a good thing in itself, these long names will definitely cause them to be abbreviated once more in the field. Let’s look at how this will go down. If vCHS == \u201cvee-cheese\u201d, does vCloud Air become \u201cvee-Care\u201d?<\/p>\n

    One upshot of this, people will stop to call v-c-a-c \u201cvee-cac\u201d and \u201cvee-cake\u201d. But I’m guessing now the new acronym vRA will be pronounced \u201cvee-rah\u201d. Sounds like one of the bad guys in a comic strip or the geeky version of an American Marine.
    \n

    \n

    And just now I just realized I need to re-certify as a \u201cVMware vRealize Certified Professional\u201d. Bummer.<\/font><\/strong><\/center><\/p>\n","protected":false},"excerpt":{"rendered":"

    Oh no. VMware just announced a huge change in names. I know “vCAC” wasn’t the best as in many languages CAC means… well you look it up. But vRealize… Really??? The new names convention: Everything vRealize\u2122 Someone at VMware probably thought this was pretty neat. “Let’s change everything to vRealize\u2122, yeah!!”. I’m not a fan. […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,6],"tags":[602,603,604,601],"class_list":["post-4637","post","type-post","status-publish","format-standard","hentry","category-vmware","category-vmware-news","tag-air","tag-vmware-air","tag-vmware-vcloud-air","tag-vrealize"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts\/4637","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4637"}],"version-history":[{"count":43,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts\/4637\/revisions"}],"predecessor-version":[{"id":4727,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts\/4637\/revisions\/4727"}],"wp:attachment":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4637"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4637"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4637"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}