Skip to content

Bare Metal

Bare Metal Server provides dedicated physical servers through a request-based provisioning workflow.

Use Bare Metal when a workload needs direct access to physical resources without virtualization overhead.

Introduction

Bare Metal Servers provide dedicated CPU, memory, storage, and network resources. Bare Metal integrates with cloud infrastructure through Bridge Gateway connectivity.

Key Features

Performance and control

Feature Description
Dedicated hardware access Full control over physical server resources without virtualization overhead or resource sharing.
Maximum performance Direct hardware access for compute-intensive workloads.
Custom hardware configurations Select CPU, memory, operating-system storage, and network specifications.
GPU-enabled hardware Select from available GPU configurations built into the hardware.
Rack space rental Rent rack space by rack units (RU) for custom hardware deployment and colocation requirements.

Integration and connectivity

Feature Description
Bridge Gateway integration Connect bare metal infrastructure to existing cloud environment through network bridging.
Hybrid cloud architecture Combine bare metal performance with cloud flexibility.
Network isolation Maintain security boundaries while enabling controlled connectivity to cloud services.

Operational management

Feature Description
Request-based provisioning Installation and configuration are handled by the operations team.
Status monitoring Provides visibility into server status, power state, and connectivity information.
Lifecycle management Supports provisioning through decommissioning.

Common Use Cases

High-performance computing

  • Database workloads that require maximum I/O performance and dedicated resources.
  • Scientific computing, financial modeling, and analytics.
  • Machine learning, AI training, and graphics processing workloads that require dedicated GPUs.
  • Real-time processing workloads with strict latency requirements.

Legacy system integration

  • Migrating applications while maintaining physical infrastructure performance characteristics.
  • Meeting requirements for physical isolation while enabling cloud connectivity.
  • Running applications that require specific hardware configurations or cannot operate in virtualized environments.
  • Supporting systems that require direct hardware access for licensing or performance reasons.
  • Deploying customer-owned hardware in rented rack space.

Enterprise workloads

  • Oracle, SQL Server, and other enterprise databases.
  • SAP, Oracle ERP, and other mission-critical business applications.
  • Custom hypervisor platforms such as OpenShift by Red Hat, VMware vSphere, or Proxmox.
  • Development environments that need dedicated resources matching production infrastructure.

Getting Started

This example demonstrates requesting your first bare metal server for a production database environment. You'll learn how to select appropriate hardware specifications, connect to an existing Bridge Gateway, and understand the provisioning workflow from request through activation.

Step 1: Prerequisites and Planning

Scenario: Your organization needs to migrate a mission-critical PostgreSQL database from a virtualized environment to dedicated hardware for improved performance and compliance requirements. The database serves a high-traffic web application requiring consistent low-latency responses.

Requirements Analysis

  • Performance Requirements: High-performance database workload requiring dedicated CPU and memory resources
  • Hardware Requirements: Minimum 32 CPU cores, 128GB RAM, OS Storage 480GB NVMe SSD with additional storage 2TB NVMe SSD for optimal database performance
  • Network Requirements: Connection to existing application infrastructure through Bridge Gateway integration
  • Provisioning Requirements: Request-based provisioning handled by professional operations team

Resource Prerequisites

  • Active Bridge Gateway already created and operational (required before bare metal request)
  • Documented hardware specifications matching database performance requirements
  • Network architecture planning including IP address assignments and connectivity requirements
  • Cloud Support coordination for installation scheduling and access requirements

Step 2: Navigate to Bare Metal Request

  1. Access Bare Metal Section
  2. Log into the Cloud Portal
  3. Navigate to Compute → Bare Metals
  4. Verify you see the Bare Metal listing page with available actions
  5. Initiate Server Request
  6. Click the Request Bare Metal button
  7. Confirm you see the bare metal request form
  8. Verify prerequisite check shows at least one active Bridge Gateway

Step 3: Configure Hardware Specifications

  1. Select Server Configuration
  2. Size: Choose "Standard" from available configurations
  3. Network Configuration
  4. Bridge Gateway: Select your existing active Bridge Gateway from dropdown
  5. IP Assignment: Review planned IP address allocation within Bridge Gateway subnet

Step 4: Specify Operational Requirements

  1. Installation Details
  2. Configuration Notes: Document any specific configuration requirements for Cloud Support in the description field. For example, specifying a preferred OS (Ubuntu 24.04 LTS, RHEL 10, Windows Server 2025), or requesting additional storage to the existing OS storage.

Step 5: Review and Submit Request

  1. Configuration Review
  2. Hardware Summary: Verify all specifications match requirements
  3. Cost and Provisioning Confirmation
    1. Review estimated costs for hardware configuration from Cloud Calculator
    2. Confirm understanding of request-based provisioning process
    3. Verify all requirements are clearly documented for our team

Step 6: Submit and Track Request

  1. Request Submission
  2. Click Submit Request to initiate provisioning workflow
  3. A ticket will be created in Cloud Support Portal for tracking and communication with our Cloud Support team
  4. Confirm request appears in Bare Metal listing with "Pending Provisioning" status
  5. Monitor Request Status
  6. Track request progress through status updates
  7. Pending Provisioning: Request being analyzed, in which physical hardware installation and configuration will start after
  8. Active: Installation complete, awaiting activation

Step 7: Activation and Validation

  1. Cloud Support Coordination
  2. Operations team handles physical installation and basic configuration
  3. Network connectivity established with specified Bridge Gateway
  4. Operating system installation and initial security configuration completed
  5. Server Activation
  6. Operations team activates server after successful installation validation
  7. Status changes to "Active" with billing initiation
  8. Server appears in listing with status information
  9. Connectivity Validation
  10. Verify server connectivity through Bridge Gateway integration
  11. Confirm network access matches planned architecture

Important Notes

  • Bare Metal Server requests require at least one active Bridge Gateway before submission
  • Physical hardware provisioning is handled through request-based workflow with Cloud Support coordination
  • Specialized hardware (GPUs, high-memory configurations) may require additional coordination and validation
  • Operations team handles all physical installation, basic configuration, and initial connectivity setup
  • Server activation initiates billing and transitions server to customer management responsibility