>>
>>> -Original Message-
>>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>>> Sent: Wednesday, 19 February 2014 8:33 PM
>>> To: dev; Kishan Kavala
>>> Subject: Re: cidrs in acls
>>>
>>> Kishan,
>>>
>>>
: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: Wednesday, 19 February 2014 8:33 PM
>> To: dev; Kishan Kavala
>> Subject: Re: cidrs in acls
>>
>> Kishan,
>>
>> Can you have a look at the branch acl-item-cidrs. I made some code to
>> handle the c
grade path to move existing cidrs to new
network_acl_item_cidr table
Regards,
kishan
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Wednesday, 19 February 2014 8:33 PM
> To: dev; Kishan Kavala
> Subject: Re: cidrs in acls
>
> Kishan
ore acl
>> cidrs. Maybe in network_acl_item_cidrs.
>>
>> Regards,
>> kishan
>>
>>> -Original Message-
>>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>>> Sent: Friday, 17 January 2014 1:05 AM
>>> To: Kishan Kavala
>>
gards,
> kishan
>
>> -Original Message-
>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: Friday, 17 January 2014 1:05 AM
>> To: Kishan Kavala
>> Cc: dev
>> Subject: cidrs in acls
>>
>> H Kishan,
>>
>> I see you im
la
> Cc: dev
> Subject: cidrs in acls
>
> H Kishan,
>
> I see you implemented CLOUDSTACK-763. it merges a lot of cidrs into one field.
> The api doesn't check the field length. I enlarged the field in the create
> table
> statement to 2048 for the 4.3 branch. Can you
H Kishan,
I see you implemented CLOUDSTACK-763. it merges a lot of cidrs into
one field. The api doesn't check the field length. I enlarged the
field in the create table statement to 2048 for the 4.3 branch. Can
you help me think about a more solid solution, please. It seems to me
those cidrs shou
