Open Stack

+kevin benton

On 03/28/2017 07:20 AM, Bartłomiej Solarz-Niesłuchowski wrote:
> Dear List,
>
> I am beginner of openstack user.

Welcome to the OpenStack community! :)

> I setup openstack with RDO on Centos 7.
>
> I have 6 machines:
>
> they have two interfaces enp2s0f0  (10.51.0.x) and enp2s0f1 (213.135.46.x)
>
> on machine x=1 i setup dashboard/neutron-server/nova/cinder/etc.. on
> machines 2-6 i setup:
>
> openstack-cinder-api.service,
> openstack-cinder-scheduler.service,
> openstack-cinder-volume.service,
> openstack-nova-api.service,
> openstack-nova-compute.service,
> openstack-nova-conductor.service,
> openstack-nova-consoleauth.service,
> openstack-nova-novncproxy.service,
> openstack-nova-scheduler.service

I am presuming you want machines 2-6 as "compute nodes" to put VMs on? 
If so, you definitely do not want to put anything *other* than the 
following on those machines:

openstack-cinder-volume.service
openstack-nova-compute.service

All the other services belong on a "controller node", where you've put 
the neutron server, dashboard, database, MQ, etc.

> I run the virtual machine instance which have ip 10.0.3.4 (on machine 5)
>
> I setup router on machine 1
>
> I can ping from the virtual instance ip of router.
>
> I see pings from wirtual machine on machine 1 (where sit router)

err, it looks to me that your machine 1 is a controller, not a compute 
node? VMs should go on machines 2-6, unless I'm reading something 
incorrectly.

> But i have totally no idea how to setup network connectivity with
> outside world.

<snip>

> [root at song-of-the-seas-01 ~(keystone_admin)]# ip ro
> default via 213.135.46.254 dev br-ex

So here is your default gateway, on br-ex...

> 10.51.0.0/24 dev enp2s0f0  proto kernel  scope link  src 10.51.0.1
> 213.135.46.0/24 dev br-ex  proto kernel  scope link  src 213.135.46.180
>
> [root at song-of-the-seas-01 ~(keystone_admin)]# ip a | grep state
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
> 2: enp2s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state
> UP qlen 1000
> 3: enp2s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master
> ovs-system state UP qlen 1000
> 4: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen
> 1000
> 5: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
> 6: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
> UNKNOWN qlen 1000

And here, it's indicating br-ex is in an unknown state. Also, br-int is 
in DOWN state, not sure if that is related. My guess would be to bring 
up br-ex and see what is failing about the bring-up.

Of course, I'm no networking expert so hopefully one of the Neutron devs 
can pop in to help. :)

Best,
-jay

> 7: vxlan_sys_4789: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65470 qdisc
> noqueue master ovs-system state UNKNOWN qlen 1000
> 8: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
>
> [root at song-of-the-seas-01 ~(keystone_admin)]# tcpdump -i vxlan_sys_4789
> tcpdump: WARNING: vxlan_sys_4789: no IPv4 address assigned
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on vxlan_sys_4789, link-type EN10MB (Ethernet), capture size
> 65535 bytes
> 13:18:26.060031 IP 10.0.3.4 > see-you-later.wsisiz.edu.pl: ICMP echo
> request, id 3713, seq 36985, length 64
> 13:18:27.060032 IP 10.0.3.4 > see-you-later.wsisiz.edu.pl: ICMP echo
> request, id 3713, seq 36986, length 64
> 13:18:28.060057 IP 10.0.3.4 > see-you-later.wsisiz.edu.pl: ICMP echo
> request, id 3713, seq 36987, length 64
> 13:18:29.060006 IP 10.0.3.4 > see-you-later.wsisiz.edu.pl: ICMP echo
> request, id 3713, seq 36988, length 64
>
>
>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>