: Re: [DISCUSS]CLOUDSTACK-6191
Seems like it could have been fixed with a smaller code replace but I
guess you are right.
@Santosh, Can you split your commit and reapply. At least chipping off
the BridgeVifDriver bit, but preferably all chopped up as other issues
will probably come up.
thanks
27;d better refactor the code in
> BridgeVifDriver->Plug
>
>> -Original Message-
>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: Tuesday, July 15, 2014 4:43 AM
>> To: dev; Edison Su; Santhosh Edukulla
>> Subject: Re: [DISCUSS]CLOUDSTACK-6191
>&
t;Plug
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Tuesday, July 15, 2014 4:43 AM
> To: dev; Edison Su; Santhosh Edukulla
> Subject: Re: [DISCUSS]CLOUDSTACK-6191
>
> Edison,
>
> You reverted a600d8408ea86782318139c17
ert or change CLOUDSTACK-6191.
>
>> -Original Message-
>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: Saturday, July 12, 2014 11:02 AM
>> To: dev
>> Subject: Re: [DISCUSS]CLOUDSTACK-6191
>>
>> -0 What does it fix and is the solution
t: Re: [DISCUSS]CLOUDSTACK-6191
>
> -0 What does it fix and is the solution bonifide. We should fix the test
> suite if
> it is. The test suite not working is not enough reason to revert a commit, it
> should block the test-suite because the system is broken, not because of
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-7051
>
> Regards,
> Rayees
>
> -Original Message-
> From: Edison Su [mailto:edison...@citrix.com]
> Sent: Friday, July 11, 2014 2:49 PM
> To: dev@cloudstack.apache.org
> Subject: [DISCUSS]CLOUDSTACK-6191
>
> Move
PM
To: dev@cloudstack.apache.org
Subject: [DISCUSS]CLOUDSTACK-6191
Move the discussion to the list about CloudStack-6191:
Automation test is blocked by this bug, we need to find a solution. My
suggestion is sort-of-revert-the-patch, but still give admin the opportunity to
specify the way to
Move the discussion to the list about CloudStack-6191:
Automation test is blocked by this bug, we need to find a solution. My
suggestion is sort-of-revert-the-patch, but still give admin the opportunity to
specify the way to optimize KVM volume creation. The reasons:
1. End user shouldn't
