sure, our use case looks like this:
we are a commercial OSS company, produce crossbar https://github.com/crossbario/ and
initiated WAMP https://wamp-proto.org/
crossbar is a decentralized messaging middleware - a data plane, like SDN for apps
we have a commercial/enterprise product built on that: crossbarfx center
this adds a controller able to manage/monitor networks of interconnected crossbarfx nodes
those nodes can also run on edge devices (IoT is a focus for us), and crossbarfx
allows to remotely deploy/manage/monitor applications components that connect to crossbar
via Docker containers and snaps
for managing Docker containers, the crossbarfx running on the edge device talks to
the Docker daemon on that edge device host (via unix domain socket), and the crossbarfx node itself connects to our controller (via outgoing secure websocket), from where the user can centrally manage all the nodes and containers
note that we have that already. works great.
as we really like the advantages of ubuntu core / snaps, in particular in IoT (but also desktop), we would like to do similar with snaps/snapd
eg admin logs into crossbarfx center (web based), selects some app microservice wrapped as a snap, selects the edge devices and hits “deploy now”.
doing it with docker works, but as docker wasn’t designed for edge devices (eg not fine grained control over hardware access permissions, rollbacks, etc), we really would love to support snap(d) as well.
well, technically, I think we have an alpha already implemented, not sure about status. anyways. technically easy to do, but we only now became aware of the policy restrictions that might bite us - hence this thread;)