Skip to content
Browse files

BioLinux in KVM

  • Loading branch information...
1 parent 8cb04b8 commit 454732007ae9d7e4cc2a5bce5fac927895d4e92e @pjotrp pjotrp committed Dec 19, 2011
Showing with 16 additions and 4 deletions.
  1. +2 −1 doc/
  2. +14 −3 test/README
3 doc/
@@ -42,6 +42,7 @@ password (preferably using a key with empty password). From that point on you
can install CloudBioLinux using the fabric file.
This is also the image the test system fingerprints for further test installs. You can
-use the ./test/test_vm.rb script to test drive the VM.
+try the ./test/test_biolinux script to test drive the VM. test_biolinux will install a
+CloudBioLinux flavor, and check whether the installation is complete.
17 test/README
@@ -1,10 +1,21 @@
Integration test for CloudBioLinux.
+When you have a base install running, you only need to supply the
+(local) IP addrees of the VM, and the password-less key for the
+install user (who has sudo bash). The tests get invoked wiht
-./test_vagrant --help
+ ./test_biolinux [-i] [-u user] IPaddr [Flavor]
-== Testing issues ==
+For further options see
+ ./test_biolinux --help
+Alternatively try the self running test using Virtualbox and Vagrant
+ ./test_vagrant --help
+== Testing issues with Vagrant ==
The test system depends on a stack of tools, including virtualbox,
vagrant, ssh, ruby and related libraries. Things can go wrong. Here we

0 comments on commit 4547320

Please sign in to comment.
Something went wrong with that request. Please try again.