Re: Should we get an account and add them to the Xenofarm?

On Fri, Jan 10, 2003 at 05:13:19PM +0100, Anders Qvist wrote:
> On Fri, Jan 10, 2003 at 04:29:57PM +0100, Laura Creighton wrote:
> > > 
> > > This may be difficult if not impossible.  Unless the testdrive setup
> > > has changed, HP used to prevent all outgoing connections through their
> > > firewall.  This means you cannot do a cvs update from their machines
> > > to pull down the latest python.  You would have to ship a tarball
> > > there each time.
> 
> Technically, this is not necessary. xenofarm gets the sources by HTTP
> in the build package. We can hack it so it leaves the source in place.
> It's still gonna make things difficult if you want to test manually,
> but it won't stop xenofarm.
> 
> We need to be able to run cron jobs on the host. Disk requirement is a
> full python build, plus a tar ball and some extras, cirka 250Mb.

crontab -e executed, I didn't test if it worked.
I will try to write a letter as Laura requested later.

> Ports:
>   In: ssh
>   Out: HTTP (GET & PUT) (one host)

HTTP (port 80) out did not work to a public www site.  What is the IP
address of the machine?

> Requirements for running the xenofarm client:
> 
> #  gzip
> #  wget              Must handle -N and set the timestamp correctly.

wget is not there, but we could build it.

> # Requirements that are normally fulfilled by the UNIX system:
> # `ls -t`           should list files sorted by modification time
> # `uname -n`        should print the nodename
> # `uname -s -r -m`  should print OS and CPU info
> # `kill -0 <pid>`   should return true if a process with that pid exists
> # `LC_ALL="C" date` should return a space-separated string with where the
> #                   first substring containing colons is on the form
> #                   <hour>:<minute>.*
> # tar               must be available in the PATH
> 
> ... and of course, all the stuff needed to build python.

All of these seem ok.

Neal