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

[Laura Creighton]

------- Forwarded Message
- ---------- Forwarded message ----------
Date: Thu, 2 Jan 2003 17:40:26 +0100
From: Martin Schulze <***@infodrom.org>
To: Debian News Channel <debian-***@lists.debian.org>
Subject: Public accessible Debian Machine
Resent-Date: Thu, 2 Jan 2003 10:47:17 -0600 (CST)
Resent-From: debian-***@lists.debian.org

- ------------------------------------------------------------------------
The Debian Project http://www.debian.org/
Public accessible Debian Machines ***@debian.org
January 2nd, 2003 http://www.debian.org/News/2003/20030102
- ------------------------------------------------------------------------

Public accessible Debian Machines

Hewlett-Packard (HP) offers public access to several machines running
Debian GNU/Linux through their Test Drive program. Software authors
and prospective users are offered an account on those machines in
order to find out more about Debian GNU/Linux and a particular HP
hardware. Four architectures are supported (Alpha, PA-RISC, IA-32 and
IA-64). Compilers are installed to that software authors can test
whether their software compiles on those platforms.

Hewlett-Packard offers access to the following four architectures:

Intel (IA-32) ProLiant DL360 G2 1.4GHz SMP
Intel (IA-64) rx2600 Itanium II SMP
Alpha (alpha) XP1000a ***@667MHz UP
Alpha (alpha) DS20 ***@500MHz UP
PA-RISC (hppa) rp5470 ***@550MHz UP

The Test Drive Program is a free service of HP. Its main purpose is
to provide developers with access to new HP hardware running various
HP and third party operating systems and applications. When you
register, you get a free shell account you can use to log into the
wide variety of systems on our Test Drive network and try out the
software and operating systems running on them.

Test Drive gives you the opportunity to try out combinations of
hardware, operating systems, and software before you buy them. For
developers, it also gives you the opportunity to ensure your software
runs on hardware, software, and operating system combinations which
you may not have available to you locally.

More information: http://testdrive.hp.com/

------- End of Forwarded Message

[Neal Norwitz]

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.

I would love to see this changed. At least if they openned up CVS
pserver access to SF. It would make life a lot easier.

The testdrive machines are a valuable resource, which I have used.

Neal

Post by Laura Creighton
------- Forwarded Message
- ---------- Forwarded message ----------
Date: Thu, 2 Jan 2003 17:40:26 +0100
Subject: Public accessible Debian Machine
Resent-Date: Thu, 2 Jan 2003 10:47:17 -0600 (CST)
- ------------------------------------------------------------------------
The Debian Project http://www.debian.org/
January 2nd, 2003 http://www.debian.org/News/2003/20030102
- ------------------------------------------------------------------------
Public accessible Debian Machines
Hewlett-Packard (HP) offers public access to several machines running
Debian GNU/Linux through their Test Drive program. Software authors
and prospective users are offered an account on those machines in
order to find out more about Debian GNU/Linux and a particular HP
hardware. Four architectures are supported (Alpha, PA-RISC, IA-32 and
IA-64). Compilers are installed to that software authors can test
whether their software compiles on those platforms.
Intel (IA-32) ProLiant DL360 G2 1.4GHz SMP
Intel (IA-64) rx2600 Itanium II SMP
The Test Drive Program is a free service of HP. Its main purpose is
to provide developers with access to new HP hardware running various
HP and third party operating systems and applications. When you
register, you get a free shell account you can use to log into the
wide variety of systems on our Test Drive network and try out the
software and operating systems running on them.
Test Drive gives you the opportunity to try out combinations of
hardware, operating systems, and software before you buy them. For
developers, it also gives you the opportunity to ensure your software
runs on hardware, software, and operating system combinations which
you may not have available to you locally.
More information: http://testdrive.hp.com/
------- End of Forwarded Message
_______________________________________________
snake-farm mailing list
http://lists.lysator.liu.se/mailman/listinfo/snake-farm

[Laura Creighton]

Post by Neal Norwitz
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.
I would love to see this changed. At least if they openned up CVS
pserver access to SF. It would make life a lot easier.
The testdrive machines are a valuable resource, which I have used.
Neal

This looks like a job for the Python Business Forum ... <looks around for
a storage closet, phone booths having gone the way of the dinosaur>
Can you please list briefly what you would like me to ask for. I will
go write up something, and then get you to proof read it, and then
go make my pitch.

Laura

[Anders Qvist]

Post by Laura Creighton

Post by Neal Norwitz
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.

Post by Laura Creighton

Post by Neal Norwitz
I would love to see this changed. At least if they openned up CVS
pserver access to SF. It would make life a lot easier.
The testdrive machines are a valuable resource, which I have used.
Neal

This looks like a job for the Python Business Forum ... <looks around for
a storage closet, phone booths having gone the way of the dinosaur>
Can you please list briefly what you would like me to ask for. I will
go write up something, and then get you to proof read it, and then
go make my pitch.

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.

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

Note that the xenofarm client does not currently work over proxy
or HTTPS.

Requirements for running the xenofarm client:

# gzip
# wget Must handle -N and set the timestamp correctly.
# Must handle --referer.
# Versions 1.6 and prior of wget are know to mangle
# the timestamps and will cause occasional missed
# builds. Versions 1.8.2 and newer are known to work.
#
# 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.

[Neal Norwitz]

Post by Anders Qvist

Post by Neal Norwitz
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.

Post by Anders Qvist
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?

Post by Anders Qvist
# gzip
# wget Must handle -N and set the timestamp correctly.

wget is not there, but we could build it.

Post by Anders Qvist
# `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

[Anders Qvist]

Post by Neal Norwitz

Post by Anders Qvist

Post by Neal Norwitz
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.

Post by Anders Qvist
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?

The client script uses wget to load the build package from

http://www.lysator.liu.se/xenofarm/python/builds/latest

eg:

wget --referer="$node" --dot-style=binary -N "$geturl"

where $geturl is the above URL.

It then uses a locally compiled program called put to do HTTP PUT of
the result package to a similar URL:

http://www.lysator.liu.se/xenofarm/python/builds/result

These URLs are in fact Roxen modules (www.roxen.com) that know how to
supply and receive build packages.

Post by Neal Norwitz

Post by Anders Qvist
# gzip
# wget Must handle -N and set the timestamp correctly.

wget is not there, but we could build it.

That's OK. It's not that big, and portable enough to be used in
xenofarm.