This Content Capsule contains CloudSlang OO flows and a Service Offering that will allow you to deploy VMs by cloning templates and user operations for Flex, Start, Stop, Suspend, Resume and Snapshot management.
The content is ready to be deployed on an on-premise instance of HCMX, as well as on an HCMX SaaS tenant. The flows have special worker group inputs that allow you to redirect the operations to an on-prem RAS instance for Proxmox vm deployments on-prem.
This content is using the Proxmox REST API to communicate with your Proxmox environment so make sure you set the Service Access Point for your Deployment Provider to the proper URL (for example https://pve.example.com:8006) and the proper access credentials (for example root@pam). Furthermore, make sure that the Proxmox server certificate and hostname are valid, or override the strict checking of it in the OO Configuration Items for this content pack.
This Content Capsule is not digitally signed and will fail to upload without adjusting some settings. In HCMX, the message you will receive this error:
Installation aborted, as the content isn't digitally trusted and only digitally trusted contents are allowed to install
To fix this, please refer to the HCMX documentation here .
Alternatively, you can unzip the capsule itself and individually import the OO content pack and the HCMX Service Design into you HCMX environement.
Suggested for you are based on app category, product compatibility, popularity, rating and newness. Some apps may not show based on entitlements. Learn more about entitlements.
This updated version of the HCMX Content Capsule for Proxmox using CloudSlang adds new OO content, Resources Offering and Service Design for deploying LXC containers in Proxmox.
The Content Capsule now supports deployment of both VMs as well as LXC containers.
This is a new HCMX Content Capsule to intergrate HCMX with the Proxmox Virtual Environment REST API. The content has been testes and working with PVE verstion 7.x
Once this capsule has been successfully deployed to your environment, create a new Proxmox resource provider. The OO content is using the Proxmox REST api to integrate into Proxmox so it is important that you enter the valid URL in the Service Access Point field of the Provider configuration, for instance https://node1.example.com:8006. You will get a warning message that the URL cannot be verified but you can safely ignore that message.
Please upgrade to one of the following broswers: Internet Explorer 11 (or greater) or the latest version of Chrome or Firefox
