Thanks Brian.
That's a very much needed implementation.
On Tue, Apr 26, 2016 at 10:55 PM, Brian Haley wrote:
> On 4/26/16 12:05 PM, Jaison Peter wrote:
>
>> Hi George,
>>
>> Thanks for letting me know that we can create distributed router by
>> disabling SNAT in central router.
>>
>> Even thou
On 04/26/2016 10:16 AM, Rick Jones wrote:
On 04/25/2016 11:33 PM, Jaison Peter wrote:
But one of the major drawback we are seeing with DVR is the public IP
consumption.If we have 100 clients and 1 VM per client , eventually
there will be 100 tenants and 100 routers. Since its a public cloud, we
On 4/26/16 12:05 PM, Jaison Peter wrote:
Hi George,
Thanks for letting me know that we can create distributed router by
disabling SNAT in central router.
Even though we use VRRP HA router, it will consume 100 public IPs in the
scenario I mentioned above, but can save IPs used in compute fip nam
On 04/25/2016 11:33 PM, Jaison Peter wrote:
I have many concerns about the scaling and right choices , since
openstack is offering lot of choices and flexibility, especially in
networking side.Our major challenge was choosing between simplicity and
performance offered by Linux bridge and feature
Hi George,
Thanks for letting me know that we can create distributed router by
disabling SNAT in central router.
Even though we use VRRP HA router, it will consume 100 public IPs in the
scenario I mentioned above, but can save IPs used in compute fip namespace.
Yes, compute node do not need publ
Hi Jaison,
This is an issue that the Neutron team is aware. They will likely be
addressing this (at some point) but your understanding aligns with my own.
So, public IPV4 usage is a well known, well documented issue and DVR / HA
exacerbates it.
On Tue, Apr 26, 2016 at 1:33 AM, Jaison Peter wrote
There's no shortage of public IPv6 addresses.
Regards,
Mike
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ope
Yes, thats also an option. But we would like to get the flexibility and
features that a floating IP provides.
So, in that case, there wont be any floating IPs , openstack will assign
public IPs like it assigning private IPs , right?
On Tue, Apr 26, 2016 at 12:57 PM, gustavo panizzo (gfa)
wrote:
On Tue, Apr 26, 2016 at 12:03:03PM +0530, Jaison Peter wrote:
> Hi all,
>
> I was working in an openstack project to build a small to medium level
> public cloud on the top of openstack. We are researching lot more about
> scalable large openstack deployments and planning our design accordingly.
