This changeset adds support of max_instances and available_instances.  Resource manager tracks all registered instances, except those in the DELETED state.  Its could_reserve? and numbers reserverable methods responds positively when the total number of undeleted instances fall under the max_instances limit.
Recognize db2 and informix as valid databases for generation of valid DATABASE_URL
Test case for detecting db2 and informix as valid RAILS databases and converting urischeme to ibmdb
Test case for detecting db2 and informix as valid RAILS databases and converting urischeme to ibmdb
Merge pull request #111 from praveend/master

Add db2 and informix as VALID Rails relational database types
Merge pull request #85 from jackfengibm/max_instances

This changeset adds support of max_instances and available_instances.
Reflect changes in warden-test-infrastructure

Signed-off-by: Michael Fraenkel <fraenkel@us.ibm.com>
Inline scripts to run specs in warden-compatible vm

They used to be in warden-test-infrastructure, we are trying to reduce the coupling in exchange for some (temporary) duplication

Signed-off-by: Michael Fraenkel <fraenkel@us.ibm.com>
Revert "This changeset adds support of max_instances and available_instances.  Resource manager tracks all registered instances, except those in the DELETED state.  Its could_reserve? and numbers reserverable methods responds positively when the total number of undeleted instances fall under the max_instances limit."

This pull request was merged in prematurely, and since we still
have some concerns about this feature and its implementation, we've
decided to revert it for the time being. Please see additional details
on the GitHub PR discussion (https://github.com/cloudfoundry/dea_ng/pull/85).

This reverts commit c0202801f7599d47540fd62adc6f21fef4790bd4.

Signed-off-by: Michael Maximilien <maxim@us.ibm.com>
Update+remove stale info from README

Signed-off-by: Michael Fraenkel <fraenkel@us.ibm.com>
Delete unused script and references

Signed-off-by: Michael Fraenkel <fraenkel@us.ibm.com>
Stop all processes in staging script on timeout

* Ensures that child processes created by system()
calls also get killed in case of timeout error.

Signed-off-by: Kai Zhang <kaizhang@cn.ibm.com>
Add info about buildpack used to staging response.

The goal is to get information about the buildpack used for staging
(including detected admin buildpacks) back to the CC so it can be used
to populate app usage events.

Highlights:
* Add path of buildpack used for staging to staging_info.yml
* Refactor buildpack manager out of the staging workspace
  - Staging task creates and holds a reference to the buildpack manager
  - Buildpack manager passed to workspace prepare
  - Consolidated builpack ordering tests in buildpack manager
* Add methods to buildpack manager to return buildpack key or a system
  buildpack url from a path
* Return the buildpack url (system or custom) and the buildpack key in
  the staging complete message