From: Loic Dachary <loic@dachary.org>
To: Sage Weil <sage@inktank.com>, ceph-devel@vger.kernel.org
Cc: hugh.saunders@rackspace.co.uk
Subject: Re: teuthology consumability
Date: Thu, 07 Nov 2013 23:28:16 +0800 [thread overview]
Message-ID: <527BB190.2010302@dachary.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1311070711080.17943@cobra.newdream.net>
[-- Attachment #1: Type: text/plain, Size: 2118 bytes --]
Hi Sage,
On 07/11/2013 23:21, Sage Weil wrote:
> Hey all,
>
> I've had a couple different conversations with week with organizations
> that want to ramp up their ceph development efforts, as a big piece of
> that, spin up their own teuthology environments. There has been a lot
> going on here, and I haven't been on the weekly calls, but I suspect
> things that will help them move forward include:
>
> - documenting a teuthology install-from-scratch. this would include
> setting up the databases, lock server, workers, etc., and will initially
> be long and ugly but will hopefully shrink over time.
>
> - adding support for euca2ools or some other cloud client that does
> openstack and ec2 for creating/destroying test machines. hopefully most
> of the integration points are mapped out from the downburst integration
> work.
>
I'm including Hugh Saunders on this thread : we discussed this topic during the OpenStack summit this week in relation to the associated ticket:
http://tracker.ceph.com/issues/6502
> - ongoing work to collapse the locking and queuing and reporting into a
> unified and/or cohesive service.
It looks like it could be associated with http://wiki.ceph.com/01Planning/02Blueprints/Firefly/Ceph-Brag for performance related tasks. Does that sound sensible ? I'm midly drunk tonight and possibly writing nonsense ;-)
Cheers
>
> I'm probably missing things and/or vastly oversimplifying, but hopefully
> others can chime in an improve this list. I think the better roadmap we
> have here, the easier it will be for new people to come online and focus
> their efforts where they will make the most difference.
>
> Of course the upcomign CDS is a good place to discuss this, but something
> should be written down first to guide/frame that discussion.
>
> sage
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-11-07 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 15:21 teuthology consumability Sage Weil
2013-11-07 15:28 ` Loic Dachary [this message]
2013-11-08 1:08 ` Sage Weil
2013-11-08 7:19 ` Hugh Saunders
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=527BB190.2010302@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=hugh.saunders@rackspace.co.uk \
--cc=sage@inktank.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.