[Interop-dev] Salt, Docker, generator images

[Nemesis]

Thanks :-)

I suggested a friend to take a look at nodewatcher-agent because he
needed something similar.

Federico



On 02/24/2015 10:20 AM, Jernej Kos wrote:
> Hello!
>
> Wireless-info should really not be used anymore. I am not sure why Mitar
> posted this link, but we are now using nodewatcher-agent (or more
> specifically its wireless module) which uses libiwinfo to obtain all the
> wireless data.
>
> Netmeasured is a small application that performs periodic pings between
> two nodes and reports loss statistics via ubus. It is currently used for
> some simple KORUZA measurements.
>
>
> Jernej
>
> On 24. 02. 2015 10:17, Nemesis wrote:
>> Thanks for sharing.
>>
>> Could you expand a bit more on the wireless-info and netmeasured repos?
>>
>> Federico
>>
>>
>>
>> On 02/23/2015 07:39 PM, Mitar wrote:
>>> Hi!
>>>
>>> Just wanting to share some new stuff we have been using in wlan
>>> slovenija network.
>>>
>>> So for managing our servers, we started using Salt and Docker. You can
>>> find our Salt configurations here:
>>>
>>> https://github.com/wlanslovenija/servers-salt-states
>>> https://github.com/tozd/salt
>>>
>>> We are putting all stuff into Docker images. Like nodewatcher, routing, etc.
>>>
>>> https://github.com/wlanslovenija/docker-router-olsrd
>>>
>>> And interesting thing we started doing is putting OpenWrt firmware
>>> generators for each platform into its own Docker image:
>>>
>>> https://github.com/wlanslovenija/firmware-core
>>>
>>> In this way it is easy to share already compiled firmware generators.
>>> People do not have to compile them themselves. You can then simply SSH
>>> into it and compile images for that platform. (We use nodewatcher to
>>> connect to them and compile based on the set of packages our users want
>>> and with configuration baked in into the image itself.)
>>>
>>> For gateways and VPN servers, we are simply using (or planing to use)
>>> OpenWrt images generated by nodewatcher. :-) For x86 platform and it
>>> works. In this way it is easy to reuse the existing stack. The servers
>>> above are mostly for website, nodewatcher itself, etc.
>>>
>>> We have also quite few OpenWrt packages:
>>>
>>> https://github.com/wlanslovenija/firmware-packages-opkg
>>>
>>> So for OpenWrt we are trying to put everything into packages. For
>>> servers into Docker images.
>>>
>>> For configuring the network stack for Docker we are using:
>>>
>>> https://github.com/wlanslovenija/netcfg
>>>
>>> Some random apps we created:
>>>
>>> https://github.com/wlanslovenija/wireless-info
>>> https://github.com/wlanslovenija/netmeasured
>>>
>>> I am sharing all this stuff so that others see if there is anything
>>> interesting so that we do not duplicate too much things. Or that we
>>> might use the same patterns/tools to be easier to reuse. Like Salt,
>>> Docker. The most interesting for me is that if we would agree upon a
>>> simple format for generator images, it would be a great way to share
>>> firmware builders one can simply plug into their own systems. We all use
>>> OpenWrt based stuff, this is then just to make module around it so that
>>> I can ship to somebody a firmware they are not used to, but they can
>>> still generate it with tools they are used to.
>>>
>>>
>>> Mitar
>>>
>>
>> _______________________________________________
>> Interop-dev mailing list
>> (spam-protected)
>> https://lists.funkfeuer.at/mailman/listinfo/interop-dev
>>
>
>
> _______________________________________________
> Interop-dev mailing list
> (spam-protected)
> https://lists.funkfeuer.at/mailman/listinfo/interop-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.funkfeuer.at/pipermail/interop-dev/attachments/20150224/227f6e70/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.funkfeuer.at/pipermail/interop-dev/attachments/20150224/227f6e70/attachment.sig>