Interfaces for ovn-exporter

To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.


  • name: ovn-exporter

  • description: ovn-exporter exposes key metrics from Open Virtual Network (OVN) and Open vSwitch (OVS) to Prometheus.

  • snapcraft: ovn-exporter/snap/snapcraft.yaml at main · canonical/ovn-exporter · GitHub

  • upstream: None

  • upstream-relation: None

  • interfaces:

    • <interface-name>: ovn-chassis
      • request-type: manual-connection
      • reasoning: Need access to ovn related files to get the metrics
    • <interface-name>: ovn-central-data
      • request-type: manual-connection
      • reasoning: Need access to ovn related files to get the metrics
  • hooks:

    • configure: snapd-control
    • connect-plug-ovn-chassis: snapd-control
    • connect-plug-ovn-central-data: snapd-control

Hi @review-team , as a published for ovn-exporter snap I would like to request above interfaces for plugs & hooks. Please check the ovn-exporter project to understand it more: GitHub - canonical/ovn-exporter

This request has been added to the queue for review by the @reviewers team.

Hello @jneo8 snapd-control is a super privileged interface that allows to circumvent all confinement so is not generally granted. Can you clarify why it’s required? As alternative, did you try to use system-files or system-observe ?

Hi @pfsmorigo

Thanks for the response. So we don’t need the snapd-control anymore. Please see the latest PR of removing the snapd-control. build: Remove snapd-control by jneo8 · Pull Request #15 · canonical/ovn-exporter · GitHub

But we still not able to release the snap, so I guess we still need some manual review approval?

$ snapcraft release ovn-exporter 2 latest/edge
Store operation failed:
- resource-not-ready: Snap cannot be published due to inconsistent state.

Revisions #2 and #3 of your snap were blocked by revision #1. I reject #1 and automatic review is now running for #2. No issues have been identified for #2 or #3, so you should be able to release them now.

1 Like

It’s been successfully released, thanks for the help. @jslarraz ++