[PL #2219] yum memory leak
justin at cs.arizona.edu via RT
devel at planet-lab.org
Tue May 17 12:30:59 EDT 2005
Email Recipients (see http://www.planet-lab.org/Support)
Requestor: mlhuang at cs.princeton.edu
Ticket Ccs: mlhuang at cs.princeton.edu, stork at cs.arizona.edu
Of course, Stork (http://www.cs.arizona.edu) doesn't leak memory and has
much better performance. Even for huge numbers of package dependencies,
the memory use of stork is negligable...
If you are looking for an installation tool for the Node Manager, etc. we
have a "stand-alone" version of Stork which doesn't communicate with the
stork slice (and thus doesn't share package contents) but is otherwise
>- no SSL support (not necessary if we sign packages, separate ticket)
Securely verifying the repository using stork is unnecessary because a
"malicious" fake repository cannot generate correct package hashes for your
keyfile or forge your keyfile without your private key...
>- no groups support (can't define an encompassing 'PlanetLab' or
>'VServer' package group)
Stork also supports this by creating virtual packages with the necessary
Additionally, PlanetLab could easily test/deploy new versions of core
software using Stork where all of the software packages would be efficiently
transferred using CoBlitz. We are currently working on improving the
usability of our incremental roll-out capability...
I'd be happy to discuss any of this in more detail...
More information about the Devel-community