<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi<div><br></div><div>I have been working, with others, on a set of blueprints (some already discussed on this list) that enhance the definition and use of domains to make Openstack more successful and acceptable to enterprise customers (both when being hosted by a openstack-based cloud provider as well as for private clouds). I would welcome comments/suggestions:</div><div><br></div><div><b>Optional private name spaces for domains</b>. The initial draft of this proposal has been discussed here before, but I have now added details of the proposed changes : <a href="https://blueprints.launchpad.net/keystone/+spec/domain-name-spaces">https://blueprints.launchpad.net/keystone/+spec/domain-name-spaces</a></div><div><br></div><div><b>Token scoping to a domain</b>. More easily enabling the operation of domain-wide admin roles: <a href="https://blueprints.launchpad.net/keystone/+spec/domain-scoping">https://blueprints.launchpad.net/keystone/+spec/domain-scoping</a></div><div><br></div><div><b>Domain role assignment.</b> Providing more flexibility in terms of what the current functionality means to assign a role to a user-domain pair: <a href="https://blueprints.launchpad.net/keystone/+spec/domain-role-assignment">https://blueprints.launchpad.net/keystone/+spec/domain-role-assignment</a></div><div><br></div><div>Henry</div></body></html>