Cloud Director saves time, so you can go for an extra cup of coffee 😉
Use Cases and Deployment Scope
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)
Most Important Features
- Availability and scalability
- Manageability, the organization, customers, products
- Visibility of resource usage
- Very secure, the rights are very good set. So customers do not interfere with each other
Return on Investment
- Saves a lot of time, and time is money
- Stable, so little to non downtime
- With P1 , good support


