> From: "Russell Bryant" <russ...@ovn.org> > What would you think of changing the DEFAULT_REMOTE option to be > CREATE_REMOTE to more clearly indicate that the option is telling ovn-ctl > that we want it to go ahead and set up a remote for us. >
Sounds good, I think CREATE_REMOTE is a better name. > When CREATE_REMOTE is "yes", instead of adding it to the ovsdb-server > command line, how about we add it to to the Connection table. That way we > can add support for some additional options. This came up from our need to Makes sense, having the remote configuration in the db would give us more flexibility. > set the inactivity_probe option. Presumably we could add some more options > to this script to let you enable SSL through options, as well. > > Numan had a start at a patch doing something like this here, but it > probably makes sense to just integrate with your patch. > > https://github.com/numansiddique/overcloud_image_for_ovn/blob/master/patches/ovs-0005-ovn-ctl-Add-remotes-in-Connection-table-of-NB-and-SB.patch > Thanks, I will steal some of that :-) I'll incorporate and post v2 shortly. Thanks, Lance > > > Regards, > > > > Lance > > > > > Some thing like below > > > > > > ######### > > > if test X"$DB_NB_DEFAULT_REMOTE" = Xno; then > > > ovn-nbctl set-connection "ptcp:$DB_NB_PORT:$DB_NB_ADDR" > > > fi > > > ######### > > > > > > Thanks > > > Numan > > > > > > > > _______________________________________________ > > dev mailing list > > d...@openvswitch.org > > https://mail.openvswitch.org/mailman/listinfo/ovs-dev > > > > > > -- > Russell Bryant > _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev