[neutron] do we need neutron-openvswitch-agent running in order to make VMs spawned with provider network?

Slawek Kaplonski skaplons at redhat.com
Fri Feb 21 15:43:17 UTC 2020


Stopping neutron-ovs-agent shouldn’t cause any failure on data plane for existing VMs. You should check if open flow rules are there in place and where exactly connectivity is broken on the host.

> On 21 Feb 2020, at 11:32, Chen CH Ji <jichenjc at cn.ibm.com> wrote:
> We are running provider network with VLAN /FLAT, does the neutron-openvswitch-agent is mandatory to be running in order to make the VM deployed able to connect outside? 
> e.g. I have a VM   instance-00000027, I login the VM and ping out side, in the mean time, use another session to 
> systemctl stop  neutron-openvswitch-agent.service then wait for a few minutes, the ping will stop, does this is an expected behavior?
> I know nova-compute is not running won't affect VM functionality, but does neutron openvswitch agent is needed or not? Thanks a lot
> [root at kvm02 ~]# virsh list
>  Id   Name                State
> -----------------------------------
>  4    instance-00000027   running
> [root at kvm02 ~]# virsh console 4
> Connected to domain instance-00000027
> Escape character is ^]
> [root at dede ~]# ping
> [root at dede ~]# ping
> PING ( 56(84) bytes of data.
> 64 bytes from icmp_seq=1 ttl=64 time=19.8 ms
> 64 bytes from icmp_seq=2 ttl=64 time=0.667 ms
> 64 bytes from icmp_seq=3 ttl=64 time=0.774 ms
> Ji Chen
> z Infrastructure as a Service architect
> Phone: 10-82451493
> E-mail: jichenjc at cn.ibm.com

Slawek Kaplonski
Senior software engineer
Red Hat

More information about the openstack-discuss mailing list