Proposal for capabilities

We made the argument in another context that all accounts should be orgs, and users just get a different UI experience.

----- Original Message -----
> > +## Global configuration
> > +Capabilities triggered from global configuration will consist of two
> > types:
> > +
> > +1. Features that are turned on/off for the whole openshift deployment
> > +2. Global resource constraints, ex: setting a minimum allocatable size per
> > container for a given system resource (mem / cpu / disk)
> > +
> > +## Project (namespace) level capabilities
> > +Capabilities for the project will consist of two main types:
> > +
> > +1. Features that are turned on/off for the project
> > +2. Resource constraints
> > +
> > +Resource constraints for the project will be stored on the
> > “ResourceController” associated with the namespace.  The
> > ResourceController is the same object used by the admission control
> > system, both to check allowed usage and to store actual usage.
> > +
> > +## Account level capabilities
> > +Account is a separate entity from user, many users might be associated
> > with a single account, and users will have a role on the account.
> 
> A user and an org are both accounts.  Both users and orgs and own projects.
> But you probably only want orgs to own teams.
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/openshift/origin/pull/569/files#r22045705