From: Mark Kirkwood <mark.kirkwood-6STWZtX7tXAqAMOr+u8IRA@public.gmane.org>
To: ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: ceph-users-Qp0mS5GaXlQ@public.gmane.org
Subject: Re: ceph-deploy progress and CDS session
Date: Wed, 07 Aug 2013 13:34:22 +1200 [thread overview]
Message-ID: <5201A41E.3000601@catalyst.net.nz> (raw)
In-Reply-To: <alpine.DEB.2.00.1308021100150.22864-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
One thing that comes to mind is the ability to create (or activate)
osd's with a custom crush specification from (say) a supplied file.
Regards
Mark
On 03/08/13 06:02, Sage Weil wrote:
> There is a session at CDS scheduled to discuss ceph-deploy (4:40pm PDT on
> Monday). We'll be going over what we currently have in backlog for
> improvements, but if you have any opinions about what else ceph-deploy
> should or should not do or areas where it is problematic, please reply to
> this thread to let us know what you think, and/or join the CDS discussion
> hangout.
>
> For those who haven't noticed, we now have a full-time devoloper,
> Alfredo Deza, who is working on ceph-deploy. He's been making huge
> progress over the last couple of weeks improving error reporting,
> visibility into what ceph-deploy is doing, and fixing various bugs. We
> have a long list of things we want to do with the tool, but any feedback
> from users is helpful to make sure we're working on the right things
> first!
>
prev parent reply other threads:[~2013-08-07 1:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 18:02 ceph-deploy progress and CDS session Sage Weil
[not found] ` <alpine.DEB.2.00.1308021100150.22864-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2013-08-02 18:39 ` Dewan Shamsul Alam
2013-08-02 19:44 ` Eric Eastman
2013-08-07 1:34 ` Mark Kirkwood [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=5201A41E.3000601@catalyst.net.nz \
--to=mark.kirkwood-6stwztx7txaqamor+u8ira@public.gmane.org \
--cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ceph-users-Qp0mS5GaXlQ@public.gmane.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 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.