From: Kefu Chai <kchai@redhat.com>
To: Sphoorti Joglekar <scjoglek@andrew.cmu.edu>,
Ceph Development <ceph-devel@vger.kernel.org>
Cc: Sage Weil <sweil@redhat.com>, Priya Avhad <pavhad@andrew.cmu.edu>
Subject: Re: Regarding projects ideas in Ceph
Date: Tue, 28 Mar 2017 09:19:18 -0400 (EDT) [thread overview]
Message-ID: <733381147.6747251.1490707158110.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAN_nQV6VBDywFmQ0BnCjc0naoS3yUmRs3=wWykRFV-HthOnerQ@mail.gmail.com>
+ ceph-devel
Sphoorti, please send your questions to the ceph-devel mailing list instead of
sending it in private. that would help you to get more help from the community.
----- Original Message -----
> From: "Sphoorti Joglekar" <scjoglek@andrew.cmu.edu>
> To: "Sage Weil" <sweil@redhat.com>
> Cc: "Priya Avhad" <pavhad@andrew.cmu.edu>, "Kefu Chai" <kchai@redhat.com>
> Sent: Tuesday, March 28, 2017 1:30:36 AM
> Subject: Re: Regarding projects ideas in Ceph
>
> Hi Sage,
>
> The infrastructure that we are currently using is a 4GB RAM ubuntu vm
> running on virtualbox and we tried following the above steps but the
> compilation is very slow and does not succeed in the end. We even tried on
4GB RAM could be a little bit small for compiling Ceph. maybe we can fix the
compilation failure if the compiling process was not killed by kernel due to
out of memory. but you need to pastebin the error messages.
> an ec2 instance but were unable to get it working there too owing to lower
> RAM and memory constraints. (t2.micro we used as it is available on student
> account).
>
> We would be willing to do the preliminary work for auto_tuning or any other
> smaller module and later develop on it.
i think you could take a look at http://libcrush.org/main/python-crush, which
allows a developer to perform experiments on CRUSH with different settings.
>
> Best Regards,
> Sphoorti Joglekar
>
>
parent reply other threads:[~2017-03-28 13:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAN_nQV6VBDywFmQ0BnCjc0naoS3yUmRs3=wWykRFV-HthOnerQ@mail.gmail.com>]
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=733381147.6747251.1490707158110.JavaMail.zimbra@redhat.com \
--to=kchai@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=pavhad@andrew.cmu.edu \
--cc=scjoglek@andrew.cmu.edu \
--cc=sweil@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox