create network-profile packages

[aparcar]

I'm working on an image on demand server creating images based on various parameter.
A community parameter could auto integrate a network profile in the build image. The problem I'm facing right now is that there is no versioning of these profiles.
I came up with to solutions:

• Use the git commit hash of a folder as version, if the installed hash is different to the current git, update the profiles. This is more like a work around
• We could auto create packages of network profiles. These could be installed in a generic way and the package generator could increment a version counter whenever a profiles changes.

Ideas for a better solution?

[nicopace]

I think @p4u can make a good opinion on this... don't despare, we are at BattleMesh and it is a little hard to have tickets updated this days ;)

[aparcar]

There is no rush, please keep me updated 👍

[aparcar]

@p4u can you please have a look into this? I've been ask to supply all information about an image to make it reproducible

[aparcar]

@p4u @ilario
with the new way to include packages in network profiles libremesh/lime-sdk@60e6109 and my need to implement this into the build-server openwrt/asu@03ca8a7 I'd like to push this issue again.
Creating packages out of the network-profiles would simplify updating to new profile versions, needed packages are set as a dependence. Re-installation after messing the configs would be possible as well.

I could create a "package-builder" and only the cooker/image-server must include a extra repo

[p4u]

I like the idea of having packages for profiles, it's actually very easy to implement.

If you like to do it, go ahead.

[aparcar]

I created a simple script that builds all packages, I'll add a readme asap.
https://github.com/aparcar/network_profiles_builder
Currently the script builds every 15 minutes the packages here
https://betaupdate.libremesh.org/static/packages/profiles/
It should be possible to add the url above to the cooker, so network profiles are installable with adding np-libremesh-encrypt-11s to a flavor or in PACKAGES= var

[p4u]

Great. Do you want to transfer this repository to the libremesh github organization? You would administrate it.

Also the reposotiry might be build on the official libremesh server and then included to the feeds.conf.default file of lime-sdk, so the profiles will be available out of the box.

[aparcar]

that would be perfect. I just triggered the change of ownership. Still I'd need some more right within the team to actually push things