Chris McEniry wrote:
> Brad Knowles wrote:
> >> What do you use?
> >
> > I'm curious to see what you think of Moobi (see
> > <http://preview.tinyurl.com/ccylql>).
>
> Well, now that I don't have to suggest that ;).
>
> As much as I like my baby, as it stands outlined in there, I'd say it's
> only of limited use to you, Trever.
>
> 1.) it's linux specific,
> 2.) it's not programmatic - i.e. no API,
> 3.) it's environmentally particular - might be as problematic as
> multicast (it's bittorrent based).
>
> That being said, it still works reasonably well for us (insert caveats
> about 80/20 problems here). If the p2p nature of it sounds good, I
> heartily recommend adapting to that model given the image size your
> looking at. Are you hitting network constraints or image server
> constraints?
>
> The only other option that I know of that really goes down that p2p path
> is some variants of ROCKS, but I haven't looked at it in a while so I
> can't comment on if it'll work for you without much adaptation.
>
>
rocks is definitely a p2p install system, but not a maintenance system.
The ROCKS strategy for maintenance is to update the bundles of packages
(name slipping mind at the moment) and then reboot and completely
rebuild the node. It uses bit-torrent as the p2p method to pull packages
from any host that wants to provide it, so you can build up a large
network of hosts fairly quickly that accelerates as more hosts get
installed.
_______________________________________________
Discuss mailing list
[email protected]
http://lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
