>
>Till 33, it went fine...
>
>Thanks,
>Pradeep S
>
>
>-Original Message-
>From: Min Chen [mailto:min.c...@citrix.com]
>Sent: Friday, January 18, 2013 11:19 AM
>To: cloudstack-dev@incubator.apache.org
>Subject: Re: [MERGE] network refactoring, phase 1
[mailto:min.c...@citrix.com]
Sent: Friday, January 18, 2013 11:19 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [MERGE] network refactoring, phase 1
Nonoss build is broken in master branch, not sure if it is related to this
merge?
[ERROR] Failed to execute goal
gt;>>>
>>>>Thanks
>>>>Animesh
>>>>
>>>>> -Original Message-
>>>>> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
>>>>> Sent: Friday, January 11, 2013 1:08 PM
>>>>> To: CloudSta
ge-
>>>> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
>>>> Sent: Friday, January 11, 2013 1:08 PM
>>>> To: CloudStack DeveloperList
>>>> Subject: Re: [MERGE] network refactoring, phase 1
>>>>
>>>> I'm going to w
u waiting on revert for 312? Murali reverted it today
>>
>>Thanks
>>Animesh
>>
>>> -Original Message-
>>> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
>>> Sent: Friday, January 11, 2013 1:08 PM
>>> To: CloudStack
Vittal [mailto:chiradeep.vit...@citrix.com]
>> Sent: Friday, January 11, 2013 1:08 PM
>> To: CloudStack DeveloperList
>> Subject: Re: [MERGE] network refactoring, phase 1
>>
>> I'm going to wait on the reverts for CLOUDSTACK-306 and CLOUDSTACK-312
>>
>>
Chiradeep
Are you waiting on revert for 312? Murali reverted it today
Thanks
Animesh
> -Original Message-
> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> Sent: Friday, January 11, 2013 1:08 PM
> To: CloudStack DeveloperList
> Subject: Re: [MERGE] netw
I'm going to wait on the reverts for CLOUDSTACK-306 and CLOUDSTACK-312
On 1/11/13 12:15 PM, "Alex Huang" wrote:
>> +1 - with an assumption that Alex and others are OK with it (since the
>> javelin branch merge was proposed first).
>
>+1 We're struggling with the merge right now so one more merge
> +1 - with an assumption that Alex and others are OK with it (since the
> javelin branch merge was proposed first).
+1 We're struggling with the merge right now so one more merge is not going to
hurt very much.
--Alex
On Thu, Jan 10, 2013 at 8:35 PM, Chiradeep Vittal
wrote:
> I would like to merge my network-refactoring branch to master
>
> The main objective of this piece of refactoring was to:
> - reduce and eliminate unneeded dependencies on the orchestration piece
> - move queries to the network data into t
+1
-Original Message-
From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
Sent: Friday, January 11, 2013 7:05 AM
To: CloudStack DeveloperList
Subject: [MERGE] network refactoring, phase 1
I would like to merge my network-refactoring branch to master
The main objective of this
On 1/10/13 5:35 PM, "Chiradeep Vittal" wrote:
>I would like to merge my network-refactoring branch to master
>
>The main objective of this piece of refactoring was to:
>- reduce and eliminate unneeded dependencies on the orchestration piece
>- move queries to the network data into the api project
I would like to merge my network-refactoring branch to master
The main objective of this piece of refactoring was to:
- reduce and eliminate unneeded dependencies on the orchestration piece
- move queries to the network data into the api project
- allow plugins to stop depending on the 'server' co
13 matches
Mail list logo
