Quantcast

Python binding: fail to generate correct request of invoke method with EndPointReference

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Python binding: fail to generate correct request of invoke method with EndPointReference

Tan, Lin
Hi,

I am trying to invoke method with a cimReference but fail to generate correct Request.

0. Here is my code:
import pywsman

ComputerSystem = ('http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem')
PowerManagementService = ('http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService')

client = pywsman.Client('30.168.98.10', 16992, '/wsman', 'http', 'admin', 'Cloud12345^')

system_epr = pywsman.EndPointReference(ComputerSystem, None)
system_epr.add_selector('Name', 'ManagedSystem')

method = 'RequestPowerStateChange'

options = pywsman.ClientOptions()
options.add_selector('Name', 'Intel(r) AMT Power Management Service')

options.add_property('PowerState', '5')
options.add_property('ManagedElement', system_epr.to_xml())

options.set_dump_request()

doc = client.invoke(options, PowerManagementService, method, None)
print doc

1. The request I generate:
<?xml version="1.0"?>
<s:Envelope xmlns:s=http://www.w3.org/2003/05/soap-envelope xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd"xmlns:n1="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService">
  <s:Header>
    <wsa:Actions:mustUnderstand="true">http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService/RequestPowerStateChange</wsa:Action>
    <wsa:To s:mustUnderstand="true">http://30.168.98.10:16992/wsman</wsa:To>
    <wsman:ResourceURIs:mustUnderstand="true">http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService</wsman:ResourceURI>
    <wsa:MessageID s:mustUnderstand="true">uuid:8688f9a8-0886-1886-8002-687c3c671e00</wsa:MessageID>
    <wsa:ReplyTo>
      <wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
    </wsa:ReplyTo>
  </s:Header>
  <s:Body>
    <n1:RequestPowerStateChange_INPUT>
      <n1:PowerState>5</n1:PowerState>
      <n1:ManagedElement> /cim-schema/2/CIM_PowerManagementService </n1:ManagedElement>
    </n1:RequestPowerStateChange_INPUT>
  </s:Body>
</s:Envelope>

It looks like there are some serious problems with ManagedElement, it should be CIM_ComputerSystem at least.


2. I print system_epr.to_xml() before invoke method:
<?xml version="1.0"?>
<wsa:EndpointReference xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd">
  <wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
  <wsa:ReferenceParameters>
    <wsman:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem</wsman:ResourceURI>
    <wsman:SelectorSet>
      <wsman:Selector Name="Name">ManagedSystem</wsman:Selector>
    </wsman:SelectorSet>
  </wsa:ReferenceParameters>
</wsa:EndpointReference>

And then RequestPowerStateChange_ INPUT will be:
<n1:RequestPowerStateChange_INPUT>
        <n1:PowerState>5</n1:PowerState>
        <n1:ManagedElement/>
</n1:RequestPowerStateChange_INPUT>


3. I use system_epr.string() instead, get RequestPowerStateChange_ INPUT:
<n1:RequestPowerStateChange_INPUT>
        <n1:PowerState>5</n1:PowerState>
        <n1:ManagedElement>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem?Name=ManagedSystem</n1:ManagedElement>
</n1:RequestPowerStateChange_INPUT>:

It looks better but still failed for the same reason:
The supplied SOAP violates the corresponding XML schema definition

4. My environment:
Ubuntu 14,04
Swig2.0
Python2.7


It's a bit longer for my question.
Do you have any ideas about where did I wrong?
The options or something else?

Best Regards,

Tan


------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Python binding: fail to generate correct request of invoke method with EndPointReference

Klaus Kaempf
* Tan, Lin <[hidden email]> [Nov 23. 2014 12:15]:
>
> options.add_property('PowerState', '5')
> options.add_property('ManagedElement', system_epr.to_xml())
                                                   ^^^^^^^^^

The call to 'to_xml()' is wrong. It converts the EndpointReference to
an xml representation as string. Thus you are passing a string value
(instead of an EndpointReference value) to ManagedElement.

Drop the .to_xml() call, just use
  options.add_property('ManagedElement', system_epr)

Also note that passing EndpointReferences via invoke() was added in
Openwsman 2.4.10, you need at least this version.


Hth,

Klaus
--
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
Maxfeldstraße 5, 90409 Nürnberg, Germany

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Python binding: fail to generate correct request of invoke method with EndPointReference

Tan, Lin
Thanks, I use 2.4.3 from Ubuntu repo.
That's the problem.
I will have a try on 2.4.10

Tan

-----Original Message-----
From: Klaus Kaempf [mailto:[hidden email]]
Sent: Tuesday, November 25, 2014 8:05 PM
To: Tan, Lin
Cc: [hidden email]
Subject: Re: [Openwsman-devel] Python binding: fail to generate correct request of invoke method with EndPointReference

* Tan, Lin <[hidden email]> [Nov 23. 2014 12:15]:
>
> options.add_property('PowerState', '5')
> options.add_property('ManagedElement', system_epr.to_xml())
                                                   ^^^^^^^^^

The call to 'to_xml()' is wrong. It converts the EndpointReference to an xml representation as string. Thus you are passing a string value (instead of an EndpointReference value) to ManagedElement.

Drop the .to_xml() call, just use
  options.add_property('ManagedElement', system_epr)

Also note that passing EndpointReferences via invoke() was added in Openwsman 2.4.10, you need at least this version.


Hth,

Klaus
--
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Python binding: fail to generate correct request of invoke method with EndPointReference

Tan, Lin
Hi Kaempf,

I can add EndPointReference into invoke method.
But I get a new problem with the sequence of property.

Here is my code:
options.add_property('PowerState', '5')
options.add_property('ManagedElement', system_epr)

According to CIM_PowerManagementService,
PowerState should be before ManagedElement.
But I get request like:
<n1:RequestPowerStateChange_INPUT>
      <n1:ManagedElement> Correct references </n1:ManagedElement>
      <n1:PowerState>5</n1:PowerState>
</n1:RequestPowerStateChange_INPUT>
So it violates the schema again.
How should I do?

My environment:
Fedora 20.
Packages from your openwsman repo:
Openwsman 2.4.12
Swig 3.0
Sblim-sfcc 2.27

Best Regards,

Tan
-----Original Message-----
From: Tan, Lin [mailto:[hidden email]]
Sent: Tuesday, November 25, 2014 8:33 PM
To: Klaus Kaempf
Cc: [hidden email]
Subject: Re: [Openwsman-devel] Python binding: fail to generate correct request of invoke method with EndPointReference

Thanks, I use 2.4.3 from Ubuntu repo.
That's the problem.
I will have a try on 2.4.10

Tan

-----Original Message-----
From: Klaus Kaempf [mailto:[hidden email]]
Sent: Tuesday, November 25, 2014 8:05 PM
To: Tan, Lin
Cc: [hidden email]
Subject: Re: [Openwsman-devel] Python binding: fail to generate correct request of invoke method with EndPointReference

* Tan, Lin <[hidden email]> [Nov 23. 2014 12:15]:
>
> options.add_property('PowerState', '5')
> options.add_property('ManagedElement', system_epr.to_xml())
                                                   ^^^^^^^^^

The call to 'to_xml()' is wrong. It converts the EndpointReference to an xml representation as string. Thus you are passing a string value (instead of an EndpointReference value) to ManagedElement.

Drop the .to_xml() call, just use
  options.add_property('ManagedElement', system_epr)

Also note that passing EndpointReferences via invoke() was added in Openwsman 2.4.10, you need at least this version.


Hth,

Klaus
--
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Python binding: fail to generate correct request of invoke method with EndPointReference

Klaus Kaempf
* Tan, Lin <[hidden email]> [Nov 26. 2014 06:43]:

> Hi Kaempf,
>
> I can add EndPointReference into invoke method.
> But I get a new problem with the sequence of property.
>
> Here is my code:
> options.add_property('PowerState', '5')
> options.add_property('ManagedElement', system_epr)
>
> According to CIM_PowerManagementService,
> PowerState should be before ManagedElement.
> But I get request like:
> <n1:RequestPowerStateChange_INPUT>
>       <n1:ManagedElement> Correct references </n1:ManagedElement>
>       <n1:PowerState>5</n1:PowerState>
> </n1:RequestPowerStateChange_INPUT>
> So it violates the schema again.

This looks fine. Order of elements within
<n1:RequestPowerStateChange_INPUT> shouldn't matter, since elements
are parsed by name, not by position.

If you still get an error response, please show it to me.


Klaus
--
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
Maxfeldstraße 5, 90409 Nürnberg, Germany

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Python binding: fail to generate correct request of invoke method with EndPointReference

Tan, Lin
Hi Kaempf,

I am not familiar with XML Schema.
But I think this the problem.
I can prove with wsmancli using two xml files, the only difference is the sequence.

(1)
wsman invoke -a RequestPowerStateChange http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService?Name='Intel(r) AMT Power Management Service' -h 30.168.98.10 -P 16992 -u admin -p Cloud12345^ -J power_on.xml

<?xml version="1.0" encoding="UTF-8"?>
<a:Envelope xmlns:a="http://www.w3.org/2003/05/soap-envelope" xmlns:b="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:c="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" xmlns:d="http://schemas.xmlsoap.org/ws/2005/02/trust" xmlns:e="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:f="http://schemas.dmtf.org/wbem/wsman/1/cimbinding.xsd" xmlns:g="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <a:Header>
    <b:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</b:To>
    <b:RelatesTo>uuid:17c0660c-08c1-18c1-8002-687c3c671e00</b:RelatesTo>
    <b:Action a:mustUnderstand="true">http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService/RequestPowerStateChangeResponse</b:Action>
    <b:MessageID>uuid:00000000-8086-8086-8086-000000000012</b:MessageID>
    <c:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService</c:ResourceURI>
  </a:Header>
  <a:Body>
    <g:RequestPowerStateChange_OUTPUT>
      <g:ReturnValue>0</g:ReturnValue>
    </g:RequestPowerStateChange_OUTPUT>
  </a:Body>
</a:Envelope>

Power_on.xml:
<p:RequestPowerStateChange_INPUT xmlns:p="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService">
  <p:PowerState>2</p:PowerState>
  <p:ManagedElement>
   <a:Address xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a:Address>
   <a:ReferenceParameters xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd">
    <w:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem</w:ResourceURI>
    <w:SelectorSet>
     <w:Selector Name="Name">ManagedSystem</w:Selector>
    </w:SelectorSet>
   </a:ReferenceParameters>
  </p:ManagedElement>
 </p:RequestPowerStateChange_INPUT>

(2)
wsman invoke -a RequestPowerStateChange http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService?Name='Intel(r) AMT Power Management Service' -h 30.168.98.10 -P 16992 -u admin -p Cloud12345^ -J power_on2.xml

<?xml version="1.0" encoding="UTF-8"?>
<a:Envelope xmlns:g="http://schemas.dmtf.org/wbem/wsman/1/cimbinding.xsd" xmlns:f="http://schemas.xmlsoap.org/ws/2004/08/eventing" xmlns:e="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" xmlns:d="http://schemas.xmlsoap.org/ws/2004/09/transfer" xmlns:c="http://schemas.xmlsoap.org/ws/2004/09/enumeration" xmlns:b="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:a="http://www.w3.org/2003/05/soap-envelope" xmlns:h="http://schemas.xmlsoap.org/ws/2005/02/trust" xmlns:i="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <a:Header>
    <b:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</b:To>
    <b:RelatesTo>uuid:23c431ef-08c1-18c1-8002-687c3c671e00</b:RelatesTo>
    <b:Action a:mustUnderstand="true">http://schemas.dmtf.org/wbem/wsman/1/wsman/fault</b:Action>
    <b:MessageID>uuid:00000000-8086-8086-8086-000000000017</b:MessageID>
  </a:Header>
  <a:Body>
    <a:Fault>
      <a:Code>
        <a:Value>a:Sender</a:Value>
        <a:Subcode>
          <a:Value>e:SchemaValidationError</a:Value>
        </a:Subcode>
      </a:Code>
      <a:Reason>
        <a:Text xml:lang="en-US">The supplied SOAP violates the corresponding XML schema definition.</a:Text>
      </a:Reason>
      <a:Detail/>
    </a:Fault>
  </a:Body>
</a:Envelope>

Power_on2.xml
<p:RequestPowerStateChange_INPUT xmlns:p="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService">
  <p:ManagedElement>
   <a:Address xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a:Address>
   <a:ReferenceParameters xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd">
    <w:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem</w:ResourceURI>
    <w:SelectorSet>
     <w:Selector Name="Name">ManagedSystem</w:Selector>
    </w:SelectorSet>
   </a:ReferenceParameters>
  </p:ManagedElement>
  <p:PowerState>2</p:PowerState>
 </p:RequestPowerStateChange_INPUT>

B.R

Tan

-----Original Message-----
From: Klaus Kaempf [mailto:[hidden email]]
Sent: Wednesday, November 26, 2014 4:08 PM
To: Tan, Lin
Cc: [hidden email]
Subject: Re: [Openwsman-devel] Python binding: fail to generate correct request of invoke method with EndPointReference

* Tan, Lin <[hidden email]> [Nov 26. 2014 06:43]:

> Hi Kaempf,
>
> I can add EndPointReference into invoke method.
> But I get a new problem with the sequence of property.
>
> Here is my code:
> options.add_property('PowerState', '5')
> options.add_property('ManagedElement', system_epr)
>
> According to CIM_PowerManagementService, PowerState should be before
> ManagedElement.
> But I get request like:
> <n1:RequestPowerStateChange_INPUT>
>       <n1:ManagedElement> Correct references </n1:ManagedElement>
>       <n1:PowerState>5</n1:PowerState>
> </n1:RequestPowerStateChange_INPUT>
> So it violates the schema again.

This looks fine. Order of elements within <n1:RequestPowerStateChange_INPUT> shouldn't matter, since elements are parsed by name, not by position.

If you still get an error response, please show it to me.


Klaus
--
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Python binding: fail to generate correct request of invoke method with EndPointReference

Johnny Hwang
Wow sounds like the provider is breaking the standard ... It should not rely on ordering. That will break clients for all common information models, from DMTF downwards.

Sent from my HTC

----- Reply message -----
From: "Tan, Lin" <[hidden email]>
To: "Klaus Kaempf" <[hidden email]>
Cc: "[hidden email]" <[hidden email]>
Subject: [Openwsman-devel] Python binding: fail to generate correct request of invoke method with EndPointReference
Date: Wed, Nov 26, 2014 12:36 AM

Hi Kaempf,

I am not familiar with XML Schema.
But I think this the problem.
I can prove with wsmancli using two xml files, the only difference is the sequence.

(1)
wsman invoke -a RequestPowerStateChange http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService?Name='Intel(r) AMT Power Management Service' -h 30.168.98.10 -P 16992 -u admin -p Cloud12345^ -J power_on.xml

<?xml version="1.0" encoding="UTF-8"?>
<a:Envelope xmlns:a="http://www.w3.org/2003/05/soap-envelope" xmlns:b="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:c="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" xmlns:d="http://schemas.xmlsoap.org/ws/2005/02/trust" xmlns:e="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:f="http://schemas.dmtf.org/wbem/wsman/1/cimbinding.xsd" xmlns:g="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <a:Header>
    <b:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</b:To>
    <b:RelatesTo>uuid:17c0660c-08c1-18c1-8002-687c3c671e00</b:RelatesTo>
    <b:Action a:mustUnderstand="true">http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService/RequestPowerStateChangeResponse</b:Action>
    <b:MessageID>uuid:00000000-8086-8086-8086-000000000012</b:MessageID>
    <c:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService</c:ResourceURI>
  </a:Header>
  <a:Body>
    <g:RequestPowerStateChange_OUTPUT>
      <g:ReturnValue>0</g:ReturnValue>
    </g:RequestPowerStateChange_OUTPUT>
  </a:Body>
</a:Envelope>

Power_on.xml:
<p:RequestPowerStateChange_INPUT xmlns:p="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService">
  <p:PowerState>2</p:PowerState>
  <p:ManagedElement>
   <a:Address xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a:Address>
   <a:ReferenceParameters xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd">
    <w:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem</w:ResourceURI>
    <w:SelectorSet>
     <w:Selector Name="Name">ManagedSystem</w:Selector>
    </w:SelectorSet>
   </a:ReferenceParameters>
  </p:ManagedElement>
 </p:RequestPowerStateChange_INPUT>

(2)
wsman invoke -a RequestPowerStateChange http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService?Name='Intel(r) AMT Power Management Service' -h 30.168.98.10 -P 16992 -u admin -p Cloud12345^ -J power_on2.xml

<?xml version="1.0" encoding="UTF-8"?>
<a:Envelope xmlns:g="http://schemas.dmtf.org/wbem/wsman/1/cimbinding.xsd" xmlns:f="http://schemas.xmlsoap.org/ws/2004/08/eventing" xmlns:e="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" xmlns:d="http://schemas.xmlsoap.org/ws/2004/09/transfer" xmlns:c="http://schemas.xmlsoap.org/ws/2004/09/enumeration" xmlns:b="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:a="http://www.w3.org/2003/05/soap-envelope" xmlns:h="http://schemas.xmlsoap.org/ws/2005/02/trust" xmlns:i="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <a:Header>
    <b:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</b:To>
    <b:RelatesTo>uuid:23c431ef-08c1-18c1-8002-687c3c671e00</b:RelatesTo>
    <b:Action a:mustUnderstand="true">http://schemas.dmtf.org/wbem/wsman/1/wsman/fault</b:Action>
    <b:MessageID>uuid:00000000-8086-8086-8086-000000000017</b:MessageID>
  </a:Header>
  <a:Body>
    <a:Fault>
      <a:Code>
        <a:Value>a:Sender</a:Value>
        <a:Subcode>
          <a:Value>e:SchemaValidationError</a:Value>
        </a:Subcode>
      </a:Code>
      <a:Reason>
        <a:Text xml:lang="en-US">The supplied SOAP violates the corresponding XML schema definition.</a:Text>
      </a:Reason>
      <a:Detail/>
    </a:Fault>
  </a:Body>
</a:Envelope>

Power_on2.xml
<p:RequestPowerStateChange_INPUT xmlns:p="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService">
  <p:ManagedElement>
   <a:Address xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a:Address>
   <a:ReferenceParameters xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd">
    <w:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem</w:ResourceURI>
    <w:SelectorSet>
     <w:Selector Name="Name">ManagedSystem</w:Selector>
    </w:SelectorSet>
   </a:ReferenceParameters>
  </p:ManagedElement>
  <p:PowerState>2</p:PowerState>
 </p:RequestPowerStateChange_INPUT>

B.R

Tan

-----Original Message-----
From: Klaus Kaempf [[hidden email]]
Sent: Wednesday, November 26, 2014 4:08 PM
To: Tan, Lin
Cc: [hidden email]
Subject: Re: [Openwsman-devel] Python binding: fail to generate correct request of invoke method with EndPointReference

* Tan, Lin <[hidden email]> [Nov 26. 2014 06:43]:
> Hi Kaempf,
>
> I can add EndPointReference into invoke method.
> But I get a new problem with the sequence of property.
>
> Here is my code:
> options.add_property('PowerState', '5')
> options.add_property('ManagedElement', system_epr)
>
> According to CIM_PowerManagementService, PowerState should be before
> ManagedElement.
> But I get request like:
> <n1:RequestPowerStateChange_INPUT>
>       <n1:ManagedElement> Correct references </n1:ManagedElement>
>       <n1:PowerState>5</n1:PowerState>
> </n1:RequestPowerStateChange_INPUT>
> So it violates the schema again.

This looks fine. Order of elements within <n1:RequestPowerStateChange_INPUT> shouldn't matter, since elements are parsed by name, not by position.

If you still get an error response, please show it to me.


Klaus
--
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Python binding: fail to generate correct request of invoke method with EndPointReference

Tan, Lin

Hi,

I don’t think this the problem of provider. It didn’t send to provider.

I check

http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService.xsd

The element SetPowerState_INPUT

<xs:element name="SetPowerState_INPUT">

<xs:complexType>

<xs:sequence>

<xs:element name="PowerState" nillable="true">...</xs:element>

<xs:element name="ManagedElement" nillable="true" type="cim:cimReference"/>

<xs:element name="Time" nillable="true" type="cim:cimDateTime"/>

</xs:sequence>

</xs:complexType>

</xs:element>

 

As it is sequence, the elements should follow the order.

 

B.R

 

Tan

 

From: Johnny Hwang [mailto:[hidden email]]
Sent: Wednesday, November 26, 2014 4:45 PM
To: Tan, Lin; Klaus Kaempf
Cc: [hidden email]
Subject: Re: [Openwsman-devel] Python binding: fail to generate correct request of invoke method with EndPointReference

 

Wow sounds like the provider is breaking the standard ... It should not rely on ordering. That will break clients for all common information models, from DMTF downwards.

 

Sent from my HTC

 

----- Reply message -----
From: "Tan, Lin" <[hidden email]>
To: "Klaus Kaempf" <[hidden email]>
Cc: "[hidden email]" <[hidden email]>
Subject: [Openwsman-devel] Python binding: fail to generate correct request of invoke method with EndPointReference
Date: Wed, Nov 26, 2014 12:36 AM

 

Hi Kaempf,

I am not familiar with XML Schema.
But I think this the problem.
I can prove with wsmancli using two xml files, the only difference is the sequence.

(1)
wsman invoke -a RequestPowerStateChange http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService?Name='Intel(r) AMT Power Management Service' -h 30.168.98.10 -P 16992 -u admin -p Cloud12345^ -J power_on.xml

<?xml version="1.0" encoding="UTF-8"?>
<a:Envelope xmlns:a="http://www.w3.org/2003/05/soap-envelope" xmlns:b="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:c="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" xmlns:d="http://schemas.xmlsoap.org/ws/2005/02/trust" xmlns:e="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:f="http://schemas.dmtf.org/wbem/wsman/1/cimbinding.xsd" xmlns:g="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <a:Header>
    <b:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</b:To>
    <b:RelatesTo>uuid:17c0660c-08c1-18c1-8002-687c3c671e00</b:RelatesTo>
    <b:Action a:mustUnderstand="true">http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService/RequestPowerStateChangeResponse</b:Action>
    <b:MessageID>uuid:00000000-8086-8086-8086-000000000012</b:MessageID>
    <c:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService</c:ResourceURI>
  </a:Header>
  <a:Body>
    <g:RequestPowerStateChange_OUTPUT>
      <g:ReturnValue>0</g:ReturnValue>
    </g:RequestPowerStateChange_OUTPUT>
  </a:Body>
</a:Envelope>

Power_on.xml:
<p:RequestPowerStateChange_INPUT xmlns:p="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService">
  <p:PowerState>2</p:PowerState>
  <p:ManagedElement>
   <a:Address xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a:Address>
   <a:ReferenceParameters xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd">
    <w:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem</w:ResourceURI>
    <w:SelectorSet>
     <w:Selector Name="Name">ManagedSystem</w:Selector>
    </w:SelectorSet>
   </a:ReferenceParameters>
  </p:ManagedElement>
 </p:RequestPowerStateChange_INPUT>

(2)
wsman invoke -a RequestPowerStateChange http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService?Name='Intel(r) AMT Power Management Service' -h 30.168.98.10 -P 16992 -u admin -p Cloud12345^ -J power_on2.xml

<?xml version="1.0" encoding="UTF-8"?>
<a:Envelope xmlns:g="http://schemas.dmtf.org/wbem/wsman/1/cimbinding.xsd" xmlns:f="http://schemas.xmlsoap.org/ws/2004/08/eventing" xmlns:e="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" xmlns:d="http://schemas.xmlsoap.org/ws/2004/09/transfer" xmlns:c="http://schemas.xmlsoap.org/ws/2004/09/enumeration" xmlns:b="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:a="http://www.w3.org/2003/05/soap-envelope" xmlns:h="http://schemas.xmlsoap.org/ws/2005/02/trust" xmlns:i="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <a:Header>
    <b:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</b:To>
    <b:RelatesTo>uuid:23c431ef-08c1-18c1-8002-687c3c671e00</b:RelatesTo>
    <b:Action a:mustUnderstand="true">http://schemas.dmtf.org/wbem/wsman/1/wsman/fault</b:Action>
    <b:MessageID>uuid:00000000-8086-8086-8086-000000000017</b:MessageID>
  </a:Header>
  <a:Body>
    <a:Fault>
      <a:Code>
        <a:Value>a:Sender</a:Value>
        <a:Subcode>
          <a:Value>e:SchemaValidationError</a:Value>
        </a:Subcode>
      </a:Code>
      <a:Reason>
        <a:Text xml:lang="en-US">The supplied SOAP violates the corresponding XML schema definition.</a:Text>
      </a:Reason>
      <a:Detail/>
    </a:Fault>
  </a:Body>
</a:Envelope>

Power_on2.xml
<p:RequestPowerStateChange_INPUT xmlns:p="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService">
  <p:ManagedElement>
   <a:Address xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a:Address>
   <a:ReferenceParameters xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd">
    <w:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem</w:ResourceURI>
    <w:SelectorSet>
     <w:Selector Name="Name">ManagedSystem</w:Selector>
    </w:SelectorSet>
   </a:ReferenceParameters>
  </p:ManagedElement>
  <p:PowerState>2</p:PowerState>
 </p:RequestPowerStateChange_INPUT>

B.R

Tan

-----Original Message-----
From: Klaus Kaempf [[hidden email]]
Sent: Wednesday, November 26, 2014 4:08 PM
To: Tan, Lin
Cc: [hidden email]
Subject: Re: [Openwsman-devel] Python binding: fail to generate correct request of invoke method with EndPointReference

* Tan, Lin <[hidden email]> [Nov 26. 2014 06:43]:
> Hi Kaempf,
>
> I can add EndPointReference into invoke method.
> But I get a new problem with the sequence of property.
>
> Here is my code:
> options.add_property('PowerState', '5')
> options.add_property('ManagedElement', system_epr)
>
> According to CIM_PowerManagementService, PowerState should be before
> ManagedElement.
> But I get request like:
> <n1:RequestPowerStateChange_INPUT>
>       <n1:ManagedElement> Correct references </n1:ManagedElement>
>       <n1:PowerState>5</n1:PowerState>
> </n1:RequestPowerStateChange_INPUT>
> So it violates the schema again.

This looks fine. Order of elements within <n1:RequestPowerStateChange_INPUT> shouldn't matter, since elements are parsed by name, not by position.

If you still get an error response, please show it to me.


Klaus
--
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel


------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Python binding: fail to generate correct request of invoke method with EndPointReference

Klaus Kaempf
* Tan, Lin <[hidden email]> [Nov 26. 2014 10:02]:

> Hi,
> I don't think this the problem of provider. It didn't send to provider.
> I check
> http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService.xsd
> The element SetPowerState_INPUT
> <xs:element name="SetPowerState_INPUT">
> <xs:complexType>
> <xs:sequence>
> <xs:element name="PowerState" nillable="true">...</xs:element>
> <xs:element name="ManagedElement" nillable="true" type="cim:cimReference"/>
> <xs:element name="Time" nillable="true" type="cim:cimDateTime"/>
> </xs:sequence>
> </xs:complexType>
> </xs:element>
>
> As it is sequence, the elements should follow the order.

Ouch, a sequence ...

IIRC, Openwsman stores invoke() parameters as a hash (set of key/value
pairs) and thus does not honor the ordering of add_property() calls.

So this might need a fix within Openwsman :-/ I'll have to check the
code.

Klaus
--
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
Maxfeldstraße 5, 90409 Nürnberg, Germany

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Python binding: fail to generate correct request of invoke method with EndPointReference

Tan, Lin
OK, great.

My plan is to integrate Intel AMT into OpenStack.
I really thank you for your effort to provide this tool. :)

As my current work is depending on this, please let me know when it is ready.
Thanks a lot.

Tan


-----Original Message-----
From: Klaus Kaempf [mailto:[hidden email]]
Sent: Wednesday, November 26, 2014 5:28 PM
To: Tan, Lin
Cc: Johnny Hwang; [hidden email]
Subject: Re: [Openwsman-devel] Python binding: fail to generate correct request of invoke method with EndPointReference

* Tan, Lin <[hidden email]> [Nov 26. 2014 10:02]:

> Hi,
> I don't think this the problem of provider. It didn't send to provider.
> I check
> http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementS
> ervice.xsd
> The element SetPowerState_INPUT
> <xs:element name="SetPowerState_INPUT"> <xs:complexType> <xs:sequence>
> <xs:element name="PowerState" nillable="true">...</xs:element>
> <xs:element name="ManagedElement" nillable="true"
> type="cim:cimReference"/> <xs:element name="Time" nillable="true"
> type="cim:cimDateTime"/> </xs:sequence> </xs:complexType>
> </xs:element>
>
> As it is sequence, the elements should follow the order.

Ouch, a sequence ...

IIRC, Openwsman stores invoke() parameters as a hash (set of key/value
pairs) and thus does not honor the ordering of add_property() calls.

So this might need a fix within Openwsman :-/ I'll have to check the code.

Klaus
--
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Python binding: fail to generate correct request of invoke method with EndPointReference

Klaus Kaempf
* Tan, Lin <[hidden email]> [Nov 26. 2014 10:56]:
> OK, great.
>
> My plan is to integrate Intel AMT into OpenStack.
> I really thank you for your effort to provide this tool. :)
>
> As my current work is depending on this, please let me know when it is ready.

Well, don't hold your breath. I will work on this, but only in my spare
time. So expect a couple of weeks delay.

Klaus
--
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
Maxfeldstraße 5, 90409 Nürnberg, Germany

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Python binding: fail to generate correct request of invoke method with EndPointReference

Tan, Lin
OK. I understand.
Thank you.

Tan

-----Original Message-----
From: Klaus Kaempf [mailto:[hidden email]]
Sent: Wednesday, November 26, 2014 6:30 PM
To: Tan, Lin
Cc: Johnny Hwang; [hidden email]
Subject: Re: [Openwsman-devel] Python binding: fail to generate correct request of invoke method with EndPointReference

* Tan, Lin <[hidden email]> [Nov 26. 2014 10:56]:
> OK, great.
>
> My plan is to integrate Intel AMT into OpenStack.
> I really thank you for your effort to provide this tool. :)
>
> As my current work is depending on this, please let me know when it is ready.

Well, don't hold your breath. I will work on this, but only in my spare time. So expect a couple of weeks delay.

Klaus
--
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Python binding: fail to generate correct request of invoke method with EndPointReference

Tan, Lin
In reply to this post by Klaus Kaempf
Hi Klaus,

Can I report a bug for this in Launchpad or somewhere else?
I use wsmancli to boot on/off and use python binding for the reset like set boot device.
But people asking me providing some info about the reason.

B.R

Tan
-----Original Message-----
From: Klaus Kaempf [mailto:[hidden email]]
Sent: Wednesday, November 26, 2014 6:30 PM
To: Tan, Lin
Cc: Johnny Hwang; [hidden email]
Subject: Re: [Openwsman-devel] Python binding: fail to generate correct request of invoke method with EndPointReference

* Tan, Lin <[hidden email]> [Nov 26. 2014 10:56]:
> OK, great.
>
> My plan is to integrate Intel AMT into OpenStack.
> I really thank you for your effort to provide this tool. :)
>
> As my current work is depending on this, please let me know when it is ready.

Well, don't hold your breath. I will work on this, but only in my spare time. So expect a couple of weeks delay.

Klaus
--
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Openwsman-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel
Loading...