libvirt-cim-bounces@redhat.com wrote on 2008-09-23 04:49:53:

> My apologies for not responding to this on Friday.
>
> >  >
> >  > 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
> > *
>
> root/virt is the namespace of the libvirt-cim providers.  The SBLIM
> providers live in root/cimv2
>
  Thanks! I can enumerate it in root/cimv2 namespace.

> >
> >  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.
>
> This is very similar to what we have to do for the ECTP test cases -
> RegisteredProfile lives in root/interop, while ComputerSystem lives in
> root/virt.
>
> I'd take a look at those test cases for ideas on how to handle multiple
> namespaces in one test.
>
>
> >  >
> >  > 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.
> >
> ttps://www.redhat.com/mailman/listinfo/libvirt-cim
>
>
> --
> 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