WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-cim

RE: [Xen-cim] Test suite

Sorry for the delay in responding (another 2 week business trip... sigh)

I agree. Seems like sblim-testsuite has some basic advantages, even in its current limited form.
And whatever dependence it has on a cli helper, ie wbemcli, should be minimally invasive and not
too bad to remove/replace with say a python/curl equivalent.

The nice thing about having a lower-level CIM client, at least right now, is that it'll allow us to
actually DO DefineVS(), since non of the existing tools support embedded instances (or even
references as arguments it seems....)

- Gareth

xen-cim-bounces@xxxxxxxxxxxxxxxxxxx wrote on 05/14/2007 08:26:04 AM:

> Gareth -

>  
> Jim, Raj, and I discussed your point exactly on Thursday.  Jim has a
> python script that does something similar to what you describe in
> your curl script.  Independence is a great thing, however, then we
> need to reinvent the wheel in a sense by rewriting test suite
> functionality.  We talked about having a separate script to define
> VMs (like Jim's python script of your curl script), etc and having a
> test suite do the other things (sblim-test suite).  Choosing sblim-
> test does not paint us into any corner and we could always opt to go
> independent if we want.  If this sounds reasonable or if something
> is missing, this is a good time to discuss it before I get too
> serious with the coding.

>  
> Luke
>
> From: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-cim-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Gareth S Bestor
> Sent: Friday, May 11, 2007 8:22 PM
> To: Jim Fehlig
> Cc: xen-cim@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-cim] Test suite

> BTW - if you want to go 'all the way' in terms of independence, we
> could ditch wbemcli/CLI/whatever and use straight CIM-XML. I have a
> small script that uses curl to submit an XML doc to a specific
> host/port and display the results if/when they get back.
>
> I'm not implying that avoiding a CLI to make our lives simpler is
> the way to go, but I just wanted to throw it out there as an option
> [BTW - one that we may be forced to take to test some things like
> DefineVS(), at least till these CIM clients correctly handle
> embedded instances...]
>
> - G
>
>
> xen-cim-bounces@xxxxxxxxxxxxxxxxxxx wrote on 05/11/2007 05:07:27 PM:
>
> > Gareth S Bestor wrote:
> > >
> > > CIM provider test tool should have little or dependency on a cimom IMO.
> > >
> >
> > Agreed.
> >
> > Luke,
> > Can you put together an equivalent patch that uses sblim-testsuite?
> > Sorry for not realizing cimtester dependencies earlier.
> >
> > Thanks,
> > Jim
> >
> > > SBLIM Testsuite has a 'dependency' on wbemcli, which is a
> > > cimom-agnostic command-line client tool for performing CIM operations,
> > > pretty much equivalent functionality to Pegasus CLI tool.
> > >
> > > Perhaps that's enugh reason to go with SBLIM Testsuite? Certainly it
> > > lacks ability today to perform complex like scripted CIM
> > > operations, but I'm not getting the impression cimtester provides
> > > significantly more in terms of functionality. Plus SBLIM Testsuite
> > > is being used today for the automated testing of the various SBLIM
> > > provider packages going into SLES & RHEL...
> > >
> > > - Gareth
> > >
> > > xen-cim-bounces@xxxxxxxxxxxxxxxxxxx wrote on 05/10/2007 02:40:28 PM:
> > >
> > > > Szymanski, Lukasz K wrote:
> > > > >
> > > > > This patch is the humble beginnings of our test suite.  The tests did
> > > > > not get too far with the latest because of all the instability (CIMOM
> > > > > seg faults), however, this is one of the reasons we started down this
> > > > > path anyway.  There are a bunch of errors if cimtester is run on a
> > > > > previous, more stable version, but the test finishes.  Let's decide
> > > > > soon which direction we want to pursue (sblim-test or cimtester) so I
> > > > > can either make improvements on the cimtester stuff or get started on
> > > > > the sblim-test work.
> > > > >
> > > >
> > > > Damn...  While playing with your patch I realized (while building it)
> > > > that cimtester has a dependency on  OW client library - which is only
> > > > available in the whole of OW itself.  So you have to have OW installed
> > > > to build/run cimtester :-(.
> > > >
> > > > sblim-testsuite has a dependency on sblim-wbemcli, but the latter has no
> > > > cimom dependencies.
> > > >
> > > > Seems to me we want a cimom-independent test infrastructure.  Thoughts?
> > > >
> > > > Jim
> > > >
> > > >
> > > > _______________________________________________
> > > > Xen-cim mailing list
> > > > Xen-cim@xxxxxxxxxxxxxxxxxxx
> > > > http://lists.xensource.com/xen-cim
> > >
> >
> > _______________________________________________
> > Xen-cim mailing list
> > Xen-cim@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-cim
> _______________________________________________
> Xen-cim mailing list
> Xen-cim@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-cim

_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim
<Prev in Thread] Current Thread [Next in Thread>