running ovn-sbctl/ovn-nbctl commands in the leader in difficult

[Felipe Reyes]

Since 21.03 the leader may change fairly often as described in the bug 1981091, from a usability perspective this is hard, the sysadmin needs to use the ovn-central ip addresses + certificates to connect and run ovn-*ctl commands which ends up being a large command, or constantly ssh to a different host chasing where the leader is.

It would be nice if the charm could alleviate some of this pain, for example defining a environment varible with all the connection information.

For example etcd uses cli flags and environment variables to determine connection information (e.g. certificates, api versions, etc) https://etcd.io/docs/v3.4/op-guide/configuration/