1. 08 Mar, 2017 2 commits
  2. 25 Jan, 2017 1 commit
    • anonym's avatar
      Remote shell: extend with persistent Python 2.7 per-user sessions. · 7c1e999c
      anonym authored
      * "persistent": effects (e.g. assignments) survive between separate
        remote shell python commands.
      * "Python 2.7": because that is what Dogtail needs.
      * "per-user": the `dogtail` module must be imported as the user
        running the applications you intend to have Dogtail interact with.
      This will allow us to optimize the performance of Dogtail
      significantly, as well as reduce the code complexity of the Dogtail
      Refs: #12059
  3. 29 Nov, 2016 1 commit
  4. 01 Nov, 2016 1 commit
  5. 27 Oct, 2016 1 commit
  6. 26 Oct, 2016 2 commits
  7. 25 Oct, 2016 3 commits
  8. 24 Oct, 2016 5 commits
    • anonym's avatar
      Fix typo. · 8b899219
      anonym authored
    • anonym's avatar
      Fix bad try_for() usage. · 3cb65137
      anonym authored
      We don't have #9223 yet, so the try_for() block must return `true` to
    • anonym's avatar
      Make the remote shell use a virtio channel for transport. · 054bcc84
      anonym authored
      The serial channel operated at 400 Kbaud = 50 KB/s (although I think it
      was significantly lower in practice) whereas we now should
      expect (depending on hardware) rates closer to 50 MB/s, i.e. 1000x
    • anonym's avatar
      Extend remote shell with *safe* file operations. · fb63bad9
      anonym authored
      ... like reading a file, and writing or appending to a file. Now we can
      read/write *any* characters without worrying that it will do crazy
      things by being passed through the shell, as was the case before.
      This commit also:
      * adds some better reporting of errors happening on the server side by
        communicating back the exception thrown.
      * removes the `user` parameter from the VM.file_* methods. They were not
        used, any way, and simply do not feel like they fit. I think the only
        reason we had it initially was because it was implemented via the
        command interface, where a user concept makes a lot of sense.
    • anonym's avatar
      Encapsulate exec_helper's class. · e35abea0
      anonym authored
      ... to not "pollute" the global namespace with all our helpers. This is
      an example of how we can work towards #9030.
      Refs: #9030
  9. 19 Oct, 2016 5 commits
  10. 18 Oct, 2016 1 commit
  11. 27 Aug, 2016 1 commit
  12. 17 Jun, 2016 1 commit
  13. 20 Apr, 2016 1 commit
    • anonym's avatar
      Completely rewrite the firewall leak detector. · c2a2465c
      anonym authored
      The old design was very inflexible, which over time lead to the
      implementation growing messy as different checks were added. The
      issue was that it had to hard-code the particular checks we
      wanted, and did not allow the user to formulate an expression for
      which packets are considered leaks or not. So, let's instead
      provide an assertion-like function to which the user passes a
      block describing how we want all our packets to look.
      Furthermore, now all firewall leak tests should be ok with the
      simulated Tor network provided by Chutney. Since all Tor nodes
      (incl. bridges) run from the same host (and IP address) we also
      include the server port when verifying that no unexpected hosts were
      Note that in some cases we've lost a bit of information and
      precision, e.g. among the anti-tests we no longer exactly match
      the protocol that was leaked, but that wasn't very valuable to
      begin with, and instead we test *exactly* the code that these are
      anti tests for -- a true anti test, indeed!
      Also, the 'no traffic has flowed to the LAN' (now renamed) had a
      serious bug which was fixed in passing -- the `@lan_host`
      variable was not set, so it is `nil`, which could never be among
      the IPv4 TCP leaks, so that step always succeeded! :S
  14. 05 Apr, 2016 1 commit
  15. 30 Mar, 2016 1 commit
  16. 26 Jan, 2016 1 commit
    • intrigeri's avatar
      Test suite: bump a bit the timeout used when waiting for the remote shell. · 01a1d6f4
      intrigeri authored
      We still see "Remote shell seems to be down" caused by a timeout,
      and last time it happened the system was under heavy load.
      I would like to discard any chance that we're simply not waiting long
      enough. Given we wait up to 30 minutes for the system to boot, we can as
      well wait for a few more dozens seconds for the remote shell to start.
  17. 22 Jan, 2016 1 commit
  18. 19 Jan, 2016 2 commits
  19. 07 Jan, 2016 1 commit
  20. 06 Jan, 2016 3 commits
    • anonym's avatar
      Add disk device to disk name mapping. · c6c319ca
      anonym authored
      Sorry for the code duplication. Something will be done about it later:
      Refs: #10864
    • anonym's avatar
      Make it possible to eject CD-ROM from running VMs. · 57b71e2b
      anonym authored
      I looked at how virsh does it (the --eject option), and it removes the
      <source> element (specifically *without* the DEVICE_MODIFY_FORCE, so
      we drop it), claiming it is "the documented way" but I failed to find
      any reference to this. Any way, it works, although Libvirt thinks it
      doesn't, throwing in error that we carefully has to match and ignore.
    • anonym's avatar
      Remove unused, irrelevant and partly incorrect code. · 42b84908
      anonym authored
      The 'tray' attribute cannot be updated on running domains, and for our
      purposes (refs: #5472) it's not useful for stopped domains.
  21. 29 Nov, 2015 2 commits
  22. 18 Nov, 2015 1 commit
  23. 17 Nov, 2015 1 commit
  24. 29 Oct, 2015 1 commit