User:Qthrul/sandbox
Regarding speedy deletions
- This Vblock page should not be speedy deleted as an unambiguous copyright infringement, because I am part of the Office of the CTO at VCE (company) and the format of this article is to properly capture the historical significance of converged infrastructure during the years of 2009 and forward. This content has been verified against the Duplication Detector. Any similarities to third party websites are those not affiliated with VCE (company). The language used in this article should be considered neutral, unbiased, contains factual references, and any unambiguous copyright materials concerns are not present. Further, you can clearly see my disclosures of potential conflicts of interest on my info page that clearly indicate who I am and my employer. In addition the Creative Commons included image is one that I personally created. If you have any questions or wish to engage in a dialog please update my talk page. Kind regards, Qthrul (talk) 02:35, 18 August 2012 (UTC)
Vblock™ Systems are a manufactured product of VCE (company). Vblock Systems are deterministic in terms of power, weight, cooling, and geometry for data center planning purposes[1].
Vblock currently comes in two series and each series has models. All are based on EMC storage, Cisco UCS blades and switches, EMC Ionix UIM/P for provisioning and VMware vSphere for virtualization in addition to Cisco Nexus 1000V and EMC PowerPath/VE as replacements for VMware native vDS and MPIO respectively[2][3].
History and Models
Vblock naming conventions have undergone branding changes since their inception[4]. In 2009, the term Vblock Infrastructure Packages was referenced in the initial announcements from then Acadia, the Virtual Computing Environment coalition, as well as their primary investors. In late 2010 and continuing through 2011, the term Packages was replaced with Platforms. By mid 2012, the term, Infrastructure Platforms was replaced with Systems in wider circulation to arrive at, simply, Vblock Systems[5]. Meanwhile, during this window of time there have been refinements to the constituent elements and technology utilized in the Vblock that coincide with enhancements and upgrades to the product lines from Cisco, EMC, and VMware.[6]
Infrastructure Packages
Originally based upon a reference architecture, these were made possible by taking a reference architecture combined with a sizable term physical and logical build initially at a customer data center or colocation data center and later within a pre-manufacturing environment for shipment to a customer data center or colocation data center. Options and choices were more limited during the time these were marketed and sold. The 0, 1, 1U, and 2 are now end of sale with the introduction of the new series and models naming conventions.
The 0 (zero)
This was the original development and testing file personality model of Vblock architected on EMC NS-120 storage.
The 1 (one)
This was the original mid-range block personality model of Vblock architected on EMC CX4-480 storage.
The 1U (one U)
This was the original mid-range file and block (unified) personality model of Vblock architected on EMC NS-960 storage.
The 2 (two)
This was the original high end block personality model of Vblock architected on EMC VMAX storage.
Series
300
This series offers a larger number of choices based on the performance envelope required as well as the capacity desired. In contrast to the 0, 1, 1U these are VCE manufactured products that are produced in global manufacturing centers that are then deployed and installed within a customer data center or colocation data center by a VCE partner and/or VCE professional services team.
EX
This model utilizes EMC VNX 5300 storage arrays.
FX
This model utilizes EMC VNX 5500 storage arrays.
GX
This model utilizes EMC VNX 5700 storage arrays.
HX
This model utilizes EMC VNX 7500 storage arrays.
700
This series offers an even larger number of options for functionality, performance, and capacity. Also, in contrast to the 2 these are VCE manufactured products that are produced in global manufacturing centers that are then deployed and installed within a customer data center or colocation data center by a VCE partner and/or VCE professional services team.
LX
This model utilizes EMC VMAXe storage arrays.
MX
This model utilizes EMC VMAX storage arrays.
Customers
It is believed that Vblock Systems are widely deployed globally in both enterprise and service provider environments but no confirmed numbers are announced publicly by VCE or its investors[7]. Previous deployments of what were called Vblock using now dated reference architectures as opposed to post late 2010 manufactured Vblock Systems are not considered to be Vblock Systems [8]. Anecdotally, institutions and companies using Vblock Systems have been involved in published testimonials[9][10].
See also
References
- ^ http://www.theregister.co.uk/2010/12/21/vce_acadia_ramp/
- ^ http://vmackem.co.uk/?p=553
- ^ http://www.lightreading.com/video.asp?doc_id=216883
- ^ http://siliconangle.com/blog/2011/08/17/is-vce-a-flailing-startup-a-study-of-snark-in-new-media/
- ^ http://vdi-virtual-desktop-infrastructure.tmcnet.com/articles/295096-vce-fastpath-platform-simplifies-vdi-vblock-systems.htm
- ^ http://www.telegram.com/article/20111211/NEWS/112119983/1002/business
- ^ http://www.crn.com/news/networking/240004002/vce-taps-cisco-veteran-as-new-ceo.htm
- ^ http://www.bythebell.com/2010/10/customers-embracing-vblocks-but-vce-sales-harmony-a-work-in-progress.html
- ^ http://www.ventech.com/2012/07/vblock-video-success-story-ms-community-college-board/
- ^ http://campustechnology.com/articles/2011/09/15/taking-college-it-out-of-the-hardware-business.aspx