mount_info_mismatch can reattach a disk to an instance/vm

Example usage:

    $ be bin/bosh cck
    Performing cloud check...

    Scanning 3 VMs
      checking VM states (00:00:00)
      3 OK, 0 unresponsive, 0 unbound, 0 out of sync (00:00:00)
    Done                    2/2 00:00:00

    Scanning 1 persistent disks
      looking for inactive disks (00:00:00)
      0 OK, 0 inactive, 1 mount-info mismatch (00:00:00)
    Done                    2/2 00:00:00
    Scan is complete, checking if any problems found...

    Found 1 problem

    Problem 1 of 1: Inconsistent mount information:
    Record shows that disk 'vol-a8de73c7' should be mounted on i-a039a3c7.
    However it is currently :
    	Not mounted in any VM.
      1. Ignore
      2. Reattach disk to instance
    Please choose a resolution [1 - 2]: 2

    Below is the list of resolutions you've provided
    Please make sure everything is fine and confirm your changes

      1. Inconsistent mount information:
    Record shows that disk 'vol-a8de73c7' should be mounted on i-a039a3c7.
    However it is currently :
    	Not mounted in any VM
         Reattach disk to instance

    Apply resolutions? (type 'yes' to continue): yes
    Applying resolutions...

    Applying problem resolutions
      mount_info_mismatch 1: Reattach disk to instance (00:00:15)
    Done                    1/1 00:00:15
    Cloudcheck is finished

Showing that the problem is resolved:

    ~/Projects/gems/bosh/bosh/cli[mount_info_mismatch*]$ be bin/bosh cck
    Performing cloud check...

    Scanning 3 VMs
      checking VM states (00:00:00)
      3 OK, 0 unresponsive, 0 unbound, 0 out of sync (00:00:00)
    Done                    2/2 00:00:00

    Scanning 1 persistent disks
      looking for inactive disks (00:00:00)
      1 OK, 0 inactive, 0 mount-info mismatch (00:00:00)
    Done                    2/2 00:00:00
    Scan is complete, checking if any problems found...
    No problems found

Change-Id: I7570f3d023313c04682fff9fd3238ea67d8e0f33
cleaup left over stemcell generator

Change-Id: I6f9b37fe34fd89acdb07fd3903275b9850fc5fce
New BOSH blobs experience

Simplified blobs management:

- no need to sync manually, 'create release' now syncs blobs
  before trying to generate anything;

- old blobstore commands are now retired in favor of two new commands:
  'bosh add blob <local_file> [<blob_dir>]' moves blob to blobs/<blob_dir>
  'bosh upload blobs' finds and uploads new/updated blobs;

- 'bosh blobs' shows what's going on and whether there are blobs that
   need to be uploaded.

Change-Id: I019005bfb8583c087ee6427f39463ef29be4569d
Fixed 'init release --git' + 1.8 bugs

* --git was only working with base dir given;
* 1.8 CLI spec suite was failing (1 test);
* progress bar with new blobs didn't work with 1.8 (fixed by flushing
  stdout).

Change-Id: I5a6449897e0af360160d7a1bfba2e04f4fc95598
Add gemspec for aws_registry

Change-Id: I294c18a7c684a7bc382f12df1144e818a2a38c98
Make drain and stop long running tasks on the agent.

Change-Id: Iad960e1898df7547d9fbab2eb8e54fe3289f2e96
Removed a test leftover

Change-Id: I5d0d1b298de0e0081be762797eeb2e7f4e5a6bb1
Merge "mount_info_mismatch can reattach a disk to an instance/vm"
Fixed invalid constant reference to Vim:DistributedVirtualPortgroup, now references Vim::Dvs::DistributedVirtualPortgroup

Change-Id: I04edf9730bc53d9d4c341a13030ad5e314b7fdee
Merge "Add gemspec for aws_registry"
Merge "Fixed invalid constant reference to Vim:DistributedVirtualPortgroup, now references Vim::Dvs::DistributedVirtualPortgroup"
Add details to the "No available resources" exception

Change-Id: I992db5a6716b59ffc1787357f19e22499f91b65c
Generate ~/.ssh/authorized_keys before getting registry settings

This is required so the deployer can create a reverse ssh tunnel
to its embedded registry.  Once the tunnel is established, the
http_agent will talk to the embedded registry through this tunnel.

Change-Id: I3a81e5fd0da5def03514f287f5af9dd41bcb7dd7
Bypass AWS registry instance_ip check for loopback

AWS Registry requests from the http_agent (Micro BOSH) will
come from the loopback address, as the http_agent talks to the
deployer's embedded AWS registry through a reverse ssh tunnel.

Change-Id: I567ce52b270774b14ee54e22b06d94a70963036e
Merge "Removed a test leftover"
Merge "Generate ~/.ssh/authorized_keys before getting registry settings"
Merge "Bypass AWS registry instance_ip check for loopback"
AWS Micro BOSH improvements

- get bosh-release apply_spec from the agent

- Bosh::Deployer::InstanceManager plugins (aws,vsphere)

- set default logging.file regardless of logging.level

- 'bosh micro' manages a local aws registry instance

- reverse ssh tunnel gives bosh http_agent access to local registry

Change-Id: I4bad0523fb6350d91d44d59991f3765873b39d0c
Merge "Add details to the "No available resources" exception"
Merge "Make drain and stop long running tasks on the agent."