<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi<div><br></div><div>So yes, I am expecting that some services to have to become "domain aware". Here's the problem:</div><div><br></div><div>In Folsom and before, the concept of a tenant/organization and the collection of items related to a work being run on openstack were merged together in one container (called tenant). In Grizzly we are enabling a separation (if required) for this into a Domain (that is a container that can represent the organization being hosted within an openstack implementation) and a set of projects that represent the work being done and will come and go with the lifecycle of the applications/work involved). Such a distinction is a must for any kind of enterprise. Further, there will be aspects of the openstack implmentation that a cloud provdier will want to manipualte a the group level - e.g. setting a quota for, as well as assigning some logical part of the infrastructure to, an organization (i.e. domain). In addition, an organization may want some object to be domain-wide, e.g. some standard images that all their projects can use. An example desired entity relationship might look like this:</div><div><br></div><div></div></body></html>