From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Teuthology queuing & archiving (was: teuthology and jenkins)
Date: Tue, 10 Sep 2013 18:32:56 +0200 [thread overview]
Message-ID: <522F49B8.6070103@dachary.org> (raw)
In-Reply-To: <5229D396.3010601@dachary.org>
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
Hi,
In the context of the OpenStack CI, James E. Blair wrote http://git.openstack.org/cgit/openstack-infra/nodepool/tree/ which is described in the Nodepool part of http://amo-probos.org/post/15 It seems a good an minimal candidate to provision machines. I'm on irc.freenode.net#openstack-infra where all these tools are discussed and will try to understand more about "gear".
Cheers
On 06/09/2013 15:07, Loic Dachary wrote:
> Hi,
>
> I've explored the idea to use jenkins as a remplacement for the queue + archive mechanism of teuthology. It turns out to be jenkins weak point. As Robert Colins ( who recently wrote a HOWTO on how to replicated the CI infrastrcture of OpenStack and is confident someone could do the same within a couple of days https://review.openstack.org/#/c/45346/ ) puts it:
>
> "OpenStack uses jenkins for it's core capabilities - running tests in a work environment, and replaces the scheduler, archiver etc with their own to avoid scaking issues with the naive approaches jenkins has".
>
> Robert further suggested that using the OpenStack CI infrastructure would be a good pick for Ceph.
>
> 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 --]
prev parent reply other threads:[~2013-09-10 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 13:07 teuthology and jenkins Loic Dachary
2013-09-10 16:32 ` Loic Dachary [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=522F49B8.6070103@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox