Support ovn-controller configuration file

[Richard Theis]

The OVN controller is currently configured used ovs-vsctl commands as part of the DevStack plugin. To improve the deployment experience, it would be nice to provide an OVN controller configuration file to replace some of these commands.

Here are some of the commands to consider replacing:
ovs-vsctl --no-wait set open_vswitch . system-type="devstack"
ovs-vsctl --no-wait set open_vswitch . external-ids:system-id="$OVN_UUID"
ovs-vsctl --no-wait set open_vswitch . external-ids:ovn-remote="$OVN_SB_REMOTE"
ovs-vsctl --no-wait set open_vswitch . external-ids:ovn-bridge="br-int"
ovs-vsctl --no-wait set open_vswitch . external-ids:ovn-encap-type="geneve"
ovs-vsctl --no-wait set open_vswitch . external-ids:ovn-encap-ip="$HOST_IP"

[Numan Siddique (numansiddique)]

@Sanjay - I assume you are working on this. In case not, let me know I can take it up :)

[Sanjay Verma (sanverm2)]

@Numan - I am currently not working on this. You may take it up.

[Numan Siddique (numansiddique)]

@Sanjay - Thanks for the reply

[Numan Siddique (numansiddique)]

Unassigning as i am not able to look into this activity.

[Russell Bryant (russellb)]

One way to approach this would be to add it to ovn-ctl (a shell script for starting/stopping ovn services). If it finds a config file, it could set the values in the db for you before starting ovn-controller. That seems like an easy way to do this...

[Pranab (pranabjb)]

Hi Russell,
This is my bug fix attempt, so please bear with me. These questions might sound silly.

1) Isn't the script ovn-ctl part of the package openvswitch ? And, we have tried experimenting openvswitch-ovn in a non-openstack set-up. This bug affects there too. So, I am guessing this bug should affect openvswitch project too and we should resolve this as a part of openvswitch project?

2) I don't think networking-ovn project has any way to configure the ovn-ctl script ? I might be wrong here.

Thanks

[Numan Siddique (numansiddique)]

You are right. This bug needs to be addressed in openvswitch and not networking-ovn. Hence we have tagged this bug as "ovn-upstream" for us to track :)

[Pranab (pranabboruah)]

Unable to spend time on this. Sorry.