RFC for OEM package

[Sergio Schvezov]

On martes 10 de marzo de 2015 10h'21:28 ART, Alexander Sack wrote:
> Hi,
>
> good start.
>
> I am very much interested in seeing the specific syntax proposal for
> defining default packages and their configs in that doc.

Look forward to it this week, I plan to pick this up again today.

> Also "Where possible and relevant, and specifically the ubuntu-core
> configuration part will feed into cloud-init." I assume that the
> ubuntu-core: cloud-init: will be the subsnippet that will get fed into
> cloud-init while the rest gets digested by other parts of ubuntu core?

Yes, ubuntu-core relevant changes/configurations will be fed into 
cloud-init.

> Another key feature not yet specced here is the ability for OEMs to
> configure hw access for factory (e.g. hw assign devices to apps that
> oem installs). Would be great to see this as explicit examples here
> too. I guess in general making a reference hello-oem snap that show
> cases all our features would be helpful!

This is part of what I still failed to propose but a new rfc for config 
parts; it's actually two. Since the oem package will take a global config 
as a seed if you must call it something it feels that these specific config 
options for hardware access be made in the config per package; so in a 
nushell, the config rfc will mention things to be consumed by snappy for:

- enabling/disabling/restarting services.
- setting hw access.

Stay tuned for that.

One thing I also failed to mention was the management of kernel modules, 
which I need some more "walks in the park" to get a clearer idea on 
something clean.