From: Kefu Chai <kchai@redhat.com>
To: Tomas Meszaros <exo@tty.sk>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: GSOC 17 questions: ceph-mgr: Slow OSD Identification, Automated Cluster Response
Date: Tue, 28 Mar 2017 09:38:01 -0400 (EDT) [thread overview]
Message-ID: <874212646.6755154.1490708281023.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170327203103.16f21220@beast>
+ ceph-devel
----- Original Message -----
> From: "Tomas Meszaros" <exo@tty.sk>
> To: kchai@redhat.com
> Sent: Tuesday, March 28, 2017 2:31:03 AM
> Subject: GSOC 17 questions: ceph-mgr: Slow OSD Identification, Automated Cluster Response
>
> Hi,
>
> I've found your email on the ceph gsoc page. I'm contacting you in
> regards of the project "ceph-mgr: Slow OSD Identification, Automated
> Cluster Response", which seems like it would be good match for me.
>
> I have read the information on the ceph gsoc web page and have some
> additional questions:
>
> - What kind of additional documentation should I read about the project
> idea before writing an application? I've read some basic information
> about ceph-mgr and osd online. If possible, can you please point me to
> the location (code/docs/...) where can I find the most relevant
> information?
you can find more information on our mailing list and by searching it over
internet.
> c
> - Main ceph gsoc page contains this point: "Submit a patch for Ceph".
> I would like to ask if applicants need to submit the path before
> submitting application. If so, what kind of patch should I submit?
yes, you are expected to include link(s) to your contribution in your
proposal.
> (What kind of quality is expected? Should I fix some bug? etc.)
all kinds of contribution/patch are welcomed. but please note, you would
be evaluated on your GSoC proposal and on any previous work that you have
contributed to Ceph.
parent reply other threads:[~2017-03-28 13:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170327203103.16f21220@beast>]
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=874212646.6755154.1490708281023.JavaMail.zimbra@redhat.com \
--to=kchai@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=exo@tty.sk \
/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