8:37 a.m.
Date: Sun, 12 Jul 2015 15:45:26 -0400
From: amuller(a)redhat.com
To: bderzhavets(a)hotmail.com
CC: apevec(a)gmail.com; rdo-list(a)redhat.com
Subject: Re: [Rdo-list] What happens to RDO Kilo on Fedora 22 ?
Can you paste openvswitch agent and L3 agent logs on the network node
when you spawn a VM and the router loses its qr/qg interfaces?
I've rebuild via packstack 3 F22 VMs hosting Controller,Network,Compute Node
Libvirt subnet for emulating external sub-net was as follows
# cat public.xml
<network>
<name>public</name>
<uuid>d0e9965b-f92c-40c1-b749-b609aed42cf2</uuid>
<forward mode='nat'>
<nat>
<port start='1024' end='65535'/>
</nat>
</forward>
<bridge name='virbr2' stp='on' delay='0' />
<mac address='52:54:00:60:f8:6d'/>
<ip address='172.24.4.225' netmask='255.255.255.240'>
<dhcp>
<range start='172.24.4.226' end='172.24.4.238' />
</dhcp>
</ip>
</network>
Attempt to create public sub-net via dashboard failed with message, that
172.24.4.225 is incorrect gateway dor 172.24.4.224/28
Then I created this sub-net via CLI as admin. This time ( more powerful box )
qrouter-namespace kept staying in normal shape (ifconfig) , but I was unable to ping
gateway 172.24.4.225 from Network Node with qg-xxxxx (172.24.4.226) and br-ex
172.24.4.232
# source keystonerc_admin
# ip netns exec qrouter-namespace ping -c 3 172.24.4.225
hanged
Same results I got for Network 174.24.4.192 / 26 gateway 174.24.4.193
Then I rebuilt external (neutron) and corresponding libvirt sub-net in way it always
been used for AIO
and two node installs (network XXX.XXX.XXX.0/24 , gateway XXX.XXX.XXX.1) .
# cat public.xml
<network>
<name>public</name>
<uuid>d0e9965b-f92c-40c1-b749-b609aed42cf2</uuid>
<forward mode='nat'>
<nat>
<port start='1024' end='65535'/>
</nat>
</forward>
<bridge name='virbr2' stp='on' delay='0' />
<mac address='52:54:00:60:f8:6d'/>
<ip address='192.168.174.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.174.2' end='192.168.174.254' />
</dhcp>
</ip>
</network>
In other words used 192.168.174.0/24 as external sub-net. This time I succeeded with
sub-net
creation via Dashboard. I became able to ping 192.168.174.1 via both qrouter or qdhcp
namespaces
Outbound/inbound connectivity was tested OK for Cirros 0.3.4 and F22 cloud VMs.
In meantime I believe that network calculator invoked for creating sub-nets is broken.
Another issue is creating ext net via CLI which allows to create unreachable gateway.
----- Original Message -----
> To enable packstack on F22 there is a hack :-
>
> # dnf install -y https://rdoproject.org/repos/rdo-release.rpm
> # dnf install -y openstack-packstack
> # dnf install -y fedora-repos-rawhide
> # dnf --enablerepo=rawhide update openstack-packstack
>
> along with disabling Neutron verification section in provision_demo.pp it
> allows AIO and
> Two node "Controller&&Network and Compute" RDO Kilo packstack
installs on F22
> VMs and bare metal boxes.
> However, splitting Controller and Network Nodes, e.g. three node packstack
> install appears not to be able to work
> in meantime, regardless successful packstack completion.
> What, actually, happens ? I am able to create external net and sub-net only
> via CLI (as admin) and change status to shared.
>
> Attempt to launch VM results qrouter-namespace to loose qg-xxxx, qr-yyyy
> interfaces.
> Outbound/inbound packets forwarding gets broken as soon as VM gets started.
> Only when nova and neutron
> services are running on the same node it doesn't happen. It's just my
> personal experience.
> RDO Kilo Three node deployment on CentOS 7.1 works fine.
>
> Thanks.
> Boris.
>
>
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe(a)redhat.com