Public VCF as-a-Service - Technical capabilities and limitations
Requirements
Before getting started, review the following guides to better understand Public VCF as-a-Service:
- Public VCF as-a-Service - Fundamental Concepts
- Public VCF as-a-Service - Network Concepts
- Public VCF as-a-Service - Creating a new virtual machine
- Public VCF as-a-Service - Creating network components
Instructions
General limitations
NOTE: At this time, Public VCF as-a-Service Advanced is not available in the US.
NOTE: When creating a snapshot that includes the VM's memory, storage usage can quickly add up. For example, if you have 1 VM with 1 GB of RAM and a 10 GB disk, and you create a snapshot that includes memory, your storage usage will be: 10 GB (disk) + 1 GB (VM swap) + up to 10 GB (disk snapshot) + 1 GB (memory snapshot) = 22 GB total.
Hardware limitations
Limitations of integration with external applications
Backup Solution
With Public VCF as-a-Service, you cannot use a backup tool other than our managed Veeam for VCD tool. Refer to the following guide for more information: Public VCF as-a-Service - Backup with Veeam Data Platform.
VMware API
Third-party products relying on vSphere APIs to function (such as Nakivo, Rubrik, Zerto, etc.) are currently not usable within the Public VCF as-a-Service product.
Certifications
At the launch of the service, no specific certification will apply to Public VCF as-a-Service by OVHcloud.
Go further
Browse all the Public VCF as-a-Service guides.
Browse the rest of the OVHcloud US documentation for guides on our other products and services.
Learn more about Hosted Private Cloud on the OVHcloud US website.
If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link to get a quote and ask our Professional Services experts for a custom analysis of your project.