Bug 992464 - Authorization token needs to raise when checking eventual consistency

Was using .first which returns nil
* Implement a membership model for OpenShift that allows an efficient query of user access based on each resource.
* Implement scope limitations that correspond to specific permissions
* Expose membership info via the REST API (disableable via config)
* Allow multiple domains per user, controlled via a configuration flag
* Support additional information per domain (application_count and gear_counts) to improve usability
* Let domains support the allowed_gear_sizes option, which limits the gear sizes available to apps in that domain
* Simplify domain update interactions - redundant validation removed, and behavior of responses differs slightly.
* Implement migration script to enable data
Ensure only users with ssh access are added with keys
New admin command to call connection hooks on an application.
Bug 995371 - Direct parameters to members were ignored

Members controller now accepts:
:members => [{:id, :role, :login}] as array of members
:member => {:id, :role, :login} as single member
:id, :role, :login => single member
Review - add comment to test
Bug 970150

Fail early during the build cycle if a Rails app name starts with a
numeral.

We should fail before we run `bundle install`, since it is completely
unnecessary if Rails can't run.

If the application is created with `--from-code`, the initial build will
fail, with error message like this:

```
Creating application '12345' ...
The initial build for the application failed: Shell command
'/sbin/runuser -s /bin/sh 80e4c0ea037a11e3962922000ab2046b -c "exec
/usr/bin/runcon 'unconfined_u:system_r:openshift_t:s0:c0,c502' /bin/sh
-c \"gear
postreceive >> /tmp/initial-build.log 2>&1\""' returned an error. rc=255

.Last 10 kB of build output:
Stopping Ruby cart
httpd (no pid file) not running
Invalid Rails application name. Please delete this applicatin and
re-create it with a name which does not start with numbers
An error occurred executing 'gear postreceive' (exit code: 1)
Error message: Failed to execute: 'control pre-build' for
/var/lib/openshift/80e4c0ea037a11e3962922000ab2046b/ruby

For more details about the problem, try running the command again with
the '--trace' option.
```

If the application is created from a template Rack app, and updated via
`git pull -s recursive -X theirs`, the build will fail on the first
push:

```
remote: Stopping Ruby cart
remote: Waiting for stop to finish
remote: CLIENT_ERROR: Invalid Rails application name. Please delete this applicatin and re-create it with a name which does not start with
numbers
remote: An error occurred executing 'gear postreceive' (exit code: 1)
remote: Error message: Failed to execute: 'control pre-build' for /var/lib/openshift/520924b77b2a19115a000001/ruby
remote:
remote: For more details about the problem, try running the command again with the '--trace' option.
To ssh://520924b77b2a19115a000001@12345-fooooooooooo.dev.rhcloud.com/~/git/12345.git/
   9b5a31d..398f08a  master -> master
```
oo-diagnostics: test_node_containerization_plugin

Add the test_node_containerization_plugin test to ensure that
OPENSHIFT_NODE_PLUGINS in /etc/openshift/node.conf does not include
unix_user_observer.
Bug 980820 - Ensure bogus PATH doesn't stop cartridge operations

* Missed setup/install calls
Use marker_present for conformity
Merge pull request #3331 from BanzaiMan/dev/hasari/bz970150

Merged by openshift-bot
Bug 994922

Warn user of supervisor control when we detect 'hot_deploy' marker.

When the hot_deploy marker is present, stop nor start is invoked, so
we need to check the presence of the marker in a different way.

Notice that the first time we push 'hot_deploy' marker, the stop cycle
will not warn that it detected the marker (because it doesn't exist on
the gear).
Merge pull request #3332 from jwhonce/bug/980820

Merged by openshift-bot
oo-accept-node: Simplify find_ext_net_dev

The node runtime simply defaults to eth0 if EXTERNAL_ETH_DEV is not set,
so make oo-accept-node do the same for consistency.
oo-accept-node: Use OpenShift::Config

Use OpenShift::Config to load and parse node.conf and resource_limits.conf
for consistency with the node runtime.

Use OpenShift::Config::NODE_CONF_FILE instead of defining NODE_CONF_FILE in
oo-accept-node.

Use the new globals $CONF and $RESOURCE_LIMITS instead of ENV for storing
the settings read from node.conf and resource_limits.conf.
Node Platform - Update oo-get-quota for new interface
Review comments

* Display and test a unique error if app create gear sizes is empty
* Continue running deprecated jobs in Domain
Merge remote-tracking branch 'origin/master' into origin_ui_73_membership_model
Merge pull request #3338 from jwhonce/wip/quota_check

Merged by openshift-bot
Default to membership off in development mode