Introduction

The Bare Metal Server service provides dedicated physical servers through a request-based provisioning workflow. This service delivers full hardware control and maximum performance for applications that require direct access to physical resources without virtualization overhead.

Unlike virtualized infrastructure that shares resources, our Bare Metal Servers ensure complete hardware isolation with dedicated CPU, memory, storage, and network resources while integrating seamlessly with your cloud infrastructure through Bridge Gateway connectivity.

Key Features

Performance and Control

• Dedicated Hardware Access: Full control over physical server resources without virtualization overhead or resource sharing
• Maximum Performance: Direct hardware access for compute-intensive workloads requiring optimal performance
• Custom Hardware Configurations: Choose from various CPU, memory, OS storage, and network specifications to match workload requirements
• GPU-Enabled Hardware: Select your preferred setup from our various GPU configurations, built-in within our hardware.
• Rack Space Rental: Rent dedicated rack space by rack units (RU) for custom hardware deployment (Bring Your Own) and colocation requirements

Integration and Connectivity

• Bridge Gateway Integration: Seamless connection to existing cloud infrastructure through automated network bridging
• Hybrid Cloud Architecture: Combine bare metal performance with cloud flexibility for comprehensive infrastructure solutions
• Network Isolation: Maintain security boundaries while enabling controlled connectivity to cloud services

Operational Management

• Request-Based Provisioning: Professional installation and configuration handled by expert operations team
• Status Monitoring: Real-time visibility into server status, power state, and connectivity information
• Lifecycle Management: Complete server lifecycle support from provisioning through decommissioning

Common Use Cases

High-Performance Computing

• Database Workloads: Mission-critical databases requiring maximum I/O performance and dedicated resources
• Compute-Intensive Applications: Scientific computing, financial modeling, and analytics requiring sustained high performance
• GPU Computing: Machine learning, AI training, and graphics processing workloads requiring dedicated GPU resources
• Real-Time Processing: Applications with strict latency requirements and consistent performance needs

Legacy System Integration

• Application Migration: Modernize legacy applications while maintaining performance characteristics of physical infrastructure
• Compliance Requirements: Meet regulatory requirements for physical isolation while enabling cloud connectivity
• Specialized Software: Run applications that require specific hardware configurations or cannot operate in virtualized environments
• Hardware-Dependent Systems: Support systems requiring direct hardware access for licensing or performance reasons
• Custom Equipment Deployment: Deploy customer-owned hardware in rented rack space for specialized requirements and legacy system integration

Enterprise Workloads

• Production Databases: Oracle, SQL Server, and other enterprise databases requiring dedicated resources and optimal performance
• ERP Systems: SAP, Oracle ERP, and other mission-critical business applications requiring consistent performance
• Custom Hypervisor Platforms: Deploy specialized virtualization platforms like OpenShift by Red Hat, VMware vSphere, or Proxmox requiring direct hardware control
• Development Environments: Provide development teams with dedicated resources matching production infrastructure

Getting Started

Basic Bare Metal Server Request for Database Workload

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
   1. Log into the Cloud Portal
   2. Navigate to Compute → Bare Metals
   3. Verify you see the Bare Metal listing page with available actions
2. Initiate Server Request
   1. Click the Request Bare Metal button
   2. Confirm you see the bare metal request form
   3. Verify prerequisite check shows at least one active Bridge Gateway

Step 3: Configure Hardware Specifications

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

Step 4: Specify Operational Requirements

1. Installation Details
   1. 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
   1. Hardware Summary: Verify all specifications match requirements
   2. 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
   1. Click Submit Request to initiate provisioning workflow
   2. A ticket will be created in Cloud Support Portal for tracking and communication with our Cloud Support team
   3. Confirm request appears in Bare Metal listing with "Pending Provisioning" status
2. Monitor Request Status
   1. Track request progress through status updates 
   2. Pending Provisioning: Request being analyzed, in which physical hardware installation and configuration will start after
   3. Active: Installation complete, awaiting activation

Step 7: Activation and Validation

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

General Bare Metal Request Summary

For All Use Cases:

1. Prerequisites Validation - Ensure active Bridge Gateway exists and hardware requirements are documented
2. Hardware Selection - Choose appropriate specifications based on workload requirements and performance needs
3. Network Integration - Plan connectivity through Bridge Gateway integration and network architecture
4. Request Submission - Submit detailed hardware and configuration requirements to Cloud Support
5. Installation Coordination - Work with operations team throughout provisioning timeline
6. Activation and Validation - Verify server functionality and integration after professional installation

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

Related Documentation

Configuration and Setup

• Bridge Gateway User Guide - Complete guide for creating and managing Bridge Gateways required for bare metal connectivity