Since September 2018, VMware has a special Cloud Verified Logo for partners who meet specific requirements for their cloud infrastructure. As my company was the first in Switzerland to receive this logo, I would like to briefly explain what this designation means and which requirements apply.
VMware recently released the latest version 2.5 of the vCloud Architecture Toolkit for Service Providers (vCAT-SP). But I know that many service and cloud providers around the globe don’t know what that is and that something like that even exists.
I will therefore try to give a brief overview and introduction to this topic and hopefully show how powerful this toolkit can be for your business.
For high availability and performance reasons, it makes sense to run multiple vCloud Director cells. To do this, you can place a load balancer in front of it. And since we already use NSX for vCloud Director 9, it makes even more sense to use an edge gateway for load balancing.
However, there are a few pitfalls, for example with terminating HTTP connections, session persistence and especially with the VM Remote Console via the browser.
In my blog post I show you how to configure NSX and vCloud Director 9 and what to consider for this setup.
The vCloud Director API is a powerful and easy to use solution for getting information about organizations, VDCs, networking, vApps and eveything else. But that’s not all. You can use it for automate all aspects of vCloud Director, too.
You may think it’s difficult to use the vCloud Director API. But I’m trying to show how easy the usage is and what you can do with this API.
So, let’s get started.
By default, vCloud Director does not limit the size of memory, disks and number of vCPUs when creating a new virtual machine. This means the global configuration maximums for vSphere apply, which can be a problem for a service provider. Depending on the settings in the allocation model that a SP uses.