Weekly teuthology meeting #2

[Loic Dachary <loic@dachary.org>]

[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]

Hi,

Today 8pm paris time / CEST was the second teuthology meeting. The general idea of these meetings is to get together developers using teuthology ( or willing to use teuthology ) outside of Inktank and people using it inside inktank. The goal is to help transition from an internal tool to something that's installable and upgradeable by any Ceph developer. 

The next meeting will be held 8pm paris time / CEST october 3rd, 2013. The IRC channel is irc.oftc.net#ceph-devel and the conference room is mumble.upstream-university.org ( http://www.mumble.com/mumble-download.php ). It is timeboxed to one hour.

I don't commit to write transcripts of these meetings but here is an idea that was discussed today:

  A teuthology installation is setup on machines that can be
  accessed by external people. Inktank publishes the ssh public key of
  trusted ceph developers. These keys are injected in the teuthology
  machines. When a test fails ( could be a very long running test ),
  the bug report filed on tracker.ceph.com mentions the teuthology
  host to which a developer could connect to get more information from
  the live system. An example would be the problem Mike is facing
  where it appears that RBD with lots of writes and almost no reads results
  in fragmentation over a period of days. Difficult to describe and
  even more difficult to reproduce from what can be included in the
  description of an issue. Probably much easier to create a YAML
  scenario and let a few machines online for a few weeks that exhibit
  the problem for Ceph developers to examine. 


Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre
All that is necessary for the triumph of evil is that good people do nothing.





[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]