Thanks for your reply.
I am deploying neutron using linuxbridge, not OpenVSwitch. I have finished the
deployment according to the official document, and created vm successfully, but
either in controller node or in vm I can't ping the external network. so I
doubt that the question is related to my network interface. I show you some
output:
Ifconfig:
brq1454236c-20: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.81.66 netmask 255.255.255.0 broadcast 192.168.81.255
inet6 fe80::210:c6ff:feb0:ae66 prefixlen 64 scopeid 0x20<link>
ether 00:10:c6:b0:ae:66 txqueuelen 1000 (Ethernet)
RX packets 600449 bytes 179184712 (170.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 304969 bytes 89025587 (84.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
brq744bc436-73: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450
inet6 fe80::542c:37ff:fee3:1e21 prefixlen 64 scopeid 0x20<link>
ether 3a:73:ea:c9:ae:0a txqueuelen 1000 (Ethernet)
RX packets 30 bytes 2916 (2.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 9 bytes 738 (738.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.81.66 netmask 255.255.255.0 broadcast 192.168.81.255
inet6 fe80::210:c6ff:feb0:ae66 prefixlen 64 scopeid 0x20<link>
ether 00:10:c6:b0:ae:66 txqueuelen 1000 (Ethernet)
RX packets 761924 bytes 216695855 (206.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 383314 bytes 115348831 (110.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf7f00000-f7f20000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 3092776 bytes 848833143 (809.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3092776 bytes 848833143 (809.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tap05af3e12-74: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fceb:41ff:fe87:341a prefixlen 64 scopeid 0x20<link>
ether fe:eb:41:87:34:1a txqueuelen 1000 (Ethernet)
RX packets 14 bytes 1124 (1.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 239462 bytes 33135870 (31.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tap2b5a00e2-af: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450
inet6 fe80::3873:eaff:fec9:ae0a prefixlen 64 scopeid 0x20<link>
ether 3a:73:ea:c9:ae:0a txqueuelen 1000 (Ethernet)
RX packets 195 bytes 22891 (22.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 220 bytes 21766 (21.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tap3f41d558-0e: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::ac85:a7ff:fe7f:591 prefixlen 64 scopeid 0x20<link>
ether ae:85:a7:7f:05:91 txqueuelen 1000 (Ethernet)
RX packets 652 bytes 28136 (27.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 238382 bytes 33028809 (31.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tap6b4cd1e2-2d: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450
inet6 fe80::ac9a:5fff:fedc:f831 prefixlen 64 scopeid 0x20<link>
ether ae:9a:5f:dc:f8:31 txqueuelen 1000 (Ethernet)
RX packets 154 bytes 17498 (17.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 249 bytes 24745 (24.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:2e:c2:95 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vxlan-43: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450
inet6 fe80::542c:37ff:fee3:1e21 prefixlen 64 scopeid 0x20<link>
ether 56:2c:37:e3:1e:21 txqueuelen 1000 (Ethernet)
RX packets 403 bytes 34480 (33.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 321 bytes 33963 (33.1 KiB)
TX errors 0 dropped 17 overruns 0 carrier 0 collisions 0
[root@controller opst]# ip netns qrouter-45dbbf8e-6c93-486b-a23d-aabddae931db
(id: 2)
qdhcp-744bc436-73b4-4e00-a41e-2698a5834a97 (id: 1)
qdhcp-1454236c-20d0-412e-902c-2e657aef78dd (id: 0)
[root@controller opst]# ip netns exec
qrouter-45dbbf8e-6c93-486b-a23d-aabddae931db ping -c 4 192.168.81.66 PING
192.168.81.66 (192.168.81.66) 56(84) bytes of data.
From 10.10.1.101 icmp_seq=1 Destination Host Unreachable From 10.10.1.101
icmp_seq=2 Destination Host Unreachable From 10.10.1.101 icmp_seq=3 Destination
Host Unreachable From 10.10.1.101 icmp_seq=4 Destination Host Unreachable
--- 192.168.81.66 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 2999ms
pipe 4
Thanks very much
Li yulei
-----邮件原件-----
发件人: Tomas Vondra [mailto:[email protected]]
发送时间: 2016年4月12日 16:39
收件人: [email protected]
主题: Re: [Openstack] [Neutron] Deploying Liberty Neutron needs how many NICs
liyulei <liyulei_walker@...> writes:
>
>
> Hello,
>
> I am deploying Liberty Neutron in CentOS7, according to the official
document there are two interfaces in controller: one for management, the other
for public, and the public interface uses a special configuration without an IP
address assigned to it. But in my controller, there is only one interface, so
how should I do ? Or do I have to have two interfaces at least ?
>
>
> Thanks
>
> Li yulei
>
Hi!
The official document is more of a best practice in this regard. I remember
that it suggested 3 NICs back when I was installing the Grizzly release.
You may of course use only one interface, but bear in mind that it is highly
managed by Neutron and if something goes wrong, you may get cut off from the
installation. That is when the management NIC comes in handy.
If you're using OpenVSwitch, something like this will add a system port to the
bridge:
ovs-vsctl add-port br-ex intport -- set Interface intport type=internal
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : [email protected]
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : [email protected]
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
