new release out now with cleaned up code - 1.04    14/06/2005
You can now go directly to the official sourceforge project page to download this latest cleaned up PuSSH, rather than to the temporary link posted in the previous update. This is better for the project statistics, and also the right way to do things.

PuSSH works on AIX!    20/01/2005
Realistically speaking, there was never any reason why it shouldn't. As long as Python is installed (in this case python-2.2-4, on AIX5.2), we seem to be in business. In other news, thanks to the testers at iverve.com, it was discovered that the current release on SF is buggy. The core functionality is there, but the '-f <filename>' option, doesn't work, among other possible options. Due to a certain lack of time, a decent testing environment and other unfavorable circumstances, a 'bum version' got released. Before a newer, fully working version is released on SF however, you can get an older, stable version here instead. Remember to change your paths if you need to, to specify the directory you want to run PuSSH from, in the pussh script itself, at lines 88/89, otherwise just dump everything into a /home/yourhomedirectory/pussh directory. Everything else you need to know is in the INSTALL.txt.

PuSSH appears on Python-Eggs.Org    15/06/2004
Fame at last! There's a fair buzz in the Python community about this eggs site. I certainly like it, even if it is just a great collection of links.

first honest impressions, after intensive stress testing    29/10/2003
apart from non-existent targets (as opposed to existing, and receptive targets i.e. those on which sshd is running and which execute the PuSSHed command) causing a slightly heavier load on the source machine than some people might expect if commands are executed in parallel on too many such machines (the results of fairly intensive benchmarking in an environment of hundreds of machines of which 75% to 95% are "valid targets" would suggest a maximum "parallel slice" of 40-50 target machines if you don't want to see a load higher than about 3 on the machine from which the PuSSHed command originates, and we have accounted for this in the latest version - the default parallel slice parameter is a fine-tuned 42, but otherwise you can fairly safely go to about 100, or even beyond, although this obviously depends on what else you have going on), the fact that no serious bug reports have appeared thus far has prompted a development status upgrade to "production/stable", although we are retaining the beta status as well and concurrently, unusual as this may seem (basically, circumstances would indicate PuSSH could technically speaking still fall under either status umbrella by definition, so why not have both?). In other news, DS Libby has officially joined the PuSSH team, as his input has been invaluable not only during most of the development life-cycle thus far, but he will also be implementing some test-scenarios shortly, with a view towards verifying and expanding the flexibility of PuSSH per se in environments where SSH could be configured differently from how it was on the original development platform (CERN PDP clusters, using Kerberos authentication).

next to no bugs in the production environment - alpha turns to beta
   10/09/2003
Because PuSSH doesn't seem to show any actual bugs as such after initial testing in the CERN production environment, yesterdays alpha release has been upgraded to a beta release (as discussed unofficially). The only significant changes to the package inbetween are the addition of an INSTALL.txt file, and the modification of the path to brussh.py to reflect the installation instructions.

a Python success story is written.    09/09/2003
The first ever alpha release of PuSSH goes global on Sourceforge - as far as anyone can tell, and as basic as the idea may seem at first, at least possibly to a somewhat a more advanced Python developer, this is the first time this kind of application has ever been attempted in Python. At present, "the construct" consists of 2 separate Python modules (one calls the other directly), both of which are now available in a .tgz. It works on most if not all Linux distros for sure, and is probably completely platform independent. On linux/unix, after downloading to your home directory, run tar -zxpf on it, and then simply run it from its own directory thereafter i.e.

[$] ~homedir/pussh/pussh --help