Bare-Metal Provisioning

How can operating systems be remotely deployed on bare-metal servers?

Problem

Both cloud providers and cloud consumers require the ability to remotely provision bare-metal servers. This process begins with the remote deployment of operating systems. However, establishing a remote connection for provisioning purposes is not possible without software being already installed on bare-metal servers.

Solution

Contemporary server features are utilized to install remote management support into the server ROM to establish the required remote bare-metal provisioning system.

Application

Specialized discovery and deployment agents can be utilized within the remote bare-metal provisioning system to locate and provision available bare-metal servers with operating systems dynamically.

Mechanisms

Cloud Storage Device, Hypervisor, Logical Network Perimeter, Resource Management System, Resource Replication, SLA Management System

Compound Patterns

Burst In, Burst Out to Private Cloud, Burst Out to Public Cloud, Cloud Authentication, Cloud Balancing, Elastic Environment, Infrastructure-as-a-Service (IaaS), Isolated Trust Boundary, Multitenant Environment, Platform-as-a-Service (PaaS), Private Cloud, Public Cloud, Resilient Environment, Resource Workload Management, Secure Burst Out to Private Cloud/Public Cloud, Software-as-a-Service (SaaS)

A sample cloud architecture resulting from the application of the Bare-Metal Provisioning pattern (Part I).

A sample cloud architecture resulting from the application of the Bare-Metal Provisioning pattern (Part II).

NIST Reference Architecture Mapping

This pattern relates to the highlighted parts of the NIST reference architecture, as follows: