Make error messages friendly and useful.

While at an openstack hackathon, an new user of OpenStack complained that the error messages were too cryptic since they were often just stacktraces. Each openstack project should capture all typical configuration mistakes, errors, etc., and ensure that they provide useful and friendly error messages, both at console and in the logs. E.g., indicating missing packages, missing or mis-configured network links, permission errors, etc.