On Thursday, September 29, 2011, Jean Weisbuch wrote:
> Le 29/09/2011 23:10, Chuck a écrit :
> > i guess sharing /etc/vservers is a bad idea. i just had another entire host do that
same
> > thing with every veserver on it..
> >
> >
> > is there no way to accomplish this? its ok if not im just being lazy ... being able
to
> > add a vserver on any machine and have all see it is really attractive.
> >
> >
> You can use rsync and i think that using a NFS share should also work
> but you might use some symlinks for eth interface or init mark for
> example as you probably wont want to boot at the same time the same
> vserver on serveral hosts.
>
yeah. only way to do that tho is human error, the startup files for each computer are
unique.
> But if you use a NFS share and its getting unavailable you wont be able
> to boot/reboot vservers so i would rather make rsyncs or a similar
> solution every time you create a vserver and/or periodically.
>
yeah i just set up an rsync update to all the servers so i have to limit myself to
installing/changing one particular host and it can update all the rest.
> And dont forget that if the hosts are running on different kernels you
> can have changes to make (for example memory limits on cgroup or rlimits
> ; schedule that prevent vserver to start on newer kernels).
>
no worries there. all are running exactly the same versions of kernel and utils. our
guests run very simply. i basically have made no basically changes other than additions
since i started using verservers around 2006 or so and those few changes such as ip
additions to guests i do manually anyway. we never bothered experimenting with cgroups or
rlimits. everything just works fine in 'simple mode'.
-- ChuckReceived on Fri Sep 30 02:33:30 2011