There is already a bug to change the service setup procedures to use a "services" tenant or more realistic setup than they currently do (using one tenant for each individual service). In addition though we also need to cover the creation of a "real" tenant used for user and resource separation, probably with a realistic example. These should cover: - Creation of the tenant itself. - Creation of endpoints for the tenant. - Additional steps required to get a "realistic" deployment, may include network setup, security group setup, etc.
NB: This is not to be confused with BZ # 965943 which talks about the initial creation of tenants to facilitate basic environment setup. Here we are talking about more realistic tenants that will be created post install to restrict access to resources and administer quotas.
Moving to Icehouse, when we can plan resourcing for this.
Since this is a post-install procedure for Keystone, reassigning this to Bruce Reeler and changing the component to Admin User Guide.
In the upstream Administration User Guide, there is a section under Dashboard and another section under CLI that describe creating and managing tenants ("projects" in dashboard). These sections cover creating tenants, assigning users to tenants, deleting tenants, and managing tenant security, and setting quotas. Hence the requirements of this bug seem to be covered for 5.0.
I have confirmed that this content has been added and is now live. Closing.