OVH Public Cloud — Setup & Management

The OVH Public Cloud module creates OpenStack instances inside your own Public Cloud project the moment a client orders — no OVH cart, no delivery delay. OVH bills your project; you bill your clients fixed Blesta prices. This one article covers both setup and operation because the module has no addon catalog and a smaller tab set than VPS/Dedicated.

Setup

Upload ovh_public_cloud to components/modules/ and install it under Settings > Company > Modules > Available.
On the Manage page click Add Cloud Project: an account name (a label for your reference), endpoint (ovh-eu, ovh-ca or ovh-us only), the three API keys — rights: GET /me plus GET/POST/PUT/DELETE /cloud/*, see OVH API Credentials, Endpoints & Subsidiaries — and the Project ID, the 32-character hexadecimal ID shown in the OVH Control Panel under Public Cloud (also in the project's URL). There is no subsidiary field. One row = one project; add more rows for more projects.
Create packages (Packages > Add Package, module OVH Public Cloud):
- Region — where new instances deploy.
- Flavor — the instance size, listed live from your project with vCPU/RAM/disk.
- Default OS Image — installed on new instances.
- OVH Billing Mode — how OVH bills the instance to your project: hourly, or monthly (cheaper for always-on instances).
Flavors and images are stored by name and resolved to region-specific IDs at provisioning time, so packages survive OVH catalog updates.
Verify the single cron task under Settings > Company > Automation: Sync OVH Public Cloud Instances (every 5 minutes). There is no price-sync task — this module has no configurable-option catalog.

Ordering and activation

New orders create the instance immediately. The service activates once the cron sees the instance ACTIVE and backfills its public IP — within a few minutes, on the next cron run. To link an instance that already exists in the project, enter its instance ID on the admin add-service form instead.

Service tabs

Actions — start/stop, soft/hard reboot, OS reinstall, VNC console.
IP Addresses — the instance's addresses.
Statistics — instance details plus your project's region quota.

There is no firewall tab: the OVH v1 API exposes no security-group management for Public Cloud. Manage security groups directly in OpenStack (Horizon or the OpenStack API) with a project user.

Suspend, unsuspend, cancel

Blesta action	What happens in your project
Suspend	The instance is stopped; its disk is retained. OVH keeps billing a stopped instance — in both hourly and monthly mode — because stopping is not OpenStack shelving; only shelving or deletion frees the compute billing.
Unsuspend	The instance is started again.
Cancel	The instance is deleted permanently, immediately — disk and data included.

Heads-up: unlike VPS and Dedicated, cancellation here is destructive and irreversible. Make sure staff understand that before processing cancellations, and snapshot anything worth keeping first.

Knowledge Base