Remove 'new' php spec.

Test plan:
- Unit tests pass

Change-Id: I39de235f9fdbebe42fcc2e6b62bc75e40d37eb00
Move php_spec from cc into staging gem

Test plan:
- Unit tests pass

Change-Id: Ib431bef894e28ba86c962a40927fc51a0f75baef
Java submodule reference update.
The latest change in the way we generate our Tomcat bits adds a sha1
fingerprint that is used in unit tests to ensure that the bits have not
been modified out-of-band. The sha1 fingerprint is saved in the vcap-java
tree. The java submodule in vcap needs to be bumped up to this latest change
to allow the unit tests to do the right thing.

Change-Id: I2263e8aa647ea28d79279e5da01494e1026984b3
Merge "Remove 'new' php spec."
Merge "Move php_spec from cc into staging gem"
Merge "Java submodule reference update. The latest change in the way we generate our Tomcat bits adds a sha1 fingerprint that is used in unit tests to ensure that the bits have not been modified out-of-band. The sha1 fingerprint is saved in the vcap-java tree. The java submodule in vcap needs to be bumped up to this latest change to allow the unit tests to do the right thing."
Final stager changes

- Rewrite stager to use NATS queue groups instead of Resque.
- Add support for staging uploads to nginx config
- Integrate CC with stager
- Add support to bin/vcap for controlling stager/redis instance

Test plan:
* Ran BVTs locally with and w/out the new stager, and with and w/out nginx support.
* Ran BVTs against my deployment with and without the new stager.
* Ran unit tests for stager and CC.

Change-Id: I3c85d7de58f518d6111ca3dbf6c55fc532350d9d
Set app state to STOPPED on staging failure

This keeps the new stager behavior in line with the old staging behavior.
We explicitly stop the app, instead of starting a single broken instance and
relying on the HM flapping logic to kick in.

Test plan:
- BVTs pass locally
- BVTs pass on deployment

Change-Id: I715d5ef6df3ddb027baa6dad4437d207cf9f8777
Fix typo

Exercise for the reader:
- How was the existing code syntactically valid?
- What did it evaluate to?

Test plan:
- BVTs pass locally
- BVTs pass on my deployment

Change-Id: Ic665a42715a543ad0481b6c82e33a74ae3caceb0
Include staging.log if it exists, abort staging plugin if gem install fails

Previously, staging would succeed even if gem installs failed. This aborts
the staging plugin if a gem install fails.

Test plan:
- Unit tests
- BVTs locally
- BVTs on my deployment

Change-Id: Ibbe96f4989ca004f048257e7cb3c2819e3163f70
Add basic varz stats

This adds counts for the number of pending tasks (tasks waiting to be processed)
as well as the number of active tasks (tasks currently running).

Test plan:
- New unit test
- Pushed N apps in parallel, watched varz counts

Change-Id: Iadc991528a97f9d50a544ab8f05b6efff8a533bc
Enable turning new stager on by email

Adds support for enabling new stager use by user email as well as by
percent.

Test plan:
- New unit test
- Enabled for my email addr, verified that I was using the new stager.
  Ran BVTs, verified they were not using the new stager.
- Ran BVTs on my deployment

Change-Id: I4c1e55c1d7fb33e608a0626db34c4b49695fa147
Strike 3 ..
Revert tomcat.zip change that introduced a digest in the archive (and the
corresponding BVT addition) in preference to a more effective unit test
described below. Also fix an incomplete test description.
We now save a SHA1 digest of the tomcat.zip resulting from running the update /
upgrade script (see vcap-java/tomcat-setup) and use a unit test (included in
this change) to verify that the SHA1 digest of the 'tomcat.zip' used by the
CloudController matches the saved SHA1 thus helping us prevent out-of-band
(to the update script) updates to the tomcat.zip used by the CloudController.
Updated to include this change in the new staging gem.
Before this change can be actually merged, an update to the 'java' submodule
reference is needed. That will be part of a different commit. (This is now done)
- Included in the new staging gem.
- Updated vcap_staging gem in vendor cache in 'stager'

Change-Id: I4006c1d04dc307a7b4c17362b565de93aa4971f9
Merge branch 'cc_stager_integration'

Conflicts:
	cloud_controller/Gemfile.lock
	cloud_controller/config/cloud_controller.yml
	cloud_controller/vendor/cache/vcap_staging-0.1.0.gem
	cloud_controller/vendor/cache/vcap_staging-0.1.4.gem
	stager/Gemfile.lock
	stager/vendor/cache/vcap_staging-0.1.0.gem
	stager/vendor/cache/vcap_staging-0.1.3.gem
	stager/vendor/cache/vcap_staging-0.1.4.gem
	staging/Rakefile
	staging/lib/vcap/staging/version.rb
	staging/vcap_staging-0.1.3.gem

Change-Id: Ia5ff28b9c349210ddb3fb86eb9506beebbdd4954
Modify staging to include mysql or postgres driver only if the app has bound
the associated service instance.
Unit tests to verify this behavior.

Change-Id: Id9c209835d7afe5364f55ca8c027c83bcba629e9
Spring 3.1 Environment support

Installs the CloudApplicationContextInitializer into Spring applications.

May cause backwards compatibility issues with Spring 3.1.0.M2 applications
that assume the default profile will be active at runtime as that profile will
no longer be active.  This is expected to be a very small minority of
applications.

Change-Id: I9b00e7d0ef5f9b39edea6146e56bea435e346f5a
add atmos gateway support

Change-Id: I317fcf06e3d6df1147aa431bb48e45c9c4db60f1
Clean up staging of Java based frameworks.
- Updates specific to a framework are in the associated plugin
- Update patterns common to two or more frameworks are in the common Tomcat class
- Each framework plugin now has a driver for all of the staging updates it needs
- Enable Lift staging unit tests that were marked 'pending' on account of
unexpected staging updates that have now been fixed.

Change-Id: Ia1edcc0c9e4460b4d49ae90792d3f39d9c3ed2ad
Add neo4j support + Misc changes

Change-Id: Ib81996a84b0283fd6afc7bb0109d12c620bbcce8

- Add neo4j support
- Save the last deployment in a deployment target file under $HOME
- Change service name i.e. make mysql => mysql_node etc
- Point out the profile file at the end of a deployment, has paths to run vmc
- Audit admin list
- Remove some packages from essentials list
- Increase timeout in bin/vcap that checks if a component is started

patch 3 - Fixed olegs comments.

Testing Done:
   Ran Neo4j feature bvt test
   Ran single host deployment
   Ran multi host mongodb deployment

Change-Id: Id96757bfe109af2f89b9a25e35a669a41c2d259c
Update tests submodule

Change-Id: I70faa6792ca03d255348b7fbb25f7425a9ee4be5