[openstack-dev] Re: [neutron]How to use external_net?

于洁 16189455 at qq.com
Fri Jul 31 01:28:28 UTC 2015

Thank you Cédric/ZZelle,
I have tried this way before, but it could not realize the connection between two networks belongs to different tenants. So the floatingIP comes from tenant A could not bind to VM from tenant B.
Do you have any suggestion about this?


------------------ 原始邮件 ------------------
发件人: "ZZelle";<zzelle at gmail.com>;
发送时间: 2015年7月30日(星期四) 晚上7:21
收件人: "OpenStack Development Mailing List (not for usage questions)"<openstack-dev at lists.openstack.org>; 

主题: Re: [openstack-dev] [neutron]How to use external_net?


You need a router to bind internal network(s) with external network.

Otherwise you cannot allocate a floating ip (on the external network) to VMs (on internal network(s)).

The doc[1] explains how to do it.

[1] http://docs.openstack.org/kilo/install-guide/install/apt/content/neutron_initial-tenant-network.html


On Thu, Jul 30, 2015 at 1:08 PM, 于洁 <16189455 at qq.com> wrote:
Hi all,
      I find that if setting the value of router:external=True for a net(example: neutron net-update netID --router:external=True)
      Users in other tenants could allocate floating IP from this net(example: neutron floatingip-create netID).
      But how could this floating IP bind to a VM created by the user from other tenants? The network is unreachable.
      Or do I misunderstand the function?


 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150731/3295a185/attachment.html>

More information about the OpenStack-dev mailing list