This patch introduces the instrumentation of redfish object's
method invocation from ``ilo.client.IloClient`` object. When
a method is invoked on client, based on the target hardware
the execution of that corresponding method bestows on RIBCL,
RIS or Redfish. Again, when the context is Redfish then there
RIBCL can remain enabled/disabled. In case of RIBCL enabled,
we fall back to RIBCL for any method invocation which is not
(yet) implemented in Redfish. For RIBCL being disabled, we
raise ``NotImplementedError``.
This also introduces a parameter in client constructor named
'use_redfish_only' which when set to True will force the use
of redfish. Default value is False.
Reviewed: https:/ /review. openstack. org/456064 /git.openstack. org/cgit/ openstack/ proliantutils/ commit/ ?id=4db1e580e28 f9b9e4a5bee9416 5816e41fa3a95a
Committed: https:/
Submitter: Jenkins
Branch: master
commit 4db1e580e28f9b9 e4a5bee94165816 e41fa3a95a
Author: Debayan Ray <email address hidden>
Date: Wed Apr 12 02:41:21 2017 -0400
Instrumenting redfish into proliantutils' client
This patch introduces the instrumentation of redfish object's IloClient` ` object. When dError` `.
method invocation from ``ilo.client.
a method is invoked on client, based on the target hardware
the execution of that corresponding method bestows on RIBCL,
RIS or Redfish. Again, when the context is Redfish then there
RIBCL can remain enabled/disabled. In case of RIBCL enabled,
we fall back to RIBCL for any method invocation which is not
(yet) implemented in Redfish. For RIBCL being disabled, we
raise ``NotImplemente
This also introduces a parameter in client constructor named redfish_ only' which when set to True will force the use
'use_
of redfish. Default value is False.
Change-Id: Iaf261a17da137a 6fa49e62d9ff2a7 cf34c97c2e3
Partial-Bug: 1646685