Use /sys/proc/... to get the cdrom device

I recently witnessed this while generating new stemcells. 
Sometimes udev may assign /dev/cdrom1 as a link to the underlying 
device and hence, the above change would catch this and let the agent
mount the correct device instead of failing on a non-existant /dev/cdrom
Use if_p in director template so it doesn't blow up when global_blobstore is missing
update stemcell build for 3.0 kernel

includes changes for vmtools to build for 3.0 kernel
added bosh-stemcell-vsphere 0.8.0 (test)
Add Retryable gem
vendor retryable gem
Added some tests and made changes to handle \n in the filename if any while searching for cdrom device
Merge branch 'master' of github.com:cloudfoundry/bosh

* 'master' of github.com:cloudfoundry/bosh:
  vendor retryable gem
  Add Retryable gem
move bosh_agent/misc/temcell/uild2 to the top level directory

- clean out ancient stemcell builders
fix randomly failing aws boostrap cli spec

also swap ruby-debug19 for debugger gem
Add some changes to pull request #59
No need to check if it is a block device now
Global cache key respects dependent package versions

* Moved generate_dependency_key from PackageCompiler and
  Models::CompiledPackage into CompileTask
* Moved compiled_package_cache_key to CompileTask private method
  generate_cache_key
Merge pull request #60 from cloudfoundry/cdrom-read-fix

Better CD-Rom based info checking
Added logging for uploading compiled packages to global cache
Move generate_build_number into CompiledPackage, add specs for it
add retryable functionality to Bosh::Common module

also include profiling in rspec configuration
HTTP plays well with a proxy environment

The https url causes HTTPClient to fail. 
This is an annoyance when someone behind a firewall is trying to 
perform an initial sync.
microBOSH system spec creates BAT deployment directory just when needed
enhance cpi tests for aws plugin and error message