On Wed, 2007-03-07 at 22:01 +0000, John Hodrien wrote: > On Wed, 7 Mar 2007, Jeffrey Law wrote: > > > During the boot process, after setup of the union and bind mounts, > > the client contacts the puppetmaster to download any configuration > > information appropriate for the client. > > I think part of my problem is a lack of understanding of puppet. Is there a > good guide I should read up on before bugging people any more. David's reply has a pointer to the canonical web page :-)
> > > Also note that without some form of persistent storage you can get > > into situations where you lose data. Consider mail or print spooling > > as an example. If the client reboots while mail or print jobs are > > in the spool directory and the client has no persistent storage, then > > those jobs will simply be lost into the ether. If the client has > > some persistent storage, then those jobs will be flushed out of the > > spool directory when the client comes back up. > > Losing data is A okay with me ;) :-) There certainly are cases where it's OK, looks like you've got one. > > > Out of curiosity, what are you trying to do with stateless? > > In many ways I'm just having a play to see what it can do. I'm installing > this on a display wall where you have a stateful headnode, shared home > directories, plus 6 stateless slaves that are powering the displays. Slaves > are entirely storage free. Ah. Does the headnode ever need to do anything to control the stateless nodes without human intervention (ie, does the head node ever fire off commands to the clients via SSH?) As an admin, do you ever remotely log into the clients via SSH? If so, then you probably need a persistent SSH private key for the clients. If that's the only persistent bit you need, then puppet may be overkill. Jeff _______________________________________________ Stateless-list mailing list [email protected] http://www.redhat.com/mailman/listinfo/stateless-list
