fugo-player: auto-connect network-manager and snapd-control on our own models

Hi, we’d like network-manager and snapd-control to auto-connect for fugo-player, on our own device models only:

plugs:
  network-manager:
    allow-auto-connection:
      on-model:
        - VfQpT9wKNFRBgcCftQh1IMK3aH3IGajn/fugo-one-amd64
        - VfQpT9wKNFRBgcCftQh1IMK3aH3IGajn/fugo-one-arm64
  snapd-control:
    allow-installation: true
    allow-auto-connection:
      on-model:
        - VfQpT9wKNFRBgcCftQh1IMK3aH3IGajn/fugo-one-amd64
        - VfQpT9wKNFRBgcCftQh1IMK3aH3IGajn/fugo-one-arm64

fugo-player is a digital signage player. We build Ubuntu Core 24 images for our own devices, where the player runs as a kiosk service under Ubuntu Frame. The devices have no login: no console-conf and no SSH user.

snapd-control: Frame’s install hook only enables its daemon when it can read the device model. snapd hides our model from Frame, so on our images Frame never starts (canonical/ubuntu-frame#161). We use the stock pc and pi gadgets, so we can’t set daemon: true in gadget defaults. A small frame-setup service in fugo-player would set ubuntu-frame’s daemon=true, a black background and a hidden cursor at boot. Its only snapd calls are GET and PUT on /v2/snaps/ubuntu-frame/conf.

network-manager: when a screen has no Ethernet, the player is the only thing an installer can use. If the device has had no network connection for a minute after boot, the player shows a Wi-Fi picker and joins the chosen network over NetworkManager’s D-Bus API: GetDevices, RequestScan, GetAllAccessPoints, AddAndActivateConnection and Settings.Connection.Delete, plus reading State and access point properties.

Scope: only the frame-setup app plugs snapd-control, so the kiosk, which renders web content, never holds it. Only the kiosk app plugs network-manager. Both services are installed disabled and enabled only on our models, so desktop installs of the snap aren’t affected.

Uploads: network-manager is already in the stable revisions (46 and 47). We haven’t uploaded snapd-control yet, because a held upload would block our regular releases. We can upload a revision for review whenever suits you, or after the declaration is granted.

  • Snap: fugo-player (snap ID wyxgIdVULzOCCbmnzFg1Np40GaRjlF9J)
  • Brand account: VfQpT9wKNFRBgcCftQh1IMK3aH3IGajn
  • Models: fugo-one-amd64 and fugo-one-arm64, grade signed

Thanks!

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

Hello @Fugo :slight_smile:

Considering that both interfaces are requested for the brand store only, this is a +1 from my side for auto-connecting network-manager and snapd-control interfaces to the fugo-player snap!

What do other @reviewers think?

Please note that brand store requests like this should go through the support portal normally though, not through the forum …

Thanks, both. To clarify, we don’t have a brand store (Dedicated Snap Store). fugo-player is in the public store, and on-model only limits the auto-connection to devices running our own models.

We posted here because the permission requests docs send these requests to this category and don’t mention the support portal. If requests from a brand account should still go through the portal, could you share the link? A line about it in those docs would help others too.

Well, the snapd-control interface is actually only granted to paid dedicated device stores.

In the global store only Canonical owned snaps are usually permitted to have it (since it grants full ownership of the device to the snap using it)

Hi @Fugo

+1 from me to grant auto-connection of network-manager interface. But as @ogra mentioned, we rarely grant auto-connection of snapd-control interface for the snaps in the global store. Hence, -1 from me to grant auto-connection of snapd-control interface.