[Voyage-linux] Automatic Deployment and Configuration

Gustin Johnson (spam-protected)
Sat Sep 3 02:17:46 HKT 2011


We have not messed with chef.  We will be doing an eval in a couple of
months.  Basically we are using svn right now.  We just scp the
scripts/configs that we want.  The number of devices that are being
managed is currently pretty small so it has been pretty low on our
list.



On Fri, Sep 2, 2011 at 11:21 AM, John Schultz <jschultz0614 at gmail.com> wrote:
> Gustin,...
>
> Do you have experience with Chef?
>
> I just installed it on my debian box and the application is not running. Is
> there a how-to for complete walkthrough on installing, configuring and
> running?
>
> Thanks,
> John
>
>
> On Thu, Sep 1, 2011 at 17:36, Gustin Johnson <gustin at meganerd.ca> wrote:
>>
>> It sounds like chef or puppet are exactly the sort of thing you are
>> looking for.  Why re-invent the wheel unnecessarily?
>>
>> Chef:
>> http://wiki.opscode.com/display/chef/Home
>>
>> Puppet:
>> http://projects.puppetlabs.com/projects/puppet
>>
>> 2011/9/1 John Schultz <jschultz0614 at gmail.com>:
>> > 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
>> >
>> >
>> > _______________________________________________
>> > Voyage-linux mailing list
>> > Voyage-linux at list.voyage.hk
>> > http://list.voyage.hk/mailman/listinfo/voyage-linux
>> >
>> >
>
>




More information about the Voyage-linux mailing list