Talk:VMware vSphere

This is the talk page for discussing improvements to the VMware vSphere article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Merge with VMware Infrastructure

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

Closing merge discussion. Consensus was not reached regarding merging after over three years. WTF? (talk) 18:17, 25 January 2013 (UTC)[reply]

Should this article be merged with VMware Infrastructure? This is an encyclopedia, not a corporate branding exercise. Are they similar products? Is VMware vSphere 4 still a suite with similar components to VMware Infrastructure 3? If we merged them, we could even have a history section and start getting out of the blatant product announcement mode. UncleDouggie (talk) 12:47, 29 August 2009 (UTC)[reply]

I strongly disagree with the proposed MERGE,

VMware decided to dedicate an entirely new product line that exclusively targets cloud computing and offers cloud-optimized virtualization only on that platform (vSphere); whereas VMware Infrastructure is the parent and source of that product line, VMware no longer intends to succeed it with cloud-enabled versions

(as vSphere originally should have, it was supposed to be VMware Infrastructure version 4 (VI 4) to succeed VI 3.5)

Are they similar products?
..If we merged them, we could even have a history section and start getting out of the blatant product announcement mode.
— User:UncleDouggie

@UncleDouggie, what is sure is that they are NOT THE SAME product, although they share the same roots in the original VMware Infrastructure version 3.5, the cloud computing components have been spun-off to a new development model (VI 4.x, Update 1 last updated November 19, 2009) in parallel to 3.5 Update 4 / March 30, 2009, which has NOT been retired by VMware and retains traditional virtualization models

if you insist on MERGE UncleDouggie, i suggest reversing the direction of merge, because vSphere is a lesser known derivative product from VI

and ALSO, VMware_vSphere is the younger article with less detail, like a stub:

the VMware vSphere article started only last 21 April 2009 - 21:55
while VMware Infrastructure has been around 22 September 2007 - 01:45, and so far more developed encyclopedic article

—-— .:Seth_Nimbosa:. (talk • contribs) 07:27, 4 December 2009 (UTC)[reply]

comments welcome These should be merged as the new product encompasses added technology which are added pieces to the older product that was focusing on cloud computing (or whatever is the newest name) In order to add proper storage handling this had to be changed. Sort of like pulsing bits to a serial port until the OS supports enough protocol functionality. — Preceding unsigned comment added by TechTalkToll (talk • contribs) 16:54, 10 March 2011 (UTC)[reply]

Agree with proposed merge. The vSphere article contains little to no real info and reads like advertising copy. The VI article contains slightly more info. VI is now obsolete and replaced so the merge should be into the article about the newer product. Liam Proven (talk) 17:43, 17 August 2011 (UTC)[reply]

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Dont tell me what to do — Preceding unsigned comment added by 109.202.138.141 (talk) 12:37, 29 August 2016 (UTC)[reply]