FlatNetworking
2016-01-17 09:55
267 查看
FlatNetworking
FlatNetworking uses ethernet adapters configured as bridgesto allow network traffic to transit between all the various nodes. This setup can be done with a single adapter on the physical host, or multiple. This option _*does not*_ require a switch that does VLAN tagging (VLANNetworking does) - and is a common development
installation or proof of concept setup.
Single Adapter, All in one setup
extremely common development setup![](https://wiki.openstack.org/w/images/9/92/FlatNetworkSingleInterfaceAllInOne.png)
Multiple nodes with a single adapter
smoke testing, proof of concept layout![](https://wiki.openstack.org/w/images/c/cd/FlatNetworkSingleInterface.png)
Multiple nodes, multiple adapters
server setup with separate admin and data traffic![](https://wiki.openstack.org/w/images/3/33/FlatNetworkMultInterface.png)
Outbound Traffic Flow
In any set up with FlatNetworking, the host with `nova-network`on it is responsible for forwarding traffic from the private network configured with the {{--fixed_range=...} directive in nova.conf. This host needs to have br100 configured and talking to any other nodes that are hosting VMs. With either of the Flat Networking
options, the default gateway for the virtual machines is set to the host which is running `nova-network`. You must set the --flat_network_bridge flag or create networks with the bridge parameter in order to avoid raising an error.
Single adapter hosts
When a virtual machine sends traffic out to the public networks, it sends it first to it's default gateway (where ever `nova-network` is configured)![](https://wiki.openstack.org/w/images/3/3d/SingleInterfaceOutbound_1.png)
Then the host on which `nova-network` is configured acts as a router and forwards the traffic out to the Internet.
![](https://wiki.openstack.org/w/images/8/8c/SingleInterfaceOutbound_2.png)
#!wiki caution If you're using a single interface, then that interface (often eth0) needs to be set into promiscuous mode for the forwarding to happen correctly. This _does not_ appear to be needed if you're running with physical hosts that have and use two interfaces.
Multiple adapter hosts
When a virtual machine sends traffic out to the public networks, it sends it first to it's default gateway (where ever `nova-network` is configured). In a multiple adapter setup, this is over the adapter that is configured as a bridge interface and connectedto the other hosts via a switch.
![](https://wiki.openstack.org/w/images/1/17/MultiInterfaceOutbound_1.png)
Then the host on which `nova-network` is configured acts as a router and forwards the traffic out to the Internet. Typically over the second interface, which has been configured with the hosts internet IP address.
![](https://wiki.openstack.org/w/images/9/90/MultiInterfaceOutbound_2.png)
Inbound Traffic
For inbound traffic (assuming a floating IP address has been set up), the `nova-network` host is responsible for hosting that IP address and doing the DNAT/SNAT addressing to route the traffic to the appropriate virtual machine.
相关文章推荐
- jq学习
- HDU 1241
- Android中进程生命周期的优先级
- Tomcat:The selected server is enabled 异常解决办法
- poj3468 splay(成段跟新 区间求和)
- 奔波
- StringUtils.isBlank()函数
- boost学习2.6:data_time库(2,处理日期)
- 拆解一个简单的KeyFile保护
- 马太效应
- 【Linux】下为普通用户添加sudo权限
- 死锁的四个必要条件
- java封装、继承和多态
- 批处理
- 小火箭
- PHP错误Warning: Cannot modify header information - headers already sent by解决方法
- HTML 页面源代码布局介绍
- JQuery实现网页右侧随动广告特效
- UID详解
- tyvj 笔记本电脑