Open Compute Project: Difference between revisions

Content deleted Content added
more details and sources
m fix botches
Line 15:
The effort came out of a redesign of Facebook's data center in [[Prineville, Oregon]].<ref>{{Cite web |url= http://www.facebook.com/notes/facebook-engineering/building-efficient-data-centers-with-the-open-compute-project/10150144039563920 |title= Building Efficient Data Centers with the Open Compute Project |author= Jonathan Heiliger |date= April 7, 2011 |work= Facebook Engineering's notes |accessdate= July 9, 2013 }}</ref>
The leader of the effort is Frank Frankovsky. After two years, it was admitted that "the new design is still a long way from live data centers."<ref>{{Cite news |title= Facebook Shatters the Computer Server Into Tiny Pieces |date= January 16, 2013 |author= Cade Metz |work= Wired |url= http://www.wired.com/wiredenterprise/2013/01/facebook-server-pieces/ |accessdate= July 9, 2013 }}</ref>
However, some aspects published were used in the Prineville center to improve the energy efficiency, as measured by the [[power usage effectiveness]] index defined by [[The Green Grid]].<ref name="Stanford">{{Cite web |title= Facebook's Open Compute Project |work= Stanford EE Computer Systems Colloquium |date= February 15, 2012 |url= http://www.stanford.edu/class/ee380/Abstracts/120215.html |author= Amir Michael |publisher= [[Stanford University]]}} ([http://ee380.stanford.edu/cgi-bin/videologger.php?target=120215-ee380-300.asx video archive])</ref>
 
Components include:
Line 21:
*Server compute nodes include one for [[Intel]] processors and one for [[AMD]] processors.
 
*Open Vault storage building blocks offer high disk densities, with 30 drives in a 2U Open Rack chassis designed for easy [[disk drive]] replacement. The 3.5 inch disks are stored in two drawers, five across and three deep in each drawer, with connections via [[serial attached SCSI]].<ref>{{Cite web |title= Open Vault Storage Hardware V0.7 OR-draco-bueana-0.7 |author= Mike Yan and Jon Ehlen |date= January 16, 2013 |url= http://www.opencompute.org/wp/wp-content/uploads/2013/01/Open_Compute_Project_Open_Vault_Storage_Specification_v0.7.pdf |accessdate= July 9, 2013 }}</ref> Another design concept was contributed by Hyve Solutions, a division of [[Synnex]] in 2012.<ref>{{Cite web |title= Hyve Solutions Contributes Storage Design Concept to OCP Community |work= News release |date= January 17, 2013 |url= http://ir.synnex.com/releasedetail.cfm?ReleaseID=733922 |accessdate= July 9, 2013 }}</ref> <ref>{{Cite web |title= Torpedo Design Concept Storage Server for Open Rack Hardware v0.3 ST-draco-chimera-0.3 |author= Conor Malone |date= January 15, 2012 |url= http://www.opencompute.org/wp/wp-content/uploads/2013/01/Open_Compute_Project_Storage_Server_for_Open_Rack_Specification_v0.3.pdf |accessdate= July 9, 2013 }}</ref>
Another design concept was contributed by Hyve Solutions, a division of [[Synnex]] in 2012.<ref>{{Cite web |title= Hyve Solutions Contributes Storage Design Concept to OCP Community |work= News release |date= January 17, 2013 |url= http://ir.synnex.com/releasedetail.cfm?ReleaseID=733922 |accessdate= July 9, 2013 }}</ref> <ref>{{Cite web |title= Torpedo Design Concept Storage Server for Open Rack Hardware v0.3 ST-draco-chimera-0.3 |author= Conor Malone |date= January 15, 2012 |url= http://www.opencompute.org/wp/wp-content/uploads/2013/01/Open_Compute_Project_Storage_Server_for_Open_Rack_Specification_v0.3.pdf |accessdate= July 9, 2013 }}</ref>
 
* Mechanical mounting system: Open racks have the same outside width (600 mm) and depth as standard [[19-inch rack]]s, but are designed to mount wider chassis with a 537mm width (about 21 inches). This allows more equipment to fit in the same volume and improves air flow. Compute chassis sizes are defined in multiples of an OpenU, which is 48mm, slightly larger than the typical [[rack unit]].
 
*Data center designs for energy efficiency, include 277 VAC power distribution that eliminates one transformer stage in typical data centers. A single voltage (12.5 VDC) power supply designed to work with 277 VAC input and 48 VDC battery backup.<ref name="Stanford" />
 
*On May 8, 2013, an effort to define an open [[network switch]] was announced.<ref>{{Cite web |title= Up next for the Open Compute Project: The Network |date= May 8, 2013 |author= Jay Hauser for Frank Frankovsky |work= Open Compute blog |url= http://www.opencompute.org/2013/05/08/up-next-for-the-open-compute-project-the-network/ |accessdate= July 9, 2013 }}</ref> The plan was to allow Facebook to load its own [[operating system]] software onto the switch. Press reports predicted that more expensive and higher-performance switches would continue to be popular, while less expensive products treated more like a [[commodity]] (using the [[buzzword]] "top-of-rack") might adopt the proposal.<ref>{{Cite news |title= Can Open Compute change network switching? |author= David Chernicoff |work= ZDNet |date= May 9, 2013 |url= http://www.zdnet.com/can-open-compute-change-network-switching-7000015141/ |accessdate= July 9, 2013 }}</ref>
A similar project for a custom switch for [[Google]] had been rumored, and evolved into the [[OpenFlow]] protocol.<ref>{{Cite news |title= Facebook Rattles Networking World With ‘Open Source’ Gear |date= May 8, 2013 |author= Cade Metz |work= Wired |url= http://www.wired.com/wiredenterprise/2013/05/facebook_networking/ |accessdate= July 9, 2013 }}</ref><ref>{{Cite news |title= Going With the Flow: Google’s Secret Switch to the Next Wave of Networking |date= April 17, 2012 |author= Steven Levy |work= Wired |url= http://www.wired.com/wiredenterprise/2012/04/going-with-the-flow-google/ |accessdate= July 9, 2013 }}</ref>
 
==References==