client discovery related queries

"sr!n!mg" <[email protected]>
Newsgroups gmane.network.open-pegasus.general
Message-ID <[email protected]>
Hi,

We have implemented providers (instance, association and method) using Open
Pegasus 2.7.1. The approach we took is that our providers will be
responsible for queries directed to implementation namespace where as use
the default pegasus interop provider for "pg_interop" namespace. We create
the required RegisteredProfile instances in the pg_interop. We link the
Array registered profile instance to cim_computersystem instance through
elementconformstoprofile instance interlinking the two cross namespaces. Now
we have the elementconformstoprofile instance having two object paths that
has one end pointing to Array registered profile (in pg_interop) and other
end pointing to cim_computersystem (in implementation namespace)

The discovery logic used by clients is they get the array registered profile
and use the elementconformstoprofile association to get to
cim_computersystem.

The question I have is:

   - With our implementation only Associator Names, References and Reference
   Names can be used. If client tries to do an Associator operation, Pegasus
   throws an error. Is there a way to fix this?
   - In general which SMI-S query is used for get to cim_computersystem from
   array instance?

Thanks,
Srini
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.