CEPH filesystem development
 help / color / mirror / Atom feed
From: Sagar Sarange <sagar.sarange9@gmail.com>
To: Ali Maredia <amaredia@redhat.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Ceph Contribution
Date: Tue, 28 Mar 2017 20:21:40 +0530	[thread overview]
Message-ID: <58DA787C.7030807@gmail.com> (raw)
In-Reply-To: <67070124.111915910.1488222937080.JavaMail.zimbra@redhat.com>

Hello everyone,
I had gone through the Ceph documentation and now I have a good 
understanding of Ceph and its architecture and its working.
I had also gone through the Ceph GSoC-2017 project ideas list and 
figured out following ideas :
1.Ceph mgr :Pool PG_NUM Autotuning.
2.Ceph mgr :Commands for CephFS clients Auth Caps creation.
3.RGW: Local file backend for RGW.

Give me information about the above ideas and issues regarding the above 
ideas ,so that I will solve issues regarding it and clear my understanding.
And will right a good proposal for GSoC 2017.

Thanks,
Sagar

On Tuesday 28 February 2017 12:45 AM, Ali Maredia wrote:
> Sagar,
>
> If you're interested in doing GSoC, I would definitely explore the current ideas on the Ceph website (http://ceph.com/gsoc2017-ideas/) as well.
>
> - Ali
>
> ----- Original Message -----
>> From: "Sage Weil" <sage@newdream.net>
>> To: "Sagar Sarange" <sagar.sarange9@gmail.com>
>> Cc: ceph-devel@vger.kernel.org
>> Sent: Monday, February 27, 2017 9:36:29 AM
>> Subject: Re: Ceph Contribution
>>
>> On Mon, 27 Feb 2017, Sagar Sarange wrote:
>>> Hello everyone,
>>> I am Computer Science Undergraduate student .I am good in C,C++ and Python.
>>> I am eager to do contribution in Ceph.I also go through Ceph repository,but
>>> I
>>> didn't understand where to start.
>>> I appreciate any feedback and guideline you could give so I can be a Ceph
>>> contributor.
>>> I am also interested to be a part of Ceph GSoC 2017.
>> Hi Sagar,
>>
>> A good place to stat might be to look at the trello board at
>>
>> 	https://trello.com/b/ugTc2QFH/ceph-backlog
>>
>> which has several smaller items under the cleanup list and elsewhere.
>> Cards marked in green or orange are small to medium-sized.  There is also
>> the tracker at
>>
>> 	http://tracker.ceph.com/projects/ceph/issues
>>
>> which has lots of bugs and features.  In both cases you'll probably need
>> to talk to folks in #ceph-devel or here on the mailing list to get more
>> context.
>>
>> Thanks!
>> 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
>>


  reply	other threads:[~2017-03-28 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27 13:12 Ceph Contribution Sagar Sarange
2017-02-27 14:36 ` Sage Weil
2017-02-27 19:15   ` Ali Maredia
2017-03-28 14:51     ` Sagar Sarange [this message]
2017-02-27 15:19 ` Mark Nelson
2017-02-27 15:27 ` Lenz Grimmer
  -- strict thread matches above, loose matches on Subject: below --
2017-03-28  6:12 Sagar Sarange

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=58DA787C.7030807@gmail.com \
    --to=sagar.sarange9@gmail.com \
    --cc=amaredia@redhat.com \
    --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