> -Original Message-
> From: Santhosh Edukulla [mailto:santhosh.eduku...@citrix.com]
> Sent: Tuesday, October 08, 2013 1:28 AM
> To: dev@cloudstack.apache.org
> Subject: RE: [DISCUSS] Breaking out Marvin from CloudStack
>
> Comments Inline.
>
> -Original
All - thanks for your detailed thoughts on this so far. It seems like
this should've come with a fair bit of notice. I will hold on this
separation for now. May be a couple more releases to see the level of
participation in the QA and if it still feels like a hindrance we'll
discuss separating it l
Comments Inline.
-Original Message-
From: Edison Su [mailto:edison...@citrix.com]
Sent: Tuesday, October 08, 2013 4:18 AM
To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
Subject: RE: [DISCUSS] Breaking out Marvin from CloudStack
Few questions:
1. About the "
to test against
http://people.apache.org/~tsp/dummy.iso, but it won't work for devcloud, or in
an internal network. The ISO data factory should be able to return an url based
on different test environment, thus iso test cases can be reused.
> -Original Message-
> From: Sant
: [DISCUSS] Breaking out Marvin from CloudStack
On Sun, Oct 6, 2013 at 8:10 PM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:
> > Yes and we will need to work down a backlog of scenarios before we ever
> > can rely on guys like me doing that. Not because they won't b
On Sun, Oct 6, 2013 at 8:10 PM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:
> > Yes and we will need to work down a backlog of scenarios before we ever
> > can rely on guys like me doing that. Not because they won't but because
> > there is to much to write tests for edging on the n
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Saturday, October 05, 2013 3:22 AM
> To: dev
> Subject: Re: [DISCUSS] Breaking out Marvin from CloudStack
>
> H Chip,
>
> As a feature-dev driven by a 150-man-strong-cloud-
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Friday, October 04, 2013 1:53 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] Breaking out Marvin from CloudStack
>
>
> Fair warning - some of this is a straw man
H Chip,
As a feature-dev driven by a 150-man-strong-cloud-operator-base that is not
interested in anything but me showing that they can work with what they
asked for:
On Fri, Oct 4, 2013 at 10:52 PM, Chip Childers wrote:
...
> On Fri, Oct 04, 2013 at 05:57:58PM +0530, Prasanna Santhanam wrote:
>
Fair warning - some of this is a straw man argument to explore the
situation, and a little bit of ranting at the end.
On Fri, Oct 04, 2013 at 05:57:58PM +0530, Prasanna Santhanam wrote:
> I'll summarize and address the concerns raised so far.
>
> Marvin has been in this repo for a long time for
Prasanna,
I share Chips concern. But let me start by saying that given the effort
Citrix puts in the integration testing, making it easy for your guys should
be somewhat a priority. However, can we do the separation is such a way
that integration tests as part of plugin and other enhancements is s
I'll summarize and address the concerns raised so far.
Marvin has been in this repo for a long time for us to start writing
tests. The only tests I've seen coming are from a specific set of
people focussed on QA efforts. I want to reduce the impediment for
people who are writing tests *today*. Tho
On Thu, Oct 03, 2013 at 05:27:27PM +, Santhosh Edukulla wrote:
> >The problem with tests being broken out from the main repo is that we
> > end up having a really hard time confirming that new features include
> > appropriate tests. Plus, tests are tied to features, which are tied to
> > the c
rom: Chip Childers [chip.child...@sungard.com]
Sent: Thursday, October 03, 2013 11:07 AM
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Breaking out Marvin from CloudStack
On Thu, Oct 03, 2013 at 05:55:14AM +, Santhosh Edukulla wrote:
> I believe both can exist independently. The fra
On Thu, Oct 03, 2013 at 05:55:14AM +, Santhosh Edukulla wrote:
> I believe both can exist independently. The framework should have more
> flexibility and facilitation to run features\test cases based upon a given
> release and version on a given test bed. It should be intelligent enough to
Regards,
Santhosh
From: Alex Huang [alex.hu...@citrix.com]
Sent: Wednesday, October 02, 2013 4:42 PM
To: dev@cloudstack.apache.org
Subject: RE: [DISCUSS] Breaking out Marvin from CloudStack
Yeah...I'm more amendable to this proposal. I just don't see t
[mailto:animesh.chaturv...@citrix.com]
Sent: Wednesday, October 02, 2013 2:08 PM
To: dev@cloudstack.apache.org
Subject: RE: [DISCUSS] Breaking out Marvin from CloudStack
> -Original Message-
> From: Chip Childers [mailto:chipchild...@apache.org]
> Sent: Wednesday, October 02, 2013 1:1
> -Original Message-
> From: Chip Childers [mailto:chipchild...@apache.org]
> Sent: Wednesday, October 02, 2013 1:10 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] Breaking out Marvin from CloudStack
>
> On Wed, Oct 02, 2013 at 07:38:33PM +, Al
Chip, that makes perfect sense to me.
On 10/2/13 1:10 PM, "Chip Childers" wrote:
>On Wed, Oct 02, 2013 at 07:38:33PM +, Alex Huang wrote:
>> I don't really understand what purpose would this serve. Would we ever
>>use newer marvin against older CloudStack or vice versa? What's the
>>benefi
Yeah...I'm more amendable to this proposal. I just don't see tests being
separated from the source release. In fact, I see a lot of problems with
matching versions and releases.
I still question the value of separating out a framework where both ends (tests
and the server it tests) stay in th
to have a different release cycle.
>> -Original Message-
>> From: Alex Huang [mailto:alex.hu...@citrix.com]
>> Sent: Wednesday, October 02, 2013 12:39 PM
>> To: dev@cloudstack.apache.org
>> Subject: RE: [DISCUSS] Breaking out Marvin from CloudStack
>>
>
On Wed, Oct 02, 2013 at 07:38:33PM +, Alex Huang wrote:
> I don't really understand what purpose would this serve. Would we ever use
> newer marvin against older CloudStack or vice versa? What's the benefit?
>
> I can understand it for cloudmonkey because cloudmonkey is an admin cli tool
> tool and reving it differently is not a bad idea. I just don't see it for
> marvin
> and, especially for the tests.
>
> --Alex
>
> > -Original Message-
> > From: Prasanna Santhanam [mailto:t...@apache.org]
> > Sent: Wednesday, October 2, 2013
n't see it for marvin
and, especially for the tests.
--Alex
> -Original Message-
> From: Prasanna Santhanam [mailto:t...@apache.org]
> Sent: Wednesday, October 2, 2013 10:14 AM
> To: CloudStack Dev
> Subject: [DISCUSS] Breaking out Marvin from CloudStack
>
> I wo
> After separating marvin
> 0. we will have a separate release cycle for marvin
> 1. we will have a new home for marvin's docs using Sphinx
> 2. if possible, a different criteria for providing commit access to
> marvin's repos.
> 3. all tests of cloudstack will also move to marvin's repository
>
I
:26 AM
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Breaking out Marvin from CloudStack
+1
On Oct 2, 2013, at 1:58 PM, Edison Su wrote:
> Seems Marvin won't depend on commands.xml any more, thus won't depend on any
> artifacts build from cloudstack. So I am +1.
>
mailto:t...@apache.org]
>> Sent: Wednesday, October 02, 2013 10:14 AM
>> To: CloudStack Dev
>> Subject: [DISCUSS] Breaking out Marvin from CloudStack
>>
>> I would like to seperate marvin from the main cloudstack repo. Much of
>> marvin's development has little
>> Sent: Wednesday, October 02, 2013 10:14 AM
>> To: CloudStack Dev
>> Subject: [DISCUSS] Breaking out Marvin from CloudStack
>>
>> I would like to seperate marvin from the main cloudstack repo. Much of
>> marvin's development has little coupling with CloudSta
gt; To: CloudStack Dev
>> Subject: [DISCUSS] Breaking out Marvin from CloudStack
>>
>> I would like to seperate marvin from the main cloudstack repo. Much of
>> marvin's development has little coupling with CloudStack.
>>
>> Similar to CloudMonkey, marvin u
ev
> Subject: [DISCUSS] Breaking out Marvin from CloudStack
>
> I would like to seperate marvin from the main cloudstack repo. Much of
> marvin's development has little coupling with CloudStack.
>
> Similar to CloudMonkey, marvin undergoes rapid changes and it is essential
> to p
I would like to seperate marvin from the main cloudstack repo. Much of
marvin's development has little coupling with CloudStack.
Similar to CloudMonkey, marvin undergoes rapid changes and it is
essential to provide a smooth workflow and faster releases for those
working with it.
There are also
31 matches
Mail list logo
