Create a VM offering after saving its Google Cloud connection. Saving the offering describes a future server; the intended activation process requests real, chargeable resources.

Configure the offering

1. Open Packages → Packages → Add Package.
2. Choose PD Google Compute Engine and the intended saved Google Cloud account.
3. Set Region & zone, Plan, Operating system and Disk size (GB) in the module fields.
4. Review Resource name prefix, SSH public key and Auto-generate SSH key, then the client controls below.
5. Set the terms and your own pricing, and save it in the intended package group.
6. When ready for sale, add that group to the appropriate order form under Packages → Order Forms.

The reviewed release uses an older Products path rather than the newer native option generator. Start with the package’s fixed resource settings and obtain guidance for your installed build before adding manual customer-selectable dimensions. Do not copy option keys from another platform.

Review the intended activation process. Eligible paid pending services use Provision Paid Pending Services automation, or staff activation if you hold them for manual review. Keep the normal cron and automation running; saving a package or receiving payment alone does not establish that a VM is ready.

Check the server specification

Select a full zone, not just a region. Choose a machine type offered in that zone and an operating-system image from the module’s choices. The machine and zone lists can come from cached provider data or a shipped fallback; an available-looking choice is not a reservation of capacity. The OS list is curated, not a list of every Google image.

Choose a disk size suitable for the image and intended workload. The module’s minimum field value is 10 GB, but that alone does not establish that a particular image fits. Supported disk growth does not imply a shrink workflow or automatic growth of the guest filesystem.

The reviewed provisioner uses the project’s default VPC network. Ask the project administrator to confirm that this network and the intended access rules exist. The product form does not expose a custom-network selector; do not disable an organisation policy broadly to recreate a missing network.

Review the actual selected checkout values, including hidden choices. Generated choices can override offering defaults.

Prepare SSH access without exposing the provider key

SSH public key is for the intended public SSH key, not a private key and not the Google service-account JSON credential. The product key applies to newly created VMs; changing it does not by itself replace keys on existing servers.

Review Auto-generate SSH key if the customer should receive a separate generated key. Confirm the intended key download and guest login during authorised verification. A saved setting is not proof that SSH is reachable through network, guest or organisation settings.

Choose the client controls

Review Client: Power controls, Client: Firewall, Client: SSH keys and Client: Console output. Console output is a read-only diagnostic view; it is separate from the interactive browser terminal.

Review Client: Snapshots together with Included snapshots and any purchased snapshot allowance. Zero included snapshots does not provide a free snapshot entitlement. Review Client: Volumes deliberately, since additional data disks create provider costs. A customer-facing switch does not decide how you price those resources.

Client: Console also depends on the module-wide browser-console setting. Leave that global setting for a separate deliberate setup; do not switch it on merely to test the product form. Review any Client Area Section text before exposing it to customers, keeping credentials out of it.

Verify an intended activation

Preview the order form and your own pricing. When ready, use your normal authorised provisioning test, recognising that VMs, disks and allocated addresses can incur provider charges. Inspect Clients & Servers, Activity, actual resource state and the intended customer access before calling setup complete. Keep the normal cron running for background progress.

A saved offering, a Ready options label or a passed connection test is not completed VM or guest-login proof. If the outcome is uncertain, reconcile existing resources before repeating activation. Do not include provider keys, SSH private keys or full customer records.

See the PD Google Compute Engine Blesta guide for related setup, or explore PD Google Compute Engine.