VMware driver config validator module for driver init and CLI validation

Registered by Shawn Hartsock

This blueprint has been superseded. See the newer blueprint "Generic configuration check framework" for updated plans.

The VMware drivers (vCenter driver in particular) can fail if it is not properly configured or if vCenter is not properly setup to anticipate interacting with OpenStack. This blueprint proposes the creation of a configuration validator module that could be called from either the driver's init sequence or a command line interface.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Shawn Hartsock
Direction:
Needs approval
Assignee:
Shawn Hartsock
Definition:
Superseded
Series goal:
Proposed for icehouse
Implementation:
Unknown
Milestone target:
None
Completed by
Shawn Hartsock

Related branches

Sprints

Whiteboard

Things to check:

* check for reachable SOAP end-points before driver start
* detect properly configured Clusters in vCenter
* detect if the driver's username has the required privilege: System.View
* Automatically detect and fix WSDL ( see: https://gist.github.com/hartsock/6227311 )
* validate configuration values such as cluster names, regular expressions for datastores, etc.
* assist in creation of configurations (browse clusters, datastores, etc and place in config file)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.