Configure internal and external network communication (virtual machine Intranet)

Environment Description:

Set up several virtual machines on the server, with the OpenStack environment built by fuel

Due to deployment, the extranet segment set for OpenStack is not an extranet segment in the real world, resulting in the inability to access the dashboard page on the physical machine

The entire environment is deployed on the server, so the server can be connected to the OpenStack extranet

The reason for viewing the command on the server is that there are two bridges, one bridge is connected to the actual physical extranet and the other is the OpenStack extranet

Problem solved: Allow your physical machine to connect to OpenStack's extranet

For example work network 192.168.10.0/24

OpenStack Network 172.16.10.0/24

Method:

1. Create a pair of virtual network cards on the server

# IP link Add virbr-br0 type Veth peer name BRO-VIRBR (http://blog.chinaunix.net/uid-27017686-id-5057025.html here is about VE Introduction of TH Peer)

2. Add two NICs to two bridges with Brctl

3. Start two virtual network cards respectively

# IP link Set xxx up

4. Configure the corresponding network segment on your own physical machine

IP addr Add xxxxxxx/xx dev eth0

This article is from the "11791489" blog, please be sure to keep this source http://11801489.blog.51cto.com/11791489/1794536

Configure internal and external network communication (virtual machine Intranet)