thanks
On Tue, Mar 11, 2014 at 1:32 AM, Santhosh Edukulla <santhosh.eduku...@citrix.com> wrote: > Take a look at setup/dev/advanced.cfg for reference, we have an element > mgtSvr and you see hypervisor key there, thats what is set under apiclient. > This happens in cloudstackTestClient.py. > > Santhosh > ________________________________________ > From: Marcus [shadow...@gmail.com] > Sent: Tuesday, March 11, 2014 3:17 AM > To: dev@cloudstack.apache.org > Subject: Re: quick marvin/integration test question > > Yeah, that doesn't seem to be working for me. it's only defined at the > cluster level, correct? I don't see it defined anywhere else in the > other devcloud marvin cfg files. Look at any of the configs in > tools/devcloud-kvm > > On Tue, Mar 11, 2014 at 1:15 AM, Santhosh Edukulla > <santhosh.eduku...@citrix.com> wrote: >> The hypervisor type is picked up from config file you provided to nosetests, >> If not default to xen. >> >> Santhosh >> ________________________________________ >> From: Marcus [shadow...@gmail.com] >> Sent: Tuesday, March 11, 2014 3:10 AM >> To: dev@cloudstack.apache.org >> Subject: Re: quick marvin/integration test question >> >> I think the answer to this is no, because if I'm understanding how it >> works, specifying a hypervisor attr would filter out most of the >> tests, since most only use tags. The main issue I'm running into is >> that the marvin api client seems to return 'xenserver', so I can't >> just wrap parts of the test in an 'if' statement. I'll see if I can >> figure out why it's doing that. >> >> On Tue, Mar 11, 2014 at 1:03 AM, Marcus <shadow...@gmail.com> wrote: >>> I'm adding extra tests to the integration suite, and I'm testing for >>> unsupported hypervisor. I'm wondering if the automated integration >>> testing we use passes the '-a hypervisor=' filter that is appropriate >>> for the test environment, such that I can appropriately mark tests to >>> be run or not run as the wiki indicates.
