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).</li>
  • - Better packaging: we would need at very least separate packages for client and server parts;</li>
  • - 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 :-( ;</li>
  • - Multiplexing: enable simultaneous and independent tests running on the same machine;</li>
  • - Ruby documentation: the Ruby API is currently undocumented.</li>

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.

Looking for hackers with the skills:

c packaging ruby

This project is part of:

Hack Week 11

Activity

  • over 1 year ago: pdostal liked Twopence
  • almost 6 years ago: sfent joined Twopence
  • almost 6 years ago: mvidner liked Twopence
  • almost 6 years ago: osynge liked Twopence
  • almost 6 years ago: bergmannf liked Twopence
  • almost 6 years ago: RBrownSUSE liked Twopence
  • almost 6 years ago: oholecek liked Twopence
  • almost 6 years ago: ancorgs liked Twopence
  • almost 6 years ago: e_bischoff added keyword "c" to Twopence
  • almost 6 years ago: e_bischoff added keyword "packaging" to Twopence
  • All Activity

    Comments

    • ancorgs
      almost 6 years ago by ancorgs | Reply

      Sounds really interesting. Any repository or documentation to have a look?

    • e_bischoff
      almost 6 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.

    • jreidinger
      almost 6 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.

    • e_bischoff
      almost 6 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.

    • e_bischoff
      over 4 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

    Improving picotm by tdz

    Picotm is a system-level transaction manager. I...


    netlink interface for ethtool by mkubecek

    There seems to be an overall consensus that the...


    ethtool ops for netdevsim by mkubecek

    This can be seen as a subproject of [ethtool ne...


    make "predictable network interface names" more predictable by mkubecek

    Since the so-called "predictable names" for net...


    dmidecode: no more open-coded printfs by jdelvare

    There's a long standing request to extend the o...


    Test functional package manager for delivering packages by jevrard

    During the week, I install guix and analyse how...


    Properly package Quick Event orienteering management software by LPechacek

    It ain't rocket science, it ain't thrilling, it...


    All our beloved acronyms in one place... also some Jekyll hackin by thutterer

    Acronyms are fun. Everyone at SUSE loves them. ...


    Learn Crystal by porting part of YaST to that language by ancorgs

    For a very long time, I have been planning to p...


    Analyser for YaST logs by jreidinger

    Well, we often stuck in YaST team with knowledg...


    ActiveJob influxdb-rails instrumentation by hennevogel

    We have ActiveJob instrumentation in the OBS co...