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

2015-07-30 Thread ????
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


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

2015-07-30 Thread yatin kumbhare
Hi,

I'm guessing tenant A is admin tenant.

Also, you can check the iptables NAT rules under router namespace in case
of ovs plugin.

You should find binding there.

Regards,
Yatin

On Fri, Jul 31, 2015 at 6:58 AM, 于洁 16189...@qq.com wrote:

 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


__
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