On Fri, Feb 07, 2014 at 06:44:07AM +, Santhosh Edukulla wrote:
> Team,
>
> Do we have any issues if we remove dpeloy\load options from
> marvinPlugin? Iam assuming users wanted to use deployDC can still
> use other options available i.e.., deployDC etc.
>
> So, we just use marvinplugin to ru
loyDC separately, if its a case we can
remove there as well.
Regards,
Santhosh
From: Prasanna Santhanam [t...@apache.org]
Sent: Friday, February 07, 2014 1:54 AM
To: dev@cloudstack.apache.org
Subject: Re: Removing deploy\load options from marvinplugin
O
On Fri, Feb 07, 2014 at 07:25:03AM +, Santhosh Edukulla wrote:
> 1. code restructuring ,definitely yes, it makes little neat and
> plugin does not worry much about deploy altogether. Take an example
> of load option, it is little redundant i believe, if user passes the
> deploy flag, deploy s
CIL
From: Prasanna Santhanam [t...@apache.org]
Sent: Friday, February 07, 2014 4:18 AM
To: dev@cloudstack.apache.org
Subject: Re: Removing deploy\load options from marvinplugin
On Fri, Feb 07, 2014 at 07:25:03AM +, Santhosh Edukulla wrote:
> 1. c
On Fri, Feb 07, 2014 at 09:36:49AM +, Santhosh Edukulla wrote:
> From: Prasanna Santhanam [t...@apache.org]
> Sent: Friday, February 07, 2014 4:18 AM
> To: dev@cloudstack.apache.org
> Subject: Re: Removing deploy\load options from marvinplugin
>
> On Fri, Feb 07, 2014 a
the question derived to see cant we remove deployDC from nosetests altogether?
Regards,
Santhosh
________________
From: Prasanna Santhanam [t...@apache.org]
Sent: Friday, February 07, 2014 5:05 AM
To: dev@cloudstack.apache.org
Subject: Re: Removing deploy\load options from marv
ose plugin. If we have references where we are using it in both
> flows then we can think of it, let us know?
>
> 1. DeployDC
> 2. Run test cases with nose tests.
>
> 8. The logging issue: What i meant was that we are doing some changes for
> logging. We are providing log fa
oyDC, we just exit without checks for
>>deployDC. Also, i mentioned the current flow as an eample, where we are
>>using explicit deployDC, followed by tests using nose plugin. If we have
>>references where we are using it in both flows then we can think of it,
>>let
>> 2. deploydatacenter (done using nose earlier)
>>> 3. restart cloudstack
>>> 4. run tests (also done by nose earlier)
>>>
>>> 7. The reason for separation is to keep things simple. As a user, i can
>>> run below. The reason i mentioned to separate deploy
