Skip to content

OVH Public Cloud

Muppy integrates with OVH Public Cloud so you can create and manage cloud instances directly as Muppy Hosts. From a connected OVH account you can:

  • Commission (create) one or more instances and have Muppy register, provision and enroll them automatically — each new instance arrives as a ==Managed== Host, ready to use, with no manual SSH setup.
  • Let an agent create one through the MCP, one instance per call, billed by the hour and always dated — see Creating an OVH instance.
  • Manage their lifecycle — an automatic decommission date is set as a safety net, and you can decommission a Host (which also deletes the OVH instance) at any time.

OVH access = a Cloud Provider Account

OVH access is configured through an OVH Cloud Provider Account — an OVH API token, found under Muppy ▸ Configuration ▸ OVH ▸ Cloud Providers Accounts. One account can expose several OVH projects. Muppy copies their catalog — regions, flavors, images, SSH keys — from OVH, and a commission chooses its region, flavor and image among it, in the wizard or in the agent's call. The instance trusts the Muppy key, registered in the project when absent: its private half never leaves Muppy, so every access to the instance goes through Muppy. An operator may choose another key in the wizard, a derogation the wizard states; an agent never may. The project, region, flavor, image and SSH key selected on the account's OVH tab serve that tab's Call GET and Call POST, a diagnostic tool.

In this section

  • Commission an Instance — connect an account, sync its catalog, create instances with the wizard, and manage the host lifecycle (auto-decommission and decommission).
  • Import existing instances — register OVH instances that already exist as Muppy Hosts (fetch → import → enroll).

Creating vs importing

Commission creates new instances. Import registers instances that already exist on OVH.