[Openstack] 答复: Does compute node require provider network?
Rui Mao
maorui2k at 163.com
Thu May 19 09:08:44 UTC 2016
I don’t want VMs exposed to Internet directly, and I don’t have enough Internet IP address for every compute node.
Is it possible that the compute nodes only attach to management and tenant network and access internet via NAT?
Best regards,
Rui Mao
发件人: Neil Jerram [mailto:neil at tigera.io]
发送时间: 2016年5月19日 16:20
收件人: Rui Mao <maorui2k at 163.com>; openstack at lists.openstack.org
主题: Re: [Openstack] Does compute node require provider network?
If you attach a VM to a provider network - instead of to a tenant network - and give it an Internet-routable fixed IP address, it can access the Internet without any NAT. This has been the case for several OpenStack releases.
Now that Neutron has address scopes, I believe it will soon be the case that a Neutron virtual router will avoid NAT when forwarding traffic between networks with the same address scope. That means that it should soon be possible for VMs attached to tenant networks to access the Internet without any NAT, too.
Regards,
Neil
On Thu, May 19, 2016 at 6:02 AM Rui Mao <maorui2k at 163.com <mailto:maorui2k at 163.com> > wrote:
http://docs.openstack.org/mitaka/install-guide-ubuntu/environment-networking.html#environment-networking
In the guide, the compute node requires a provider network connection, and the neutron run in controller node.
But per my understanding, all VMs access the internet via NAT, and the nova node has no internet access requirement in production environment.
Anything I missed or misunderstood?
Best regards,
Rui Mao
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack at lists.openstack.org <mailto:openstack at lists.openstack.org>
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160519/ccc3c740/attachment.html>
More information about the Openstack
mailing list