More than just fixing docs - I reattached a disk!

[Dr Nic Williams]

I did some proud sysadminerification on my wordpress deployment. It has its disk reattached and mysql restarted and http://ec2-23-23-247-237.compute-1.amazonaws.com/?p=4 is back in action.

Are there any other types of resolution to add to mount_info_mismatch problem handler? http://reviews.cloudfoundry.org/#/c/5124/

Except for having to write the problem handler, the next time this happens this sysadminificationering would be a simple matter of:

$ bosh cck

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

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

$ bosh restart mysql 0

And you'd be in business. That's a nice set of tools.

Nic

---

Dr Nic Williams - VP Developer Evangelism

The Leading Platform as a Service

Office: 415 860 2185

Skype: nicwilliams

Twitter: @drnic

---