Twopence is (will be) a remote execution engine for tests, able to run tests in virtual machines and real hardware through various means of communication : virtio for KVM / QEmu, ssh on top of libssh, serial lines. This library can be called from shell and ruby wrappers.
While it is already functional (and used), it still needs polishing, stabilizing, and extending. It is also planned to integrate it with Pennyworth (project Machinery) and let it go fully Open Source.
All crazy ideas and good will are welcome. It could be Python wrappers, support for multiple simultaneous tests, support for Linux containers, tests through a firewire cable, or whatever crosses your mind.
What was achieved
- - GitHub: The project moved to GitHub and is willing to play the rules of OpenSource;
- - Ctrl-C and other aborts: now it is possible to interrupt a remote execution with Ctrl-C, both from shell and from Ruby interface;
- - Pennyworth integration: now Pennyworth (project Machinery) calls Twopence to execute remote commands, inject or extract files.
What was not achieved
- - Bug: running the Twopence server for virtio or serial lines with output redirected to a file results in the whole output being repeated with each new message (probably some buffer not flushed).
- - Better packaging: we would need at very least separate packages for client and server parts;
- - Run over firewire: this item is a bit crazy - the idea is to use firewire to run tests and transfer files without using the network stack, by using either raw libraries or raw devices. I bought the necessary hardware but had no time to play with it :-( ;
- - Multiplexing: enable simultaneous and independent tests running on the same machine;
- - Ruby documentation: the Ruby API is currently undocumented.
What could be done better
- - Ctrl-C and other aborts: enable aborting a file transfer, not only remote execution of commands;
- - Pennyworth integration: transferring recursively a whole directory's contents is still done with Cheetah.
This project is part of:
Hack Week 11
Activity
Comments
-
-
about 10 years ago by e_bischoff | Reply
Currently only on https://build.suse.de/package/show/home:ebischoff/twopence (sources available). I was planning to move them to GitHub right for the hackweek.
-
about 10 years ago by jreidinger | Reply
I think it make good sense to also support VNC as a way how to communicate with machine as it immediatelly increase range where it is useful. BTW some comparison to openQA if it is orthogonal or if it can benefit from some synerge would be nice.
-
about 10 years ago by e_bischoff | Reply
Twopence is used to execute remote commands and transfer files just like you would do with scp or ssh (but works even with no network, unlike ssh). It is not a remote display system like VNC. It works only with a running system, unlike OpenQA, because it either needs a SSH server or a Twopence server on the System Under Tests, so it cannot test the early stages of boot. In short, there is not much duplication of functionality - at least with those two pieces of software.
-
over 8 years ago by e_bischoff | Reply
I'll mark this project as finished. Not everything has been done, but it is now stable and regularly used software.
Similar Projects
Add a machine-readable output to dmidecode by jdelvare
Description
There have been repeated reques...
FizzBuzz OS by mssola
Project Description
FizzBuzz OS (or just ...
Update Haskell ecosystem in Tumbleweed to GHC-9.10.x by psimons
Description
We are currently at GHC-9.8.x...
Framework laptop integration by nkrapp
Project Description
Although openSUSE doe...
Packaging Mu on OBS by joeyli
Description
Packaging Microsoft Mu project ...
Recipes catalog and calculator in Rails 8 by gfilippetti
[comment]: # (Please use the project descriptio...
Fix RSpec tests in order to replace the ruby-ldap rubygem in OBS by enavarro_suse
Description
_"LDAP mode is not official s...