This will be changed in the future. The problem is that Linux_ComputerSystem lives in a different namespace, so we need to make the association providers handle the different namespaces.
In the SBLIM case, you'll want to use Linux_ComputerSystem instead of HostSystem. However, we don't support that yet. I'd add a bug to
libvirt-cim-bounces@redhat.com wrote on 2008-09-18 23:41:40: the
cimtest wiki and then have the tests XFAIL in the situation where you need to use Linux_ComputerSystem to resolve an association.
Then how to verify the test use Linux_ComputerSystem instead of HostSystem in test? One way is to check if sblim base provider is installed, the other way is to check the return instance of enumerate HostSystem. Any other suggestion?
Thanks!
I'd do the following:
1) HostSystem: 01_enum.py - Enum Linux_ComputerSystem - if this call returns an instance, then the enum of HostSystem shouldn't return any instances. Otherwise, you should get back a HostSystem instance.
Which namespace does Linux_ComputerSystem live in? The enum of Linux_ComputerSystem return NULL: [root@elm** ~]# wbemcli ein http://root:password@localhost/root/virt:Linux_ComputerSystem * * wbemcli: Cim: (5) CIM_ERR_INVALID_CLASS: Linux_ComputerSystem * Since the namespace of Linux_ComputerSystem is different from the others, how to set CIM_NS twice in one test case? That is to say, I have to set CIM_NS as /root/virt when I enum HostSystem, then the namespace have to be set others when I enum Linux_ComputerSystem in one test case. Thanks!
2) For all other tests the depend on a HostSystem instance, do an enum of HostSystem. If no instances are returned, do an enum of Linux_ComputerSystem and use that instance.
Does this help? -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com
_______________________________________________ Libvirt-cim mailing list Libvirt-cim@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-cim