cloudesire documentation

cloudesire documentation

  • Docs
  • API
  • Syndication
  • Glossary
  • Back to cloudesire.com

›Available Integrations

Platform

  • Home
  • Platform modules
  • Glossary
  • Users and permissions
  • Billing
  • Event notification
  • Channel management
  • Live reporting
  • Orders approval workflow
  • Vendors approval workflow
  • Customer Cloud Credentials
  • Cloud providers
  • Email automation
  • Marketplace customization
  • Integrations
  • Tech Radar
  • Open Source
  • GDPR Compliance

Products Onboarding

  • Onboarding a new product
  • Product types

    • Syndicated applications
    • Cloud Services
    • Virtual-Machines
    • Services
  • Pricing Plans
  • Pricing models
  • Extra Resources
  • Order validation
  • External configuration parameter values

Available Integrations

  • vCloud VDC
  • OpenStack VDC
  • OKD projects
  • Commvault tenants
  • vCloud Availability tenants
  • Public Cloud Tenants
  • Kubernetes as a service
  • Helm charts
  • Google Workspace
  • Microsoft CSP
  • API as a Service
  • Keycloak

API

  • REST API Introduction
  • Java Client
  • TypeScript Client
  • PHP Client
  • API Reference
Edit

Selling and provisioning of VMware vCloud Director tenants

Cloudesire platform enables selling of vCloud director tenants via a native API integration.

A special product on the marketplace is available for purchase that automatically provisions a VDC organization with admin access.

To achieve this, administrator credentials of a vCloud Director platform is necessary to be able to dynamically create new VDCs.

Both prepaid and pay-as-you-go pricing models are supported.

Switching between different pricing models on an active subscription is not yet supported.

Prepaid pricing model

In prepaid plans, customer selects how many CPU cores, GB of memory, GB of disk space and IP addresses he wants to buy. In this case, project quotas are automatically setup to ensure that the customer will not acquire too many resources.

Pay-as-you-go pricing model

In pay-as-you-go plans, customer is billed at the end of the billing period by using the automatically gathered metrics for each of the billed resources (CPU cores, GB of memory, GB of disk space). IP address needs to be bought as a prepaid extra resources to be available inside the VDC network.

Last updated by Matteo Giordano
← External configuration parameter valuesOpenStack VDC →
  • Prepaid pricing model
  • Pay-as-you-go pricing model
Pages
Documentation IndexAPI ReferencePlatform modulesOpen SourceCorporate website
Social
TwitterFacebookGitHub
Copyright © 2025 Cloudesire.com by Engineering D.HUB