User:Jlo: Difference between revisions

From Alpine Linux
(Created page with "I was User:Jch but I forgot my passwd and the email used to suscribe is not valid anymore...")
 
No edit summary
Line 1: Line 1:
I was [[User:Jch]] but I forgot my passwd and the email used to suscribe is not valid anymore...
I was [[User:Jch]] but I forgot my passwd and the email used to suscribe is not valid anymore...
I'm today senior system architect at some startup.<br/>
We are building a network of embedded devices controlling hardware stuff.<br/>
I'm stepping it as the product is transitioning from prototype phase to industrial phase.
The main app is written for Oracle Java8 and running in Apache/Karaf environment.
The proto was done with Debian boxes managed with salt stack (about 100 of those with a mix of Wheezy and Jessie).
I would like to see the boxes running AL in ''run-from-ram'' mode pulling the apkovl tarball (or at least some tarball to be applied in the /etc/local.d sequence) from a remote server somewhere in the cloud.<br/>
To upgrade would just to rsync the normally read-only SSD and reboot.
To achieve this with AlpineLinux, one has to:
*    deploy Oracle Java 7 with glibc
*    deploy Oracle Java 8 with glibc
*    deploy python2.7 with needed libs
*    deploy hardware watchdog
*    deploy network drivers (eth, usb-eth, wlan, 3g, lte)
*    deploy USB drivers
*    rewrite init scripts
*    prepare a custom image with every needed packages locally present in disk repo
*    adapt custom deb packages to apk ones
To configure a box is done in two parts:
*    the network. done locally
*    the app layer. done via a webinterface; commited to a server and download by the box at each boot.

Revision as of 07:45, 10 June 2017

I was User:Jch but I forgot my passwd and the email used to suscribe is not valid anymore...

I'm today senior system architect at some startup.
We are building a network of embedded devices controlling hardware stuff.
I'm stepping it as the product is transitioning from prototype phase to industrial phase.

The main app is written for Oracle Java8 and running in Apache/Karaf environment.

The proto was done with Debian boxes managed with salt stack (about 100 of those with a mix of Wheezy and Jessie).

I would like to see the boxes running AL in run-from-ram mode pulling the apkovl tarball (or at least some tarball to be applied in the /etc/local.d sequence) from a remote server somewhere in the cloud.
To upgrade would just to rsync the normally read-only SSD and reboot.

To achieve this with AlpineLinux, one has to:

  • deploy Oracle Java 7 with glibc
  • deploy Oracle Java 8 with glibc
  • deploy python2.7 with needed libs
  • deploy hardware watchdog
  • deploy network drivers (eth, usb-eth, wlan, 3g, lte)
  • deploy USB drivers
  • rewrite init scripts
  • prepare a custom image with every needed packages locally present in disk repo
  • adapt custom deb packages to apk ones

To configure a box is done in two parts:

  • the network. done locally
  • the app layer. done via a webinterface; commited to a server and download by the box at each boot.