Search code examples
networkingintegrationopenstackopendaylightopenvswitch

Integration Opendaylight, OVSDB. Creation of new Manager at Reboot

I carry out the integration between OpenDayLight and OVS through OVSDB in order to realize a ecosystem in which OpenStack is integrated with OpenDayLight and NetVirt for the Virtualization of Tenant Network. When I set the manager in OVS. Every works: The Manager and the Controller works. When I reboot the machine, only the Controller has the label "is_connected:true". Moreover when I reboot a new Manager add in the OVS. 

6735bd9d-3575-44fb-a1a3-6ddbf10307e9
    Manager "ptcp:6640:127.0.0.1"
    Manager "tcp:10.0.0.11:6640"
    Bridge br-int
        Controller "tcp:10.0.0.11:6653"
            is_connected: true
        fail_mode: secure
        Port br-int
            Interface br-int
                type: internal
        Port "tun65171854b4b"
            Interface "tun65171854b4b"
                type: vxlan
                options: {key=flow, local_ip="10.0.0.11", remote_ip="10.0.0.31"}
    ovs_version: "2.9.5"
Solution

  • I solve the problem. The service named "neutron-ovs-cleanup" create the manager every reboot. Disabling it or uninstalling openvswitch-agent (It is not needed with opendaylight ml2 driver) the problem is solved.