Creating more Snappy frameworks

Registered by Daniel Holbach on 2015-10-27

Frameworks extend the functionality of Snappy Ubuntu Core systems in a vary practical way. Let's discuss how we can bring more services to Snappy Ubuntu Core.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Notes:

Definition: frameworks are there to mediate resources, not to ship additional dependencies

available frameworks: docker, lxd, webdm, mir (only amd64)

frameworks in the works: connectivity snap (based on network manager), bluetooth,
 - https://code.launchpad.net/~morphis/+git/nm-snap (not confined, some bits needs more work still)
   - implemented for a specific product, based on vivid NM (0.9.10.x ) stack, not in public store
 - https://code.launchpad.net/~morphis/+git/snap-manual-bluez5 (fully confined, not using snapcraft yet)

requested frameworks:
 - pulseaudio (who requested? I just mentioned as another complex framework target, like NM )
 - User switching, sessions.
 - mir on other archs (arm)
 - IoT frameworks?

Open questions:
 - DBus activation?
 - What about codecs?
 - dependencies between frameworks
   - maybe at some stage via the capabilities system (a bit early still)
 - seems this should be autodetected: when both frameworks are around they detect each other

(?)

Work Items

Work items:
[dholbach] file a bug to review framework docs and add examples if necessary (https://github.com/ubuntu-core/snappy/issues/80): DONE
[dholbach] do a bit of a survey on the mailing list about frameworks and their use (https://lists.ubuntu.com/archives/snappy-app-devel/2015-November/000441.html): DONE

This blueprint contains Public information 
Everyone can see this information.