Misplaced Pages

Bare-metal server: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 12:38, 18 August 2017 editAndy Dingley (talk | contribs)Autopatrolled, Extended confirmed users, Pending changes reviewers, Rollbackers160,333 edits restore quotes - clearer before← Previous edit Latest revision as of 20:59, 10 September 2024 edit undoDiscospinster (talk | contribs)Administrators464,928 edits →Companies offering BMaaS products: remove entries with no article 
(109 intermediate revisions by 54 users not shown)
Line 1: Line 1:
{{short description|Computer server which is used by one tenant only}}
{{Original_research|date=July 2017}}
{{rewrite|date=May 2023}}
⚫ A ''' 'bare-metal server' ''' is a descriptive term for a ] to distinguish it from modern forms of ] and ]. It is defined as a 'single-tenant physical server'.<ref >{{Cite web |title=Bare metal vs. virtual servers: Which choice is right for you? |website=Thoughts on Cloud |date=July 25, 2014 |author=Reynaldo Mincov |url=http://www.thoughtsoncloud.com/2014/07/bare-metal-vs-virtual-servers-choice-right/ }}</ref>


⚫ In ], a '''bare-metal server '''is a physical ] that is used by one consumer, or tenant, only.<ref>{{ cite web | title = Bare metal vs. virtual servers: Which choice is right for you? | website = Thoughts on Cloud | date = 25 July 2014 | author = Reynaldo Mincov | url = http://www.thoughtsoncloud.com/2014/07/bare-metal-vs-virtual-servers-choice-right/ }}</ref> Each server offered for rental is a distinct physical piece of ] that is a functional server on its own. They are not ] running in multiple pieces of shared hardware.
Bare-metal servers have a single 'tenant'. They are not shared between customers. Each server may run any amount of work for the customer, or may have multiple simultaneous users, but they are dedicated entirely to the customer who is renting them. Unlike many servers in a ], they are not being shared between multiple customers.


The term is used for distinguishing between servers that can host multiple tenants and which use ] and ].<ref name="Rackspace" /> Unlike bare-metal servers, cloud servers are shared between multiple tenants. Each bare-metal server may run any amount of work for a user, or have multiple simultaneous users, but they are dedicated entirely to the entity who is renting them.
Bare-metal servers are 'physical' servers. Each logical server offered for rental is a distinct physical piece of hardware that is a functional server on its own. They are not ] running in multiple on shared hardware.

== Development of virtualisation ==
⚫ At one time, ''all'' servers were bare-metal servers. Servers were kept ] and often belonged to the organisation using and operating them. ]s developed very early on (early 1960s) to allow ]. Single large computers, ]s or ]s, were commonly housed in centralised locations and their services shared through a ]. The shift to cheap ]s in the 1980s changed this as the market expanded, and most organizations, even the smallest, began to purchase or lease their own computers. Popular growth of the internet, and particularly the web, in the 1990s encouraged the practice of hosting in ]s, where many customers shared the facilities of single servers. Small web servers at this time often cost more for their connectivity than their hardware cost, encouraging this centralisation. ]'s ability for ] also made it easy to co-host many web sites on the same ].

⚫ From around 2000, or 2005 in commercially practical terms, interest grew in the use of ] and then ], where ] made the computing ''service'' the ] commodity, rather than the server hardware. ]s were developed which could offer many ]s hosted on larger physical servers. The load pattern of multiple users has long been recognised as being smoother overall than individual users, so these virtual machines could make more efficient use of the physical hardware and its costs, whilst also appearing to have higher individual performance than a simple cost-share would suggest.


== Bare-metal advocacy == == Bare-metal advocacy ==

Hypervisors provide secure isolation between tenants but there can still be a 'noisy neighbour effect'.<ref name="Internap" >{{Cite web |title= Bare metal vs. hypervisor: The evolution of dedicated servers |date=February 26, 2015 |author= Eric Sarault |url=http://www.internap.com/2015/02/26/bare-metal-vs-hypervisor/ }}</ref> If a physical server is multi-tenanted, peaks of load from one tenant may consume enough machine resources to temporarily affect other tenants. As the tenants are otherwise isolated, it is also hard to manage or ] this. Bare-metal servers, and single tenancy, can avoid this. As, once again, server costs are dropping as a proportion of ] against their administration overhead, the classic solution of 'throwing hardware at the problem' becomes viable again.
]s provide some isolation between tenants but there can still be a noisy neighbour effect.<ref name="Internap" >{{Cite web
|title= Bare metal vs. hypervisor: The evolution of dedicated servers
|date=26 February 2015
|author= Eric Sarault
|url=http://www.internap.com/2015/02/26/bare-metal-vs-hypervisor/
}}</ref> If a physical server is multi-tenanted, peaks of load from one tenant may consume enough machine resources to temporarily affect other tenants. As the tenants are otherwise isolated, it is also hard to manage or ] this. Bare-metal servers, and single tenancy, can avoid this.<ref name="Rackspace" /> In addition, hypervisors provide weaker isolation and are much more risky from a security point-of-view compared to using separate machines. Attackers have always found vulnerabilities in the isolation software (such as hypervisors), covert channels are impractical to counter without physically separate machines, and shared hardware is vulnerable to defects in hardware protection mechanisms such as ], ], and ].<ref name="Wheeler" >{{Cite web
|title= Cloud Security: Virtualization, Containers, and Related Issues
|date=2018-08-20
|author= David A. Wheeler
|url= https://www.dwheeler.com/essays/cloud-security-virtualization-containers.html
}}</ref> As, once again, server costs are dropping as a proportion of ] against their administration overhead, the classic solution of 'throwing hardware at the problem' becomes viable again.


== Bare-metal cloud hosting == == Bare-metal cloud hosting ==
{{quote|Bare-metal cloud servers do not run a hypervisor, are not virtualised -- but can still be delivered via a cloud-like service model.|source=<ref name="CWDN" >{{Cite web |title= What is bare-metal cloud? |website=] Application Developer Network|author=Adrian Bridgwater |date=September 6, 2013 |url=http://www.computerweekly.com/blogs/cwdn/2013/09/what-is-bare-metal-cloud.html }}</ref>}} {{blockquote|Bare-metal cloud servers do not run a hypervisor, are not virtualised -- but can still be delivered via a cloud-like service model.|source= Gopala Tumuluri, '']''<ref name="CWDN" >{{Cite web
|title= What is bare-metal cloud?
|website=] Application Developer Network
|author=Gopala Tumuluri
|date=6 September 2013
|url=http://www.computerweekly.com/blogs/cwdn/2013/09/what-is-bare-metal-cloud.html
}}</ref>}}
], particularly through ], offers many advantages to make hosting conveniently manageable. Combining the features of both cloud hosting, and bare-metal servers, offers most of these, whilst still conveying the performance advantages.<ref name="CWDN" /> ], particularly through ], offers many advantages to make hosting conveniently manageable. Combining the features of both cloud hosting, and bare-metal servers, offers most of these, whilst still conveying the performance advantages.<ref name="CWDN" /> These cloud offerings are also called Bare-Metal-as-a-Service (BMaaS).

Some bare-metal cloud servers may run a hypervisor or containers, e.g., to simplify maintenance or provide additional layers of isolation.<ref name="Wheeler" />

Note that the distinction between these services and the traditional dedicated server offerings is the user's ability to provision infrastructures composed out of multiple servers, a complex network and storage setup rather than servers in isolation.

== Bare-metal cloud software ==
Both commercial and open-source platforms ] enabling companies to build their own private bare-Metal private clouds.

BMaaS software typically takes over the lifecycle management of the equipment in a datacenter (compute, storage and network Switches, firewalls, load balancers and others). It enables datacenter operators to offload much of the manual work typically associated with deploying hardware. It also reduces waste by simplifying reuse and increases security by implementing automatic cleanup and automatic segmentation between tenants at the network level. Increasingly BMaaS software is used internally to reduce the costs associated with lifecycle management of equipment for enterprises with large fleets of servers.<ref>{{Cite web|date=2021-09-21|title=Bare-Metal Servers Gain Momentum in the Data Center Market|url=https://datacenterfrontier.com/bare-metal-servers-gain-momentum-in-the-data-center-market/|access-date=2021-11-22|website=datacenterfronier.com | language=en}}</ref>

BMaaS software aims to simplify hardware management and enable its as-a-service consumption. It handles primarily the layer below a ] or container-based solution. It often collaborates with the layers above through integrations such as the Kubernetes cluster autoscaler.<ref>{{Cite web|date=2021-11-22|title=Kubernetes Cluster Autoscaler implementation for Packet|url=https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/packet/README.md#notes|access-date=2021-11-22|website=github.com|language=en}}</ref>

== Comparison with composable disaggregated infrastructure==
BMaaS software has a similar objective to ] in that it aims to offer the user the ability to "compose" the desired compute unit defined as a set of resources (such as compute or storage). The distinction is that the storage and compute need not be "dissagregated" (accessed from outside the server unit) as this often requires specialized hardware. Instead, the same result is achieved with off-the-shelf hardware by selecting a matching server that matches the desired characteristics (RAM, CPU cores, local disk capacity, GPU, FPGA, SmartNICs) from a pool of servers and reconfiguring the network so that the server joins the others that a tenant has deployed.

Note that in some implementations, the storage component is external to the systems using ] blurring the lines between BMaaS and composable infrastructure. This allows the user to choose the size and performance of the node's storage in a manner similar to classical virtualized Infrastructure as a Service offerings. This has the advantage of lower variability (snowflaking) in the hardware pool and the possibility of faster migration from one equipment to another in the event of hardware failure.

==Use in edge computing==
As new workloads such as ], ], ]s, and ] are gaining ground so is the demand for low latency cloud services so does demand for ].<ref>{{Cite web|date= 2019-11-26|title=Living On The Edge (Part II): What's Driving Edge Computing?|url=https://www.forbes.com/sites/forbestechcouncil/2019/11/26/living-on-the-edge-part-ii-whats-driving-edge-computing/?sh=616829f03c40|access-date=2022-03-29|website= www.forbes.com|language=en}}</ref>

Bare Metal and the BMaaS automation software is used for edge cloud implementations, where large numbers of small data-centers need to be automated and then consumed as a service and where the service needs to offer the lowest latency possible.<ref>{{Cite web|date=2022-03-09|title=How PhoenixNAP's bare metal PoP in American Tower data center connects to bigger picture|url=https://www.edgeir.com/how-phoenixnaps-bare-metal-pop-in-american-tower-data-center-connects-to-bigger-picture-20220309|access-date=2022-03-29|website= www.edgeir.com|language=en}}</ref>

==History==

⚫ At one time, all servers were bare-metal servers. Servers were kept ] and often belonged to the organisation using and operating them. ]s developed very early on (early 1960s) to allow ]. Single large computers, ]s or ]s, were commonly housed in centralised locations and their services shared through a ]. The shift to cheap ]s in the 1980s changed this as the market expanded, and most organisations, even the smallest, began to purchase or lease their own computers. Popular growth of the internet, and particularly the web, in the 1990s encouraged the practice of hosting in ]s, where many customers shared the facilities of single servers. Small web servers at this time often cost more for their connectivity than their hardware cost, encouraging this centralisation. ]'s ability for ] also made it easy to co-host many web sites on the same ].

⚫ From around 2000, or 2005 in commercially practical terms, interest grew in the use of ] and then ], where ] made the computing ''service'' the ] commodity, rather than the server hardware. ]s were developed which could offer many ]s hosted on larger physical servers. The load pattern of multiple users has long been recognised as being smoother overall than individual users, so these virtual machines could make more efficient use of the physical hardware and its costs, whilst also appearing to have higher individual performance than a simple cost-share would suggest.

One of the forefathers of bare metal provisioning is ] that appeared in the 1990s and was using the ] (PXE) protocol. Since then various cloud providers have been building their own in-house stacks in order to offer variants of dedicated servers or bare metal cloud offerings such as:
* April 2015 OpenStack Ironic component was launched as part of the Kilo release.<ref>{{Cite web|date=2021-11-22|title=Kilo Release Schedule|url=https://wiki.openstack.org/Kilo_Release_Schedule|access-date=2021-11-22|website=equinix.com|language=en}}</ref>
* March 2020, Equinix acquired bare metal cloud provider Packet<ref>{{Cite web|date=2021-11-22|title=Equinix Completes Acquisition of Bare Metal Leader Packet|url=https://www.equinix.com/newsroom/press-releases/2020/03/equinix-completes-acquisition-of-bare-metal-leader-packet|access-date=2021-11-22|website=equinix.com|language=en}}</ref>
for $335 million.
* May 2020 Packet released a part of their stack as Tinkerbell<ref>{{Cite web|date=2021-05-04|title=Open Sourcing Tinkerbell|url=https://metal.equinix.com/blog/open-sourcing-tinkerbell/|access-date=2021-11-22|website=equinix.com|language=en}}</ref>
* June 2020 MetalSoft was launched to commercialize the Stack behind Bigstep Cloud.<ref>{{Cite web|date=2020-06-23|title=MetalSoft Launches Intelligent Bare Metal Automation Platform to Support Cloud Native Workloads|url=https://www.prweb.com/releases/metalsoft-launches-intelligent-bare-metal-automation-platform-to-support-cloud-native-workloads-808659996.html|access-date=2021-11-22|website=]|language=en}}</ref>

==Examples of BMaaS software==
Examples of BMaaS software both open-source and commercial:
* ] Ironic (open source)
* ] MaaS (open source)
* ] (commercial)
* RackN DigitalRebar (commercial) <ref>{{Cite web|date=2021-11-22|title=RackN Digital Rebar|url=https://rackn.com/rebar/|access-date=2021-11-22|website=RackN Digital Rebar|language=en}}</ref>
* Tinkerbell (open source) <ref>{{Cite web|date=2021-11-22|title=Tinkerbell|url=https://tinkerbell.org|access-date=2021-11-22|website=Tinkerbell.org|language=en}}</ref>
* xCAT (open source)
* RackHD (open source)
* Cobbler (open source)
* Foreman (open source)
* Puppet Labs Razor (commercial)

== Companies offering BMaaS products ==

* ] Metal (former Packet)
* ]
* ]


== See also == == See also ==

* ] * ]


== References == == References ==

{{Reflist|30em}}
{{refs|refs=
<ref name="Rackspace">{{ cite web | title = What is a Bare Metal Server? | publisher = ] | url = https://www.rackspace.com/en-gb/library/what-is-a-bare-metal-server }}</ref>
}}

== External links ==

*
*
*
*
*
*
*
*
*


] ]

Latest revision as of 20:59, 10 September 2024

Computer server which is used by one tenant only
This article may need to be rewritten to comply with Misplaced Pages's quality standards. You can help. The talk page may contain suggestions. (May 2023)

In computer networking, a bare-metal server is a physical computer server that is used by one consumer, or tenant, only. Each server offered for rental is a distinct physical piece of hardware that is a functional server on its own. They are not virtual servers running in multiple pieces of shared hardware.

The term is used for distinguishing between servers that can host multiple tenants and which use virtualisation and cloud hosting. Unlike bare-metal servers, cloud servers are shared between multiple tenants. Each bare-metal server may run any amount of work for a user, or have multiple simultaneous users, but they are dedicated entirely to the entity who is renting them.

Bare-metal advocacy

Hypervisors provide some isolation between tenants but there can still be a noisy neighbour effect. If a physical server is multi-tenanted, peaks of load from one tenant may consume enough machine resources to temporarily affect other tenants. As the tenants are otherwise isolated, it is also hard to manage or load balance this. Bare-metal servers, and single tenancy, can avoid this. In addition, hypervisors provide weaker isolation and are much more risky from a security point-of-view compared to using separate machines. Attackers have always found vulnerabilities in the isolation software (such as hypervisors), covert channels are impractical to counter without physically separate machines, and shared hardware is vulnerable to defects in hardware protection mechanisms such as Rowhammer, Spectre, and Meltdown. As, once again, server costs are dropping as a proportion of total cost of ownership against their administration overhead, the classic solution of 'throwing hardware at the problem' becomes viable again.

Bare-metal cloud hosting

Bare-metal cloud servers do not run a hypervisor, are not virtualised -- but can still be delivered via a cloud-like service model.

— Gopala Tumuluri, Computer Weekly

Infrastructure as a service, particularly through infrastructure as code, offers many advantages to make hosting conveniently manageable. Combining the features of both cloud hosting, and bare-metal servers, offers most of these, whilst still conveying the performance advantages. These cloud offerings are also called Bare-Metal-as-a-Service (BMaaS).

Some bare-metal cloud servers may run a hypervisor or containers, e.g., to simplify maintenance or provide additional layers of isolation.

Note that the distinction between these services and the traditional dedicated server offerings is the user's ability to provision infrastructures composed out of multiple servers, a complex network and storage setup rather than servers in isolation.

Bare-metal cloud software

Both commercial and open-source platforms exist enabling companies to build their own private bare-Metal private clouds.

BMaaS software typically takes over the lifecycle management of the equipment in a datacenter (compute, storage and network Switches, firewalls, load balancers and others). It enables datacenter operators to offload much of the manual work typically associated with deploying hardware. It also reduces waste by simplifying reuse and increases security by implementing automatic cleanup and automatic segmentation between tenants at the network level. Increasingly BMaaS software is used internally to reduce the costs associated with lifecycle management of equipment for enterprises with large fleets of servers.

BMaaS software aims to simplify hardware management and enable its as-a-service consumption. It handles primarily the layer below a hyper-converged or container-based solution. It often collaborates with the layers above through integrations such as the Kubernetes cluster autoscaler.

Comparison with composable disaggregated infrastructure

BMaaS software has a similar objective to composable disaggregated infrastructure in that it aims to offer the user the ability to "compose" the desired compute unit defined as a set of resources (such as compute or storage). The distinction is that the storage and compute need not be "dissagregated" (accessed from outside the server unit) as this often requires specialized hardware. Instead, the same result is achieved with off-the-shelf hardware by selecting a matching server that matches the desired characteristics (RAM, CPU cores, local disk capacity, GPU, FPGA, SmartNICs) from a pool of servers and reconfiguring the network so that the server joins the others that a tenant has deployed.

Note that in some implementations, the storage component is external to the systems using iSCSI blurring the lines between BMaaS and composable infrastructure. This allows the user to choose the size and performance of the node's storage in a manner similar to classical virtualized Infrastructure as a Service offerings. This has the advantage of lower variability (snowflaking) in the hardware pool and the possibility of faster migration from one equipment to another in the event of hardware failure.

Use in edge computing

As new workloads such as augmented reality, mixed reality, connected cars, and telerobotics are gaining ground so is the demand for low latency cloud services so does demand for edge computing.

Bare Metal and the BMaaS automation software is used for edge cloud implementations, where large numbers of small data-centers need to be automated and then consumed as a service and where the service needs to offer the lowest latency possible.

History

At one time, all servers were bare-metal servers. Servers were kept on-premises and often belonged to the organisation using and operating them. Operating systems developed very early on (early 1960s) to allow time-sharing. Single large computers, mainframes or minis, were commonly housed in centralised locations and their services shared through a bureau. The shift to cheap commodity PCs in the 1980s changed this as the market expanded, and most organisations, even the smallest, began to purchase or lease their own computers. Popular growth of the internet, and particularly the web, in the 1990s encouraged the practice of hosting in data centres, where many customers shared the facilities of single servers. Small web servers at this time often cost more for their connectivity than their hardware cost, encouraging this centralisation. HTTP 1.1's ability for virtual hosting also made it easy to co-host many web sites on the same server.

From around 2000, or 2005 in commercially practical terms, interest grew in the use of virtual servers and then cloud hosting, where infrastructure as a service made the computing service the fungible commodity, rather than the server hardware. Hypervisors were developed which could offer many virtual machines hosted on larger physical servers. The load pattern of multiple users has long been recognised as being smoother overall than individual users, so these virtual machines could make more efficient use of the physical hardware and its costs, whilst also appearing to have higher individual performance than a simple cost-share would suggest.

One of the forefathers of bare metal provisioning is Cobbler that appeared in the 1990s and was using the Preboot Execution Environment (PXE) protocol. Since then various cloud providers have been building their own in-house stacks in order to offer variants of dedicated servers or bare metal cloud offerings such as:

  • April 2015 OpenStack Ironic component was launched as part of the Kilo release.
  • March 2020, Equinix acquired bare metal cloud provider Packet

for $335 million.

  • May 2020 Packet released a part of their stack as Tinkerbell
  • June 2020 MetalSoft was launched to commercialize the Stack behind Bigstep Cloud.

Examples of BMaaS software

Examples of BMaaS software both open-source and commercial:

  • OpenStack Ironic (open source)
  • Canonical MaaS (open source)
  • MetalSoft (commercial)
  • RackN DigitalRebar (commercial)
  • Tinkerbell (open source)
  • xCAT (open source)
  • RackHD (open source)
  • Cobbler (open source)
  • Foreman (open source)
  • Puppet Labs Razor (commercial)

Companies offering BMaaS products

See also

References

  1. Reynaldo Mincov (25 July 2014). "Bare metal vs. virtual servers: Which choice is right for you?". Thoughts on Cloud.
  2. ^ "What is a Bare Metal Server?". Rackspace.
  3. Eric Sarault (26 February 2015). "Bare metal vs. hypervisor: The evolution of dedicated servers".
  4. ^ David A. Wheeler (2018-08-20). "Cloud Security: Virtualization, Containers, and Related Issues".
  5. ^ Gopala Tumuluri (6 September 2013). "What is bare-metal cloud?". Computer Weekly Application Developer Network.
  6. "Bare-Metal Servers Gain Momentum in the Data Center Market". datacenterfronier.com. 2021-09-21. Retrieved 2021-11-22.
  7. "Kubernetes Cluster Autoscaler implementation for Packet". github.com. 2021-11-22. Retrieved 2021-11-22.
  8. "Living On The Edge (Part II): What's Driving Edge Computing?". www.forbes.com. 2019-11-26. Retrieved 2022-03-29.
  9. "How PhoenixNAP's bare metal PoP in American Tower data center connects to bigger picture". www.edgeir.com. 2022-03-09. Retrieved 2022-03-29.
  10. "Kilo Release Schedule". equinix.com. 2021-11-22. Retrieved 2021-11-22.
  11. "Equinix Completes Acquisition of Bare Metal Leader Packet". equinix.com. 2021-11-22. Retrieved 2021-11-22.
  12. "Open Sourcing Tinkerbell". equinix.com. 2021-05-04. Retrieved 2021-11-22.
  13. "MetalSoft Launches Intelligent Bare Metal Automation Platform to Support Cloud Native Workloads". PRWeb. 2020-06-23. Retrieved 2021-11-22.
  14. "RackN Digital Rebar". RackN Digital Rebar. 2021-11-22. Retrieved 2021-11-22.
  15. "Tinkerbell". Tinkerbell.org. 2021-11-22. Retrieved 2021-11-22.

External links

Categories: