Re: community testing

I think the test infra as described is great, but I think we're hurting a little more for basics. For example, we don't need a full infrastructure with hardware to ensure that the support matrix works. I could bring up a VM with CentOS and one with Ubuntu, and test NFS, CLVM, and RBD on each. CLVM

Re: Java process not running in KVM SSVM

Since the 4.2 code isn't yet available from a pre-built source on the web, maybe I should do 4.1.1. Otherwise I'd have to build the 4.2 .debs and we'd be subject to the same possible build errors. Unless the 4.2 ones are available on the web. On Wed, Sep 11, 2013 at 11:11 PM, Marcus Sorensen wr

Re: community testing

Yeah, I would love to get a SolidFire test suite up and running and plugged into the main builds. On Wed, Sep 11, 2013 at 11:15 PM, Marcus Sorensen wrote: > I think the test infra as described is great, but I think we're > hurting a little more for basics. For example, we don't need a full > inf

Re: Java process not running in KVM SSVM

Agree with Marcus, it could because of the different ./client/tomcatconf/ nonossComponentContext.xml.in and ./client/tomcatconf/ componentContext.xml.in Mike, could you try "mvn -P developer,systemvm clean install" instead? 2013/9/12 Mike Tutkowski > Since the 4.2 code isn't yet available from

Re: Java process not running in KVM SSVM

The "Premium" comes from this part in ./client/tomcatconf/nonossComp onentContext.xml 2013/9/12 Wei ZHOU > Agree with Marcus, it could because of the different ./client/tomcatconf/ > nonossComponentContext.xml.in a

Re: community testing

I guess I was unaware that the test infrastructure tests various deployment configs from the ground up, rebuilding from baremetal (I guess?). I was initially thinking "We already test KVM, let me just run two commands on the host to set up a volume group, then tweak the marvin test to register it

Re: Java process not running in KVM SSVM

Sure, I can run "mvn -P developer,systemvm clean install" (omitting -Dnonoss). I can then redeploy the .debs and see what happens. I'll do this in 4.2. On Wed, Sep 11, 2013 at 11:18 PM, Wei ZHOU wrote: > Agree with Marcus, it could because of the different ./client/tomcatconf/ > nonossCompone

Re: Java process not running in KVM SSVM

I think there's a special command to generate the nonoss debs. I've seen it on the mailing list recently, it seems. On Wed, Sep 11, 2013 at 11:21 PM, Wei ZHOU wrote: > The "Premium" comes from this part in ./client/tomcatconf/nonossComp > onentContext.xml

Re: Java process not running in KVM SSVM

Thanks, Wei. So, not putting in -Dnonoss should solve my problem, it seems. However, is there still not a problem for those who need -Dnonoss? On Wed, Sep 11, 2013 at 11:21 PM, Wei ZHOU wrote: > The "Premium" comes from this part in ./client/tomcatconf/nonossComp > onentContext.xml

Re: community testing

Thanks Marcus - I wanted to work through some concrete steps for the infra now that we have some idea what we want to do. We should have basic product setup and install and a single deployvm test for all possible configurations: As a start can we work to setup devcloud and devcloud-kvm environment

Re: Java process not running in KVM SSVM

Ah, if what Marcus says is accurate, then that would likely explain the situation. On Wed, Sep 11, 2013 at 11:23 PM, Marcus Sorensen wrote: > I think there's a special command to generate the nonoss debs. I've > seen it on the mailing list recently, it seems. > > On Wed, Sep 11, 2013 at 11:21 PM

Re: Java process not running in KVM SSVM

What about that script, though? The domain variable being referenced instead of the vmName one. That still seems like an issue. On Wed, Sep 11, 2013 at 11:24 PM, Mike Tutkowski < mike.tutkow...@solidfire.com> wrote: > Ah, if what Marcus says is accurate, then that would likely explain the > situ

Re: Java process not running in KVM SSVM

Mike, The script is an issue only in master branch. Few people work are working on testing it as most are on 4.2 release now. Please feel free to create JIRA ticket and commit patch for it.

Re: Marvin tests for VPC - why create VPC offering?

On Thu, Sep 12, 2013 at 05:15:16AM +, Sowmya Krishnan wrote: > I find for most of the VPC tests we create a new VPC Offering which > provides almost the same set of services as the "Default VPC > Offering" already available by default. We also have a separate > function to create this offering,

Re: Release Criteria

I've repeated it several times in other threads, but I think at a bare minimum it has to work in the listed versions of Ubuntu, CentOS (both mgmt server and KVM host), XenServer, VmWare, what have you, along with the advertised storage and networking. We can discuss limiting that to OSS, maybe, as

Re: Java process not running in KVM SSVM

Sure, I can fix that code in 4.2. On Wed, Sep 11, 2013 at 11:33 PM, Wei ZHOU wrote: > Mike, > The script is an issue only in master branch. Few people work are > working on testing it as most are on 4.2 release now. > Please feel free to create JIRA ticket and commit patch for it. > -- *Mi

RE: Marvin tests for VPC - why create VPC offering?

> -Original Message- > From: Prasanna Santhanam [mailto:t...@apache.org] > Sent: Thursday, September 12, 2013 11:07 AM > To: dev@cloudstack.apache.org > Subject: Re: Marvin tests for VPC - why create VPC offering? > > On Thu, Sep 12, 2013 at 05:15:16AM +, Sowmya Krishnan wrote: > > I

Re: Review Request 14079: marvin tests for IP Address reservation within a network

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/14079/#review26049 --- test/integration/component/test_ip_reservation.py

Re: Marvin tests for VPC - why create VPC offering?

See inline, there seems to be a bug in the design. On Thu, Sep 12, 2013 at 05:53:45AM +, Sowmya Krishnan wrote: > > -Original Message- > > From: Prasanna Santhanam [mailto:t...@apache.org] > > Sent: Thursday, September 12, 2013 11:07 AM > > To: dev@cloudstack.apache.org > > Subject: Re

Re: community testing

On Sep 12, 2013, at 7:24 AM, Prasanna Santhanam wrote: > Thanks Marcus - I wanted to work through some concrete steps for the infra now > that we have some idea what we want to do. We should have basic product setup > and install and a single deployvm test for all possible configurations: > > A

<    1   2