Consistently use bytes for memory statistics

For some reason, stat_collector assumed rss was reported in kilobytes
instead of bytes and multiplied it by 1024.  The rest of the code then
started to divide the 'used_memory_in_bytes' by 1024 to really get bytes
back.  Very odd.

This change simply removes the hacks that multiply and divide to get
expected data.
Make memory reported match cgroup usage data

The DEA was reporting 'used_memory_in_bytes' as the RSS returned from
warden.  RSS, however, is not what cgroup uses when checking container
memory limits so it's inappropriate memory statistic to report to end
users via cf stats.

The Linux cgroup implementation reports container memory usage in
memory/memory.usage_in_bytes and calculates this by adding
memory/memory.stat:cache and memory/memory.stat:rss so this change will
introduce the same logic to the DEA.  Instead of using cache and rss,
however, total_rss and total_cache will be used as it accounts for child
containers when present.
updated license and notice file
Update log messages when starting and stopping apps

[finished #63115394]

Signed-off-by: Phan Le <ple@pivotallabs.com>
Remove duplicate debugger gem entry

Signed-off-by: Maria Shaldibina <mariash@pivotallabs.com>
Remove .bundle/config

Signed-off-by: Maria Shaldibina <mariash@pivotallabs.com>
Cleanup ignore file

Signed-off-by: Maria Shaldibina <mariash@pivotallabs.com>
Re-add debugger gem and organize Gemfile

Signed-off-by: Aram Price <aprice@pivotallabs.com>
Remove unnecessary version from nokogiri gem

Signed-off-by: Aram Price <aprice@pivotallabs.com>
Ignore .bundle dir

Signed-off-by: Aram Price <aprice@pivotallabs.com>
Remove version from uuidtools gem entry

Signed-off-by: Aram Price <aprice@pivotallabs.com>
Remove version from loggregator_emitter gem entry

Signed-off-by: Aram Price <aprice@pivotallabs.com>
Merge pull request #94 from rogerluo410/master

updated license and notice file
Add rspec-fire

Signed-off-by: Phan Le <ple@pivotallabs.com>
Reorganize requires
Fix quoting
Introduce SPEC_ROOT
Use ruby 1.9 style hashes
Update container_tools gem

so that we can get output from timed-out container execution

[#61987714]

Signed-off-by: Phan Le <ple@pivotallabs.com>
Emit staging messages even when staging fails

Prior to loggregator, staging output was provided to the user by tailing
the logs generated during staging.  This pattern enabled end users to
see messages generated while staging was in-flight and included messages
related to ffailures in staging, but the newer Loggregator paths only emit
staging messages when staging completes successfully.

This change will cause staging messages to be emitted even when staging
fails but it still requires the staging task to complete.  An
investigation is needed into whether or not (and how) to emit messages
while staging is occuring as that seems like the 'correct' approach.