| copyright |
|
||
|---|---|---|---|
| lastupdated | 2026-02-12 | ||
| keywords | vmware, vSphere, hypervisor,{{site.data.keyword.BluSoftlayer_full}}, {{site.data.keyword.cloud_notm}}, {{site.data.keyword.baremetal_short}}, | ||
| subcollection | vmware |
{{site.data.keyword.attribute-definition-list}}
{: #about-vmware}
YOu can use {{site.data.keyword.BluSoftlayer_full}} to provision dedicated {{site.data.keyword.baremetal_short}} upon which you can deploy your own VMware based private cloud. For example, you can create a hybrid cloud where on-premises VMware-based servers, tools, and processes can be extended into the public cloud. {: shortdesc}
vSphere workloads and catalogs can be provisioned onto VMware vSphere environments within {{site.data.keyword.cloud_notm}} data centers without modification to VMware VMs or guests. The use of a common vSphere hypervisor and management or orchestration platform makes these deployments possible. vSphere implementations also enable the use of other components of the VMware vCloud Suite – vSphere, vRealize, vSAN, Site Recovery Manager (SRM), and NSX.
The core objective of VMware and {{site.data.keyword.cloud_notm}} is to assist vSphere administrators to deploy VMware vSphere environments within an {{site.data.keyword.cloud_notm}} infrastructure. VMware administrators can use bare metal instances and network, storage, and backup and recovery constructs in a self-service manner. These constructs can then be used to deploy fully functional vSphere implementations, which can be built to extend or replace on-premises vSphere implementations.
For more information about administering vSphere, see
- VMware Education{: external}
- VMware vSphere documentation{: external}.