wip talk

diff --git a/make-log b/make-log
new file mode 100755 (executable)
index 0000000..b605753
--- /dev/null
+++ b/make-log
@@ -0,0 +1,20 @@
+#!/bin/sh
+set -e
+: ${OSSTEST_GIT:=$HOME/work/testing.git/.git}
+(set -e
+ git --git-dir=$OSSTEST_GIT log \
+     --date-order --pretty=format:'%an %ai'
+ echo) \
+| perl -l -a -F'/\t/' -ne '
+        next if $F[0] eq "xen.org";
+        $F[0] = "Roger Pau Monné" if $F[0] eq "Roger Pau Monne";
+        $F[0] = "Anthony Perard" if $F[0] eq "Anthony PERARD";
+        $F[1] =~ s/ .*//;
+       $d{$F[0]} = $F[1];
+        END {
+               foreach my $k (sort { $d{$a} cmp $d{$b} } keys %d) {
+                       print "$d{$k}  $k";
+                }
+        }
+' \
+| tac

diff --git a/talk.txt b/talk.txt
new file mode 100644 (file)
index 0000000..34eb5f9
--- /dev/null
+++ b/talk.txt
@@ -0,0 +1,87 @@
+[title]
+
+
+[intro]
+
+osstest is the Xen Project's automated testing system.
+
+[push gate]
+
+We use the production instance to test the mainline development branch
+of the Xen hypervisor and tools, as found in xen.git.
+
+Each test run picks up the latest version of the pre-test git branch,
+known as `staging'.  If the tests do not show any regressions, the
+system pushes the tested code to `master', which serves as a stable
+basis for most ongoing development.
+
+[list of branches and jobs]
+
+osstest's focus is on basic functional testing of a wide matrix of
+configurations.
+
+A complete Xen system uses a number of important components other than
+the hypervisor and tools.  We test these too, and many of them have
+their own push gates.
+
+This not only provides us with always-useable versions of these
+subcomponents, but also allows us to quickly spot problems introduced
+in the other projects we depend on.
+
+[standalone mode README excerpt]
+
+osstest can also operate in a `standalone' mode, which does not depend
+on a database of tests, the host allocation infrastructure, resource
+scheduler, and so on.
+
+With standalone mode, you need just a dhcp and pxe server, and a local
+webserver for autoinstall data.  You can then use osstest to provision
+test boxes, and/or use it to run specific tests.  This is very useful
+for developing osstest itself.
+
+[hosting]
+
+Currently osstest is running in a test network at Citrix's Cambridge
+office in the UK.  There is a dedicated pool of just 11 test machines.
+
+Test reports and logs are posted publicly; the osstest system's source
+code and deployment documentation is of course published (and
+contributions are welcome).
+
+Because it's inside the Citrix network, it isn't possible for other
+members of the Xen community to directly access the test environment
+or help administer it.
+
+The Xen Project Advisory Board have agreed funding for a new facility
+for automated testing.  There is a Test Working Group who've been
+working out the details.  We have now selected Earthlink in
+Massachusets for colocation.  We're planning an initial deployment
+including 24 test hosts.
+
+There has been some discussion about whether to use some other test
+framework.  The Xen Project Test Working Group have agreed that we
+will move the existing deployed system, osstest, into the new
+facility.  The new facility has been specified to be able to host
+alternatives such as XenRT, so if we want to consider moving away from
+osstest, this new facility will give us the ability to evaluate
+the alternatives and plan a transition.
+
+
+Decisions about sw
+
+
+what is osstest
+
+ push gates
+
+hosting
+
+ currently citrix
+
+ Xen Project LF AB moving to own colo
+
+kinds of tests
+
+ basic functional
+ compatibility
+ external projects