increase postpone_update interval to 30

Change-Id: I8f64330c0ade055b04c5280b34139f82669ec98a
record analysis time in varz

calculate wall clock elapsed time for analysis loop and bulk update
loop. Publish them in log messages and through varz.

Change-Id: I3269bae86ecf5579f743358dd170f3f279db3d7e
scheduler: multiple iterations per single EM tick

Change-Id: I2734f80013baa9555626964a43fae2acd21ac5c9
only get keys once when iterating over droplets

Change-Id: Ie012d1304ffa9eaa0c0a164dc7014f857c56aca8
Fix the nil values of frameworks and runtimes of HMv2 varz

Change-Id: Ic69ac8cef0fd96074e364c2a0d5646ac1f35f5c7
fix: droplet marked as STOPPED incorrectly

This patch fixes the bug when droplet.exited with reason "STOPPED" is
interpreted to mean that the application is stopped.

While it holds true in most of the cases, it does not hold true for
the case of downscaling an app to fewer instances. In this case, extra
instances are explicitly stopped by the cc.

The bug is subtle because the true application state is soon restored
using the bulk_api, so there's a short window of incorrect state,
based on which hm can make a wrong decision.

Change-Id: I3f0354bab1080f73cb1c73f25206df2071f079eb
Merge "Fix the nil values of frameworks and runtimes of HMv2 varz"
remove unnecessary interpolation

Change-Id: Ifbf027e398d010e28d402837caedf20453eebab6
use yajl everywhere

Change-Id: I90f454834f13022f2590fad98d2e4242f3ff008f
Flapping logic for missing instances

Refactor flapping logic. Reuse it for both crashed instances and
missing instances.

Change-Id: Ib2856a4bf7d5674582e47d60f2b67aa3b8ecf1ff
Merge "use yajl everywhere"
update vcap-common

source vcap-common from github, bump gem versions.

Change-Id: I44c2fd7065426fcba32d8dec13dfbf57ea0b3382
bump steno gem

Change-Id: I996ea9ef7e64d71109dcd1c9202c5ef60a687ad9
varz: missing_instances

Rename varz statistic named "down_instances" to the more appropriate
"missing_instances". This is also the name needed by dashboard app.

Improve test coverage for varz.

Change-Id: Ie42c9baac92ce4c5e72fa6b33b73e280d10f5b77
fix: do not publish expected vitals in case of error

a refactoring that cleans up the logic of releasing the varz as a step
separate from publishing. In case of error (e.g., bulk api provider
timeout), the varz that were reset to zero are no longer published for
collector to pick up.

Change-Id: Ic08c2a794504bdc5adb2def6aa65037c24d0c95c
Add Travis configuration

Change-Id: If3b5b39c048703ff30ecdebfe82aefe4e765160a
Merge pull request #1 from cloudfoundry/master

Take the latest from CF