Frequently asked questions about Colt Private Cloud on VMware Cloud Foundation

You should have familiarity with the VMware Cloud Director web client.

With just a minimal amount of familiarity with VMware Cloud Director, you'll be able to scale environments up and down, provision firewall rules, manage your virtual load balancers, copy entire environments for migration or replication, set up NAT, provision site-to-site or client-to-site VPNs, do SSL offloading, mount CD ROM drives, reboot, and much more.

A catalog is a container for vApp templates and media files in an organization. Organization administrators and catalog authors can create catalogs in an organization. Catalog contents can be shared with other users in the organization and can also be published to all organizations in the VMware Cloud Director installation.

You can start with your own templates, which you can upload in the catalog and deploy as you like, or you can use the base templates that we will provide.

Yes, you can assign different privileges and control access to different catalogs on a user-by-user basis.

Migrations leverage VMware Cloud Director, where you configure your VMware environment to point to your Colt Private Cloud on VMware Cloud Foundation endpoint, and then move workloads from the target to the destination environment.

Like any private cloud, it will take 6–8 weeks to stand-up your Colt Private Cloud on VMware Cloud Foundation stack. But once in place, you can deploy VMs virtually instantly.

You can easily add a Colt Private Cloud on VMware Cloud Foundation Provider within Cloud Application Manager. Once that is done, you can orchestrate the deployment and management of compute.

No, this is a bundled product with VMware licenses included. If you prefer to bring your own licenses, we recommend Foundation Hosting as an option.

No, we manage that for you.

The minimum node configuration to support vSAN is three nodes. We add a fourth node so we can offer "N-plus-2" high availability. That means we can support two of the base-4 nodes failing and still keep the system up and running.

vSAN is limited to a maximum of 64 nodes within a single cluster. However, you can have multiple clusters managed by a single vCenter. You'll just interconnect them with the switching fabric to make one happy family.