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
Upgrade Java Buildpack to v2.0.2

This change updates the Java Buildpack to v2.0.2.  This update
contains changes to ensure that failed DNS lookups cause the buildpack
to assume that there is no Internet connection.

[#67329818]
Improved the clarity of health check failure messages.

[#63057646]
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>
No longer need to create vagrant box locally

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>
Merge pull request #113 from nebhale/67329818-java-buildpack-v2.0.2

Upgrade Java Buildpack to v2.0.2
Remove system buildpacks

Remove tests associated with system buildpacks
Update #promise_stop to accept a kill flag

* this is to enable use during staging task teardown on timeout

Signed-off-by: Aram Price <aprice@pivotallabs.com>
Parenthesize all logging calls

* Also modernize hash syntax and reduce multi-line calls.

Signed-off-by: Aram Price <aprice@pivotallabs.com>
Remove staging timeout grace period

* Other post-staging operations on the container occur after the timeout,
so there should be no reason for this to differ from the staging timeout
implemented in the staging script that is run in the container.

Signed-off-by: Eric Malm <emalm@pivotallabs.com>