Description of problem:

Existing oschecks are required pre-existing openstack configuration in order to work correctly. 

Oschecks don't work "from scratch" on a fresh openstack deployment.

----------------------------------------------------------------------------
This means that some of oschecks will report failures on a fresh openstack deployment.
----------------------------------------------------------------------------

In order to make those checks to work the following should be configured on a fresh openstack deployment:

1.flavor  named “m1.tiny”
2.external network named “public”
3.Image named “cirrus”
4.IPv4 subnet for creating floating IP
5.The cinder volume check uses an outdated api and results in the WARRNING message.



oschecks should work on fresh openstack deployment without additional configuration.