OVHcloud Module

Connect WISECP to OVHcloud Public Cloud. The catalogue becomes priced products, instances are provisioned automatically, and customers get controlled tools.

Reaching the Screen

Go to Products → Hosting Server → OVHcloud: {admin}/ovhcloud

Activate the Module Menu

1. Open Products → Hosting Server and click Add New Server below the page title.
2. Under Server Automation Module, choose Virtualization, then select OVHcloud.
3. In Address, enter your regional API host, such as ca.api.ovh.com.
4. Fill Application Key, Application Secret and Consumer Key. OVH signs every request with these three values.
5. Add your Public Cloud Project ID and pick the matching API Endpoint.
6. Click Test Connection, then Add New Server at the bottom.
7. The record is created as active and the menu appears.

What the Module Does

Catalogue and product control

The flavour grid shows provider hardware and cost next to the WISECP product. Each row carries a public name, region policy, category, sale price and status. A flavour without a product shows a Publish button and a suggested price. New products start inactive.

Customer service tools

Feature switches decide what the customer can do. Available actions are start, stop, restart, reinstall, rename, console, rescue mode and activity. Volumes and snapshots are capped by the purchased add-on quota. The overview shows outgoing bandwidth plus allocated CPU, RAM and disk; live usage is unavailable.

Automation and lifecycle

Product generation creates the operating-system requirement. It also adds optional instance name, user-data and SSH-key inputs. Provisioning records the provider instance ID against the service. Suspension, reactivation and cancellation use that link, and cancellation removes its volumes and snapshots.

Scheduled tasks

Two automation tasks stay idle until you enable the matching setting. OVHcloud Stock Sync runs hourly and hides a product when the flavour is unavailable everywhere. OVHcloud Cost Sync runs daily, refreshes costs and reprices from your margin.

Before You Configure It

1. Create a Public Cloud project and note its project ID. Every resource lives in that project.
2. Create an application at api.ovh.com/createToken with unlimited validity and rights on /cloud/*. Treat the secret and consumer key as passwords.
3. Enable the OVHCloud server module and create an active server record. Without the record this page is not routed into the menu.
4. Enable the currency your OVHcloud subsidiary bills in. Product generation is blocked while it is missing.
5. Confirm the module license, plus enough provider quota for a controlled test instance.

Settings and Product Controls

Installation and Operation

Prepare the provider credentials

1. Open api.ovh.com/createToken, request rights on /cloud/* for all four methods, and choose unlimited validity.
2. Store the three values in a password manager.
3. Keep one Public Cloud project for WISECP automation. The catalogue is read from it.

Connect and test the module

1. On the module page, click the gear-shaped Settings button in the top action bar.
2. Choose the endpoint, paste the three credential values, and enter the project ID.
3. Set the margin, stock and cost-sync policy, then pick the add-ons and features.
4. Click Test Connection. It uses the values currently typed in the form.
5. After the connected indicator appears, click Save Settings.

Import and reconcile the catalogue

1. Click the cloud-download Import from API button in the top action bar.
2. Choose at least one option, then click Start Import in the window footer.
3. Missing flavours arrive with the default margin. A cost-only update leaves sale prices untouched.
4. A pinned region that no longer exists is reset to automatic.

Review flavours and pricing

1. Check hardware, cost and region, then choose the public name, region policy and category.
2. Click Publish on a flavour you want to sell. The product is created inactive.
3. Enter the sale price and save the grid.
4. For bulk repricing, enter a rate in Target Margin and click Apply to All.

Configure requirements and paid extras

1. Enable only the volume and snapshot add-ons you intend to sell.
2. Review the generated operating-system, instance-name, user-data and SSH-key requirements.
3. Set add-on prices and quotas against provider costs. The tools enforce them.

Verify with an inactive test product

1. Keep one product inactive and create a controlled test order.
2. Run provisioning. Confirm the instance ID, IP and name return to WISECP.
3. Test the enabled power, console, reinstall, snapshot and volume tools.
4. Cancel the test service. Confirm the instance, volumes and snapshots are gone at OVHcloud.
5. Activate the product for sale.

Maintain prices, stock and choices

1. Run catalogue import after provider changes. Use cost synchronization to keep sale prices manual.
2. Review stock visibility, pinned regions and add-on quotas before publishing.

Things to Watch

Privileges

Product Operations (PRODUCTS_OPERATION) is required to configure the page, import flavours and change prices. Customers get only the tools enabled in module settings.

Related Screens

• Servers
• Product Groups
• Server Modules