python 3.4 does not have a self.message, so we need to set one up
in our own base class so the conversion to string work.
Change-Id: I5d963125ccb5cc29fa0563313d229046a81ca3d0
Deprecate the following unused exceptions:
* VMwareDriverConfigurationException
* UseLinkedCloneConfigurationFault
* MissingParameter
The above exceptions are specific to VMware Nova driver and
should be moved to Nova code base.
Change-Id: I74482d6ac436fbea4383a197f24704bc3d033076
Currently VMwareDriverException is raised for unknown
VIM faults. Sometimes clients may need to handle such
faults. Therefore it is better if we throw
VimFaultException with the fault_list set to the relevant
VIM fault class name.
Change-Id: I97d93ceaa82514d029fff87f1c5ad942895d8940
There are two roots for the current exception hierarchy: VimException
and VMwareDriverException, which is not a good design. This patch
refactors the exception hierarchy to fix this problem.
Summary of changes:
* Change parent of VimException to VMwareDriverException
* Change parent of exceptions corresponding to known VIM faults
to VimException
* Change parent of VimSessionOverLoadException, VimConnectionException,
VimAttributeException and ImageTransferException to
VMwareDriverException.
The guidelines followed for this refactoring are:
* The changes in existing driver code should be NIL.
* The changes in other parts of the library should be minimal.
* Any exception raised by invocation of vim APIs should be a VimException
and any exception raised by pbm APIs should be a PbmException. But this
will result in lot of changes in the library as well as existing clients.
Therefore, we define a single root for these two types of exceptions which
is labeled as VimException.
* Any exception raised by the library should be a child of
VMwareDriverException. Therefore, VimException, VimSessionOverLoadException,
VimConnectionException, VimAttributeException and ImageTransferException
are children of VMwareDriverException. Ideally, VMwareDriverException
should be renamed as ServiceException, but it will result in backward
incompatibility.
Change-Id: Ide1bf891be78766e8670f8446792e3dc9c7ec88f
This reverts commit 1668fef9cabea6a23023aab6b97617b4368b14d6
This is a backwards incompatible change, as we see with the
nova driver code that is expecting a VMwareDriverException
but is now getting back a VimFaultException because the unit
tests in nova were passing an unknown fault class name.
Change-Id: I0f8042c6e47f6eb9802e770ffb7d09bdbe57013b
Closes-Bug: #1459021
Some API calls that depend on VMware Tools will return a
ToolsUnavailable fault such as ShutdownGuest. This patch adds the
new fault so that callers can catch this specific fault rather
than the general one.
Change-Id: Ibe132e54dd84e12d01e32528824e6db8ec785b52
Currently VMwareDriverException is raised for unknown
VIM faults. Sometimes clients may need to handle such
faults. Therefore it is better if we throw
VimFaultException with the fault_list set to the relevant
VIM fault class name.
Change-Id: I34f84f3ea3f5f0d6878f1d4438cf25bf22f293fd
vSphere APIs such as ExtendVirtualDisk_Task, CopyVirtualDisk_Task
throw NoDiskSpace fault when there is insufficient datastore
space. Currently, VMwareDriverException is thrown by oslo.vmware in
response to NoDiskSpace VIM fault. This patch adds a new exception
class corresponding to NoDiskSpace fault.
Change-Id: I50c5a93aae7fa2b5ad29951eec4d5a07e4f02045
SPBM APIs throw SecurityError on session expiry. Currently
it is unhandled which could result in session reconnection
failure. This patch fixes it.
Change-Id: Ibbd534464c73cc8afc30ba6ff29b46f9287a83c6
Move the public API out of oslo.vmware to oslo_vmware. Retain the ability
to import from the old namespace package for backwards compatibility
for this release cycle.
bp/drop-namespace-packages
Change-Id: I11cf038c3832a7357ed53363d8ccf143daddd2a2