[Starlingx-discuss] [multi os] Need of systemd for adoption of flock services in other os (regression worries)
vm.rod25 at gmail.com
Mon Sep 16 21:11:09 UTC 2019
On Mon, Sep 16, 2019 at 9:45 AM Dominig ar Foll (Intel Open Source)
<dominig.arfoll at fridu.net> wrote:
> One of the comment/worry that have seen on the instant message was about
> the potential regression risk related to the move to systemD.
> I would like to share the exchange as it relevant for all the community
> concerned by that topic.
> I am afraid that changing this will impact flocks functionality or big
> regression testing is required.
> Adding security and multiOS support will require some retest for sure.
> But if we add a plugin we could keep different DBs for different OSes.
> One calling for init.d scripts for legacy support while for multiOS a
> new DB would call for systemD.
> With that model, we would minimise risk, as only minimalistic regression
> test would be required until the DB content is changed for a given OS.
I like the idea, keep the current system working as it is and do not
interfere with functionality in order to enable another OS has been
part of our goals. The plugin solution is a great idea. The testing
part is naturally, the more features we have / os we run the more
testing it is needed.
Does anyone one on the community think that this change need a spec?
Thoughts from other OSs ( Debian / Yocto )
> Dominig ar Foll
> Senior Software Architect
> Intel Open Source Technology Centre
More information about the Starlingx-discuss