Myna parakeet: request for auto-connection

store-requests privileged-interfaces
1 
name: myna-parakeet
description: Parakeet speech-to-text inference snap for Myna
snapcraft: https://github.com/canonical/myna/blob/integration-220627/parakeet-snap/snap/snapcraft.yaml
upstream: https://github.com/canonical/myna
upstream-relation: the publisher is the upstream (Canonical); this snap is built from that repository
plugs:
  hardware-observe:
    request-type: auto-connection
    reasoning: |
      modelctl detects local compute with lscompute, which reads /sys/devices/system/cpu/**,
      /sys/class/drm/** and /sys/bus/pci/**. It backs show-engine,
      use-engine --auto and status, and it runs from the install and
      post-refresh hooks, which choose the engine with no user present.
      Read-only: no device node is opened and nothing is written. Without an
      auto-connection the very first boot silently selects the fallback engine
      and the CLI reports unknown hardware, so a later manual connection
      cannot recover the decision it was needed for.
  system-observe:
    request-type: auto-connection
    reasoning: |
      ONNX Runtime reads /sys/devices/system/cpu/** for core topology and
      /sys/fs/cgroup/** for cpuset/quota info to size its thread pool.
      hardware-observe covers /sys/devices/**; system-observe adds
      /sys/fs/cgroup/** and /proc/**.

Notes for the reviewer

  • The snap is strictly confined and fully offline. There is no network plug anywhere in the fleet: model weights ship as snap components, so nothing is fetched at runtime. network-bind is present only because snapd’s seccomp template gates listen(2) behind it even for an AF_UNIX socket.
  • The snap has no access to audio hardware. It receives PCM pushed by a client over a Unix socket exported through a content slot (ubustt-socket).
  • Both requested interfaces are read-only; neither of them is a super-privileged interface, so no installation grant is being asked for.
2

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

3

Hello @charles05 :slight_smile:

Given the reasoning provided, this is a +1 from my sidee, for auto-connecting thehardware-observe and system-observe interfaces to myna-parakeet!

1 Like
4

Hello all,

Given the provided reasoning, this is also a +1 from me for granting auto-connection for the hardware-observe and system-observe interfaces for the myna-parakeet snap. Thank you!

5

Hello team, I am trying to upload,

$ snapcraft upload --release latest/edge myna-parakeet_0.1.0-dev_amd64.snap --component model-parakeet-int8=myna-parakeet+model-parakeet-int8.comp --component model-parakeet-fp32=myna-parakeet+model-parakeet-fp32.comp --component onnxruntime-cuda=myna-parakeet+onnxruntime-cuda.comp
Issues while processing snap:
- Snap is not allowed to use components
Full execution log: '/home/charles/.local/state/snapcraft/log/snapcraft-20260917-125026.895521.log'

Please can this be approved as soon as possible?

6

Hello,

I got my permission to upload components, but I notice neither hardware-observe nor system-observe were auto-connected for myna-parakeet. Does this need a flip now that the snap is uploaded?

7

+2 votes for, 0 against granting hardware-observe and system-observe to myna-parakeet. This is now live!

1 Like