5. vCloud Resource Design : 5.2 Organizations
5.2 Organizations
Organizations are the unit of multitenancy within vCloud Director and represent a single logical security boundary. Each organization contains a collection of end users, computing resources, catalogs, and vCloud workloads. For a public vCloud, vCloud Director organizations typically represent different customers. In a private vCloud, organizations can map to different department or business units. Each department or business unit might have multiple environments, such as development and production.
Organization users can be local users or imported from an LDAP server. LDAP integration can be specific to an organization or inherit the system LDAP configuration defined by the vCloud system administrator. For information about how to configure LDAP, see the vCloud Director Installation and Upgrade Guide (http://www.vmware.com/support/pubs/vcd_pubs.html). Create a local organization administrator for each organization to mitigate loss of administrative control due to LDAP authentication or connectivity issues.
The name of the organization, specified when the organization is created, maps to a unique URL that allows access to the UI for that organization. For example, an organization named Company1 maps to https://<hostname>/cloud/org/Company1. Use a standard naming convention for organization names and avoid using special characters or spaces because they can affect the URL in undesirable ways.
Use system defaults for most of the other organization settings, with the exception of leases, quotas, and limits. There are no specific requirements called out by the service definitions for these values—set them as needed.