Cloud Director saves time, so you can go for an extra cup of coffee 😉
Use Cases and Deployment Scope
We are a cloud provider and we use Cloud director as the main entrance for our customers to access there VMware environment. From there they can do everything within there environment and go to Availability if there is a need voor a failover or migration.
As admin you can set limitations to the origination of a customer (like max CPU, memory and storage use) and set also the needed rights. Within the organization, the organization admin (de customer) can set his own set of user rights to his users.
Because the end user can do som much itself on a safe way, it safes us a lot of time and we know it secure.
Pros
- Seperate organizations (customers)
- Give end user the freedom to make new users in his own organization
- Quotes on the organization (cpu, memory, storage), set Limits so the hardware underneath will not be over asked
- The integration with Availability
- Integration with multiple cloud director sites (you can just open one site but can enter all the other sites from there too)
Cons
- Logging, there is a lot of logging but is not always clear where to look for the right logging.
- The syncing of policy, you can't see if or what he did/didn't sync and the status of it.
- More integrations with VMware product (click like Availability)
Likelihood to Recommend
If you have a lot of customers that all need to have a separate place to work in, without the possibility of getting in each other way, and you want to safe yourself a lot of work. Than I strongly recommend you Cloud director. Ofcourse, only if you have a VMware environment as your working environment.
If you just have a small group of customers and you can easily handle the work that's coming from it, then it is overkill to add cloud director to your environment. In a later station, you can always introduce cloud director (so tis never to late if you still want to use it)
