[Voyage-linux] Automatic Deployment and Configuration

[John Schultz]

Martin,.. I have been looking for this kind of feature ever since I started
working with Voyage. The easiest way would be to develop a web based
interface that contains all the settings, save this in a central repo., and
then have the nodes check in every X minutes, if there is a change, then
apply the changes and based on what change, do a system reboot if necessary.

On Thu, Sep 1, 2011 at 09:26, Martin Kos <martin at kos.li> wrote:

> Hi all
>
> i have the need to deploy a lot of alix boards with voyage linux running
> on them. the have a "common" configuration, but still each alix has it's
> own settings.
> one thing is the inital configuration of the alix, but then when they
> are deployed and i want to make changes to the configurations, that
> should be automated and scalable. the problem is that not all of the
> boxes are reachable from outside, so they need to have some "call home"
> feature.
> i have thought about using puppet for this purpose? but haven't checked
> the details yet.
> one idea was to make some kind of dual boot system, where one system is
> a "read only, never change" system that can make the inital installation
> of the seconde "real" system, and that will "always" work. which means
> that in case of any damage to the real system, the other system can
> boot, download the whole real system and configure it. so also upgrades
> to newer version of voyage linux etc would be possible, or just "reset"
> the system to the inital state.
> what do you think about this ideas? anybody tried something simliar?
>
> greets
>  KoS
>
> ______________________________**_________________
> Voyage-linux mailing list
> Voyage-linux at list.voyage.hk
> http://list.voyage.hk/mailman/**listinfo/voyage-linux<http://list.voyage.hk/mailman/listinfo/voyage-linux>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20110901/e10a3443/attachment.html>