openstack team mailing list archive
Mailing list archive
Re: Quantum question
One more thing to this slide there is a physical router that can be configured by the admin etc and I can do a port mapping from there so why the floating will not be an option? Not clear again.
Inviato da iPad ()
Il giorno Jul 13, 2013, alle ore 15:26, Remo Mattei <remo@xxxxxxxxxx> ha scritto:
> So if I add a virtual router I will have this working the models are not well describe why and that is a problem not only to me but others as well when to choose which one etc.
> Inviato da iPad ()
> Il giorno Jul 13, 2013, alle ore 13:44, Staicu Gabriel <gabriel_staicu@xxxxxxxxx> ha scritto:
>> Hi Remo,
>> If your talking about this document: http://docs.openstack.org/grizzly/openstack-network/admin/content/use_cases_single_flat.html I think that in that case you don't have something from the logical point of view something like a router. You just have L2 segments so there is no place where NAT can happen and therefore you can not use floating ip notion.
>> In floating ip case practically the framework creates a static NAT between the floating ip and the private ip that the instance receive when boots up.
>> From: Remo Mattei <remo@xxxxxxxxxx>
>> To: openstack@xxxxxxxxxxxxxxxxxxx
>> Sent: Saturday, July 13, 2013 11:23 PM
>> Subject: [Openstack] Quantum question
>> Hello everyone I was reading the doc and it was saying that model one on quantum does not support floating ip address and I wonder why this limitation
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp