Code change for regex filter matching

Remove REGEXP_LIKE operator for oracle db backend since it's not suitable,
Such as:
Oracle: 'select xxx from xxx where REGEXP_LIKE (column, pattern)'
Mysql: 'select xxx from xxx where column REGEXP pattern'

For the simple pattern matching(LIKE operator) used for unsupported backend db,
add '%' wildcard character on both sides of the value.

Change-Id: I4682d38086a06032bb5650a14b253f6b2b859613
Closes-Bug: #1230102
Catch volume errors during local delete

The delete code in compute/manager.py has a catch-all exception
handler for any volume related errors that occur during deletion.
This change brings the local_delete() method in compute/api.py
in line with that.

Fixes bug: 1224546

Change-Id: I399075f29d202355b28e7da1b2f1a29a66c86a4e
Host aggregate configuration throws exception

If the virtualization driver did not implement the host
aggregate support functions (add_to_aggregate,
remove_from_aggregate and undo_aggregate_operation) then an
exception is thrown when a host aggregate was created/deleted.
Configuration of the host aggregates breaks tempest tests when
the underlying driver does not have these methods implemented.

The only driver that actually uses this is the Xen driver.
The solution enables all drivers to support this without
having to add in specific code. More specifically, the compute
manager will not raise NotImplementedError.

Closes-Bug: 1229912
Closes-Bug: 1229911

Change-Id: Iee69e45d94047742b6a499a139bac96ad9dd971f
VMware: Check for the propSet attribute's existence before using

There may be cases when the call to RetrievePropertiesEx may have missing
data. That is, the propSet field may be missing. In this case the missing
field will be logged. This will help with troubleshooting the problem.

Fields may be missing due to one of the following reasons:
 - SystemError if there was some unknown problem reading the value
 - NoPermission if the logged in session did not have permission to read
   the value

The propSet attribute is marked as optional in the API documentation so this
should have been anticipated and this can be interpreted as a bug in the
client code.

http://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.wssdk.apiref.doc/vmodl.query.PropertyCollector.ObjectContent.html

Fixes bug: 1215958

Change-Id: If8fd912327e057320cd6013c276000617b9c320c
Merge "VMware: Check for the propSet attribute's existence before using"
Merge "Code change for regex filter matching"
Merge "Host aggregate configuration throws exception"
Merge "Catch volume errors during local delete"