How does this Bare Metal Solution config builder keep up with new GCP features?

The Bare Metal Solution options surface what is currently documented in the Google Cloud reference for that service. When Google adds a new property or value, we add it here after verifying the schema in a real project. If a recently-announced feature is not yet selectable, treat that as a 'not yet supported' signal rather than an opinion that it should not be used.

Will the output of this Bare Metal Solution config builder pass `gcloud ... --validate-only` or `terraform validate`?

It produces structurally valid output for the GCP schemas it supports. We still recommend running provider validation locally before applying — schemas evolve and a recently-released property may not yet be reflected. When validation does fail, the message points at the exact attribute the schema rejected.

GCP Bare Metal Solution Config Builder

ComputeGCP

Build Bare Metal Solution configurations with machine types, network attachments, LUNs, and NFS volumes.

Last verified: May 2026

Bare Metal Solution Configuration

Build Bare Metal Solution configurations with machine types, network attachments, LUNs, and NFS volumes.

Required Fields

namemachineTypeosImagenetworksluns

{
  "name": "projects/my-project/locations/us-central1/instances/bms-oracle-prod-01",
  "machineType": "o2-standard-112-metal",
  "osImage": "projects/my-project/locations/us-central1/osImages/rhel-8-sap",
  "hyperthreadingEnabled": true,
  "networks": [
    {
      "name": "projects/my-project/locations/us-central1/networks/bms-client-network",
      "type": "CLIENT",
      "ipAddress": "10.240.0.10",
      "vlanAttachments": [
        {
          "peerVlanId": 100,
          "peerIp": "169.254.0.1/30",
          "routerIp": "169.254.0.2/30"
        }
      ]
    },
    {
      "name": "projects/my-project/locations/us-central1/networks/bms-private-network",
      "type": "PRIVATE",
      "ipAddress": "192.168.1.10"
    }
  ],
  "luns": [
    {
      "name": "boot-lun",
      "sizeGb": 200,
      "storageType": "SSD",
      "shareable": false
    },
    {
      "name": "data-lun-01",
      "sizeGb": 4096,
      "storageType": "SSD",
      "shareable": false
    },
    {
      "name": "log-lun-01",
      "sizeGb": 1024,
      "storageType": "SSD",
      "shareable": false
    }
  ],
  "volumes": [
    {
      "name": "projects/my-project/locations/us-central1/volumes/nfs-shared",
      "protocol": "NFS",
      "sizeGb": 2048,
      "snapshotPolicy": {
        "enabled": true,
        "hourlySchedule": { "snapshotsToKeep": 24 },
        "dailySchedule": { "snapshotsToKeep": 7 }
      }
    }
  ],
  "labels": {
    "workload": "oracle-db",
    "environment": "production"
  }
}

Generated Output

Output will appear here...

About This Tool

Build Bare Metal Solution configurations with machine types, network attachments, LUNs, and NFS volumes. This tool helps GCP engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.

Real-World Scenario

Your team is migrating an Oracle Database workload from on-prem Exadata to the cloud. Oracle's licensing prohibits running on virtualized infrastructure for the 'core-based' license you have. Standard Compute Engine VMs would require relicensing at significantly higher cost. The builder generates a BMS config: dedicated physical hardware with the same Oracle license you already own, connected to your GCP VPC for app-tier integration. Migration completes without relicensing; performance is comparable to on-prem; operational overhead drops because Google manages the BMS hardware.

When to Use This Tool

•Replacing a hand-edited Bare Metal Solution resource with a clean, reviewable version that lives in source control going forward.
•Generating a Bare Metal Solution starting point for a Google Cloud Architecture Framework review where reviewers want baseline configs.
•Pre-flighting a Bare Metal Solution change against a change-management ticket so the implementation matches what was approved.
•Comparing two candidate Bare Metal Solution layouts side by side to pick the one with the cleaner IAM blast radius.

Pro Tips

TIP

Bare Metal Solution is GCP's purpose-built infrastructure for Oracle Database workloads, SAP HANA, and other apps requiring dedicated physical hardware with low-latency connectivity to GCP services. For most workloads, regular Compute Engine is the right answer; BMS is for specific licensing/performance requirements.

TIP

BMS hardware is single-tenant and physical — no hypervisor, no shared resources. This satisfies Oracle's 'core-based' licensing without the BYOL complications of running Oracle Database on virtualized infrastructure. Combined with the OCI-style 'low-latency to cloud APIs', this is the best of both worlds for hybrid Oracle workloads.

TIP

BMS has high minimum commitments — typically 6-month or 12-month contracts. Don't provision BMS hardware for short-term projects. The use case is: you're committing to Oracle on GCP for years, and BMS provides the hardware compliance Oracle requires.

How It Works Under the Hood

The builder constructs Bare Metal Solution configurations: instance resource (machine type from BMS catalog: a3-highgpu, hpc-12r-2vol, etc., network attachments specifying VLANs and IP ranges, LUNs for block storage, NFS shares for file storage), and the surrounding networking (BMS pod connection to GCP VPC). Output is generated as gcloud bms commands and Terraform google_bare_metal_solution_instance + google_bare_metal_solution_volume resources.

Frequently Asked Questions

How does this Bare Metal Solution config builder keep up with new GCP features?: The Bare Metal Solution options surface what is currently documented in the Google Cloud reference for that service. When Google adds a new property or value, we add it here after verifying the schema in a real project. If a recently-announced feature is not yet selectable, treat that as a 'not yet supported' signal rather than an opinion that it should not be used.
Will the output of this Bare Metal Solution config builder pass `gcloud ... --validate-only` or `terraform validate`?: It produces structurally valid output for the GCP schemas it supports. We still recommend running provider validation locally before applying — schemas evolve and a recently-released property may not yet be reflected. When validation does fail, the message points at the exact attribute the schema rejected.

Related Learning Guides

Compute Engine Machine Types22 min read
GKE vs Cloud Run Decision24 min read

Was this tool helpful?

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.

GCP Bare Metal Solution Config Builder

ComputeGCP

Build Bare Metal Solution configurations with machine types, network attachments, LUNs, and NFS volumes.

Last verified: May 2026

Bare Metal Solution Configuration

Build Bare Metal Solution configurations with machine types, network attachments, LUNs, and NFS volumes.

Required Fields

namemachineTypeosImagenetworksluns

Generated Output

Output will appear here...

About This Tool

Real-World Scenario

When to Use This Tool

•Replacing a hand-edited Bare Metal Solution resource with a clean, reviewable version that lives in source control going forward.
•Generating a Bare Metal Solution starting point for a Google Cloud Architecture Framework review where reviewers want baseline configs.
•Pre-flighting a Bare Metal Solution change against a change-management ticket so the implementation matches what was approved.
•Comparing two candidate Bare Metal Solution layouts side by side to pick the one with the cleaner IAM blast radius.

Pro Tips

TIP

How It Works Under the Hood

Frequently Asked Questions

How does this Bare Metal Solution config builder keep up with new GCP features?: The Bare Metal Solution options surface what is currently documented in the Google Cloud reference for that service. When Google adds a new property or value, we add it here after verifying the schema in a real project. If a recently-announced feature is not yet selectable, treat that as a 'not yet supported' signal rather than an opinion that it should not be used.
Will the output of this Bare Metal Solution config builder pass `gcloud ... --validate-only` or `terraform validate`?: It produces structurally valid output for the GCP schemas it supports. We still recommend running provider validation locally before applying — schemas evolve and a recently-released property may not yet be reflected. When validation does fail, the message points at the exact attribute the schema rejected.

Related Learning Guides

Compute Engine Machine Types22 min read
GKE vs Cloud Run Decision24 min read

Was this tool helpful?