This is not related to portable IP. This enforcement was added as part of
commit 657d9e4789d73c7c8ed460e59f088b8cb9aa7697.

Anothony might have context for this check.

On 11/06/14 2:18 PM, "Andrija Panic" <andrija.pa...@gmail.com> wrote:

>It was not there pre 4.3, and it's just causing me problems, I had to
>manually add database entries to vlan and user_ip_address tables, not very
>convinient...
>Thanks,
>Andrija
>
>
>On 11 June 2014 02:45, Chiradeep Vittal <chiradeep.vit...@citrix.com>
>wrote:
>
>> Not sure what this has to do with Portable IP. But I agree that the
>>check
>> should be removed.
>>
>> From: ilya musayev <ilya.mailing.li...@gmail.com<mailto:
>> ilya.mailing.li...@gmail.com>>
>> Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
>><
>> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
>> Date: Friday, June 6, 2014 at 10:38 AM
>> To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <
>> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
>> Subject: Re: Anybody addressing this bug ? Overlaping IP subnets across
>> different vlans
>>
>> Andrija
>>
>> I dont know if we can qualify this as a bug, this check was placed with
>> some purpose in mind - yet its not clear what it is and why would
>> someone think its bad.
>>
>>
>> 
>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=a3b1a
>>49c303a929c754561ca07fd8a9ed84e0382
>>
>> https://issues.apache.org/jira/browse/CLOUDSTACK-3911
>>
>> Chime in on the discussion in thread above,
>>
>> Regards,
>> ilya
>>
>>
>> On 6/6/14, 5:48 AM, Andrija Panic wrote:
>> Hi,
>> aftger upgrade to 4.3, I reported a bug where CS will not let me add
>> additional IP ranges.... when there are 2 vlans using same IP range - I
>> don't see point comparing IP ranges across two separate broadcast
>> domains...
>>
>> https://issues.apache.org/jira/browse/CLOUDSTACK-6814
>>
>> Thanks,
>>
>>
>>
>
>
>-- 
>
>Andrija Panić
>--------------------------------------
>  http://admintweets.com
>--------------------------------------
>


Reply via email to