Re: [gentoo-dev] Portage through SSH

[John Nilsson <john@milsson.nu>]

rdist is probably great if you would like to have identical hosts.
But if you are having diffrent kind of installations it could get messy.

I was thinking something along these lines.

  %emerge sync && emerge world --target server1 --update

   1. rsync to localhost

   2. read localhost:/var/cache/edb/server1/world || \
      read server1:/var/cache/edb/localhost/world

   3. calculate which packages have to be updated

   4. read localhost:/var/cache/edb/server1/make.conf || \
      read server1:/etc/make.conf

   5. download and compile localy

   6. install to server1:/

   7. modify server1:/var/cache/edb/localhost/world && \
      modify localhost:/var/cache/edb/server1/world


-John


Terje Kvernes wrote:
> John Nilsson <john@milsson.nu> writes:
> 
> 
>>Some requirement thoughts: A network of gentoo hosts should have
>>only one portage processing server and any number of installation
>>leafs.
> 
> 
>   this is what I'm doing today, so I'll agree.  :-)
>  
> 
>>First of all portage needs to easily handle more than one
>>installation.  Second the "leaf-installations" should have a very
>>strict minimum requiremnts.  Third redundancy is probably
>>important. The information to restore a lost "leaf" should be
>>availible on booth the portage host and on the leaf it self.
> 
> 
>   this is easily doable with something like rdist.  most things under
>   unix are files.  keeping this in mind when working with unix is a
>   very good idea.
> 
>   at work, me and one other guy maintain about 150-odd linux boxes
>   with rdist and a little bit extra.  the idea is to rdist / with a
>   few appropriate exceptions.  we also maintain a configuration
>   database (flat files under /etc/config) that gets rdisted as well.
>   this means that all configuration for all the machines is available
>   everywhere -- which is nice even though we have tape backups. 
> 



--
gentoo-dev@gentoo.org mailing list