RE: open pegasus 2.12 & SCVMM integration

Oh, the namespace in the xml is not the problem. Open Pegasus by default uses root/PG_InterOp (historical reasons). But "interop" is supported from 2.12, so using "interop" is not a problem in Open Pegasus. The xml below was just an example.

I guess MS uses root/interop. You could try using root/interop if required by setting the "PEGASUS_INTEROP_NAMESPACE" to root/interop.

Some CQL related problems in Open Pegasus are listed in https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:workgroups:pegasus_26_snia_requirements_pep&s[]=cql<https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:workgroups:pegasus_26_snia_requirements_pep&s%5b%5d=cql> under CQL functionality.

The easiest way to get some clue on this is to enables traces.

Regards,
Rohini Deshpande

From: Paul Robert Marino [mailto:[email protected]]
Sent: Wednesday, February 27, 2013 9:52 PM
To: Ben Wang
Cc: Deshpande, Rohini (IESL); [email protected]; [email protected]
Subject: Re: open pegasus 2.12 & SCVMM integration

Ben
this is what i was getting at
http://msdn.microsoft.com/en-us/library/windows/desktop/ee309362%28v=vs.85%29.aspx
Its called the interop namespace but its actual name is usually root\interop which is the standard for most WBEM implementations.
There are a few exceceptions such as older versions of openpegasus call it root\PG_Interop but in general root\interop is the standard for nearly every WBEM server.
That being said just because it should be registered in root\interop doesn't mean it should be used in the root\interop namespace.In addition I've never seen a single work namespace before and while I dont think ive seen any thing in the standard that explicitly forbids it it is implied in the DMTF documents that you shouldn't do it, so i don't know how well WBEM servers or even the clients would deal with it.

so If I'm right
"
        <LOCALNAMESPACEPATH>
          <NAMESPACE NAME="interop" />
        </LOCALNAMESPACEPATH>
"
should really be
"
        <LOCALNAMESPACEPATH>
          <NAMESPACE NAME="root" />
          <NAMESPACE NAME="interop" />
        </LOCALNAMESPACEPATH>
"
On Wed, Feb 27, 2013 at 10:28 AM, Ben Wang <[email protected]<mailto:[email protected]>> wrote:
Paul,

According to MS spec, they expect all standalone providers use interop namespace, indications are only supported in this namespace.

I found an interesting discussion thread in Google Pegasus group. I have not verified the validity of his opinions, it was published on 6/8/09. It may NOT represent the latest Pegasus status.

"
here should not be differences in the CIMOM to support per-defined vs client-defined indication filters, but the Pegasus CIMOM has a variety of quirks that causes it to handle indications differently depending on build options and workarounds to Pegasus bugs.
1) unless you specifically enable CQL support, Pegasus CIMOM will not handle CQL indications ( I don't recall the name of the build option) (I highly doubt)
2) Even with the CQL build options enabled, Pegasus CIMOM does not support indication filters with the ANY keyword (this is required by the CQL standard for InstModification filters with a comparison of an array property and a specific value)
3) if you build Pegasus CIMOM with PEGASUS_SNIA_EXTENSIONS enabled, it will tolerate the ISA keyword SMI-S  uses in  some WQL InstModification indication filters
4) Pegasus CIMOM always rejects client-defined (CreateInstance) for WQL  IndicationFilters with a filter containing a period (e.g., SourceInstance.OperationalStatus), though it does allow these to be pre-defined.

2) and 4) are clearly bugs. Apparently some SMI-S vendors have updated their implementations ofd Pegasus to work around the bugs.

"

I will do more experiments and hopefully find a way out.

_____________________________________
Ben Wang
Software Engineer
FalconStor Software, Inc. (NASDAQ: FALC)
2 Huntington Quadrangle, Suite 2S01
Melville, NY 11747
O: 1.631.773.4489<tel:1.631.773.4489>
M: 1.631.988.2209<tel:1.631.988.2209>
[email protected]<mailto:[email protected]>

Defining Data Protection, Again(tm)

[signature_promoting_final]<http://www.falconstor.com/news-and-events/press-center/press-releases-top-story/2256-falconstor-recovertrac-2-5-selected-for-a-best-of-vmworld-2012-gold-award>

Follow us:
[Blogger]<http://www.falconstor.com/community/blogs>[Twitter1-icon]<http://twitter.com/FalconStor> [linkedin-icon] <http://www.linkedin.com/groups?mostPopular=&gid=776377>  [Youtube-icon] <http://www.youtube.com/user/FalconStor>  [Flickr-icon1] <http://www.flickr.com/photos/falconstor/>

This email and any attachment(s) is for the intended recipient only and may be confidential. If you are not the intended recipient, please delete this e-mail and advise the sender immediately. Unauthorized use or distribution is prohibited.

From: Paul Robert Marino [mailto:[email protected]<mailto:[email protected]>]
Sent: Wednesday, February 27, 2013 8:24 AM
To: Deshpande, Rohini (IESL); Ben Wang; [email protected]<mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>
Subject: RE: open pegasus 2.12 & SCVMM integration

The namespace you specified is interop are you sure you didn't want root/interop

-- Sent from my HP Pre3

________________________________
On Feb 27, 2013 1:00 AM, Deshpande, Rohini (IESL) <[email protected]<mailto:[email protected]>> wrote:
Hi Ben Wang,

I'm not sure what is wrong with your request, but a similar request went through when I tested.

<?xml version="1.0" encoding="utf-8" ?>
<CIM CIMVERSION="2.0" DTDVERSION="2.0">
<MESSAGE ID="1000" PROTOCOLVERSION="1.0">
<SIMPLEREQ>
<IMETHODCALL NAME="CreateInstance">
<LOCALNAMESPACEPATH>
<NAMESPACE NAME="test"/>
<NAMESPACE NAME="testprovider"/>
</LOCALNAMESPACEPATH>
<IPARAMVALUE NAME="NewInstance">
<INSTANCE CLASSNAME="CIM_IndicationFilter" >
<PROPERTY NAME="Name"  TYPE="string">
<VALUE>filter2</VALUE>
</PROPERTY>
<PROPERTY NAME="Query"  TYPE="string">
<VALUE>SELECT * from IndicationStressTestClass</VALUE>
</PROPERTY>
<PROPERTY NAME="QueryLanguage"  TYPE="string">
<VALUE>DMTF:CQL</VALUE>
</PROPERTY>
<PROPERTY NAME="SourceNamespace"  TYPE="string">
<VALUE>test/testprovider</VALUE>
</PROPERTY>
</INSTANCE>
</IPARAMVALUE>
</IMETHODCALL>
</SIMPLEREQ>
</MESSAGE>
</CIM>

Maybe you can try the above request. You could also try using the cimsub command with "-c" for creating the filter.
You can enable cimserver tracing to know why it is failing.  "cimserver traceLevel=4 traceComponents=All" (for tracing all components at level 4).

Regards,
Rohini Deshpande
Software Engineer/OpenPegasus Committer
Hewlett Packard

From: Ben Wang [mailto:[email protected]]
Sent: Wednesday, February 27, 2013 4:24 AM
To: [email protected]<mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>
Subject: open pegasus 2.12 & SCVMM integration

Hi all,

I am using Open Pegasus 2.12 + CIMPLE provider to integration with MS SCVMM 2012. According to MS spec, life cycle indication will be used to sync client cache with provider.

SCVMM will try to register client specific filters during its discovery stage. However, my provider fails to respond to the registration request, here is snippet of xml dump

...
<?xml version="1.0" encoding="UTF-8"?>
<CIM CIMVERSION="2.0" DTDVERSION="2.0">
  <MESSAGE ID="11" PROTOCOLVERSION="1.0">
    <SIMPLEREQ>
      <IMETHODCALL NAME="CreateInstance">
        <LOCALNAMESPACEPATH>
          <NAMESPACE NAME="interop" />
        </LOCALNAMESPACEPATH>
        <IPARAMVALUE NAME="NewInstance">
          <INSTANCE CLASSNAME="CIM_IndicationFilter">
            <PROPERTY NAME="Name" TYPE="string">
              <VALUE>54479A7D15EC4D4F923090046D0D9E91:CIM_InstDeletion:CIM_ComputerSystem</VALUE>
            </PROPERTY>
            <PROPERTY NAME="Caption" TYPE="string">
              <VALUE>Microsoft Storage Service Subscription</VALUE>
            </PROPERTY>
            <PROPERTY NAME="QueryLanguage" TYPE="string">
              <VALUE>DMTF:CQL</VALUE>
            </PROPERTY>
            <PROPERTY NAME="Query" TYPE="string">
              <VALUE>SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_ComputerSystem</VALUE>
            </PROPERTY>
            <PROPERTY NAME="SourceNamespace" TYPE="string">
              <VALUE>interop</VALUE>
            </PROPERTY>
          </INSTANCE>
        </IPARAMVALUE>
      </IMETHODCALL>
    </SIMPLEREQ>
  </MESSAGE>
</CIM>

02/26/13 16:39:29 INFORMATION:

<?xml version="1.0" encoding="utf-8" ?>
<CIM CIMVERSION="2.0" DTDVERSION="2.0">
<MESSAGE ID="11" PROTOCOLVERSION="1.0">
<SIMPLERSP>
<IMETHODRESPONSE NAME="CreateInstance">
<ERROR CODE="7" DESCRIPTION="CIM_ERR_NOT_SUPPORTED: DMTF:CQL"/></IMETHODRESPONSE>
</SIMPLERSP>
</MESSAGE>
</CIM>
...


I do have some debug messages in my CIM_IndicationFilter and CIM_InstDeletion provider, but those message never get printed out. It seems to me that Pegasus responds to the client registration request without asking my provider.

I am still exploring the right way to implement an indication provider, so I appreciate if someone can cast light on my issue even if it sounds a little dumb:)

PS: I did have PEGASUS_ENABLE_CQL=true when I compiled Open Pegasus.

Could somebody cast some light on my issue?

Thank you very much.
_____________________________________
Ben Wang
Software Engineer
FalconStor Software, Inc. (NASDAQ: FALC)
2 Huntington Quadrangle, Suite 2S01
Melville, NY 11747
O: 1.631.773.4489<tel:1.631.773.4489>
M: 1.631.988.2209<tel:1.631.988.2209>
[email protected]<mailto:[email protected]>

Defining Data Protection, Again(tm)

[signature_promoting_final]<http://www.falconstor.com/news-and-events/press-center/press-releases-top-story/2256-falconstor-recovertrac-2-5-selected-for-a-best-of-vmworld-2012-gold-award>

Follow us:
[Blogger]<http://www.falconstor.com/community/blogs>[Twitter1-icon]<http://twitter.com/FalconStor> [linkedin-icon] <http://www.linkedin.com/groups?mostPopular=&gid=776377>  [Youtube-icon] <http://www.youtube.com/user/FalconStor>  [Flickr-icon1] <http://www.flickr.com/photos/falconstor/>

This email and any attachment(s) is for the intended recipient only and may be confidential. If you are not the intended recipient, please delete this e-mail and advise the sender immediately. Unauthorized use or distribution is prohibited.