Alias request for various microovn binaries

store-requests
1

Hello,

We would like to request alias for following binaries:

  • ovn-appctl
  • ovn-nbctl
  • ovn-sbctl
  • ovn-trace
  • ovs-appctl
  • ovs-dpctl
  • ovs-ofctl
  • ovs-vsctl
  • ovsdb-tool
  • ovsdb-client

In the MicroOVN snap. This snap is intended as an alternative distribution and deployment method for OVN/OVS packages. Currently, all these binaries need to be prefixed with microovn. which is slightly cumbersome, but more importantly, it prevents us to act as a drop-in replacement for the packaged OVN/OVS.

Side question: If the alias request is granted, would these aliases be activated for the whole snap, or is it possible to limit them only to certain channels?

(cc @fnordahl @crypticcoder )

1 Like
2

:+1: i agree, this would be very useful regarding certain issues

3

Hey folks,

Those aliases sounds reasonable to me and I could not find any obvious conflict. Thus +1 from me.

Side question: If the alias request is granted, would these aliases be activated for the whole snap, or is it possible to limit them only to certain channels?

AFAIK, there is no way to limit them certain channels

4

Thanks Jorge,

Not a problem, I was just curious if we can limit this change of behavior only to the new release.

5

+1 from me as well as they are reasonable for the snap. +2 votes for, 0 votes against, granting auto-alias of:

  • ovn-appctl
  • ovn-nbctl
  • ovn-sbctl
  • ovn-trace
  • ovs-appctl
  • ovs-dpctl
  • ovs-ofctl
  • ovs-vsctl
  • ovsdb-tool
  • ovsdb-client

This is now live.

1 Like