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?
Thanks.


YU




------------------ ???????? ------------------
??????: "ZZelle";<zze...@gmail.com>;
????????: 2015??7??30??(??????) ????7:21
??????: "OpenStack Development Mailing List (not for usage 
questions)"<openstack-dev@lists.openstack.org>; 

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



Hi,


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



C??dric/ZZelle











On Thu, Jul 30, 2015 at 1:08 PM, ???? <16189...@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?


Thanks,
Yu

__________________________________________________________________________
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to